Merge "[docs] Add vEPC test case preparation steps"

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

diff --git a/docs/testing/user/userguide/opnfv_yardstick_tc057.rst b/docs/testing/user/userguide/opnfv_yardstick_tc057.rst
index 2a4ce40..245a58e 100644 (file)
--- a/docs/testing/user/userguide/opnfv_yardstick_tc057.rst
+++ b/docs/testing/user/userguide/opnfv_yardstick_tc057.rst
@@ -10,8 +10,11 @@ Yardstick Test Case Description TC057
 
 +-----------------------------------------------------------------------------+
 |OpenStack Controller Cluster Management Service High Availability            |
-+==============+==============================================================+
-|test case id  |                                                              |
+|                                                                             |
++--------------+--------------------------------------------------------------+
+|test case id  | OPNFV_YARDSTICK_TC057_HA: OpenStack Controller Cluster       |
+|              | Management Service High Availability                         |
+|              |                                                              |
 +--------------+--------------------------------------------------------------+
 |test purpose  | This test case will verify the quorum configuration of the   |
 |              | cluster manager(pacemaker) on controller nodes. When a       |
@@ -46,17 +49,21 @@ Yardstick Test Case Description TC057
 |              | -host: node1                                                 |
 +--------------+--------------------------------------------------------------+
 |monitors      | In this test case, a kind of monitor is 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 scripts. It should be always set to              |
-|              | "openstack-cmd" for this monitor.                            |
-|              | 2) command_name: which is the command name used for request  |
 |              |                                                              |
-|              | In this case, the command_name of monitor1 should be services|
-|              | that are managed by the cluster manager. (Since rabbitmq and |
-|              | haproxy are managed by pacemaker, most Openstack Services    |
-|              | can be used to check high availability in this case)         |
+|              |    1. monitor_type: which is used for finding the monitor    |
+|              |       class and related scripts. It should be always set to  |
+|              |       "openstack-cmd" for this monitor.                      |
+|              |    2. command_name: which is the command name used for       |
+|              |       request                                                |
+|              |                                                              |
+|              | In this case, the command_name of monitor1 should be         |
+|              | services that are managed by the cluster manager.            |
+|              | (Since rabbitmq and haproxy are managed by pacemaker,        |
+|              | most Openstack Services can be used to check high            |
+|              | availability in this case)                                   |
 |              |                                                              |
 |              | (e.g.)                                                       |
 |              | monitor1:                                                    |
@@ -155,11 +162,17 @@ Yardstick Test Case Description TC057
 |              | Result: The test case is passed or not.                      |
 |              |                                                              |
 +--------------+------+----------------------------------+--------------------+
-|post-action   | It is the action when the test cases exist. It will check the|
-|              | status of the cluster messaging process(corosync) on the     |
+|post-action   | It is the action when the test cases exist. It will check    |
+|              | the status of the cluster messaging process(corosync) on the |
 |              | host, and restart the process if it is not running for next  |
-|              | test cases                                                   |
+|              | 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  |
 |              | execution problem.                                           |
+|              |                                                              |
 +--------------+--------------------------------------------------------------+