1 .. This work is licensed under a Creative Commons Attribution 4.0 International
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, Huawei Technologies Co.,Ltd and others.
6 *************************************
7 Yardstick Test Case Description TC043
8 *************************************
10 .. _cirros-image: https://download.cirros-cloud.net
12 +-----------------------------------------------------------------------------+
13 |Network Latency Between NFVI Nodes |
15 +--------------+--------------------------------------------------------------+
16 |test case id | OPNFV_YARDSTICK_TC043_Latency_between_ |
17 | | NFVI_nodes_measurements |
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 different |
26 +--------------+--------------------------------------------------------------+
27 |configuration | file: opnfv_yardstick_tc043.yaml |
29 | | Packet size 100 bytes. Total test duration 600 seconds. |
30 | | One ping each 10 seconds. SLA RTT is set to maximum 10 ms. |
32 +--------------+--------------------------------------------------------------+
35 | | Ping is normally part of any Linux distribution, hence it |
36 | | doesn't need to be installed. It is also part of the |
37 | | Yardstick Docker image. |
39 +--------------+--------------------------------------------------------------+
40 |references | Ping man page |
44 +--------------+--------------------------------------------------------------+
45 |applicability | Test case can be configured with different packet sizes, |
46 | | burst sizes, ping intervals and test duration. |
47 | | SLA is optional. The SLA in this test case serves as an |
48 | | example. Considerably lower RTT is expected, and |
49 | | also normal to achieve in balanced L2 environments. However, |
50 | | to cover most configurations, both bare metal and fully |
51 | | virtualized ones, this value should be possible to achieve |
52 | | and acceptable for black box testing. Many real time |
53 | | applications start to suffer badly if the RTT time is higher |
54 | | than this. Some may suffer bad also close to this RTT, while |
55 | | others may not suffer at all. It is a compromise that may |
56 | | have to be tuned for different configuration purposes. |
58 +--------------+--------------------------------------------------------------+
59 |pre_test | Each pod node must have ping included in it. |
62 +--------------+--------------------------------------------------------------+
63 |test sequence | description and expected result |
65 +--------------+--------------------------------------------------------------+
66 |step 1 | The pod is available. Two nodes as server and client. |
67 | | Ping is invoked and logs are produced and stored. |
69 | | Result: Logs are stored. |
71 +--------------+--------------------------------------------------------------+
72 |test verdict | Test should not PASS if any RTT is above the optional SLA |
73 | | value, or if there is a test case execution problem. |
75 +--------------+--------------------------------------------------------------+