...
ONAP target architecture (R2 and beyond):
Architecture Principles
ONAP Target Architecture
The target architecture are currently being developed by the tiger team using a set of design principles listed below. There principles were reviewed and agreed upon by the Architecture Subcommittee, See the link below for detailsWere Reviewed Earlier and Agreed Upon by the Architecture Team:
- ONAP is a layered architecture – Orchestration, Multi-Cloud, Controller, etc.
- Functional role of each layer should be well defined per the aforementioned architecture principles agreed by the architecture team (see the above link).
- ONAP should support integrated design studio to capture full life-cycle management models (TOSCA models for NF, simple / nested services augmented with BPMN, Policy / Analytic design models, etc.).
- ONAP Should Support Cloud Agnostic Model and Multi-Cloud adaption layer while hiding infrastructure details.
- ONAP Target Goal is: Modular, Model-driven, Microservices-based architecture.
- Models drive interfaces between layers/components.
- ONAP should define well-described and consistent NB-APIs at all layers.
- Keep flexible capability for commercial solution (no vendor lock-in).
- Agree to unified modeling for integration across all modules: VES in DCAE, Logging & monitor inside ONAP and more.
Architecture Tiger Team Weekly Meeting
...