ONAP Architecture Meeting 88 Chris Donley Agenda Review

ONAP Architecture Meeting 8/8 Chris Donley

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

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

Architecture Baseline for R 1 (with projects) (Chris) Run-time Usecase UI ONAP CLI Dashboard OA&M (VID) Design-time External API Framework Service Orchestration A&AI ESR Policy Frmwk App. Auth. Framework SDN-C Microservice Bus VF-C (NFV-O/ gvnfm) APP-C DCAE VNF SDK CLAMP Multi-VIM/Multi. Cloud & WAN Open. Stack VMware Rack. Space ONAP Operations Manager 4 Azure . . . University Alarm Correlation App (Holmes) Opt. Frmwk (OOF) Logging CCSDK VNF Requirements DMaa. P Integration Common Services Modeling (Utilities) SDC VNF Validation Program Portal Framework

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

1 set o f prop FUNCTIONAL Architecture for R 2+ OPEN-O UI (GUI/CLI) Portal Design-time SDC UI Server External Data Movement & APIs A&AI ESR Service Orchestration Policy Creation Analytic Application Creation Recipie/ Engineering Rules & Policy Distribution Catalog Common Service DMaa. P Interface Needed? Service Design Workflow Design hange s Run-time Dashboard OA&M (VID) VNF Design osed c Microservice Bus Auth. Alarm Correlation (Holmes) Resource Orchestration (using ETSI terminology – will refine label) Better Name? Interface … Policy DCAE SDN-C APP-C gvnfm NFV-O NFV Collector (Monitor) Multi-VIM/Multi. Cloud VNF SDK Cloud & WAN Open. Stack VMware Rack. Space Azure . . . Consensus on layered architecture. This picture does not imply project structure. 6 Other ?

2 nd se t of pr FUNCTIONAL Architecture for R 2+ OPEN-O UI (GUI/CLI) Portal d chan ges Run-time Design-time Dashboard OA&M (VID) SDC UI Servr VNF Design opose External Data Movement & APIs Service Orchestration A&AI ESR Domain Service Descriptors Service Design Workflow Design Policy Creation Analytic Application Creation Recipie/ Engineering Rules & Policy Distribution Catalog Common Service DMaa. P Microservice Bus Auth. Alarm Correlation (Holmes) Resource Orchestration Domain Resource Descriptors Interface … Policy DCAE SDN-C APP-C vnfm NFV-O NFV Collector (Monitor) Multi-VIM/Multi. Cloud VNF SDK Cloud & WAN Open. Stack VMware Rack. Space Azure . . . Consensus on layered architecture. This picture does not imply project structure. 7 Other ?

Chris’ FUNCTIONAL Architecture for R 2+ Portal d chan ges Run-time (GUI/CLI) Design-time propo se External Data Movement & APIs Dashboard OA&M (VID) Service Orchestration A&AI ESR Domain Service Descriptors SDC Resource Orchestration Common Service VNF SDK CLAMP DMaa. P Auth. Policy Microservice Bus Alarm Correlation (Holmes) Domain Resource Descriptors … … DCAE SDN-C APP-C (g/s) vnfm Multi-VIM/Multi. Cloud & WAN Open. Stack VMware Rack. Space Azure . . . Consensus on layered architecture. This picture does not imply project structure. 8 Other ?

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

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 Open. Stack for servers, storage, and switches 11

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 12

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 13

Straw Proposal • Service 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. 14

With l FUNCTIONAL Architecture for R 2+ Portal ge upd ate Run-time (GUI/CLI) Design-time angua External Data Movement & APIs Dashboard OA&M (VID) Service Orchestration A&AI ESR Domain Service Descriptors SDC Domain Orchestration Common Service VNF SDK CLAMP DMaa. P Auth. Policy Microservice Bus Alarm Correlation (Holmes) Domain Resource Descriptors … … DCAE SDN-C APP-C (g/s) vnfm Multi-VIM/Multi. Cloud & WAN Open. Stack VMware Rack. Space Azure . . . Consensus on layered architecture. This picture does not imply project structure. 15 Other ?

Joint ARC/Use Case call • Agenda - present proposed R 2 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? What are the multi-tenancy requirements? Do we need to consider enhanced networking features (e. g. , underlays)? 16

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