Current Status (Iruya)

VSPERF was never designed to be used with Openstack - i.e., use openstack apis to install vsperf, the dut, trafficgen etc. It was designed as a standalone tool.

To use VSPERF, typically, one has to download the source to the DUT system (where vSwitch and VNF are run), and install the software toolchain (vSwitch, Qemu, DPDK, VPP, etc.). One installed, DUT is setup (configuration of the sotware toolchain), traffic-generator is setup, configuration file is created and tests are run.

VSPERF also supports "trafficgen" mode of operation, where none of the DUT setup operations are performed, only tests are run with a particular traffic-generator.

This trafficgen mode is a potential candidate to use with Openstack. However, there are many prerequisites to meet before it can be used with openstack. Some of them are:

1. There is not need to install complete software toolchain
   1. minimal vsperf should be sufficient.
2. The trafficgenerator is setup as VM in openstack
   1. Image creation and upload to glance has to be automated.
3. This Trafficgen deployment as VM(s) can be in multiple ways - Single or multiple instances, On Single or multiple compute hosts, etc
   1. Multiple automated deployment scenarios should be supported
4.  After the traffic-generator is instantiated as VM(s) in openstack, its IP has to be obtained to create the configuration file.
   1. Obatining the IP and creating config file has to be automated

Proposal

Close all the 'gaps' (prerequisites mentioned above) for using VSPERF in trafficgen mode with Openstack.

1. Exclude the necessity to install and run VSPERF on DUT.
2. Enhance Trafficgen mode to include additional information.
3. Build tools to (a) Create Trafficgen (Test-VM) image for openstack, (b) deploy Trafficgen VM in different topologies.
4. Minimal framework for X-Testing Integration with VSPERF-Openstack.

Actions