aboutsummaryrefslogtreecommitdiffstats
path: root/docs/configguide/yardstick_testcases/opnfv_yardstick_tc011.rst
diff options
context:
space:
mode:
authorwym_libra <yimin.wang@huawei.com>2016-01-14 22:53:10 +0800
committerqi liang <liangqi1@huawei.com>2016-01-15 01:34:39 +0000
commit09c6f91228759e22a08bd9344962d65c1818e6b3 (patch)
tree1ccc975858cd7af3fc8a74e61df546f54313aa34 /docs/configguide/yardstick_testcases/opnfv_yardstick_tc011.rst
parent9d36842e3966185e97cc5732aa7a0edd2050bfe2 (diff)
Add test case description and task file for TC011
Add test case description for Packet delay variation between VMs (TC011) and test case .yaml task file. ** Please note that the SLA value has not yet been determined. ** Change-Id: I68a374224946d46c173ad477c14cb79d573b1eee Signed-off-by: wym_libra <yimin.wang@huawei.com>
Diffstat (limited to 'docs/configguide/yardstick_testcases/opnfv_yardstick_tc011.rst')
-rw-r--r--docs/configguide/yardstick_testcases/opnfv_yardstick_tc011.rst83
1 files changed, 83 insertions, 0 deletions
diff --git a/docs/configguide/yardstick_testcases/opnfv_yardstick_tc011.rst b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc011.rst
new file mode 100644
index 000000000..6760ce067
--- /dev/null
+++ b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc011.rst
@@ -0,0 +1,83 @@
+*************************************
+Yardstick Test Case Description TC011
+*************************************
+
+.. _iperf3: https://iperf.fr/
+
++-----------------------------------------------------------------------------+
+|Packet delay variation between VMs |
+| |
++--------------+--------------------------------------------------------------+
+|test case id | OPNFV_YARDSTICK_TC011_Packet delay variation between VMs |
+| | |
++--------------+--------------------------------------------------------------+
+|metric | jitter: packet delay variation (ms) |
+| | |
++--------------+--------------------------------------------------------------+
+|test purpose | Measure the packet delay variation sending the packets from |
+| | one VM to the other. |
+| | |
++--------------+--------------------------------------------------------------+
+|configuration | File: opnfv_yardstick_tc011.yaml |
+| | |
+| | * options: |
+| | protocol: udp # The protocol used by iperf3 tools |
+| | bandwidth: 20m # It will send the given number of packets |
+| | without pausing |
+| | * runner: |
+| | duration: 30 # Total test duration 30 seconds. |
+| | |
+| | * SLA (optional): |
+| | jitter: 10 (ms) # The maximum amount of jitter that is |
+| | accepted. |
+| | |
++--------------+--------------------------------------------------------------+
+|test tool | iperf3 |
+| | |
+| | iPerf3 is a tool for active measurements of the maximum |
+| | achievable bandwidth on IP networks. It supports tuning of |
+| | various parameters related to timing, buffers and protocols. |
+| | The UDP protocols can be used to measure jitter delay. |
+| | |
+| | (iperf3 is not always part of a Linux distribution, hence it |
+| | needs to be installed. It is part of the Yardstick Docker |
+| | image. |
+| | As an example see the /yardstick/tools/ directory for how |
+| | to generate a Linux image with pktgen included.) |
+| | |
++--------------+--------------------------------------------------------------+
+|references | iperf3_ |
+| | |
+| | ETSI-NFV-TST001 |
+| | |
++--------------+--------------------------------------------------------------+
+|applicability | Test can be configured with different |
+| | |
+| | * bandwidth: Test case can be configured with different |
+| | bandwidth |
+| | |
+| | * duration: The test duration can be configured |
+| | |
+| | * jitter: SLA is optional. The SLA in this test case |
+| | serves as an example. |
+| | |
++--------------+--------------------------------------------------------------+
+|pre-test | The test case image needs to be installed into Glance |
+|conditions | with iperf3 included in the image. |
+| | |
+| | No POD specific requirements have been identified. |
+| | |
++--------------+--------------------------------------------------------------+
+|test sequence | description and expected result |
+| | |
++--------------+--------------------------------------------------------------+
+|step 1 | The hosts are installed, as server and client. iperf3 is |
+| | invoked and logs are produced and stored. |
+| | |
+| | Result: Logs are stored. |
+| | |
++--------------+--------------------------------------------------------------+
+|test verdict | Test should not PASS if any jitter is above the optional SLA |
+| | value, or if there is a test case execution problem. |
+| | |
++--------------+--------------------------------------------------------------+