Add a document describing vIPSEC testcase

Create a test case description file for NSB vIPSEC

JIRA: YARDSTICK-1450

Change-Id: Iebaca9535e0ebc9f597d8e3c82c4339637eb3180
Signed-off-by: treyad <treyad@viosoft.com>
(cherry picked from commit ebd3b805b14a3f85c8db8b8ca9cd619abf0cde25)

2 files changed, 114 insertions, 0 deletions

diff --git a/docs/testing/user/userguide/nsb/nsb-list-of-tcs.rst b/docs/testing/user/userguide/nsb/nsb-list-of-tcs.rst
index 6c18c7d89..a578216da 100644
--- a/docs/testing/user/userguide/nsb/nsb-list-of-tcs.rst
+++ b/docs/testing/user/userguide/nsb/nsb-list-of-tcs.rst
@@ -36,3 +36,4 @@ NSB PROX Test Case Descriptions
    tc_vfw_rfc2544
    tc_vfw_rfc2544_correlated
    tc_vfw_rfc3511
+   tc_vpp_baremetal_crypto_ipsec
diff --git a/docs/testing/user/userguide/nsb/tc_vpp_baremetal_crypto_ipsec.rst b/docs/testing/user/userguide/nsb/tc_vpp_baremetal_crypto_ipsec.rst
new file mode 100644
index 000000000..6a4a37697
--- /dev/null
+++ b/docs/testing/user/userguide/nsb/tc_vpp_baremetal_crypto_ipsec.rst
@@ -0,0 +1,113 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International
+.. License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) OPNFV, 2019 Viosoft Corporation.
+
+***********************************************
+Yardstick Test Case Description: NSB VPP IPSEC
+***********************************************
+
++------------------------------------------------------------------------------+
+|NSB VPP test for vIPSEC characterization                                      |
+|                                                                              |
++--------------+---------------------------------------------------------------+
+|test case id  | tc_baremetal_rfc2544_ipv4_{crypto_dev}_{crypto_alg}           |
+|              |                                                               |
+|              | * crypto_dev = HW_cryptodev or SW_cryptodev;                  |
+|              | * crypto_alg = aes-gcm or cbc-sha1;                           |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|metric        | * Network Throughput NDR or PDR;                              |
+|              | * Connections Per Second (CPS);                               |
+|              | * Latency;                                                    |
+|              | * Number of tunnels;                                          |
+|              | * TG Packets Out;                                             |
+|              | * TG Packets In;                                              |
+|              | * VNF Packets Out;                                            |
+|              | * VNF Packets In;                                             |
+|              | * Dropped packets;                                            |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|test purpose  | IPv4 IPsec tunnel mode performance test:                      |
+|              |                                                               |
+|              | * Finds and reports throughput NDR (Non Drop Rate) with zero  |
+|              |   packet loss tolerance or throughput PDR (Partial Drop Rate) |
+|              |   with non-zero packet loss tolerance (LT) expressed in       |
+|              |   number of packets transmitted.                              |
+|              |                                                               |
+|              | * The IPSEC test cases are implemented to run in baremetal    |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|configuration | The IPSEC test cases are listed below:                        |
+|              |                                                               |
+|              | * tc_baremetal_rfc2544_ipv4_hw_aesgcm_IMIX_trex.yaml          |
+|              | * tc_baremetal_rfc2544_ipv4_hw_aesgcm_trex.yaml               |
+|              | * tc_baremetal_rfc2544_ipv4_hw_cbcsha1_IMIX_trex.yaml         |
+|              | * tc_baremetal_rfc2544_ipv4_hw_cbcsha1_trex.yaml              |
+|              | * tc_baremetal_rfc2544_ipv4_sw_aesgcm_IMIX_trex.yaml          |
+|              | * tc_baremetal_rfc2544_ipv4_sw_aesgcm_trex.yaml               |
+|              | * tc_baremetal_rfc2544_ipv4_sw_cbcsha1_IMIX_trex.yaml         |
+|              | * tc_baremetal_rfc2544_ipv4_sw_cbcsha1_trex.yaml              |
+|              |                                                               |
+|              | Test duration is set as 500sec for each test.                 |
+|              | Packet size set as 64 bytes or higher.                        |
+|              | Number of tunnels set as 1 or higher.                         |
+|              | Number of connections set as 1 or higher                      |
+|              | These can be configured                                       |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|test tool     | Vector Packet Processing (VPP)                                |
+|              | The VPP platform is an extensible framework that provides     |
+|              | out-of-the-box production quality switch/router functionality.|
+|              | Its high performance, proven technology, its modularity and,  |
+|              | flexibility and rich feature set                              |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|applicability | This VPP IPSEC test cases can be configured with different:   |
+|              |                                                               |
+|              | * packet sizes;                                               |
+|              | * test durations;                                             |
+|              | * tolerated loss;                                             |
+|              | * crypto device type;                                         |
+|              | * number of physical cores;                                   |
+|              | * number of tunnels;                                          |
+|              | * number of connections;                                      |
+|              | * encryption algorithms - integrity algorithm;                |
+|              |                                                               |
+|              | Default values exist.                                         |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|pre-test      | For Baremetal tests cases VPP and DPDK must be installed in   |
+|conditions    | the hosts where the test is executed. The pod.yaml file must  |
+|              | have the necessary system and NIC information                 |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|test sequence | description and expected result                               |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|step 1        | For Baremetal test: The TG and VNF are started on the hosts   |
+|              | based on the pod file.                                        |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|step 2        | Yardstick is connected with the TG and VNF by using ssh.      |
+|              | The test will resolve the topology and instantiate the VNF    |
+|              | and TG and collect the KPI's/metrics.                         |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|step 3        | Test packets are generated by TG on links to DUTs. If the     |
+|              | number of dropped packets is more than the tolerated loss     |
+|              | the line rate or throughput is halved. This is done until     |
+|              | the dropped packets are within an acceptable tolerated loss.  |
+|              |                                                               |
+|              | The KPI is the number of packets per second for a packet size |
+|              | specified in the test case with an accepted minimal packet    |
+|              | loss for the default configuration.                           |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|step 4        | In Baremetal test: The test quits the application and unbind  |
+|              | the DPDK ports.                                               |
+|              |                                                               |
++--------------+---------------------------------------------------------------+
+|test verdict  | The test case will achieve a Throughput with an accepted      |
+|              | minimal tolerated packet loss.                                |
++--------------+---------------------------------------------------------------+
\ No newline at end of file