blob: 68d36ecd204f92d9a401e951817cb5799db05e6a (
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
66
67
68
69
|
*************************************
Yardstick Test Case Description TC014
*************************************
.. _unixbench: https://github.com/kdlucas/byte-unixbench/blob/master/UnixBench
+-----------------------------------------------------------------------------+
|Processing speed |
| |
+--------------+--------------------------------------------------------------+
|test case id | OPNFV_YARDSTICK_TC014_Processing speed |
| | |
+--------------+--------------------------------------------------------------+
|metric | score of single cpu running, score of parallel running |
| | |
+--------------+--------------------------------------------------------------+
|test purpose | To evaluate the IaaS processing speed with regards to score |
| | of single cpu running and parallel running |
| | 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_tc014.yaml |
| | |
| | run_mode: Run unixbench in quiet mode or verbose mode |
| | test_type: dhry2reg, whetstone and so on |
| | |
| | For SLA with single_score and parallel_score, both can be |
| | set by user, default is NA |
| | |
+--------------+--------------------------------------------------------------+
|test tool | unixbench |
| | |
| | (unixbench 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 unixbench included.) |
| | |
+--------------+--------------------------------------------------------------+
|references | unixbench_ |
| | |
| | ETSI-NFV-TST001 |
| | |
+--------------+--------------------------------------------------------------+
|applicability | Test can be configured with different test types, dhry2reg, |
| | whetstone and so on. |
| | |
+--------------+--------------------------------------------------------------+
|pre-test | The test case image needs to be installed into Glance |
|conditions | with unixbench included in it. |
| | |
| | No POD specific requirements have been identified. |
| | |
+--------------+--------------------------------------------------------------+
|test sequence | description and expected result |
| | |
+--------------+--------------------------------------------------------------+
|step 1 | The hosts are installed, as a client. unixbench 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. |
| | |
+--------------+--------------------------------------------------------------+
|
