1 *************************************
2 Yardstick Test Case Description TC002
3 *************************************
5 +-----------------------------------------------------------------------------+
7 +==============+==============================================================+
8 |test case id | OPNFV_YARDSTICK_TC002_NW LATENCY |
9 +--------------+--------------------------------------------------------------+
10 |metric | RTT, Round Trip Time |
11 +--------------+--------------------------------------------------------------+
12 |test purpose | To do a basic verification that network latency is within |
13 | | acceptable boundaries when packets travel between hosts |
14 | | located on same or different compute blades. |
15 | | The purpose is also to be able to spot trends. Test results, |
16 | | graphs and similar shall be stored for comparison reasons and|
17 | | product evolution understanding between different OPNFV |
18 | | versions and/or configurations. |
19 +--------------+--------------------------------------------------------------+
20 |configuration | file: opnfv_yardstick_tc002.yaml |
22 | | Packet size 100 bytes. Total test duration 600 seconds. |
23 | | One ping each 10 seconds. SLA RTT is set to maximum 10 ms. |
24 +--------------+--------------------------------------------------------------+
27 | | Ping is normally part of any Linux distribution, hence it |
28 | | doesn't need to be installed. It is also part of the |
29 | | Yardstick Docker image. |
30 | | (For example also a Cirros image can be downloaded from |
31 | | https://download.cirros-cloud.net, it includes ping) |
32 +--------------+--------------------------------------------------------------+
33 |references | Ping man page |
36 +--------------+--------------------------------------------------------------+
37 |applicability | Test case can be configured with different packet sizes, |
38 | | burst sizes, ping intervals and test duration. |
39 | | SLA is optional. The SLA in this test case serves as an |
40 | | example. Considerably lower RTT is expected, and |
41 | | also normal to achieve in balanced L2 environments. However, |
42 | | to cover most configurations, both bare metal and fully |
43 | | virtualized ones, this value should be possible to achieve |
44 | | and acceptable for black box testing. Many real time |
45 | | applications start to suffer badly if the RTT time is higher |
46 | | than this. Some may suffer bad also close to this RTT, while |
47 | | others may not suffer at all. It is a compromise that may |
48 | | have to be tuned for different configuration purposes. |
49 +--------------+--------------------------------------------------------------+
50 |pre-test | The test case image needs to be installed into Glance |
51 |conditions | with ping included in it. |
53 | | No POD specific requirements have been identified. |
54 +--------------+------+----------------------------------+--------------------+
55 |test sequence | step | description | result |
56 | +------+----------------------------------+--------------------+
57 | | 1 | The hosts are installed, as | Logs are stored |
58 | | | server and client. Ping is | |
59 | | | invoked and logs are produced | |
61 +--------------+------+----------------------------------+--------------------+
62 |test verdict | Test should not PASS if any RTT is above the optional SLA |
63 | | value, or if there is a test case execution problem. |
64 +--------------+--------------------------------------------------------------+