Harald Welte facbb6575e 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 19:08:45 +01:00
..
.release	add ttcn3-bsc-test container with osmo-bsc test suite	2017-12-17 17:21:04 +01:00
BSC_Tests.cfg	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00
Dockerfile	ttcn3-bsc-test: Add missing 'git fetch'	2018-01-27 20:25:10 +01:00
Makefile	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00
jenkins.sh	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00
osmo-bsc.cfg	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00
osmo-stp.cfg	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00