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 TC027
8 *************************************
10 .. _ipv6: https://wiki.opnfv.org/display/ipv6
12 +-----------------------------------------------------------------------------+
13 |IPv6 connectivity between nodes on the tenant network |
15 +--------------+--------------------------------------------------------------+
16 |test case id | OPNFV_YARDSTICK_TC027_IPv6 connectivity |
18 +--------------+--------------------------------------------------------------+
19 |metric | RTT, Round Trip Time |
21 +--------------+--------------------------------------------------------------+
22 |test purpose | To do a basic verification that IPv6 connectivity is within |
23 | | acceptable boundaries when ipv6 packets travel between hosts |
24 | | located on same or different compute blades. |
25 | | The purpose is also to be able to spot trends. Test results, |
26 | | graphs and similar shall be stored for comparison reasons and|
27 | | product evolution understanding between different OPNFV |
28 | | versions and/or configurations. |
30 +--------------+--------------------------------------------------------------+
31 |configuration | file: opnfv_yardstick_tc027.yaml |
33 | | Packet size 56 bytes. |
34 | | SLA RTT is set to maximum 30 ms. |
35 | | ipv6 test case can be configured as three independent modules|
36 | | (setup, run, teardown). if you only want to setup ipv6 |
37 | | testing environment, do some tests as you want, "run_step" |
38 | | of task yaml file should be configured as "setup". if you |
39 | | want to setup and run ping6 testing automatically, "run_step"|
40 | | should be configured as "setup, run". and if you have had a |
41 | | environment which has been setup, you only wan to verify the |
42 | | connectivity of ipv6 network, "run_step" should be "run". Of |
43 | | course, default is that three modules run sequentially. |
45 +--------------+--------------------------------------------------------------+
48 | | Ping6 is normally part of Linux distribution, hence it |
49 | | doesn't need to be installed. |
51 +--------------+--------------------------------------------------------------+
56 +--------------+--------------------------------------------------------------+
57 |applicability | Test case can be configured with different run step |
58 | | you can run setup, run benchmark, teardown independently |
59 | | SLA is optional. The SLA in this test case serves as an |
60 | | example. Considerably lower RTT is expected. |
62 +--------------+--------------------------------------------------------------+
63 |pre-test | The test case image needs to be installed into Glance |
64 |conditions | with ping6 included in it. |
66 | | For Brahmaputra, a compass_os_nosdn_ha deploy scenario is |
67 | | need. more installer and more sdn deploy scenario will be |
70 +--------------+--------------------------------------------------------------+
71 |test sequence | description and expected result |
73 +--------------+--------------------------------------------------------------+
74 |step 1 | To setup IPV6 testing environment: |
75 | | 1. disable security group |
76 | | 2. create (ipv6, ipv4) router, network and subnet |
77 | | 3. create VRouter, VM1, VM2 |
79 +--------------+--------------------------------------------------------------+
80 |step 2 | To run ping6 to verify IPV6 connectivity : |
82 | | 2. Ping6 to ipv6 router from VM1 |
83 | | 3. Get the result(RTT) and logs are stored |
85 +--------------+--------------------------------------------------------------+
86 |step 3 | To teardown IPV6 testing environment |
87 | | 1. delete VRouter, VM1, VM2 |
88 | | 2. delete (ipv6, ipv4) router, network and subnet |
89 | | 3. enable security group |
91 +--------------+--------------------------------------------------------------+
92 |test verdict | Test should not PASS if any RTT is above the optional SLA |
93 | | value, or if there is a test case execution problem. |
95 +--------------+--------------------------------------------------------------+