Add test case description and modify task file for TC042

JIRA:YARDSTICK-233

Change-Id: I5fd879ceae7ec2bfaf75db50bdc0e8d3a1ec1f88
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>

diff --git a/docs/userguide/03-list-of-tcs.rst b/docs/userguide/03-list-of-tcs.rst
index 85846d1..4f986cd 100644 (file)
--- a/docs/userguide/03-list-of-tcs.rst
+++ b/docs/userguide/03-list-of-tcs.rst
@@ -39,6 +39,7 @@ Generic NFVI Test Case Descriptions
    opnfv_yardstick_tc024.rst
    opnfv_yardstick_tc037.rst
    opnfv_yardstick_tc038.rst
+   opnfv_yardstick_tc042.rst
    opnfv_yardstick_tc043.rst
    opnfv_yardstick_tc044.rst
    opnfv_yardstick_tc055.rst

diff --git a/docs/userguide/opnfv_yardstick_tc042.rst b/docs/userguide/opnfv_yardstick_tc042.rst
new file mode 100644 (file)
index 0000000..8660d92
--- /dev/null
+++ b/docs/userguide/opnfv_yardstick_tc042.rst
@@ -0,0 +1,87 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International
+.. License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) OPNFV, ZTE and others.
+
+***************************************
+Yardstick Test Case Description TC0042
+***************************************
+
+.. _DPDK: http://dpdk.org/doc/guides/index.html
+.. _Testpmd: http://dpdk.org/doc/guides/testpmd_app_ug/index.html
+.. _Pktgen-dpdk: http://pktgen.readthedocs.io/en/latest/index.html
+
++-----------------------------------------------------------------------------+
+|Network Performance                                                          |
+|                                                                             |
++--------------+--------------------------------------------------------------+
+|test case id  | OPNFV_YARDSTICK_TC042_DPDK pktgen latency measurements       |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|metric        | L2 Network Latency                                           |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|test purpose  | Measure L2 network latency when DPDK is enabled between hosts|
+|              | on different compute blades.                                 |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|configuration | file: opnfv_yardstick_tc042.yaml                             |
+|              |                                                              |
+|              | * Packet size: 64 bytes                                      |
+|              | * SLA(max_latency): 100usec                                  |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|test tool     | DPDK_                                                        |
+|              | Pktgen-dpdk_                                                 |
+|              |                                                              |
+|              | (DPDK and Pktgen-dpdk are not part of a Linux distribution,  |
+|              | hence they needs to be installed.                            |
+|              | As an example see the /yardstick/tools/ directory for how to |
+|              | generate a Linux image with DPDK and pktgen-dpdk included.)  |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|references    | DPDK_                                                        |
+|              |                                                              |
+|              | Pktgen-dpdk_                                                 |
+|              |                                                              |
+|              | ETSI-NFV-TST001                                              |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|applicability | Test can be configured with different packet sizes. Default  |
+|              | values exist.                                                |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|pre-test      | The test case image needs to be installed into Glance        |
+|conditions    | with DPDK and pktgen-dpdk included in it.                    |
+|              |                                                              |
+|              | The NICs of compute nodes must support DPDK on POD.          |
+|              |                                                              |
+|              | And at least compute nodes setup hugepage.                   |
+|              |                                                              |
+|              | If you want to achievement a hight performance result, it is |
+|              | recommend to use NUAM, CPU pin, OVS and so on.               |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|test sequence | description and expected result                              |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|step 1        | The hosts are installed on different blades, as server and   |
+|              | client. Both server and client have three interfaces. The    |
+|              | first one is management such as ssh. The other two are used  |
+|              | by DPDK.                                                     |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|step 2        | Testpmd_ is invoked with configurations to forward packets   |
+|              | from one DPDK port to the other on server.                   |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|step 3        | Pktgen-dpdk is invoked with configurations as a traffic      |
+|              | generator and logs are produced and stored on client.        |
+|              |                                                              |
+|              | Result: Logs are stored.                                     |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|test verdict  | Fails only if SLA is not passed, or if there is a test case  |
+|              | execution problem.                                           |
+|              |                                                              |
++--------------+--------------------------------------------------------------+

diff --git a/tests/opnfv/test_cases/opnfv_yardstick_tc042.yaml b/tests/opnfv/test_cases/opnfv_yardstick_tc042.yaml
index a47f71a..158f507 100644 (file)
--- a/tests/opnfv/test_cases/opnfv_yardstick_tc042.yaml
+++ b/tests/opnfv/test_cases/opnfv_yardstick_tc042.yaml
@@ -10,22 +10,21 @@ scenarios:
   options:
     packetsize: 64
     rate: 100
-    duration: 20
 
-  host: demeter.yardstick
-  target: poseidon.yardstick
+  host: demeter.yardstick-TC042
+  target: poseidon.yardstick-TC042
 
   runner:
     type: Iteration
-    iterations: 2
+    iterations: 1
     interval: 1
 
   sla:
-    max_rtt: 1000
+    max_latency: 100
     action: monitor
 
 context:
-  name: yardstick
+  name: yardstick-TC042
   image: yardstick-image-pktgen-ready
   flavor: yardstick-pktgen-dpdk.flavor
   user: ubuntu