Merge "[docs][userguide] Update NSB intro in ch12"

[yardstick.git] / docs / testing / user / userguide / opnfv_yardstick_tc019.rst

diff --git a/docs/testing/user/userguide/opnfv_yardstick_tc019.rst b/docs/testing/user/userguide/opnfv_yardstick_tc019.rst
index 57e8ddf..d27b201 100644 (file)
--- a/docs/testing/user/userguide/opnfv_yardstick_tc019.rst
+++ b/docs/testing/user/userguide/opnfv_yardstick_tc019.rst
@@ -43,20 +43,24 @@ Yardstick Test Case Description TC019
 |              |                                                              |
 +--------------+--------------------------------------------------------------+
 |monitors      | In this test case, two kinds of monitor are needed:          |
+|              |                                                              |
 |              | 1. the "openstack-cmd" monitor constantly request a specific |
 |              |    Openstack command, which needs two parameters:            |
-|              | 1) monitor_type: which is used for finding the monitor class |
-|              | and related scritps. It should be always set to              |
-|              | "openstack-cmd" for this monitor.                            |
-|              | 2) command_name: which is the command name used for request  |
+|              |                                                              |
+|              |    1. monitor_type: which is used for finding the monitor    |
+|              |       class and related scritps. It should be always set to  |
+|              |       "openstack-cmd" for this monitor.                      |
+|              |    2. command_name: which is the command name used for       |
+|              |       request                                                |
 |              |                                                              |
 |              | 2. the "process" monitor check whether a process is running  |
 |              |    on a specific node, which needs three parameters:         |
-|              | 1) monitor_type: which used for finding the monitor class    |
-|              | and related scritps. It should be always set to "process"    |
-|              | for this monitor.                                            |
-|              | 2) process_name: which is the process name for monitor       |
-|              | 3) host: which is the name of the node runing the process    |
+|              |                                                              |
+|              |    1. monitor_type: which used for finding the monitor class |
+|              |       and related scritps. It should be always set to        |
+|              |       "process" for this monitor.                            |
+|              |    2. process_name: which is the process name for monitor    |
+|              |    3. host: which is the name of the node runing the process |
 |              |                                                              |
 |              | e.g.                                                         |
 |              | monitor1:                                                    |
@@ -125,7 +129,12 @@ Yardstick Test Case Description TC019
 +--------------+--------------------------------------------------------------+
 |post-action   | It is the action when the test cases exist. It will check    |
 |              | the status of the specified process on the host, and restart |
-|              | the process if it is not running for next test cases         |
+|              | the process if it is not running for next test cases.        |
+|              |                                                              |
+|              | Notice: This post-action uses 'lsb_release' command to check |
+|              | the host linux distribution and determine the OpenStack      |
+|              | service name to restart the process. Lack of 'lsb_release'   |
+|              | on the host may cause failure to restart the process.        |
 |              |                                                              |
 +--------------+--------------------------------------------------------------+
 |test verdict  | Fails only if SLA is not passed, or if there is a test case  |