dpdk_performance_tests/test_environment
dpdk_performance_tests/documentation
+.. toctree::
+ :maxdepth: 2
+ :caption: VPP Device
+
+ vpp_device_tests/overview
+ vpp_device_tests/csit_release_notes
+ vpp_device_tests/test_environment
+ vpp_device_tests/documentation
+
.. toctree::
:maxdepth: 2
:caption: VPP Functional
introduction/index
vpp_performance_tests/index
dpdk_performance_tests/index
+ vpp_device_tests/index
vpp_functional_tests/index
honeycomb_functional_tests/index
nsh_sfc_functional_tests/index
::
$ cat /proc/cmdline
- BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=efb7e8b3-3548-4440-98f6-6ebe102e9ec6 ro isolcpus=1-17,19-35 nohz_full=1-17,19-35 rcu_nocbs=1-17,19-35 intel_pstate=disable console=tty0 console=ttyS0,115200n8
+ BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=UUID=5d2ecc97-245b-4e94-b0ae-c3548567de19 ro isolcpus=1-17,19-35 nohz_full=1-17,19-35 rcu_nocbs=1-17,19-35 numa_balancing=disable intel_pstate=disable intel_iommu=on iommu=pt nmi_watchdog=0 audit=0 nosoftlockup processor.max_cstate=1 intel_idle.max_cstate=1 hpet=disable tsc=reliable mce=off console=tty0 console=ttyS0,115200n8
Linux uname
::
$ uname -a
- Linux t3-sut2 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
+ Linux t1-tg1 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
System-level core jitter
Reader Numa Node
Writer Numa Node 0 1
0 - 107.7
- 1 106.6 -
\ No newline at end of file
+ 1 106.6 -
Below a subset of the running configuration:
-1. Xeon Haswell - Ubuntu 16.04.1 LTS
+1. Xeon Haswell - Ubuntu 18.04.1 LTS
::
$ lsb_release -a
No LSB modules are available.
- Distributor ID: Ubuntu
- Description: Ubuntu 16.04.1 LTS
- Release: 16.04
- Codename: xenial
+ Distributor ID: Ubuntu
+ Description: Ubuntu 18.04.1 LTS
+ Release: 18.04
+ Codename: bionic
+
2. Xeon Skylake - Ubuntu 18.04 LTS
Applied Boot Cmdline
~~~~~~~~~~~~~~~~~~~~
-1. Xeon Haswell - Ubuntu 16.04.1 LTS
+1. Xeon Haswell - Ubuntu 18.04.1 LTS
::
$ cat /proc/cmdline
- BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=35ea11e4-e44f-4f67-8cbe-12f09c49ed90 ro isolcpus=1-17,19-35 nohz_full=1-17,19-35 rcu_nocbs=1-17,19-35 intel_pstate=disable console=tty0 console=ttyS0,115200n8
+ BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=UUID=5d2ecc97-245b-4e94-b0ae-c3548567de19 ro isolcpus=1-17,19-35 nohz_full=1-17,19-35 rcu_nocbs=1-17,19-35 numa_balancing=disable intel_pstate=disable intel_iommu=on iommu=pt nmi_watchdog=0 audit=0 nosoftlockup processor.max_cstate=1 intel_idle.max_cstate=1 hpet=disable tsc=reliable mce=off console=tty0 console=ttyS0,115200n8
2. Xeon Skylake - Ubuntu 18.04 LTS
-Host IRQ Affinity
-~~~~~~~~~~~~~~~~~
-
-IRQs are pinned to core 0. The same configuration is applied in host Linux and guest VM.
-
-::
-
- $ for l in `ls /proc/irq`; do echo 1 | sudo tee /proc/irq/$l/smp_affinity; done
-
-Host RCU Affinity
-~~~~~~~~~~~~~~~~~
-
-RCUs are pinned to core 0. The same configuration is applied in host Linux and guest VM.
-
-::
-
- $ for i in `pgrep rcu[^c]` ; do sudo taskset -pc 0 $i ; done
-
Host Writeback Affinity
~~~~~~~~~~~~~~~~~~~~~~~
- CVE-2018-3646 [L1 terminal fault] aka 'Foreshadow-NG (VMM)'
::
+
$ sudo ./spectre-meltdown-checker.sh --no-color
Spectre and Meltdown mitigation detection tool v0.40
- CVE-2018-3646 [L1 terminal fault] aka 'Foreshadow-NG (VMM)'
::
+
$ sudo ./spectre-meltdown-checker.sh --no-color
Spectre and Meltdown mitigation detection tool v0.40
--- /dev/null
+Release Notes
+=============
+
+Changes in |csit-release|
+-------------------------
+
+#. Initial release
+
+Known Issues
+------------
+
+List of known issues in |csit-release| for VPP functional tests in VIRL:
+
++---+----------------------------------------+---------------------+
+| # | JiraID | Issue Description |
++===+========================================+=====================+
+| 1 | | |
++---+----------------------------------------+---------------------+
--- /dev/null
+Documentation
+=============
+
+`CSIT VPP Device Tests Documentation`_ contains detailed
+functional description and input parameters for each test case.
+
--- /dev/null
+VPP Device
+==========
+
+.. toctree::
+
+ overview
+ csit_release_notes
+ test_environment
+ documentation
--- /dev/null
+Overview
+========
+
+Virtual Topologies
+------------------
+
+CSIT VPP Device tests are executed in Physical containerized topologies
+created on demand using set of scripts hosted and developed under CSIT
+repository. It runs on physical baremetal servers hosted by LF FD.io project.
+Based on the packet path thru SUT Containers, two distinct logical topology
+types are used for VPP DUT data plane testing:
+
+#. vfNIC-to-vfNIC switching topologies.
+#. Nested-VM service switching topologies. (Planned to be added in rls1901)
+
+vfNIC-to-vfNIC Switching
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+The simplest physical topology for software data plane application like
+VPP is vfNIC-to-vfNIC switching. Tested virtual topologies for 2-Node testbeds
+are shown in figures below.
+
+.. only:: latex
+
+ .. raw:: latex
+
+ \begin{figure}[H]
+ \centering
+ \graphicspath{{../_tmp/src/vpp_device_tests/}}
+ \includegraphics[width=0.90\textwidth]{vf-2n-nic2nic}
+ \label{fig:vf-2n-nic2nic}
+ \end{figure}
+
+.. only:: html
+
+ .. figure:: ../vpp_device_tests/vf-2n-nic2nic.svg
+ :alt: vf-2n-nic2nic
+ :align: center
+
+SUT1 is Docker Container (running Ubuntu, depending on the test suite), TG is
+a Traffic Generator (running Ubuntu Container). SUTs run VPP
+SW application in Linux user-mode as a Device Under Test (DUT) within
+the container. TG runs Scapy SW application as a packet Traffic Generator.
+Network connectivity between SUTs and to TG is provided using virtual function
+of physical NICs.
+
+Virtual topologies are created on-demand whenever a verification job is
+started (e.g. triggered by the gerrit patch submission) and destroyed
+upon completion of all functional tests. Each node is a container running on
+physical server. During the test execution, all nodes are reachable thru
+the Management (not shown above for clarity).
+
+Functional Tests Coverage
+-------------------------
+
+|csit-release| includes following VPP functionality tested in virtual VM
+environment:
+
++-----------------------+----------------------------------------------+
+| Functionality | Description |
++=======================+==============================================+
+| IPv4 | ICMPv4. |
++-----------------------+----------------------------------------------+
+| IPv6 | ICMPv6. |
++-----------------------+----------------------------------------------+
+
+Tests Naming
+------------
+
+|csit-release| follows a common structured naming convention for all
+performance and system functional tests, introduced in CSIT-17.01.
+
+The naming should be intuitive for majority of the tests. Complete
+description of CSIT test naming convention is provided on
+:ref:`csit_test_naming`.
--- /dev/null
+
+.. include:: ../../vpp-device.rst
+++ /dev/null
----
-# file: group_vars/haswell/sut.yaml
-
-isolcpus: "1-17,19-35"
+++ /dev/null
----
-# file: group_vars/skylake/sut.yaml
-
-isolcpus: "1-27,29-55,57-83,85-111"
+++ /dev/null
----
-# file: vppdevice.yaml
-
-- hosts: vppdevice
- remote_user: testuser
- become: yes
- become_user: root
- roles:
- - common
- - vppdevice
Code Review / csit.git / commitdiff