...
- in the arguments, --vswitch
- In testcase definition, under 'vSwitch'
- In conf/02_vswitch.conf modify the variable VSWITCH (default)
- Separate configuration file the variable 'VSWITCH'
If, vSwitch is set to 'Nonenone', then ViNePerf will treat it as "pkt-forwarding' case and does not deploy any vSwitch, else it creates vswitch based on 'deployment-scenario'. Here, 'deployment-scenario' mainly control what kind of flow and interface configuration should be done on the managed vSwitch.
As this is an external case, we should set the VSWITCH to None'none', which will make ViNePerf to consider it as a 'Packet-Forwarding' scenario. We do not want to use the packet-forwarding option too - hence, a 'dummyDummy' packet-forwarder (named as DummyFWD) is created. Using vSwitch as None and PKT_FWD as dummy'none' and PKTFWD as DummyFWD, we will ensure the ViNePerf will not bother about vSwitch, and just focuses on Pods and Traffic-management.
For this case, ensure the following configuration:
- --set vswitch is set to None or in Testcase vSwitch is set to None.to none - use any one of the above 4 approaches.
- PKTFWD PKT_FWD is set to Dummy.DummyFWD
- The 'deployment' of testcase starts with pc (For KaLi release - as only North-South is supported for now).
- The EXT_VSWITCH in conf/12_k8s.conf is set to True.
- EXT_VSWITCH_TYPE is set to 'vpp'
...