Adding scale up feature to prox MPLS Tagging OvS-DPDK & SRIOV
[yardstick.git] / docs / testing / user / userguide / opnfv_yardstick_tc042.rst
1 .. This work is licensed under a Creative Commons Attribution 4.0 International
2 .. License.
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, ZTE and others.
5
6 ***************************************
7 Yardstick Test Case Description TC042
8 ***************************************
9
10 .. _DPDK: http://dpdk.org/doc/guides/index.html
11 .. _Testpmd: http://dpdk.org/doc/guides/testpmd_app_ug/index.html
12 .. _Pktgen-dpdk: https://pktgen-dpdk.readthedocs.io/en/latest/index.html
13
14 +-----------------------------------------------------------------------------+
15 |Network Performance                                                          |
16 |                                                                             |
17 +--------------+--------------------------------------------------------------+
18 |test case id  | OPNFV_YARDSTICK_TC042_DPDK pktgen latency measurements       |
19 |              |                                                              |
20 +--------------+--------------------------------------------------------------+
21 |metric        | L2 Network Latency                                           |
22 |              |                                                              |
23 +--------------+--------------------------------------------------------------+
24 |test purpose  | Measure L2 network latency when DPDK is enabled between hosts|
25 |              | on different compute blades.                                 |
26 |              |                                                              |
27 +--------------+--------------------------------------------------------------+
28 |configuration | file: opnfv_yardstick_tc042.yaml                             |
29 |              |                                                              |
30 |              | * Packet size: 64 bytes                                      |
31 |              | * SLA(max_latency): 100usec                                  |
32 |              |                                                              |
33 +--------------+--------------------------------------------------------------+
34 |test tool     | DPDK_                                                        |
35 |              | Pktgen-dpdk_                                                 |
36 |              |                                                              |
37 |              | (DPDK and Pktgen-dpdk are not part of a Linux distribution,  |
38 |              | hence they needs to be installed.                            |
39 |              | As an example see the /yardstick/tools/ directory for how to |
40 |              | generate a Linux image with DPDK and pktgen-dpdk included.)  |
41 |              |                                                              |
42 +--------------+--------------------------------------------------------------+
43 |references    | DPDK_                                                        |
44 |              |                                                              |
45 |              | Pktgen-dpdk_                                                 |
46 |              |                                                              |
47 |              | ETSI-NFV-TST001                                              |
48 |              |                                                              |
49 +--------------+--------------------------------------------------------------+
50 |applicability | Test can be configured with different packet sizes. Default  |
51 |              | values exist.                                                |
52 |              |                                                              |
53 +--------------+--------------------------------------------------------------+
54 |pre-test      | The test case image needs to be installed into Glance        |
55 |conditions    | with DPDK and pktgen-dpdk included in it.                    |
56 |              |                                                              |
57 |              | The NICs of compute nodes must support DPDK on POD.          |
58 |              |                                                              |
59 |              | And at least compute nodes setup hugepage.                   |
60 |              |                                                              |
61 |              | If you want to achievement a hight performance result, it is |
62 |              | recommend to use NUAM, CPU pin, OVS and so on.               |
63 |              |                                                              |
64 +--------------+--------------------------------------------------------------+
65 |test sequence | description and expected result                              |
66 |              |                                                              |
67 +--------------+--------------------------------------------------------------+
68 |step 1        | The hosts are installed on different blades, as server and   |
69 |              | client. Both server and client have three interfaces. The    |
70 |              | first one is management such as ssh. The other two are used  |
71 |              | by DPDK.                                                     |
72 |              |                                                              |
73 +--------------+--------------------------------------------------------------+
74 |step 2        | Testpmd_ is invoked with configurations to forward packets   |
75 |              | from one DPDK port to the other on server.                   |
76 |              |                                                              |
77 +--------------+--------------------------------------------------------------+
78 |step 3        | Pktgen-dpdk is invoked with configurations as a traffic      |
79 |              | generator and logs are produced and stored on client.        |
80 |              |                                                              |
81 |              | Result: Logs are stored.                                     |
82 |              |                                                              |
83 +--------------+--------------------------------------------------------------+
84 |test verdict  | Fails only if SLA is not passed, or if there is a test case  |
85 |              | execution problem.                                           |
86 |              |                                                              |
87 +--------------+--------------------------------------------------------------+