NETWORK FUNCTION VIRTUALIZATION - AN INSIGHT

Transcription

1 NETWORK FUNCTION VIRTUALIZATION - AN INSIGHT Presented by Deepanshu Gautam for Workshop of India-EU Collaboration on Standardisation for Select Technologies 5/11/2015

2 BACKGROUND

3 PROBLEM STATEMENT AND OBSERVATION Problem Statement Complex carrier networks with a large variety of proprietary nodes and hardware appliances. Launching new services is difficult and takes too long, and requires just another variety of box, which needs to be integrated into the existing network and IT environments. Operation is expensive, due to existing procure-design-integrate-deploy cycle. Observation Commercial-off-the-shelf IT-platforms allow to host a large variety of applications. New virtualization technology allows to abstract underlying hardware, and enables elasticity, scalability and automation. Network Technology suppliers already use such technologies, but in a proprietary way.

4 VISION Efficient Resource Utilization Remote configuration and install Single design based on commodity hardware Reduces OpEX and VapEX. Reduces system complexities Multivendor network management platform Reduce power consumption.. Efficient test and integration bcz of common infrastructure Rapid Time to Market

5 ETSI NFV INDUSTRY SPECIFICATION GROUP (ISG)

6 FACTS In the 2 months since NFV#10: 10 new ISG member companies, 71 conference calls and 1 F2F meeting week In the 32 months since the creation of ISG NFV: 280 Member companies, (115 ETSI Members, 165 Participant organisations) 1300 people subscribed to the principal NFV mailing list 34 Work Items under way, a further 2 NWIs proposed Plenary attendance: NFV#1 (165), NFV#2 (285), NFV#3 (242), NFV#4 (355), NFV#5 (260), NFV#6 (258), NFV#7 (303), NFV#8(220), NFV#9 (244), NFV#10 (171)

7 CURRENT MEMBERSHIP

8 8 NFV ISG LIFE SPAN NFV White Paper Released at SDN & OpenFlow summit in Germany October 2012 Chairm an TSC NOC Working Groups Expert Group INF PER SEC SWA MAN O REL February 2013 NFV#1 Kick-off PoC ETSI headquarter, France Structure decided NFV#2 Santa Clara ISG WI created for E2E architecture, use cases requirements terminology April 2013 July 2013 MANO#1 NFV#4 Sunnyvale Phase 1 work continues October 2013 NFV#3 Bonn ISG mainly work on the ISG level documents ISG releases first set of specifications as a major milestone E2E architecture, use cases requirements terminology February 2014 MANO#2 NFV#5 Malaga ISG decided to go for Phase 2 OPNFV proposed NFV#6 Okinawa ISG leadership changes. AT&T took the chair position NOC chair changed affiliation Phase 1 specifications published MANO, SWA, REL, INF etc. NFV#8 Scottsdale ISG Phase 2 started NFV Phase 1 officially ended. February 2015 NFV#10 Sanya ISG decided to make all working drafts publically available MANO#4 May 2015 NFV#9 Prague July WG chairs 2014 November and vice 2014 chair elected Phase 2 progresses NFV#7 MANO#3 Election of 2 Santa Clara Docomo took additional ISG May the ISG vicechair vice-chair took 2014 position ISG approves the Phase 2 place. HP and ALU took the positions mission statement Chairm an IT was decided that Phase 2 will develop TSC NOC normative Working Groups stage 2 (Architecture) work IFA EVE TST REL SEC July 2015 MANO#5 NFV#11 San Jose Phase 3 planning started Beyond 2016 planning started Phase 3 features proposals starts flowing All rights reserved NFV#12 Jersey City October 2015 NFV#13

9 LEADERSHIP AND STRUCTURE Raquel Morera, Verizon Chair Mehmet Ersue, Nokia Vice Chair Elected at NFV#9

10 MAJOR ISSUES

11 11 NFV Architecture OSS/BSS EM 1 EM VNF 1 NFVI VNF Virtual Computing Vn-Nf NF VI Execution Computing reference points Hardware OSS/BSS Os-Ma-nfvo NS VNF 3 NFV Orchestrato r VNF Manager(s) Vn-Nf Vi-Vnfm Ve-Vnfm-vnf Vi-Vnfm NFVI Virtual Virtual NFVI Compute Management Storage Network Or-Vi NFVI Networking Management Virtualised NFVI Storage Management Infrastructure Nf-Vi Virtualised NFVI Hypervisor Management Or-Vi Virtualisation Nf-Vi Layer Manager (VIM) Infrastructure Vl-Ha NFV-MANO Manager(s) Virtual Resource Hardware resources Storage Other Network Main NFV reference reference points Hardware Hardware points Execution reference points Catalogu Catalogu EM 2 EM 3 e Ve-Vnfm-em VNF 2 NFV Orchestrator (NFVO) VNF e Or-Vnfm VNF Manager (VNFM) NFV Instanc es Other reference points Os-Ma NFVI Resourc Ve-Vnfm es NFV Management and Orchestration NS Lifecycle Management NS Lifecycle Change Notifications NS Descriptor Management NS Performance Management NS Fault Management Or-Vnfm Main NFV reference points Network Service VNF Service, VNF and Infrastructure Description VNF Package Management VNF Image Management VNF Lifecycle Management VNF Lifecycle Operation Granting VNF Lifecycle Change Notifications VNF Configuration Management VNF Performance Management VNF Fault Management vresource Catalog Management vresource Capacity Management vresource Performance Management vresource Fault Management vresource Management

12 12 NFV LAYERS VIEW E2E Network Service End Point Network Service End Point Logical Abstractions Logical Links VNF VNF VNF FG PNF VNF VNF Forwarding Graph (including Service Chain) SW Instances VNF Instances VNF VNF VNF VNF NFV Infrastructure (NFVI) VNF : Virtualized Network Function PNF : Virtualized Network Function Virtual Resources Virtualization SW Virtual Compute Virtual Storag e Virtualization Layer Virtual Network HW Resources Compute Storag e Network

13 MANO DESCRIPTORS 13 NSD Id Vendor Version vnfd Vnffgd Vld Lifecycle_event Vnf_depedency Monitoring_parameters Deployment_flavour Auto_scale_policy CP pnfd VNFD vendor descriptor_version version vdu virtual_link connection_point lifecycle_event dependency monitoring_parameter deployment_flavour auto_scale_policy manifest_file manifest_file_security VDU id vm_image computation_requirement virtual_memory_resource_element virtual_network_bandwidth_resource lifecycle_event constraint high_availability scale_in_out vnfc monitoring_parameter id vm_image vnfc id connection_point VNFFGD Id Vendor Descriptor_version Version Constituent_vnf Cp Nfp Depedent_virtual_link Number _of_endpoints number_of_virtual_lin k VLD Id Vendor Version Root_requirements Leaf_requirements Qos connection Connectivity_type Test_access NFP Id policy connection

14 VNF LCM OPTIONS 14 VNF LCM in direct Mode VNF LCM in in-direct Mode VNFM talk to VIM, for resource management, directly after getting a permission (granting) form NFVO for particular LCM operation. VNFM talk to VIM, for resource management, via NFVO even after getting a permission (granting) form NFVO for particular LCM operation. Pending Issues: Is granting always needed? What bout cases where LCM request is received by NFVO in first place. Can granting be delegated

15 15 IFA008 (Ve-Vnfm) Generic VNFM Specific VNFM Vendors Boundaries The most controversial Interface in NFV architecture

16 NFVO SPLIT 16 NFVO- DO acts as a proxy between NFV-SO and VNFM for VNF LCM NFVO(RO) acts as a proxy between NSO and VIM hiding underlining multiple VIM form NSO.

17 IFA012 (app & services running on top) Details of 'DGS/NFV-IFA012' Work Item This work item will entail work to specify the interface(s) and the corresponding requirements that comprise the Os-Ma-nfvo reference point as currently defined in the GS NFV-MAN 001 regarding applications/services on top of Network Services (NS). Life cycle management of Services (applications/services on top of NS). Monitoring/Tracing (e. g. concerning services). Flexible/dynamic service orchestration including creation and modification (e. g. orchestration, launching of a service and adaptation of running services. On-top may imply: Grouping: Having an existing NS grouped with the application/service on top. Full (entire NS) and partial (few VNF of a NS) grouping is possible Grouping may imply dependencies between NS and application/service on-top. What is on-top?? 17

18 NFV STANDARDIZATION AND DEPLOYMENTS

19 STAKEHOLDERS Vendors: providing solutions/products VNF/Network Service Vendors Converting their existing NFs into VNF/NS NFV Hardware vendors (NFV COTS) Provide an efficient COTS which can meet integrated hardware in terms of efficiency. NFV MANO vendor Providing multivendor NFV network management system. Legacy NMS (EM, OSS/BSS) vendor Saving the current investments Network Operators: deploying provided solutions/products No-vendor lock-in Reducing OpEx Reducing CpEx Service Providers: consuming NFV service and providing further service to end-users VNFaaS, NFVIaaS End Users No impact

20 STAGE 3 STANDARDIZATION LANDSCAPE???? Standardized Open Source Public 20

21 RELATED SDO AND TECHNOLOGIES Category NFV 3GPP TMF OASI S IETF DMTF OMG OpenSt ack OPNFV OpenMA NO OpenDayl ight Business Layer Business Processing ZOOM BPEL BPMN Modeling Modeling IFA (MANO) SID TOSC A YANG Project Policy Policy Manageme nt IFA(MAN O) ZOOM NFV- RG Architect ure Interface/A PIs IFA (MANO, SWA) SA5 OMI, ODE CAM P CIMI Projects OpenDayli ght Orchestrati on IFA (MANO) FMSS (Service Chaining) ZOOM SFC NFV-RG Heat OpenMA NO OpenDayli ght VNFM IFA (MANO,S WA, INF) SA5 ZOOM Projects OpenDayli ght NFVI OpenSt ack Projects OpenDayli ght Reliability Reliability/ Resiliency REL VNFP ool 21

22 NFV PHASED DEPLOYMENTS NFV is considered to be a disruptive technology. Specially, it is expected to change the way current networks is being managed. The multi-vendor management and orchestration objective of NFV need to controlled. Smooth migration is required. Phase 1 Phase 2 Phase 3 Phase 4 Final Phase Standardized Interface 22

23 NFV OPEN SOURCE

24 OPNFV (OPEN PLATFORM FOR NFV) Launched 30 Sep 2014 Speed up implementation of NFV Create a carrier grade Open Source Ecosystem Website: Wiki: OPNFV Arno: o

25 OPNFV CONTND OPNFV Project Pipeline Next OPNFV release (in discussion) now is called OPNFV Brahmaputra release aka B release For details:

26 OPEN MANO Openmano (spelled without capitals), a reference implementation of an NFV orchestrator Openvim, a reference implementation of a virtualized infrastructure manager (VIM) A graphical user interface. 26

27 SDN Vs. NFV

28 WHAT ARE THEY? NFV enables executing existing network functions on virtual machine where as, SDN separate control flow from data flow. NFV Applied SDN Applied Managed Router Service

29 PLACEMENT IN ETSI NFV ARCHITECTURE SDN vswitch SDN vswirch The most obvious NFV construct related with SDN would be NFPs (network forwarding path aka service chain) included in VNFFG. OpenFlow SDN Controller SDN could be used to configure vswitch to forward the traffic as per a particular NFP. 29

30 SOME USEFUL POINTERS NFV Public page NFV published Specifications All NFV working drafts are publically accessible NFV PoC updates NFV Liaison Matrix

31 NFV FUTURE PLANNING

32 RELEASE 2016 TIMELINE Feature based 2016 Release 32

33 FEATURE PROPOSAL SUBMITTED Total 24 feature proposal were submitted for 2016 release. 4% 4% 4% 7% 7% 7% 4% Contributions 4% 11% 30% 18% AT&T Huawei HP DT DoCoMo PTP 33

34 FEATURE PROPOSAL RECOMMENDED BY TSC Listed in TSC recommendation NOT listed in TSC recommendation Withdrawn/Merged New Features : FTR002 (CHRG) FTR003 (NFV_SECM) FTR007 (POLICY) FTR008 (SEC4SNC) FTR013 (VEMOSS) FTR016 (VNF_PHOTO) FTR017 (NFV_M&Ms) FTR019 (SWUP) FTR030 (NFVWAN) FTR031 (CONF&IOP) FTR004 (REAL-TIME) FTR011 (NFVI_PATH_TEST) FTR018 (NFV_FM) NFV039 (INTENT) Extensions : FTR001 (IM-NFV) FTR010 (NFVO_ARCH) FTR026 (HWENV) FTR035 (FASTSWITCH) FTR023 (VNFCON) FTR005 (DM-NFV) FTR012 (HWMET) FTR027 (PLACEMENT) FTR029 (MARKETPLACE) FTR033 (G-VNFM) FTR036 (PAAS) FTR037 (BBF-MSBN) FTR006 (IOT-5G) FTR020 (NFVI-EndPoints) FTR021 (NFVI-EndPoints) FTR022 (NFVI-EndPoints) FTR024 (WAN services) FTR025 (WAN control services) FTR028 (MAN-REL) FTR032 (Lightweight Containers) FTR009 (VNFM_ARCH) Research Agenda: FTR004 (REAL-TIME) FTR014 (DEVOPS) FTR015 (PNF2VNF) FTR034 (VCONF)

35 FEATURE MAPPINGTO WGs Features INTENT (FTR039) EVE, IFA VNFCON (FTR023) EVE REAL-TIME (FTR004) EVE, IFA Extensions EVE IFA REL TST SEC HWENV (FTR026) EVE, SEC, REL NFV-IM (FTR001) IFA CHRG (FTR002) IFA POLICY (FTR007) IFA VEMOSS (FTR013) IFA NFV_M&M (FTR017) IFA, SEC, REL NFVO_ARCH (FTR010) IFA NFVWAN (FTR030) IFA FASTSWITCH (FTR035) IFA NFV_FM (FTR018) REL SWUP (FTR019) REL, TST, IFA, SEC PATH_TEST (FTR011) TST VNF_PHOTO (FTR016) TST, IFA, SEC CONF&IOP (FTR031) TST NFV_SECM (FTR003) SEC, IFA SEC4SNC (FTR008) SEC, IFA Building Blocks New Technologies Transition into NFV and Integration NFV Information Modelling Charging, Billing and Accounting Policy Management End-to-End Management Service and Network Service Orchestration Acceleration Fault Management Continuous Integration Testing Security Management To derive work items Work Item set to update Work published Item set to update GS(s) published GS(s) Work Item set for feature Work related Item set for normative feature work related normative work Work Item set to cover Work Stage Item 3 set to cover Stage 3 Work Item set for feature Work related Item set for informative feature work related informative work

36 STEPS AHEAD 1. Refine the document on endorsed features 2. Request the NOC to recommend priorities for the endorsed features 3. Identify sources for work item definitions By the end of November 4. The TSC will prepare work-item guidelines according to these sources 5. Work-item proposal collection Deadline: two weeks before NFV#13 6. Discuss and approve the WID proposals at NFV#13

37 BEYOND 2016 Whether ISG NFV should continue Whether ISG should do Stage 3 work Whether to use open source based stage 3 work Whether to use conventional specification based stage 3 work

38 Thank you!