7 CSIT VPP Device tests are executed in Physical containerized topologies
8 created on demand using set of scripts hosted and developed under CSIT
9 repository. It runs on physical baremetal servers hosted by LF FD.io project.
10 Based on the packet path thru SUT Containers, three distinct logical topology
11 types are used for VPP DUT data plane testing:
13 #. vfNIC-to-vfNIC switching topologies.
14 #. vfNIC-to-vhost-user switching topologies.
15 #. vfNIC-to-memif switching topologies.
17 vfNIC-to-vfNIC Switching
18 ~~~~~~~~~~~~~~~~~~~~~~~~
20 The simplest physical topology for software data plane application like
21 VPP is vfNIC-to-vfNIC switching. Tested virtual topologies for 2-Node testbeds
22 are shown in figures below.
30 \graphicspath{{../_tmp/src/vpp_device_tests/}}
31 \includegraphics[width=0.90\textwidth]{vf-2n-nic2nic}
32 \label{fig:vf-2n-nic2nic}
37 .. figure:: ../vpp_device_tests/vf-2n-nic2nic.svg
41 SUT1 is Docker Container (running Ubuntu, depending on the test suite), TG is
42 a Traffic Generator (running Ubuntu Container). SUTs run VPP
43 SW application in Linux user-mode as a Device Under Test (DUT) within
44 the container. TG runs Scapy SW application as a packet Traffic Generator.
45 Network connectivity between SUTs and to TG is provided using virtual function
48 Virtual topologies are created on-demand whenever a verification job is
49 started (e.g. triggered by the gerrit patch submission) and destroyed
50 upon completion of all functional tests. Each node is a container running on
51 physical server. During the test execution, all nodes are reachable thru
52 the Management (not shown above for clarity).
54 vfNIC-to-vhost-user Switching
55 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
57 vfNIC-to-vhost-user switching topology test cases require VPP DUT to communicate
58 with Virtual Machine (VM) over Vhost-user virtual interfaces. VM is created on
59 SUT1 for the duration of these particular test cases only. Virtual test topology
60 with VM is shown in the figure below.
68 \graphicspath{{../_tmp/src/vpp_device_tests/}}
69 \includegraphics[width=0.90\textwidth]{vf-2n-nic2vhost}
70 \label{fig:vf-2n-nic2vhost}
75 .. figure:: ../vpp_device_tests/vf-2n-nic2vhost.svg
79 vfNIC-to-memif Switching
80 ~~~~~~~~~~~~~~~~~~~~~~~~
82 vfNIC-to-memif switching topology test cases require VPP DUT to communicate
83 with another Docker Container over memif interfaces. Container is created for
84 the duration of these particular test cases only and it is running the same VPP
85 version as running on DUT. Virtual test topology with Memif is shown in
94 \graphicspath{{../_tmp/src/vpp_device_tests/}}
95 \includegraphics[width=0.90\textwidth]{vf-2n-nic2memif}
96 \label{fig:vf-2n-nic2memif}
101 .. figure:: ../vpp_device_tests/vf-2n-nic2memif.svg
102 :alt: vf-2n-nic2memif
105 Functional Tests Coverage
106 -------------------------
108 |csit-release| includes following VPP functionality tested in VPP Device
111 +-----------------------+----------------------------------------------+
112 | Functionality | Description |
113 +=======================+==============================================+
114 | IPv4 | IPv4 routing, ICMPv4. |
115 +-----------------------+----------------------------------------------+
116 | IPv6 | IPv4 routing, ICMPv6. |
117 +-----------------------+----------------------------------------------+
118 | L2BD | L2 Bridge-Domain switching for untagged |
120 +-----------------------+----------------------------------------------+
121 | L2XC | L2 Cross-Connect switching for untagged |
123 +-----------------------+----------------------------------------------+
124 | Vhost-user Interface | Baseline VPP vhost-user interface tests. |
125 +-----------------------+----------------------------------------------+
126 | Memif Interface | Baseline VPP memif interface tests. |
127 +-----------------------+----------------------------------------------+
132 |csit-release| follows a common structured naming convention for all
133 performance and system functional tests, introduced in CSIT-17.01.
135 The naming should be intuitive for majority of the tests. Complete
136 description of CSIT test naming convention is provided on
137 :ref:`csit_test_naming`.