aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report/introduction/general_notes.rst
diff options
context:
space:
mode:
authorPeter Mikus <pmikus@cisco.com>2017-07-03 20:19:11 +0200
committerPeter Mikus <pmikus@cisco.com>2017-07-04 13:51:27 +0000
commit785519e26196b9e0a5016d0fc54ed099fd0a920f (patch)
tree1235a2c16c17f5534f3aa0d3574ca96a8a57f00b /docs/report/introduction/general_notes.rst
parentd166ae0881c29dfd05ed61b9a12156f17981bb6d (diff)
CSIT-702 Update static content after optimizations
Update the mechanics of script for generating report to reflect the latest changes. Update some static content. Change-Id: If60f7b74245138cc3044a49c46ff06d5850732de 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.rst25
1 files changed, 15 insertions, 10 deletions
diff --git a/docs/report/introduction/general_notes.rst b/docs/report/introduction/general_notes.rst
index 5015b6bb16..d96dc00101 100644
--- a/docs/report/introduction/general_notes.rst
+++ b/docs/report/introduction/general_notes.rst
@@ -3,10 +3,10 @@ General Notes
All CSIT test results listed in this report are sourced and auto-generated
from output.xml Robot Framework (RF) files resulting from LF FD.io Jenkins
-jobs execution against VPP-17.04 release artifacts. References are provided
-to the original LF FD.io Jenkins job results. However, as LF 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
+jobs execution against |vpp-release| release artifacts. References are
+provided to the original LF FD.io Jenkins job results. However, as LF 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 RF result files that got archived in FD.io nexus online
storage system.
@@ -21,13 +21,14 @@ is listed separately, as follows:
interfaces, range of multi-thread and multi-core configurations. VPP
application runs in host user- mode. TRex is used as a traffic generator.
-#. **Testpmd Performance Tests** - VPP is using DPDK code to control and drive
+#. **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
- profile the DPDK sub-system of VPP. Testpmd performance tests executed in
- physical FD.io testbeds, focusing on Testpmd 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 application runs
- in host user-mode. TRex is used as a traffic generator.
+ 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
+ interfaces, range of multi-thread and multi-core configurations.
+ 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
FD.io testbeds focusing on VPP packet processing functionality, including
@@ -40,6 +41,10 @@ is listed separately, as follows:
functionality of VPP. Tests cover a range of CRUD operations executed
against VPP.
+#. **TLDK Tests** - TODO
+
+#. **NSH_SFC Tests** - TODO
+
In addition to above, CSIT |release| report does also include VPP unit test
results. VPP unit tests are developed within the FD.io VPP project and as they
complement CSIT system functional tests, they are provided mainly as a reference