Mobile World Congress 2016 OPEN SOURCE MANO (OSM) E2E Orchestration Demo. February 2016

Transcription

1 osm.etsi.org

2 Mobile World Congress 2016 OPEN SOURCE MANO () E2E Orchestration Demo February 2016

3 Open Source MANO () aims to accelerate NFV adoption around a common IM for orchestration Delivering an open source MANO stack aligned to ETSI NFV Information Models Capable of consuming published Information Models (IM) for NFV service and deployment (VNFD, NSD, etc.) Extending the IM, and recommending back to ETSI NFV Assuring predictable behaviour of Virtualized Network Functions (VNF) and Network Services (NS) under said information models Enabling an eco-system of IM-compliant VNF vendors Ready to be offered to cloud and service providers No need of integration per- customer & MANO vendor basis 3

4 providing a friendly environment for developers, minimizing entry barriers & paving the way for DevOps LOCAL DEVELOPMENT &TESTING TEST POOL FOR DEVELOPERS SERVICE PROVIDER Descriptors Descriptors VM images VM images Open Development Env Functional tests Low cost Integration from the beginning Real servers and switches Performance tests (EPA can be enforced) Cost-effective shared infrastructure Move the value to VNF services Production/pre-production environment Real network scenarios Final service configuration Fast deployment Low final integration cost SAME IMAGES AND DESCRIPTORS ACROSS ALL THE CHAIN!

5 Why? 3 reasons that make the difference 5

6 1) Initiative driven by Service Providers requirements and supported by key players of the virtualization space REMAINING OPEN TO NEW FELLOW TRAVELLERS

7 2) Embraces the complexity required for deployments in field 1. EPA support 2. Multi-VIM x Multi-site 4. SO and RO can be detached 7

8 including the operational aspects and modelling of abstractions required for E2E service orchestration 8

9 3) And does not start from scratch! The project starts with running code from the beginning OpenMANO (RO) Juju Charms (VNF Modelling & Config) Rift.io (SO/NS management) Seed code represents an initial starting point, being all components pluggable/replaceable for which helps to: Avoid over-engineering due to excess of abstraction Start getting traction at SP level Help to understand the value Bridge between long and short term Assure prompt feedback from practical experiences Ecosystem steering Assure VNF availability Better influence (via credibility) in other forums 9

10 PROJECT SCOPE & AREAS 1 COMMUNITY-DRIVEN IMPLEMENTATION OF NFVO+VNFM+SO* NFV management and Orchestration OSS/BSS Os-Ma NFV Orchestrator Or-Vi NFVI VNF 1 EM(s) Virtual Computing Computing Hardware VNF 2 Virtual Storage Virtualisation Layer Vl-Ha Storage Hardware Specific VNF-M(s) Vn-Nf VNF 3 Virtual Network Hardware resources Network Hardware Ve-Vnfm (*) Note: Service Orchestrator (SO) is currently beyond ETSI scope for MANO Nf-Vi Generic VNF Manager Or-Vnfm Vi-Vnfm Virtualised Infrastructure Manager(s) 2 DESCRIPTORS (VNFD & NSD) Service, VNF and Infrastructure Description 3 INTEROP & EPA SUPPORT W/REFERENCE VIM(s)

11 COMMUNITY CHARACTERISTICS OPEN COMMUNITY-BASED NFVO, based on these principles: Compliance and Feedback to ETSI ISG Architecture and Specs Base implementation information model Evolution Independent IOP labs to test & integrate in the community With an open governance model based on technical meritocracy TYPES OF ENGAGEMENT Developers (of course!) Early adopters Testers (modules & IOP) Advisors END USER ADVISORY BOARD Service providers and other end users of the technology (not integrators or resellers) will become members Produce Feature requests to the technical groups 11

12 Demonstration: L3 VPN service with value added services Putting in practice 12

13 MWC 2016 Demo - Rationale OBJECTIVE: Demonstrate the feasibility of the concepts, starting with existing code seeds As realistic as possible, with commercial VNFs Proof of main concepts of : E2E automation EPA & underlay control SLA can be guaranteed Multi-Site Multi-VIM Combination of multi-tenant and single-tenant VNFs Connection to external physical lines Useful for next stages of the project Enabler for further code development Room for further evolution/complexity 13

14 Real operation is multi-layered by nature, so MANO needs to embrace it to have real operational impact NETWORK CREATION FULFILLMENT ASSURANCE (L3) SERVICE OPERATION (Chaining of VAS & selfcare portal) Add users to VPN Add and chain VAS to VPN (self-care) QoE monitoring (L2) SERVICE MANAGER (VPN service) VPN service design VPN deployment VPN service monitoring (L1) NETWORK DEPARTMENT (Network core) (L0) NFVI OPERATOR Network scenario creation & deployment (PE per site) Installation of switches & servers 14 Network scenario provisioning Tenant creation. Allocation of tenant quotes. Network scenario monitoring Monitoring of usage of resources by tenants. Monitoring of NFVI infrastructure

15 Real operation is multi-layered by nature, but current MANO approaches are partial (L3) SERVICE OPERATION (Chaining of VAS & selfcare portal) (L2) SERVICE MANAGER (VPN service) (L1) NETWORK DEPARTMENT (Network core) (L0) NFVI OPERATOR NETWORK CREATION VPN service design Network scenario creation & deployment (PE per site) Installation of switches & servers 15 FULFILLMENT Add users to VPN Add and chain VAS to VPN (self-care) VPN deployment Network scenario provisioning ASSURANCE QoE monitoring SCOPE OF CURRENT MANO APPROACHES Tenant creation. Allocation of tenant quotes. VPN service monitoring STATIC / TRADITIONAL OPERATION CLOUD OPERATION Network scenario monitoring Monitoring of usage of resources by tenants. Monitoring of NFVI infrastructure

16 Real operation is multi-layered by nature, but current MANO approaches are partial (L3) SERVICE OPERATION (Chaining of VAS & selfcare portal) (L2) SERVICE MANAGER (VPN service) (L1) NETWORK DEPARTMENT (Network core) (L0) NFVI OPERATOR NETWORK CREATION VPN service design Network scenario creation & deployment (PE per site) Installation of switches & servers 16 FULFILLMENT Add users to VPN Add and chain VAS to VPN (self-care) VPN deployment Network scenario provisioning ASSURANCE QoE monitoring STATIC / TRADITIONAL OPERATION Tenant creation. Allocation of tenant quotes. VPN service monitoring SCOPE OF CURRENT MANO APPROACHES Network scenario monitoring STATIC / TRADITIONAL OPERATION CLOUD OPERATION Monitoring of usage of resources by tenants. Monitoring of NFVI infrastructure

17 Real operation is multi-layered by nature, so MANO needs to embrace it to have real operational impact (L3) SERVICE OPERATION (Chaining of VAS & selfcare portal) (L2) SERVICE MANAGER (VPN service) (L1) NETWORK DEPARTMENT (Network core) (L0) NFVI OPERATOR NETWORK CREATION VPN service design Network scenario creation & deployment (PE per site) 17 FULFILLMENT Add users to VPN Add and chain VAS to VPN (self-care) VPN deployment SCOPE OF Installation of switches & servers Network scenario provisioning Tenant creation. Allocation of tenant quotes. CLOUD OPERATION ASSURANCE QoE monitoring VPN service monitoring Network scenario monitoring Monitoring of usage of resources by tenants. Monitoring of NFVI infrastructure

18 STEP 0: NFVI+VIM are available at different locations (L0) VIM 1 VIM 2 interdc VLAN Z Multi-tenant VNF Single-tenant VNF net-os VIM tenant L2 connection for dataplane L2 connection for low BW

19 STEP 1: PE core is deployed and configured (L1) 16data1 PE 1 PE 2 16data2 PE 3 VIM 1 VIM 2 interdc VLAN Z Multi-tenant VNF Single-tenant VNF net-os VIM tenant L2 connection for dataplane L2 connection for low BW

20 STEP 2: Monitoring VPN is provisioned (L1) Corp. SP /24 VLAN data1 PE 1 PE 2 Corp. SP /24 16data2 VLAN 3000 PE 3 VIM 1 VIM 2 interdc VLAN Z Multi-tenant VNF Single-tenant VNF net-os VIM tenant L2 connection for dataplane L2 connection for low BW

21 STEP 3: Connectivity is validated with traffic generator (L1) Generator Corp. SP /24 VLAN data1 PE 1 PE 2 Corp. SP /24 16data2 VLAN 3000 PE 3 VIM 1 VIM 2 interdc VLAN Z Multi-tenant VNF Single-tenant VNF net-os VIM tenant L2 connection for dataplane L2 connection for low BW

22 STEP 4: VPN for Corporation A is created (L2) Generator Corp. SP /24 VLAN data1 PE 1 PE 2 Corp. SP /24 16data2 VLAN 3000 VLAN Y /24 VLAN X PE /24 VIM 1 VIM 2 interdc VLAN Z /24 Multi-tenant VNF Single-tenant VNF net-os VIM tenant L2 connection for dataplane L2 connection for low BW

23 STEP 5: SSL access for Corporation A is added in 2 sites (L3) Generator Corp. SP /24 VLAN data1 PE 1 PE 2 Corp. SP /24 16data2 VLAN 3000 VLAN Y SSL VPN /24 VLAN X PE /24 SSL VPN 2 VIM 1 interdc VIM 2 VLAN Z Multi-tenant VNF /24 Single-tenant VNF net-os VIM tenant L2 connection for dataplane L2 connection for low BW

24 STEP 6: Corporate VoIP service added to Corporation A (L3) Generator Corp. SP /24 VLAN data1 PE 1 PE 2 Corp. SP /24 16data2 VLAN 3000 VLAN Y SSL VPN /24 VLAN X PE /24 SSL VPN 2 VIM 1 interdc VIM 2 VLAN Z Multi-tenant VNF /24 Single-tenant VNF IMS-corpA net-os VIM tenant L2 connection for dataplane L2 connection for low BW

25 STEP 7: User is provisioned in corporate VoIP service (L3) Generator Corp. SP /24 VLAN data1 PE 1 PE 2 Corp. SP /24 16data2 VLAN 3000 VLAN Y SSL VPN /24 VLAN X PE /24 SSL VPN 2 VIM 1 interdc VIM 2 VLAN Z Multi-tenant VNF /24 Single-tenant VNF IMS-corpA net-os VIM tenant L2 connection for dataplane (domain, users) L2 connection for low BW

26 STEP 8: VoIP call in Corporation A (L3) Generator Corp. SP /24 VLAN data1 PE 1 PE 2 Corp. SP /24 16data2 VLAN 3000 VLAN Y SSL VPN /24 VLAN X PE /24 SSL VPN 2 VIM 1 interdc VIM 2 VLAN Z Multi-tenant VNF /24 Single-tenant VNF IMS-corpA net-os VIM tenant L2 connection for dataplane (domain, users) L2 connection for low BW

27 CONCLUSIONS E2E Service Orchestration is key to realizing the promised benefits of NFV It will deliver the broad multi use case benefits of NFV to the operator community The ability to integrate multi-vendor VNFs is essential to realize this vision Common procedures and mechanisms Lower cost of integration New competitive eco-system An open, well-understood and testable IM is key to enable such an open ecosystem of VNF providers The most effective vehicle to create certainty around the IM is a reference open source implementation 27

28 & NEXT STEPS was born to create such a reference implementation for the MANO stack The highest levels of openness and community access will be enabled through its widespread adoption VNF Vendors System Integrators Operators Academia The best way to stay involved in is to participate (many options are possible) Code Contributors Lab testers End user advisors General advisors in discussion s fora (osm.etsi.org) 28

29 Find out more at: osm.etsi.org 29