Emerson Moura · Seminar Series Sponsor Event Sponsors Emerson Moura CALA Marketing Co-Chair, MEF...
23
Seminar Series Sponsor Event Sponsors Emerson Moura CALA Marketing Co-Chair, MEF Distinguished Systems Engineer, Cisco MEF's Lifecycle Service Orchestration (LSO) Reference Architecture and Framework
Transcript of Emerson Moura · Seminar Series Sponsor Event Sponsors Emerson Moura CALA Marketing Co-Chair, MEF...
Seminar Series Sponsor Event Sponsors
Emerson MouraCALA Marketing Co-Chair, MEF
Distinguished Systems Engineer, Cisco
MEF's Lifecycle Service Orchestration (LSO) Reference Architecture and Framework
25 min
2
What is MEF LSO?
• Lifecycle Service Orchestration (LSO) provides for the orchestrated management and control of Third Network Connectivity Services
• 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
3
MEF LSO Ecosystem Capabilities
4
Moving Up The Curve
Adaptive
DynamicAPI driven
Automation
10GE UNI
Standardized Ethernet Services
Layer 2 / 3 VPNs
Multiple Access Options
Low Latency
100GE UNI
Multi-CoS
SLAs Standardized Services
Faster Service Turn Up
E-Access
100G Transport
Real-Time PM
Programmable Cloud-Centric ModelFixed Connectivity Model
2004 2015 Future
Scal
able
, Dyn
amic
, Cu
sto
miz
ed, U
biq
uit
ou
s
Coordinated
5
Network as a Service - Single Domain
• Some service providers offer ….
– Fast service fulfillment
– Rich service feature sets
• But moving up the curve is…
– Costly and slow to add new features
– Limited to single domain
OSS/BSS/Orchestration
Fulfillment, Control,Performance, Assurance,
Usage, Analytics, Security, Policy
Retail Service Provider(Single Domain)
UserService Endpoint
UserService Endpoint
End-to-End Network as a Service
6
Adaptive
DynamicAPI driven
Automation
10GE UNI
Standardized Ethernet Services
Layer 2 / 3 VPNs
Multiple Access Options
Low Latency
100GE UNI
Multi-CoS
SLAs Standardized Services
Faster Service Turn Up
E-Access
100G Transport
Real-Time PM
Programmable Cloud-Centric ModelFixed Connectivity Model
2004 2015 Future
Scal
able
, Dyn
amic
, Cu
sto
miz
ed, U
biq
uit
ou
s
Coordinated
Single Domain Service Provider
1
Single Domain Service Provider
2
Single Domain Service Provider
3
Moving Up The Curve – Single Domain
7
Network as a Service – Multi Domain
• Manual processes between Operators dominate
• Limited feature sets
• Even slower to add new service features
• Exponential complexity for 3 or more Operators
End-to-End Network as a Service
Operator 1
Retail Service Provider(Multi-Operator)
Operator 2
UserService Endpoint
UserService Endpoint
OSS/BSS/Orchestration
Fulfillment, Control,Performance, Assurance,
Usage, Analytics, Security, Policy
OSS/BSS/Orchestration
Fulfillment, Control,Performance, Assurance,Usage, Analytics, Security, Policy
8
Adaptive
DynamicAPI driven
Automation
10GE UNI
Standardized Ethernet Services
Layer 2 / 3 VPNs
Multiple Access Options
Low Latency
100GE UNI
Multi-CoS
SLAs Standardized Services
Faster Service Turn Up
E-Access
100G Transport
Real-Time PM
Programmable Cloud-Centric ModelFixed Connectivity Model
2004 2015 Future
Scal
able
, Dyn
amic
, Cu
sto
miz
ed, U
biq
uit
ou
s
Coordinated
Moving Up The Curve - Multi-Domain
Multi Domain Service Provider
3
Operator 3A
Operator 3B
Multi Domain Service Provider
1
Operator 1A
Operator 1B Multi Domain Service Provider
2
Operator 2A
Operator 2B
9
LSO Helps to Bring It All Together
Cloud – Flexibility
and Scale
NFV – Network
Functionality
SDN – End-to-
End Control
Carrier Ethernet -
Connectivity
Infrastructure
and compute
for applications
and VNFs
Cost-effective,
flexible network
functionality
Automation and
streamlined
operations
Connectivity
between end-
points across a
WAN chaining
between VNFs to
form a service
10
Service Lifecycle Process Model (MEF 50)
Product Catalogue* Service Ordering*
Service Activation*
Performance Reporting (MEF 52)
Lifecycle Service Orchestration Helps to Bring It All Together
Fulfillment | Performance | Control | AssuranceUsage | Analytics | Security | Policy
* Future MEF Framework Specification
Service Qualification Questionnaire (MEF 53)
11
MEF LSO Ecosystem Capabilities
Lifecycle Services Orchestration
Design of E2E services and assignment of resources
Order and Request management and tracking
Coordination of all provisioning tasks
Testing orchestration and turn-up
Service delivery orchestration
E2E Fulfillment Orchestration
12
Service Lifecycle Process Model (MEF 50)
Product Lifecycle Service Operations Lifecycle
Market Analysis & Product Strategy
Product Design
Service & Resource Design
Product Launch
Marketing Fulfillment Response
Sales Proposal & Feasibility
Customer Order
Service Configuration &
Activation
Fault Management
Quality Management
Revenue Management
Service Termination
Serviceability
Fulfillment
Operation
MEF 50 leverages the TM Forum’s Business Process Framework, also referred to as the enhanced Telecom Operations Map (eTOM).
13
LSO-Related MEF Activities
MEF 6.2, 33, 51, 10.3, 26.2, etc.
MEF Service Definitions(including virtualization)
Common Information Models
LSO ReferenceArchitecture & Framework
Business Process Flows
Interface ProfilesAPI Specifications& Data Models
ReferenceImplementations
API ImplementationsCertifications
MEF 7.3, Common Model, Resource
Model,Cloud Services
MEF 50.x
Profiles for LSO Presto, LSO Legato, etc.
NRP, YANG, etc.
LSO Hackathon,
ODL project, OPNFV
MEF LSO Reference
Architecture& UNITE
NRP API Test Suite
Ops Area: Product Catalog, Ordering, Performance
Reporting, Serviceability
14
MEF 55: LSO Reference Architecture
Network Infrastructure
CustomerApplication Coordinator
Element Control and Management
Infrastructure Control and Management
Service Orchestration Functionality
Service Orchestration Functionality
PRESTO(SOF:ICM)
LEGATO(BUS:SOF)
Element Control and Management
Infrastructure Control and Management
ADAGIO (ICM:ECM)
LEGATO(BUS:SOF)
PRESTO(SOF:ICM)
ADAGIO (ICM:ECM)
Business Applications
Business Applications
SONATA(BUS:BUS)
INTERLUDE (SOF:SOF)
CANTATA(CUS:BUS)
ALLEGRO(CUS:SOF)
15
LSO Example with SDN and NFV
Subnetwork / WAN Managers
Network Infrastructure
NFV Infrastructure
NFVO
VNFM
VNF
EM
VIMSDN Infrastructure
CANTATA APIs
ALLEGRO APIs
End User Apps
End User Apps
SONATA APIs
INTERLUDE APIs
Partner Domain
Partner Domain
LSO Business Apps
(Commercial)
LSO Business Applications
LSO Service Orchestration Functionality
LSO Service Orchestration Functionality
SDN Controllers(ODL, ONOS & RHU)
SDN Controllers
PRESTO APIs PRESTO APIsPRESTO APIs
LEGATO APIs
ADAGIO APIsOpenFlow, ADAGIO and others
LSO Customer
ApplicationCoordinator
LSO Customer
ApplicationCoordinator
Subnetwork / WAN Managers
NFVO
16
LSO 2016 Work Items
• LSO RA (MEF 55) was approved in March 2016
• Work on next LSO RA Revision and / or Supplements– Detailed Operational Threads / Use Cases
– Details of Interface Reference Point Interactions
– Interface Reference Point Functional Requirements
– SOF Architecture and Functional Requirements
– Mappings: MEF 50 update; TM Forum APIs, etc.
– Definition of the role of OASIS TOSCA in LSO
– Analysis of information model layering for orchestration
– Relationship with ONF SDN & ETSI NFV
– OpenLSO for Cloud and OpenCS
17
• Definition– OpenLSO is a MEF-facilitated service orchestration ecosystem within which MEF
member companies collaborate to maximize the alignment of market implementations - both Open Source and proprietary - with MEF-defined LSO specifications.
– The objective of OpenLSO is to accelerate market adoption of LSO as defined by MEF in order to achieve fully-featured end to end service orchestration of MEF-defined service lifecycles.
• Objectives– Simplify and accelerate adoption of LSO specs for orchestration of Third Network
services
– Work towards APIs that are standardized and open
– Maximize alignment of LSO specifications and Open Source code for consistency with LSO use cases and capabilities
18
MEF Open Initiatives for Third Network Services
OpenCS Technology Domains
Third Network Services
OpenLSO Capabilities
Cloud Exchange
Data Center Optical Transport SD-WANNFVPacket WAN
Presto APIs
5G Wireless
Orchestrated Connectivity Services
E-Line E-LAN E-Tree E-Access
BIaaS SECaaS
Orchestrated Cloud Services
E-Transit
Internet Access L3 VPNs
IaaS SaaS PaaS UCaaS
IP Transit L4-L7 NFaaSWavelength
Fulfillment Performance Control Assurance Usage Analytics Security Policy
Sonata APIs
Interlude APIs
OpenLSO Capabilities – Fulfillment Project
• Fulfillment, in the context of LSO, refers to the set of service provider or operator activities and assets used to fulfill an order for a service provider from a customer.
• The objective of the project is to understand the requirements from future MEF specifications in order to support the fulfillment of a L2 or L3 VPN spanning multiple domains based on a variety of combinations of OpenLSO scenarios and of OpenCS use cases.
OpenLSO Capabilities – Analytics Project
• This OpenLSO Analytics project aims to provide examples of implementations of LSO Analytics, the benefits of integration into Third Network service user stories, and the requirements for additional specifications work in the MEF TOC.
• LSO Analytics also supports other LSO capabilities such as LSO Assurance and LSO Performance. The project aims to demonstrate examples of these inter-relationships via the LSO sub-architecture as defined in LSO Reference Architecture Phase 2.
21
Summary
• MEF’s Third Network:– Combining the best of Carrier Ethernet and the Internet
– Agile, Assured and Orchestrated!
• MEF’s LSO Vision: – Automation of each function of a Third Network service lifecycle
• LSO will enable:– Third Network’s Agile, Assured, and Orchestrated Services across multiple
network/operator domains
Q&A
Seminar Series Sponsor Event Sponsors
Emerson MouraCALA Marketing Co-Chair, MEF
Distinguished Systems Engineer, Cisco
MEF's Lifecycle Service Orchestration (LSO) Reference Architecture and Framework
25 min
