ONAP Architecture Meeting 8/8 Chris Donley

Agenda Review Diagrams Terminology Prepare for joint use case/architecture meeting

ONAP Projects R1 (Lingli) OF E-Services BSS/OSS Big Data Usecase UI Portal OPEN-O UI (GUI/CLI) Run-time CLI Modeling (specs & Utilities) Integration VNF Requirements Security High Availability Documentation University Dashboard OA&M (VID) External Data Movement & APIs VID Design-time A&AI Service Orchestration Portal Framework SDC UI Server ESR VNF Design Service Design Common Service Workflow Design OOM DMaaP AAF Logging MSB CCSDK Policy Creation Policy Framework Alarm Correlation App (Holmes) Multi-Cloud Controllers Analytic Application Creation SDN-C APP-C VF-C ICE & Lab NFVO Recipie/ Engineering Rules & Policy Distribution DCAE G-VNFM Catalog Multi-VIM VNF SDK CLAMP Cloud & WAN OpenStack VMware RackSpace Azure From openECOMP From OPEN-O Convergence from both sides New 3rd Legend

Architecture Baseline for R1 (with projects) (Chris) ONAP Operations Manager Portal Frame- work ONAP CLI Run-time Modeling (Utilities) Integration VNF Requirements University VNF Validation Program Dashboard OA&M (VID) External API Framework Usecase UI A&AI Service Orchestration ESR Design-time SDC Common Services DMaaP CCSDK Logging App. Auth. Framework Microservice Bus Policy Frmwk SDN-C Alarm Correlation App (Holmes) APP-C VF-C VNF SDK DCAE Architecture Baseline for R1. SO and VFC PTLs to talk and see if they can make additional progress towards longer-term architecture in R1 timeframe Multi-VIM/Cloud Controller driver sVNFM/EMS driver CLAMP Cloud/VIM driver External components OpenStack VMware RackSpace Azure ...... Controller VNFM EMS VNFs

FUNCTIONAL Architecture for R2+ As presented in the Virt Dev Event Portal OPEN-O UI (GUI/CLI) Run-time Dashboard OA&M (VID) External Data Movement & APIs Design-time A&AI Service Orchestration SDC UI Server Service Design ESR VNF Design Interface Common Service Resource Orchestration (using ETSI terminology – will refine label) Workflow Design DMaaP Auth. Microservice Bus Policy Creation Analytic Application Creation Interface DCAE Alarm Correlation (Holmes) Policy SDN-C APP-C gvnfm Other? Recipie/ Engineering Rules & Policy Distribution Catalog NFV-O NFV Collector (Monitor) Multi-VIM/MultiCloud VNF SDK Cloud & WAN OpenStack VMware RackSpace Azure ...... Consensus on layered architecture. This picture does not imply project structure.

FUNCTIONAL Architecture for R2+ 1 set of proposed changes Portal OPEN-O UI (GUI/CLI) Run-time Dashboard OA&M (VID) External Data Movement & APIs Design-time A&AI Service Orchestration SDC UI Server ESR Needed? Interface VNF Design Service Design Common Service Resource Orchestration (using ETSI terminology – will refine label) Workflow Design DMaaP Auth. Microservice Bus Policy Creation Better Name? Analytic Application Creation DCAE Alarm Correlation (Holmes) Policy Interface … SDN-C APP-C gvnfm Other? Recipie/ Engineering Rules & Policy Distribution NFV-O NFV Collector (Monitor) Catalog Multi-VIM/MultiCloud VNF SDK Cloud & WAN OpenStack VMware RackSpace Azure ...... Consensus on layered architecture. This picture does not imply project structure.

FUNCTIONAL Architecture for R2+ 2nd set of proposed changes Portal OPEN-O UI (GUI/CLI) Run-time Dashboard OA&M (VID) External Data Movement & APIs Design-time A&AI Service Orchestration Domain Service Descriptors Domain Service Descriptors SDC UI Servr ESR VNF Design Service Design Common Service Resource Orchestration Workflow Design Domain Resource Descriptors Domain Resource Descriptors DMaaP Auth. Microservice Bus Policy Creation Analytic Application Creation DCAE Alarm Correlation (Holmes) … Policy Interface SDN-C APP-C vnfm Other? Recipie/ Engineering Rules & Policy Distribution NFV-O NFV Collector (Monitor) Catalog Multi-VIM/MultiCloud VNF SDK Cloud & WAN OpenStack VMware RackSpace Azure ...... Consensus on layered architecture. This picture does not imply project structure.

FUNCTIONAL Architecture for R2+ Chris’ proposed changes Portal (GUI/CLI) Run-time Dashboard OA&M (VID) External Data Movement & APIs Design-time A&AI Service Orchestration Domain Service Descriptors Domain Service Descriptors ESR SDC Common Service Resource Orchestration Domain Resource Descriptors Domain Resource Descriptors VNF SDK DMaaP Auth. Microservice Bus … CLAMP Policy DCAE Alarm Correlation (Holmes) … Multi-VIM/MultiCloud SDN-C APP-C (g/s) vnfm Other? Cloud & WAN OpenStack VMware RackSpace Azure ...... Consensus on layered architecture. This picture does not imply project structure.

Terminology Recent discussions have made clear the need for a common dictionary Terms used within the ONAP community (and the larger industry) are inconsistent and lead to misunderstandings The following slides are meant to stimulate discussion, and should not be considered “final”

Service Orchestration terminology Service Orchestration Functionality (SOF) [MEF-55]: The set of service management layer functionality supporting an agile framework to streamline and automate the service lifecycle in a sustainable fashion for coordinated management supporting design, fulfillment, control, testing, problem management, quality management, usage measurements, security management, analytics, and policy-based management capabilities providing coordinated end-to-end management and control of Layer 2 and Layer 3 Connectivity Services. Network Service Orchestration [IFA-009] Management of Network Services templates and VNF packages: Responsible for connectivity between VNFs, PNFs and any nested NSs (when applicable) i.e. VNF FGs and VLs by calling the respective ROs. Unaware of resources status in each administrative domain, it’s only aware of the resource capacity exposed by the various ROs. Service orchestration [Ciena] the execution of the operational and functional processes involved in designing, creating, and delivering an end-to-end service.

Resource Orchestration terminology Resource Orchestration [IFA-009] provides an overall view of the resources present in the administrative domain to which it provides access hides the interfaces of the VIMs present below it. regions/NFVI-Pop and resource groups defined by the various VIMs in the administrative domain are visible at the RO interface. aware of the resource usage and availability in the NFVI, of the logical grouping of the resource requirements e.g. per the VNF. acts only based on instructions from either the relevant VNFM or the relevant NSO, does not take decisions based on VNF instances or on NS instances Resource Orchestration [MANO] subset of NFV Orchestrator functions that are responsible for global resource management governance Infrastructure Orchestration [Michael Howard] Managing OpenStack for servers, storage, and switches

Control/Management terminology Infrastructure Control and Management (ICM) [MEF-55] The set of functionality providing domain specific network and topology view resource management capabilities including configuration, control and supervision of the network infrastructure. ICM is responsible for providing coordinated management across the network resources within a specific management and control domain. For example, a system supporting ICM capabilities provides connection management across a specific subnetwork domain. Such capabilities may be provided within systems such as subnetwork managers, SDN controllers, etc. Element Control and Management (ECM) [MEF-55] The set of functionality supporting element management layer capabilities for individual network elements. While a system supporting ECM capabilities provides for the abstraction of individual infrastructure elements, it may reflect the element view for multiple elements, but not provide coordinated management across the set of elements. Controller [Margaret Rouse, Techtarget] configure network devices and choose the optimal network path for application traffic

Suggestion Terminology used in ONAP should be industry-neutral, clear, and extensible across SDN/NFV/(future domains?) ARC to create and maintain glossary over time “Resource Orchestration” term appears specific to NFV domain, although concept extends to others -> suggest “domain orchestration” term

Straw Proposal Service Orchestration Domain Orchestration Management of end-to-end services across administrative and technology domains Domain Orchestration Management of network services and infrastructure inside a single administrative and technical domain Control/Management (“Controller”) Management of domain-specific resources supporting a single element (e.g., VNF, PNF, etc.). While a controller provides for the abstraction of individual infrastructure elements, it may reflect the element view for multiple elements.

FUNCTIONAL Architecture for R2+ With language update Portal (GUI/CLI) Run-time Dashboard OA&M (VID) External Data Movement & APIs Design-time A&AI Service Orchestration Domain Service Descriptors Domain Service Descriptors ESR SDC Common Service Domain Orchestration Domain Resource Descriptors Domain Resource Descriptors VNF SDK DMaaP Auth. Microservice Bus … CLAMP Policy DCAE Alarm Correlation (Holmes) … SDN-C APP-C (g/s) vnfm Other? Multi-VIM/MultiCloud Cloud & WAN OpenStack VMware RackSpace Azure ...... Consensus on layered architecture. This picture does not imply project structure.

Joint ARC/Use Case call Agenda present proposed R2 architecture and use cases Highlight differences Q&A to drive alignment Initial set of questions (for discussion) would the use case(s) require multi-site support? multi-region/multi-domain/federation? Multi-national? Do we need to consider enhanced networking features (e.g., underlays)? Can individual use cases be built from same components? (common APIs/models) What are the challenges from the first set of use cases? What technical debt have you identified? Clarify business drivers and capabilities of the use cases What are the functional commonalities between the use cases? Are there generic elements where we should focus?

New Jira site https://jira.onap.org/projects/ONAPARC/ Use to add and prioritize discussion topics