osmo-gbproxy-master is derived from osmo-sgsn-mater, and the former
needs to be re-built to catch up with osmo-sgsn.git changes (Where
the osmo-gbproxy source code is located)
Change-Id: I8abc9f89d19d657403569b7705cd923342ff300b
For some magic reason, apt segfaults while installing the DEBs:
$ apt install ./libfftranscode0_0.3_${DPKG_ARCH}.deb \
./libfftranscode-dev_0.3_${DPKG_ARCH}.deb
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Segmentation fault (core dumped)
so it kind of confirms the warning about its stability ;)
Change-Id: I7f3288161577b055145afe89de7dff50853760f5
In Change-Id I80de01c96185c60fe2de7a8ffa9daed2669658e1 we introduced
the wrong hdlcnetX device names. We must use each devoce only once,
rather than trying to use hdlcnet1..4 twice.
Change-Id: I56f75995fe94b46b0210de2a4f83e384b4e4ca4f
In Change-Id I80de01c96185c60fe2de7a8ffa9daed2669658e1 we updated
only the osmo-gbproxy.cfg, but noth the GBProxy_Tests.cfg for the
test suite, which of course won't work.
Change-Id: I35603dc76926d76e57993f7eab1354eea8d25dad
Related: SYS#5226
We are using centos8 as distro name instead of centos everywher else
and jenkins-common.sh are expecting that.
Related: OS#4888
Change-Id: I05b012abced5b812e74315ccf64365896412e876
This allows easily changing to another osmocom repo base URL if the
default one is down.
Related: OS#4862
Change-Id: I8010b08f3dabacfb3c13a44eece6c7a490e0742e
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
Testing FR support in osmo-gbproxy is a bit more complicated
as it involves the "hdlc" net-devices privded by the hdlc_fr.ko
kernel module.
So we need to
* run on a host with actual hdlc net-devices (e.g. dahdi_dyamic_loc)
* move those net-devices into the containers after starting them
* wait for the net-devices to appear in the containers before starting
either gbproxy or the test suite
Change-Id: Id4b52877db53cb6e59f6d0d3f754aaae633949e8
Using a separate container will allow us to do gbproxy specific things
like waiting for physical net-devices to show up in the docker netns
before actually starting the osmo-gbproxy executable
Change-Id: I5e6351055ac9430f13e43291cf2a9d52683fe6bf
In osmo-ttcn3-hacks.git Change-Id If1220852785853f8a5d8de183d5053ddd6ccb958
we introduce support for multiple NS-VC inside a NS-VCG. This modifies
the configuration structures, and we need to adjust all config files
accordingly.
Change-Id: I6ac250555c3ac2aa8feb70bd3a052aafec5d4210
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
This is needed on the target remote hosts, where osmo-gsm-tester will
install a copy of the script to run remotely at runtime.
Change-Id: I59151dfe7091628707cd016db42171d22729a60c
The python bindings of gnuradio are used to control a zmq connection
broker between srsENB and srsUE to emulate attenuations.
Change-Id: Ic4e8c4d6a5d1e20dd336ff15868c7c3f51dea323
This part is missing from the already merged
I3394f391a6068ab8afeafa329b69a8ae4ad05cd9
which enabled LCS tests for osmo-bsc.
Change-Id: I873d6e46e00ee0e91b15d719829baff2bf9f115a
We currently only invalidate the cache if the Debian repository changes,
but not if the CentOS repository changes. This leads to strange
artefacts, such as CentOS containers for osmo-bts-master using an
old libosmocore, despite a new one being available in the repo.
As Dockerfiles don't support conditional "ADD", we need to actually
add both the CentOS and the Debian repsotiry file, so any change
in either of the two will now (unneccessarily) invalidate the cache
for both Debian and CentOS builds.
Change-Id: I7b13644afb9d3be3b94184193177e003c13718d3
Notably LCS tests are still disabled, just routing BSSMAP-LE/SCCP via STP to
the virtual SMLC is now possible.
Change-Id: Ic296291886ce18fd3ff34d45c519de605ba827cc
Introduce this switch for enabling the Lb interface startup, and first off set
to false everywhere. A later patch will enable Lb where it makes sense.
Depends: Idf463c3c2169cad953b4ebc5b5845b31d5efb848 (osmo-ttcn3-hacks)
Change-Id: Id26064931c482c25217bccdeec866e9afc1fd9b5
For more details, see Ie87820537d6d616da4fd4bbf73eab06e28fda5e1.
Change-Id: Ibe7eac7ff82955fab16373fae6d9ef4efb35a3a5
Depends: If6245d73ed701e631b67146ace4ba028bdb4226c
Depends: Icebee25b53fef623db6ae91ca0d943e70a3c86b7
osmo-gsm-tester requires patchelf 0.11 since a while ago to solve some
bugs on older versions. See osmo-ci
d276db78afbb3f28fc6a4a949bca131d0cfac1d4 for more information.
Related: OS#4389
Change-Id: I3a0c2168420d2a4ee2302a191824f571ec17786b
In Change-Id I6904520d8c2f546327029777d68b1907611a8cf5 of
osmo-ttcn3-hacks, we change the structure of NSConfiguration. Let's
adjust the configs accordingly.
Change-Id: I8c5e59e79b69c13632d69f5011be9279b827a4fa
Depends: osmo-ttcn3-hacks I6904520d8c2f546327029777d68b1907611a8cf5