Introduction

DCAE Transformation was multi-release intiative to simplify DCAE architecture and align with Cloudnative function/technologies to manage DCAE services. With completion of DCAE Architecture transformation to Helm, several of platform components has been retired in Jakarta release. Following page capture the resource optmization/saving made with this feature. 

Realization Path

• Honolulu release (Phase 1)
  • REQ-479  Introduction of Helm SVC template for DCAE components; migrate bootstrap services to helm (DCAEGEN-2488); Cloudify remained primary orchestration for dynamic deployments (MOD/CLAMP flows)
• Istanbul release (Phase 2)
  • REQ-685   Extend DCAE SVC template to provide more generic capabilities; migrate all remaining DCAE svc to helm and change default DCAE Svc deployment to Helm (instead of Cloudify)
• Jakarta release (Phase 3) 
  • REQ-1038  Integrate MOD to support helm flows; remove Cloudify & platform components from ONAP/DCAE deployments. Extend SVC template to support add-on capabilities and complete component CBS SDK migration for removing Consul (and CBS) dependency

Architecture

Deployment Optimization

With platform dependency removed completely in Jakarta release, there is significant improvement in microservice deployment.  DCAE component dependencies are identified within respective DCAE charts and install of DCAE bootstrap can now be completed under 3 min (for locally available images)

• Istanbul: Platform component/Handlers required to be up & running prior to DCAE Services component deployment
• Jakarta: MS deployment are uniquely handled and controlled via independent charts

Resouce Optimization

    CPU utilization reduced by ~75% among bootstrapped DCAE components

    Memory utilization reduced by ~60%

  (see stats below)

 DCAE Jakarta release deployment can be done on single node/cluster (8 core and 16GB) along with other ONAP component dependencies (e.g DMAAP, AAF)

Stats Report 

UNH Lab

Windriver Lab