Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 102 Next »

Lead: Parviz Yegani

Mailing list: onap-arch-tiger-team (email Parviz or Chris)

ONAP target architecture (R2 and beyond): 

ONAP End-to-End Architecture 

The end-to-end architecture of the ONAP platform is currently being developed by the tiger team using a set of design principles listed below: 

  • 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.

These principles were reviewed and agreed upon by the Architecture Subcommittee. You can find the details here.

Below slide deck provides the latest ONAP architecture for R2 and beyond. This is work in progress. These slides are also available at the Architecture (ARC) Subcommittee contributions page: https://wiki.onap.org/display/DW/Contributions

Architecture Tiger Team Weekly Meeting

Meeting Information (Fridays):

UTC 03:00 PMChina 11:00 PMEastern 10:00 AMPacific 07:00 AM
  • IRC: TBA

Meeting Agenda + Notes:

Tiger Team Contributions:


  • No labels