CSIT-612 Report: Minimization of hand-crafted content.

- replace dynamic text content and links by variables.

Change-Id: I1a7ec371fc80af3c9dd416bf91dd2c639097cf1e
Signed-off-by: Peter Mikus <pmikus@cisco.com>

6 files changed, 38 insertions, 37 deletions

diff --git a/docs/report/vpp_performance_tests/csit_release_notes.rst b/docs/report/vpp_performance_tests/csit_release_notes.rst
index 2c0aaf7414..a4077c13a5 100644
--- a/docs/report/vpp_performance_tests/csit_release_notes.rst
+++ b/docs/report/vpp_performance_tests/csit_release_notes.rst
@@ -48,7 +48,7 @@ Performance Improvements
 Substantial improvements in measured packet throughput have been

 observed in a number of CSIT |release| tests listed below, with relative

 increase  of double-digit percentage points. Relative improvements are

-calculated against the test results listed in CSIT rls1701 report.

+calculated against the test results listed in CSIT |release-1| report.

 VPP-16.09 numbers are provided for reference.

 

 NDR Throughput

@@ -119,7 +119,7 @@ Other Performance Changes
 Other changes in measured packet throughput, with either minor relative

 increase or decrease, have been observed in a number of CSIT |release|

 tests listed below. Relative changes are calculated against the test

-results listed in CSIT rls1701 report.

+results listed in CSIT |release-1| report.

 

 NDR Throughput

 ~~~~~~~~~~~~~~

diff --git a/docs/report/vpp_performance_tests/documentation.rst b/docs/report/vpp_performance_tests/documentation.rst
index b282c2a9b6..9f0d0a4cb3 100644
--- a/docs/report/vpp_performance_tests/documentation.rst
+++ b/docs/report/vpp_performance_tests/documentation.rst
@@ -1,6 +1,5 @@
 Documentation

 =============

 

-`CSIT VPP Performance Tests Documentation

-<https://docs.fd.io/csit/rls1704/doc/tests.perf.html>`_ contains detailed

+`CSIT VPP Performance Tests Documentation`_ contains detailed

 functional description and input parameters for each test case.

diff --git a/docs/report/vpp_performance_tests/overview.rst b/docs/report/vpp_performance_tests/overview.rst
index 3ee9b2b955..ccf8063ec2 100644
--- a/docs/report/vpp_performance_tests/overview.rst
+++ b/docs/report/vpp_performance_tests/overview.rst
@@ -194,7 +194,7 @@ Performance Tests Naming
 ------------------------
 
 CSIT |release| follows a common structured naming convention for all
-performance and system functional tests, introduced in CSIT rls1701.
+performance and system functional tests, introduced in CSIT |release-1|.
 
 The naming should be intuitive for majority of the tests. Complete
 description of CSIT test naming convention is provided on `CSIT test naming wiki
@@ -313,8 +313,8 @@ Methodology: KVM VM vhost
 -------------------------
 
 CSIT |release| introduced environment configuration changes to KVM Qemu vhost-
-user tests in order to more representatively measure VPP-17.04 performance in
-configurations with vhost-user interfaces and VMs.
+user tests in order to more representatively measure |vpp-release| performance
+in configurations with vhost-user interfaces and VMs.
 
 Current setup of CSIT FD.io performance lab is using tuned settings for more
 optimal performance of KVM Qemu:
@@ -357,7 +357,7 @@ specific configuration.
 TRex is installed and run on the TG compute node. The typical procedure is:
 
     - If the TRex is not already installed on TG, it is installed in the
-      suite setup phase - see `TRex intallation <https://gerrit.fd.io/r/gitweb?p=csit.git;a=blob;f=resources/tools/t-rex/t-rex-installer.sh;h=8090b7568327ac5f869e82664bc51b24f89f603f;hb=refs/heads/rls1704>`_.
+      suite setup phase - see `TRex intallation`_.
     - TRex configuration is set in its configuration file
       ::
 
@@ -366,7 +366,7 @@ TRex is installed and run on the TG compute node. The typical procedure is:
     - TRex is started in the background mode
       ::
 
-        sh -c 'cd /opt/trex-core-2.22/scripts/ && sudo nohup ./t-rex-64 -i -c 7 --iom 0 > /dev/null 2>&1 &' > /dev/null
+        sh -c 'cd /opt/trex-core-2.25/scripts/ && sudo nohup ./t-rex-64 -i -c 7 --iom 0 > /dev/null 2>&1 &' > /dev/null
 
     - There are traffic streams dynamically prepared for each test. The traffic
       is sent and the statistics obtained using trex_stl_lib.api.STLClient.
diff --git a/docs/report/vpp_performance_tests/packet_latency_graphs/index.rst b/docs/report/vpp_performance_tests/packet_latency_graphs/index.rst
index f71709453f..307bf3caf1 100644
--- a/docs/report/vpp_performance_tests/packet_latency_graphs/index.rst
+++ b/docs/report/vpp_performance_tests/packet_latency_graphs/index.rst
@@ -7,21 +7,20 @@ latency per test.
 
 *Title of each graph* is a regex (regular expression) matching all
 throughput test cases plotted on this graph, *X-axis labels* are indices
-of individual test suites executed by csit-vpp-perf-1704-all job that
-created result output file used as data source for the graph, *Y-axis
-labels* are measured packet Latency [uSec] values, and the *Graph
-legend* lists the plotted test suites and their indices. Latency is
-reported for concurrent symmetric bi-directional flows, separately for
-each direction: i) West-to-East: TGint1-to-SUT1-to-SUT2-to-TGint2, and
-ii) East-to-West: TGint2-to-SUT2-to-SUT1-to-TGint1.
+of individual test suites executed by
+`FD.io test executor vpp performance jobs`_ that created result output file
+used as data source for the graph, *Y-axis labels* are measured packet Latency
+[uSec] values, and the *Graph legend* lists the plotted test suites and their
+indices. Latency is reported for concurrent symmetric bi-directional flows,
+separately for each direction: i) West-to-East:
+TGint1-to-SUT1-to-SUT2-to-TGint2, and ii) East-to-West:
+TGint2-to-SUT2-to-SUT1-to-TGint1.
 
 .. note::
 
-    Test results have been generated by FD.io test executor jobs
-    `csit-vpp-perf-1704-all
-    <https://jenkins.fd.io/view/csit/job/csit-vpp-perf-1704-all/>`_,
-    with Robot Framework result files csit-vpp-perf-1704-all-6.zip
-    `archived here <../../_static/archive/>`_.
+    Test results have been generated by
+    `FD.io test executor vpp performance jobs`_ with Robot Framework result
+    files csit-vpp-perf-\*.zip `archived here <../../_static/archive/>`_.
 
 .. toctree::
 
diff --git a/docs/report/vpp_performance_tests/packet_throughput_graphs/index.rst b/docs/report/vpp_performance_tests/packet_throughput_graphs/index.rst
index d744ef09e5..c203aa1144 100644
--- a/docs/report/vpp_performance_tests/packet_throughput_graphs/index.rst
+++ b/docs/report/vpp_performance_tests/packet_throughput_graphs/index.rst
@@ -19,20 +19,20 @@ have the same value, only a horizontal line is plotted.
 
 *Title of each graph* is a regex (regular expression) matching all
 throughput test cases plotted on this graph, *X-axis labels* are indices
-of individual test suites executed by csit-vpp-perf-1704-all jobs that
-created result output files used as data sources for the graph, *Y-axis
-labels* are measured Packets Per Second [pps] values, and the *Graph
-legend* lists the plotted test suites and their indices.
+of individual test suites executed by
+`FD.io test executor vpp performance jobs`_ jobs that created result output
+files used as data sources for the graph, *Y-axis labels* are measured Packets
+Per Second [pps] values, and the *Graph legend* lists the plotted test suites
+and their indices.
+
 
 .. note::
 
-    Test results have been generated by FD.io test executor jobs
-    `csit-vpp-perf-1704-all
-    <https://jenkins.fd.io/view/csit/job/csit-vpp-perf-1704-all/>`_,
-    with Robot Framework result files csit-vpp-perf-1704-all-<id>.zip
-    `archived here <../../_static/archive/>`_. Plotted data set size per
-    test case is equal to the number of job executions presented in this
-    report version: **10**.
+    Test results have been generated by
+    `FD.io test executor vpp performance jobs`_ with Robot Framework result
+    files csit-vpp-perf-\*.zip `archived here <../../_static/archive/>`_.
+    Plotted data set size per test case is equal to the number of job executions
+    presented in this report version: **10**.
 
 .. toctree::
 
diff --git a/docs/report/vpp_performance_tests/test_environment.rst b/docs/report/vpp_performance_tests/test_environment.rst
index 7198b01173..a232650e8c 100644
--- a/docs/report/vpp_performance_tests/test_environment.rst
+++ b/docs/report/vpp_performance_tests/test_environment.rst
@@ -3497,11 +3497,11 @@ DUT Configuration - VPP
 

 **VPP Version**

 

-17.01-release_amd64

+|vpp-release|

 

 **VPP Compile Parameters**

 

-VPP Compile Job: https://jenkins.fd.io/view/vpp/job/vpp-merge-1701-ubuntu1604/

+`FD.io VPP compile job`_

 

 **VPP Install Parameters**

 

@@ -3539,6 +3539,7 @@ Tagged by **1T1C**::
         dev 0000:0a:00.0

         no-multi-seg

     }

+    heapsize 3G

     ip6 {

         hash-buckets 2000000

         heap-size 3G

@@ -3559,6 +3560,7 @@ Tagged by **2T1C**::
     cpu {

         main-core 0 corelist-workers 1,2

     }

+    heapsize 3G

     dpdk {

         socket-mem 1024,1024

         dev default {

@@ -3588,6 +3590,7 @@ Tagged by **4T4C**::
     cpu {

         main-core 0 corelist-workers 1,2,3,4

     }

+    heapsize 3G

     dpdk {

         socket-mem 1024,1024

         dev default {

@@ -3608,7 +3611,7 @@ TG Configuration - TRex
 

 **TG Version**

 

-TRex v2.22

+|trex-release|

 

 **DPDK version**

 

@@ -3616,7 +3619,7 @@ DPDK v17.02 (f4decdc59e9323ecff5ddb5de7ebf0c79d50a960 - in DPDK repo)
 

 **TG Build Script used**

 

-https://gerrit.fd.io/r/gitweb?p=csit.git;a=blob;f=resources/tools/t-rex/t-rex-installer.sh;h=8090b7568327ac5f869e82664bc51b24f89f603f;hb=refs/heads/rls1704

+`TRex intallation`_

 

 **TG Startup Configuration**

 

@@ -3634,4 +3637,4 @@ https://gerrit.fd.io/r/gitweb?p=csit.git;a=blob;f=resources/tools/t-rex/t-rex-in
 

 **TG common API - pointer to driver**

 

-https://gerrit.fd.io/r/gitweb?p=csit.git;a=blob;f=resources/tools/t-rex/t-rex-stateless.py;h=ae8d18767013ebecb0bec6c732ac66e483408661;hb=refs/heads/rls1704

+`TRex driver`_