summaryrefslogtreecommitdiffstats
path: root/docs/sections/configuration.rst
diff options
context:
space:
mode:
authorVENKATESH KUMAR <vv770d@att.com>2020-04-22 17:31:32 -0400
committerVENKATESH KUMAR <vv770d@att.com>2020-04-27 12:09:51 -0400
commit7cfaea2ee5e73a5a0a669da3b8c949000245cb83 (patch)
tree579f20962a4c23380ddd67b24edcd4de6ed1fd06 /docs/sections/configuration.rst
parent06d45b681f12fcb88fcca76bcc6170eaf020560b (diff)
dcae r6 doc updates cont.
Change-Id: I2303d59ad9491c555adb70de57eb14ab1fa7233c Signed-off-by: VENKATESH KUMAR <vv770d@att.com> Issue-ID: DCAEGEN2-1891 Signed-off-by: VENKATESH KUMAR <vv770d@att.com>
Diffstat (limited to 'docs/sections/configuration.rst')
-rw-r--r--docs/sections/configuration.rst52
1 files changed, 29 insertions, 23 deletions
diff --git a/docs/sections/configuration.rst b/docs/sections/configuration.rst
index 22e77d18..b62a5406 100644
--- a/docs/sections/configuration.rst
+++ b/docs/sections/configuration.rst
@@ -6,19 +6,23 @@ Configuration
DACEGEN2 platform is deployed via helm charts. The configuration are maintained as on values.yaml and can be updated for deployment if necessary.
-The following components are migrated to helm chart part of Dublin release.
+For Frankfurt release, the helm charts for each platform component can be controlled via separate override file
+https://wiki.onap.org/pages/viewpage.action?pageId=71837415
+
+
-ConfigBindingService
.. csv-table::
:header: "Component", "Charts"
:widths: 22,100
- "ConfigBinding Service", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/charts/dcae-config-binding-service"
- "Deployment Handler", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/charts/dcae-deployment-handler"
- "Policy Handler", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/charts/dcae-policy-handler"
- "ServiceChangeHandler", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/charts/dcae-servicechange-handler"
- "Invetory", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/charts/dcae-servicechange-handler/charts/dcae-inventory-api"
+ "Cloudify", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/components/dcae-cloudify-manager"
+ "ConfigBinding Service", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/components/dcae-config-binding-service"
+ "Deployment Handler", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/components/dcae-deployment-handler"
+ "Policy Handler", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/components/dcae-policy-handler"
+ "ServiceChangeHandler", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/components/dcae-servicechange-handler"
+ "Inventory", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/components/dcae-inventory-api"
+ "Dashboard", "https://git.onap.org/oom/tree/kubernetes/dcaegen2/components/dcae-dashboard"
@@ -43,32 +47,34 @@ In addition, for DCAE components deployed through Cloudify Manager blueprints, t
* The blueprint input files may contain Helm templates, which are resolved into actual deployment time values following the rules for Helm values.
-Now we walk through an example, how to configure the Docker image for the DCAE dashboard, which is deployed by Cloudify Manager.
+DCAE Service components are deployed via Cloudify Blueprints. Instruction for deployment and configuration are documented under https://docs.onap.org/en/latest/submodules/dcaegen2.git/docs/sections/services/serviceindex.html
-In the ``k8s-dashboard.yaml-template`` blueprint template, the Docker image to use is defined as an input parameter with a default value:
+Now we walk through an example, how to configure the Docker image for the DCAE VESCollector, which is deployed by Cloudify Manager.
-.. code-block:: yaml
+In the `k8s-ves.yaml <https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-ves.yaml>`_ blueprint, the Docker image to use is defined as an input parameter with a default value:
- dashboard_docker_image:
- description: 'Docker image for dashboard'
- default: 'nexus3.onap.org:10001/onap/org.onap.ccsdk.dashboard.ccsdk-app-os:1.1.0-SNAPSHOT-latest'
+.. code-block:: yaml
-Then in the input file, ``oom/kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs/k8s-dashboard-inputs.yaml``,
+ tag_version:
+ type: string
+ default: "nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.ves.vescollector:1.5.4"
+
+The corresponding input file, ``https://git.onap.org/oom/tree/kubernetes/dcaegen2/components/dcae-bootstrap/resources/inputs/k8s-ves-inputs-tls.yaml``,
it is defined again as:
.. code-block:: yaml
+ {{ if .Values.componentImages.ves }}
+ tag_version: {{ include "common.repository" . }}/{{ .Values.componentImages.ves }}
+ {{ end }}
+
- dashboard_docker_image: {{ include "common.repository" . }}/{{ .Values.componentImages.dashboard }}
-
-Thus, when ``common.repository`` and ``componentImages.policy_handler`` are defined in the ``values.yaml`` files,
-their values will be plugged in here and the resulting ``policy_handler_image`` value
-will be passed to the Policy Handler blueprint as the Docker image tag to use instead of the default value in the blueprint.
+Thus, when ``common.repository`` and ``componentImages.ves`` are defined in the ``values.yaml`` files,
+their values will be plugged in here and the resulting ``tag_version`` value
+will be passed to the blueprint as the Docker image tag to use instead of the default value in the blueprint.
-Indeed the ``componentImages.dashboard`` value is provided in the ``oom/kubernetes/dcaegen2/charts/dcae-bootstrap/values.yaml`` file:
+The ``componentImages.ves`` value is provided in the ``oom/kubernetes/dcaegen2/charts/dcae-bootstrap/values.yaml`` file:
.. code-block:: yaml
componentImages:
- dashboard: onap/org.onap.ccsdk.dashboard.ccsdk-app-os:1.1.0
-
-DCAE Service components are deployed via Cloudify Blueprints. Instruction for deployment and configuration are documented under https://docs.onap.org/en/latest/submodules/dcaegen2.git/docs/sections/services/serviceindex.html
+ ves: onap/org.onap.dcaegen2.collectors.ves.vescollector:1.5.4