Update the documentation to Danube release: JIRA: DOCTOR-81

[doctor.git] / docs / scenarios / functest / doctor-scenario-in-functest.rst

diff --git a/docs/scenarios/functest/doctor-scenario-in-functest.rst b/docs/scenarios/functest/doctor-scenario-in-functest.rst
index 29af739..b3d73d5 100644 (file)
--- a/docs/scenarios/functest/doctor-scenario-in-functest.rst
+++ b/docs/scenarios/functest/doctor-scenario-in-functest.rst
@@ -6,7 +6,7 @@
 Platform overview
 """""""""""""""""
 
-Doctor platform provides these features in `Colorado Release <https://wiki.opnfv.org/display/SWREL/Colorado>`_:
+Doctor platform provides these features in `Danube Release <https://wiki.opnfv.org/display/SWREL/Danube>`_:
 
 * Immediate Notification
 * Consistent resource state awareness for compute host down
@@ -41,11 +41,11 @@ You can see an overview of the Doctor platform and how components interact in
     :name: figure-p1
     :width: 100%
 
-    Doctor platform and typical sequence (Colorado)
+    Doctor platform and typical sequence
 
 Detailed information on the Doctor architecture can be found in the Doctor
 requirements documentation:
-http://artifacts.opnfv.org/doctor/colorado/requirements/05-implementation.html
+http://artifacts.opnfv.org/doctor/docs/requirements/05-implementation.html
 
 Use case
 """"""""
@@ -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.