docker-playground/ttcn3-bscnat-test
Oliver Smith f997b4e771 network_create: find free subnet automatically
Try multiple subnet numbers until successfully creating a network. This
way we can run the same ttcn3 testsuite multiple times in parallel
without conflicts (e.g. once against latest, once against nightly). Also
we don't need to make sure each new testsuite has a unique subnet
number anymore.

I've considered also adjusting network_bridge_create, but that gets used
exclusively by osmo-ran/jenkins.sh, a script which we don't actually run
in jenkins. It seems that in this script it makes more sense to not get
a random subnet number.

Related: OS#5802
Change-Id: I57152b08ef0f38e17e7019a8df032189b03f56cf
2023-01-16 15:19:29 +00:00
..
BSCNAT_Tests.cfg ttcn3-bscnat: Prepare cfgs for VTY & Osmux support 2019-05-27 18:06:06 +00:00
Dockerfile Use gerrit as osmo-ttcn3-hacks.git git remote 2022-09-20 12:09:32 +02:00
Makefile Add ttcn3-bscnat-test docker image 2018-11-09 17:22:05 +01:00
bscs.config ttcn3-bscnat: Prepare cfgs for VTY & Osmux support 2019-05-27 18:06:06 +00:00
jenkins.sh network_create: find free subnet automatically 2023-01-16 15:19:29 +00:00
osmo-bsc-nat.cfg Update ttcn3-*/jenkins.sh to log stdout+stderr of process to log file 2019-11-20 17:17:45 +01:00