diff options
| author |   Per Holmgren <per.q.holmgren@ericsson.com> | 2016-01-14 16:06:34 +0100 |
|---|---|---|
| committer |   Ana Cunha <ana.cunha@ericsson.com> | 2016-01-15 09:08:14 +0000 |
| commit | 9598fee99c2b2cabd3d0546de8cdfb7a942a9500 (patch) | |
| tree | 474753be62857b42ae052b5621e7e683cb94680a | |
| parent | 2b22ae88bac773da32febfe50b097951000b3500 (diff) | |
Adds desription for TC024, the CPU load/mpstat test case
Change-Id: Ifbc571e3e216349d065ac21df1a3f10fe94d4e9a
JIRA: -
(cherry picked from commit bb82fb8c9198d6e792b8558bf6eaf4f53710c7fe)
| -rw-r--r-- | docs/configguide/yardstick_testcases/03-list-of-tcs.rst | 1 | ||||
| -rw-r--r-- | docs/configguide/yardstick_testcases/opnfv_yardstick_tc024.rst | 64 |
2 files changed, 65 insertions, 0 deletions
diff --git a/docs/configguide/yardstick_testcases/03-list-of-tcs.rst b/docs/configguide/yardstick_testcases/03-list-of-tcs.rst index 763a4d633..bb3fbbac5 100644 --- a/docs/configguide/yardstick_testcases/03-list-of-tcs.rst +++ b/docs/configguide/yardstick_testcases/03-list-of-tcs.rst @@ -30,6 +30,7 @@ Generic NFVI Test Case Descriptions opnfv_yardstick_tc011.rst opnfv_yardstick_tc012.rst opnfv_yardstick_tc014.rst + opnfv_yardstick_tc024.rst opnfv_yardstick_tc037.rst opnfv_yardstick_tc038.rst diff --git a/docs/configguide/yardstick_testcases/opnfv_yardstick_tc024.rst b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc024.rst new file mode 100644 index 000000000..1e8d4e6f3 --- /dev/null +++ b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc024.rst @@ -0,0 +1,64 @@ +************************************* +Yardstick Test Case Description TC024 +************************************* + +.. _man-pages: http://manpages.ubuntu.com/manpages/trusty/man1/mpstat.1.html + ++-----------------------------------------------------------------------------+ +| CPU Load | +| | ++--------------+--------------------------------------------------------------+ +|test case id | OPNFV_YARDSTICK_TC024_CPU Load | +| | | ++--------------+--------------------------------------------------------------+ +|metric | CPU load | +| | | ++--------------+--------------------------------------------------------------+ +|test purpose | To evaluate the CPU load performance of the IaaS. This test | +| | case should be run in parallel to other Yardstick test cases | +| | and not run as a stand-alone test case. | +| | | +| | The purpose is also to be able to spot trends. Test results, | +| | graphs ans similar shall be stored for comparison reasons and| +| | product evolution understanding between different OPNFV | +| | versions and/or configurations. | +| | | ++--------------+--------------------------------------------------------------+ +|configuration | file: cpuload.yaml (in the 'samples' directory) | +| | | +| | There is are no additional configurations to be set for this | +| | TC. | +| | | ++--------------+--------------------------------------------------------------+ +|test tool | mpstat | +| | | +| | (mpstat is not always part of a Linux distribution, hence it | +| | needs to be installed. It is part of the Yardstick Glance | +| | image. However, if mpstat is not present the TC instead uses | +| | /proc/stats as source to produce "mpstat" output. | +| | | ++--------------+--------------------------------------------------------------+ +|references | man-pages_ | +| | | ++--------------+--------------------------------------------------------------+ +|applicability | Run in background with other test cases. | +| | | ++--------------+--------------------------------------------------------------+ +|pre-test | The test case image needs to be installed into Glance | +|conditions | with mpstat included in it. | +| | | +| | No POD specific requirements have been identified. | +| | | ++--------------+--------------------------------------------------------------+ +|test sequence | description and expected result | +| | | ++--------------+--------------------------------------------------------------+ +|step 1 | The host is installed. The related TC, or TCs, is | +| | invoked and mpstat logs are produced and stored. | +| | | +| | Result: Stored logs | +| | | ++--------------+--------------------------------------------------------------+ +|test verdict | None. CPU load results are fetched and stored. | +| | | ++--------------+--------------------------------------------------------------+ |