Current Status (

...

Jerma)

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 Once installed, DUT is setup (configuration of the sotware software toolchain), traffic-generator is setup, configuration file is created and tests are run.

VSPERF also supports "trafficgen-only" mode of operation, where none all of the data path configuration and instantiation in the DUT is performed by Openstack through API-level commands. None of the DUT setup operations are performance, only performed by VSPERF; only the automated VSPERF tests are run with a particular traffic-generator connected to the DUT data path.

This trafficgen-only 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
   1. VSPERF installation should be sufficient.
2. The trafficgenerator traffic generator is setup as VM in openstack - Image creation and upload to glance has to be automated.This setup Openstack
   1. An appropriate VM Image must be created,  (a one time operation), and
   2. Image must be on-boarded to glance  (where is automation needed, in on-boarding? doesn't OS already have this to some degree?).
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
   2. Comment: I see a problem here with multiple traffic-gen VMs on multiple hosts: Synchronized counter measurements (for Loss) clock measurements (for Latency)
   3. Question: Can we use Ironic to do a baremetal Traffic gen installation? this would also help with the accuracy issues identified above.
4.  After the traffic-generator is instantiated as VM(s) in openstackOpenstack, its IP has to be obtained to create the configuration file. - Obatining
   1. Obtaining the IP and creating config file has to be automated
   2. Comment: there may be a way around this with network configuration in OS Neutron? a small /28 network without floating IPs?

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-only 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.

...