From 5adb1785ccc34775c9246d2fd675151f9ef1d8e3 Mon Sep 17 00:00:00 2001 From: Eric Debeau Date: Fri, 17 Nov 2017 20:34:11 +0000 Subject: [PATCH] Update the setting-up Indication of manual tasks to perform for DCAE components Suppress link to Rackspace Minor editorial changes Change-Id: I6a9ee260e3454b729b4539b9bb6cab26e6fbe2ce Issue-ID: DOC-153 Signed-off-by: Eric Debeau --- docs/guides/onap-developer/settingup/fullonap.rst | 25 +++++++++++++++++++---- 1 file changed, 21 insertions(+), 4 deletions(-) diff --git a/docs/guides/onap-developer/settingup/fullonap.rst b/docs/guides/onap-developer/settingup/fullonap.rst index 6d3d891da..48236bce6 100644 --- a/docs/guides/onap-developer/settingup/fullonap.rst +++ b/docs/guides/onap-developer/settingup/fullonap.rst @@ -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 installation requires some manual taks to setup the DCAE components. + **Requirements** ================ @@ -141,13 +143,19 @@ The list of various services and ports used can be found on the `ONAP wiki `_. + 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. -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 `_ +. In case some containers are missing, check the docker logs using the following command: .. code-block:: bash -- 2.16.6