summaryrefslogtreecommitdiffstats
path: root/docs/scenarios
diff options
context:
space:
mode:
authordongwenjuan <dong.wenjuan@zte.com.cn>2016-08-25 08:56:37 +0800
committerwenjuan dong <dong.wenjuan@zte.com.cn>2016-08-31 09:31:31 +0000
commit315cf19d5f54687bfa8995f0b8767b986c43fbf6 (patch)
tree4b7290072bd6edd0889ee1c9fef5a20247548749 /docs/scenarios
parent6cf036177753359bdbb65464fb0abe3abe3db153 (diff)
fix the description in doctor_scenario_in_functest.rst
Change-Id: I76d5437c64b080a5908b41ffca7686c7e7ae8e3b Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
Diffstat (limited to 'docs/scenarios')
-rw-r--r--docs/scenarios/functest/doctor-scenario-in-functest.rst16
1 files changed, 12 insertions, 4 deletions
diff --git a/docs/scenarios/functest/doctor-scenario-in-functest.rst b/docs/scenarios/functest/doctor-scenario-in-functest.rst
index 29af7390..3c021d61 100644
--- a/docs/scenarios/functest/doctor-scenario-in-functest.rst
+++ b/docs/scenarios/functest/doctor-scenario-in-functest.rst
@@ -92,20 +92,28 @@ Test case
Functest will call the "run.sh" script in Doctor to run the test job.
-Currently, only 'Apex' and 'local' installer are supported.
+Currently, only 'Apex' and 'local' installer are supported. The test also
+can run successfully in 'fuel' installer with the modification of some
+configurations of OpenStack in the script. But still need 'fuel' installer
+to support these configurations.
The "run.sh" script will execute the following steps.
-Firstly, prepare image for booting VM, then create a test project and test
+Firstly, get the installer ip according to the installer type. Then ssh to
+the installer node to get the private key for accessing to the cloud. As
+'fuel' installer, ssh to the controller node to modify nova and ceilometer
+configurations.
+
+Secondly, prepare image for booting VM, then create a test project and test
user (both default to doctor) for the Doctor tests.
-Secondly, boot a VM under the doctor project and check the VM status to verify
+Thirdly, boot a VM under the doctor project and check the VM status to verify
that the VM is launched completely. Then get the compute host info where the VM
is launched to verify connectivity to the target compute host. Get the consumer
ip according to the route to compute ip and create an alarm event in Ceilometer
using the consumer ip.
-Thirdly, the Doctor components are started, and, based on the above preparation,
+Fourthly, the Doctor components are started, and, based on the above preparation,
a failure is injected to the system, i.e. the network of compute host is
disabled for 3 minutes. To ensure the host is down, the status of the host
will be checked.