Revision as of 13:00, 13 July 2016

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 functional tests - dev plan

For the purpose of tracking CSIT dev work, CSIT functional test cases are grouped into the following VPP functional areas:

1. IPv4 data plane
2. IPv4 control plane
3. IPv4 encapsulations
4. IPv6 data plane
5. IPv6 control plane
6. IPv6 encapsulations
7. Ethernet L2 data plane
8. Ethernet L2 control plane
9. Ethernet L2 encapsulations
10. Ethernet L2 management plane
11. MPLS data plane
12. NSH data plane
13. OPNFV-FDS integration

Following sections provide a top-level breakdown of CSIT dev work items covering functional test cases per area, and their proposed priorities. Items completed to date are prefixed with [DONE]; remaining items are prefixed with their respective priority per target release as described earlier. Indicative VPP functionality coverage is listed at the beginning of each section.

Identified VPP working code availability dependencies are marked by VPP Jira ticket [TODO VPP-xxx].

IPv4 data plane

Indicative coverage = 30%

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

IPv4 control plane

Indicative coverage = 50%

1. [1609-P0] Proxy ARP.
2. [1609-P0] IKEv2.
3. [1609-P1] DHCPv4 proxy.
4. [1606-DONE] ARP.
5. [1606-DONE] ICMPv4.
6. [1606-DONE] DHCPv4 client.

IPv4 encapsulations

Indicative coverage = 50%

1. [1609-P0] ip4-ipsec-ip4 - baseline.
2. [1606-DONE] ip4-gre-ip4 - baseline.

IPv6 data plane

Indicative coverage = 67%

1. [1609-P0] VPN routed forwarding (VRF) - baseline.
2. [1609-P0] extranet VPN routed forwarding (VRF) - baseline.
3. [1609-P0] security - source IPv6 Reverse Path Forwarding (RPF).
4. [1609-P0] qos - ingress policing - 1r2c-(cb,ca), 2r3c-(cb,ca) policers, RFC2475, RFC2697, RFC2698.
5. [1609-P1] routing multipath (ECMP, UECMP) - baseline.
6. [1609-P2] [TODO VPP-xxx] security - stateful firewall.
7. [1606-DONE] routing [rfc2460] - baseline.
8. [1606-DONE] security - iacl with n-tuple classification.
9. [1606-DONE] security - cop white-/black-list ip4 src addr filtering.

IPv6 control plane

Indicative coverage = 40%

1. [1609-P0] router advertisement.
2. [1609-P1] DHCPv6 proxy.
3. [1609-P2] [TODO VPP-xxx] ip6-ioam, in-band OAM.
4. [1606-DONE] neighbor discovery, RFC4861.
5. [1606-DONE] ICMPv6.

IPv6 encapsulations

Indicative coverage = 0%

1. [1609-P0] ip4-o-ip6 softwire.
2. [1609-P0] ip6-ipsec-ip6.
3. [1609-P1] [TODO VPP-xxx] ip6-segment-routing.

Ethernet L2 data plane

Indicative coverage = 60%

1. [1609-P0] Bridge domain - with VLAN tag acrobatics 1-to-1, 1-to-2, 2-to-1, 2-to-2.
2. [1609-P1] Integrated Routing-Bridging (IRB) - baseline.
3. [1606-DONE] L2 Cross-connec - baseline.
4. [1606-DONE] L2 Cross-connect - with VLAN tag acrobatics 1-to-1, 1-to-2, 2-to-1, 2-to-2.
5. [1606-DONE] Bridge domain - baseline.

Ethernet L2 control plane

Indicative coverage =

1. [1609-P2] [TODO VPP-xxx] CDP/LLDP.
2. [1606-DONE] MAC learning.
3. [1606-DONE] MAC split-horizon.

Ethernet L2 encapsulations

Indicative coverage = 33%

1. [1609-P2] l2-eth-l2tpv3-ip4.
2. [1609-P2] l2-eth-l2tpv3-ip6.
3. [1609-P2] l2-eth-gre-ip4.
4. [1609-P2] l2-eth-gre-ip6.
5. [1606-DONE] l2-vxlan-ipv4 - with bridge-domain.
6. [1606-DONE] l2-vxlan-ipv4 - with L2 cross-connect.

MPLS data plane

Indicative coverage = 0%

1. [1609-P2] vpnv4-mpls-gre-ip4.
2. [1609-P2] mpls-o-eth.

NSH data plane

Indicative coverage = 0%

1. [1609-P1] ip4-nsh-gre-ip4.
2. [1609-P1] ip4-nsh-vxlan-gpe-ip4.

OPNFV-FDS integration

Indicative coverage = 100%

1. [1606-DONE] FDS VM scenario with two L2 bridge domains – ICMPv4.
2. [1606-DONE] FDS VM scenario with two L2 bridge domains with static L2FIB entries – ICMPv4.
3. [1606-DONE] FDS VM scenario with two L2 bridge domains – ICMPv6.
4. [1606-DONE] FDS VM scenario with two L2 bridge domains with static L2FIB entries – ICMPv6.
5. [1606-DONE] FDS VM scenario with L2 cross-connect – ICMPv4.
6. [1606-DONE] FDS VM scenario with L2 cross-connect – ICMPv6.
7. [1606-DONE] FDS L2 test cases with tenant networks (VXLAN).
8. [1606-DONE] FDS L2 test cases with provider physical networks (VLAN).