X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Fguides%2Fonap-developer%2Fsettingup%2Ffullonap.rst;h=86fc31cd143dcca7de257af8b588ce0e76464f54;hb=7b727a59bb7a41a2b477205ca2d57c12f236cdc5;hp=6d3d891da32216b8472403a87a503798470535a0;hpb=b57b15c83fe31d7663478dd2e8143d1e73e9700a;p=doc.git diff --git a/docs/guides/onap-developer/settingup/fullonap.rst b/docs/guides/onap-developer/settingup/fullonap.rst index 6d3d891da..86fc31cd1 100644 --- a/docs/guides/onap-developer/settingup/fullonap.rst +++ b/docs/guides/onap-developer/settingup/fullonap.rst @@ -18,13 +18,15 @@ **Context** =========== -ONAP may be deployed in different contexts depending on your requirements. The recommended installation for Amsterdam Release is currently based on OpenStack. +ONAP may be deployed in different contexts depending on your requirements. The recommended installation for Amsterdam Release is currently based on OpenStack HEAT Template. -Using the Amsterdam Release installer, ONAP components may be deployed in a single tenant or multiple tenants. One tenant for all the components except DCAE, and another tenant dedicated to the DCAE components. +Using the Amsterdam HEAT Template installer, ONAP can be deployed in a single tenant or multiple tenants. One tenant for all the components except DCAE, and another tenant dedicated to the DCAE components. -The VNFs managed by ONAP may be deployed in different OpenStack tenants or based on top of VMware based infrastructure (cf MultiCloud project). +The VNFs managed by ONAP may be deployed in different OpenStack tenants or based on top of VMware based infrastructure. For details, refer :ref:`to MultiCloud project`. -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 components deployed in High Availability mode. + +The installation requires some manual tasks to setup the DCAE components. **Requirements** ================ @@ -52,7 +54,7 @@ To deploy OpenStack, you can use various solutions: - `OPNFV Cross Community Continuous Integration - XCI installer `_ *Designate* component is usually not deployed using standard OpenStack installers. -Please find a guide to deploy and configure *Designate* +Use the procedure below to deploy and configure *Designate* .. toctree:: :maxdepth: 1 @@ -64,7 +66,7 @@ The OpenStack infrastructure must enable internet access. ONAP components --------------- -The following table presents the mapping between the created VM and the ONAP components, and provides informtaion about he VM (flavor and image): +The following table presents the mapping between the created VM and the ONAP components, and provides VM information (flavor and image): =================== ================= ======= ============ VM name ONAP project(s) Flavor Image @@ -107,15 +109,15 @@ The ONAP installation requires the following footprint: - 148 vCPU - 336 GB RAM - 3 TB Storage - - 29 floating IP + - 29 floating IP addresses -.. Note: the default flavor size may be optimized. The ONAP community is working to provide adpted flavors for basic ONAP installation. +.. Note: The default flavor size may be optimized. The ONAP community is working to update flavors of basic ONAP installation. -.. Note: you should also reserve some resourcse for the VNFs to be deployed. +.. Note: You should also reserve some resources for the VNFs to be deployed. Artifacts --------- -The following artifacts must be deployed on the OpenStack infrastructure. +The following artifacts must be deployed on the OpenStack infrastructure: - a public SSH key to access the various VM - private SSH key and public key SSH key for the DCAE VM - Ubuntu 14.04 image @@ -123,17 +125,17 @@ The following artifacts must be deployed on the OpenStack infrastructure. - CentOS 7 image - Set of flavors: small, medium, large, medium, large, xlarge, xxlarge -.. Note that floating IP may be private IP. +.. Note: The floating IP may be private IP. -.. Note Basic flavors can reuse the default flavors as defined by `OpenStack `_ - The xxlarge flavor should be confiured using the following values: 12 vCPU, 64 GB RAM and 120 GB storage. +.. Note: Basic flavors can reuse the default flavors as defined by `OpenStack `_ + The xxlarge flavor should be configured using the following values: 12 vCPU, 64 GB RAM and 120 GB storage. Security -------- The default installation assumes that the Default security group is configured to enable full access between the ONAP components. Depending on your environment, we may need to open some security groups (eg when using the portal from your desktop). -The list of various services and ports used can be found on the `ONAP wiki `_ +The list of various services and ports used can be found on the `ONAP wiki `_. **Deployment** ============== @@ -141,13 +143,19 @@ The list of various services and ports used can be found on the `ONAP wiki `_. Detect problems --------------- @@ -395,7 +406,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 @@ -417,7 +429,7 @@ To use the portal on your desktop, you must configure the following information aai.ui.simpledemo.onap.org -You can use the Horizon dashboard to get the IP adresses associated with the Virtual Machines or use the following command line: +You can use the Horizon dashboard to get the IP addresses associated with the Virtual Machines or use the following command line: .. code-block:: bash