OPNFV_YARDSTICK_TC043_Latency_between_NFVI_nodes_measurements

JIRA: YARDSTICK-258

Change-Id: I330fecead430618cb1a16e3e02d92b1a3bc5875a
Signed-off-by: rexlee8776 <limingjiang@huawei.com>

1 files changed, 75 insertions, 0 deletions

diff --git a/docs/userguide/opnfv_yardstick_tc043.rst b/docs/userguide/opnfv_yardstick_tc043.rst
new file mode 100644
index 000000000..2f907e9ef
--- /dev/null
+++ b/docs/userguide/opnfv_yardstick_tc043.rst
@@ -0,0 +1,75 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International
+.. License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) OPNFV, Huawei Technologies Co.,Ltd and others.
+
+*************************************
+Yardstick Test Case Description TC043
+*************************************
+
+.. _cirros-image: https://download.cirros-cloud.net
+
++-----------------------------------------------------------------------------+
+|Network Latency Between NFVI Nodes                                           |
+|                                                                             |
++--------------+--------------------------------------------------------------+
+|test case id  | OPNFV_YARDSTICK_TC043_Latency_between_                       |
+|              | NFVI_nodes_measurements                                      |
++--------------+--------------------------------------------------------------+
+|metric        | RTT, Round Trip Time                                         |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|test purpose  | To do a basic verification that network latency is within    |
+|              | acceptable boundaries when packets travel between different  |
+|              | nodes.                                                       |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|configuration | file: opnfv_yardstick_tc043.yaml                             |
+|              |                                                              |
+|              | Packet size 100 bytes. Total test duration 600 seconds.      |
+|              | One ping each 10 seconds. SLA RTT is set to maximum 10 ms.   |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|test tool     | ping                                                         |
+|              |                                                              |
+|              | Ping is normally part of any Linux distribution, hence it    |
+|              | doesn't need to be installed. It is also part of the         |
+|              | Yardstick Docker image.                                      |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|references    | Ping man page                                                |
+|              |                                                              |
+|              | ETSI-NFV-TST001                                              |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|applicability | Test case can be configured with different packet sizes,     |
+|              | burst sizes, ping intervals and test duration.               |
+|              | SLA is optional. The SLA in this test case serves as an      |
+|              | example. Considerably lower RTT is expected, and             |
+|              | also normal to achieve in balanced L2 environments. However, |
+|              | to cover most configurations, both bare metal and fully      |
+|              | virtualized ones, this value should be possible to achieve   |
+|              | and acceptable for black box testing. Many real time         |
+|              | applications start to suffer badly if the RTT time is higher |
+|              | than this. Some may suffer bad also close to this RTT, while |
+|              | others may not suffer at all. It is a compromise that may    |
+|              | have to be tuned for different configuration purposes.       |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|pre_test      | Each pod node must have ping included in it.                 |
+|conditions    |                                                              |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|test sequence | description and expected result                              |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|step 1        | The pod is available. Two nodes as server and client.        |
+|              | Ping is invoked and logs are produced and stored.            |
+|              |                                                              |
+|              | Result: Logs are stored.                                     |
+|              |                                                              |
++--------------+--------------------------------------------------------------+
+|test verdict  | Test should not PASS if any RTT is above the optional SLA    |
+|              | value, or if there is a test case execution problem.         |
+|              |                                                              |
++--------------+--------------------------------------------------------------+