summaryrefslogtreecommitdiffstats
path: root/docs/testing/user/userguide/opnfv_yardstick_tc092.rst
diff options
context:
space:
mode:
authorEmma Foley <emma.l.foley@intel.com>2018-10-03 13:54:09 +0100
committerRex Lee <limingjiang@huawei.com>2018-11-09 18:02:10 +0000
commit4dff5f3edda4b68bb238addb65def5f97f71154e (patch)
tree8b220e0b75b2d9e6d0c158e9cf61a4781e637212 /docs/testing/user/userguide/opnfv_yardstick_tc092.rst
parente153537764f9eb8e6570602b2d855e77062115d7 (diff)
[docs] Fix docs {un,}indent warnings in Testcase definitions
Mostly, the issues were with un/indentation. This has been fixed, and `tox -e docs` now issues less warnings. JIRA: YARDSTICK-1416 Change-Id: Ie58a8dba42e9868357e1dce414cb1a01af8ad1f4 Signed-off-by: Emma Foley <emma.l.foley@intel.com> (cherry picked from commit 28e64c520fc2a52c1d3eb736f88ad4608b87c142)
Diffstat (limited to 'docs/testing/user/userguide/opnfv_yardstick_tc092.rst')
-rw-r--r--docs/testing/user/userguide/opnfv_yardstick_tc092.rst33
1 files changed, 19 insertions, 14 deletions
diff --git a/docs/testing/user/userguide/opnfv_yardstick_tc092.rst b/docs/testing/user/userguide/opnfv_yardstick_tc092.rst
index 895074a85..9c833fa23 100644
--- a/docs/testing/user/userguide/opnfv_yardstick_tc092.rst
+++ b/docs/testing/user/userguide/opnfv_yardstick_tc092.rst
@@ -43,6 +43,7 @@ Yardstick Test Case Description TC092
+--------------+--------------------------------------------------------------+
|attackers | In this test case, an attacker called “kill-process” is |
| | needed. This attacker includes three parameters: |
+| | |
| | 1. ``fault_type``: which is used for finding the attacker's |
| | scripts. It should be set to 'kill-process' in this test |
| | |
@@ -92,17 +93,20 @@ Yardstick Test Case Description TC092
| | |
+--------------+--------------------------------------------------------------+
|configuration | This test case needs two configuration files: |
-| | 1. test case file: opnfv_yardstick_tc092.yaml |
-| | - Attackers: see above “attackers” discription |
-| | - Monitors: see above “monitors” discription |
-| | - waiting_time: which is the time (seconds) from the |
-| | process being killed to stoping monitors the |
-| | monitors |
-| | - SLA: see above “metrics” discription |
+| | 1. test case file: opnfv_yardstick_tc092.yaml |
+| | |
+| | - Attackers: see above “attackers” discription |
+| | - Monitors: see above “monitors” discription |
+| | |
+| | - waiting_time: which is the time (seconds) from the |
+| | process being killed to stoping monitors the |
+| | monitors |
| | |
-| | 2. POD file: pod.yaml The POD configuration should record |
-| | on pod.yaml first. the “host” item in this test case |
-| | will use the node name in the pod.yaml. |
+| | - SLA: see above “metrics” discription |
+| | |
+| | 2. POD file: pod.yaml The POD configuration should record |
+| | on pod.yaml first. the “host” item in this test case |
+| | will use the node name in the pod.yaml. |
| | |
+--------------+--------------------------------------------------------------+
|test sequence | Description and expected result |
@@ -168,11 +172,12 @@ Yardstick Test Case Description TC092
| | |
+--------------+--------------------------------------------------------------+
|step 8 | Start IP connectivity monitors for the new VM: |
-| | 1. Check the L2 connectivity from the existing VMs to the |
-| | new VM in the Neutron network. |
| | |
-| | 2. Check connectivity from one VM to an external host on |
-| | the Internet to verify SNAT functionality. |
+| | 1. Check the L2 connectivity from the existing VMs to the |
+| | new VM in the Neutron network. |
+| | |
+| | 2. Check connectivity from one VM to an external host on |
+| | the Internet to verify SNAT functionality. |
| | |
| | Result: The monitor info will be collected. |
| | |