diff options
author | Peter Mikus <pmikus@cisco.com> | 2018-04-24 13:36:20 +0200 |
---|---|---|
committer | Peter Mikus <pmikus@cisco.com> | 2018-04-26 04:42:05 +0000 |
commit | 1261ada9edd22c784a7763d861c5acf87ccd1ae1 (patch) | |
tree | fcc489ab2d802c970b5abc404fd14809480dcfec /docs/report/introduction/general_notes.rst | |
parent | a1728c4f56cc44b9acb45614c20fc0a546ee3161 (diff) |
Update report content
- Update report content to match with rls1804 and master
Change-Id: Ib50df2482635f07c94ba92f0ed766bd95bc8e52c
Signed-off-by: Peter Mikus <pmikus@cisco.com>
Diffstat (limited to 'docs/report/introduction/general_notes.rst')
-rw-r--r-- | docs/report/introduction/general_notes.rst | 26 |
1 files changed, 12 insertions, 14 deletions
diff --git a/docs/report/introduction/general_notes.rst b/docs/report/introduction/general_notes.rst index b51ed159c5..b94a82e2dc 100644 --- a/docs/report/introduction/general_notes.rst +++ b/docs/report/introduction/general_notes.rst @@ -5,11 +5,9 @@ All CSIT test results listed in this report are sourced and auto-generated from :file:`output.xml` :abbr:`RF (Robot Framework)` files resulting from :abbr:`LF (Linux Foundation)` FD.io Jenkins jobs execution against |vpp-release| release artifacts. References are provided to the original :abbr:`LF (Linux -Foundation)` FD.io Jenkins job results. However, as :abbr:`LF (Linux -Foundation)` FD.io Jenkins infrastructure does not automatically archive all jobs -(history record is provided for the last 30 days or 40 jobs only), additional -references are provided to the :abbr:`RF (Robot Framework)` result files that -got archived in FD.io nexus online storage system. +Foundation)` FD.io Jenkins job results. Additional references are provided to +the :abbr:`RF (Robot Framework)` result files that got archived in FD.io nexus +online storage system. FD.io CSIT project currently covers multiple FD.io system and sub-system testing areas and this is reflected in this report, where each testing area @@ -25,18 +23,18 @@ is listed separately, as follows: #. **LXC and Docker Containers VPP memif - Performance** - VPP memif virtual interface tests interconnect multiple VPP instances running in containers. VPP vswitch instance runs in bare-metal user-mode - handling Intel x520 NIC 10GbE interfaces and connecting over memif - (Master side) virtual interfaces to more instances of VPP running in - LXC or in Docker Containers, both with memif virtual interfaces (Slave - side). Tested across a range of multi-thread and multi-core - configurations. TRex is used as a traffic generator. + handling Intel x520 NIC 10GbE, Intel x710 NIC 10GbE, Intel xl710 NIC 40GbE + interfaces and connecting over memif (Slave side) virtual interfaces to more + instances of VPP running in LXC or in Docker Containers, both with memif + virtual interfaces (Master side). Tested across a range of multi-thread and + multi-core configurations. TRex is used as a traffic generator. #. **Container Topologies Orchestrated by K8s - Performance** - CSIT Container topologies connected over the memif virtual interface (shared memory interface). For these tests VPP vswitch instance runs in a Docker Container - handling Intel x520 NIC 10GbE interfaces and connecting over memif (Master - side) virtual interfaces to more instances of VPP running in Docker - Containers with memif virtual interfaces (Slave side). All containers are + handling Intel x520 NIC 10GbE, Intel x710 NIC 10GbE interfaces and connecting + over memif virtual interfaces to more instances of VPP running in Docker + Containers with memif virtual interfaces. All containers are orchestrated by Kubernetes, with `Ligato <https://github.com/ligato>`_ for container networking. TRex is used as a traffic generator. @@ -71,7 +69,7 @@ and to provide a more complete view of automated testing executed against |vpp-release|. FD.io CSIT system is developed using two main coding platforms :abbr:`RF (Robot -Framework)` and Python. CSIT |release| source code for the executed test +Framework)` and Python2.7. CSIT |release| source code for the executed test suites is available in CSIT branch |release| in the directory :file:`./tests/<name_of_the_test_suite>`. A local copy of CSIT source code can be obtained by cloning CSIT git repository - :command:`git clone |