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
192 .. topic:: HOSTS_1024
194 Stateless or stateful traffic stream with 1024 client source IP4 addresses,
195 usually with 63 flow differing in source port number. Could be UDP or TCP.
196 If NAT is used, the clients are inside. Outside IP range can differ.
198 .. topic:: HOSTS_4096
200 Stateless or stateful traffic stream with 4096 client source IP4 addresses,
201 usually with 63 flow differing in source port number. Could be UDP or TCP.
202 If NAT is used, the clients are inside. Outside IP range can differ.
204 .. topic:: HOSTS_16384
206 Stateless or stateful traffic stream with 16384 client source IP4 addresses,
207 usually with 63 flow differing in source port number. Could be UDP or TCP.
208 If NAT is used, the clients are inside. Outside IP range can differ.
210 .. topic:: HOSTS_65536
212 Stateless or stateful traffic stream with 65536 client source IP4 addresses,
213 usually with 63 flow differing in source port number. Could be UDP or TCP.
214 If NAT is used, the clients are inside. Outside IP range can differ.
216 .. topic:: HOSTS_262144
218 Stateless or stateful traffic stream with 262144 client source IP4 addresses
219 usually with 63 flow differing in source port number. Could be UDP or TCP.
220 If NAT is used, the clients are inside. Outside IP range can differ.
222 .. topic:: GENEVE4_1TUN
224 Test with 1 GENEVE IPv4 tunnel.
226 .. topic:: GENEVE4_4TUN
228 Test with 4 GENEVE IPv4 tunnels.
230 .. topic:: GENEVE4_16TUN
232 Test with 16 GENEVE IPv4 tunnels.
234 .. topic:: GENEVE4_64TUN
236 Test with 64 GENEVE IPv4 tunnels.
238 .. topic:: GENEVE4_256TUN
240 Test with 256 GENEVE IPv4 tunnels.
242 .. topic:: GENEVE4_1024TUN
244 Test with 1024 GENEVE IPv4 tunnels.
251 All functional test cases.
255 All performance test cases.
257 Performance Type Tags
258 ---------------------
262 Single test finding both No Drop Rate and Partial Drop Rate simultaneously.
263 The search is done by optimized algorithm which performs
264 multiple trial runs at different durations and transmit rates.
265 The results come from the final trials, which have duration of 30 seconds.
269 Performance tests where TG sends the traffic at maximum rate (line rate)
270 and reports total sent/received packets over trial duration.
271 The result is an average of 10 trials of 1 second duration.
275 Performance tests using PLRsearch to find the critical load.
279 Performance tests aimed to measure lost packets (time) when performing
280 reconfiguration while full throughput offered load is applied.
282 Ethernet Frame Size Tags
283 ------------------------
285 These are describing the traffic offered by Traffic Generator,
286 "primary" traffic in case of asymmetric load.
287 For traffic between DUTs, or for "secondary" traffic, see ${overhead} value.
291 64B frames used for test. Generic ethernet or IPv4.
295 78B frames used for test. Ipv6.
299 114B frames used for test. IPv4+vxlan.
303 118B frames used for test. Dot1q+IPv4+vxlan.
307 IMIX frame sequence (28x 64B, 16x 570B, 4x 1518B) used for test.
311 1460B frames used for test.
315 1480B frames used for test.
319 1514B frames used for test.
323 1518B frames used for test.
327 9000B frames used for test.
334 Baseline test cases, no encapsulation, no feature(s) configured in tests.
335 No scaling whatsoever, beyond minimum needed for RSS.
339 IPv4 baseline test cases, no encapsulation, no feature(s) configured in
340 tests. Minimal number of routes. Other quantities may be scaled.
344 IPv6 baseline test cases, no encapsulation, no feature(s) configured in
349 L2XC baseline test cases, no encapsulation, no feature(s) configured in
354 L2BD baseline test cases, no encapsulation, no feature(s) configured in
359 L2PATCH baseline test cases, no encapsulation, no feature(s) configured in
364 Scale test cases. Other tags specify which quantities are scaled.
365 Also applies if scaling is set on TG only (e.g. DUT works as IP4BASE).
369 Test cases where encapsulation is used. Use also encapsulation tag(s).
373 At least one feature is configured in test cases. Use also feature tag(s).
377 Tests which use any kind of UDP traffic (STL or ASTF profile).
381 Tests which use any kind of TCP traffic (STL or ASTF profile).
384 TODO: Should we define tags STL and ASTF?
388 Tests which use unidirectional UDP traffic (STL profile only).
392 Tests which use bidirectional UDP traffic (STL profile only).
396 Tests which measure connections per second on minimal UDP pseudoconnections.
397 This implies ASTF traffic profile is used.
398 This tag selects specific output processing in PAL.
402 Tests which measure connections per second on empty TCP connections.
403 This implies ASTF traffic profile is used.
404 This tag selects specific output processing in PAL.
408 Tests which measure packets per second on lightweight UDP transactions.
409 This implies ASTF traffic profile is used.
410 This tag selects specific output processing in PAL.
414 Tests which measure packets per second on lightweight TCP transactions.
415 This implies ASTF traffic profile is used.
416 This tag selects specific output processing in PAL.
420 Tests which use traffic formed of valid HTTP requests (and responses).
423 TODO: Add HTTP tag to the current hoststack tests.
424 TODO: Document other tags already used by hoststack tests.
426 .. topic:: NF_DENSITY
428 Performance tests that measure throughput of multiple VNF and CNF
429 service topologies at different service densities.
431 NF Service Density Tags
432 -----------------------
436 NF service density tests with VNF or CNF service chain topology(ies).
440 NF service density tests with CNF service pipeline topology(ies).
442 .. topic:: NF_L3FWDIP4
444 NF service density tests with DPDK l3fwd IPv4 routing as NF workload.
448 NF service density tests with VPP IPv4 routing as NF workload.
452 Service density matrix locator {r}R{c}C, {r}Row denoting number of
453 service instances, {c}Column denoting number of NFs per service
454 instance. {r}=(1,2,4,6,8,10), {c}=(1,2,4,6,8,10).
458 Service density {n}VM{t}T, {n}Number of NF Qemu VMs, {t}Number of threads
463 Service density {n}DCR{t}T, {n}Number of NF Docker containers, {t}Number of
466 .. topic:: {n}_ADDED_CHAINS
468 {n}Number of chains (or pipelines) added (and/or removed)
474 .. topic:: L2BDMACSTAT
476 VPP L2 bridge-domain, L2 MAC static.
478 .. topic:: L2BDMACLRN
480 VPP L2 bridge-domain, L2 MAC learning.
484 VPP L2 point-to-point cross-connect.
488 VPP IPv4 routed forwarding.
492 VPP IPv6 routed forwarding.
494 .. topic:: LOADBALANCER_MAGLEV
496 VPP Load balancer maglev mode.
498 .. topic:: LOADBALANCER_L3DSR
500 VPP Load balancer l3dsr mode.
502 .. topic:: LOADBALANCER_NAT4
504 VPP Load balancer nat4 mode.
517 .. topic:: MPLSUNRLAY
530 IPv4 overlay (IPv4 payload).
534 IPv6 overlay (IPv6 payload).
541 All test cases with dot1q.
545 All test cases with dot1ad.
552 All test cases with base Ethernet (no encapsulation).
556 All test cases with LISP.
560 All test cases with LISP-GPE.
562 .. topic:: LISP_IP4o4
564 All test cases with LISP_IP4o4.
566 .. topic:: LISPGPE_IP4o4
568 All test cases with LISPGPE_IP4o4.
570 .. topic:: LISPGPE_IP6o4
572 All test cases with LISPGPE_IP6o4.
574 .. topic:: LISPGPE_IP4o6
576 All test cases with LISPGPE_IP4o6.
578 .. topic:: LISPGPE_IP6o6
580 All test cases with LISPGPE_IP6o6.
584 All test cases with Vxlan.
588 All test cases with VXLAN-GPE.
592 All test cases with GRE.
596 All test cases with IPSEC.
600 All test cases with Segment routing over IPv6 dataplane.
604 All SRv6 test cases with single SID.
606 .. topic:: SRv6_2SID_DECAP
608 All SRv6 test cases with two SIDs and with decapsulation.
610 .. topic:: SRv6_2SID_NODECAP
612 All SRv6 test cases with two SIDs and without decapsulation.
616 All test cases with GENEVE.
618 .. topic:: GENEVE_L3MODE
620 All test cases with GENEVE tunnel in L3 mode.
627 All test cases which use physical interface(s).
631 All test cases which uses Generic Segmentation Offload.
635 All test cases which uses VHOST.
637 .. topic:: VHOST_1024
639 All test cases which uses VHOST DPDK driver with qemu queue size set
644 All test cases which uses VIRTIO native VPP driver.
646 .. topic:: VIRTIO_1024
648 All test cases which uses VIRTIO native VPP driver with qemu queue size set
653 All test cases which uses VM with optimised scheduler policy.
657 All test cases which uses TUN and TAP.
661 All test cases which uses AFPKT.
665 All test cases which uses Netmap.
669 All test cases which uses Memif.
671 .. topic:: SINGLE_MEMIF
673 All test cases which uses only single Memif connection per DUT. One DUT
674 instance is running in container having one physical interface exposed to
679 All test cases which uses link bonding (BondEthernet interface).
681 .. topic:: LBOND_DPDK
683 All test cases which uses DPDK link bonding.
687 All test cases which uses VPP link bonding.
689 .. topic:: LBOND_MODE_XOR
691 All test cases which uses link bonding with mode XOR.
693 .. topic:: LBOND_MODE_LACP
695 All test cases which uses link bonding with mode LACP.
697 .. topic:: LBOND_LB_L34
699 All test cases which uses link bonding with load-balance mode l34.
703 All test cases which uses one link for link bonding.
707 All test cases which uses two links for link bonding.
711 All test cases which uses Intel Adaptive Virtual Function (AVF) device
712 plugin for VPP. This plugins provides native device support for Intel AVF.
713 AVF is driver specification for current and future Intel Virtual Function
714 devices. In essence, today this driver can be used only with Intel
715 XL710 / X710 / XXV710 adapters.
717 .. topic:: DRV_VFIO_PCI
719 All test cases which uses vfio-pci device driver. It supports variety of NIC
722 .. topic:: DRV_RDMA_CORE
724 All test cases which uses rdma-core device driver. It supports Mellanox
727 .. topic:: RXQ_SIZE_{n}
729 All test cases which RXQ size (RX descriptors) are set to {n}. Default is 0,
730 which means VPP (API) default.
732 .. topic:: TXQ_SIZE_{n}
734 All test cases which TXQ size (TX descriptors) are set to {n}. Default is 0,
735 which means VPP (API) default.
744 .. topic:: ADLALWLIST
750 NAT44 configured and tested.
754 NAT44 configured and tested.
758 ACL plugin configured and tested.
762 ACL plugin configured and tested on input path.
766 ACL plugin configured and tested on output path.
768 .. topic:: ACL_STATELESS
770 ACL plugin configured and tested in stateless mode (permit action).
772 .. topic:: ACL_STATEFUL
774 ACL plugin configured and tested in stateful mode (permit+reflect action).
778 ACL plugin configured and tested with 1 not-hitting ACE.
782 ACL plugin configured and tested with 10 not-hitting ACEs.
786 ACL plugin configured and tested with 50 not-hitting ACEs.
788 .. topic:: SRv6_PROXY
790 SRv6 endpoint to SR-unaware appliance via proxy.
792 .. topic:: SRv6_PROXY_STAT
794 SRv6 endpoint to SR-unaware appliance via static proxy.
796 .. topic:: SRv6_PROXY_DYN
798 SRv6 endpoint to SR-unaware appliance via dynamic proxy.
800 .. topic:: SRv6_PROXY_MASQ
802 SRv6 endpoint to SR-unaware appliance via masquerading proxy.
817 IPSec in transport mode.
821 IPSec in tunnel mode.
825 IPSec in interface mode.
829 IPSec using AES algorithms.
831 .. topic:: AES_128_CBC
833 IPSec using AES 128 CBC algorithms.
835 .. topic:: AES_128_GCM
837 IPSec using AES 128 GCM algorithms.
839 .. topic:: AES_256_GCM
841 IPSec using AES 256 GCM algorithms.
845 IPSec using HMAC integrity algorithms.
847 .. topic:: HMAC_SHA_256
849 IPSec using HMAC SHA 256 integrity algorithms.
851 .. topic:: HMAC_SHA_512
853 IPSec using HMAC SHA 512 integrity algorithms.
857 IPSec using crypto sw scheduler engine.
864 All test cases which use at least one virtual machine.
868 All test cases which use Linux container and LXC utils.
872 All test cases which use at least one Docker container.
876 All test cases which use Docker as container manager.
880 All test cases with specific APP use.
882 Container Orchestration Tags
883 ----------------------------
887 VPP running in Docker container acting as VSWITCH.
891 1 VPP running in Docker container acting as VNF work load.
895 2 VPP running in 2 Docker containers acting as VNF work load.
899 4 VPP running in 4 Docker containers acting as VNF work load.
907 All test cases using single poll mode thread.
912 All test cases using more then one poll mode driver thread.
916 All test cases with packet processing on single socket.
920 All test cases with packet processing on two sockets.
924 1 worker thread pinned to 1 dedicated physical core; or if HyperThreading is
925 enabled, 2 worker threads each pinned to a separate logical core within 1
926 dedicated physical core. Main thread pinned to core 1.
930 2 worker threads pinned to 2 dedicated physical cores; or if HyperThreading
931 is enabled, 4 worker threads each pinned to a separate logical core within 2
932 dedicated physical cores. Main thread pinned to core 1.
936 4 worker threads pinned to 4 dedicated physical cores; or if HyperThreading
937 is enabled, 8 worker threads each pinned to a separate logical core within 4
938 dedicated physical cores. Main thread pinned to core 1.
943 1 worker thread pinned to 1 dedicated physical core. 1 receive queue per
944 interface. Main thread pinned to core 1.
949 2 worker threads pinned to 2 dedicated physical cores. 1 receive queue per
950 interface. Main thread pinned to core 1.
955 4 worker threads pinned to 4 dedicated physical cores. 2 receive queues per
956 interface. Main thread pinned to core 1.
961 2 worker threads each pinned to a separate logical core within 1 dedicated
962 physical core. 1 receive queue per interface. Main thread pinned to core 1.
967 4 worker threads each pinned to a separate logical core within 2 dedicated
968 physical cores. 2 receive queues per interface. Main thread pinned to core
974 8 worker threads each pinned to a separate logical core within 4 dedicated
975 physical cores. 4 receive queues per interface. Main thread pinned to core