NFV Unbound from physical boxes to virtual, open infrastructures - PowerPoint PPT Presentation

NFV Unbound from physical boxes to virtual, open infrastructures Christos Kolias Sr. Research Scientist Network Architecture, Orange Silicon Valley christos.kolias@orange.com Open Daylight Summit February 4-5, 2014 – Santa Clara, CA 1

Agenda  NFV: A Year Later  Use Cases & PoCs  Open NFV  NFV+SDN  Orange NFV PoCs  Future of … 2 ETSI NFV

NFV: implementing network functions in software - that (today) run on proprietary hardware - leveraging (high volume) commodity servers and IT virtualization ETSI NFV ISG: a group for producing NFV specifications and a reference framework - not a standardization body 3 ETSI NFV

The NFV Concept & Vision Classical Network Model: The New Network Model: Virtual Appliances Hardware Appliances WAN Session Border CDN Message Acceleration Controller Router DPI Carrier Firewall Tester/QoE Grade NAT Orchestration & Automation monitor BRAS PE Router SGSN/GGSN Radio/Fixed Access standard servers, storage, switches Network Nodes  Network Functions are based on specialized hardware  Network Functions are SW-based  One physical node per role. Physical install per site  Multiple roles over same HW. Remote operation  Static. Hard to scale up & out  Dynamic. Extremely easy to scale 4 ETSI NFV

A Potted History of NFV • Network operators had independently discovered that NFV technology now has sufficient performance for real-world network work loads • Informal discussions on cooperation to encourage industry progress began at ONS in Santa Clara in April 2012 • At an operator meeting in Paris in June 2012 we coined the new term “Network Functions Virtualisation (NFV)”. • We decided to convene a new industry forum, and publish a joint white paper to galvanise the industry • At a meeting in San Francisco in September 2012 we decided to parent the new forum under ETSI • In October 2012 we published the first joint-operator NFV white paper as a “call to action”.  This paper is widely regarded as the seminal paper heralding this new approach for networks. • The first NFV ISG plenary session was held in January 2013 13 signatories to first NFV • In October 2013 the first NFV ISG documents were released white paper after only 10 months, and a second joint-carrier NFV white paper published to provide our perspectives on progress. 5 ETSI NFV

Fields of Application (examples) • • Security functions Mobile networks:  Firewalls, virus scanners, intrusion  HLR/HSS, MME, SGSN, GGSN/PDN- detection systems, spam protection GW, eNodeB, vEPC • • Tunnelling gateway NGN signalling: elements:  SBCs, IMS  IPSec/SSL VPN gateways • Switching elements: • Converged and network-  BNG, CG-NAT, routers wide functions: • Home environment:  AAA servers, policy control and charging  home router, set top box, picocell platforms • • Application-level Traffic analysis/forensics: optimization:  DPI, QoE measurement  CDNs, Cache Servers, Load Balancers, • Traffic Monitoring: Application Accelerators  Service Assurance, SLA monitoring, Test and Diagnostics 6 ETSI NFV

ETSI NFV Group • Global operators-initiated Industry Specification Group (ISG) under the auspices of ETSI >170 companies ‒ ‒ 28 Tier-1 carriers (and mobile operators) & service providers, cable industry • Open membership ‒ ETSI members sign the “Member Agreement” ‒ Non-ETSI members sign the “Participant Agreement” • Operates by consensus (formal voting only when required) • Deliverables: requirements specifications, architectural framework, PoCs, standards liaisons • Face-to-face meetings quarterly. Currently four (4) WGs, two (2) expert groups (EGs), 4 root-level work items (WIs) WG1: Infrastructure Architecture ‒ ‒ EG1: Security WG2: Management and Orchestration ‒ ‒ EG2: Performance & Portability, PoCs WG3: Software Architecture ‒ WG4: Reliability & Availability ‒ • Network Operators Council (NOC): technical advisory body • Technical Steering Committee (TSC): WG Chairs + EG Leaders, TMs, PMs, Rapporteurs 7 ETSI NFV

ETSI NVF Organization & Structure ISG Chair Network Operators ISG V. Chair Council Support from ETSI Secretariat (Chaired by NOC Chair) ISG Plenary Technical Management (Chaired by ISG Chair) (TM and ATM) Technical Steering Committee (Chaired by Technical Manager) . . . WG WG WG Expert Group 8 ETSI NFV

Architectural Groups  Related to functional requirements  Have a clear location in the NFV architecture ‒ Keep consistency with both requirements and architecture  INF ‒ The supporting infrastructure interfaces and elements  MANO ‒ The external interfaces and behaviour of a VNF  SWA ‒ The internals of a VNF  Refining the architecture  Addressing use cases  Mostly oriented to produce reference documents 9 ETSI NFV

Transversal Groups  Related to non-functional requirements  Transversal to the architecture ‒ Influencing work in the architectural groups  REL ‒ Specify resiliency requirements, mechanisms , and architectures  PER ‒ Predictability in the data plane and function portability  SEC ‒ Function by function and infrastructure  Refining the requirements  Assessing use cases  Mostly concerned with recommendations and architecture models 10 ETSI NFV

ETSI NFV’s objectives  Provide a common requirements and architectural framework  Four specification documents ratified and published (Oct. ‘13) • Architecture Framework, Use Cases, Requirements, Terminology www.etsi.org/nfv  Identify overall technical challenges and scope, e.g.: ‒ Achieving high performance with portability between different hardware vendors (and hypervisors) ‒ Specify interfaces between functional blocks ‒ Achieving co-existence with bespoke hardware based network platforms whilst enabling an efficient migration path to fully virtualised network platforms ‒ Managing and orchestrating many virtual network appliances while ensuring security from attack and misconfiguration ‒ Achieving scale through automation ‒ Integrating multiple virtual appliances from different vendors (“mix & match”) without incurring significant integration costs, and while avoiding lock-in 11 ETSI NFV

 Templates/patterns/config-schemes for instantiating the VNFs ‒ They could be network/operator specific ‒ Compile VNFs  Encourage common approaches to solving these technical challenges in an open ecosystem  The NFV ISG provides a forum for the industry & operators to collaborate, to converge requirements, agree common approaches, and to validate recommendations  Develop and exhibit Proof-of-Concepts (PoCs). Benchmarking  Perform a Gap Analysis ‒ Map WG tasks to relevant externals bodies 12 ETSI NFV

External Relationships  Most relevant SDOs ONF MoU  Open Source projects  Identifying concrete areas of cooperation  Need to avoid fragmentation  Public documents, www.etsi.org/nfv  Early access to stable drafts  Participation in joint events  Coordinated individual contributions 13 ETSI NFV

An E2E View: Architectural Use Cases  Network Functions Virtualisation Infrastructure as a Service (NVFIaaS) ‒ Network functions go to the cloud  Virtual Network Function as a Service (VNFaaS) ‒ Ubiquitous, delocalized network functions  Virtual Network Platform as a Service (VNPaaS) ‒ Applying multi-tenancy at the VNF level  VNF Forwarding Graphs ‒ Building E2E services by composition NVFIaaS Example 14 ETSI NFV

XaaS for Network Services User NSP VNF Forwarding Graph VNF VNF VNF Admin User VNPaaS VNF VNF Admin User VNFaaS Hosting Service Provider VNF VNF VNF VNF VNF VNF VNF VNF VNF VNF Tenants NFVIaaS NFVI Provider IaaS NaaS NaaS PaaS PaaS SaaS 15 ETSI NFV

An E2E View: Service-Oriented Use Cases  Mobile core network and IMS ‒ Elastic, scalable, more resilient EPC ‒ Specially suitable for a phased approach  Mobile base stations ‒ Evolved Cloud-RAN ‒ Enabler for SON  Home environment ‒ L2 visibility to the home network ‒ Smooth introduction of residential services  CDNs ‒ Better adaptability to traffic surges ‒ New collaborative service models  Fixed access network ‒ Offload computational intensive optimization ‒ Enable on-demand access services 16 ETSI NFV

An E2E View: Requirements  Focused on the differences introduced by NFV ‒ Not on aspects that are identical whether the implementation is physical or virtual  High level requirements on ‒ Portability Service assurance ‒ ‒ Performance Operation and management ‒ ‒ Elasticity Energy Efficiency requirements ‒ ‒ Resiliency Transition and coexistence with ‒ ‒ Security existing infrastructures ‒ Service continuity  Requirements for supporting ‒ Deployment ‒ Multi-tenant service models ‒ Maintenance 17 ETSI NFV