summaryrefslogtreecommitdiffstats
path: root/docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst
diff options
context:
space:
mode:
authorAna C <ana.cunha@ericsson.com>2016-02-10 19:07:13 +0100
committerAna Cunha <ana.cunha@ericsson.com>2016-02-11 15:05:18 +0000
commit95cdd0ea41e3892422de92f13fac39871585706e (patch)
treed8703d6411af6614b299a1005495c389327793ad /docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst
parent5f2938cc116f5c8769317e043440d79a0fb2045f (diff)
Add license info and update structure
This change adds license to all .rst files under userguide. It also combines all configguide files into user guide. New reference.rst with list of links. Updated glossary, removed separate directories for apexlake and yardstick framework. Change-Id: I6532ed073905b0fa85a17e759ea7dc3c24acb91f Signed-off-by: Ana C <ana.cunha@ericsson.com> (cherry picked from commit 702eebbf78b29fb9046436dd71575b4f210f4731)
Diffstat (limited to 'docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst')
-rw-r--r--docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst69
1 files changed, 0 insertions, 69 deletions
diff --git a/docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst
deleted file mode 100644
index 68d36ecd2..000000000
--- a/docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst
+++ /dev/null
@@ -1,69 +0,0 @@
-*************************************
-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. |
-| | |
-+--------------+--------------------------------------------------------------+