Since osmo-gsm-tester.git Change-Id Ieca65b71b543c44cfcec8e83efd0fe053c432e55,
the -c parameter holds the config file and not the directory where it is contained.
Change-Id: I5aa0507d0e82616ee3cca74573fea6bdb7459b53
As of osmo-gsm-tester.git Change-Id
I7eb69f870d0dcb5906d45ae067d6bed1aabf5862, the enviornment variable
OSMO_GSM_TESTER_CONF is deprecated in favour of already existing -c cmd
line argument. Let's use it while still providing the docker setup with
a way (using same env var name) to modify where the conf dir is to be
found inside the docker container (for instance, to provide an external
conf dir).
Change-Id: I54ea9dc4d0bb205debf312f5a37053bc60cfcdb7
Allow to pass options to each "docker run" line in the various
jenkins.sh scripts. I'm using this to run the testsuites and Osmocom
components in docker with the same configurations as jenkins, but with
Osmocom and testsuite binaries built outside and mounted into the
containers:
DOCKER_ARGS="-v /usr/local:/usr/local:ro -v $hacks:/osmo-ttcn3-hacks:ro"
This allows very short test cycles without a second set of configs. The
full script that makes use of this feature is in osmo-dev.git,
ttcn3/ttcn3.sh.
Change-Id: I8d1f78aee926f8f6ec0b704e16639bc83f525816
Fix error after DGSM-related patches were merged:
osmo-hlr: error while loading shared libraries: libosmo-gsup-client.so.0: cannot open shared object file: No such file or directory
Change-Id: I80554fdbfd2c518868485f84a46c56df985c671c
This can serve as an entrypoint for running open5gs-pgw inside
the open5gs-master container. It will run setup.sh to create the ogstun
device, followed by running open5gs-pgwd as 'osmocom' user.
Change-Id: I4527b5e328fb248552e69961b80b9f791ec74293
Since osmo-gsm-tester.git I364e0859c0851b9167907a4d948b659a0f6a19fb the
example/ directory has been renamed to sysmocom/
Change-Id: I8ca085e02330be51de12066da0555c1bc0c8b767
osmo-bts-virtual fails to start:
Error occurred during reading the below line:
ms-power-control dsp
This BTS model has no DSP/HW MS Power Control support
Failed to parse the config file: '/data/osmo-bts.cfg'
Change-Id: Ic85603db10c11de911d20313caf2f819e92d94d1
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.
Change-Id: If02272c08ba2df37d1295d09c104d11f96abbe1e
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.
Change-Id: I266d6f6ed54d1457b1ca63b87fc1c29f6dd40caf
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.
Change-Id: Ie2afacfc15589c26238214cddc00baaf80e993c1
Since osmo-gsm-tester.git I38bcf6abf789f52c3ed0bee7911567fa872e2491
these features are included and used in the "4g" suite to allow
selecting 4G modems different than srsue.
Change-Id: Ie1942fd661b91218780bc52bb000d192259e2b69
Some days ago the Dockerfile was changed to pull from
debian-stretch-jenkins instead of debian-stretch-build, since the first
one has extra runtime dependencies required by osmo-gsm-tester.
However, the jenkins script is still requiring the old dependency. Let's
update it accordingly.
Change-Id: If33aab60e04da7beb4cd0715d5cb3145c001823a
for some strange reason, the tests developed + merged in September 2019
are not yet automatically executed. Let's fix that.
"latest" should work fine, the BSC side code was already present in 1.6.0
Change-Id: I4408265d1be900359256f5cab553893d03cc8362
This way one can quickly see if osmo-gsm-tester run fine or an issue
ocurred and logs need to be checked.
Change-Id: I0b267889f403fc1505f9dd859568bc15a120dd81
It's set to /tmp/trial by default for convenience, since it's a
temporary directory and easy to remember and to access. Still, let's
give the opportunity to change it (if user wants it to be stored in
persistent data or if has low amounts of non-persistent memory).
Change-Id: I2a7ea361c6156c97bd8d2d94cf1b6856344d4d9f
osmo-gsm-tester uses also the "inst/" directory, so using that name to
install from cmake is not a good idea here, since they will end up in
the same directory under /tmp/trial/inst.
Also, make sure the temporary install dst directory is removed after
creating the archive, since at that point is no longer needed.
Change-Id: Ib6610487140f0703d5817241bc4a63027696c1d4
osmo-gsm-tester.git/contrib/jenkins-build-srslte.sh cannot be used
because there's a need to split the fetch step from the build step.
That's because we want to fetch in the host (in order to use host's user
ssh key for potential private repos) while still building inside the
docker container, where we have all the dependencies (and where the
binaries are going to be run afterwards by osmo-gsm-tester).
During the changes above it was also noticed that /tmp/trial on the host
got its UID+GID changed (because we switch user inside the container to
downscale privileges). Fix it by chown'ing the directory back to the
host user's UID+GID.
Change-Id: Ia0db8fba840392a0b7883cfc15e45c2e80407a16
That image contains extra runtime dependencies (such as libua5.3) which
may be required by software run by osmo-gsm-tester.
Change-Id: I5c6239e1beb0cdc6d2b1477ddb60d66debe5d1aa
After this patch, one can run osmo-gsm-tester with specific parameters
(debug level, suite and tests to run, etc.) by using
OSMO_GSM_TESTER_OPTS variable:
OSMO_GSM_TESTER_OPTS="-s 4g -t ping -l error" ./jenkins.sh
Change-Id: I2e8ff51a3152125148c6a117a987e8c11a576e1e
We currently build libulfius 2.5. It doesn't say anywhere in osmo-remsim
that libulfius-3.6.4 is required anyway.
Change-Id: Ie6b07f676f8e06959eaac5e865c163de3f9c939d
These are required to allow setting rt prio for jenkins user inside the
docker container, as well as for being allowed to create coredump files.
Change-Id: I8ed6193196d739c1416976d431d07b8a0c55ee2a
* Fix wrong KI.
* Add an extra IP address to slave so that ENB and EPC can be run on
different IP addresses and their GTP ports don't collide.
* Add required rf parameters to resources.conf
Change-Id: I0198bc99f75e9567ee717aa79e434ec28705fac9
Currently srsLTE trials link against soapySDR library to have LimeSDR
support. We need to move installation of those new packages further
below in the Dockerfiler because that lib version is only available with
osmocom repositories (which were added at a later point in the file).
Change-Id: Ia0e506954ffebd94adb75fec6bf481e41f9ec436
This set up allows running a typical osmo-gsm-tester set up with a main
unit (ogt-master) attached to one (or more) slaves where resources are
located and processes are run.
As an example, current config allows running an iperf3 test over an srsLTE
stack using the ZeroMQ backend.
Change-Id: Iac7c0b613048ce332642d3957c55cc7c53b56d42
This way we can actually tests TPDU transmission from a simulated
remsim client through the real bankd into a simulated SIM card.
Change-Id: I584e4c5e3d120bfbd26ade545fe41e541308f26a
This way we can run the container with osmo-remsim-bankd + ifd-vpcd,
i.e. with a simulated smart card reader behind the bank.
Change-Id: I463eca0f66197b409e00028e75e9501de620cc8b
The upstream redmine container/image has meanwhile upgraded to a more
recent version of the ruby base modules which don't require to be
patched anymore.
Change-Id: I0fd7684bdab55eece889a7d9e524ec2a25b30a3b
Disable mp_hlr_supports_dgsm, until patches providing the VTY commands
are merged to osmo-hlr.git.
Related: OS#4380
Change-Id: I766d54c65ae9e7b6333f9bcfce49a70c588845d0
Since examples/sccp_demo_user (the binary used to test SCCP) is not
installed by libosmo-sccp.git during make install, we need to install it
manually after "make" step, and hence it's only available in
osmo-stp-master, because in osmo-stp-latest we used packaged files.
Related: OS#4343
Depends: osmo-ttcn3-hacks.git Ied9fbfb9bd35a99205ca13db033dd9ea03d51238
Change-Id: I5a7e6ff5f6e5f6e34d6a5ab29bd760a6f9d49c4b
Match username of debian-stretch-jenkins, so we can use the same docker
arguments for both images in gerrit-verifications.yml of osmo-ci.git.
Related: OS#4345
Change-Id: Ia3eaec6090c9652549b2850de74ee21730374bbd
Pau Espin
Harald Welte
Oliver Smith
Vadim Yanitskiy