@@ -26,6+26,8 @@ The VNFs managed by ONAP may be deployed in different OpenStack tenants or based
The current installation is based on the single tenant deployment (all the ONAP components will be hosted in a unique tenant) with DCAE componntes deployed in High Availability mode.
The current installation is based on the single tenant deployment (all the ONAP components will be hosted in a unique tenant) with DCAE componntes deployed in High Availability mode.
+The installation requires some manual taks to setup the DCAE components.
+
**Requirements**
================
**Requirements**
================
@@ -141,13+143,19 @@ The list of various services and ports used can be found on the `ONAP wiki <http
.. Note The Heat template deployment may take time (up to one hour) depending on your hardware environment.
.. Note The Heat template deployment may take time (up to one hour) depending on your hardware environment.
+Deploy DCAE
+-----------
+The HEAT template deployed the onap-dcae-bootstrap virtual machine.
+
+.. Note To provide the manual tasks to configure the local environment
+
Test the installation
---------------------
Test the installation
---------------------
-Every ONAP component offers a HealthCheck REST API. The *Robot Virtual Machine* can be used to test that every components run smoothly.
+Every ONAP component offers a HealthCheck REST API. The Robot Virtual Machine (*onap-robot*) can be used to test that every components run smoothly.
Run the following command to perform the HealthCheck:
.. code-block:: bash
Run the following command to perform the HealthCheck:
.. code-block:: bash
@@ -387,6+401,8 @@ Run the following command to perform the HealthCheck:
This testsuite will execute 30 tests towards the various ONAP components.
This testsuite will execute 30 tests towards the various ONAP components.
+After the installation, it is possible to deploy the various use-cases described `ONAP wiki <https://wiki.onap.org/display/DW/Running+the+ONAP+Demos>`_.
+
Detect problems
---------------
If all the tests are not OK, many causes are possible.
Detect problems
---------------
If all the tests are not OK, many causes are possible.
@@ -395,7+411,8 @@ Here is a simple procedure to detect where the problem occurs:
* Check the OpenStack Virtual Machine logs
* Connect to the Virtual Machine and check that the various containers are running.
* Check the OpenStack Virtual Machine logs
* Connect to the Virtual Machine and check that the various containers are running.
-The list of containers are described in the following section. In case some containers are missing, check the docker logs using the following command:
+The list of containers are described on the `ONAP wiki <https://wiki.onap.org/display/DW/ONAP+Services+List#ONAPServicesList-ONAPServices>`_
+. In case some containers are missing, check the docker logs using the following command: