Commit Graph

24 Commits

Author SHA1 Message Date
Vadim Yanitskiy 0448871bac */osmo-bsc.cfg: BTS type 'sysmobts' (deprecated) -> osmo-bts
Change-Id: I98ea9e96d490473efbbe189842ed9f547060dc7d
2024-03-28 04:42:35 +07:00
Oliver Smith 38f7fcb265 */.release: remove
These files are in .gitignore and get generated at the end of running
'make'. Remove them to have less cluttered 'git grep' output.

Change-Id: Ie5bf05220359ac0941f62cc86ed843363548784a
2022-07-06 12:36:26 +02:00
Vadim Yanitskiy b5ecf1c3ef osmo-bsc.cfg: change logging level nm info -> notice
Stop spamming logs with tons of DNM messages (state changes, events).
GSMTAP emits all these messages (including 'debug' ones) anyway.

Related: I9e60ea0968a44aa29753226626864ac9f4c1f8ab (osmo-ttcn3-hacks.git)
Change-Id: I49352b3caf9f6bbdd594cfcdea54038fc0eaa874
2022-05-29 20:25:56 +06:00
Vadim Yanitskiy 83c6938888 Revert "osmo-bsc-{master,latest}/osmo-bsc.cfg: set AMR link adaptation params"
This reverts commit 029c8df999.

I actually meant to change osmo-bsc.cfg in ttcn3-bsc-test.

Change-Id: I85c577cbc608a77d6d6a5816f1fb7205361f7b4a
Related: SYS#5917
2022-04-16 21:42:02 +03:00
Vadim Yanitskiy 029c8df999 osmo-bsc-{master,latest}/osmo-bsc.cfg: set AMR link adaptation params
The default AMR link adaptation parameters have been changed in
the recent osmo-bsc, so set the old expected default explicitly.

Change-Id: Ic1c46d54ef97278100bd52156ad5627418ef5c97
Related: osmo-bsc.git Ic5f8d55d250976d8d4c9cae2d89480fd52326717
Related: SYS#5917
2022-04-14 22:53:23 +03:00
Oliver Smith 8e95373986 osmo-*-latest: use OSMOCOM_REPO_VERSION
Related: SYS#5370
Change-Id: I237a296ea8a1e08bc31f351c5f42a59fe7438815
2021-05-04 09:30:48 +02:00
Vadim Yanitskiy 79b752fa32 */osmo-bsc.cfg: remove obsolete no-op parameters
Change-Id: Idebf9df98648b3fe8213cae550ce50e9805bac96
2021-03-09 13:50:41 +01:00
Oliver Smith 69b3ecb912 osmo-*-latest: support centos8
Add a new centos8-obs-latest container with shared code (just like
debian-stretch-obs-latest) and adjust the package install blocks in
osmo-*-latest.

Related: OS#5049
Change-Id: I274b31d4903df07e99fd434af25bdb72991f6923
2021-03-04 14:42:32 +01:00
Oliver Smith effdb1a452 debian-stretch-obs-latest: new container
Move common code from osmo-*-latest to debian-stretch-obs-latest:
* add the OBS repository key
* add the OBS repository with "latest" feed
* install telnet
* invalidate the cache once the repository is updated

This is in preparation to make osmo-*-latest work with centos8,
preventing the following issues we would have without this refactoring:
* avoid need to read the repository index of both debian-stretch and
  centos8, and to invalidate the cache if either of them changes
  (instead of just the relevant one). This is currently a problem in
  osmo-*-master/Dockerfile, Id69f3eaf37f823bac0947366f27a25edd277a4cb
  will fix it there.
* no need to add boilerplate code to install the centos8 repository to
  each osmo-*-latest/Dockerfile

While at it, also remove deprecated MAINTAINER lines.

Related: OS#5049
Related: https://docs.docker.com/engine/reference/builder/#maintainer-deprecated
Change-Id: I443d52eba416ea298cc5421e280ad2f4ca59283b
2021-03-04 14:39:46 +01:00
Pau Espin 7d7a06b749 common: Introduce OSMOCOM_REPO_MIRROR param
This allows easily changing to another osmocom repo base URL if the
default one is down.

Related: OS#4862
Change-Id: I8010b08f3dabacfb3c13a44eece6c7a490e0742e
2020-12-02 14:27:02 +01:00
Pau Espin 78ae9377a7 common: Automatize UPSTREAM_DISTRO name based on image name
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
2020-12-01 11:46:20 +00:00
Harald Welte 027826fdba introduce 'REGISTRY' argument to all Dockerfiles
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
2020-11-02 17:02:26 +01:00
Vadim Yanitskiy c69cb106fd osmo-{bsc,msc}.cfg: eliminate 'periodic location update 30'
This parameter has been deprecated in both osmo-msc and osmo-bsc.

Change-Id: I6d33c6d9c43078ee9961d3b076386188ec45be0f
2020-06-01 01:17:35 +07:00
Vadim Yanitskiy 3bd7fc452b osmo-bsc.cfg: drop deprecated '11bit_rach_support_for_egprs'
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
2020-05-29 19:23:55 +07:00
Vadim Yanitskiy 28badfaf6e osmo-bsc.cfg: drop deprecated 'ip.access rtp-base' parameter
Change-Id: Ie5494fd08fc7d2277a087ccc9502b5076fa2565b
2020-05-29 14:34:31 +07:00
Vadim Yanitskiy d210c90a68 osmo-bsc.cfg: drop non-existing 'access-list-name bsc-list'
In the recent osmo-bsc master, this configuration parameter has
been removed, so it fails to start due to "unknown parameter".

Change-Id: I8f763a4b35f80f4db637bebdd8e802a835a9fd2d
2020-05-29 14:34:31 +07:00
Vadim Yanitskiy 34152ebda6 osmo-bsc-{latest,master}/osmo-bsc.cfg: Remove 'nat' from logging
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.

Change-Id: If02272c08ba2df37d1295d09c104d11f96abbe1e
2020-04-05 00:14:29 +07:00
Harald Welte 1bccbb8a66 update OBS Release.key; the old one expired today.
Change-Id: I0dd7d7f54a3eb93ca677f3bdc5e00f62694aaa9e
2020-03-30 18:06:58 +02:00
Pau Espin a9877bf487 Update osmo-*/Dockerfile to log stdout+stderr of process to log file
This way we get VTY parsing failures as well as backtraces upon process
crash.

Related: OS#4212
Change-Id: I9493ff73ef27c7c6d32b00cf827704b3f9cbf86a
2019-11-19 18:29:00 +00:00
Philipp Maier 7cb84b0d16 osmo-bsc-latest: remove obsolete logging categories
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
2019-10-30 13:49:16 +00:00
Vadim Yanitskiy b6c3dd787a .../osmo-bsc.cfg: drop deprecated dyn_ts_allow_tch_f
Since Ib2335d02ea545aff837aadd49f15b2fdb418c46e, this VTY option
is deprecated in osmo-bsc, so let's actualize the config files.

Change-Id: I709e1afd2a9cccdc92eec312dff607947a10c299
2019-01-14 21:07:36 +00:00
Harald Welte ff3dc6e45f ensure well-formed config files
Change-Id: Id687e63c418e2e955ccbb92f2420a80fc0704ea4
2018-09-26 09:27:38 +00:00
Harald Welte cf81610bd4 remove deprecated "dest" config option from config files
Change-Id: I1073846c04a8466f2ccf501e27cf152df09042c5
2018-06-03 17:11:22 +00:00
Harald Welte a421358ab8 Add osmo-*-latest Dockerfiles
Those containers are using the OBS-built "latest" packages on Debian 9

Change-Id: I6a564206dd81743deb1eb27eca7081bc333d7434
2018-05-04 18:12:37 +02:00