ONAP and MEF LSO External API Framework Functional Reference Architecture 12 July 2017 Andy Mayer, Ph.D. © 2016 AT&T Intellectual Property. All rights.

Slides:



Advertisements
Similar presentations
1 Introducing the Specifications of the Metro Ethernet Forum.
Advertisements

1 Introducing the Specifications of the Metro Ethernet Forum.
Gap Analysis of Simplified Use of Policy Abstractions (SUPA) Presenter: Jun Bi draft-bi-supa-gap-analysis-02 IETF 92 SUPA BoF Dallas, TX March 23, 2015.
1 Introducing the Specifications of the MEF MEF 50: Carrier Ethernet Service Lifecycle Process Model.
UNI Manager Project Proposal to OpenDaylight
TOSCA Monitoring Reference Architecture Straw-man Roger Dev CA Technologies March 18, 2015 PRELIMINARY.
Page 1 Accounting Management in a TINA- Based Service and Network Environment Patrick Hellemans, Cliff Redmond, Koen Daenen, Dave Lewis IS&N 99 - Barcelona.
GEN15 LSO Hackathon. Session Topics LSO Hackathon vision (GEN15 and beyond) GEN15 LSO/CE 2.0 oriented scope (review of the diagram) and defined outputs.
Independent Insight for Service Oriented Practice Summary: Service Reference Architecture and Planning David Sprott.
WELCOME TO THE Presenter Name Presenter Name Jack Pugaczewski
Open Source and Info Models 17 Dec 2015 Bryan Sullivan, AT&T.
14 March 2016 Bryan Sullivan, AT&T Artur Tyloch, Canonical
ONAP SD-WAN Use Case Proposal.
Bryan Sullivan, AT&T June 13, 2017
Master Service Orchestrator (MSO)
Orchestration and Controller Architecture Alignment Vimal Begwani AT&T
Rationalizing ONAP Architecture for R2 and Beyond Vimal Begwani – AT&T
Euro17 LSO Hackathon Open LSO Analytics
ONAP layering/MEF alignment
Defining ONAP APIs With BSS/OSS
MEF Modeling Activities
ONAP Architecture Meeting 8/8
LSO Hackathon Kickoff Charles Eckel.
Lifecycle Service Orchestration (LSO) Models in context
Orchestration and Controller Alignment for ONAP Release 1
ONAP Architecture Slides Current Plan of Record
MEF Common Information Model Overview
Aligning Orchestration and Controller Per Merger Agreement Vimal Begwani – AT&T Jamil Chawki – Orange Alla Goldner -- Amdocs.
AT&T Marketplace for Enterprise MEF Hackathon
OPEN-O Modeling Directions (DRAFT 0.6)
Defining ONAP VNF Package Model
Tina Tsou, Bryan Sullivan,
Aligning Orchestration and Controller Per Merger Agreement Vimal Begwani – AT&T Jamil Chawki – Orange Alla Goldner -- Amdocs.
Network instantiation
ONAP and SD-WAN Integration Proposal
ONAP Interface to External Controllers
ONAP Architecture Meeting 8/8
IEEE 802 OmniRAN Study Group: SDN Use Case
OPEN-O Modeling Directions (DRAFT 0)
MEF Modeling Activities
LSO Hackathon Kickoff Charles Eckel.
MEF Q2, April Frankfurt, Germany
ONAP Integration Through Information and Data Modeling
MEF LSO Legato SDK 24 October 2017 Andy Mayer, Ph.D. Tara Cummings.
ONAP Integration to External Domain Management Systems (DMS)
LSO Hackathon Summary Charles Eckel, Cisco DevNet.
17 Dec 2015 Bryan Sullivan, AT&T
Using the MEF Core Model in ONAP John Strassner, Ph. D. Andy Mayer, Ph
Use Cases and Requirements for I2NSF_
ONAP – Centralised Parser Distribution Atul Purohit - Vodafone
Intent Based Orchestration for Applications
ONAP APIs Andrew Mayer, AT&T
MEF 3.0.
ONAP Amsterdam Architecture
ONAP Integration Through Information and Data Modeling
TMF Information Framework
Consideration of Modeling Evolution in ONAP Michela Bevilacqua Peter Wörndle and Tara Cummings 13 December , 2017.
SDN use case 1: VPN Fengkai Li.
TMF Information Framework
MEF API Development Approach
Introducing the Specifications of the MEF
Documenting ONAP components (functional)
ONAP Beijing Architecture Chris Donley 1/9/18
Unified Modeling Language
Phaethon: a lightpath provisioning adapter for LightSoft
Defining ONAP VNF Package Model
ONAP Information Model Topics Timeline
Candidate for ONAP Dublin Implementation 5G RAN E2E Slice Design, Deploy and Manage 5G Use Case Team.
Karthik Sethuraman, NEC
Architecture Face to Face Planning Meeting ONAP Architecture – Modeling Inter-Relationship Andy Mayer; Deng Hui.
Presentation transcript:

ONAP and MEF LSO External API Framework Functional Reference Architecture 12 July 2017 Andy Mayer, Ph.D. © 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.

About MEF 55 (What is LSO?) LSO provides for the orchestrated management and control of Third Network Connectivity Services across all internal and external network domains from one or more network operators LSO Reference Architecture characterizes the management and control domains and entities that enable the cooperative LSO capabilities LSO overcomes existing complexity by defining product, service, and resource abstractions that hide the complexity of underlying technologies and network layers from the applications and users of the services Within each provider domain, the infrastructure may be implemented with WAN technologies, as well as NFV and/or SDN Not only dramatically decreases the time to establish and modify the characteristics of the Connectivity Service, but also assure the overall service quality and security for these services

LSO Engineering Methodology MEF 6.2, 33, 51, 10.3, 26.2, etc. MEF Service Definitions (including virtualization) Common Information Models LSO Reference Architecture & Framework Business Process Flows Interface Profiles API Specifications & Data Models Reference Implementations API Implementations Certifications MEF 7.3, Common Model, Resource Model, Cloud Services MEF 50 Profiles for Presto, Lagato, etc. SCA, YANG, etc. LSO Hackathon, ODL project, OPNFV MEF LSO Reference Architecture & UNITE SCA API Test Suite SOC: Product Catalog, Ordering, Performance Reporting, Serviceability

Business Applications Business Applications REFERENCE ARCHITECTURE Customer Domain SP Domain Partner Domain Cantata (CUS:BUS) Business Applications Business Applications Sonata (BUS:BUS) Customer Application Coordinator LEGATO (BUS:SOF) LEGATO (BUS:SOF) Service Orchestration Functionality Interlude (SOF:SOF) Service Orchestration Functionality Allegro (CUS:SOF) Presto (SOF:ICM) Presto (SOF:ICM) Infrastructure Control and Management Infrastructure Control and Management ADAGIO (ICM:ECM) ADAGIO (ICM:ECM) Element Control and Management Element Control and Management Network Infrastructure

LSO Management View Abstractions Service View Element & Equipment Element Control & Management Service Orchestration & Infrastructure Management (Subnetwork) LSO RA Context Information Class Examples per Management Abstraction View Network Element Card Product Offering Logical Termination Point Forwarding Construct Port Service Orchestration (Provider domains & multi-domain) Business Apps Product View Catalog Customer Link Network & Topology Service Server Facility Fabric Management Abstractions Service Spec Forwarding Domain VNF Resource View Spec Instance Service Component Service Access Point Route Cross Connect VNE Interface

LSO RA Phase 2 Deliverables Description Deliverable 1 Operational Threads and Interface Reference Points Deliverable 2 Architectural Relationship with ONF SDN & ETSI NFV Deliverable 3 SOF Sub-Architecture and Functional Requirements Deliverable 4 LSO Mappings (MEF 50.1, TM Forum APIs) Deliverable 5 Definition of the role of OASIS TOSCA in LSO Deliverable 6 Analysis of information model layering for orchestration Deliverable 7 LSO Security Framework Deliverable 8 Policy-Driven Orchestration

SOF Interface Reference Points Service feasibility; Service configuration & activation; Usage events & metrics; Service performance & quality; Service policy LEGATO Dynamic service control; Service state info; Service performance & quality; Service related alerts; Service Orchestration Functionality Dynamic service control; Service parameter config; Service state info; Service performance info; Service problem alerts ALLEGRO INTERLUDE PRESTO Connectivity and network function feasibility; Configuration, activation, and management of connectivity and logical network functions; Topology and routing; Performance and Fault; Connectivity policy

Business Applications Business Applications ONAP / LSO Relationship Customer Domain SP Domain Partner Domain Cantata (CUS:BUS) Business Applications Business Applications Sonata (BUS:BUS) Customer Application Coordinator LEGATO (BUS:SOF) LEGATO (BUS:SOF) ONAP ONAP Service Orchestration Functionality Interlude (SOF:SOF) Service Orchestration Functionality Allegro (CUS:SOF) Presto (SOF:ICM) Presto (SOF:ICM) Infrastructure Control and Management Infrastructure Control and Management ADAGIO (ICM:ECM) ADAGIO (ICM:ECM) Element Control and Management Element Control and Management Network Infrastructure

MEF Interface Reference Points & ONAP (need updated arch diagram) Interlude (SOF:SOF) Allegro (CUS:SOF) LEGATO (BUS:SOF) Presto (SOF:ICM)

LSO RA Phase 2 Operational Threads Detailed Operational Threads / User Stories for: Partners on-boarding (to be defined) Product Ordering and Service Activation Orchestration Controlling a Service Customer Viewing Service Performance and Fault Reports and Metrics Placing and Tracking Trouble Reports Assessing Service Quality Based on SLS Collection and Reporting of Billing and Usage Securing Management and Control Mechanisms (to be defined) Providing Connectivity Services for Cloud (to be defined)

LSO RA Phase 2 Operational Threads

Describe Target Use Cases & Interactions (Example) Serviceability and Ordering

Next Steps Describe each of the MEF LSO Interface Reference Points (IRPs) within the ONAP context. For each IRP provide the functional description of target ONAP capabilities for interactions Describe deployment scenarios Use ONAP Use Cases as the basis for identifying key external interactions & apply MEF LSO Operational Threads

BACKUP MATERIAL © 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.