diff options
Diffstat (limited to 'docs/sections/installation_oom.rst')
| -rw-r--r-- | docs/sections/installation_oom.rst | 24 |
1 files changed, 15 insertions, 9 deletions
diff --git a/docs/sections/installation_oom.rst b/docs/sections/installation_oom.rst index 1715237c..bd1b752d 100644 --- a/docs/sections/installation_oom.rst +++ b/docs/sections/installation_oom.rst @@ -1,14 +1,14 @@ .. This work is licensed under a Creative Commons Attribution 4.0 International License. .. http://creativecommons.org/licenses/by/4.0 -Helm Chart Based DCAE Deployment -================================ +DCAE Deployment (using Helm and Cloudify) +========================================= This document describes the details of the Helm chart based deployment process for R4 ONAP and how DCAE is deployed through this process. -ONAP Deployment Overview ------------------------- +Deployment Overview +------------------- ONAP R4 extends the Kubernetes deployment method introduced in R2 and continued in R3. Kubernetes is a container orchestration technology that organizes containers into composites of various patterns for easy deployment, management, and scaling. @@ -24,10 +24,16 @@ and invokes Kubernetes deployment operations for all the resources. All ONAP Helm charts are organized under the **kubernetes** directory of the **OOM** project, where roughly each ONAP component occupies a subdirectory. DCAE charts are placed under the **dcaegen2** directory. +In Dublin, all DCAE platform components (exception of Dashboard) have corresponding Helm chart which will be used to trigger the deployment. +All DCAE Services are deployed through Cloudify Blueprint. The default ONAP DCAE deployment includes small subset of DCAE services deployed through Bootstrap pod to meet +ONAP Integration usecases. Optionally operators can deploy on-demand other MS required for their usecases as described in `On-demand MS Installation +<installation_MS_ondemand>`_. + The PNDA data platform is an optional DCAE component that is placed under the **pnda** directory. Details for how to configure values to enable PNDA installation during Helm install -are described in `Installing PNDA During Helm Chart Based DCAE Deployment -<installation_pnda>`. +are described in `Installing PNDA through Helm Chart +<installation_pnda>`_. + DCAE Chart Organization ----------------------- @@ -143,7 +149,7 @@ Now we walk through an example, how to configure the Docker image for the DCAE d In the ``k8s-dashboard.yaml-template`` blueprint template, the Docker image to use is defined as an input parameter with a default value: -.. code-block:: +.. code-block:: yaml dashboard_docker_image: description: 'Docker image for dashboard' @@ -152,7 +158,7 @@ In the ``k8s-dashboard.yaml-template`` blueprint template, the Docker image to u Then in the input file, ``oom/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-dashboard-inputs.yaml``, it is defined again as: -.. code-block:: +.. code-block:: yaml dashboard_docker_image: {{ include "common.repository" . }}/{{ .Values.componentImages.dashboard }} @@ -162,7 +168,7 @@ will be passed to the Policy Handler blueprint as the Docker image tag to use in Indeed the ``componentImages.dashboard`` value is provided in the ``oom/kubernetes/dcaegen2/charts/dcae-bootstrap/values.yaml`` file: -.. code-block:: +.. code-block:: yaml componentImages: dashboard: onap/org.onap.ccsdk.dashboard.ccsdk-app-os:1.1.0 |