Page History

...

Integration/Deployment steps should include below

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

...

1. 1. 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. Blueprint

...

1. 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)
2. 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
3. DCAE bootstrap deployment integration

   ...

   1. 1. Add the new cloudify

   ...

   1. 1. blueprint template on DCAE blueprint repository
      2. Add any corresponding inputs under OOM

   ...

   1. 1. dcaegen2

   ...

   1. 1. bootstrap chart
      2. 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

   Dynamic Components

   These services are deployed on-demand (either from CLAMP or Dashboard); requires dynamic policy configuration management support.  Services involved in control loop flow will generally fall under this classification.

   ...

   Onboarding/Deployment steps should include below

   
   

   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

   ...

   1. 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. 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)
   3. Policy Model creation (using SDC Tosca_lab)
      1. Policy model creation require policy schema definition in spec specifying the structure of configuration to be exposed in policy. Follow Tosca Lab Tool Instructions to generate the policy models
      2. Verify with policy team if the created policy model conforms to the specification Policy team expects
      Note: Rest of models (schema/template/translate) are not compatible to K8S deployment;  Tosca_lab version in SDC will be updated in Dublin to align/support DCAE k8s model. 
   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. SDC/CLAMP Integration

      ...

      1. 1. Add the new models/blueprints

      ...

      1. 1. in service component gerrit repo

      ...

      1. 1. under following directory structure - dpo/spec, dpo/data-formats, dpo/tosca_models, dpo/blueprints.
            1. Note: Both tosca_models and blueprint are temporary place holders for Dublin.
         2. Work with Integration team/usecase owner to upload the artifacts (blueprints & policy model) into SDC and trigger Service creation and distribution from SDC.
         3. Work with CLAMP team to configure the policy and trigger the MS deployment.