diff options
| -rw-r--r-- | docs/userguide/opnfv_yardstick_tc043.rst | 75 | ||||
| -rw-r--r-- | tests/opnfv/test_cases/opnfv_yardstick_tc043.yaml | 29 | ||||
| -rw-r--r-- | tests/opnfv/test_suites/opnfv_huawei-pod1_daily.yaml | 2 | ||||
| -rw-r--r-- | tests/opnfv/test_suites/opnfv_huawei-pod1_weekly.yaml | 4 |
4 files changed, 109 insertions, 1 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. | +| | | ++--------------+--------------------------------------------------------------+ diff --git a/tests/opnfv/test_cases/opnfv_yardstick_tc043.yaml b/tests/opnfv/test_cases/opnfv_yardstick_tc043.yaml new file mode 100644 index 000000000..b45e41ebf --- /dev/null +++ b/tests/opnfv/test_cases/opnfv_yardstick_tc043.yaml @@ -0,0 +1,29 @@ +--- +# Yardstick TC043 config file +# Measure latency between NFVI nodes using ping + +schema: "yardstick:task:0.1" + +scenarios: +- + type: Ping + options: + packetsize: 100 + host: node1.LF + target: node2.LF + + runner: + type: Duration + duration: 60 + interval: 1 + + sla: + max_rtt: 10 + action: monitor + + +context: + type: Node + name: LF + file: etc/yardstick/nodes/compass_sclab_physical/pod.yaml + diff --git a/tests/opnfv/test_suites/opnfv_huawei-pod1_daily.yaml b/tests/opnfv/test_suites/opnfv_huawei-pod1_daily.yaml index 3a3bfccc0..35eeb34a7 100644 --- a/tests/opnfv/test_suites/opnfv_huawei-pod1_daily.yaml +++ b/tests/opnfv/test_suites/opnfv_huawei-pod1_daily.yaml @@ -22,3 +22,5 @@ test_cases: file_name: opnfv_yardstick_tc027.yaml - file_name: opnfv_yardstick_tc037.yaml +- + file_name: opnfv_yardstick_tc043.yaml diff --git a/tests/opnfv/test_suites/opnfv_huawei-pod1_weekly.yaml b/tests/opnfv/test_suites/opnfv_huawei-pod1_weekly.yaml index cda46969d..8a9ce4dc0 100644 --- a/tests/opnfv/test_suites/opnfv_huawei-pod1_weekly.yaml +++ b/tests/opnfv/test_suites/opnfv_huawei-pod1_weekly.yaml @@ -23,4 +23,6 @@ test_cases: - file_name: opnfv_yardstick_tc037.yaml - - file_name: opnfv_yardstick_tc040.yaml
\ No newline at end of file + file_name: opnfv_yardstick_tc040.yaml +- + file_name: opnfv_yardstick_tc043.yaml |