aboutsummaryrefslogtreecommitdiffstats
path: root/docs/configguide/yardstick_testcases
diff options
context:
space:
mode:
authorkubi <jean.gaoliang@huawei.com>2016-01-11 23:34:45 +0800
committerliang gao <jean.gaoliang@huawei.com>2016-01-11 15:55:14 +0000
commit70ea780b12007a188471dd1a594dccf16ca1a1cb (patch)
tree7f58830871684f02351d7f92fdd53f21c7396ab2 /docs/configguide/yardstick_testcases
parent8bbc0bd8ac3c6060f5b5ee3591bccf61e2aeca86 (diff)
IPv6 connectivity between nodes on the tenant network
Test case yaml and .rst file for ipv6 Change-Id: Ib9a554dc05445023687efb0ac608c7cbd0da4c21 Signed-off-by: kubi <jean.gaoliang@huawei.com>
Diffstat (limited to 'docs/configguide/yardstick_testcases')
-rw-r--r--docs/configguide/yardstick_testcases/03-list-of-tcs.rst1
-rw-r--r--docs/configguide/yardstick_testcases/opnfv_yardstick_tc027.rst67
2 files changed, 68 insertions, 0 deletions
diff --git a/docs/configguide/yardstick_testcases/03-list-of-tcs.rst b/docs/configguide/yardstick_testcases/03-list-of-tcs.rst
index c46d29b33..99be668b8 100644
--- a/docs/configguide/yardstick_testcases/03-list-of-tcs.rst
+++ b/docs/configguide/yardstick_testcases/03-list-of-tcs.rst
@@ -28,6 +28,7 @@ Generic NFVI Test Case Descriptions
opnfv_yardstick_tc010.rst
opnfv_yardstick_tc012.rst
opnfv_yardstick_tc014.rst
+ opnfv_yardstick_tc027.rst
opnfv_yardstick_tc037.rst
opnfv_yardstick_tc038.rst
opnfv_yardstick_tc040.rst
diff --git a/docs/configguide/yardstick_testcases/opnfv_yardstick_tc027.rst b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc027.rst
new file mode 100644
index 000000000..56c8227df
--- /dev/null
+++ b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc027.rst
@@ -0,0 +1,67 @@
+*************************************
+Yardstick Test Case Description TC027
+*************************************
+
+.. _ipv6: https://wiki.opnfv.org/ipv6_opnfv_project
+
++-----------------------------------------------------------------------------+
+|IPv6 connectivity between nodes on the tenant network |
+| |
++--------------+--------------------------------------------------------------+
+|test case id | OPNFV_YARDSTICK_TC002_IPv6 connectivity |
+| | |
++--------------+--------------------------------------------------------------+
+|metric | RTT, Round Trip Time |
+| | |
++--------------+--------------------------------------------------------------+
+|test purpose | To do a basic verification that IPv6 connectivity is within |
+| | acceptable boundaries when ipv6 packets travel between hosts |
+| | located on same or different compute blades. |
+| | The purpose is also to be able to spot trends. Test results, |
+| | graphs and similar shall be stored for comparison reasons and|
+| | product evolution understanding between different OPNFV |
+| | versions and/or configurations. |
+| | |
++--------------+--------------------------------------------------------------+
+|configuration | file: opnfv_yardstick_tc027.yaml |
+| | |
+| | Packet size 56 bytes. |
+| | SLA RTT is set to maximum 10 ms. |
+| | |
++--------------+--------------------------------------------------------------+
+|test tool | ping6 |
+| | |
+| | Ping6 is normally part of Linux distribution, hence it |
+| | doesn't need to be installed. |
+| | |
++--------------+--------------------------------------------------------------+
+|references | ipv6_ |
+| | |
+| | ETSI-NFV-TST001 |
+| | |
++--------------+--------------------------------------------------------------+
+|applicability | Test case can be configured with different run step |
+| | you can run setup, run benchmakr, teardown independently |
+| | SLA is optional. The SLA in this test case serves as an |
+| | example. Considerably lower RTT is expected. |
+| | |
++--------------+--------------------------------------------------------------+
+|pre-test | The test case image needs to be installed into Glance |
+|conditions | with ping6 included in it. |
+| | |
+| | No POD specific requirements have been identified. |
+| | |
++--------------+--------------------------------------------------------------+
+|test sequence | description and expected result |
+| | |
++--------------+--------------------------------------------------------------+
+|step 1 | The hosts are installed, 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. |
+| | |
++--------------+--------------------------------------------------------------+