Similar to what is already done with DISTRO, which points to given image
of ours based on name. This time we do the same with upstream images,
such as debian:stretch or centos:centos8.
This way, for instance calling docker_images_require
"osmo-bsc-latest-centos8" would try to build the
osmo-bsc-latest/Dockerfile file starting from a centos8 image.
Change-Id: I33cb21aa024396974559fd98f9f3c64e2c351eda
This is initialized to docker.io, keeping the default behaviour
if not specified. However, it allows us to specify a private
registry later on.
Related: OS#4839
Change-Id: I32d4ee6256033c809108c1b86cb6b6c58d880f49
EGPRS Packet Channel Request cannot be enabled in 'GPRS only' mode
anyway. Moreover, this command was deprecated. Let's just remove it.
Change-Id: I03733490d9c4bf78a748d22874e550e015fbab78
In the recent osmo-bsc master, this configuration parameter has
been removed, so it fails to start due to "unknown parameter".
Change-Id: I8f763a4b35f80f4db637bebdd8e802a835a9fd2d
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.
Change-Id: If02272c08ba2df37d1295d09c104d11f96abbe1e
The logging categories cc and mgcp are obsolete for osmo-bsc and will
cause recent versions of osmo-bsc to crash. Lets remove this logging
categories from the config file now.
Change-Id: Idd85318abe3fc982909c11115c886835a3d8cd37
Since Ib2335d02ea545aff837aadd49f15b2fdb418c46e, this VTY option
is deprecated in osmo-bsc, so let's actualize the config files.
Change-Id: I709e1afd2a9cccdc92eec312dff607947a10c299