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

Compare with Current View Page History

« Previous Version 4 Next »

Topic Leader(s)

Topic Description

75m, Ranny Haiby

  • EMCO/ONAP Architecture alignment Deep Dive

Topic Overview

Slides & Recording


Agenda


  • EMCO/ONAP Architecture alignment Deep Dive
    • Part 1: On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
      • Infrastructure→Applications>Onboarding>MANO>Infrastructure (end-to-end)
    • Appropriate use cases for EMCO and ONAP, when to use them separately and or together
    • The teams have identified two fundamental configurations, each ideally suited for different high level use cases
      • ONAP is the centralized Service Orchestrator, Service Assurance and Automation Framework, with EMCO fulfilling specific roles as a component (multi cluster support, etc)
      • EMCO is the distributed edge focused Service Orchestrator, with select ONAP Service Assurance components configured as needed.
    • We can draw from the following examples and other supporting material during this session to describe the rationale
    • Review of the EMCO_ONAP Alignment Proposal PPT.
    • Lessons learned from:
    • EMCO team overviews the rationale for, deploying an app/service such as Magma as the primary SO
    • Given the different configurations , how can the 5G SBP program demonstrate and delineate the rationale for the two configurations?

Minutes

Presentation:  LFN DTF_EMCO_ONAP Alignment Proposal_V3.pptx

  • Presentation walk-thru
    • Two "variations" for the integration
      • Variation 1 - "SDO inspired"
      • Variation 2- 

Action Items

  •  
  • No labels