Introduce reconfig suites, for dot1q+ip4+vxlan

Ticket: CSIT-1551

+ Config copied from other suites.
+ Layer keywords prepared for additional chains.
+ Renamed "create" argument to "vlan_per_chain".
+ TrafficGenerator result extraction improvements.
 + Also unified TG type and subtype checking.
+ Throughput estimated as PDR for zero PLR.
+ Actual Qemu start is skipped.
+ Parse xstats instead of stats in trex stop scipt.
 - Because stats are unconditionally cleared on each script connect.
+ Remember start values to get better ReceiveMeasurementResult at stop.
+ Expose loss count and time as appropriate test message.
+ Autogen support.
+ Multiple chain amounts and core densities.
 - Only 1 additional chain.
+ Proper TAGs. Documented.
 + Clarified min framesize tags are for TG-DUT.
  + Added a TODO concerning overhead values.
 + Added 118B tag.
+ Robot performance keywords improvements.
 + Added missing return value documentation.
 + Frame size as required test variable, not an explicit argument.
 + MLRsearch keyword to store result (not into test message).
  - TODO: De-duplicate: main keyword to measure, minor to set test message.
   - But implementation uses the fact default arguments are different.
 + Keywords for starting and stopping background traffic.
  - No checks whether start-stop pair is complete.
+ Multiple minor indentation and logging improvements.
- Missing / TODOs:
 - Support also vlan_per_chain=True?
 - Support dot1q without vxlan?
 - Support also deletion?
 - How to package config steps so -reconf can be generated from -ndrpdr?

Change-Id: If0270697f9ffa837c34ef802917220a53f156703
Signed-off-by: Vratko Polak <vrpolak@cisco.com>

1 files changed, 32 insertions, 14 deletions

diff --git a/docs/tag_documentation.rst b/docs/tag_documentation.rst
index b28fd89c6f..5c68858bfa 100644
--- a/docs/tag_documentation.rst
+++ b/docs/tag_documentation.rst
@@ -220,20 +220,33 @@ Performance Type Tags
 
     Performance tests using PLRsearch to find the critical load.
 
+.. topic:: RECONF
+
+    Performance tests aimed to measure lost packets (time) when performing
+    reconfiguration while full throughput offered load is applied.
+
 Ethernet Frame Size Tags
 ------------------------
 
+These are describing the traffic offered by Traffic Generator,
+"primary" traffic in case of asymmetric load.
+For traffic between DUTs, or for "secondary" traffic, see ${overhead} value.
+
 .. topic:: 64B
 
-    64B frames used for test.
+    64B frames used for test. Generic ethernet or IPv4.
 
 .. topic:: 78B
 
-    78B frames used for test.
+    78B frames used for test. Ipv6.
 
 .. topic:: 114B
 
-    114B frames used for test.
+    114B frames used for test. IPv4+vxlan.
+
+.. topic:: 118B
+
+    118B frames used for test. Dot1q+IPv4+vxlan.
 
 .. topic:: IMIX
 
@@ -337,35 +350,40 @@ NF Service Density Tags
 
 .. topic:: CHAIN
 
-   NF service density tests with VNF or CNF service chain topology(ies).
+    NF service density tests with VNF or CNF service chain topology(ies).
 
 .. topic:: PIPE
 
-   NF service density tests with CNF service pipeline topology(ies).
+    NF service density tests with CNF service pipeline topology(ies).
 
 .. topic:: NF_L3FWDIP4
 
-   NF service density tests with DPDK l3fwd IPv4 routing as NF workload.
+    NF service density tests with DPDK l3fwd IPv4 routing as NF workload.
 
 .. topic:: NF_VPPIP4
 
-   NF service density tests with VPP IPv4 routing as NF workload.
+    NF service density tests with VPP IPv4 routing as NF workload.
 
 .. topic:: {r}R{c}C
 
-   Service density matrix locator {r}R{c}C, {r}Row denoting number of
-   service instances, {c}Column denoting number of NFs per service
-   instance. {r}=(1,2,4,6,8,10), {c}=(1,2,4,6,8,10).
+    Service density matrix locator {r}R{c}C, {r}Row denoting number of
+    service instances, {c}Column denoting number of NFs per service
+    instance. {r}=(1,2,4,6,8,10), {c}=(1,2,4,6,8,10).
 
 .. topic:: {n}VM{t}T
 
-   Service density {n}VM{t}T, {n}Number of NF Qemu VMs, {t}Number of threads
-   per NF.
+    Service density {n}VM{t}T, {n}Number of NF Qemu VMs, {t}Number of threads
+    per NF.
 
 .. topic:: {n}DCRt}T
 
-   Service density {n}DCR{t}T, {n}Number of NF Docker containers, {t}Number of
-   threads per NF.
+    Service density {n}DCR{t}T, {n}Number of NF Docker containers, {t}Number of
+    threads per NF.
+
+.. topic:: {n}_ADDED_CHAINS
+
+    {n}Number of chains (or pipelines) added (and/or removed)
+    during RECONF test.
 
 Forwarding Mode Tags
 --------------------