Lead: Parviz Yegani
Mailing list: onap-arch-tiger-team (email Parviz or Chris)
ONAP target architecture (R2 and beyond):
ONAP Target Architecture
The target architecture is currently being developed by the tiger team using a set of design principles listed below. These principles were reviewed and agreed upon by the Architecture Subcommittee, See the link below for details:
- ONAP is a layered architecture – Orchestration, Multi-Cloud, Controller, etc.
- Functional role of each layer should be well defined per the aforementioned architecture principles.
- 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.
Below is the latest R2+ architecture deck. It's also located at: https://wiki.onap.org/display/DW/Contributions
- py20180109 ONAP R2+ Architecture Proposal
- py20180102 ONAP R2+ Architecture Proposal
Architecture Tiger Team Weekly Meeting
Meeting Information (Fridays):
UTC 03:00 PM | China 11:00 PM | Eastern 10:00 AM | Pacific 07:00 AM |
IRC: TBA
US numbers:
+1 646 558 8656 or +1 669 900 6833
Meeting ID: 761 325 550
International numbers available: https://zoom.us/zoomconference?m=D_WZofsWmNr8ZvyR_5uMQv1i2yKSoUpS
Agenda - ONAP Architecture Tiger Team Call (12-JAN-2018)
Agenda - ONAP Architecture Tiger Team Call (08-JAN-2018)
Agenda - ONAP Architecture Tiger Team Call (22-DEC-2017)