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).
321 Functional test cases for TLDK.
325 Functional test cases for DMM.
333 Performance tests which measure connections per second using http requests.
337 Performance tests which measure requests per second using http requests.
341 Tests which use HTTP.
343 .. topic:: NF_DENSITY
345 Performance tests that measure throughput of multiple VNF and CNF
346 service topologies at different service densities.
348 NF Service Density Tags
349 -----------------------
353 NF service density tests with VNF or CNF service chain topology(ies).
357 NF service density tests with CNF service pipeline topology(ies).
359 .. topic:: NF_L3FWDIP4
361 NF service density tests with DPDK l3fwd IPv4 routing as NF workload.
365 NF service density tests with VPP IPv4 routing as NF workload.
369 Service density matrix locator {r}R{c}C, {r}Row denoting number of
370 service instances, {c}Column denoting number of NFs per service
371 instance. {r}=(1,2,4,6,8,10), {c}=(1,2,4,6,8,10).
375 Service density {n}VM{t}T, {n}Number of NF Qemu VMs, {t}Number of threads
380 Service density {n}DCR{t}T, {n}Number of NF Docker containers, {t}Number of
383 .. topic:: {n}_ADDED_CHAINS
385 {n}Number of chains (or pipelines) added (and/or removed)
391 .. topic:: L2BDMACSTAT
393 VPP L2 bridge-domain, L2 MAC static.
395 .. topic:: L2BDMACLRN
397 VPP L2 bridge-domain, L2 MAC learning.
401 VPP L2 point-to-point cross-connect.
405 VPP IPv4 routed forwarding.
409 VPP IPv6 routed forwarding.
422 .. topic:: MPLSUNRLAY
435 IPv4 overlay (IPv4 payload).
439 IPv6 overlay (IPv6 payload).
446 All test cases with dot1q.
450 All test cases with dot1ad.
457 All test cases with base Ethernet (no encapsulation).
461 All test cases with LISP.
465 All test cases with LISP-GPE.
469 All test cases with Vxlan.
473 All test cases with VXLAN-GPE.
477 All test cases with GRE.
481 All test cases with IPSEC.
485 All test cases with Segment routing over IPv6 dataplane.
489 All SRv6 test cases with single SID.
491 .. topic:: SRv6_2SID_DECAP
493 All SRv6 test cases with two SIDs and with decapsulation.
495 .. topic:: SRv6_2SID_NODECAP
497 All SRv6 test cases with two SIDs and without decapsulation.
504 All test cases which use physical interface(s).
508 All test cases which uses VHOST.
512 All test cases which uses VHOST with qemu queue size set to 256.
514 .. topic:: VHOST_1024
516 All test cases which uses VHOST with qemu queue size set to 1024.
520 All test cases which uses VM with optimised scheduler policy.
524 All test cases which uses TUN and TAP.
528 All test cases which uses AFPKT.
532 All test cases which uses Netmap.
536 All test cases which uses Memif.
538 .. topic:: SINGLE_MEMIF
540 All test cases which uses only single Memif connection per DUT. One DUT
541 instance is running in container having one physical interface exposed to
546 All test cases which uses link bonding (BondEthernet interface).
548 .. topic:: LBOND_DPDK
550 All test cases which uses DPDK link bonding.
554 All test cases which uses VPP link bonding.
556 .. topic:: LBOND_MODE_XOR
558 All test cases which uses link bonding with mode XOR.
560 .. topic:: LBOND_MODE_LACP
562 All test cases which uses link bonding with mode LACP.
564 .. topic:: LBOND_LB_L34
566 All test cases which uses link bonding with load-balance mode l34.
570 All test cases which uses one link for link bonding.
574 All test cases which uses two links for link bonding.
578 All test cases which uses Intel Adaptive Virtual Function (AVF) device
579 plugin for VPP. This plugins provides native device support for Intel AVF.
580 AVF is driver specification for current and future Intel Virtual Function
581 devices. In essence, today this driver can be used only with Intel
582 XL710 / X710 / XXV710 adapters.
597 NAT44 configured and tested.
601 NAT44 configured and tested.
605 ACL plugin configured and tested.
609 ACL plugin configured and tested on input path.
613 ACL plugin configured and tested on output path.
615 .. topic:: ACL_STATELESS
617 ACL plugin configured and tested in stateless mode (permit action).
619 .. topic:: ACL_STATEFUL
621 ACL plugin configured and tested in stateful mode (permit+reflect action).
625 ACL plugin configured and tested with 1 not-hitting ACE.
629 ACL plugin configured and tested with 10 not-hitting ACEs.
633 ACL plugin configured and tested with 50 not-hitting ACEs.
635 .. topic:: SRv6_PROXY
637 SRv6 endpoint to SR-unaware appliance via proxy.
639 .. topic:: SRv6_PROXY_STAT
641 SRv6 endpoint to SR-unaware appliance via static proxy.
643 .. topic:: SRv6_PROXY_DYN
645 SRv6 endpoint to SR-unaware appliance via dynamic proxy.
647 .. topic:: SRv6_PROXY_MASQ
649 SRv6 endpoint to SR-unaware appliance via masquerading proxy.
664 IPSec in transport mode.
668 IPSec in tunnel mode.
672 IPSec in interface mode.
676 IPSec using AES algorithms.
678 .. topic:: AES_128_CBC
680 IPSec using AES 128 CBC algorithms.
682 .. topic:: AES_128_GCM
684 IPSec using AES 128 GCM algorithms.
686 .. topic:: AES_256_GCM
688 IPSec using AES 256 GCM algorithms.
692 IPSec using HMAC integrity algorithms.
694 .. topic:: HMAC_SHA_256
696 IPSec using HMAC SHA 256 integrity algorithms.
698 .. topic:: HMAC_SHA_512
700 IPSec using HMAC SHA 512 integrity algorithms.
707 All test cases which use at least one virtual machine.
711 All test cases which use Linux container and LXC utils.
715 All test cases which use at least one Docker container.
719 All test cases which use Docker as container manager.
723 All test cases with specific APP use.
725 Container Orchestration Tags
726 ----------------------------
730 All test cases which use Kubernetes for orchestration.
732 .. topic:: SFC_CONTROLLER
734 All test cases which use ligato/sfc_controller for driving configuration
735 of vpp inside container.
739 All test cases which use Golang implementation of a control/management plane
744 VPP running in Docker container acting as VSWITCH.
748 1 VPP running in Docker container acting as VNF work load.
752 2 VPP running in 2 Docker containers acting as VNF work load.
756 4 VPP running in 4 Docker containers acting as VNF work load.
764 All test cases using single poll mode thread.
769 All test cases using more then one poll mode driver thread.
773 All test cases with packet processing on single socket.
777 All test cases with packet processing on two sockets.
781 1 worker thread pinned to 1 dedicated physical core; or if HyperThreading is
782 enabled, 2 worker threads each pinned to a separate logical core within 1
783 dedicated physical core. Main thread pinned to core 1.
787 2 worker threads pinned to 2 dedicated physical cores; or if HyperThreading
788 is enabled, 4 worker threads each pinned to a separate logical core within 2
789 dedicated physical cores. Main thread pinned to core 1.
793 4 worker threads pinned to 4 dedicated physical cores; or if HyperThreading
794 is enabled, 8 worker threads each pinned to a separate logical core within 4
795 dedicated physical cores. Main thread pinned to core 1.
800 1 worker thread pinned to 1 dedicated physical core. 1 receive queue per
801 interface. Main thread pinned to core 1.
806 2 worker threads pinned to 2 dedicated physical cores. 1 receive queue per
807 interface. Main thread pinned to core 1.
812 4 worker threads pinned to 4 dedicated physical cores. 2 receive queues per
813 interface. Main thread pinned to core 1.
818 2 worker threads each pinned to a separate logical core within 1 dedicated
819 physical core. 1 receive queue per interface. Main thread pinned to core 1.
824 4 worker threads each pinned to a separate logical core within 2 dedicated
825 physical cores. 2 receive queues per interface. Main thread pinned to core
831 8 worker threads each pinned to a separate logical core within 4 dedicated
832 physical cores. 4 receive queues per interface. Main thread pinned to core
840 Honeycomb functional test cases.
844 Honeycomb NSH test cases.
846 .. topic:: HC_PERSIST
848 Honeycomb persistence test cases.
850 .. topic:: HC_REST_ONLY
852 (Exclusion tag) Honeycomb test cases that cannot be run in Netconf mode
853 using ODL client for Restfconf -> Netconf translation.