osmocom
/
docker-playground
mirror of https://gerrit.osmocom.org/docker-playground
10
0
Fork 0
Code Releases Activity
595 Commits 32 Branches 14 Tags 9.9 MiB
Commit Graph

7 Commits

Author SHA1 Message Date
Harald Welte a10c26d6f7 ttcn3-gbproxy-test-fr: depend also on osmo-sgsn-master 
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
 2020-12-11 12:16:07 +01:00
Harald Welte 233d37ee88 ttcn3-gbproxy-test-fr: Fix hdlcnet device names 
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
 2020-12-09 19:28:51 +01:00
Harald Welte d3dacd4ad4 gbproxy-test-fr: Fix syntax error in config file 
It's mp_enable_bss_load_sharing, not mp_enable_load_sharing

Change-Id: I0d2241e0d9e376f27d04721034b1e197901aa662
 2020-12-09 12:02:39 +01:00
Harald Welte 5e299ecfea gbproxy: Enable test of load-sharing when running over FR 
Change-Id: I2ce1f67dc8f45f7a62a923e45fb479c4c482eec9
Depends: osmo-ttcn3-hacks.git I96e8b6a1a69148f770476e87c920dc256c1d7379
Related: OS#4520
 2020-12-08 08:37:53 +01:00
Harald Welte 01eb160c53 gbproxy: update ttcn3 configuration to reflect osmo-gbproxy.cfg 
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
 2020-12-08 08:37:53 +01:00
Daniel Willmann 2689304aa5 ttcn3-gbproxy-test-fr: Catch up with config changes 
Change-Id: I80de01c96185c60fe2de7a8ffa9daed2669658e1
Related: SYS#5226
Depends: I698a932b3dc78c776e9350283109463bcdc40e6b (osmo-ttcn3-hacks)
 2020-12-04 20:09:04 +01:00
Harald Welte b83c28fc34 Add ttcn3-gbproxy-test-fr for FR related testing 
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
 2020-11-30 15:50:31 +01:00