Open GPRS services and do not restart the osmo-sgsn every 24 hours.
Let's see how long it runs and how everything behaves with the maximum load
we can give it.
The old (soon to be removed) openbsc class installed
the osmo-sgsn dependent on a config parameter. Leave the config
param as a possibility to be set to 'disabled', but otherwise
install and run the sgsn.
Prevent errors output from cron jobs trying access the sgsn vty
The creation of this file should depend on the Vcsrepo, not on the File
directive, otherwise on an initial install if the file is created first,
then Vcsrepo will refuse to clone the repo:
Error: Path /var/rhizomatica exists and is not the desired repository.
At least on Debian 10, use msmtp and install a basic configuration.
Previously the network was using a mishmash of exim, sendmail or
whatever happened to be installed. For the moment, install the config
also on debian9, some of which are using ssmtp, which is no longer
maintained in debian :(
In a development, you may not want puppet to change the remote and branch
in the rccn repo, so now you can disable that by setting the hiera param
'notouchrepo' - which cause the repo to rnu with a schedule of 'never'
This commit installs the osmo stack daemons and configuration
if the hiera parameter rhizo::osmo_stack is 'split'
Setting this param won't break anything for a nitb based install,
but it will disable running the nitb and run osmo-bsc instead.
Introduces a multiple file template and iterates over the defined
BTS array from the hiera data.
This is really a backport of the as yet uncommitted work on creating osmo-*
config files for the split stack. Making this change here for the nitb will
allow for removal for some deprecated variables in hiera.
At this time, I don't think there is any site that is actually using
a puppet-generated nitb config file, but if there were, the results of this code
should be more less funcionally equivalent, providing the BTS definition is correct.
