User Tools

Site Tools


wiki:vswitch_work_items

vSwitch Performance Characterization for Telco NFV Use Cases - Candidate work items

Candidate work items

This section lists features which "vswitchperf" will develop. It is expected that the output here will fold into higher level OPNFV test projects (e.g. for system level functionality testing, specific VNF use-case tests, performance tests etc.) - which are in the process of being defined.

Effort

Relative size Days
XS 1
S 2
M 3
L 5
XL 8
TENT 13

Priority 1

Feature Description Priority JIRA Effort Impact
Moongen Integration Integrate Moongen with VSPERF High L High
Traffic Gen control Utility Create a python utility that's capable of directly controlling the traffic generators supported by vsperf. High L High
Implement the IMIX genome as a traffic gen API function and allow it to be configurable from the cli IMIX specification as an option to the traffic generator using RFC 6985 High VSPERF-97 XL Med
Yardstick integration Not scoped need to colaborate with Yardstick but need some basics completed first High VSPERF-79 L High
vSwitch None Option Implement a vswitch None option that allows you to setup the use case you want to test without a vswitch. Med M Low
Bypass/SR-IOV setup support Enable Bypass/SR-IOV setup support with vsperf for the no vswitch use case. Med XL Med
VXLAN/overlay tests. Port TOIT VXLAN tests to VSPERF High L Med
QoS tests Port TOIT QoS tests to VSPERF High L Med
VM 2 VM tests Enable VM-vswitch-VM - vhost user High VSPERF-89 XL High
Port all old toit integration tests to VSPERF High XL Med
Any outstanding RFC2544 tests implementation Packetloss profile test implementation High L Med
report frameloss % from IXIA High S High
Exploration of a reference pipeline configuration for release C /supporting openstack/more realistic pipelines we need to extend our support from the baseline deployment benchmarks to include more complex but realistic deployment scenarios for the vSwitch. In other words we need to be able to support integration with openstack. The activities that will be key to supporting this is: 1. Enabling end used to use our automated traffic generation scripts (either through the implementation of a separate control utility for the traffic gens or through supporting a NONE option for vSwitches and VNFs). 2. Integration with Yardstick. 3. Exploration of a suitable reference pipeline configuration (service chaining as a possible example). 4.Supporting a SW traffic generator High TENT High

Priority 2

Feature Description Priority JIRA Effort Impact
Support TCP traffic in traffic gens Add TCP support to IxNET TCL script. (UDP is hardcoded) Med M Low
TCL script cleanup Remove TCL lines that can be generated by IxNet generate (highLevelStream 1500+ lines) items (Ongoing) Med XL Low
Migrate to IXIA python APIs instead of TCL scripts Med XL High
Detailed benchmark reporting and graphing. Med XL High
IXIA RFC 5481 evaluation and study of scripts Study the IXIA scripts provided by IXIA and integrate them with the traffic gen utility in VSPERF - scripts are written for the IXIA Sw version supported by POD3 and will need to be tested there. Med L High
RFC2889 tests implementation Med L Med
deployment as a test argument remove the deployment from the test name - it's exploding our testcases config file, it should be passed as a parameter/list to the testcase which has an agnostic name and reported as part of the result. Med M Med
Fix OF table structure for PVP and PVVP to match P2P OF table structure used in VSPERF is not followed by PVP and PVVP scenarios (flows are just in first table) Med XL Med
Allow for conrigurable port numbers for frame modification physical port numbers are currently hardcoded in frame modification settings, so it can't be used easily with other deployments than P2P Med L Low
Update implementation for background load generation to run multiple instances of the background load. background load generated by stress(-ng) doesn't work well with isolcpus option; It has to be modified to run x instances of stress and pinpoint them to "free" cpus. Med L Med
Xena Networks traffic generator integration with VSPERF Integrate Xena with VSPERF Med L High
Decouple the controller from OVS Migrate OpenFlow dependency out of the controllers and down to the vswitches themselves to decouple the controller from OVS Med VSPERF-113 XL High
L2, L3, L4 flows Extend test definitions and implementation to do L2, L3, and L4 level flow matching Med TENT High
Test Prioritization Establish a Wiki/JIRA story where we prioritize the tests to define and implement. High S High
Common params for traffig gens leverage the terminology used in RFC 1242 and RFC 2285 to rename the parameters (both input and output) from traffic gens High M High
Support vfio instead of igb_uio migrate DPDK setup to use vfio or enable vfio as an option High S High
Report iteration results as well as aggregate results High S High

Priority 3

Feature Description Priority JIRA Effort Impact
Single port traffic gen Source and Sink Single port traffic gen support (today we just use 2 ports) Low L Low
pcap replay as an option for traffic gens. Implement a function to allow for pcap replay from the traffic gens supported by OPNFV (Priority 1 SW pkt Gens, Priority 2 IXIA & Spirent) Low L Med
Fix UDP/TCP port error (Port 63 is hardcoded) Low S Low
Linux bridge as a switch Low M High
Kevin's recommendations for perf benchmarking TODO get these from Kevin High M Low
Ciara's recommendations for vhost benchmarking TODO get these from Ciara High M Low
Investigate IXIA SDN + NFV testsuite: OpenFlow Switch Forwarding test Investigate the tests provided by the IXIA blackbook on SDN + NFV testing to see if there are test we can leverge Low VSPERF-84 L Med
RFC 2544 Scalability tech debt - pre intstall flows on the vswitch VSPERF-83 M Low
Vanilla OVS PVP/PVVP - differences in RX values for bidirectional flows Med VSPERF-117 L Med
Add Spirent traffic gen virtual equipment to POD3 High VSPERF-143
Add Spirent support for throughput mod vlan family of tests Med VSPERF-145
Add Spirent support for continuous traffic tests Med VSPERF-146
Add Spirent support for b2b family of tests Med VSPERF-144
Modify Spirent RFC2544 throughput test to use Spirent's REST API Med VSPERF-148
Add Spirent support for scalability family of tests Med VSPERF-147
Deployment Naming and extension we need to come up with a better naming scheme for our deployment scenarios, that’s intuitive and extensible, we will work with new committers/contributors on this. Med M High

Activities and Tasks

Task Description Interested Committers/contributors
Test Case Specification Generic specification (not vSwitch specific, or architecture specific). Requires a lot of work and diverse community involvement as Committers. The Test case specification must be absoutely generic - it may not even refer to any specific vSwitch implementation. This is the intent of the project - generic vSwitch characterization. The project will not prevent the creation of additional test configurations for different vSwitches - whether its kernel based data paths, or user space data paths, etc. Intel (Maryam Tahhan), Dell (Wenjing Chu), Thomas Graf (Noiro Networks), Mark Lambe (AeroFlex), Christoph Meyer (Ericsson), Aihua Li (Huawei)
Project Repo Structure Organize and maintain high level directory tree . Aihua Li (Hauwei)
HW Specification Need to describe the initial HW that can be available for use by this project. Linux Foundation virtual infrastructure probably not sufficient, will need to use the facilties of the OPNFV Performance and Test Lab infrastructure. Trevor Cooper (Intel)
Test implementation and integration into framework Implement test cases into test framework Intel (Maryam Tahhan), Gene Schneider (Huawei), Madhu Challa (Noiro Networks), Dell (Name to follow from Wenjing), Wang Xiao, Chen Jinzhou ( Huawei ), Christoph Meyer (Ericsson)
wiki/vswitch_work_items.txt · Last modified: 2016/03/03 16:42 by Maryam Tahhan