1 *************************************
2 Yardstick Test Case Description TC008
3 *************************************
5 .. _pktgen: https://www.kernel.org/doc/Documentation/networking/pktgen.txt
7 +-----------------------------------------------------------------------------+
8 |Packet Loss Extended Test |
10 +--------------+--------------------------------------------------------------+
11 |test case id | OPNFV_YARDSTICK_TC008_NW PERF, Packet loss Extended Test |
13 +--------------+--------------------------------------------------------------+
14 |metric | Number of flows, packet size and throughput |
16 +--------------+--------------------------------------------------------------+
17 |test purpose | To evaluate the IaaS network performance with regards to |
18 | | flows and throughput, such as if and how different amounts |
19 | | of packet sizes and flows matter for the throughput between |
20 | | VMs on different compute blades. Typically e.g. the |
21 | | performance of a vSwitch |
22 | | depends on the number of flows running through it. Also |
23 | | performance of other equipment or entities can depend |
24 | | on the number of flows or the packet sizes used. |
25 | | The purpose is also to be able to spot trends. Test results, |
26 | | graphs ans similar shall be stored for comparison reasons and|
27 | | product evolution understanding between different OPNFV |
28 | | versions and/or configurations. |
30 +--------------+--------------------------------------------------------------+
31 |configuration | file: opnfv_yardstick_tc008.yaml |
33 | | Packet size: 64, 128, 256, 512, 1024, 1280 and 1518 bytes. |
35 | | Number of ports: 1, 10, 50, 100, 500 and 1000. The amount of |
36 | | configured ports map from 2 up to 1001000 flows, |
37 | | respectively. Each packet_size/port_amount combination is run|
38 | | ten times, for 20 seconds each. Then the next |
39 | | packet_size/port_amount combination is run, and so on. |
41 | | The client and server are distributed on different HW. |
43 | | For SLA max_ppm is set to 1000. |
45 +--------------+--------------------------------------------------------------+
48 | | (Pktgen is not always part of a Linux distribution, hence it |
49 | | needs to be installed. It is part of the Yardstick Docker |
51 | | As an example see the /yardstick/tools/ directory for how |
52 | | to generate a Linux image with pktgen included.) |
54 +--------------+--------------------------------------------------------------+
55 |references | pktgen_ |
59 +--------------+--------------------------------------------------------------+
60 |applicability | Test can be configured with different packet sizes, amount |
61 | | of flows and test duration. Default values exist. |
63 | | SLA (optional): max_ppm: The number of packets per million |
64 | | packets sent that are acceptable to loose, not received. |
66 +--------------+--------------------------------------------------------------+
67 |pre-test | The test case image needs to be installed into Glance |
68 |conditions | with pktgen included in it. |
70 | | No POD specific requirements have been identified. |
72 +--------------+--------------------------------------------------------------+
73 |test sequence | description and expected result |
75 +--------------+--------------------------------------------------------------+
76 |step 1 | The hosts are installed, as server and client. pktgen is |
77 | | invoked and logs are produced and stored. |
79 | | Result: Logs are stored. |
81 +--------------+--------------------------------------------------------------+
82 |test verdict | Fails only if SLA is not passed, or if there is a test case |
83 | | execution problem. |
85 +--------------+--------------------------------------------------------------+