#opnfv-vswitchperf: vswitchperf

Meeting summary

1. Development Updates. (srao, 16:00:30)
   1. Al Morton (acm, 16:00:52)
   2. Sridhar: Thanks for reviews. 1 more review is pending - Timestamping-Logfiles. (srao, 16:02:55)
   3. Opened a Jira for Reinstalling OS on NOde-1 and Node-2 - and prepare the sandbox. (srao, 16:03:37)
   4. The goal is to create/modify jenkins job to run build process on the new-sandbox. (srao, 16:04:28)
   5. I have started work on "live Results" - spirent and t-rex. (srao, 16:05:08)
   6. Live Results: For every sec (configurable duration) obtain (configurable) metrics. (srao, 16:05:43)
   
   
2. ONS-NA 2019 (srao, 16:06:39)
   1. We have planned a demo session under LFN-booth. (srao, 16:06:58)
   2. https://etherpad.opnfv.org/p/Booth_Demo_Proposals_for_ONS_NA_2019 (srao, 16:07:12)
   3. Call for participation: Anybody else planning to attend and participate please let me know. (srao, 16:07:58)
   4. Skydive can be used to display topology and corresponding metrics (srao, 16:14:06)
   5. Felician: Grafana has a dashboard for topology display, we should consider it. (srao, 16:16:29)
   6. Barometr project has used Grafana (acm, 16:16:31)
   
   
3. Tipsy Update (srao, 16:16:58)
   1. Tipsey - also tests control plane, dynamic control workload effects on dataplane (stress) (acm, 16:18:42)
   2. Output Metrics - Performance Metrics (throughput, latency) (srao, 16:20:31)
   3. always look at smallest packet size, and plot in Mpps (not Mbps) and Latency (acm, 16:20:48)
   4. Dimensions include number of available CPUs, others... (acm, 16:22:09)
   5. Input Metrics - Available number of CPUs, Pipeline Size - spatial and temporal, active-flow count. (srao, 16:22:33)
   6. have pipeline of number of flows in the tables of the switch, another dimension of characterization (acm, 16:23:22)
   7. deployment model fo Tipsey: SW installed on both DUT and SW generator - assumes SW switch is already running! (acm, 16:25:03)
   8. #info have some custom SW to setup the vswitch, etc. and Tipsey on the DUT runs the OpenFlow COntroller (acm, 16:26:37)
   9. Deployment: Tipsy on DUT: Runs on the OFC, , Tipsy on Tester: Orchestrates the measurements, generate traffic needs to be sent. (srao, 16:26:40)
   10. can test HW switch, control with OpenFlow (acm, 16:27:28)
   11. so, the summary is that Tipsey operates the traffic generator (--tgen mode on VSPERF) (acm, 16:29:00)
   12. VSPERF is welcome to re-use Tipsey Piplines, like Mobile Gateway with a SW switch (acm, 16:29:56)
   13. if measuring a SW switch, can use the Openflow Tipey application to configure the switch. (acm, 16:30:34)
   14. OF Controller usually runs on DUT/SUT, but uses TCP connections and can be located anywhere. (acm, 16:31:32)
   15. Connect with felician for reuse of the source. (srao, 16:31:34)
   16. Felician is available for questions when considering integration of Tipsey- xxx (acm, 16:32:13)
   
   
4. Plugfest results update. (srao, 16:33:59)
   1. Sorry : 1,$ s/Tipsey/Tipsy/g (acm, 16:34:19)
   2. for P2P X-NUMA case, Scenario 2 is not realistic, but kept for consistency with PVP (acm, 16:36:02)
   3. Scenario 3 was worse than 2 -- this was a surprise because the PHD is split across nodes. (acm, 16:37:15)
   4. Finding that it's OK to have PMD on diff node than vSwitch (acm, 16:38:23)
   5. Set the trial-duration reasonably - considering transient impairments (srao, 16:47:50)
   6. link for Long-duration Testing: https://wiki.opnfv.org/display/vsperf/Long+Duration+Testing (srao, 16:49:22)
   7. PROX can help in identifying interrupt processing - and in turn detect process that can be the reason for affecting the performance (srao, 16:50:54)
   8. Waiting for input from Xavier for sec-by-sec prox output to file. (srao, 16:53:35)
   9. Should we put the V-1 of vsperf containers in main VSPERF distribution under docker folder...? (srao, 16:55:37)
   10. Submit a patch - following the review, we can decide. (srao, 16:58:31)

Action items

1. (none)

People present (lines said)

1. srao (26)
2. acm (18)
3. collabot` (3)