After merging Change-Id: Ie844c4de62e0ef5d5c4c366185968211a7f6d676
in osmo-ttcn3-hacks, the module parameters for BSSAP configuration
require one extra argument.
Change-Id: I2a0011bc6f7bdf013005d1ea36da591673344eed
Related: OS#2544
In osmo-ttcn3-hacks Change-Id I52a4c8118828c1605cf672889982f987568ad17d
we introduced changes to the BSSAP_Adapter, but the config file for
the BSC hasn't been updated accordingly here.
Change-Id: I7cfc6414c1a783bab54f0d82589de82af4764daa
Allow the osmo-bsc-main docker container to reach the virtual MGW set up by the
ttcn3-bsc-tests.
The module parameter mp_test_ip sets the IP address at which the virtual
services are set up to listen for connections -- currently actually only the
virtual MGW. Set this to 172.18.2.203 instead of using the default 127.0.0.1.
This fixes the second half of the disconnect between BSC and virtual MGW in
this docker setup. The first half is Ib53f000ec7e717b14a3e5df6e803d3d0950b937f
Change-Id: I3038481ed0bba1084b63dc6a6d2ff6e970100890
In osmo-ttcn3-hacks, we have removed the *.control from the *.default
files, so let's add it here in the config files. You can now change
the tests to be executed by simply editing the config here.
This uses osmo-ttcn3-hacks Change-Id
I3db452e24e5238aa05254d903739c64d202e61db, which introduces
some shared/common config file as well as per-testcase pcap file
generation.
Ideally we would want to launch a group of containers with their own
private network segment and use the same static IP addresses in those
isolated networks.
The stupidity of docker is requiring unique IPv4 addresses even on
isolated (!) networks. This means we have to manually give each of our
test setups a different subnet, and then we can at least run one
instance that test in parallel to at most one instance of each other
test.
If this weird reestriction about unique IPv4 addresses didn't exist,
we could start any number of test runs in parallel.
Harald Welte
Neels Hofmeyr