Network Virtualization: Recent Developments

Transcription

1 Network Virtualization: Recent Developments Washington University in Saint Louis Saint Louis, MO CSE 770 Networking Research Seminar at WUSTL January 28, 2013 These slides and audio/video recordings are available at: 1

2 Overview 1. Virtualization: Why, How? 2. Recent Networking Virtualization Technologies 3. Software Defined Networking 4. Our Research: Open Application Delivery Note: References to sources are either on the same slide or at the end. 2

3 Internet Virtualization Virtualization of Life No need to get out for Office Shopping Entertainment Education Virtual Workplace Virtual Shopping Virtual Education Virtual Sex Virtual Computing 3

4 Why Virtualize? 1. Sharing: Break up a large resource Large Capacity or high-speed 2. Isolation: Protection from other tenants 3. Aggregating: Combine many resources in to one 4. Dynamics: Fast allocation, Change/Mobility, load balancing 5. Ease of Management Cost Savings 6. Mobility for fault tolerance 10Gb Switch Switch Switch Switch 4

5 Storage: Virtualization in Computing Virtual Memory L1, L2, L3,... Recursive Virtual CDs, Virtual Disks (RAID), Cloud storage Computing: Virtual Desktop Virtual Server Virtual Datacenter Thin Client VMs Cloud Networking: Plumbing Virtual Channels, Virtual LANs, Virtual Private Networks Networks consist of: Hosts - L2 Links - L2 Bridges - L2 Networks - L3 Links - L3 Routers - L3 Networks L4 Transports L5 Applications Each of these can be/need to be virtualized Quick review of recent technologies for network virtualization 5

6 vnics Each VM needs its own network interface card (NIC) vm1 vnic1 vm2 vnic2 Hypervisor p = Physical v = Virtual M = Machine pm vswitch pnic pnic pswitch 6

7 pm vm1 vnic1 vm2 vswitch pnic vnic2 vnics (Cont) pm vm1 vnic1 pnic 1. VM vendors: S/W NICs in Hypervisor w Virtual Ethernet Bridge (VEB)(overhead, not ext manageable, not all features) 2. NIC Vendors: NIC provides virtual ports using Single-Route I/O virtualization (SR-IOV) on PCI bus 3. Switch Vendors: Switch provides virtual channels for inter- VM Communications using virtual Ethernet port aggregator (VEPA): 802.1Qbg (s/w upgrade), 802.1Qbh (new switches) 7 vm2 Hypervisor vswitch vnic2 pm vm1 vnic1 VEPA pnic vm2 pswitch vnic2

8 Bridge Port Extension Multiple physical bridges to make a single virtual bridge with a large number of ports Easy to manage and configure IEEE 802.1BR Bridge Bridge Bridge Bridge Bridge Bridge Bridge Bridge 8

9 Multi-Tenants Each tenant needs its own networking domain with its VLAN IDs Server 1 Server 2 VM1-1 VNI 22 VM1-2 VNI 34 VM2-1 VNI 34 VM2-2 VNI 74 VM1-3 VNI 74 VM1-4 VNI 98 VM2-3 VNI 98 VM2-4 VNI 22 Hypervisor VTEP IP1 L3 Networks Hypervisor VTEP IP2 1. Virtual Extensible Local Area Networks (VXLAN) 2. Network Virtualization using Generic Routing Encapsulation (NVGRE) 3. Stateless Transport Tunneling Protocol (STT) Network Virtualization over L3 (NVO3) group in IETF 9

10 Multi-Site Better to keep VM mobility in a LAN (IP address changes if subnet changes) Solution: IP encapsulation Transparent Interconnection of Lots of Links (TRILL) 10

11 Clouds and Mobile Apps Global Virtual Net August 25, 2006: Amazon announced EC2 Birth of Cloud Computing in reality (Prior theoretical concepts of computing as a utility) Web Services To Drive Future Growth For Amazon ($2B in 2012, $7B in 2019) - Forbes, Aug 12, 2012 June 29, 2007: Apple announced iphone Birth of Mobile Internet, Mobile Apps Almost all services are now mobile apps: Google, Facebook, Bank of America, Almost all services need to be global (World is flat) Almost all services use cloud computing Networks need to support efficient service setup and delivery 11

12 Application Delivery Evolution Single Server Data Center 3. Global Clouds 3. Global Clouds Load Balancers SSL Off loaders Global Internet Need to make the global Internet look like a data center 12

13 Google WAN Google L7 Proxy Access ISP Network POP Google WAN Google Data Center #1 Access ISP Google appliances in Tier 3 ISPs Details of Google WAN are not public ISPs can not use it: L7 proxies require app msg reassembly Google L7 Proxy 13 Google Data Center #2

14 Our Solution: OpenADN Open Application Delivery Networking Platform Platform = OpenADN aware clients, servers, switches, and middle-boxes Allows Application Service Providers (ASPs) to quickly setup services on Internet using cloud computing Global datacenter Servers A1, B1 Servers A2 OpenADN middle-box Access ISP Internet Access ISP OpenADN Switches Legacy Routers Clients Clients 14

15 Development 1: Centralization of Control Plane Control = Prepare forwarding table Data Plane: Forward using the table Forwarding table is prepared by a central controller Protocol between the controller and the forwarding element: OpenFlow Centralized control of policies Switches are simple. Controller can be complex Can use powerful CPUs Lots of cheap switches = Good for large datacenters Switch Forwarding Element Forwarding Element Control OpenFlow Data Forwarding Element Forwarding Element Ref: [MCK08] ``OpenFlow: Enabling Innovation in Campus Networks," OpenFlow Whitepaper, March

16 Centralized vs. Distributed Fully centralized is not scalable. Fully distributed is not manageable. Hierarchy 16

17 Development 2: Standardized Abstractions The routers are expensive because there is no standard implementation. Every vendor has its own hardware, operating/ management system, and proprietary protocol implementations. Similar to Mainframe era computers. No cross platform operating systems (e.g., Windows) or cross platform applications (java programs). OSPF BGP DHCP Network Operating System Proprietary fast forwarding hardware Cisco IOS Juniper JUNOS Ref: 17

18 Example: PC Paradigm Shift Computing became cheaper because of clear division of hardware, operating system, and application boundaries with well defined APIs between them Virtualization simple management + multi-tenant isolation Scientific Business Batch OS360 Operating System IBM 360 HW, Storage, 1981 MSOffice OpenOffice DOS Windows LINUX Intel AMD ARM 1998 VM1 VM2 VM3 Hypervisor Physical HW 18

19 Software Defined Networking Layered abstractions with standardized APIs Enterprise 1 Enterprise 2 Enterprise 3 Multicasting Mobility App1 App2 Applications Network OS1 Network OS2 Network OS3 Network OS Network Virtualization Virtualization Forwarding HW Forwarding HW Forwarding HW Forwarding HW Ref: 19 Forwarding

20 Northbound SDN s Layered Abstraction ASP1 ASP2 ASP3 OpenADN OpenADN OpenADN Net App1 Net App2 Net App3 Application Level Control (ASP) Network Level Control (ISP) Network OS1 Network OS2 Network OS3 Network OS Network Virtualization Virtualization Southbound OpenFlow Forwarding HW Forwarding Forwarding HW Forwarding HW SDN provides standardized mechanisms for distribution of control information 20

21 SDN Architecture Component Examples NOX oftrace openseer oflops Multicasting Beacon OpenFlow Mobility Maestro FlowVisor HP Floodlight NEC ofmonitor Ciena Helios Monitoring/ Debugging Control Applications Network OS/ Controller Virtualization/ Slicing Forwarding Juniper Pronto Netgear Open- VSwitch Ref: 21

22 SDN Impact Why so much industry interest? Commodity hardware Lots of cheap forwarding engines Low cost Programmability Customization Those who buy routers, e.g., Google, Amazon, Docomo, DT will benefit significantly Tsunami of software defined devices: Software defined wireless base stations Software defined optical switches Software defined routers 22

23 Life Cycles of Technologies Potential SDN Research Hype Dis illusionment MPLS ATM Success or Failure Time 25

24 Industry Growth: Formula for Success Number of Companies Innovators Startups Technology Differentiation Big Companies Manufacturing Price differentiation New Consolidation Stable Time Entrants Growth Paradigm Shifts Leadership Shift Old market leaders stick to old paradigm and loose Mini Computers PC, Phone Smart Phone, PC Smart Phone 26

25 OpenADN in SDN s Layered Abstraction ASP1 ASP2 ASP3 OpenADN OpenADN OpenADN App1 App2 App3 App4 Application Level Control (ASP) Network Level Control (ISP) Network OS1 Network OS2 Network OS3 Network OS Network Virtualization Virtualization OpenADN Aware OpenFlow Forwarding HW Forwarding Forwarding HW Forwarding HW SDN provides standardized mechanisms for distribution of control information 27

26 Key Features of OpenADN 1. Edge devices only. Core network can be current TCP/IP based, OpenFlow or future SDN based 2. Coexistence (Backward compatibility): Old on New. New on Old 3. Incremental Deployment 4. Economic Incentive for first adopters 5. Resource owners (ISPs) keep complete control over their resources Most versions of Ethernet followed these principles. Many versions of IP did not. 28

27 Summary 1. Cloud computing Virtualization of computing, storage, and networking Numerous recent standards related to networking virtualization both in IEEE and IETF 2. Recent Networking Architecture Trends: 1. Centralization of Control plane 2. Standardization of networking abstractions Software Defined Networking (SDN) 3. Most networking devices will be software defined 3. OpenADN enables delivery of applications using North-bound SDN API 29

28 References Subharthi Paul, Raj Jain, "OpenADN: Mobile Apps on Global Clouds Using OpenFlow and Software Defined Networking," First International workshop on Management and Security technologies for Cloud Computing (ManSec-CC) 2012, Decenber 7, 2012, in conjunction with IEEE Global Communications Conference (Globecom) 2012, Anaheim, CA, December 3-7, 2012, Intel, Simplifying the management of network elements in Telecom, White paper, -management-solutions-telecom-paper.html Nicira, Networking in the era of virtualization, White paper, 20of%20Virtualization.pdf OpenStack Object Storage Developers Guide, OpenStack Community Welcome Guide, 30

29 References (Cont) Juniper Networks, The important role of the network in a virtualized world, Juniper Networks, Solutions for deploying server virtualization in Datacenters, Joe Pellisier and Guru Chahaal, (Cisco) Virtualization Convergence over Ethernet, 2-2A_Pelissier_Chahal.pdf HP, Virtual networking technologies at the server network edge, 1.pdf HP, Facts about IEEE 802.1Qbg proposal, 5.pdf Emulex, Optimizing virtualized servers with SR-IOV, 04b89d798a78/elx_wp-all_srv-iov.pdf 31