Controller/Platform Components
These are DCAE components which are responsible for LCM of DCAE services. This includes below
- Cloudify
- Deployment-handler
- ConfigbindingService
- InventoryAPI
- ServiceChange Handler
- Dashboard*
All the above component will be deployed as Helm chart for Dublin release (maintained under oom/kubernetes/dcaegen2)
DCAE Services
This include all service which provides data collection and analytics services; based on usecase - different collection and analytics components can be deployed. These are deployed and managed by the DCAE Platform.
For Dublin - DCAE services will be classified below for ONAP deployment standpoint.
Static Components
These are generic services used by ONAP integration team. These services are not binded to any specific usecase and require no dynamic policy configuration support.
- VESCollector
- HV_VES
- SNMPTrap
- Holmes Rules/Engine
- TCA
- PRH/Extension - 5G and BBS
Integration/Deployment steps should include below
- Component spec creation
- Validation of spec using dcae_cli
- Blueprint creation (manual for R4; new tool will be available post R4)
- Validation of blueprint/deployment in DCAE environment on K8S
- DCAE bootstrap deployment integration
- Define the new cloudify blueprint here - https://gerrit.onap.org/r/gitweb?p=dcaegen2/platform/blueprints.git;a=tree;f=blueprints;hb=refs/heads/master
- Add any corresponding inputs under OOM https://gerrit.onap.org/r/gitweb?p=oom.git;a=tree;f=kubernetes/dcaegen2/charts/dcae-bootstrap/resources/inputs;h=214a9cff1cb73a3367192ff595937e8a11be7fed;hb=refs/heads/master
- Once above are merged, update DCAE bootstrap to include Service part of OOM DCAE instantiation
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.
- RESTConf (New) - BBS
- DFC - 5G
- VES-Mapper (New) - BBS
- PM-Mapper (New) – 5G
- SON Handler (New) – 5G
- Heartbeat (New)
- TCA-GEN2* (New)
(* Stretch goal)
Onboarding/Deployment steps should include below
- Component spec creation
- Validation of spec using dcae_cli
- Blueprint and Policy Model creation (manual for R4; SDC/DCAE-DS post R4)
- Validation of blueprint/deployment in K8S
- SDC/CLAMP Integration
- Ensure new models/blueprints are in service gerrit repo (dpo/spec, dpo/data-formats, dpo/tosca_models, dpo/blueprints. Note: Both tosca_models and blueprint are temporary place holders.
- Work with Integration team/usecase owner to upload the artifacts (blueprints & policy model) into SDC and trigger Service creation and distribution from SDC.
- Work with CLAMP team to trigger the MS deployment.