4 FD.io |csit-release| report includes multiple test scenarios of VPP
5 centric applications, topologies and use cases. In addition it also
6 covers baseline tests of DPDK sample applications. Tests are executed in
7 physical (performance tests) and virtual environments (functional
10 Brief overview of test scenarios covered in this report:
12 #. **VPP Performance**: VPP performance tests are executed in physical
13 FD.io testbeds, focusing on VPP network data plane performance in
14 NIC-to-NIC switching topologies. Tested across Intel Cascadelake
15 and Skylake servers, ARM, Denverton, range of NICs (10GE, 25GE, 40GE, 100GE)
16 and multi-thread/multi-core configurations. VPP application runs in
17 bare-metal host user-mode handling NICs. TRex is used as a traffic generator.
19 #. **VPP Vhostuser Performance with KVM VMs**: VPP VM service switching
20 performance tests using vhostuser virtual interface for
21 interconnecting multiple NF-in-VM instances. VPP vswitch
22 instance runs in bare-metal user-mode handling NICs and connecting
23 over vhost-user interfaces to VM instances each running VPP with virtio
24 virtual interfaces. Similarly to VPP Performance, tests are run across a
25 range of configurations. TRex is used as a traffic generator.
27 #. **VPP Memif Performance with LXC and Docker Containers**: VPP
28 Container service switching performance tests using memif virtual
29 interface for interconnecting multiple VPP-in-container instances.
30 VPP vswitch instance runs in bare-metal user-mode handling NICs and
31 connecting over memif (Slave side) interfaces to more instances of
32 VPP running in LXC or in Docker Containers, both with memif
33 interfaces (Master side). Similarly to VPP Performance, tests are
34 run across a range of configurations. TRex is used as a traffic
37 #. **DPDK Performance**: VPP uses DPDK to drive the NICs and physical
38 interfaces. DPDK performance tests are used as a baseline to
39 profile performance of the DPDK sub-system. Two DPDK applications
40 are tested: Testpmd and L3fwd. DPDK tests are executed in the same
41 testing environment as VPP tests. DPDK Testpmd and L3fwd
42 applications run in host user-mode. TRex is used as a traffic
45 #. **VPP Functional**: VPP functional tests are executed in virtual
46 FD.io testbeds, focusing on VPP packet processing functionality,
47 including both network data plane and in-line control plane. Tests
48 cover vNIC-to-vNIC vNIC-to-nestedVM-to-vNIC forwarding topologies.
49 Scapy is used as a traffic generator.
51 All CSIT test data included in this report is auto-
52 generated from :abbr:`RF (Robot Framework)` :file:`output.xml` files
53 produced by :abbr:`LF (Linux Foundation)` FD.io Jenkins jobs executed
54 against |vpp-release| artifacts. References are provided to the
55 original FD.io Jenkins job results and all archived source files.
57 FD.io CSIT system is developed using two main coding platforms: :abbr:`RF (Robot
58 Framework)` and Python. |csit-release| source code for the executed test
59 suites is available in CSIT branch |release| in the directory
60 :file:`./tests/<name_of_the_test_suite>`. A local copy of CSIT source code
61 can be obtained by cloning CSIT git repository - :command:`git clone
62 https://gerrit.fd.io/r/csit`.