X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=docs%2Freport%2Fintroduction%2Fgeneral_notes.rst;h=b94a82e2dc340debca4632a2f80b47793a1f55de;hb=d520749e07fe534ff278b3713cc5032368bb32fc;hp=5213a6ac42f725cb43c4bd380f13db8cc449cac3;hpb=1c66ee7e4d3c0ac6375c1c5ca15bc349d8cb3bfa;p=csit.git

diff --git a/docs/report/introduction/general_notes.rst b/docs/report/introduction/general_notes.rst
index 5213a6ac42..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,35 +23,30 @@ 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.
 
 #. **DPDK Performance** - VPP is using DPDK code to control and drive
    the NICs and physical interfaces. Tests are used as a baseline to
-   profile the DPDK sub-system of VPP. DPDK performance tests executed in
+   profile performance of the DPDK sub-system. DPDK tests are executed in
    physical FD.io testbeds, focusing on Testpmd/L3FWD data plane performance for
    Phy-to-Phy (NIC-to-NIC). Tests cover a range of NICs, 10GE and 40GE
    interfaces, range of multi-thread and multi-core configurations.
    Testpmd/L3FWD application runs in host user-mode. TRex is used as a traffic
    generator.
 
-#. **Honeycomb Performance** - Honeycomb performance tests are executed in
-   physical FD.io testbeds, focusing on the performance of Honeycomb management
-   and programming functionality of VPP. Tests cover a range of CRUD operations
-   executed against VPP.
-
 #. **VPP Functional** - VPP functional tests are executed in virtual
    FD.io testbeds focusing on VPP packet processing functionality, including
    network data plane and in -line control plane. Tests cover vNIC-to-vNIC
@@ -76,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