================\r
\r
CSIT functional tests are currently executed in FD.IO VIRL testbed. The physical\r
-VIRL testbed infrastructure consists of three identical VIRL hosts:\r
+VIRL testbed infrastructure consists of three VIRL hosts:\r
\r
- All hosts are Cisco UCS C240-M4 (2x Intel(R) Xeon(R) CPU E5-2699 v3 @2.30GHz,\r
18c, 512GB RAM)\r
-- Hosts run Ubuntu 14.04.3\r
-- VIRL software versions:\r
\r
- - STD server version 0.10.24.7\r
- - UWM server version 0.10.24.7\r
+- tb4-virl1:\r
+\r
+ - Status: Production\r
+ - OS: Ubuntu 16.04.2\r
+ - STD server version 0.10.32.16\r
+ - UWM server version 0.10.32.16\r
+\r
+- tb4-virl2:\r
+\r
+ - Status: Production\r
+ - OS: Ubuntu 16.04.2\r
+ - STD server version 0.10.32.16\r
+ - UWM server version 0.10.32.16\r
+\r
+- tb4-virl3:\r
+\r
+ - Status: Testing\r
+ - OS: Ubuntu 16.04.2\r
+ - STD server version 0.10.32.19\r
+ - UWM server version 0.10.32.19\r
\r
Whenever a patch is submitted to gerrit for review, parallel VIRL simulations\r
are started to reduce the time of execution of all functional tests. The number\r
of parallel VIRL simulations is equal to number of test groups defined by\r
-TEST_GROUPS variable in csit/bootstrap.sh file. The VIRL host to run VIRL\r
-simulation is selected randomly per VIRL simulation.\r
+TEST_GROUPS variable in :file:`csit/bootstrap.sh` file. The VIRL host to run\r
+VIRL simulation is selected based on least load algorithm per VIRL simulation.\r
\r
Every VIRL simulation uses the same three-node - Traffic Generator (TG node) and\r
two Systems Under Test (SUT1 and SUT2) - "double-ring" topology. The appropriate\r
pre-built VPP packages built by Jenkins for the patch under review are then\r
-installed on the two SUTs, along with their /etc/vpp/startup.conf file, in all\r
-VIRL simulations.\r
+installed on the two SUTs, along with their :file:`/etc/vpp/startup.conf` file,\r
+in all VIRL simulations.\r
\r
SUT Configuration - VIRL Guest VM\r
---------------------------------\r
\r
-Configuration of the SUT VMs is defined in file\r
+Configurations of the SUT VMs is defined in `VIRL topologies directory`_\r
\r
- /csit/resources/tools/virl/topologies/double-ring-nested.xenial.virl\r
- \r
- List of SUT VM interfaces:::\r
\r
<interface id="0" name="GigabitEthernet0/4/0"/>\r
<interface id="1" name="GigabitEthernet0/5/0"/>\r
<interface id="2" name="GigabitEthernet0/6/0"/>\r
<interface id="3" name="GigabitEthernet0/7/0"/>\r
- \r
+\r
- Number of 2MB hugepages: 1024\r
\r
- Maximum number of memory map areas: 20000\r
SUT Configuration - VIRL Guest OS Linux\r
---------------------------------------\r
\r
-In CSIT terminology, the VM operating system for both SUTs that VPP 17.01 has\r
+In CSIT terminology, the VM operating system for both SUTs that |vpp-release| has\r
been tested with, is the following:\r
\r
-**#. ubuntu-16.04.1_2016-12-19_1.6**\r
-\r
-This image implies Ubuntu 16.04.1 LTS, current as of 2016/12/19 (that is,\r
-package versions are those that would have been installed by a "apt-get update",\r
-"apt-get upgrade" on December 19), produced by CSIT disk image build scripts\r
-version 1.6.\r
+#. **Ubuntu VIRL image**\r
\r
-The exact list of installed packages and their versions (including the Linux\r
-kernel package version) are included in CSIT source repository:\r
+ This image implies Ubuntu 16.04.1 LTS, current as of yyyy-mm-dd (that is,\r
+ package versions are those that would have been installed by a\r
+ :command:`apt-get update`, :command:`apt-get upgrade` on that day), produced\r
+ by CSIT disk image build scripts.\r
\r
- resources/tools/disk-image-builder/ubuntu/lists/ubuntu-16.04.1_2016-12-19_1.6\r
+ The exact list of installed packages and their versions (including the Linux\r
+ kernel package version) are included in `VIRL ubuntu images lists`_.\r
\r
-A replica of this VM image can be built by running the "build.sh" script in CSIT\r
-repository resources/tools/disk-image-builder/ubuntu.\r
+ A replica of this VM image can be built by running the :command:`build.sh`\r
+ script in CSIT repository.\r
\r
-**#. centos-7.3-1611_2017-01-24_1.2**\r
+#. **CentOS VIRL image**\r
\r
-The Centos7.3 image is ready to be used but no tests running on it now.\r
-Corresponding Jenkins jobs are under preparation.\r
+ This image implies Centos 7.4-1711, current as of yyyy-mm-dd (that is,\r
+ package versions are those that would have been installed by a\r
+ :command:`yum update`, :command:`yum upgrade` on that day), produced\r
+ by CSIT disk image build scripts.\r
\r
-The exact list of installed packages and their versions (including the Linux\r
-kernel package version) are included in CSIT source repository:\r
+ The exact list of installed packages and their versions (including the Linux\r
+ kernel package version) are included in `VIRL centos images lists`_.\r
\r
- resources/tools/disk-image-builder/ubuntu/lists/centos-7.3-1611_2017-01-24_1.2\r
+ A replica of this VM image can be built by running the :command:`build.sh`\r
+ script in CSIT repository.\r
\r
-A replica of this VM image can be built by running the "build.sh" script in CSIT\r
-repository resources/tools/disk-image-builder/centos.\r
+#. **Nested VM image**\r
\r
-**#. Nested VM image**\r
+ In addition to the "main" VM image, tests which require VPP to communicate to\r
+ a VM over a vhost-user interface, utilize a "nested" VM image.\r
\r
-In addition to the "main" VM image, tests which require VPP to communicate to a\r
-VM over a vhost-user interface, utilize a "nested" VM image.\r
-\r
-This "nested" VM is dynamically created and destroyed as part of a test case,\r
-and therefore the "nested" VM image is optimized to be small, lightweight and\r
-have a short boot time. The "nested" VM image is not built around any\r
-established Linux distribution, but is based on BuildRoot\r
-(https://buildroot.org/), a tool for building embedded Linux systems. Just as\r
-for the "main" image, scripts to produce an identical replica of the "nested"\r
-image are included in CSIT GIT repository, and the image can be rebuilt using\r
-the "build.sh" script at:\r
-\r
- resources/tools/disk-image-builder/ubuntu/lists/nested\r
+ This "nested" VM is dynamically created and destroyed as part of a test case,\r
+ and therefore the "nested" VM image is optimized to be small, lightweight and\r
+ have a short boot time. The "nested" VM image is not built around any\r
+ established Linux distribution, but is based on `BuildRoot\r
+ <https://buildroot.org/>`_, a tool for building embedded Linux systems. Just\r
+ as for the "main" image, scripts to produce an identical replica of the\r
+ "nested" image are included in CSIT GIT repository, and the image can be\r
+ rebuilt using the "build.sh" script at `VIRL nested`_.\r
\r
DUT Configuration - VPP\r
-----------------------\r
**DUT port configuration**\r
\r
Port configuration of DUTs is defined in topology file that is generated per\r
-VIRL simulation based on the definition stored in file\r
+VIRL simulation based on the definition stored in `VIRL topologies directory`_.\r
\r
- /csit/resources/tools/virl/topologies/double-ring-nested.xenial.yaml\r
- \r
Example of DUT nodes configuration:::\r
\r
DUT1:\r
EqrzZXl7ACUuo1dH0Eipm41j2+BZWlQjiUgq5uj8+yzy+EU1ZRRyJcOKzbDACeuD\r
BpWWSXGBI5G4CppeYLjMUHZpJYeX1USULJQd2c4crLJKb76E8gz3Z9kN\r
-----END RSA PRIVATE KEY-----\r
- \r
+\r
interfaces:\r
port1:\r
mac_address: "fa:16:3e:9b:89:52"\r
EqrzZXl7ACUuo1dH0Eipm41j2+BZWlQjiUgq5uj8+yzy+EU1ZRRyJcOKzbDACeuD\r
BpWWSXGBI5G4CppeYLjMUHZpJYeX1USULJQd2c4crLJKb76E8gz3Z9kN\r
-----END RSA PRIVATE KEY-----\r
- \r
+\r
interfaces:\r
port1:\r
mac_address: "fa:16:3e:ad:6c:7d"\r
\r
**VPP Version**\r
\r
-17.01-release_amd64\r
+|vpp-release|\r
\r
-**VPP Installed Packages**\r
+**VPP Installed Packages - Ubuntu**\r
::\r
\r
$ dpkg -l vpp\*\r
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend\r
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)\r
||/ Name Version Architecture Description\r
- +++-==============-=============-============-=============================================\r
- ii vpp 17.01-release amd64 Vector Packet Processing--executables\r
- ii vpp-dbg 17.01-release amd64 Vector Packet Processing--debug symbols\r
- ii vpp-dev 17.01-release amd64 Vector Packet Processing--development support\r
- ii vpp-dpdk-dev 17.01-release amd64 Vector Packet Processing--development support\r
- ii vpp-dpdk-dkms 17.01-release amd64 DPDK 2.1 igb_uio_driver\r
- ii vpp-lib 17.01-release amd64 Vector Packet Processing--runtime libraries\r
- ii vpp-plugins 17.01-release amd64 Vector Packet Processing--runtime plugins\r
+ +++-==============-=============-============-=================================================\r
+ ii vpp 18.04-release amd64 Vector Packet Processing--executables\r
+ ii vpp-dbg 18.04-release amd64 Vector Packet Processing--debug symbols\r
+ ii vpp-dev 18.04-release amd64 Vector Packet Processing--development support\r
+ ii vpp-dpdk-dkms 18.02-vpp1 amd64 DPDK Development Package for VPP - Kernel Modules\r
+ ii vpp-lib 18.04-release amd64 Vector Packet Processing--runtime libraries\r
+ ii vpp-plugins 18.04-release amd64 Vector Packet Processing--runtime plugins\r
+\r
+**VPP Installed Packages - Centos**\r
+::\r
+\r
+ $ rpm -qai vpp*\r
+ Name : vpp\r
+ Version : 18.04\r
+ Release : release\r
+ Architecture: x86_64\r
+ Install Date: Fri 04 May 2018 02:47:36 AM EDT\r
+ Group : Unspecified\r
+ Size : 2311324\r
+ License : ASL 2.0\r
+ Signature : (none)\r
+ Source RPM : vpp-18.04-release.src.rpm\r
+ Build Date : Wed 25 Apr 2018 01:00:24 PM EDT\r
+ Build Host : c29a51c12e88\r
+ Relocations : (not relocatable)\r
+ Summary : Vector Packet Processing\r
+ Description :\r
+ This package provides VPP executables: vpp, vpp_api_test, vpp_json_test\r
+ vpp - the vector packet engine\r
+ vpp_api_test - vector packet engine API test tool\r
+ vpp_json_test - vector packet engine JSON test tool\r
+ Name : vpp-lib\r
+ Version : 18.04\r
+ Release : release\r
+ Architecture: x86_64\r
+ Install Date: Fri 04 May 2018 02:47:36 AM EDT\r
+ Group : System Environment/Libraries\r
+ Size : 24949034\r
+ License : ASL 2.0\r
+ Signature : (none)\r
+ Source RPM : vpp-18.04-release.src.rpm\r
+ Build Date : Wed 25 Apr 2018 01:00:24 PM EDT\r
+ Build Host : c29a51c12e88\r
+ Relocations : (not relocatable)\r
+ Summary : VPP libraries\r
+ Description :\r
+ This package contains the VPP shared libraries, including:\r
+ vppinfra - foundation library supporting vectors, hashes, bitmaps, pools, and string formatting.\r
+ svm - vm library\r
+ vlib - vector processing library\r
+ vlib-api - binary API library\r
+ vnet - network stack library\r
+ Name : vpp-selinux-policy\r
+ Version : 18.04\r
+ Release : release\r
+ Architecture: x86_64\r
+ Install Date: Fri 04 May 2018 02:47:35 AM EDT\r
+ Group : System Environment/Base\r
+ Size : 86170\r
+ License : ASL 2.0\r
+ Signature : (none)\r
+ Source RPM : vpp-18.04-release.src.rpm\r
+ Build Date : Wed 25 Apr 2018 01:00:24 PM EDT\r
+ Build Host : c29a51c12e88\r
+ Relocations : (not relocatable)\r
+ Summary : VPP Security-Enhanced Linux (SELinux) policy\r
+ Description :\r
+ This package contains a tailored VPP SELinux policy\r
+ Name : vpp-devel\r
+ Version : 18.04\r
+ Release : release\r
+ Architecture: x86_64\r
+ Install Date: Fri 04 May 2018 02:47:38 AM EDT\r
+ Group : Development/Libraries\r
+ Size : 10632218\r
+ License : ASL 2.0\r
+ Signature : (none)\r
+ Source RPM : vpp-18.04-release.src.rpm\r
+ Build Date : Wed 25 Apr 2018 01:00:24 PM EDT\r
+ Build Host : c29a51c12e88\r
+ Relocations : (not relocatable)\r
+ Summary : VPP header files, static libraries\r
+ Description :\r
+ This package contains the header files for VPP.\r
+ Install this package if you want to write a\r
+ program for compilation and linking with vpp lib.\r
+ vlib\r
+ vlibmemory\r
+ vnet - devices, classify, dhcp, ethernet flow, gre, ip, etc.\r
+ vpp-api\r
+ vppinfra\r
+ Name : vpp-plugins\r
+ Version : 18.04\r
+ Release : release\r
+ Architecture: x86_64\r
+ Install Date: Fri 04 May 2018 02:47:37 AM EDT\r
+ Group : System Environment/Libraries\r
+ Size : 44145968\r
+ License : ASL 2.0\r
+ Signature : (none)\r
+ Source RPM : vpp-18.04-release.src.rpm\r
+ Build Date : Wed 25 Apr 2018 01:00:24 PM EDT\r
+ Build Host : c29a51c12e88\r
+ Relocations : (not relocatable)\r
+ Summary : Vector Packet Processing--runtime plugins\r
+ Description :\r
+ This package contains VPP plugins\r
\r
**VPP Startup Configuration**\r
\r
-VPP startup configuration is common for all test cases.\r
+VPP startup configuration is common for all test cases except test cases related\r
+to SW Crypto device.\r
+\r
+**Default**\r
+\r
::\r
\r
$ cat /etc/vpp/startup.conf\r
unix {\r
nodaemon\r
- log /tmp/vpp.log\r
+ log /var/log/vpp/vpp.log\r
full-coredump\r
+ cli-listen /run/vpp/cli.sock\r
+ gid vpp\r
}\r
- \r
+\r
api-trace {\r
+ ## This stanza controls binary API tracing. Unless there is a very strong reason,\r
+ ## please leave this feature enabled.\r
on\r
+ ## Additional parameters:\r
+ ##\r
+ ## To set the number of binary API trace records in the circular buffer, configure nitems\r
+ ##\r
+ ## nitems <nnn>\r
+ ##\r
+ ## To save the api message table decode tables, configure a filename. Results in /tmp/<filename>\r
+ ## Very handy for understanding api message changes between versions, identifying missing\r
+ ## plugins, and so forth.\r
+ ##\r
+ ## save-api-table <filename>\r
}\r
- \r
+\r
api-segment {\r
gid vpp\r
}\r
- \r
+\r
cpu {\r
## In the VPP there is one main thread and optionally the user can create worker(s)\r
## The main thread and worker thread(s) can be pinned to CPU core(s) manually or automatically\r
- \r
+\r
## Manual pinning of thread(s) to CPU core(s)\r
- \r
+\r
## Set logical CPU core where main thread runs\r
# main-core 1\r
- \r
+\r
## Set logical CPU core(s) where worker threads are running\r
# corelist-workers 2-3,18-19\r
- \r
+\r
## Automatic pinning of thread(s) to CPU core(s)\r
- \r
+\r
## Sets number of CPU core(s) to be skipped (1 ... N-1)\r
## Skipped CPU core(s) are not used for pinning main thread and working thread(s).\r
## The main thread is automatically pinned to the first available CPU core and worker(s)\r
## are pinned to next free CPU core(s) after core assigned to main thread\r
# skip-cores 4\r
- \r
+\r
## Specify a number of workers to be created\r
## Workers are pinned to N consecutive CPU cores while skipping "skip-cores" CPU core(s)\r
## and main thread's CPU core\r
# workers 2\r
- \r
+\r
## Set scheduling policy and priority of main and worker threads\r
- \r
+\r
## Scheduling policy options are: other (SCHED_OTHER), batch (SCHED_BATCH)\r
## idle (SCHED_IDLE), fifo (SCHED_FIFO), rr (SCHED_RR)\r
# scheduler-policy fifo\r
- \r
+\r
## Scheduling priority is used only for "real-time policies (fifo and rr),\r
## and has to be in the range of priorities supported for a particular policy\r
# scheduler-priority 50\r
}\r
- \r
- dpdk {\r
+\r
+ # dpdk {\r
## Change default settings for all intefaces\r
# dev default {\r
## Number of receive queues, enables RSS\r
## Default is 1\r
# num-rx-queues 3\r
- \r
+\r
## Number of transmit queues, Default is equal\r
## to number of worker threads or 1 if no workers treads\r
# num-tx-queues 3\r
- \r
+\r
## Number of descriptors in transmit and receive rings\r
## increasing or reducing number can impact performance\r
## Default is 1024 for both rx and tx\r
# num-rx-desc 512\r
# num-tx-desc 512\r
- \r
+\r
## VLAN strip offload mode for interface\r
## Default is off\r
# vlan-strip-offload on\r
# }\r
- \r
+\r
## Whitelist specific interface by specifying PCI address\r
# dev 0000:02:00.0\r
- \r
+\r
## Whitelist specific interface by specifying PCI address and in\r
## addition specify custom parameters for this interface\r
# dev 0000:02:00.1 {\r
# num-rx-queues 2\r
# }\r
- \r
- ## Change UIO driver used by VPP, Options are: uio_pci_generic, vfio-pci\r
- ## and igb_uio (default)\r
- # uio-driver uio_pci_generic\r
- \r
+\r
+ ## Specify bonded interface and its slaves via PCI addresses\r
+ ##\r
+ ## Bonded interface in XOR load balance mode (mode 2) with L3 and L4 headers\r
+ # vdev eth_bond0,mode=2,slave=0000:02:00.0,slave=0000:03:00.0,xmit_policy=l34\r
+ # vdev eth_bond1,mode=2,slave=0000:02:00.1,slave=0000:03:00.1,xmit_policy=l34\r
+ ##\r
+ ## Bonded interface in Active-Back up mode (mode 1)\r
+ # vdev eth_bond0,mode=1,slave=0000:02:00.0,slave=0000:03:00.0\r
+ # vdev eth_bond1,mode=1,slave=0000:02:00.1,slave=0000:03:00.1\r
+\r
+ ## Change UIO driver used by VPP, Options are: igb_uio, vfio-pci,\r
+ ## uio_pci_generic or auto (default)\r
+ # uio-driver vfio-pci\r
+\r
## Disable mutli-segment buffers, improves performance but\r
## disables Jumbo MTU support\r
# no-multi-seg\r
- \r
+\r
## Increase number of buffers allocated, needed only in scenarios with\r
## large number of interfaces and worker threads. Value is per CPU socket.\r
- ## Default is 32768\r
+ ## Default is 16384\r
# num-mbufs 128000\r
- \r
+\r
## Change hugepages allocation per-socket, needed only if there is need for\r
## larger number of mbufs. Default is 256M on each detected CPU socket\r
# socket-mem 2048,2048\r
+\r
+ ## Disables UDP / TCP TX checksum offload. Typically needed for use\r
+ ## faster vector PMDs (together with no-multi-seg)\r
+ # no-tx-checksum-offload\r
+ # }\r
+\r
+\r
+ # plugins {\r
+ ## Adjusting the plugin path depending on where the VPP plugins are\r
+ # path /home/bms/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins\r
+\r
+ ## Disable all plugins by default and then selectively enable specific plugins\r
+ # plugin default { disable }\r
+ # plugin dpdk_plugin.so { enable }\r
+ # plugin acl_plugin.so { enable }\r
+\r
+ ## Enable all plugins by default and then selectively disable specific plugins\r
+ # plugin dpdk_plugin.so { disable }\r
+ # plugin acl_plugin.so { disable }\r
+ # }\r
+\r
+ ## Alternate syntax to choose plugin path\r
+ # plugin_path /home/bms/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins\r
+\r
+**SW Crypto Device**\r
+\r
+::\r
+\r
+ $ cat /etc/vpp/startup.conf\r
+ unix\r
+ {\r
+ cli-listen /run/vpp/cli.sock\r
+ gid vpp\r
+ nodaemon\r
+ full-coredump\r
+ log /tmp/vpp.log\r
+ }\r
+ api-segment\r
+ {\r
+ gid vpp\r
+ }\r
+ dpdk\r
+ {\r
+ vdev cryptodev_aesni_gcm_pmd,socket_id=0\r
+ vdev cryptodev_aesni_mb_pmd,socket_id=0\r
}\r
\r
TG Configuration\r
\r
**TG VM configuration**\r
\r
-Configuration of the TG VMs is defined in file\r
+Configuration of the TG VMs is defined in `VIRL topologies directory`_.\r
\r
/csit/resources/tools/virl/topologies/double-ring-nested.xenial.virl\r
- \r
+\r
- List of TG VM interfaces:::\r
\r
<interface id="0" name="eth1"/>\r
**TG node port configuration**\r
\r
Port configuration of TG is defined in topology file that is generated per VIRL\r
-simulation based on the definition stored in file\r
-\r
- /csit/resources/tools/virl/topologies/double-ring-nested.xenial.yaml\r
+simulation based on the definition stored in `VIRL topologies directory`_.\r
\r
Example of TG node configuration:::\r
\r
EqrzZXl7ACUuo1dH0Eipm41j2+BZWlQjiUgq5uj8+yzy+EU1ZRRyJcOKzbDACeuD\r
BpWWSXGBI5G4CppeYLjMUHZpJYeX1USULJQd2c4crLJKb76E8gz3Z9kN\r
-----END RSA PRIVATE KEY-----\r
- \r
+\r
interfaces:\r
port3:\r
mac_address: "fa:16:3e:b9:e1:27"\r
**Traffic generator**\r
\r
Functional tests utilize Scapy as a traffic generator. There was used Scapy\r
-v2.3.1 for VPP 17.01 tests.\r
+v2.3.1 for |vpp-release| tests.\r
\r
Code Review / csit.git / blobdiff