CSIT/perf1609-draft

DRAFT - WORK IN PROGRESS - PLEASE TREAT IT AS SUCH

CSIT development plan - background

CSIT test development priorities are aligned with VPP releases timeline, with relative dev work prioritization for each VPP release driven by perceived importance of test verification for VPP functionality and performance. Specific CSIT dev work priorities are driven by rough consensus within the project and contributors and committers availability and willingness to do work.

Following priority tagging scheme is used in this CSIT wiki and FD.io jira for CSIT:

• [$VppRlsNo-$RelPrio]
  • VppRlsNo - aligned VPP release number - 16.09, 16.12, 17.03.
  • RelPrio - CSIT release priority - P0 for Must Have, P1 for Should Have, P2 for Could Have
• CSIT dev work tagging examples:
  • [1609-P0] - CSIT Must Have for vpp-v1609
  • [1609-P1] - CSIT Should Have for vpp-v1609
  • [1609-P2] - CSIT Could Have for vpp-v1609

CSIT dev work plan execution tracked on CSIT jira, with priority tags encoded as Jira labels for easy of tracking and reporting.

CSIT performance tests - dev plan

CSIT performance test cases devevelopment work is grouped and tracked across the following VPP functional areas:

1. IPv4 data plane
2. IPv4 control plane
3. IPv4 encapsulations
4. IPv4 telemetry
5. IPv6 data plane
6. IPv6 control plane
7. IPv6 encapsulations
8. IPv6 telemetry
9. Ethernet L2 data plane
10. Ethernet L2 control plane
11. Ethernet L2 encapsulations
12. Ethernet L2 management plane
13. Ethernet L2 telemetry
14. MPLS data plane
15. NSH data plane

CSIT team is tracking completed CSIT dev work per above area (completed == test cases running in FD.io), as well as top-level test coverage metric [%] of VPP functions. VPP code development dependencies are marked with [VPP-DEP].

IPv4 data plane

Indicative coverage =

1. [1609-P0] continue to expand VPP driver coverage - DPDK, other TBD (Netmap?, )
   • (single_physical_interface_type,NIC_type)
   • (all_physical_interface_type,NIC_type)
   • (single_virtual_interface_type,VF_type)
   • (all_virtual_interface_type,VF_type) - box-full tests
2. [1609-P0] QoS policer - rate metering, marking and rate-limiting

Inputs from functional test plan

   # [1609-P0] VPN routed forwarding (VRF) - baseline.
   # [1609-P0] extranet VPN routed forwarding (VRF) - baseline.
   # [1609-P0] security - source IPv4 Reverse Path Forwarding (RPF).
   # [1609-P0] qos - ingress policing - 1r2c-(cb,ca), 2r3c-(cb,ca) policers, RFC2475, RFC2697, RFC2698.
   # [1609-P1] routing multipath (ECMP, UECMP) - baseline.
   # [1609-P1] [TODO VPP-xxx] carrier grade nat 44, CGN44, RFC6598, RFC6888.
   # [1609-P2] [TODO VPP-xxx] security - stateful firewall.
   # [1606-DONE] IPv4 routing RFC791 - baseline.
   # [1606-DONE] security - iacl with n-tuple classification, ip4, ip6, mac.
   # [1606-DONE] security - cop white-/black-list ip4 src addr filtering.

1. IPv4 control plane

Indicative coverage =

1. IPv4 encapsulations

Indicative coverage =