mirror of
https://github.com/kernelkit/infix.git
synced 2026-08-04 14:43:01 +02:00
Joachim Wiberg
fc7e1d0745
For a heavily loaded system, 10 seconds/retries is not enough time to expect containers to have started up. Particularly after the changes done recently to do prune before and after a container is started. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
=== Container with VETH pair
==== Description
Verify connectivity with a simple web server container from behind a
regular bridge, a VETH pair connects the container to the bridge.
....
.-------------. .---------------. .--------.
| | mgmt |---------| mgmt | | | web- |
| host | data |---------| data | target | | server |
'-------------' '---------------' '--------'
| /
br0 /
`----- veth0 -----'
....
==== Topology
ifdef::topdoc[]
image::{topdoc}../../test/case/infix_containers/container_veth/topology.svg[Container with VETH pair topology]
endif::topdoc[]
ifndef::topdoc[]
ifdef::testgroup[]
image::container_veth/topology.svg[Container with VETH pair topology]
endif::testgroup[]
ifndef::testgroup[]
image::topology.svg[Container with VETH pair topology]
endif::testgroup[]
endif::topdoc[]
==== Test sequence
. Set up topology and attach to target DUT
. Create 'web-br0-veth' container from bundled OCI image
. Verify container 'web-br0-veth' has started
. Verify basic DUT connectivity, host:data can ping DUT 10.0.0.2
. Verify container 'web-br0-veth' is reachable on http://10.0.0.2:91
<<<