-
Story
-
Resolution: Unresolved
-
Medium
-
None
-
None
As part of Architecture Subcommittee's ONAP Modularity, this epic specifies initial steps on how the Controller framework in CCSDK is to be decomposed and simplified.
- Enable controller personas to be created
- Decouple data layer from controller application layer utilizing platform data management's DBaaS
- Migrate select current controller functions to become ONAP platform’s common services for the other ONAP Components to utilize (IP Address Assignment, Model Parser, Ansible Server are Dublin candidate common services)
- Pivot to a microservices approach that enables select modules in the Controller to auto-heal and auto-scale as load increases (candidates: NB API handler, some SB adapters, DG/service logic)
see this link for detail: ONAP_Modularization_ATT_Huawei_10_26_2018_Final.pdf
- relates to
-
ONAPARC-301 Modularity within ONAP components
- Open