1 .. This work is licensed under a Creative Commons Attribution 4.0 International
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, Ericsson AB and others.
6 *************************************
7 Yardstick Test Case Description TC001
8 *************************************
10 .. _pktgen: https://www.kernel.org/doc/Documentation/networking/pktgen.txt
12 +-----------------------------------------------------------------------------+
13 |Network Performance |
15 +--------------+--------------------------------------------------------------+
16 |test case id | OPNFV_YARDSTICK_TC001_NW PERF |
18 +--------------+--------------------------------------------------------------+
19 |metric | Number of flows and throughput |
21 +--------------+--------------------------------------------------------------+
22 |test purpose | To evaluate the IaaS network performance with regards to |
23 | | flows and throughput, such as if and how different amounts |
24 | | of flows matter for the throughput between hosts on |
25 | | different compute blades. Typically e.g. the performance of |
26 | | a vSwitch depends on the number of flows running through it. |
27 | | Also performance of other equipment or entities can depend |
28 | | on the number of flows or the packet sizes used. |
29 | | The purpose is also to be able to spot trends. Test results, |
30 | | graphs ans similar shall be stored for comparison reasons |
31 | | and product evolution understanding between different OPNFV |
32 | | versions and/or configurations. |
34 +--------------+--------------------------------------------------------------+
35 |configuration | file: opnfv_yardstick_tc001.yaml |
37 | | Packet size: 60 bytes |
38 | | Number of ports: 10, 50, 100, 500 and 1000, where each |
39 | | runs for 20 seconds. The whole sequence is run |
40 | | twice. The client and server are distributed on different |
42 | | For SLA max_ppm is set to 1000. The amount of configured |
43 | | ports map to between 110 up to 1001000 flows, respectively. |
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 +--------------+--------------------------------------------------------------+