4 All CSIT test cases are labelled with Robot Framework tags used to allow for
5 easy test case type identification, test case grouping and selection for
6 execution. Following sections list currently used CSIT tags and their
12 .. topic:: 2_NODE_DOUBLE_LINK_TOPO
14 2 nodes connected in a circular topology with two links interconnecting
17 .. topic:: 2_NODE_SINGLE_LINK_TOPO
19 2 nodes connected in a circular topology with at least one link
20 interconnecting devices.
22 .. topic:: 3_NODE_DOUBLE_LINK_TOPO
24 3 nodes connected in a circular topology with two links interconnecting
27 .. topic:: 3_NODE_SINGLE_LINK_TOPO
29 3 nodes connected in a circular topology with at least one link
30 interconnecting devices.
37 Test case(s) marked to not run in case of vpp-csit-verify (i.e. VPP patch)
38 and csit-vpp-verify jobs (i.e. CSIT patch).
40 .. topic:: SKIP_VPP_PATCH
42 Test case(s) marked to not run in case of vpp-csit-verify (i.e. VPP patch).
49 DUTs and TGs are running on bare metal.
53 DUTs and TGs are running in virtual environment.
57 DUTs with VPP and capable of running Virtual Machine.
62 .. topic:: NIC_Intel-X520-DA2
66 .. topic:: NIC_Intel-XL710
70 .. topic:: NIC_Intel-X710
74 .. topic:: NIC_Intel-XXV710
78 .. topic:: NIC_Cisco-VIC-1227
82 .. topic:: NIC_Cisco-VIC-1385
91 2x10,000 entries in single fib table
95 2x100,000 entries in single fib table
99 2x1,000,000 entries in single fib table
103 Test with 1 L2 bridge domain.
107 Test with 10 L2 bridge domains.
111 Test with 100 L2 bridge domains.
115 Test with 1000 L2 bridge domains.
119 Test with 1 VLAN sub-interface.
123 Test with 10 VLAN sub-interfaces.
127 Test with 100 VLAN sub-interfaces.
131 Test with 1000 VLAN sub-interfaces.
135 Test with 1 VXLAN tunnel.
139 Test with 10 VXLAN tunnels.
143 Test with 100 VXLAN tunnels.
147 Test with 1000 VXLAN tunnels.
151 IPSec in tunnel mode - {t} tunnels.
153 .. topic:: SRC_USER_1
155 Traffic flow with 1 unique IP (users) in one direction.
157 .. topic:: SRC_USER_10
159 Traffic flow with 10 unique IPs (users) in one direction.
161 .. topic:: SRC_USER_100
163 Traffic flow with 100 unique IPs (users) in one direction.
165 .. topic:: SRC_USER_1000
167 Traffic flow with 1000 unique IPs (users) in one direction.
169 .. topic:: SRC_USER_2000
171 Traffic flow with 2000 unique IPs (users) in one direction.
173 .. topic:: SRC_USER_4000
175 Traffic flow with 4000 unique IPs (users) in one direction.
179 Traffic stream with 100 unique flows (10 IPs/users x 10 UDP ports) in one
184 Traffic stream with 10 000 unique flows (10 IPs/users x 1000 UDP ports) in
187 .. topic:: 100k_FLOWS
189 Traffic stream with 100 000 unique flows (100 IPs/users x 1000 UDP ports) in
197 All functional test cases.
201 All performance test cases.
203 Performance Type Tags
204 ---------------------
208 Single test finding both No Drop Rate and Partial Drop Rate simultaneously.
209 The search is done by optimized algorithm which performs
210 multiple trial runs at different durations and transmit rates.
211 The results come from the final trials, which have duration of 30 seconds.
215 Performance tests where TG sends the traffic at maximum rate (line rate)
216 and reports total sent/received packets over trial duration.
217 The result is an average of 10 trials of 1 second duration.
221 Performance tests using PLRsearch to find the critical load.
225 Performance tests aimed to measure lost packets (time) when performing
226 reconfiguration while full throughput offered load is applied.
228 Ethernet Frame Size Tags
229 ------------------------
231 These are describing the traffic offered by Traffic Generator,
232 "primary" traffic in case of asymmetric load.
233 For traffic between DUTs, or for "secondary" traffic, see ${overhead} value.
237 64B frames used for test. Generic ethernet or IPv4.
241 78B frames used for test. Ipv6.
245 114B frames used for test. IPv4+vxlan.
249 118B frames used for test. Dot1q+IPv4+vxlan.
253 IMIX frame sequence (28x 64B, 16x 570B, 4x 1518B) used for test.
257 1460B frames used for test.
261 1480B frames used for test.
265 1514B frames used for test.
269 1518B frames used for test.
273 9000B frames used for test.
280 Baseline test cases, no encapsulation, no feature(s) configured in tests.
284 IPv4 baseline test cases, no encapsulation, no feature(s) configured in
289 IPv6 baseline test cases, no encapsulation, no feature(s) configured in
294 L2XC baseline test cases, no encapsulation, no feature(s) configured in
299 L2BD baseline test cases, no encapsulation, no feature(s) configured in
304 L2PATCH baseline test cases, no encapsulation, no feature(s) configured in
313 Test cases where encapsulation is used. Use also encapsulation tag(s).
317 At least one feature is configured in test cases. Use also feature tag(s).
325 Performance tests which measure connections per second using http requests.
329 Performance tests which measure requests per second using http requests.
333 Tests which use HTTP.
335 .. topic:: NF_DENSITY
337 Performance tests that measure throughput of multiple VNF and CNF
338 service topologies at different service densities.
340 NF Service Density Tags
341 -----------------------
345 NF service density tests with VNF or CNF service chain topology(ies).
349 NF service density tests with CNF service pipeline topology(ies).
351 .. topic:: NF_L3FWDIP4
353 NF service density tests with DPDK l3fwd IPv4 routing as NF workload.
357 NF service density tests with VPP IPv4 routing as NF workload.
361 Service density matrix locator {r}R{c}C, {r}Row denoting number of
362 service instances, {c}Column denoting number of NFs per service
363 instance. {r}=(1,2,4,6,8,10), {c}=(1,2,4,6,8,10).
367 Service density {n}VM{t}T, {n}Number of NF Qemu VMs, {t}Number of threads
372 Service density {n}DCR{t}T, {n}Number of NF Docker containers, {t}Number of
375 .. topic:: {n}_ADDED_CHAINS
377 {n}Number of chains (or pipelines) added (and/or removed)
383 .. topic:: L2BDMACSTAT
385 VPP L2 bridge-domain, L2 MAC static.
387 .. topic:: L2BDMACLRN
389 VPP L2 bridge-domain, L2 MAC learning.
393 VPP L2 point-to-point cross-connect.
397 VPP IPv4 routed forwarding.
401 VPP IPv6 routed forwarding.
403 .. topic:: LOADBALANCER_MAGLEV
405 VPP Load balancer maglev mode.
407 .. topic:: LOADBALANCER_L3DSR
409 VPP Load balancer l3dsr mode.
411 .. topic:: LOADBALANCER_NAT4
413 VPP Load balancer nat4 mode.
426 .. topic:: MPLSUNRLAY
439 IPv4 overlay (IPv4 payload).
443 IPv6 overlay (IPv6 payload).
450 All test cases with dot1q.
454 All test cases with dot1ad.
461 All test cases with base Ethernet (no encapsulation).
465 All test cases with LISP.
469 All test cases with LISP-GPE.
471 .. topic:: LISP_IP4o4
473 All test cases with LISP_IP4o4.
475 .. topic:: LISPGPE_IP4o4
477 All test cases with LISPGPE_IP4o4.
479 .. topic:: LISPGPE_IP6o4
481 All test cases with LISPGPE_IP6o4.
483 .. topic:: LISPGPE_IP4o6
485 All test cases with LISPGPE_IP4o6.
487 .. topic:: LISPGPE_IP6o6
489 All test cases with LISPGPE_IP6o6.
493 All test cases with Vxlan.
497 All test cases with VXLAN-GPE.
501 All test cases with GRE.
505 All test cases with IPSEC.
509 All test cases with Segment routing over IPv6 dataplane.
513 All SRv6 test cases with single SID.
515 .. topic:: SRv6_2SID_DECAP
517 All SRv6 test cases with two SIDs and with decapsulation.
519 .. topic:: SRv6_2SID_NODECAP
521 All SRv6 test cases with two SIDs and without decapsulation.
528 All test cases which use physical interface(s).
532 All test cases which uses VHOST.
534 .. topic:: VHOST_1024
536 All test cases which uses VHOST DPDK driver with qemu queue size set
541 All test cases which uses VIRTIO native VPP driver.
543 .. topic:: VIRTIO_1024
545 All test cases which uses VIRTIO native VPP driver with qemu queue size set
550 All test cases which uses VM with optimised scheduler policy.
554 All test cases which uses TUN and TAP.
558 All test cases which uses AFPKT.
562 All test cases which uses Netmap.
566 All test cases which uses Memif.
568 .. topic:: SINGLE_MEMIF
570 All test cases which uses only single Memif connection per DUT. One DUT
571 instance is running in container having one physical interface exposed to
576 All test cases which uses link bonding (BondEthernet interface).
578 .. topic:: LBOND_DPDK
580 All test cases which uses DPDK link bonding.
584 All test cases which uses VPP link bonding.
586 .. topic:: LBOND_MODE_XOR
588 All test cases which uses link bonding with mode XOR.
590 .. topic:: LBOND_MODE_LACP
592 All test cases which uses link bonding with mode LACP.
594 .. topic:: LBOND_LB_L34
596 All test cases which uses link bonding with load-balance mode l34.
600 All test cases which uses one link for link bonding.
604 All test cases which uses two links for link bonding.
608 All test cases which uses Intel Adaptive Virtual Function (AVF) device
609 plugin for VPP. This plugins provides native device support for Intel AVF.
610 AVF is driver specification for current and future Intel Virtual Function
611 devices. In essence, today this driver can be used only with Intel
612 XL710 / X710 / XXV710 adapters.
614 .. topic:: DRV_VFIO_PCI
616 All test cases which uses vfio-pci device driver. It supports variety of NIC
619 .. topic:: DRV_RDMA_CORE
621 All test cases which uses rdma-core device driver. It supports Mellanox
624 .. topic:: RXQ_SIZE_{n}
626 All test cases which RXQ size (RX descriptors) are set to {n}. Default is 0,
627 which means VPP (API) default.
629 .. topic:: TXQ_SIZE_{n}
631 All test cases which TXQ size (TX descriptors) are set to {n}. Default is 0,
632 which means VPP (API) default.
647 NAT44 configured and tested.
651 NAT44 configured and tested.
655 ACL plugin configured and tested.
659 ACL plugin configured and tested on input path.
663 ACL plugin configured and tested on output path.
665 .. topic:: ACL_STATELESS
667 ACL plugin configured and tested in stateless mode (permit action).
669 .. topic:: ACL_STATEFUL
671 ACL plugin configured and tested in stateful mode (permit+reflect action).
675 ACL plugin configured and tested with 1 not-hitting ACE.
679 ACL plugin configured and tested with 10 not-hitting ACEs.
683 ACL plugin configured and tested with 50 not-hitting ACEs.
685 .. topic:: SRv6_PROXY
687 SRv6 endpoint to SR-unaware appliance via proxy.
689 .. topic:: SRv6_PROXY_STAT
691 SRv6 endpoint to SR-unaware appliance via static proxy.
693 .. topic:: SRv6_PROXY_DYN
695 SRv6 endpoint to SR-unaware appliance via dynamic proxy.
697 .. topic:: SRv6_PROXY_MASQ
699 SRv6 endpoint to SR-unaware appliance via masquerading proxy.
714 IPSec in transport mode.
718 IPSec in tunnel mode.
722 IPSec in interface mode.
726 IPSec using AES algorithms.
728 .. topic:: AES_128_CBC
730 IPSec using AES 128 CBC algorithms.
732 .. topic:: AES_128_GCM
734 IPSec using AES 128 GCM algorithms.
736 .. topic:: AES_256_GCM
738 IPSec using AES 256 GCM algorithms.
742 IPSec using HMAC integrity algorithms.
744 .. topic:: HMAC_SHA_256
746 IPSec using HMAC SHA 256 integrity algorithms.
748 .. topic:: HMAC_SHA_512
750 IPSec using HMAC SHA 512 integrity algorithms.
757 All test cases which use at least one virtual machine.
761 All test cases which use Linux container and LXC utils.
765 All test cases which use at least one Docker container.
769 All test cases which use Docker as container manager.
773 All test cases with specific APP use.
775 Container Orchestration Tags
776 ----------------------------
780 VPP running in Docker container acting as VSWITCH.
784 1 VPP running in Docker container acting as VNF work load.
788 2 VPP running in 2 Docker containers acting as VNF work load.
792 4 VPP running in 4 Docker containers acting as VNF work load.
800 All test cases using single poll mode thread.
805 All test cases using more then one poll mode driver thread.
809 All test cases with packet processing on single socket.
813 All test cases with packet processing on two sockets.
817 1 worker thread pinned to 1 dedicated physical core; or if HyperThreading is
818 enabled, 2 worker threads each pinned to a separate logical core within 1
819 dedicated physical core. Main thread pinned to core 1.
823 2 worker threads pinned to 2 dedicated physical cores; or if HyperThreading
824 is enabled, 4 worker threads each pinned to a separate logical core within 2
825 dedicated physical cores. Main thread pinned to core 1.
829 4 worker threads pinned to 4 dedicated physical cores; or if HyperThreading
830 is enabled, 8 worker threads each pinned to a separate logical core within 4
831 dedicated physical cores. Main thread pinned to core 1.
836 1 worker thread pinned to 1 dedicated physical core. 1 receive queue per
837 interface. Main thread pinned to core 1.
842 2 worker threads pinned to 2 dedicated physical cores. 1 receive queue per
843 interface. Main thread pinned to core 1.
848 4 worker threads pinned to 4 dedicated physical cores. 2 receive queues per
849 interface. Main thread pinned to core 1.
854 2 worker threads each pinned to a separate logical core within 1 dedicated
855 physical core. 1 receive queue per interface. Main thread pinned to core 1.
860 4 worker threads each pinned to a separate logical core within 2 dedicated
861 physical cores. 2 receive queues per interface. Main thread pinned to core
867 8 worker threads each pinned to a separate logical core within 4 dedicated
868 physical cores. 4 receive queues per interface. Main thread pinned to core
876 Honeycomb functional test cases.
880 Honeycomb NSH test cases.
882 .. topic:: HC_PERSIST
884 Honeycomb persistence test cases.
886 .. topic:: HC_REST_ONLY
888 (Exclusion tag) Honeycomb test cases that cannot be run in Netconf mode
889 using ODL client for Restfconf -> Netconf translation.