- Configuration of a testbed topology is defined in one file:
testbed.csv - One script to operate all testbeds:
testbed-cli.sh - Flexible topologies which allow to use VM_SET and PTF container as one entity
- All VM management ip information in one place:
veosinventory file - PTF container is generalized and used in every topology
- Automatic provisioning of fanout switch configuration (should be refactored)
- Please follow the Example section if you want to set up any testbed and topology.
- One entry in
testbed.csvconsist of:- physical topology: How ports of VMs and PTF connected to DUT
- configuration templates for VMs
- Topologies are defined in vars/topo_*.yml files
- Current topologies are:
- t1: 32 VMs + PTF container for injected ports
- t1-lag: 24 VMs + PTF container for injected ports. 8 VMs has two ports each in LAG
- ptf32: classic PTF container with 32 ports connected directly to DUT ports
- ptf64: as ptf32, but with 64 ports
- t0: 4 VMs + ptf. PTF container has 4 injected ports + 28 directly connected ports
- Requires 72 VMs
- All DUT ports are connected to VMs
- PTF container has injected ports only
- Requires 32 VMs
- All DUT ports are connected to VMs
- PTF container has injected ports only
- Requires 24 VMs
- All DUT ports are connected to VMs
- PTF container has injected ports only
- Requires 0 VMs
- All DUT ports are directly connected to PTF container
- PTF container has no injected ports
- Requires 0 VMs
- All DUT ports are directly connected to PTF container
- PTF container has no injected ports
- Requires 4 VMs
- 4 DUT ports are connected to VMs
- PTF container has 4 injected ports and 28 directly connected ports
- Requires 8 VMs
- 16 DUT ports are connected to VMs
- PTF container has 16 injected ports and 64 directly connected ports