#opnfv-vswitchperf: vswitchperf

Meeting summary

1. Jerma Release Planning Actions. (SRao, 15:03:45)
   1. Release planning Wiki Page is Ready. Set of Issues related to Jerma is Created under VSPERF. RelReq 6 and 9 are also created. (SRao, 15:09:25)
   2. Unable to link the issues created under VSPERF (for jerma) to The RelReq-6 and RelReq-9. (SRao, 15:09:59)
   3. ACTION: Send an email to David - explaining the completed activities, and asking for ToDoS. (SRao, 15:20:01)
   
   
2. Openstack-VSPERF (SRao, 15:23:09)
   1. Current Status: We can deploy Traffic Generators in different topologies. WIP: VSPERF Config File Creations. Issue: Instance Public-Network reachability. (SRao, 15:24:14)
   
   
3. vSwitch in Containers - PB. (SRao, 15:25:41)
   1. We don't have any performance numbers on running vSwitch in a container. (SRao, 15:26:03)
   2. In CNTT with Airship Deployments, on all compute Nodes, with vswitch is running in a container. (SRao, 15:26:27)
   3. Do we need to do any performance testing for this usecase? Bob: Consider NUMA assignment, PMD Assignments (SRao, 15:34:38)
   4. Normal-Mode: Isolate CPUs used for VSWITCH (2), PMDs (3-6), VNFs. We should be able to replicate the same behavior. (SRao, 15:36:04)
   5. Can we run container and force with CPU allocation to it? Possibly YES. (SRao, 15:36:36)
   6. - How it affects the automation - Setting up OVS with all physical and virtual ports, running VNF, configuring VNF and running the test. (SRao, 15:38:06)
   
   
4. CNB-K8S (SRao, 15:44:47)
   1. Relook - B2B Results. Update OVS Throughput with New Results. (SRao, 16:04:15)

Action items

1. Send an email to David - explaining the completed activities, and asking for ToDoS.

People present (lines said)

1. SRao (17)
2. collab-meetbot (3)