industry collaboration for open lifecycle service orchestration … · 2018-05-29 · industry...
TRANSCRIPT
Industry Collaboration for Open Lifecycle Service Orchestration (LSO) APIs
Dan Pitt [email protected] www.mef.net
OCP Summit, March 21, 2018
Outline
• Who we are & what we’re up to (and why it matters to OCP)
• MEF 3.0
• LSO: abstractions & realities
• Community, open source (SW & HW), proof points, OCP
MEF: Who, What, How
1. Who: 200+ Communication service providers, vendors (enterprises)
2. What: Agile, assured, orchestrated, revenue-producing services
3. How: Service definitions, LSO APIs, certification, community
Fiber/Copper Access
Network
Fixed & Mobile Broadband Networks
Fiber/Copper Access
Network
Automated, Virtualized, Application-Aware
Fixed & Mobile Broadband Networks
CSP Co-Lo Data
Center
CSP Co-Lo Data
Center
CSP Co-Lo Data
Center
Enterprise Site
FCAPS Machine-to- Machine Workflow Process
Enterprise Site
Enterprise Site
Enterprise Site
Self-service Web Portal
Internet Internet SDN NFV
VNF Orchestrated Connectivity
Services
Optical Carrier Ethernet IP
New Orchestrated Virtualize Services
SD-WAN L4-L7 SECaaS
SD-WAN Controller
VNF
SD-WAN Controller SD-WAN
Edge CPE SD-WAN
Edge CPE
AI Analytics
AI Analytics
AI Analytics AI Analytics
AI Analytics
App Aware Services using AI Analytics
Key Principles
• SDN, NFV, Cloud, disaggregation, open source • For MEF community: easily include OCP as an implementation option • For OCP community: understand large OCP market opportunity enabled by MEF 3.0
& LSO abstractions
• Brownfield
• Healthy ecosystems: operators, vendors, enterprise customers
• Business success (despite transformation pain)
Orchestrated&Dynamic Open
Agile Expanded
MEF 3.O: Four Pillars for Agile, Assured, Orchestrated Services
• Multi-providerserviceorchestration
• Multi-technologynetworkorchestration
• SDKsandspecifications
• Globalmembership• Developercommunity• Certifiedprofessionals• Opensourceprojects&SDOs• Enterpriseadvisorycouncil• MEFnetplatform
• Wavelengths• CarrierEthernet• IPVPNs• SD-WAN• Security-as-a-Service• ApplicationServices
• Cloud-basedtestandcertificationplatform
• Subscription-based• Forbothservices&LSOAPIs
LSO – Lifecycle Service Orchestration
• Framework of abstractions • Components defined by function, separated by ref. points
• Customer Application Coordinator; Business Applications; Service Orchestration Function; Infrastructure Control & Management; Element Control & Management
• Abstraction boundaries described by APIs – East-West: Cantata, Allegro, Sonata, Interlude – North-South: Legato, Presto, Adagio
• Purposes: – Enable service providers to compose & concatenate services using their choice of
components: closed, proprietary, open, open-source, integrated, bare metal – Foster a supplier ecosystem that optimizes organically
Formalities
• API definitions • Information models • Data models • Interface profile specifications • Service definitions • Certifications
• LSO Hackathons • Developer Community • “SDK”s before IPSs • MEFnet • Example implementations • Reference implementations
Informalities
3-6 month sprint cycles
LSO APIs, SDKs
Based on MEF 55: LSO Framework Specification
Released as SDKs
Available in experimental or published states
• Define epics, user stories for the LSO Reference Point • Example: Sonata Epic1: availability capabilities; Epic2:
ordering capabilities • Implement the Data Model on MEFnet • Test on MEFnet and feed results back to refine Data Models • Share with other SDOs, open source projects • Showcase at the end of sprint
LSO API Abstraction Details SP Domain Customer Domain Partner Domain
Network Infrastructure
Customer Application Coordinator
Element Control and Management
Infrastructure Control
and Management
Service Orchestration Functionality
PRESTO (SOF:ICM)
ALLEGRO (CUS:SOF)
LEGATO (BUS:SOF)
CANTATA (CUS:BUS)
Element Control and Management
Infrastructure Control
and Management ADAGIO (ICM:ECM)
LEGATO (BUS:SOF)
PRESTO (SOF:ICM)
ADAGIO (ICM:ECM)
INTERLUDE (SOF:SOF)
SONATA (BUS:BUS)
Business Applications
Business Applications
Service Orchestration Functionality
Key CUS: Customer Application Coordinator BUS: Business Applications SOF: Service Orchestration Functionality ICM: Infrastructure Control and Management ECM: Element Control and Management
Product catalog; Product feasibility; Product ordering;
Acceptance-testing info; Billing and usage;
Trouble reports / status; Product-level quality;
Dynamic service control; Service state info;
Service performance & quality; Service-related alerts;
Create and manage connectivity and logical network functions;
Topology and routing; Performance and Fault;
Resource inventory; Connectivity policy;
Serviceability & qualification; Product catalog; Product ordering;
Acceptance-testing info; Billing exchange;
Trouble reports / status; Product-level quality;
Service feasibility; Service activation;
Usage events & metrics; Service performance & quality;
Service policy;
Dynamic service control; Service parameter config;
Service state info; Service performance info;
Service problem alerts;
Manage fabric or network functions on specific elements;
Element level configuration ; Element resource state;
Element fault and performance; Element-level policy;
MEF Expanded Community
MEF 3.0 Implementations
MEF Developer Community
Open source project & SDO collaboration
Hackathons to accelerate code development
Enterprise Advisory Council
Certified Professionals
Information Models
• Collaborative effort with TMF, ONF, ETSI, LF/ONAP • Goal: common or federated modeling approach
• Modeling language, patterns, extensibility, hierarchy, metadata • Tooling
MEF 3.0 Implementation Projects
MULTI-VENDOR SD-WAN FULFILLMENT AND ACTIVATION SERVICE TELEMETRY
SECAAS OPTICAL TRANSPORT MULTI-ONAP
REAL-TIME MEDIA CLOSED LOOP CONTROL CONNECTED VENUE
LSO Incorporating SDN, NFV, Open Source, OCP
NetworkOperator2NetworkOperator1
UserServiceEndpoint
UserServiceEndpoint
OperatorServiceEndpoint
End-to-EndNetwork-as-a-Service
Cloud Service Provider
SDN Switch
Packet PNFs
UNI UNI ENNI
Packet PNFs
Traditional EMS
SDN Controller
NFV MANO
Packet SDN Controller
EMS: Element Management System PNF: Physical Network Function SOF: Service Orchestration Function
HeadOffice
FRAMEWORK FRAMEWORK
Self-serviceWebPortal
LSO Interlude
LSO Presto
LSO Sonata LSO Cantata
LSO Allegro LSO Legato
Business Applications
SOF SOF
LSO Legato
LSO Presto
Business Applications
LSO Adagio LSO Adagio
Proof Point: ONAP-Based Global Virtual Fabric Global Enterprise
Cloud Service Provider
United States - Dallas United Kingdom – London/Ireland France - Lannion
Service Catalogue / Enterprise Orchestrator
Novitas Engine
Cloud Tenant Media Server VM
Enterprise device Enterprise device
AT&T Network
UNI-C-A UNI-C-Z
ENNI
UNI-C-C1
Cloud Tenant Media Server VM
UNI-C-C2
LEGATO
CANTATA
SONATA
Media Client
1
Orange Network
LEGATO
SONATA
Media Server
UNI-O-Z
Virtuora SDN-C
CANTATA
UNI-O-A
ENNI
BSS Service Orchestrator
Portal
Cloud Controller
Media Client
2
INTERLUDE
Operator Degrees of Freedom • Greenfield/brownfield
• Transport technology
• Telco cloud, public cloud, edge cloud, premises DC, out in the network
• Open source, open I/F, closed source
• SW/HW, integrated, bare metal, OCP, TIP
Enabled by LSO abstractions
Conclusions, Implications • Telco transformation inevitable
• New technologies, architectures (networking, computing) • Services, apps invariant over technology choices • Breakdown of rigid, monolithic solutions into SDN, NFV, OCP • New supply chain • New skills
• MEF transformation inevitable • Not just specifications but SDKs, POCs, IMs, experience • Global ecosystem of partner cos., orgs., .orgs • Pace, cadence, tension, agility
Many opportunities to incorporate OCP