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
86 .. topic:: NIC_Amazon-Nitro-50G
95 2x10,000 entries in single fib table
99 2x100,000 entries in single fib table
103 2x1,000,000 entries in single fib table
107 Test with 1 L2 bridge domain.
111 Test with 10 L2 bridge domains.
115 Test with 100 L2 bridge domains.
119 Test with 1000 L2 bridge domains.
123 Test with 1 VLAN sub-interface.
127 Test with 10 VLAN sub-interfaces.
131 Test with 100 VLAN sub-interfaces.
135 Test with 1000 VLAN sub-interfaces.
139 Test with 1 VXLAN tunnel.
143 Test with 10 VXLAN tunnels.
147 Test with 100 VXLAN tunnels.
151 Test with 1000 VXLAN tunnels.
155 IPSec in tunnel mode - {t} tunnels.
157 .. topic:: SRC_USER_1
159 Traffic flow with 1 unique IP (users) in one direction.
161 .. topic:: SRC_USER_10
163 Traffic flow with 10 unique IPs (users) in one direction.
165 .. topic:: SRC_USER_100
167 Traffic flow with 100 unique IPs (users) in one direction.
169 .. topic:: SRC_USER_1000
171 Traffic flow with 1000 unique IPs (users) in one direction.
173 .. topic:: SRC_USER_2000
175 Traffic flow with 2000 unique IPs (users) in one direction.
177 .. topic:: SRC_USER_4000
179 Traffic flow with 4000 unique IPs (users) in one direction.
183 Traffic stream with 100 unique flows (10 IPs/users x 10 UDP ports) in one
188 Traffic stream with 10 000 unique flows (10 IPs/users x 1000 UDP ports) in
191 .. topic:: 100k_FLOWS
193 Traffic stream with 100 000 unique flows (100 IPs/users x 1000 UDP ports) in
196 .. topic:: HOSTS_1024
198 Stateless or stateful traffic stream with 1024 client source IP4 addresses,
199 usually with 63 flow differing in source port number. Could be UDP or TCP.
200 If NAT is used, the clients are inside. Outside IP range can differ.
202 .. topic:: HOSTS_4096
204 Stateless or stateful traffic stream with 4096 client source IP4 addresses,
205 usually with 63 flow differing in source port number. Could be UDP or TCP.
206 If NAT is used, the clients are inside. Outside IP range can differ.
208 .. topic:: HOSTS_16384
210 Stateless or stateful traffic stream with 16384 client source IP4 addresses,
211 usually with 63 flow differing in source port number. Could be UDP or TCP.
212 If NAT is used, the clients are inside. Outside IP range can differ.
214 .. topic:: HOSTS_65536
216 Stateless or stateful traffic stream with 65536 client source IP4 addresses,
217 usually with 63 flow differing in source port number. Could be UDP or TCP.
218 If NAT is used, the clients are inside. Outside IP range can differ.
220 .. topic:: HOSTS_262144
222 Stateless or stateful traffic stream with 262144 client source IP4 addresses
223 usually with 63 flow differing in source port number. Could be UDP or TCP.
224 If NAT is used, the clients are inside. Outside IP range can differ.
226 .. topic:: GENEVE4_1TUN
228 Test with 1 GENEVE IPv4 tunnel.
230 .. topic:: GENEVE4_4TUN
232 Test with 4 GENEVE IPv4 tunnels.
234 .. topic:: GENEVE4_16TUN
236 Test with 16 GENEVE IPv4 tunnels.
238 .. topic:: GENEVE4_64TUN
240 Test with 64 GENEVE IPv4 tunnels.
242 .. topic:: GENEVE4_256TUN
244 Test with 256 GENEVE IPv4 tunnels.
246 .. topic:: GENEVE4_1024TUN
248 Test with 1024 GENEVE IPv4 tunnels.
255 All functional test cases.
259 All performance test cases.
261 Performance Type Tags
262 ---------------------
266 Single test finding both No Drop Rate and Partial Drop Rate simultaneously.
267 The search is done by optimized algorithm which performs
268 multiple trial runs at different durations and transmit rates.
269 The results come from the final trials, which have duration of 30 seconds.
273 Performance tests where TG sends the traffic at maximum rate (line rate)
274 and reports total sent/received packets over trial duration.
275 The result is an average of 10 trials of 1 second duration.
279 Performance tests using PLRsearch to find the critical load.
283 Performance tests aimed to measure lost packets (time) when performing
284 reconfiguration while full throughput offered load is applied.
286 Ethernet Frame Size Tags
287 ------------------------
289 These are describing the traffic offered by Traffic Generator,
290 "primary" traffic in case of asymmetric load.
291 For traffic between DUTs, or for "secondary" traffic, see ${overhead} value.
295 64B frames used for test. Generic ethernet or IPv4.
299 78B frames used for test. Ipv6.
303 114B frames used for test. IPv4+vxlan.
307 118B frames used for test. Dot1q+IPv4+vxlan.
311 IMIX frame sequence (28x 64B, 16x 570B, 4x 1518B) used for test.
315 1460B frames used for test.
319 1480B frames used for test.
323 1514B frames used for test.
327 1518B frames used for test.
331 9000B frames used for test.
338 Baseline test cases, no encapsulation, no feature(s) configured in tests.
339 No scaling whatsoever, beyond minimum needed for RSS.
343 IPv4 baseline test cases, no encapsulation, no feature(s) configured in
344 tests. Minimal number of routes. Other quantities may be scaled.
348 IPv6 baseline test cases, no encapsulation, no feature(s) configured in
353 L2XC baseline test cases, no encapsulation, no feature(s) configured in
358 L2BD baseline test cases, no encapsulation, no feature(s) configured in
363 L2PATCH baseline test cases, no encapsulation, no feature(s) configured in
368 Scale test cases. Other tags specify which quantities are scaled.
369 Also applies if scaling is set on TG only (e.g. DUT works as IP4BASE).
373 Test cases where encapsulation is used. Use also encapsulation tag(s).
377 At least one feature is configured in test cases. Use also feature tag(s).
381 Tests which use any kind of UDP traffic (STL or ASTF profile).
385 Tests which use any kind of TCP traffic (STL or ASTF profile).
388 TODO: Should we define tags STL and ASTF?
392 Tests which use unidirectional UDP traffic (STL profile only).
396 Tests which use bidirectional UDP traffic (STL profile only).
400 Tests which measure connections per second on minimal UDP pseudoconnections.
401 This implies ASTF traffic profile is used.
402 This tag selects specific output processing in PAL.
406 Tests which measure connections per second on empty TCP connections.
407 This implies ASTF traffic profile is used.
408 This tag selects specific output processing in PAL.
412 Tests which measure requests per second on empty TCP connections.
413 This implies ASTF traffic profile is used.
414 This tag selects specific output processing in PAL.
418 Tests which measure packets per second on lightweight UDP transactions.
419 This implies ASTF traffic profile is used.
420 This tag selects specific output processing in PAL.
424 Tests which measure packets per second on lightweight TCP transactions.
425 This implies ASTF traffic profile is used.
426 This tag selects specific output processing in PAL.
430 Tests which use traffic formed of valid HTTP requests (and responses).
433 TODO: Add HTTP tag to the current hoststack tests.
434 TODO: Document other tags already used by hoststack tests.
438 LDP NGINX is un-modified NGINX with VPP via LD_PRELOAD.
440 .. topic:: NF_DENSITY
442 Performance tests that measure throughput of multiple VNF and CNF
443 service topologies at different service densities.
445 NF Service Density Tags
446 -----------------------
450 NF service density tests with VNF or CNF service chain topology(ies).
454 NF service density tests with CNF service pipeline topology(ies).
456 .. topic:: NF_L3FWDIP4
458 NF service density tests with DPDK l3fwd IPv4 routing as NF workload.
462 NF service density tests with VPP IPv4 routing as NF workload.
466 Service density matrix locator {r}R{c}C, {r}Row denoting number of
467 service instances, {c}Column denoting number of NFs per service
468 instance. {r}=(1,2,4,6,8,10), {c}=(1,2,4,6,8,10).
472 Service density {n}VM{t}T, {n}Number of NF Qemu VMs, {t}Number of threads
477 Service density {n}DCR{t}T, {n}Number of NF Docker containers, {t}Number of
480 .. topic:: {n}_ADDED_CHAINS
482 {n}Number of chains (or pipelines) added (and/or removed)
488 .. topic:: L2BDMACSTAT
490 VPP L2 bridge-domain, L2 MAC static.
492 .. topic:: L2BDMACLRN
494 VPP L2 bridge-domain, L2 MAC learning.
498 VPP L2 point-to-point cross-connect.
502 VPP IPv4 routed forwarding.
506 VPP IPv6 routed forwarding.
508 .. topic:: LOADBALANCER_MAGLEV
510 VPP Load balancer maglev mode.
512 .. topic:: LOADBALANCER_L3DSR
514 VPP Load balancer l3dsr mode.
516 .. topic:: LOADBALANCER_NAT4
518 VPP Load balancer nat4 mode.
531 .. topic:: MPLSUNRLAY
544 IPv4 overlay (IPv4 payload).
548 IPv6 overlay (IPv6 payload).
555 All test cases with dot1q.
559 All test cases with dot1ad.
566 All test cases with base Ethernet (no encapsulation).
570 All test cases with LISP.
574 All test cases with LISP-GPE.
576 .. topic:: LISP_IP4o4
578 All test cases with LISP_IP4o4.
580 .. topic:: LISPGPE_IP4o4
582 All test cases with LISPGPE_IP4o4.
584 .. topic:: LISPGPE_IP6o4
586 All test cases with LISPGPE_IP6o4.
588 .. topic:: LISPGPE_IP4o6
590 All test cases with LISPGPE_IP4o6.
592 .. topic:: LISPGPE_IP6o6
594 All test cases with LISPGPE_IP6o6.
598 All test cases with Vxlan.
602 All test cases with VXLAN-GPE.
606 All test cases with GRE.
610 All test cases with GTPU.
614 All test cases with IPSEC.
618 All test cases with Segment routing over IPv6 dataplane.
622 All SRv6 test cases with single SID.
624 .. topic:: SRv6_2SID_DECAP
626 All SRv6 test cases with two SIDs and with decapsulation.
628 .. topic:: SRv6_2SID_NODECAP
630 All SRv6 test cases with two SIDs and without decapsulation.
634 All test cases with GENEVE.
636 .. topic:: GENEVE_L3MODE
638 All test cases with GENEVE tunnel in L3 mode.
645 All test cases which use physical interface(s).
649 All test cases which uses Generic Segmentation Offload.
653 All test cases which uses VHOST.
655 .. topic:: VHOST_1024
657 All test cases which uses VHOST DPDK driver with qemu queue size set
662 All test cases which uses VIRTIO native VPP driver.
664 .. topic:: VIRTIO_1024
666 All test cases which uses VIRTIO native VPP driver with qemu queue size set
671 All test cases which uses VM with optimised scheduler policy.
675 All test cases which uses TUN and TAP.
679 All test cases which uses AFPKT.
683 All test cases which uses Netmap.
687 All test cases which uses Memif.
689 .. topic:: SINGLE_MEMIF
691 All test cases which uses only single Memif connection per DUT. One DUT
692 instance is running in container having one physical interface exposed to
697 All test cases which uses link bonding (BondEthernet interface).
699 .. topic:: LBOND_DPDK
701 All test cases which uses DPDK link bonding.
705 All test cases which uses VPP link bonding.
707 .. topic:: LBOND_MODE_XOR
709 All test cases which uses link bonding with mode XOR.
711 .. topic:: LBOND_MODE_LACP
713 All test cases which uses link bonding with mode LACP.
715 .. topic:: LBOND_LB_L34
717 All test cases which uses link bonding with load-balance mode l34.
721 All test cases which uses one link for link bonding.
725 All test cases which uses two links for link bonding.
729 All test cases which uses Intel Adaptive Virtual Function (AVF) device
730 plugin for VPP. This plugins provides native device support for Intel AVF.
731 AVF is driver specification for current and future Intel Virtual Function
732 devices. In essence, today this driver can be used only with Intel
733 XL710 / X710 / XXV710 adapters.
735 .. topic:: DRV_VFIO_PCI
737 All test cases which uses vfio-pci device driver. It supports variety of NIC
740 .. topic:: DRV_RDMA_CORE
742 All test cases which uses rdma-core device driver. It supports Mellanox
745 .. topic:: RXQ_SIZE_{n}
747 All test cases which RXQ size (RX descriptors) are set to {n}. Default is 0,
748 which means VPP (API) default.
750 .. topic:: TXQ_SIZE_{n}
752 All test cases which TXQ size (TX descriptors) are set to {n}. Default is 0,
753 which means VPP (API) default.
762 .. topic:: ADLALWLIST
768 NAT44 configured and tested.
772 NAT44 configured and tested.
776 ACL plugin configured and tested.
780 ACL plugin configured and tested on input path.
784 ACL plugin configured and tested on output path.
786 .. topic:: ACL_STATELESS
788 ACL plugin configured and tested in stateless mode (permit action).
790 .. topic:: ACL_STATEFUL
792 ACL plugin configured and tested in stateful mode (permit+reflect action).
796 ACL plugin configured and tested with 1 not-hitting ACE.
800 ACL plugin configured and tested with 10 not-hitting ACEs.
804 ACL plugin configured and tested with 50 not-hitting ACEs.
806 .. topic:: SRv6_PROXY
808 SRv6 endpoint to SR-unaware appliance via proxy.
810 .. topic:: SRv6_PROXY_STAT
812 SRv6 endpoint to SR-unaware appliance via static proxy.
814 .. topic:: SRv6_PROXY_DYN
816 SRv6 endpoint to SR-unaware appliance via dynamic proxy.
818 .. topic:: SRv6_PROXY_MASQ
820 SRv6 endpoint to SR-unaware appliance via masquerading proxy.
835 IPSec in transport mode.
839 IPSec in tunnel mode.
843 IPSec in interface mode.
847 IPSec using AES algorithms.
849 .. topic:: AES_128_CBC
851 IPSec using AES 128 CBC algorithms.
853 .. topic:: AES_128_GCM
855 IPSec using AES 128 GCM algorithms.
857 .. topic:: AES_256_GCM
859 IPSec using AES 256 GCM algorithms.
863 IPSec using HMAC integrity algorithms.
865 .. topic:: HMAC_SHA_256
867 IPSec using HMAC SHA 256 integrity algorithms.
869 .. topic:: HMAC_SHA_512
871 IPSec using HMAC SHA 512 integrity algorithms.
875 IPSec using crypto sw scheduler engine.
882 All test cases which use at least one virtual machine.
886 All test cases which use Linux container and LXC utils.
890 All test cases which use at least one Docker container.
894 All test cases which use Docker as container manager.
898 All test cases with specific APP use.
900 Container Orchestration Tags
901 ----------------------------
905 VPP running in Docker container acting as VSWITCH.
909 1 VPP running in Docker container acting as VNF work load.
913 2 VPP running in 2 Docker containers acting as VNF work load.
917 4 VPP running in 4 Docker containers acting as VNF work load.
925 All test cases using single poll mode thread.
930 All test cases using more then one poll mode driver thread.
934 All test cases with packet processing on single socket.
938 All test cases with packet processing on two sockets.
942 1 worker thread pinned to 1 dedicated physical core; or if HyperThreading is
943 enabled, 2 worker threads each pinned to a separate logical core within 1
944 dedicated physical core. Main thread pinned to core 1.
948 2 worker threads pinned to 2 dedicated physical cores; or if HyperThreading
949 is enabled, 4 worker threads each pinned to a separate logical core within 2
950 dedicated physical cores. Main thread pinned to core 1.
954 4 worker threads pinned to 4 dedicated physical cores; or if HyperThreading
955 is enabled, 8 worker threads each pinned to a separate logical core within 4
956 dedicated physical cores. Main thread pinned to core 1.
961 1 worker thread pinned to 1 dedicated physical core. 1 receive queue per
962 interface. Main thread pinned to core 1.
967 2 worker threads pinned to 2 dedicated physical cores. 1 receive queue per
968 interface. Main thread pinned to core 1.
973 4 worker threads pinned to 4 dedicated physical cores. 2 receive queues per
974 interface. Main thread pinned to core 1.
979 2 worker threads each pinned to a separate logical core within 1 dedicated
980 physical core. 1 receive queue per interface. Main thread pinned to core 1.
985 4 worker threads each pinned to a separate logical core within 2 dedicated
986 physical cores. 2 receive queues per interface. Main thread pinned to core
992 8 worker threads each pinned to a separate logical core within 4 dedicated
993 physical cores. 4 receive queues per interface. Main thread pinned to core