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	bumped to version 0.1.0	2017-08-20 11:58:18 +02:00
Dockerfile	m3ua-test: Generate junitxml output for jenkins integration	2017-08-20 11:22:50 +02:00
Makefile	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00
all-sgp-tests.txt	m3ua-test: Generate junitxml output for jenkins integration	2017-08-20 11:22:50 +02:00
dotguile	Dockerfile for a containes with m3ua-testtool / sua-testtool	2017-05-03 16:50:02 +02:00
jenkins.sh	move every 'test network' to its own IP address space	2018-02-06 19:08:45 +01:00
m3ua-param-testtool.scm	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