Existing infrastructure that is available in ONAP
•Use SDC for onboarding management applications if they are independent of VNF Or make management app also part of VNF if it needs to be dynamic
•Use SO to bring up the management app like any other VNF
•Leverage MC for talking to various cloud-regions of different technologies (Management App as VM or container or public cloud entity)
•Leverage OOF to make placement decisions (such as HPA, affinity, anti-affinity) | EOM: ECOMP Subsystem that deploys and
manages the lifecycle of ECOMP and all
software required to make it operational,
including scaling and self-healing
▪ EOM merges the functionality of:
▪ ECOMP-C developed by AT&T
▪ DCAE-C developed by AT&T
▪ DCAE-C from ONAP
▪ ONAP OOM (TOSCA) & HELM Plugin
▪ CCSDK (ONAP)
▪ Single code base
▪ Continuous process of insourcing / opensourcing between ONAP and EOM | Cloud Native K8S Ecosystem - https://landscape.cncf.io/ ONAP OOM Project - Prescriptive Helm Charts for various ONAP management plane components |
