docs/configguide/yardstick_testcases/opnfv_yardstick_tc024.rst

   1 *************************************
   2 Yardstick Test Case Description TC024
   3 *************************************
   4
   5 .. _man-pages: http://manpages.ubuntu.com/manpages/trusty/man1/mpstat.1.html
   6
   7 +-----------------------------------------------------------------------------+
   8 | CPU Load                                                                    |
   9 |                                                                             |
  10 +--------------+--------------------------------------------------------------+
  11 |test case id  | OPNFV_YARDSTICK_TC024_CPU Load                               |
  12 |              |                                                              |
  13 +--------------+--------------------------------------------------------------+
  14 |metric        | CPU load                                                     |
  15 |              |                                                              |
  16 +--------------+--------------------------------------------------------------+
  17 |test purpose  | To evaluate the CPU load performance of the IaaS. This test  |
  18 |              | case should be run in parallel to other Yardstick test cases |
  19 |              | and not run as a stand-alone test case.                      |
  20 |              |                                                              |
  21 |              | The purpose is also to be able to spot trends. Test results, |
  22 |              | graphs ans similar shall be stored for comparison reasons and|
  23 |              | product evolution understanding between different OPNFV      |
  24 |              | versions and/or configurations.                              |
  25 |              |                                                              |
  26 +--------------+--------------------------------------------------------------+
  27 |configuration | file: cpuload.yaml (in the 'samples' directory)              |
  28 |              |                                                              |
  29 |              | There is are no additional configurations to be set for this |
  30 |              | TC.                                                          |
  31 |              |                                                              |
  32 +--------------+--------------------------------------------------------------+
  33 |test tool     | mpstat                                                       |
  34 |              |                                                              |
  35 |              | (mpstat is not always part of a Linux distribution, hence it |
  36 |              | needs to be installed. It is part of the Yardstick Glance    |
  37 |              | image. However, if mpstat is not present the TC instead uses |
  38 |              | /proc/stats as source to produce "mpstat" output.            |
  39 |              |                                                              |
  40 +--------------+--------------------------------------------------------------+
  41 |references    | man-pages_                                                   |
  42 |              |                                                              |
  43 +--------------+--------------------------------------------------------------+
  44 |applicability | Run in background with other test cases.                     |
  45 |              |                                                              |
  46 +--------------+--------------------------------------------------------------+
  47 |pre-test      | The test case image needs to be installed into Glance        |
  48 |conditions    | with mpstat included in it.                                  |
  49 |              |                                                              |
  50 |              | No POD specific requirements have been identified.           |
  51 |              |                                                              |
  52 +--------------+--------------------------------------------------------------+
  53 |test sequence | description and expected result                              |
  54 |              |                                                              |
  55 +--------------+--------------------------------------------------------------+
  56 |step 1        | The host is installed. The related TC, or TCs, is            |
  57 |              | invoked and mpstat logs are produced and stored.             |
  58 |              |                                                              |
  59 |              | Result: Stored logs                                          |
  60 |              |                                                              |
  61 +--------------+--------------------------------------------------------------+
  62 |test verdict  | None. CPU load results are fetched and stored.               |
  63 |              |                                                              |
  64 +--------------+--------------------------------------------------------------+