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

diff --git a/docs/report/introduction/general_notes.rst b/docs/report/introduction/general_notes.rst
index 50a9d4c4a3..5213a6ac42 100644
--- a/docs/report/introduction/general_notes.rst
+++ b/docs/report/introduction/general_notes.rst
@@ -12,18 +12,36 @@ 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
+testing areas and this is reflected in this report, where each testing area
 is listed separately, as follows:
 
-#. **VPP Performance Tests** - VPP performance tests are executed in physical
+#. **VPP - Performance** - VPP benchmarking tests are executed in physical
    FD.io testbeds, focusing on VPP network data plane performance at this stage,
    both for Phy-to-Phy (NIC-to-NIC) and Phy-to-VM-to-Phy (NIC-to-VM-to-NIC)
    forwarding topologies. Tested across a range of NICs, 10GE and 40GE
    interfaces, range of multi-thread and multi-core configurations. VPP
-   application runs in host user- mode. TRex is used as a traffic generator.
+   application runs in host user-mode. TRex is used as a traffic generator.
 
-#. **DPDK Performance Tests** - VPP is using DPDK code to control and drive
-   the NICs and physical interfaces. Testpmd tests are used as a baseline to
+#. **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.
+
+#. **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
+   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
    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
@@ -31,23 +49,23 @@ is listed separately, as follows:
    Testpmd/L3FWD application runs in host user-mode. TRex is used as a traffic
    generator.
 
-#. **VPP Functional Tests** - VPP functional tests are executed in virtual
+#. **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
    vNIC-to-VM-to-vNIC forwarding topologies. Scapy is used as a traffic
    generator.
 
-#. **Honeycomb Functional Tests** - Honeycomb functional tests are executed in
+#. **Honeycomb Functional** - Honeycomb functional tests are executed in
    virtual FD.io testbeds, focusing on Honeycomb management and programming
    functionality of VPP. Tests cover a range of CRUD operations executed
    against VPP.
 
-#. **Honeycomb Performance Tests** - 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.
-
-#. **NSH_SFC Functional Tests** - NSH_SFC functional tests are executed in
+#. **NSH_SFC Functional** - NSH_SFC functional tests are executed in
    virtual FD.io testbeds focusing on NSH_SFC of VPP. Tests cover a range of
    CRUD operations executed against VPP.