|
|
| Line 1: |
Line 1: |
| | + | '''WORK IN PROGRESS - PLEASE TREAT IT AS SUCH''' |
| | + | |
| | __TOC__ | | __TOC__ |
| − | ==CSIT Jenkins Jobs for Functional Tests==
| |
| | | | |
| − | Three Jenkins jobs involving CSIT functional test cases:
| + | =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 [https://jira.fd.io/secure/RapidBoard.jspa?rapidView=1&projectKey=CSIT 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: |
| | + | |
| | + | # IPv4 data plane |
| | + | # IPv4 control plane |
| | + | # IPv4 encapsulations |
| | + | # IPv4 telemetry |
| | + | # IPv6 data plane |
| | + | # IPv6 control plane |
| | + | # IPv6 encapsulations |
| | + | # IPv6 telemetry |
| | + | # Ethernet L2 data plane |
| | + | # Ethernet L2 control plane |
| | + | # Ethernet L2 encapsulations |
| | + | # Ethernet L2 management plane |
| | + | # Ethernet L2 telemetry |
| | + | # MPLS data plane |
| | + | # NSH data plane |
| | + | # 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== |
| | + | |
| | + | '''INSERT LINK''' to JIRA filter showing the live status for below functional test cases. |
| | + | |
| | + | Indicative coverage = 30% |
| | + | |
| | + | # [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. |
| | + | |
| | + | ==IPv4 control plane== |
| | + | |
| | + | Indicative coverage = 50% |
| | + | |
| | + | # [1609-P0] Proxy ARP. |
| | + | # [1609-P0] IKEv2. |
| | + | # [1609-P1] DHCPv4 proxy. |
| | + | # [1606-DONE] ARP. |
| | + | # [1606-DONE] ICMPv4. |
| | + | # [1606-DONE] DHCPv4 client. |
| | + | |
| | + | ==IPv4 encapsulations== |
| | + | |
| | + | Indicative coverage = 10% |
| | + | |
| | + | # [1609-P0] ip4-ipsec-ip4 - baseline main fib. |
| | + | # [1609-P0] ip4-lispgpe-ip4 - main fib, vrf (gpe_vni-to-vrf), phy2lisp, virt2lisp. |
| | + | # [1609-P0] ip4-lispgpe-ip4 - main fib, vrf (gpe_vni-to-vrf), lisp2lisp. |
| | + | # [1609-P0] ip4-ipsec-lispgpe-ip4 - main fib, vrf (gpe_vni-to-vrf), phy2lisp, virt2lisp. |
| | + | # [1609-P0] ip4-ipsec-lispgpe-ip4 - main fib, vrf (gpe_vni-to-vrf), lisp2lisp. |
| | + | # [1606-DONE] ip4-gre-ip4 - baseline main fib. |
| | + | |
| | + | ==IPv4 telemetry== |
| | + | |
| | + | Indicative coverage = 0% |
| | + | |
| | + | # [1609-P0] IPv4 IPFIX - stats collection and export - baseline. |
| | + | # [1609-P0] IPv4 IPFIX - stats collection and export - functional scale. |
| | + | # [1609-P0] Switched port analyzer mirroring SPAN - (flow,port) mirroring to local port - baseline. |
| | + | # [1609-P1] Lawful intercept - (flow,port) mirroring to remote locatio via LI UDP tunnel - baseline. |
| | + | |
| | + | ==IPv6 data plane== |
| | + | |
| | + | Indicative coverage = 67% |
| | + | |
| | + | # [1609-P0] VPN routed forwarding (VRF) - baseline. |
| | + | # [1609-P0] extranet VPN routed forwarding (VRF) - baseline. |
| | + | # [1609-P0] [TODO VPP-194] security - source IPv6 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-P2] [TODO VPP-xxx] security - stateful firewall. |
| | + | # [1606-DONE] routing [rfc2460] - baseline. |
| | + | # [1606-DONE] security - iacl with n-tuple classification. |
| | + | # [1606-DONE] security - cop white-/black-list ip4 src addr filtering. |
| | + | |
| | + | ==IPv6 control plane== |
| | + | |
| | + | Indicative coverage = 40% |
| | + | |
| | + | # [1609-P0] router advertisement. |
| | + | # [1609-P0] DHCPv6 client. |
| | + | # [1609-P1] DHCPv6 proxy. |
| | + | # [1609-P2] [TODO VPP-xxx] ip6-ioam, in-band OAM. |
| | + | # [1606-DONE] neighbor discovery, RFC4861. |
| | + | # [1606-DONE] ICMPv6. |
| | | | |
| − | # task: verify vpp code changes as they come - functional tests
| + | ==IPv6 encapsulations== |
| − | #* job: [https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-virl/ vpp-csit-verify-virl]
| + | |
| − | #* triggers: gerrit change commit, "recheck" patch comment
| + | |
| − | #* vpp code: vpp master branch PLUS gerrit change under test
| + | |
| − | #* csit code: csit-verified-tag
| + | |
| − | #* testbed: LF VIRL compute nodes
| + | |
| − | #* status: WORKING
| + | |
| − | # task: identify vpp-master-verified vpp build for csit-* jobs and provide trending reports – semiweekly
| + | |
| − | #* job: csit-vpp-master-verify-semiweekly
| + | |
| − | #* triggers: periodic semiweekly
| + | |
| − | #* vpp code: latest build from nexus repository (deposited by vpp-merge-master job)
| + | |
| − | #** https://nexus.fd.io/content/repositories/fd.io.dev/io/fd/vpp/vpp/*
| + | |
| − | #** on success: update vpp-master-verified vpp build reference in csit bootstrap scripts
| + | |
| − | #* csit code: csit-verified-tag
| + | |
| − | #* testbed: LF VIRL for functional and HW compute nodes for performance
| + | |
| − | #* status: OPEN / PARTIAL
| + | |
| − | #** [https://jenkins.fd.io/view/csit/job/csit-vpp-master-verify-weekly/ csit-vpp-master-verify-weekly]
| + | |
| − | # task: verify csit code changes as they come - functional tests
| + | |
| − | #* job: [https://jenkins.fd.io/view/csit/job/csit-vpp-functional-virl/ csit-vpp-functional-virl]
| + | |
| − | #* triggers: gerrit change commit, "recheck" patch comment
| + | |
| − | #* vpp code: vpp-master-verified vpp build
| + | |
| − | #* csit code: csit master branch PLUS gerrit change
| + | |
| − | #* testbed: LF VIRL compute nodes
| + | |
| − | #* status: WORKING
| + | |
| − | # task: verify csit code against vpp-master-verified vpp build – weekly
| + | |
| − | #* job: csit-vpp-verify-weekly
| + | |
| − | #* triggers: periodic weekly
| + | |
| − | #* vpp code: vpp-master-verified vpp build
| + | |
| − | #* csit code: csit master branch
| + | |
| − | #** on success: update csit-verified-tag
| + | |
| − | #* testbed: LF HW compute nodes
| + | |
| − | #* status: OPEN
| + | |
| | | | |
| − | ==Functional Test Cases - Working== | + | Indicative coverage = 0% |
| | | | |
| − | # Working functional test cases - 74 working in FD.io today. | + | # [1609-P0] ip4-o-ip6 softwire. |
| − | # List of working functional test cases:
| + | # [1609-P0] ip6-ipsec-ip6. |
| − | ## csit$ grep "^| [a-zA-Z]" -nr tests | grep -v Documentation | grep -vi " | " | grep -v performance
| + | # [1609-P0] ip6-lispgpe-ip6 - main fib, vrf (gpe_vni-to-vrf), phy2lisp, virt2lisp. |
| − | ## tests/suites/bridge_domain/bridge_domain_untagged.robot:41:| VPP reports interfaces
| + | # [1609-P0] ip6-lispgpe-ip6 - main fib, vrf (gpe_vni-to-vrf), lisp2lisp. |
| − | ## tests/suites/bridge_domain/bridge_domain_untagged.robot:46:| Vpp forwards packets via L2 bridge domain 2 ports | + | # [1609-P1] ip4-lispgpe-ip6 - main fib, vrf (gpe_vni-to-vrf), phy2lisp, virt2lisp. |
| − | ## tests/suites/bridge_domain/bridge_domain_untagged.robot:62:| Vpp forwards packets via L2 bridge domain in circular topology
| + | # [1609-P1] ip4-lispgpe-ip6 - main fib, vrf (gpe_vni-to-vrf), lisp2lisp. |
| − | ## tests/suites/bridge_domain/bridge_domain_untagged.robot:83:| Vpp forwards packets via L2 bridge domain in circular topology with static L2FIB entries
| + | # [1609-P0] ip6-ipsec-lispgpe-ip6 - main fib, vrf (gpe_vni-to-vrf), phy2lisp, virt2lisp. |
| − | ## tests/suites/bridge_domain/bridge_domain_untagged.robot:127:| Vpp forwards packets via L2 bridge domain with split-horizon groups set in circular topology
| + | # [1609-P0] ip6-ipsec-lispgpe-ip6 - main fib, vrf (gpe_vni-to-vrf), lisp2lisp. |
| − | ## tests/suites/bridge_domain/bridge_domain_untagged.robot:172:| VPP forwards ICMPv4 packets through VM via two L2 bridge domains
| + | # [1609-P1] ip4-ipsec-lispgpe-ip6 - main fib, vrf (gpe_vni-to-vrf), phy2lisp, virt2lisp. |
| − | ## tests/suites/bridge_domain/bridge_domain_untagged.robot:200:| VPP forwards ICMPv6 packets through VM via two L2 bridge domains
| + | # [1609-P1] ip4-ipsec-lispgpe-ip6 - main fib, vrf (gpe_vni-to-vrf), lisp2lisp. |
| − | ## tests/suites/bridge_domain/bridge_domain_untagged.robot:228:| VPP forwards ICMPv4 packets through VM via two L2 bridge domains with static L2FIB entries
| + | # [1609-P1] [TODO VPP-xxx] ip6-segment-routing. |
| − | ## tests/suites/bridge_domain/bridge_domain_untagged.robot:279:| VPP forwards ICMPv6 packets through VM via two L2 bridge domains with static L2FIB entries
| + | |
| − | ## tests/suites/cop/cop_whitelist_blacklist.robot:59:| VPP permits packets based on IPv4 src addr
| + | |
| − | ## tests/suites/cop/cop_whitelist_blacklist.robot:87:| VPP drops packets based on IPv4 src addr
| + | |
| − | ## tests/suites/cop/cop_whitelist_blacklist_IPv6.robot:63:| VPP permits packets based on IPv6 src addr
| + | |
| − | ## tests/suites/cop/cop_whitelist_blacklist_IPv6.robot:96:| VPP drops packets based on IPv6 src addr
| + | |
| − | ## tests/suites/gre/gre_encapsulation.robot:48:| VPP can route IPv4 traffic from GRE tunnel
| + | |
| − | ## tests/suites/gre/gre_encapsulation.robot:81:| VPP can encapsulate IPv4 traffic in GRE
| + | |
| − | ## tests/suites/gre/gre_encapsulation.robot:107:| VPP can decapsulate IPv4 traffic in GRE
| + | |
| − | ## tests/suites/honeycomb/1 - interface_management.robot:40:| Honeycomb configures and reads interface state
| + | |
| − | ## tests/suites/honeycomb/1 - interface_management.robot:54:| Honeycomb modifies interface configuration - ipv4
| + | |
| − | ## tests/suites/honeycomb/1 - interface_management.robot:73:| Honeycomb modifies interface configuration - ipv6 | + | |
| − | ## tests/suites/honeycomb/1 - interface_management.robot:85:| Honeycomb modifies interface configuration - ethernet,routing
| + | |
| − | ## tests/suites/honeycomb/2 - vxlan.robot:38:| Honeycomb configures VxLAN tunnel
| + | |
| − | ## tests/suites/honeycomb/2 - vxlan.robot:51:| Honeycomb disables VxLAN tunnel
| + | |
| − | ## tests/suites/honeycomb/2 - vxlan.robot:63:| Honeycomb does not set VxLAN configuration on another interface type | + | |
| − | ## tests/suites/honeycomb/2 - vxlan.robot:77:| Honeycomb does not set invalid VxLAN configuration
| + | |
| − | ## tests/suites/honeycomb/2 - vxlan.robot:89:| Honeycomb configures VxLAN tunnel with ipv6
| + | |
| − | ## tests/suites/honeycomb/3 - bridge_domain.robot:35:| Honeycomb sets up l2 bridge domain
| + | |
| − | ## tests/suites/honeycomb/3 - bridge_domain.robot:45:| Honeycomb assigns interfaces to bridge domain
| + | |
| − | ## tests/suites/honeycomb/3 - bridge_domain.robot:58:| Honeycomb manages multiple bridge domains on node
| + | |
| − | ## tests/suites/honeycomb/3 - bridge_domain.robot:75:| Honeycomb removes bridge domains | + | |
| − | ## tests/suites/honeycomb/4 - tap.robot:34:| Honeycomb configures TAP interface
| + | |
| − | ## tests/suites/honeycomb/4 - tap.robot:48:| Honeycomb modifies existing TAP interface configuration
| + | |
| − | ## tests/suites/honeycomb/4 - tap.robot:63:| Honeycomb removes TAP interface
| + | |
| − | ## tests/suites/honeycomb/5 - interface_vhost_user.robot:35:| Honycomb creates vhost-user interface - server | + | |
| − | ## tests/suites/honeycomb/5 - interface_vhost_user.robot:49:| Honycomb modifies vhost-user interface - server
| + | |
| − | ## tests/suites/honeycomb/5 - interface_vhost_user.robot:75:| Honycomb deletes vhost-user interface - server | + | |
| − | ## tests/suites/honeycomb/5 - interface_vhost_user.robot:89:| Honycomb creates vhost-user interface - client
| + | |
| − | ## tests/suites/honeycomb/5 - interface_vhost_user.robot:103:| Honycomb modifies vhost-user interface - client
| + | |
| − | ## tests/suites/honeycomb/5 - interface_vhost_user.robot:129:| Honycomb deletes vhost-user interface - client | + | |
| − | ## tests/suites/honeycomb/5 - interface_vhost_user.robot:143:| Honeycomb does not set vhost-user configuration on another interface type
| + | |
| − | ## tests/suites/honeycomb/5 - interface_vhost_user.robot:155:| Honeycomb does not set invalid vhost-user configuration
| + | |
| − | ## tests/suites/ipv4/ipv4_iacl_untagged.robot:40:| VPP drops packets based on IPv4 source addresses
| + | |
| − | ## tests/suites/ipv4/ipv4_iacl_untagged.robot:72:| VPP drops packets based on IPv4 destination addresses | + | |
| − | ## tests/suites/ipv4/ipv4_iacl_untagged.robot:104:| VPP drops packets based on IPv4 src-addr and dst-addr
| + | |
| − | ## tests/suites/ipv4/ipv4_untagged.robot:30:| VPP replies to ICMPv4 echo request
| + | |
| − | ## tests/suites/ipv4/ipv4_untagged.robot:39:| TG can route to DUT egress interface
| + | |
| − | ## tests/suites/ipv4/ipv4_untagged.robot:48:| TG can route to DUT2 through DUT1
| + | |
| − | ## tests/suites/ipv4/ipv4_untagged.robot:57:| TG can route to DUT2 egress interface through DUT1
| + | |
| − | ## tests/suites/ipv4/ipv4_untagged.robot:66:| TG can route to TG through DUT1 and DUT2
| + | |
| − | ## tests/suites/ipv4/ipv4_untagged.robot:87:| VPP can process ICMP echo request from min to 1500B packet size with 1B increment
| + | |
| − | ## tests/suites/ipv4/ipv4_untagged.robot:91:| VPP can process ICMP echo request from 1500B to max packet size with 10B increment
| + | |
| − | ## tests/suites/ipv4/ipv4_untagged.robot:109:| VPP responds to ARP request
| + | |
| − | ## tests/suites/ipv6/ipv6_iacl_untagged.robot:42:| VPP drops packets based on IPv6 source addresses
| + | |
| − | ## tests/suites/ipv6/ipv6_iacl_untagged.robot:74:| VPP drops packets based on IPv6 destination addresses
| + | |
| − | ## tests/suites/ipv6/ipv6_iacl_untagged.robot:106:| VPP drops packets based on IPv6 src-addr and dst-addr
| + | |
| − | ## tests/suites/ipv6/ipv6_untagged.robot:33:| VPP replies to ICMPv6 echo request
| + | |
| − | ## tests/suites/ipv6/ipv6_untagged.robot:37:| VPP can process ICMPv6 echo request from min to 1500B packet size with 1B increment
| + | |
| − | ## tests/suites/ipv6/ipv6_untagged.robot:41:| VPP can process ICMPv6 echo request from 1500B to max packet size with 10B increment | + | |
| − | ## tests/suites/ipv6/ipv6_untagged.robot:59:| TG can route to first DUT egress interface
| + | |
| − | ## tests/suites/ipv6/ipv6_untagged.robot:64:| TG can route to second DUT through first DUT
| + | |
| − | ## tests/suites/ipv6/ipv6_untagged.robot:69:| TG can route to second DUT egress interface through first DUT
| + | |
| − | ## tests/suites/ipv6/ipv6_untagged.robot:74:| TG can route to TG through first and second DUT
| + | |
| − | ## tests/suites/ipv6/ipv6_untagged.robot:79:| VPP replies to IPv6 Neighbor Solicitation
| + | |
| − | ## tests/suites/l2_xconnect/l2_xconnect_untagged.robot:33:| Vpp forwards ICMPv4 packets via L2 xconnect in circular topology
| + | |
| − | ## tests/suites/l2_xconnect/l2_xconnect_untagged.robot:47:| Vpp forwards ICMPv6 packets via L2 xconnect in circular topology
| + | |
| − | ## tests/suites/l2_xconnect/l2_xconnect_untagged.robot:61:| VPP forwards ICMPv4 packets through VM via L2 x-connect
| + | |
| − | ## tests/suites/l2_xconnect/l2_xconnect_untagged.robot:80:| VPP forwards ICMPv6 packets through VM via L2 x-connect
| + | |
| − | ## tests/suites/lisp/lisp_untagged.robot:35:| VPP can add and delete locator_set
| + | |
| − | ## tests/suites/lisp/lisp_untagged.robot:49:| VPP can add, reset and delete locator_set
| + | |
| − | ## tests/suites/lisp/lisp_untagged.robot:64:| Vpp can add and delete eid address
| + | |
| − | ## tests/suites/lisp/lisp_untagged.robot:78:| Vpp can add and delete lisp map resolver address
| + | |
| − | ## tests/suites/tagging/qinq_l2_xconnect.robot:33:| VPP can push and pop two VLAN tags to traffic transferring through xconnect
| + | |
| − | ## tests/suites/vxlan/vxlan_bd_dot1q.robot:32:| VPP can encapsulate L2 in VXLAN over IPv4 over Dot1Q
| + | |
| − | ## tests/suites/vxlan/vxlan_bd_untagged.robot:31:| VPP can pass IPv4 bidirectionally through VXLAN | + | |
| − | ## tests/suites/vxlan/vxlan_xconnect_untagged.robot:30:| VPP can pass IPv4 bidirectionally through VXLAN
| + | |
| | | | |
| − | ==Functional Test Cases - Plan and Status== | + | ==IPv6 telemetry== |
| | | | |
| − | Below laundry list of functions that could/should be tested - need to prioritize based on FD.io community needs and feedback, and scheduled for CSIT development. To work and be useful, CSIT development should be done in coordination with VPP Release Candidate content and release schedule.
| + | Indicative coverage = 0% |
| | | | |
| − | Each test case and CSIT development work items prefixed with status and/or proposed priority relative to FD.io VPP release:
| + | # [1609-P0] IPv6 IPFIX - stats collection and export - baseline. |
| − | * [Pn-Rm] – Proposed coverage of VPP functionality by FD.io CSIT functional and performance test cases.
| + | # [1609-P0] IPv6 IPFIX - stats collection and export - functional scale. |
| − | ** '''P'''n – CSIT development and integration '''priority'''; n=0,1,2, 0-for-MUST, 1-for-SHOULD, 2-for-COULD.
| + | # [1609-P0] Switched port analyzer mirroring SPAN - (flow,port) mirroring to local port - baseline. |
| − | ** '''R'''m – VPP major '''release''', R1 stands for the first FD.io VPP release, R2 for the 2nd FD.io VPP release.
| + | # [1609-P1] Lawful intercept - (flow,port) mirroring to remote locatio via LI UDP tunnel - baseline. |
| | | | |
| − | Plan execution tracked on [https://jira.fd.io/secure/RapidBoard.jspa?rapidView=1&projectKey=CSIT CSIT jira]
| + | ==Ethernet L2 data plane== |
| | | | |
| − | '''VPP network functions:'''
| + | Indicative coverage = 60% |
| | | | |
| − | # IP4 data plane
| + | # [1609-P0] Bridge domain - with VLAN tag acrobatics 1-to-1, 1-to-2, 2-to-1, 2-to-2. |
| − | ## [DONE-R1] baseline routing [rfc791]
| + | # [1609-P1] Integrated Routing-Bridging (IRB) - baseline. |
| − | ##* [DONE-R1] TG packets routed to DUT ingress interface
| + | # [1606-DONE] L2 Cross-connec - baseline. |
| − | ##* [DONE-R1] TG packets routed to DUT egress interface
| + | # [1606-DONE] L2 Cross-connect - with VLAN tag acrobatics 1-to-1, 1-to-2, 2-to-1, 2-to-2. |
| − | ##* [DONE-R1] TG packets routed to DUT2 through DUT1
| + | # [1606-DONE] Bridge domain - baseline. |
| − | ##* [DONE-R1] TG packets routed to DUT2 egress interface through DUT1
| + | |
| − | ##* [DONE-R1] TG packets routed to TG through DUT1 and DUT2
| + | |
| − | ## [P2-R1] vpn baseline routed forwarding (VRF)
| + | |
| − | ##* [P2-R1] TG packets routed to DUT ingress interface, VPP configured with two VRFs
| + | |
| − | ##* [P2-R1] TG packets routed to DUT egress interface, VPP configured with two VRFs
| + | |
| − | ##* [P2-R1] TG packets routed to DUT2 through DUT1, VPP configured with two VRFs
| + | |
| − | ##* [P2-R1] TG packets routed to DUT2 egress interface through DUT1, VPP configured with two VRFs
| + | |
| − | ##* [P2-R1] TG packets routed to TG through DUT1 and DUT2, VPP configured with two VRFs
| + | |
| − | ## [P1-R2] vpn extranet baseline routed forwarding (VRF)
| + | |
| − | ##* [P1-R2] TG packets routed to DUT ingress interface, VPP configured with two extranet VRFs
| + | |
| − | ##* [P1-R2] TG packets routed to DUT egress interface, VPP configured with two extranet VRFs
| + | |
| − | ##* [P1-R2] TG packets routed to DUT2 through DUT1, VPP configured with two extranet VRFs
| + | |
| − | ##* [P1-R2] TG packets routed to DUT2 egress interface through DUT1, VPP configured with two extranet VRFs
| + | |
| − | ##* [P1-R2] TG packets routed to TG through DUT1 and DUT2, VPP configured with two extranet VRFs
| + | |
| − | ## [P2-R1] routing multipath
| + | |
| − | ##* [P2-R1] equal cost multi-path (ECMP)
| + | |
| − | ##* [P2-R1] unequal cost multi-path (UECMP)
| + | |
| − | ## [P0-R1] security - iacl with n-tuple classification
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 source addresses (src-addr); JIRA: [https://jira.fd.io/browse/CSIT-15 CSIT-15]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 destination addresses (dst-addr); JIRA: [https://jira.fd.io/browse/CSIT-15 CSIT-15]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 src-addr and dst-addr; JIRA: [https://jira.fd.io/browse/CSIT-15 CSIT-15]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 protocol (TCP/UDP); JIRA: [https://jira.fd.io/browse/CSIT-92 CSIT-92]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 TCP src ports; JIRA: [https://jira.fd.io/browse/CSIT-92 CSIT-92]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 TCP dst ports; JIRA: [https://jira.fd.io/browse/CSIT-92 CSIT-92]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 TCP src+dst ports; JIRA: [https://jira.fd.io/browse/CSIT-92 CSIT-92]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 UDP src ports; JIRA: [https://jira.fd.io/browse/CSIT-92 CSIT-92]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 UDP dst ports; JIRA: [https://jira.fd.io/browse/CSIT-92 CSIT-92]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 UDP src+dst ports; JIRA: [https://jira.fd.io/browse/CSIT-92 CSIT-92]
| + | |
| − | ##* [P2-R1] VPP drops packets based on MAC src addr
| + | |
| − | ## [P0-R1] security - cop white-/black-lists
| + | |
| − | ##* [DONE-R1] VPP permits packets based on IPv4 src addr; JIRA: [https://jira.fd.io/browse/CSIT-9 CSIT-9]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv4 src addr; JIRA: [https://jira.fd.io/browse/CSIT-9 CSIT-9]
| + | |
| − | ## [P2-R1] security - source IPv4 Reverse Path Forwarding (RPF)
| + | |
| − | ##* [P2-R1] VPP source RPF check on IPv4 src-addr
| + | |
| − | ## [P1-R1] qos - ingress policing - 1r2c-(cb,ca), 2r3c-(cb,ca) policers (cb=color-blind, ca=color-aware)
| + | |
| − | ##* [P1-R1] VPP 1r2c-cb policing packets based on DiffServ marking - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 1r2c-ca policing packets based on DiffServ marking - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P1-R1] VPP 2r3c-cb policing packets based on DiffServ marking - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 2r3c-ca policing packets based on DiffServ marking - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 1r2c-cb policing packets based on packet classify - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 1r2c-ca policing packets based on packet classify - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 2r3c-cb policing packets based on packet classify - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 2r3c-ca policing packets based on packet classify - [TBD-VPP] depends on VPP code ready
| + | |
| − | ## [TBD] qos - egress policing - 1r2c-(cb,ca), 2r3c-(cb,ca) policers
| + | |
| − | ## [P1-R2] carrier grade nat 44, CGN44 [rfc6598], [rfc6888]
| + | |
| − | ##* [P1-R2] CGN address-only
| + | |
| − | ##* [P1-R2] CGN address-and-port
| + | |
| − | ##* [TBD] CGN address-only and application layer gateway (ALG)
| + | |
| − | ##* [TBD] CGN address-and-port and ALG
| + | |
| − | # IP4 control plane
| + | |
| − | ## [P1-R1] ARP
| + | |
| − | ##* [DONE-R1] VPP responds to ARP request [rfc826]
| + | |
| − | ##* [DONE-R1] VPP sends ARP requests for unknown destinations; JIRA: [https://jira.fd.io/browse/CSIT-23 CSIT-23]
| + | |
| − | ## [P1-R1] Proxy ARP
| + | |
| − | ##* [P1-R1] VPP responds to ARP requests on behalf of host present on another VPP interface.
| + | |
| − | ## [DONE-R1] ICMPv4
| + | |
| − | ##* [DONE-R1] VPP can process ICMP echo request from min to 1500B packet size with 1B increment
| + | |
| − | ##* [DONE-R1] VPP can process ICMP echo request from 1500B to max packet size with 10B increment
| + | |
| − | ##* [DONE-R1] VPP replies to ICMPv4 echo request [rfc792]
| + | |
| − | ## [P2-R1] DHCPv4 proxy
| + | |
| − | ##* [P2-R1] VPP proxies valid DHCPv4 request to DHCPv4 server
| + | |
| − | ##* [P2-R1] VPP proxy ignores invalid DHCPv4 request
| + | |
| − | ## [DONE-R1] DHCPv4 client; JIRA: [https://jira.fd.io/browse/CSIT-26 CSIT-26]
| + | |
| − | ##* [DONE-R1] VPP sends DHCPv4 Discover; JIRA: [https://jira.fd.io/browse/CSIT-100 CSIT-100]
| + | |
| − | ##* [DONE-R1] VPP sends DHCPv4 Request after Offer; JIRA: [https://jira.fd.io/browse/CSIT-101 CSIT-101]
| + | |
| − | ##* [DONE-R1] VPP honors DHCPv4 lease time; JIRA: [https://jira.fd.io/browse/CSIT-130 CSIT-130]
| + | |
| − | ##* [DONE-R1] VPP releases allocated address; JIRA: [https://jira.fd.io/browse/CSIT-26 CSIT-26]
| + | |
| − | ##* [DONE-R1] VPP retries DHCPv4 Discover ???times until ???total second timeout; JIRA: [https://jira.fd.io/browse/CSIT-26 CSIT-26]
| + | |
| − | ##* [DONE-R1] VPP retries DHCPv4 Request ???times until ???total second timeout; JIRA: [https://jira.fd.io/browse/CSIT-26 CSIT-26]
| + | |
| − | ## [P1-R2] IKEv2
| + | |
| − | ##* [P1-R2] psk auth
| + | |
| − | ##* [P1-R2] rsa key auth
| + | |
| − | ##* [P1-R2] ID type IPv4 address
| + | |
| − | ##* [P1-R2] ID type (email) [rfc822]
| + | |
| − | ##* [P1-R2] ID type key-id
| + | |
| − | ##* [P1-R2] test various supported encryption/prf/integrity algs, DH groups, extended sequence number
| + | |
| − | # IP4 encapsulations
| + | |
| − | ## [P1-R1] ip4-gre-ip4
| + | |
| − | ##* [P1-R1] VPP can encapsulate IPv4 traffic in GRE; JIRA: [https://jira.fd.io/browse/CSIT-18 CSIT-18]
| + | |
| − | ##* [P1-R1] VPP can route IPv4 traffic from GRE tunnel; JIRA: [https://jira.fd.io/browse/CSIT-18 CSIT-18]
| + | |
| − | ## [P1-R2] ip4-ipsec-ip4
| + | |
| − | ##* [P1-R2] basic connectivity test - create ipsec SA and policy on VPP, test different encryption and integrity algorithms; JIRA: [https://jira.fd.io/browse/CSIT-28 CSIT-28]
| + | |
| − | ##* [P1-R2] add/del SA and policy tests; JIRA: [https://jira.fd.io/browse/CSIT-28 CSIT-28]
| + | |
| − | ##* [P1-R2] encryprion/integrity key update test; JIRA: [https://jira.fd.io/browse/CSIT-28 CSIT-28]
| + | |
| − | ##* [P1-R2] some negative tests (each side has different enryption/integrity alg); JIRA: [https://jira.fd.io/browse/CSIT-28 CSIT-28]
| + | |
| − | # ip6 data plane
| + | |
| − | ## [DONE-R1] baseline routing [rfc2460]
| + | |
| − | ##* [DONE-R1] TG can route to first DUT egress interface
| + | |
| − | ##* [DONE-R1] TG can route to second DUT through first DUT
| + | |
| − | ##* [DONE-R1] TG can route to second DUT egress interface through first DUT
| + | |
| − | ##* [DONE-R1] TG can route to TG through first and second DUT
| + | |
| − | ## [P2-R1] vpn baseline routed forwarding (VRF)
| + | |
| − | ##* [P2-R1] TG can ping to DUT ingress interface, VPP configured with two VRFs
| + | |
| − | ##* [P2-R1] TG can ping to DUT egress interface, VPP configured with two VRFs
| + | |
| − | ##* [P2-R1] TG can ping to DUT2 through DUT1, VPP configured with two VRFs
| + | |
| − | ##* [P2-R1] TG can ping to DUT2 egress interface through DUT1, VPP configured with two VRFs
| + | |
| − | ##* [P2-R1] TG can ping to TG through DUT1 and DUT2, VPP configured with two VRFs
| + | |
| − | ## [P0-R1] security - iacl with n-tuple classification
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 src-addr; JIRA: [https://jira.fd.io/browse/CSIT-16 CSIT-16]
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 dst-addr; JIRA: [https://jira.fd.io/browse/CSIT-16 CSIT-16]
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 src-addr and dst-addr; JIRA: [https://jira.fd.io/browse/CSIT-16 CSIT-16]
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 protocol (TCP/UDP); JIRA: [https://jira.fd.io/browse/CSIT-107 CSIT-107]
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 TCP src port; JIRA: [https://jira.fd.io/browse/CSIT-107 CSIT-107]
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 TCP dst port; JIRA: [https://jira.fd.io/browse/CSIT-107 CSIT-107]
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 TCP src+dst port; JIRA: [https://jira.fd.io/browse/CSIT-107 CSIT-107]
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 UDP src port; JIRA: [https://jira.fd.io/browse/CSIT-107 CSIT-107]
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 UDP dst port; JIRA: [https://jira.fd.io/browse/CSIT-107 CSIT-107]
| + | |
| − | ##* [DONE-R1] VPP can drop packets based on IPv6 UDP src+dst port; JIRA: [https://jira.fd.io/browse/CSIT-107 CSIT-107]
| + | |
| − | ##* [P2-R1] VPP can drop packets based on src MAC + IPv6 UDP src+dst port
| + | |
| − | ## [P0-R1] security - cop white-/black-lists
| + | |
| − | ##* [DONE-R1] VPP permits packets based on IPv6 src-addr; JIRA: [https://jira.fd.io/browse/CSIT-17 CSIT-17]
| + | |
| − | ##* [DONE-R1] VPP drops packets based on IPv6 src-addr; JIRA: [https://jira.fd.io/browse/CSIT-17 CSIT-17]
| + | |
| − | ## [P2-R1] security - source IPv6 Reverse Path Forwarding (RPF)
| + | |
| − | ##* [P2-R1] - source RPF check on IPv6 src-addr
| + | |
| − | ## [P1-R1] qos traffic conditioning - ingress rate metering, marking and rate-limiting - 1r2c-(cb,ca), 2r3c-(cb,ca) policers (cb=color-blind, ca=color-aware) [rfc2475], [rfc2697], [rfc2698]
| + | |
| − | ##* [P1-R1] VPP 1r2c-cb policing packets based on DiffServ marking - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 1r2c-ca policing packets based on DiffServ marking - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P1-R1] VPP 2r3c-cb policing packets based on DiffServ marking - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 2r3c-ca policing packets based on DiffServ marking - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 1r2c-cb policing packets based on packet classify - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 1r2c-ca policing packets based on packet classify - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 2r3c-cb policing packets based on packet classify - [TBD-VPP] depends on VPP code ready
| + | |
| − | ##* [P2-R1] VPP 2r3c-ca policing packets based on packet classify - [TBD-VPP] depends on VPP code ready
| + | |
| − | # ip6 control plane
| + | |
| − | ## [P0-R1] router advertisement
| + | |
| − | ##* [P0-R1] VPP transmits RA from IPv6 enabled interface
| + | |
| − | ##* [P0-R1] ??? ^ retransmits ???
| + | |
| − | ##* [P0-R1] VPP ??? handles RA ???
| + | |
| − | ## [DONE-R1] neighbor discovery [rfc4861]
| + | |
| − | ##* [DONE-R1] VPP validates and replies to IPv6 NS/NA messages
| + | |
| − | ## [DONE-R1] ICMPv6
| + | |
| − | ##* [DONE-R1] VPP replies to ICMPv6 echo request
| + | |
| − | ##* [DONE-R1] VPP can process ICMPv6 echo request from min to 1500B packet size with 1B increment
| + | |
| − | ##* [DONE-R1] VPP can process ICMPv6 echo request from 1500B to max packet size with 10B increment
| + | |
| − | ## [TBD] ip6-ioam (in-band OAM)
| + | |
| − | ## [P1-R2] DHCPv6 proxy
| + | |
| − | ##* [P1-R2] VPP proxies valid DHCPv6 request to DHCPv6 server
| + | |
| − | ##* [P1-R2] VPP proxy ignores invalid DHCPv6 request
| + | |
| − | # ip6 encapsulations
| + | |
| − | ## [P1-R1] ip4-o-ip6 softwire
| + | |
| − | ##* [P1-R1] lightweight46 [rfc7596]
| + | |
| − | ##* [P2-R1] map-e [rfc7597]
| + | |
| − | ##* [P2-R1] map-t [rfc7599]
| + | |
| − | ## [TBD] ip6-segment-routing
| + | |
| − | ## [P1-R2] ip6-ipsec-ip6
| + | |
| − | ##* [P1-R2] basic connectivity test - create ipsec SA and policy on VPP, test different encryption and integrity algorithms
| + | |
| − | ##* [P1-R2] add/del SA and policy tests
| + | |
| − | ##* [P1-R2] encryprion/integrity key update test
| + | |
| − | ##* [P1-R2] some negative tests (each side has different enryption/integrity alg)
| + | |
| − | # l2 data plane
| + | |
| − | ## [DONE-R1] L2 xconnect
| + | |
| − | ##* [DONE-R1] VPP forwards packets via L2 xconnect in 3-node topology
| + | |
| − | ##* [P2-R1] VPP forwards packets via L2 xconnect with VLAN tag acrobatics a'la MEF EVC - 1-to-1, dot1q-to-dot1q
| + | |
| − | ##* [P2-R1] VPP forwards packets via L2 xconnect with VLAN tag acrobatics a'la MEF EVC - 1-to-2, dot1q-to-dot1ad
| + | |
| − | ##* [P2-R1] VPP forwards packets via L2 xconnect with VLAN tag acrobatics a'la MEF EVC - 2-to-1, dot1ad-to-dot1q
| + | |
| − | ##* [P2-R1] VPP forwards packets via L2 xconnect with VLAN tag acrobatics a'la MEF EVC - 2-to-2, dot1ad-to-dot1ad7 | + | |
| − | ## [DONE-R1] Bridge domain
| + | |
| − | ##* [DONE-R1] VPP forwards packets via L2 bridge domain 2 ports
| + | |
| − | ##* [DONE-R1] VPP forwards packets via L2 bridge domain in 3-node topology
| + | |
| − | ##* [DONE-R1] VPP forwards packets via L2 bridge domain in 3-node topology with static L2FIB entries | + | |
| − | ##* [P2-R1] VPP forwards packets via L2 bridge domain with VLAN tag acrobatics a'la MEF EVC - 1-to-1, dot1q-to-dot1q
| + | |
| − | ##* [P2-R1] VPP forwards packets via L2 bridge domain with VLAN tag acrobatics a'la MEF EVC - 1-to-2, dot1q-to-dot1ad
| + | |
| − | ##* [P2-R1] VPP forwards packets via L2 bridge domain with VLAN tag acrobatics a'la MEF EVC - 2-to-1, dot1ad-to-dot1q
| + | |
| − | ##* [P2-R1] VPP forwards packets via L2 bridge domain with VLAN tag acrobatics a'la MEF EVC - 2-to-2, dot1ad-to-dot1ad
| + | |
| − | ## [TBD] irb
| + | |
| − | ##* [TBD] TG can route to DUT ingress irb interface
| + | |
| − | ##* [TBD] TG can route to DUT egress irb interface
| + | |
| − | ##* [TBD] TG can route to DUT2 through DUT1, both DUTs using irb interfaces
| + | |
| − | ##* [TBD] TG can route to DUT2 egress irb interface through DUT1
| + | |
| − | ##* [TBD] TG can route to TG through DUT1 and DUT2, both DUTs using irb interfaces
| + | |
| − | # l2 control plane
| + | |
| − | ## [DONE-R1] MAC learning
| + | |
| − | ## [DONE-R1] MAC split-horizon; JIRA: [https://jira.fd.io/browse/CSIT-19 CSIT-19]
| + | |
| − | ## [TBD] cdp/lldp
| + | |
| − | # l2 encapsulations
| + | |
| − | ## [DONE-R1] l2-vxlan-ipv4
| + | |
| − | ##* [DONE-R1] VPP can encapsulate L2 in VXLAN over V4 using bridge-domain
| + | |
| − | ##* [DONE-R1] VPP can pass IPv4 bidirectionally through VXLAN tunnel using l2-xconnect
| + | |
| − | ## [TBD] l2-eth-l2tpv3-ip4
| + | |
| − | ## [TBD] l2-eth-l2tpv3-ip6
| + | |
| − | ## [TBD] l2-eth-gre-ip4
| + | |
| − | ## [TBD] l2-eth-gre-ip6
| + | |
| − | # l2 management plane
| + | |
| − | ## [DONE-R1] VPP reports interfaces
| + | |
| − | # mpls
| + | |
| − | ## [TBD] vpnv4-mpls-gre-ip4
| + | |
| − | ## [TBD] mpls-o-eth
| + | |
| − | # nsh
| + | |
| − | ## [TBD] ip4-nsh-gre-ip4
| + | |
| − | ## [TBD] ip4-nsh-vxlan-gpe-ip4
| + | |
| − | # VPP tests for FDS
| + | |
| − | ## [DONE-R1] VPP forwards packets through VM via two L2 bridge domains – ICMPv4; JIRA: [https://jira.fd.io/browse/CSIT-61 CSIT-61]
| + | |
| − | ## [DONE-R1] VPP forwards packets through VM via two L2 bridge domains with static L2FIB entries – ICMPv4; JIRA: [https://jira.fd.io/browse/CSIT-61 CSIT-61]
| + | |
| − | ## [DONE-R1] VPP forwards packets through VM via two L2 bridge domains – ICMPv6; JIRA: [https://jira.fd.io/browse/CSIT-61 CSIT-61]
| + | |
| − | ## [DONE-R1] VPP forwards packets through VM via two L2 bridge domains with static L2FIB entries – ICMPv6; JIRA: [https://jira.fd.io/browse/CSIT-61 CSIT-61]
| + | |
| − | ## [DONE-R1] VPP forwards packets through VM via x-connect – ICMPv4; JIRA: [https://jira.fd.io/browse/CSIT-61 CSIT-61]
| + | |
| − | ## [DONE-R1] VPP forwards packets through VM via x-connect – ICMPv6; JIRA: [https://jira.fd.io/browse/CSIT-61 CSIT-61]
| + | |
| − | ## [DONE-R1] L2 test cases with tenant networks (VXLAN); JIRA: [https://jira.fd.io/browse/CSIT-64 CSIT-64]
| + | |
| − | ## [DONE-R1] Provider network test cases with provider physical networks (VLAN); JIRA: [https://jira.fd.io/browse/CSIT-64 CSIT-64]
| + | |
| | | | |
| | + | ==Ethernet L2 control plane== |
| | | | |
| − | '''VPP deployment topologies:'''
| + | Indicative coverage = |
| | | | |
| − | # [DONE-R1] Phy1-VPP-Phy2, VPP in host user-mode | + | # [1609-P2] [TODO VPP-xxx] CDP/LLDP. |
| − | # [P0-R1] Phy1-VPP-VM-VPP-Phy2, VPP in host user-mode; JIRA: [https://jira.fd.io/browse/CSIT-20 CSIT-20]
| + | # [1606-DONE] MAC learning. |
| − | # [TBD] Phy1-pcipt-VPPVM-pcipt-Phy2, VPP in guest user-mode | + | # [1606-DONE] MAC split-horizon. |
| − | # [TBD] VPP in container
| + | |
| − | # [TBD] VPP as vSwitch for containers | + | |
| | | | |
| − | '''VPP negative testing:'''
| + | ==Ethernet L2 encapsulations== |
| | | | |
| − | # [TBD] physical interfaces down/up
| + | Indicative coverage = 33% |
| − | # [TBD] virtual interfaces down/up
| + | |
| − | # [TBD] VPP crash recovery
| + | |
| | | | |
| − | '''Other tests:'''
| + | # [1609-P0] l2-eth-lispgpe-ip6 - L2BD, L2XC. |
| | + | # [1609-P0] l2-eth-lispgpe-ip4 - L2BD, L2XC. |
| | + | # [1609-P0] l2eth-gre-ip4-ipsec-ip4-eth - L2BD, L2XC. |
| | + | # [1609-P2] l2-eth-l2tpv3-ip4 - L2BD, L2XC. |
| | + | # [1609-P2] l2-eth-l2tpv3-ip6 - L2BD, L2XC. |
| | + | # [1609-P2] l2-eth-gre-ip4 - L2BD, L2XC. |
| | + | # [1609-P2] l2-eth-gre-ip6 - L2BD, L2XC. |
| | + | # [1606-DONE] l2-vxlan-ipv4 - with bridge-domain. |
| | + | # [1606-DONE] l2-vxlan-ipv4 - with L2 cross-connect. |
| | | | |
| − | # [TBD] Memory utilization tests
| + | ==L2 telemetry== |
| − | # [TBD] Memory leak tests
| + | |
| − | # [TBD] Consistency of memory footprint for selected configs
| + | |
| | | | |
| − | '''Honeycomb'''
| + | Indicative coverage = 0% |
| − | # Interfaces - Basic interface management
| + | |
| − | #* [DONE] Honeycomb (modifies) CONFIGURES and READS interface state; JIRA: [https://jira.fd.io/browse/CSIT-40 CSIT-40]
| + | |
| − | #* [DONE] Honeycomb modifies interface configuration - IPv4; JIRA: [https://jira.fd.io/browse/CSIT-37 CSIT-37]
| + | |
| − | #* [DONE] Honeycomb modifies interface configuration - IPv6; JIRA: [https://jira.fd.io/browse/CSIT-38 CSIT-38]
| + | |
| − | #* [DONE] Honeycomb modifies interface configuration - ethernet, routing; JIRA: [https://jira.fd.io/browse/CSIT-39 CSIT-39]
| + | |
| − | # Bridge domain
| + | |
| − | #* [DONE-R1] Honeycomb creates l2 bridge domain; JIRA: [https://jira.fd.io/browse/CSIT-41 CSIT-41]
| + | |
| − | #* [DONE-R1] Honeycomb manages multiple bridge domains on node; JIRA: [https://jira.fd.io/browse/CSIT-42 CSIT-42]
| + | |
| − | #* [DONE-R1] Honeycomb removes bridge domain; JIRA: [https://jira.fd.io/browse/CSIT-43 CSIT-43]
| + | |
| − | #* [DONE-R1] Honeycomb bridge domain configuration; JIRA: [https://jira.fd.io/browse/CSIT-44 CSIT-44]
| + | |
| − | # VXLAN
| + | |
| − | #* [DONE-R1] Honeycomb configures VXLAN; JIRA: [https://jira.fd.io/browse/CSIT-45 CSIT-45]
| + | |
| − | #* [DONE-R1] Vxlan gpe support; JIRA: [https://jira.fd.io/browse/CSIT-131 CSIT-131]
| + | |
| − | # Tap interface configuration
| + | |
| − | #* [DONE-R1] Tap configuration; JIRA: [https://jira.fd.io/browse/CSIT-75 CSIT-75]
| + | |
| − | # Honeycomb items for GBP (FDS)
| + | |
| − | #* [DONE-R1] Honeycomb provides vhostuser support; JIRA: [https://jira.fd.io/browse/CSIT-76 CSIT-76]
| + | |
| − | #* [DONE-R1] Honeycomb checks VXLAN Tunneling; JIRA: [https://jira.fd.io/browse/CSIT-47 CSIT-47]
| + | |
| − | #* [DONE-R1] Provider networks (VLAN); JIRA: [https://jira.fd.io/browse/CSIT-48 CSIT-48]
| + | |
| − | #* [DONE-R1] Sub-interface configuration; JIRA: [https://jira.fd.io/browse/CSIT-94 CSIT-94]
| + | |
| − | #* [DONE-R1] Persistence; JIRA: [https://jira.fd.io/browse/CSIT-121 CSIT-121]
| + | |
| − | #* [TBD] Policy - security groups
| + | |
| − | #* [TBD] Policy - security group rules
| + | |
| − | # Honeycomb Keywords
| + | |
| − | #* [DONE-R1] VxLAN Configuration; JIRA: [https://jira.fd.io/browse/CSIT-51 CSIT-51]
| + | |
| − | #* [DONE-R1] TAP Configuration; JIRA: [https://jira.fd.io/browse/CSIT-69 CSIT-69]
| + | |
| − | #* [DONE-R1] Vhost-user Configuration; JIRA: [https://jira.fd.io/browse/CSIT-70 CSIT-70]
| + | |
| − | #* [DONE-R1] Honeycomb provides vhostuser support; JIRA: [https://jira.fd.io/browse/CSIT-46 CSIT-46]
| + | |
| | | | |
| | + | # [1609-P1] L2 FIB - stats collection and export - baseline. |
| | + | # [1609-P2] L2 FIB - stats collection and export - functional scale. |
| | + | # [1609-P0] Switched port analyzer mirroring SPAN - (flow,port) mirroring to local port - baseline. |
| | + | # [1609-P1] Lawful intercept - (flow,port) mirroring to remote locatio via LI UDP tunnel - baseline. |
| | | | |
| | + | ==MPLS data plane== |
| | | | |
| − | '''Non-coding work items'''
| + | Indicative coverage = 0% |
| − | # design docs
| + | |
| − | # usability docs
| + | |
| | | | |
| − | ==Functional tests infra work areas==
| + | # [1609-P2] vpnv4-mpls-gre-ip4. |
| | + | # [1609-P2] mpls-o-eth. |
| | | | |
| − | CSIT Golden Branch
| + | ==NSH data plane== |
| − | * Name of the CSIT branch is "csit-verified".
| + | |
| − | * It is created by CSIT team in CSIT gerrit project.
| + | |
| − | * It represents the version of CSIT code that is tested and verified to work perfectly.
| + | |
| − | * At the moment, csit-verified is a git branch, stored in gerrit.fd.io, that points to concrete version of master branch of CSIT project.
| + | |
| − | * Link to branch: https://gerrit.fd.io/r/gitweb?p=csit.git;a=shortlog;h=refs%2Fheads%2Fcsit-verified
| + | |
| − | * In future, we plan to switch from using branch to tag, because is suites gerrit better than branching (since we use the branch only to point to a version in master).
| + | |
| | | | |
| − | Run testcases based on vpp code change (no clear ideas yet)
| + | Indicative coverage = 0% |
| − | * for now execute all baseline tests - l2, ip4, ip6
| + | |
| − | * future per code change functional and vpp node graph dependencies
| + | |
| | | | |
| − | Gathering of stats/logs/core dumps from DUTs/TGs after test execution:
| + | # [1609-P1] ip4-nsh-gre-ip4. |
| − | * naming schemes, storage, packaging
| + | # [1609-P1] ip4-nsh-vxlan-gpe-ip4. |
| − | * collection of TELEMETRY
| + | |
| − | * plain text - structured
| + | |
| − | ** one-time snapshot of the system
| + | |
| − | ** for human driven hand-crafted debugging
| + | |
| − | ** for human driven part-automated debugging
| + | |
| − | ** for machine driven fully-automated analysis
| + | |
| − | * use Network Data Analytics engine in the future
| + | |
| | | | |
| − | Honeycomb tests framework
| + | ==OPNFV-FDS integration== |
| − | * NETCONF FrameWork
| + | |
| − | ** library that understands netconf and ssh
| + | |
| − | * Existing CSIT RF (Robot-Framework) and Python libraries / tools extension to use HC/VAT/CLI "driver" to execute things
| + | |
| − | ** the same logical code - execute across different driver APIs
| + | |
| − | *** HC, VAT, CLI
| + | |
| | | | |
| − | VPP project
| + | Indicative coverage = 100% |
| − | * plannig and coordinating with code development
| + | |
| − | * specifying and identifying dependencies to/from
| + | |
| − | ** deployment use cases
| + | |
| − | ** CSIT
| + | |
| | | | |
| − | Honeycomb project
| + | # [1606-DONE] FDS VM scenario with two L2 bridge domains – ICMPv4. |
| − | * plannig and coordinating with code development
| + | # [1606-DONE] FDS VM scenario with two L2 bridge domains with static L2FIB entries – ICMPv4. |
| − | * specifying and identifying dependencies to/from
| + | # [1606-DONE] FDS VM scenario with two L2 bridge domains – ICMPv6. |
| − | ** deployment use cases
| + | # [1606-DONE] FDS VM scenario with two L2 bridge domains with static L2FIB entries – ICMPv6. |
| − | ** CSIT
| + | # [1606-DONE] FDS VM scenario with L2 cross-connect – ICMPv4. |
| | + | # [1606-DONE] FDS VM scenario with L2 cross-connect – ICMPv6. |
| | + | # [1606-DONE] FDS L2 test cases with tenant networks (VXLAN). |
| | + | # [1606-DONE] FDS L2 test cases with provider physical networks (VLAN). |
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:
For the purpose of tracking CSIT dev work, CSIT functional test cases are grouped into the following VPP functional areas:
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].
