Page History

...

1. Component spec creation 
   1. Every component to be onboarded into DCAE, should prepare a component spec (a.k.a spec) - which is meta data represented in json describing the component configuration model. Details on spec creation can be found here - RTD spec  
2. Validation of spec and docker image using dcae_cli
1. The dcae_cli tools enables MS owner to validate the component spec and data_Formats created and also "test" the container deployment of MS itself. This allows components to mimic the configuration returned from ConfigBinding Service as expected on typical cloudify based deployment by DCAE platform (Documentation on spec format and tool usage can be found under RTD dcae_cli). There is also vagrant setup available which can be used to dcae_cli test/validation.
2. Once spec and data_formats are validated, add them under service component gerrit repo under following directory structure - dpo/spec, dpo/data-formats
3. Blueprint creation (manual for R4; new tool will be available post R4)
   1. Components developer can hand-craft the cloudify blueprints. For blueprint reference - check existing services k8s blueprint template under  - DCAE Blueprint repository (refer only to blueprint with prefix - "k8s-" for OOM deployment)
4. Validation of blueprint/deployment in DCAE environment on K8S
   1. The blueprint should be tested on any DCAE deployment by executing into DCAE bootstrap pod; instruction to deploy/validate via blueprint can be found here - Cloudify Blueprint validation under OOM
5. DCAE bootstrap deployment integration
   1. Add the new cloudify blueprint template on DCAE blueprint repository
   2. Add any corresponding inputs under OOM dcaegen2 bootstrap chart
   3. Once above are merged, update DCAE bootstrap to include Service part of OOM DCAE instantiation
      1. https://git.onap.org/dcaegen2/deployments/tree/k8s-bootstrap-container/bootstrap.sh
      2. https://git.onap.org/oom/tree/kubernetes/dcaegen2/charts/dcae-bootstrap/values.yaml

...