osmocom
/
docker-playground
mirror of https://gerrit.osmocom.org/docker-playground
10
0
Fork 0
Code Releases Activity
1,015 Commits 31 Branches 14 Tags 9.6 MiB
Commit Graph

8 Commits

Author SHA1 Message Date
Oliver Smith 4f459b779e docker kill: wait until containers are stopped 
As "docker kill" / "docker container kill" (alias) doesn't block until
the given container stops, make sure to always run "docker wait"
afterwards.

Closes: OS#5928
Change-Id: I0242ece96541d8036ebbf8b0f498ebf231db26b5
 2023-03-07 09:02:02 +00:00
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
Oliver Smith 9a2556824a scripts/regen_doc: use SUBNET variable 
Add a $SUBNET parameter and use it throughout the script, similar to
other ttcn3-*/jenkins.sh scripts. This is in preparation for figuring
out a free network in network_create() automatically in a future patch.

Related: OS#5802
Change-Id: I3bda4bd7280469ad5ee02104295134a2e0b768e3
 2022-12-22 13:59:10 +01:00
Harald Welte 306a51dd30 Enable IPv6 in docker networking 
We previously only allocated IPv4 sub-nets to the network segments
created with 'docker network'.  Let's fix that by assigning both
IPv4 and IPv6 address ranges to each docker network.

Related: OS#4700
Change-Id: I8802208fddcce1ffa57e5626575d23d02b320d99
 2020-08-13 15:01:58 +00:00
Daniel Willmann 533fef5815 regen_doc: Change IP network to an unused subnet 
Previously we were using 178.18.12.0/24 which could have conflicted with
the osmo-bsc sccplite TTCN3 tests.

Change-Id: Ib5ab391ebb21ce2455fbb1ae47dd01ed53cd2e41
 2019-07-24 18:05:02 +02:00
Oliver Smith 0436d95f2e regen_doc: check OSMO_INTERACT_VTY, fix default 
Change default from osmo-interact-vty.py to osmo_interact_vty.py, which
is the name of the script in osmo-python-tests.git.

Check if that script is in PATH before building and running the docker
container.

Change-Id: I763c7379b710160e0155f1fde091137754141335
 2019-06-27 09:57:01 +02:00
Daniel Willmann 63023eb7e6 regen_doc.sh: Add optional parameter to customize docker execution 
The osmo-nitb-master image can run not only osmo-nitb, but also
osmo-bsc_nat. In that case we can't use the default command from
Dockerfile, but should provide our own. This argument makes it possible
to do so.

Change-Id: I52c3cb2cdcfb143e71ac2c1aa40bb466e41a0f5c
Related: OS#1700
 2019-06-19 14:04:46 +02:00
Daniel Willmann 3b96cf3bb4 Add script to regenerate VTY and counter documentation 
This script needs access to the VTY interface, so I changed some
remaining config files to bind the VTY interface to 0.0.0.0.

There are a couple of services that do that already.

Related: OS#1700
Change-Id: Ic5cf7f59de0c18d4c5568b89433c2b11db2a72a5
 2019-06-18 18:18:08 +00:00