X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=docs%2Freport%2Fintroduction%2Ftest_scenarios_overview.rst;h=ee334a6407c1f9e50d6be32095c1e2b9e7679596;hb=b659ab3d2638652de0357d29be1ec7704df97555;hp=8b7266d0a4ca78a7174f5e96deeb7aaee6814bbc;hpb=e253cf226e1595acecf42db1262e1cb179aae5e7;p=csit.git diff --git a/docs/report/introduction/test_scenarios_overview.rst b/docs/report/introduction/test_scenarios_overview.rst index 8b7266d0a4..ee334a6407 100644 --- a/docs/report/introduction/test_scenarios_overview.rst +++ b/docs/report/introduction/test_scenarios_overview.rst @@ -1,14 +1,13 @@ -Test Scenarios Overview -======================= +Test Scenarios +============== -FD.io CSIT report includes multiple test scenarios of a number of VPP +FD.io |csit-release| report includes multiple test scenarios of VPP centric applications, topologies and use cases. In addition it also -covers baseline tests of DPDK sample applications. Tests are executed -executed in physical (performance tests) and virtual environments -(functional tests). +covers baseline tests of DPDK sample applications. Tests are executed in +physical (performance tests) and virtual environments (functional +tests). -Following list provides a brief overview of test scenarios covered in -this report: +Brief overview of test scenarios covered in this report: #. **VPP Performance**: VPP performance tests are executed in physical FD.io testbeds, focusing on VPP network data plane performance in @@ -36,12 +35,6 @@ this report: run across a range of configurations. TRex is used as a traffic generator. -#. **K8s Container/Pod Topologies Performance**: VPP container - performance tests using memif for interconnecting VPP-in- - Container/Pod instances orchestrated by K8s integrated with `Ligato - `_ for container networking. TRex is - used as a traffic generator. - #. **DPDK Performance**: VPP uses DPDK to drive the NICs and physical interfaces. DPDK performance tests are used as a baseline to profile performance of the DPDK sub-system. Two DPDK applications @@ -61,22 +54,25 @@ this report: programming functionality of VPP. Tests cover a range of CRUD operations executed against VPP. -#. **NSH_SFC Functional**: NSH_SFC functional tests are executed in - virtual FD.io testbeds focusing on VPP nsh-plugin data plane - functionality. Scapy is used as a traffic generator. - -#. **DMM Functional**: DMM functional tests are executed in virtual - FD.io testbeds demonstrating a single server (DUT1) and single - client (DUT2) scenario using DMM framework and Linux kernel TCP/IP - stack. +.. + #. **DMM Functional**: DMM functional tests are executed in virtual + FD.io testbeds demonstrating a single server (DUT1) and single + client (DUT2) scenario using DMM framework and Linux kernel TCP/IP + stack. + #. **K8s Container/Pod Topologies Performance**: VPP container + performance tests using memif for interconnecting VPP-in- + Container/Pod instances orchestrated by K8s integrated with `Ligato + `_ for container networking. TRex is + used as a traffic generator. + #. **NSH_SFC Functional**: NSH_SFC functional tests are executed in + virtual FD.io testbeds focusing on VPP nsh-plugin data plane + functionality. Scapy is used as a traffic generator. -All CSIT test results listed in this report are sourced and auto- +All CSIT test data included in this report is auto- generated from :abbr:`RF (Robot Framework)` :file:`output.xml` files -resulting from :abbr:`LF (Linux Foundation)` FD.io Jenkins jobs executed -against |vpp-release| release artifacts. References are provided to the -original 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. +produced by :abbr:`LF (Linux Foundation)` FD.io Jenkins jobs executed +against |vpp-release| artifacts. References are provided to the +original FD.io Jenkins job results and all archived source files. FD.io CSIT system is developed using two main coding platforms: :abbr:`RF (Robot Framework)` and Python2.7. |csit-release| source code for the executed test