Page tree
Skip to end of metadata
Go to start of metadata

vSwitch Performance Characterization for Telco NFV Use Cases - 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

Story Points

XS

1

S

2

M

3

L

5

XL

8

TENT

13

RELEASE D

 

Feature

Status

Description

Priority

JIRA

Effort

Impact

RFC 5481 evaluation in any/all Traffic Generators & Measurement Systems

In Progress

Determine the capabilities of all of the traffic generator/measurement systems integrated with VSPERF - goal is to measure packet delay variation on (a subset of) flows at RFC 2544 Throughput level.

 

VSPERF-384

M

 
yardstick D Integration Requires the Yardstick plug-in feature, planned for D release (question), and cross-project coordination.** XL (question) 
40Gb + 100Gb NIC support      

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

*

VSPERF-97

XL

 

QoS tests

 

Port TOIT QoS tests to VSPERF

*

 

L

 

VM 2 VM tests

 

Enable VM-vswitch-VM - vhost user
Nailed down methodology 

*

VSPERF-89

XL

 

Any outstanding RFC2544 tests implementation

 

Packetloss profile test implementation

*

 

L

 

Exploration of a reference pipeline configuration for release C /supporting openstack/more realistic pipelines

Will be done through yardstick

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

 

 

TENT

 

Support TCP traffic in traffic gens

 

Add TCP support to IxNET TCL script. (UDP is hardcoded)

 

 

M

 

TCL script cleanup

 

Remove TCL lines that can be generated by IxNet generate (highLevelStream 1500+ lines) items (Ongoing)

 

 

XL

 

Migrate to IXIA python APIs instead of TCL scripts

 

 

 

 

XL

 

Detailed benchmark reporting and graphing.

 

Is done through the OPNFV Results Dashboard

 

 

XL

 

RFC2889 tests implementation

 

 

 

 

L

 

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.

 

 

M

 

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)

 

 

XL

 

Allow for configurable 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

 

 

L

 

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.

 

 

L

 

Decouple the controller from OVS

 

Migrate OpenFlow dependency out of the controllers and down to the vswitches themselves to decouple the controller from OVS

 

VSPERF-113

XL

 

L2, L3, L4 flows

 

Extend test definitions and implementation to do L2, L3, and L4 level flow matching

 

 

TENT

 

Common params for traffic gens

 

leverage the terminology used in RFC 1242 and RFC 2285 to rename the parameters (both input and output) from traffic gens

 

 

M

 

Report iteration results as well as aggregate results

 

 

 

 

S

 

Single port traffic gen Source and Sink

 

Single port traffic gen support (today we just use 2 ports)

 

 

L

 

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)

 

 

L

 

Fix UDP/TCP port error (Port 63 is hardcoded)

 

 

 

 

S

 

Linux bridge as a switch

 

 

 

 

M

 

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

 

VSPERF-84

L

 

RFC 2544 Scalability tech debt - pre install flows on the vswitch

 

 

 

VSPERF-83

M

 

Vanilla OVS PVP/PVVP - differences in RX values for bidirectional flows

 

 

 

VSPERF-117

L

 

Add Spirent traffic gen virtual equipment to POD3

 

 

 

VSPERF-143

 

 

Add Spirent support for throughput mod vlan family of tests

 

 

 

VSPERF-145

 

 

Add Spirent support for continuous traffic tests

 

 

 

VSPERF-146

 

 

Add Spirent support for b2b family of tests

 

 

 

VSPERF-144

 

 

Modify Spirent RFC2544 throughput test to use Spirent's REST API

 

 

 

VSPERF-148

 

 

Add Spirent support for scalability family of tests

 

 

 

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.

 

 

M

 

Module tests prepare moduletest environment and start to write MTs to get good coverage (e.g. 60% in D and 95% in E); MTs to be run by OPNFV Jenkins jobs  XL 
VSPERF Container?      
Add support for flow based traffic. Traffic patterns that better model real world HTTP traffic. Each flow consists of a number of (small) number of packets. Many flows. VSPERF-403M 
Add support for hardware accelerated OVS NICs. There are an increasing number of smart NICs now, that support offload of OVS processing onto the NIC hardware. Enhance the framework to support configuration and testing of such NICs as the DUT. VSPERF-404M 
Add Namespace/RSTP Testcase to Integration We added some functionality for STP protocol testing, but no test case was added. Need to add a test case to show the functionality of these new features.* M 
Moongen Bonding test Add a new topology that would use dpdk bonding with Moongen. The topology would include two switches, one guest, and 20 flow rules to better mimic a realistic openstack scenario.* L 
Add more reporting features Reporting should include more details such as lossrate used, PMD statistics, and more host info such as cpu pinnings.* M 

RELEASE C

Priority 1

Feature

Status

Description

Priority

JIRA

Effort

Impact

Moongen Integration

Done

Integrate Moongen with VSPERF

High

 

L

High

Traffic Gen control Utility

Done

Create a python utility that's capable of directly controlling the traffic generators supported by vsperf.

High

 

L

High

Yardstick integration

Done

Minimal integration complete

High

VSPERF-79

L

High

vSwitch None Option

Done

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

Done

Enable Bypass/SR-IOV setup support with vsperf for the no vswitch use case.

Med

 

XL

Med

VXLAN, GRE, NVGRE /overlay integration tests.

Done

Port TOIT VXLAN tests to VSPERF

High

 

L

Med

Port all old toit integration tests to VSPERF

Done

 

High

 

XL

Med

report frameloss % from IXIA

Done

 

High

 

S

High

Priority 2

Feature

Status

Description

Priority

JIRA

Effort

Impact

Xena Networks traffic generator integration with VSPERF

Done

Integrate Xena with VSPERF

Med

 

L

High

Test Prioritization

Done

Establish a Wiki/JIRA story where we prioritize the tests to define and implement.

High

 

S

High

Support vfio instead of igb_uio

Done

migrate DPDK setup to use vfio or enable vfio as an option

High

 

S

High

  • No labels