CSIT/csit-perf-tc-naming-change
CSIT Performance TCs Naming
Contents
[hide]- 1 Background
- 2 FD.io Gerrit Patches
- 3 Performance TCs - Naming Scheme
- 4 Performance TCs - New Names
- 5 Performance TCs - Old Names
- 6 Performance TCs - Tagging for Performance Trending Graphs
- 7 Functional TCs - Naming Scheme
- 8 Functional TCs - New Names
- 9 Functional TCs - Old Names
- 10 Miscellaneous Notes
Background
Now that number and type of CSIT test cases (TCs) grew significantly, existing naming notation does not work anymore. Firstly, the existing practice does not follow any strict naming convention. Secondly current TC names do not clearly capture neither encapsulations nor the actual type and content of the tests. Thirdly HW configurations in terms of NICs and ports number and locality are not captured in the name. Bottom line, within the CSIT project we agreed to define a new stricter TC naming convention and update all existing test cases.
This wiki page captures this change.
FD.io Gerrit Patches
- Performance tests
- Functional tests
- <to be added>
Performance TCs - Naming Scheme
Test topologies and functions encoded using tree notation with physical ports and NIC on the left (underlay), followed by outer most frame header, then other stacked headers up to the header processed by vSwitch-VPP, then VPP forwarding function, then encap on vhost interface, number of vhost interfaces, number of VMs. Some examples and legend here:
- 10ge2p1x520-ethip4-ip4base2.robot
- 10ge2p1x520-ethip4-ip4base20k.robot
- 10ge2p1x520-ethip4-ip4base200k.robot
- 10ge2p1x520-ethip4-ip4base2m.robot
- 10ge2p1x710-ethip4-ip4base2.robot
- 10ge2p1vic1227-ethip4-ip4base2.robot
- 40ge2p1xl710-ethip4-ip4base2.robot
- 40ge2p1vic1385-ethip4-ip4base2.robot
- 10ge2p1x520-eth-l2bdbase-eth-2vhost-1vm
- 10ge2p1x520-dot1q-l2bdbase-eth-2vhost-1vm
- 10ge2p1x520-ethip4-ip4base-eth-2vhost-1vm
- 10ge2p1x520-eth-l2xcbase-eth-2vhost-1vm
- 10ge2p1x520-dot1q-l2xcbase-eth-2vhost-1vm
- 10ge2p1x520-ethip4vxlan-l2bdbase-eth-2vhost-1vm
Legend:
- <n>ge - n=10|40|100
- <n>p - number of physical Ethernet ports
- <n><nic_model> - number of NICs and NIC model
- eth|dot1q|dot1ad
- eth - untagged Ethernet on the physical wire
- dot1q - single VLAN tag on physical wire
- dot1ad - double VLAN tag on physical wire
- ip4|ip6
- ip4 - IPv4 header
- ip6 - IPv6 header
- vxlan - VXLAN header
- l2bdbase, l2bdscale - VPP L2 bridge-domain, L2 MAC learning&switching
- base - baseline test with one L2 MAC flow received per interface
- scale - scale tests with many L2 MAC flows received per interface
- distinct L@ MAC flow - distinct (src-mac,dst-mac) tuple in MAC headers
- l2xcbase, l2xcscale - VPP L2 point-to-point crossconnect
- base - baseline test with one L2 MAC flow received per interface
- scale - scale tests with many L2 MAC flows received per interface
- distinct L2 MAC flow - distinct (src-mac,dst-mac) tuple in MAC headers
- ip4base, ip4scale - VPP IPv4 routed forwarding
- base - baseline test with one IPv4 flow received per interface
- scale - scale tests with many IPv4 flows received per interface
- distinct IPv4 flow - distinct (src-ip4,dst-ip4) tuple in IPv4 headers
- Short tests:
- use suffix "-ndrchk"
Performance TCs - New Names
Listing order is the same as for old names, listed in next section:
- 10ge2p1x520-eth-l2bdbasemaclrn-ndrchk.robot
- 10ge2p1x710-eth-l2bdbasemaclrn-ndrdisc.robot
- 40ge2p1xl710-eth-l2bdbasemaclrn-ndrdisc.robot
<list to be completed>
10ge2p1x520-dot1ad-l2xcbase-ndrchk.robot
Performance TCs - Old Names
Listing order is the same as for new names, listed in previous section:
- Bridge_Domain_Intel-X520-DA2.robot
- Bridge_Domain_Intel-X710-DA2.robot
- Bridge_Domain_Intel-XL710.robot
- Long_Bridge_Domain_Vhost_Intel-X520-DA2.robot
- Long_IPv4_Cop_Intel-X520-DA2.robot
- Long_IPv4_Fib_200k_Intel-X520-DA2.robot
- Long_IPv4_Fib_20k_Intel-X520-DA2.robot
- Long_IPv4_Fib_2M_Intel-X520-DA2.robot
- Long_IPv4_Intel-X520-DA2.robot
- Long_IPv4_Intel-XL710.robot
- Long_IPv4_Policer_Intel-X520-DA2.robot
- Long_IPv4_Vhost_Intel-X520-DA2.robot
- Long_IPv4_iAcl_Intel-X520-DA2.robot
- Long_IPv6_Cop_Intel-X520-DA2.robot
- Long_IPv6_Fib_200k_Intel-X520-DA2.robot
- Long_IPv6_Fib_20k_Intel-X520-DA2.robot
- Long_IPv6_Fib_2M_Intel-X520-DA2.robot
- Long_IPv6_Intel-X520-DA2.robot
- Long_IPv6_Intel-XL710.robot
- Long_IPv6_iAcl_Intel-X520-DA2.robot
- Long_Lisp_Intel-X520-DA2.robot
- Long_Xconnect_Dot1ad_Intel-X520-DA2.robot
- Long_Xconnect_Dot1q_Intel-X520-DA2.robot
- Long_Xconnect_Intel-X520-DA2.robot
- Long_Xconnect_Intel-XL710.robot
- Long_Xconnect_Vhost_Intel-X520-DA2.robot
- Long_Xconnect_Vxlan_Ipv4_Intel-X520-DA2.robot
- Short_Bridge_Domain_Intel-X520-DA2.robot
- Short_IPv4_Cop_Intel-X520-DA2.robot
- Short_IPv4_Fib_200k_Intel-X520-DA2.robot
- Short_IPv4_Fib_20k_Intel-X520-DA2.robot
- Short_IPv4_Fib_2M_Intel-X520-DA2.robot
- Short_IPv4_Intel-X520-DA2.robot
- Short_IPv4_Policer_Intel-X520-DA2.robot
- Short_IPv4_iAcl_Intel-X520-DA2.robot
- Short_IPv6_Cop_Intel-X520-DA2.robot
- Short_IPv6_Fib_200k_Intel-X520-DA2.robot
- Short_IPv6_Fib_20k_Intel-X520-DA2.robot
- Short_IPv6_Fib_2M_Intel-X520-DA2.robot
- Short_IPv6_Intel-X520-DA2.robot
- Short_IPv6_iAcl_Intel-X520-DA2.robot
- Short_Lisp_Intel-X520-DA2.robot
- Short_Xconnect_Dot1ad_Intel-X520-DA2.robot
- Short_Xconnect_Dot1q_Intel-X520-DA2.robot
- Short_Xconnect_Intel-X520-DA2.robot
- Short_Xconnect_Vxlan_Ipv4_Intel-X520-DA2.robot
Performance TCs - Tagging for Performance Trending Graphs
In order to group performance TC results into performance trending graphs, CSIT is using RF tags. CSIT RF tags are described in `/docs/tag_documentation.rst'. RF tag changes related to performance TC naming change are captured as part of patch #3856.
Functional TCs - Naming Scheme
<to be added>
Functional TCs - New Names
<to be added>
Functional TCs - Old Names
<to be added>
Miscellaneous Notes
Alternative Perf TC Name Proposal - Deprecated
- short_x520_dot1ad-l2xc.robot
- short_x520_dot1q-l2xc.robot
- short_x520_eth-ip4-base.robot
- short_x520_eth-ip4-cop-whitelist.robot
- short_x520_eth-ip4-fib-200k.robot
- short_x520_eth-ip4-fib-20k.robot
- short_x520_eth-ip4-fib-2M.robot
- short_x520_eth-ip4-iacl-dst.robot
- short_x520_eth-ip4-lisp-ip4.robot
- short_x520_eth-ip4-lisp-ip6.robot
- short_x520_eth-ip4-policer-marker.robot
- short_x520_eth-ip4-vxlan-l2xc.robot
- short_x520_eth-ip6-base.robot
- short_x520_eth-ip6-cop-whitelist.robot
- short_x520_eth-ip6-fib-200k.robot
- short_x520_eth-ip6-fib-20k.robot
- short_x520_eth-ip6-fib-2M.robot
- short_x520_eth-ip6-iacl-dst.robot
- short_x520_eth-ip6-lisp-ip4.robot
- short_x520_eth-ip6-lisp-ip6.robot
- short_x520_eth-l2bd-base.robot
- short_x520_eth-l2xc-base.robot
- x520_dot1ad-l2xc.robot
- x520_dot1q-l2xc.robot
- x520_eth-ip4-base-vhost.robot
- x520_eth-ip4-base.robot
- x520_eth-ip4-cop-whitelist.robot
- x520_eth-ip4-fib-200k.robot
- x520_eth-ip4-fib-20k.robot
- x520_eth-ip4-fib-2M.robot
- x520_eth-ip4-iacl-dst.robot
- x520_eth-ip4-lisp-ip4.robot
- x520_eth-ip4-lisp-ip6.robot
- x520_eth-ip4-policer-marker.robot
- x520_eth-ip4-vxlan-l2xc.robot
- x520_eth-ip6-base.robot
- x520_eth-ip6-cop-whitelist.robot
- x520_eth-ip6-fib-200k.robot
- x520_eth-ip6-fib-20k.robot
- x520_eth-ip6-fib-2M.robot
- x520_eth-ip6-iacl-dst.robot
- x520_eth-ip6-lisp-ip4.robot
- x520_eth-ip6-lisp-ip6.robot
- x520_eth-l2bd-base-vhost.robot
- x520_eth-l2bd-base.robot
- x520_eth-l2xc-base-vhost.robot
- x520_eth-l2xc-base.robot
- x710_eth-l2bd-base.robot
- xl710_eth-ip4-base.robot
- xl710_eth-ip6-base.robot
- xl710_eth-l2bd-base.robot
- xl710_eth-l2xc-base.robot