This feature introduces the ability for independent deployment of the DCAE Components. In the past, all 10 existing DCAE Components were deployed as sub-charts of the dcaegen2 chart. We switched to using the Helm component model which allows us to control the deployment of each component by setting a corresponding value in an overrides file.
This feature is available in Frankfurt Release per OOM-1574 - Getting issue details... STATUS .
Use a helm override file (-f option to helm install) for managing dcae components. e.g.
helm install --debug local/dcaegen2 --name dev-dcae --namespace onap -f ~/dcae_frankfurt.yaml --timeout 900
File ~/dcae_frankfurt.yaml has the following contents:
dcae-bootstrap: enabled: true dcae-cloudify-manager: enabled: true dcae-config-binding-service: enabled: true dcae-healthcheck: enabled: true dcae-redis: enabled: true dcae-servicechange-handler: enabled: false dcae-inventory-api: enabled: true dcae-deployment-handler: enabled: true dcae-policy-handler: enabled: true dcae-dashboard: enabled: false
In this example, most dcae components will be deployed, but dcae-service-change-handler and dcae-dashboard would not be deployed because their enabled flag is false.
The resulting deployment should look similar to this:
