blob: 8ac5f49f9c804d88aa5446bbecbf9016849a51e2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
*************************************
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. |
| | |
+--------------+--------------------------------------------------------------+
|
