osmocom
/
docker-playground
mirror of https://gerrit.osmocom.org/docker-playground
10
0
Fork 0
Code Releases Activity
docker-playground/ttcn3-mgw-test/MGCP_Test.cfg

17 lines
255 B
INI
Raw Normal View History

Use new split config file + tcpdump support of osmo-ttcn3-hacks This uses osmo-ttcn3-hacks Change-Id I3db452e24e5238aa05254d903739c64d202e61db, which introduces some shared/common config file as well as per-testcase pcap file generation.
2018-02-14 19:04:17 +00:00
[ORDERED_INCLUDE]
"/osmo-ttcn3-hacks/Common.cfg"
"/osmo-ttcn3-hacks/mgw/MGCP_Test.default"
Add mgw-test docker container
2017-11-19 00:50:18 +00:00
Use new split config file + tcpdump support of osmo-ttcn3-hacks This uses osmo-ttcn3-hacks Change-Id I3db452e24e5238aa05254d903739c64d202e61db, which introduces some shared/common config file as well as per-testcase pcap file generation.
2018-02-14 19:04:17 +00:00
[LOGGING]
Add mgw-test docker container
2017-11-19 00:50:18 +00:00
[TESTPORT_PARAMETERS]
[MODULE_PARAMETERS]
move every 'test network' to its own IP address space 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.
2018-02-06 16:41:33 +00:00
mp_local_ip:= "172.18.4.181";
mp_remote_ip:= "172.18.4.180";
Add mgw-test docker container
2017-11-19 00:50:18 +00:00
[MAIN_CONTROLLER]
[EXECUTE]
mgw_test: Use entire "control" section of testsuite Change-Id: Id4121bd6974b58faaa8c471597708085ce14a192
2018-03-28 10:21:36 +00:00
MGCP_Test.control