aboutsummaryrefslogtreecommitdiffstats
path: root/docs/configguide/yardstick_testcases/opnfv_yardstick_tc028.rst
diff options
context:
space:
mode:
authorQiLiang <liangqi1@huawei.com>2016-01-12 22:45:42 +0000
committerqi liang <liangqi1@huawei.com>2016-01-12 14:47:52 +0000
commitdf2fe5be08cdaeaee264ae5fcae719e6fba13620 (patch)
tree1e303dc3cb4fb81d0ee6090f9ba333a0d7244494 /docs/configguide/yardstick_testcases/opnfv_yardstick_tc028.rst
parent4936801c7f5e64f3f7ef037b0cec58ec056f9154 (diff)
Add test case description for TC028-kvm
JIRA: YARDSTICK-188 Change-Id: I16f8c5ac3a3997640ce96a77984c4dbe9ccb2804 Signed-off-by: QiLiang <liangqi1@huawei.com> (cherry picked from commit ef353b91b2527580a642da561a387d67b71e753d)
Diffstat (limited to 'docs/configguide/yardstick_testcases/opnfv_yardstick_tc028.rst')
-rw-r--r--docs/configguide/yardstick_testcases/opnfv_yardstick_tc028.rst66
1 files changed, 66 insertions, 0 deletions
diff --git a/docs/configguide/yardstick_testcases/opnfv_yardstick_tc028.rst b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc028.rst
new file mode 100644
index 000000000..8b6db1131
--- /dev/null
+++ b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc028.rst
@@ -0,0 +1,66 @@
+*************************************
+Yardstick Test Case Description TC028
+*************************************
+
+.. _Cyclictest: https://rt.wiki.kernel.org/index.php/Cyclictest
+
++-----------------------------------------------------------------------------+
+|KVM Latency measurements |
+| |
++--------------+--------------------------------------------------------------+
+|test case id | OPNFV_YARDSTICK_TC028_KVM Latency measurements |
+| | |
++--------------+--------------------------------------------------------------+
+|metric | min, avg and max latency |
+| | |
++--------------+--------------------------------------------------------------+
+|test purpose | To evaluate the IaaS KVM virtualization capability with |
+| | regards to min, avg and max latency. |
+| | 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: samples/cyclictest-node-context.yaml |
+| | |
++--------------+--------------------------------------------------------------+
+|test tool | Cyclictest |
+| | |
+| | (Cyclictest is not always part of a Linux distribution, |
+| | hence it needs to be installed. As an example see the |
+| | /yardstick/tools/ directory for how to generate a Linux |
+| | image with cyclictest included.) |
+| | |
++--------------+--------------------------------------------------------------+
+|references | Cyclictest_ |
+| | |
++--------------+--------------------------------------------------------------+
+|applicability | This test case is mainly for kvm4nfv project CI verify. |
+| | Upgrade host linux kernel, boot a gust vm update it's linux |
+| | kernel, and then run the cyclictest to test the new kernel |
+| | is work well. |
+| | |
++--------------+--------------------------------------------------------------+
+|pre-test | The test kernel rpm, test sequence scripts and test guest |
+|conditions | image need put the right folders as specified in the test |
+| | case yaml file. |
+| | The test guest image needs with cyclictest included in it. |
+| | |
+| | No POD specific requirements have been identified. |
+| | |
++--------------+--------------------------------------------------------------+
+|test sequence | description and expected result |
+| | |
++--------------+--------------------------------------------------------------+
+|step 1 | The host and guest os kernel is upgraded. Cyclictest is |
+| | invoked and logs are produced and stored. |
+| | |
+| | Result: Logs are stored. |
+| | |
++--------------+--------------------------------------------------------------+
+|test verdict | Fails only if SLA is not passed, or if there is a test case |
+| | execution problem. |
+| | |
++--------------+--------------------------------------------------------------+
+