SDN and NFV: Why ODL ticks all the right boxes?

Transcription

1 SDN and NFV: Why ODL ticks all the right boxes? Sridhar K. N. Rao (Ph.D) NEC Technologies India Limited.

2 Acknowledgement Image Sources. NEC America. ETSI-NfV Framework ETSI-NFV PoCs From slides distributed during SDN-NFV Conference held at Dusseldorf, Germany, in October ONF Stefan Schnitter Jim Machi Justin Dustzadeh THANKS A LOT.

3 Agenda

4 6 Questions What is NFV? Role of SDN in NfV? SDN-Elements (Controller, NEs and Apps) in NfV Architecture? What are expectations from SDN controllers for NFV? Why ODL ticks all the right boxes? What are the related trends to look out for?

5 What is NfV?

6 Traditional Approach Message Router CDN Session Border Controller DPI Firewall Carrier Grade NAT PHYSICAL NETWORK FUNCTIONS PE Router EPC WAN Acceleration BRAS DNS Tester/QoE monitor Fragmented non-commodity HW Physical install per appliance per site Low asset utilization HW development is time consuming and can t be continuously deployed / upgraded HW development is challenging for new vendors Limits modularity, vendor choice

7 Flexibility / Extensibility High asset utilization Continuously deployed / upgraded Achieve Modularity Gain Software benefits Opens the competitive landscape up Innovative Ecosystem Virtualized Network Function VM VM VM VM VM VM Virtual Virtual Appliance Virtual Appliance Appliance Virtual Virtual Appliance Virtual Appliance Appliance Commodity/Off the Shelf Servers and Network Elements NFV Orchestrators (OpenStack) and other Controllers

8 ** Alcatel-Lucent What is NfV Cloudifying** the Network Network Functions Virtualization (NFV) replaces the need for physical appliances with virtualized network functions running on standard server platforms Moving the functions usually embedded in network hardware into software that can run in a VM on the standard servers. Functions: Routers, DPI, EPC, Firewalls. Separation of HW and SW NO Vertical Integration Hw Vendor, Sw Vendor, Management Soln. Vendor Once Network elements are software-based hardware elements are managed as a pool of resources.

9 Examples: vcpe and vepc

10 vcpe (1) IP service edge function as VNF on COTS server (2) CPE functionalities integrated into telecom carrier facility Source :

11 vepc Source: Source: 3gpp.org

12 NfV Architecture

13 NFV Architecture OSS/BSS Service, VNF and Infrastructure Description Os-Ma Se-Ma Orchestrator Or-Vnfm EMS 1 EMS 2 EMS 3 Ve-Vnfm VNF Manager(s) NFVI VNF 1 VNF 2 Vn-Nf VNF 3 Vi-Vnfm Or-Vi Virtual Computing Virtualisation Layer Vl-Ha Computing Hardware Virtual Storage Storage Hardware Virtual Network Hardware resources Network Hardware Nf-Vi Virtualised Infrastructure Manager(s) Execution reference points Other reference points Main NFV reference points Source: ETSI NFV Architectural Framework

14 A Layered View Source: Andy Reid, British Telecom

15 Examples: Proof of Concepts

16 CloudNFV Open NFV Framework PoC#1 Source: ETSI PoCs

17 E2E vepc Orchestration in an multivendor open NFVI environment PoC#5 Source: ETSI PoCs

18 Virtualized Mobile Network with Integrated DPI (PoC#6) Source: ETSI PoCs

19 Biggest Challenge How to achieve Carrier Grade? Uptimes: Five-9s at the services level and Six-9s for the Infrastructure (including networking).* Enterprise software : Three-9s Ensuring a highly stateful and secure end-to-end service is always available. Statefulness High Availability Ultra-low Latency. Security & Reliability Rapid Provisioning and Resource Optimization

20 Carrier Grade Vs COTS Hardware* Carrier Grade Strong fault detection and fault isolation capabilities at hardware level Well established traditions on software upgrade, patching, and maintenance Reliably Central Office assumed COTS May have smaller mean time between failure (MTBF) Relative smaller mean time to repair (MTTR) COTS procedures for software upgrade, patching, and aintenance contribute more to scheduled down time Different grade of reliability for data centers *Dr. Li Mo, CTO Group

21 SDN in NFV

22 SDN is Necessary to Exploit the NFV Potential.. Prodip Sen, HP SDN and NFV: Twins or Distant Cousins?... Arpit Joshipura (Dell) SDN and NFV are independent. But, SDN has a significant role to play in NfV Carrier SDN= SDN + NFV, is getting mature and commercially ready brings significant benefit to Telecom Industry.. Hashimoto (NEC)

23 SDN is already been well explored by Telcos for (multi-layer) WAN. We can come across many solutions where SDN is used for Transport Networks (SDN-Transport) SDN has played a Significant role in such Multi- Layer/Multi-Domain environments. SDN in Telco Clouds with NFV

24 SDN and NfV: Similarity * Both owe their existence to similar market forces, Better processor capability significant improvement in the processor technology Simplification in connectivity - scope for separation of planes. Virtualization maturity. Both technologies are designed to increase flexibility, decrease costs, support scalability, and speed the introduction of new services. Source: Stefan Schnitter Detecon International *Source: Jim Machi

25 Why Do we need SDN in NfV? It is not mandatory to have SDN for NfV. But NFV is a complementary initiative to SDN. SDN makes realization of NfV much easier and better - improve performance and simplify operations As long as NFV addresses the general case of policy-managed forwarding, and need dynamic service orchestration SDN can play a major role.

26 Why do we need SDN in NfV? Use of Dynamic Virtual Overlays and need for Multitenancy in NfV also drives the need for SDN. Currently, the widely acknowledged role of SDN in NfV: Supporting Service Chain Management. Traffic Steering. Offload, Bypass, Selection, etc. Dynamic Scale-up and Scale-out Service chain with Virtual-Networks. Load Balancing.

27 Service chaining On-demand network service composition by dynamically chaining virtual network functions, such as router, firewall, DPI, NAT, etc. CE Router Firewall DPI NAT PE Router Tenant-A Tenant-B

28 ETSI : SDN for NfV Classification of user-traffic Adding labels to the packet. L3-L4 or L7 traffic steering. L2-Transparent network service chaining with traffic steering. Automation of mapping in Multi-layer bandwidth on Demand Automation of the process to map the service request requirements into available network resources Dynamic manage of these resources can map the service into the appropriate network layer for the most efficient use of network resources Interconnecting VNFCs Interconnecting VNFs connecting traffic sources and sinks, provide processing of traffic in transit. To provide a specified service of network design. Chained based on customer policy/service or on VNF Processing. Load balancing across VNFs - VNF elasticity.

29 Summary: SDN in NfV Flexible Service Chaining Network Virtualization: large-scale Overlays. Policy Enforcing Traffic Engineering

30 Real-World SDN & NFV Developments Source: Justin Dustzadeh, Huawei

31 ETSI NFV Proof of Concepts Source: ETSI-NFV Service Description (Infrastructure part) Orchestration Or-Vi Multi-Tenant Virtualization management Nf-Vi Virtualization Layer Orchestrator NOVA API Virtualized Infrastructure Manger - OpenStack NOVA VM-1 VM-2 VM-n Hypervisor Se-MA SWIFT SWIFT API SDN plugin L2 Sw Neutron SDN daemon SDN Agent SDN controller Hypervisor Switch Quantum API OpenFlow NEUTRON Rest API /Network service OpenFlow Physical Layer Server HW Standard L2 Switch Fabric IP Core Network DC GW SDN is used to implement the MAC forwarding required to connect The QOSMOS the clustered DPI VNFs VNFC expects components packets routed within through the VNF and to and/or connect copied the to VNF its to ports the so network. that it can analyse the traffic.

32 SDN Elements in NFV architecture

33 SDN Components SDN Applications Business Apps Plane MANAGEMENT PLANE SDN Controller Control Plane OSS/BSS NETWORK ELEMENTS Data Plane Source: ONF

34 Source: ETSI GS NFV-SWA 001 V NFV Architecture OSS/BSS Service, VNF and Infrastructure Description Os-Ma Se-Ma Orchestrator Or-Vnfm EMS 1 EMS 2 EMS 3 Ve-Vnfm VNF Manager(s) 2 VNF 1 VNF 2 VNF Or-Vi NFVI Virtual Computing Virtualisation Layer 1 Vl-Ha Computing Hardware Virtual Storage Storage Hardware Vn-Nf Virtual Network Hardware resources Network Hardware 0 3 Nf-Vi Vi-Vnfm Virtualised Infrastructure Manager(s) 4 Execution reference points Other reference points Main NFV reference points Application Data Control

35 SDN in NFV Architecture DATA: SDN-enabled Network Elements Virtual and Physical CONTROL: SDN Controller. APPLICATION: SDN Applications. SDN enabled Virtual Network Function? Should there be any overlap with VNFM and SDN Controllers? VNFs are providing networking services - virtual routers They may be configured by SDN Controllers?

36 SDN Controllers and Nfv

37 NfV framework enhances and redefines the role of SDN controllers.

38 Expectations from an SDN Controller for NfV Multi-Deployment Support Fully Programmable, Open Interfaces Virtualized Infrastructure connectivity Management. Support Multiple Southbound/Data-Plane Elements Interoperability with other controllers/orchestrator/managers. Rich Feature Set. Routing, SFC, etc. Transport Networks: Multi-Layer Multi-Domain Non-Functional: Scalability Low-Latency

39 SDN Controller Deployment Options Options Description Single/Redundant Single (or with redundancy) controller for the network Hierarchical A hierarchy of controllers with, possibly, client/server relationships between them. Options Description Non Virtualized Complete controller instance running on single system (a physical machine) Virtualized Controller instance running in virtualized environment (as a VM) Options Integrated Distributed Description All the SDN controller functions running under single instance. SDN controller functions are distributed.

40 Deployment SDN Controller should support multiple deployment models. Support different Control plane options in NfV Architecture. VIM, NFVI, VNFM, etc. In either case - Support appropriate interfaces in each model and option.

41 Virtualized Infrastructure connectivity*** Responsible for the following aspects related to NFVI connectivity services: Interconnecting VNFs Waypoint * support. Resource management and tracking of network resources and attributes such as bandwidth, jitter, delay etc. Connectivity services to create overlay tunnels (e.g., VXLAN, NVGRE, MPLS over GRE) or network partitions.

42 Support Multiple Southbound/Data-Plane Elements Southbound support of multiple protocols OpenFlow, NetConf, SNMP, BGP-LS etc Support IETF protocols to control physical and virtual routers and switches Border Gateway Protocol Link State (BGP-LS) Path Computation Element Protocol (PCEP)

43 Fully Programmable, Open Interfaces Fully programmatic open interfaces for service and Resource Orchestration within and across NFVIs (Data-Centers). Support different deployment options too. Minimize Manual/Proprietary interfacing.

44 Interoperability Interoperability with other controllers and Orchestrators. Non-SDN Network Controllers VIMs Support different scenarios Multiple Orchestration (VIMs)? Single VIM and multiple SDN Controllers. Within Single and Across Multiple Data Centers.

45 Transport Networks Support: Interconnecting Data Centers Controller/Orchestrator VIM VIM SDN Controller(s) SDN Controller(s) SDN Controller(s) NEs NEs NEs DC-1 WAN DC-2

46 Rich and Relevant Feature Set Features : Multi-layer Topology Management. Real-Time Monitoring. Policy Driven Load Balancing. Policy Driven Traffic Steering. Service Function Chaining Management.

47 Service Insertion and Chaining Ability to manage network service chains. Ability to manage network functions within the chain Service Insertion/Deletion No disruption to existing traffic when new service is inserted in the chain. Traffic Steering Ability to define traffic rules to bypass network functions in the chain. Ability to define traffic rules for selecting the chain out of multiple chains. Multi-tenancy and Service Chaining Management of network service chain with virtual networks. Ability to associate multiple network service chains to a network.

48 Why ODL ticks all the right boxes?

49 ODL is the best OpenSource solution we have for NfV, at least for now, and the competition is heating up!

50 ODL for NfV: Features Expectations Multiple Deployment Model Support Including the modularity, Clustering and Virtualization of the Controller ODL YES Multiple Southbound Protocols including IETF Protocols Service Function Chaining and Insertion Multiple Network Virtualization support Multiple Network Configuration Protocols Multi-Layer Network Optimization for transport networks. Support for Integration with VIM (Openstack) and VNFM (Proprietary). Deeper Integration with Openstack. Interoperability YES YES and PARTIAL YES [VTNs, Dove, etc] YES (NETCONF and SNMP) YES YES and PARTIAL YES

51 ODL for NfV: Platform Dynamically pluggable module architecture brings lot of advantages. The Helium release: The platform has evolved Key Areas High availability, clustering and security, Newer concepts like OpenFlow Table Type Patterns, PacketCable MultiMedia, Application policy framework and tools for Service Function Chaining

52 ODL for NfV: Usage in PoCs ODL has been used in NfV Proof Of Concepts Ex: POC# 19. Demonstrated at Dusseldorf, Germany Service Acceleration of NW Functions in Carrier Networks Acceleration of Virtualized NW functions (VNFs) that work on carrier networks utilizing commoditized white box hardware DPI and Firewall

53 ODL For NfV: ODL-Based* ODL-Based Controllers by Ciena Huawei HP Ericsson ADVA Brocade ConteXtream Oracle Cisco Intel.

54 How ODL fares in comparison with Other OpenSource SDN Controllers Controllers Use-Cases Trema Nox/Pox RYU Floodlight ODL ONOS*** Network Virtualizaiton by Virtual Overlays YES YES YES PARTIAL YES NO Hop-by-hop Network Virtualization NO NO NO YES YES YES OpenStack Neutron Support NO NO YES YES YES NO Legacy Network Interoperability NO NO NO NO YES PARTIAL Service Insertion and Chaining NO NO PARTIAL NO YES PARTIAL Network Monitoring PARTIAL PARTIAL YES YES YES YES Policy Enforcement NO NO NO PARTIAL YES PARTIAL Load Balancing NO NO NO NO YES NO Traffic Engineering PARTIAL PARTIAL PARTIAL PARTIAL YES PARTIAL Dynamic Network Taps NO NO YES YES YES NO Multi-Layer Network Optimization NO NO NO NO PARTIAL PARTIAL Transport Networks - NV, Traffic- Rerouting, Interconnecting DCs, etc. NO NO PARTIAL NO PARTIAL PARTIAL Campus Networks PARTIAL PARTIAL PARTIAL PARTIAL PARTIAL NO Routing YES NO YES YES YES YES

55 Related Trends and Open Source Projects

56 There are other interesting opensource projects to watch out for

57 Significant Open Source Works OPNFV April 23 rd 2015 Open-MANO Telefonica Bare Metal Switches and Open Networking Open Compute Project by Facebook. Open Source Software and Open Hardware ONL Switch Abstraction Interface Forwarding Abstraction. Open Network Switch Library (NSL)by Broadcom Closed Source, but, Open API. FBOSS Agent Use of Docker Containers in NfV Environments Related SDN Controller ONOS from ON.LAB