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

10 Commits

Author SHA1 Message Date
Harald Welte a8d0c95710 gbproxy: Add mp_gbproxy_ip to check BVC FSM state 
In docker-playground.git I272e43b9be8ba53d8a815e8ab099c939f63413a7
we introduce FSM state introspection and we need to add the CTRL
hostname here.

Change-Id: Idcd77353a661cfc1685ded64b5993ff63637addc
 2021-04-09 10:40:54 +02:00
Harald Welte 22b58d7ecc osmo-gbproxy: fix configuration 
also, only change those values from their default values that are
neccessary to change; fall-back on the defaults whenever possible.

Change-Id: I5fba21ddf1854ed2b4f829785ab016dfa284456e
 2021-01-21 20:54:18 +01:00
Harald Welte 98365d159f gbproxy: Use separate NS-VC for data + signaling 
This follows the change implemented in osmo-ttcn3-hacks.git
If0e404bdf2c30a5e18748695608611be83f61109 to use data-only
and signalling-only NS-VCs on the SGSN side

Change-Id: I58f8a6d1c8d01551d366bd7d0dbfb892cce512ae
Requires: osmo-ttcn3-hacks.git If0e404bdf2c30a5e18748695608611be83f61109
Related: OS#4953
 2021-01-21 09:43:20 +00:00
Harald Welte 9f53e36985 gbproxy,pcu,sgsn: Update config files 
In upstream I9798e639b4bc8658482945970775b012b5840779 we introduce
two additional fields per NSVC (data_weight, signalling_weight). Make
sure those are specified everywhere.

Related: OS#4953
Requires: osmo-ttcn3-hacks.git I9798e639b4bc8658482945970775b012b5840779
Change-Id: Ic607b3edc3bf724a8b2dbd6be8c806002c229509
 2021-01-21 09:43:20 +00:00
Harald Welte d12441a935 gbproxy: Update configs for SGSN poool with 2 SGSN, NRI, ... 
Change-Id: Iac57e079d1375f186ddc200471bad1fa622c8860
 2021-01-17 19:26:34 +01:00
Alexander Couzens 663c77203b gbproxy-fr: Enable IP-SNS towards SGSN 
Change-Id: Id59cc404c355a3f494ad60be8d3a499b217084ec
 2021-01-11 22:50:59 +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
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