1 .. This work is licensed under a Creative Commons Attribution 4.0 International
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, Yin Kanglin and others.
5 .. 14_ykl@tongji.edu.cn
7 *************************************
8 Yardstick Test Case Description TC053
9 *************************************
11 +-----------------------------------------------------------------------------+
12 |OpenStack Controller Load Balance Service High Availability |
14 +--------------+--------------------------------------------------------------+
15 |test case id | OPNFV_YARDSTICK_TC053: OpenStack Controller Load Balance |
16 | | Service High Availability |
17 +--------------+--------------------------------------------------------------+
18 |test purpose | This test case will verify the high availability of the |
19 | | load balance service(current is HAProxy) that supports |
20 | | OpenStack on controller node. When the load balance service |
21 | | of a specified controller node is killed, whether other load |
22 | | balancers on other controller nodes will work, and whether |
23 | | the controller node will restart the load balancer are |
25 +--------------+--------------------------------------------------------------+
26 |test method | This test case kills the processes of load balance service |
27 | | on a selected control node, then checks whether the request |
28 | | of the related Openstack command is OK and the killed |
29 | | processes are recovered. |
30 +--------------+--------------------------------------------------------------+
31 |attackers | In this test case, an attacker called "kill-process" is |
32 | | needed. This attacker includes three parameters: |
33 | | 1) fault_type: which is used for finding the attacker's |
34 | | scripts. It should be always set to "kill-process" in this |
36 | | 2) process_name: which is the process name of the specified |
37 | | OpenStack service. If there are multiple processes use the |
38 | | same name on the host, all of them are killed by this |
40 | | In this case. This parameter should always set to "swift- |
42 | | 3) host: which is the name of a control node being attacked. |
45 | | -fault_type: "kill-process" |
46 | | -process_name: "haproxy" |
49 +--------------+--------------------------------------------------------------+
50 |monitors | In this test case, two kinds of monitor are needed: |
51 | | 1. the "openstack-cmd" monitor constantly request a specific |
52 | | Openstack command, which needs two parameters: |
53 | | 1) monitor_type: which is used for finding the monitor class |
54 | | and related scritps. It should be always set to |
55 | | "openstack-cmd" for this monitor. |
56 | | 2) command_name: which is the command name used for request. |
58 | | 2. the "process" monitor check whether a process is running |
59 | | on a specific node, which needs three parameters: |
60 | | 1) monitor_type: which used for finding the monitor class |
61 | | and related scripts. It should be always set to "process" |
62 | | for this monitor. |
63 | | 2) process_name: which is the process name for monitor |
64 | | 3) host: which is the name of the node runing the process |
65 | | In this case, the command_name of monitor1 should be |
66 | | services that is supported by load balancer and the process- |
67 | | name of monitor2 should be "haproxy", for example: |
71 | | -monitor_type: "openstack-cmd" |
72 | | -command_name: "nova image-list" |
74 | | -monitor_type: "process" |
75 | | -process_name: "haproxy" |
78 +--------------+--------------------------------------------------------------+
79 |metrics | In this test case, there are two metrics: |
80 | | 1)service_outage_time: which indicates the maximum outage |
81 | | time (seconds) of the specified Openstack command request. |
82 | | 2)process_recover_time: which indicates the maximun time |
83 | | (seconds) from the process being killed to recovered |
85 +--------------+--------------------------------------------------------------+
86 |test tool | Developed by the project. Please see folder: |
87 | | "yardstick/benchmark/scenarios/availability/ha_tools" |
89 +--------------+--------------------------------------------------------------+
90 |references | ETSI NFV REL001 |
92 +--------------+--------------------------------------------------------------+
93 |configuration | This test case needs two configuration files: |
94 | | 1) test case file: opnfv_yardstick_tc053.yaml |
95 | | -Attackers: see above "attackers" discription |
96 | | -waiting_time: which is the time (seconds) from the process |
97 | | being killed to stoping monitors the monitors |
98 | | -Monitors: see above "monitors" discription |
99 | | -SLA: see above "metrics" discription |
101 | | 2)POD file: pod.yaml |
102 | | The POD configuration should record on pod.yaml first. |
103 | | the "host" item in this test case will use the node name in |
106 +--------------+--------------------------------------------------------------+
107 |test sequence | description and expected result |
109 +--------------+--------------------------------------------------------------+
110 |step 1 | start monitors: |
111 | | each monitor will run with independently process |
113 | | Result: The monitor info will be collected. |
115 +--------------+--------------------------------------------------------------+
116 |step 2 | do attacker: connect the host through SSH, and then execute |
117 | | the kill process script with param value specified by |
120 | | Result: Process will be killed. |
122 +--------------+--------------------------------------------------------------+
123 |step 3 | stop monitors after a period of time specified by |
126 | | Result: The monitor info will be aggregated. |
128 +--------------+--------------------------------------------------------------+
129 |step 4 | verify the SLA |
131 | | Result: The test case is passed or not. |
133 +--------------+--------------------------------------------------------------+
134 |post-action | It is the action when the test cases exist. It will check |
135 | | the status of the specified process on the host, and restart |
136 | | the process if it is not running for next test cases. |
138 +--------------+--------------------------------------------------------------+
139 |test verdict | Fails only if SLA is not passed, or if there is a test case |
140 | | execution problem. |
142 +--------------+--------------------------------------------------------------+