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 TC002
8 *************************************
10 .. _cirros-image: https://download.cirros-cloud.net
12 +-----------------------------------------------------------------------------+
15 +--------------+--------------------------------------------------------------+
16 |test case id | OPNFV_YARDSTICK_TC002_NW LATENCY |
18 +--------------+--------------------------------------------------------------+
19 |metric | RTT, Round Trip Time |
21 +--------------+--------------------------------------------------------------+
22 |test purpose | To do a basic verification that network latency is within |
23 | | acceptable boundaries when packets travel between hosts |
24 | | located on same or different compute blades. |
25 | | The purpose is also to be able to spot trends. Test results, |
26 | | graphs and 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_tc002.yaml |
33 | | Packet size 100 bytes. Total test duration 600 seconds. |
34 | | One ping each 10 seconds. SLA RTT is set to maximum 10 ms. |
36 +--------------+--------------------------------------------------------------+
39 | | Ping is normally part of any Linux distribution, hence it |
40 | | doesn't need to be installed. It is also part of the |
41 | | Yardstick Docker image. |
42 | | (For example also a Cirros image can be downloaded from |
43 | | cirros-image_, it includes ping) |
45 +--------------+--------------------------------------------------------------+
46 |references | Ping man page |
50 +--------------+--------------------------------------------------------------+
51 |applicability | Test case can be configured with different packet sizes, |
52 | | burst sizes, ping intervals and test duration. |
53 | | SLA is optional. The SLA in this test case serves as an |
54 | | example. Considerably lower RTT is expected, and |
55 | | also normal to achieve in balanced L2 environments. However, |
56 | | to cover most configurations, both bare metal and fully |
57 | | virtualized ones, this value should be possible to achieve |
58 | | and acceptable for black box testing. Many real time |
59 | | applications start to suffer badly if the RTT time is higher |
60 | | than this. Some may suffer bad also close to this RTT, while |
61 | | others may not suffer at all. It is a compromise that may |
62 | | have to be tuned for different configuration purposes. |
64 +--------------+--------------------------------------------------------------+
65 |pre-test | The test case image needs to be installed into Glance |
66 |conditions | with ping included in it. |
68 | | No POD specific requirements have been identified. |
70 +--------------+--------------------------------------------------------------+
71 |test sequence | description and expected result |
73 +--------------+--------------------------------------------------------------+
74 |step 1 | The hosts are installed, as server and client. Ping is |
75 | | invoked and logs are produced and stored. |
77 | | Result: Logs are stored. |
79 +--------------+--------------------------------------------------------------+
80 |test verdict | Test should not PASS if any RTT is above the optional SLA |
81 | | value, or if there is a test case execution problem. |
83 +--------------+--------------------------------------------------------------+