NETWORK VIRTUALIZATION BASED ON SOFTWARE DEFINED NETWORK

Transcription

1 NETWORK VIRTUALIZATION BASED ON SOFTWARE DEFINED NETWORK

2 Introduction Motivation Concept Open Flow Virtual Switch SOFTWARE DEFINED NETWORK

3 We have lost our way Routing, management, mobility management, access control, VPNs, App App App Operating System Million of lines of source code 5400 RFCs Barrier to entry Specialized Packet Forwarding Hardware 500M gates 10Gbytes RAM Bloated Power Hungry Many complex functions baked into the infrastructure OSPF, BGP, multicast, differentiated services, Traffic Engineering, NAT, firewalls, MPLS, redundant layers, An industry with a mainframe-mentality

4 Reality App App App Operating System Specialized Packet Forwarding Hardware App App Operating System App Specialized Packet Forwarding Hardware Lack of competition means glacial innovation Closed architecture means blurry, closed interfaces Vertically integrated, complex, closed, proprietary Not suitable for experimental ideas Not good for network owners & users Not good for researchers

5 Glacial process of innovation made worse by captive standards process Idea Standardize Deployment Wait 10 years Driven by vendors Consumers largely locked out Lowest common denominator features Glacial innovation

6 Introduction Motivation Concept Open Flow Virtual Switch SOFTWARE DEFINED NETWORK

7 Trend App App App App App App Windows Windows Windows (OS) (OS) (OS) Linux Linux Linux Mac Mac Mac OS OS OS NOX Controller Controller 1 1 (Network OS) Controller Controller Network 22 OS Virtualization layer x86 (Computer) Virtualization or Slicing OpenFlow Computer Industry Network Industry

8 The Software-defined Network App App App Network Operating System Ap p Ap p Ap p Operating System Specialized Packet Forwarding Hardware Ap p Ap p Operating System Ap p Ap p Ap p Operating System Ap p Specialized Packet Forwarding Hardware Ap p Ap p Operating System Ap p Specialized Packet Forwarding Hardware Ap p Ap p Ap p Specialized Packet Forwarding Hardware Operating System Specialized Packet Forwarding Hardware

9 3. Well-defined open API App The Software-defined Network 2. At least one good operating system Extensible, possibly open-source App App Network Operating System 1. Open interface to hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware

10 Isolated slices Many operating systems, or Many versions App App App App App App App App Network Operating System 1 Network Operating System 2 Network Operating System 3 Network Operating System 4 Open interface to hardware Virtualization or Slicing Layer Open interface to hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware

11 Consequences More innovation in network services Owners, operators, 3 rd party developers, researchers can improve the network E.g. energy management, data center management, policy routing, access control, denial of service, mobility Lower barrier to entry for competition Healthier market place, new players

12 Introduction Motivation Concept Open Flow Virtual Switch SOFTWARE DEFINED NETWORK

13 Traditional network node: Router Router can be partitioned into control and data plane Management plane/ configuration Control plane / Decision: OSPF (Open Shortest Path First) Data plane / Forwarding Adjacent Router Routing Control plane OSPF Router Management/Policy plane Configuration / CLI / GUI Control plane OSPF Static routes Adjacent Router Control plane OSPF Switching Data plane Neighbor table Data plane Link state database IP routing table Forwarding table Data plane

14 Traditional network node: Switch Typical Networking Software Management plane Control Plane The brain/decision maker Data Plane Packet forwarder

15 SDN Concept Separate Control plane and Data plane entities Network intelligence and state are logically centralized The underlying network infrastructure is abstracted from the applications Execute or run Control plane software on general purpose hardware Decouple from specific networking hardware Use commodity servers Have programmable data planes Maintain, control and program data plane state from a central entity An architecture to control not just a networking device but an entire network

16 Control Program Control program operates on view of network Input: global network view (graph/database) Output: configuration of each network device Control program is not a distributed system Abstraction hides details of distributed state

17 Software-Defined Network with key Abstractions in the Control Plane Well-defined API Routing Traffic Engineering Network Operating System Other Applications Network Virtualization Network Map Abstraction Forwarding Forwarding Forwarding Separation of Data and Control Plane Forwarding

18 Forwarding Abstraction Purpose: Abstract away forwarding hardware Flexible Behavior specified by control plane Built from basic set of forwarding primitives Minimal Streamlined for speed and low-power Control program not vendor-specific OpenFlow is an example of such an abstraction

19 OpenFlow Basics Control Program A Control Program B Network OS OpenFlow Protocol Ethernet Control Switch Path OpenFlow Data Path (Hardware)

20 OpenFlow Basics Control Program A Control Program B Network OS Packet Forwarding If header = p, send to port 4 If header = q, overwrite header with r, add header s, and send to ports 5,6 If header =?, send to me Packet Forwarding Flow Table(s) Packet Forwarding

21 Match arbitrary bits in headers: Plumbing Primitives <Match, Action> Header Data Match: 1000x01xx x Match on any header, or new header Allows any flow granularity Action Forward to port(s), drop, send to controller Overwrite header with mask, push or pop Forward at specific bit-rate 21

22 General Forwarding Abstraction Small set of primitives Forwarding instruction set Protocol independent Backward compatible Switches, routers, WiFi APs, basestations, TDM/WDM

23 Introduction Motivation Concept Open Flow Virtual Switch SOFTWARE DEFINED NETWORK

24 What is OpenFlow OpenFlow is similar to an x86 instruction set for the network Provide open interface to black box networking node (ie. Routers, L2/L3 switch) to enable visibility and openness in network Separation of control plane and data plane. The datapath of an OpenFlow Switch consists of a Flow Table, and an action associated with each flow entry The control path consists of a controller which programs the flow entry in the flow table OpenFlow is based on an Ethernet switch, with an internal flow-table, and a standardized interface to add and remove flow entries

25 OpenFlow Consortium Goal Evangelize OpenFlow to vendors Free membership for all researchers Whitepaper, OpenFlow Switch Specification, Reference Designs Licensing: Free for research and commercial use

26 OpenFlow building blocks oftrace oflops openseer Monitoring/ debugging tools Stanford Provided ENVI (GUI) LAVI n-casting Expedient Applications NOX Beacon Trema Maestro ONIX Controller FlowVisor Console Commercial Switches HP, NEC, Pronto, Juniper.. and many more FlowVisor Stanford Provided Software NetFPGA Ref. Switch OpenWRT PCEngine WiFi AP Broadcom Ref. Switch Open vswitch Slicing Software OpenFlow Switches 26

27 Components of OpenFlow Network Controller OpenFlow protocol messages Controlled channel Processing Pipeline Processing Packet Matching Instructions & Action Set OpenFlow switch Secure Channel (SC) Flow Table Flow entry

28 OpenFlow Controllers Name Lang Platform(s) License Original Author OpenFlow Reference C Linux OpenFlow License Stanford/Nici ra Notes not designed for extensibility NOX Python, C++ Linux GPL Nicira actively developed Beacon Java Win, Mac, Linux, Android GPL (core), FOSS Licenses for your code David Erickson (Stanford) runtime modular, web UI framework, regression test framework Maestro Java Win, Mac, Linux LGPL Zheng Cai (Rice) Trema Ruby, C Linux GPL NEC includes emulator, regression test framework RouteFlow? Linux Apache CPqD (Brazil) virtual IP routing as a service 28

29 Secure Channel (SC) SC is the interface that connects each OpenFlow switch to controller A controller configures and manages the switch via this interface. Receives events from the switch Send packets out the switch SC establishes and terminates the connection between OpneFlow Switch and the controller using the procedures Connection Setup Connection Interrupt The SC connection is a TLS connection. Switch and controller mutually authenticate by exchanging certificates signed by a site-specific private key.

30 Flow table in switches, routers, and chipsets Flow Table Flow 1. Rule (exact & wildcard) Action Statistics Flow 2. Rule (exact & wildcard) Action Statistics Flow 3. Rule (exact & wildcard) Action Statistics Flow N. Rule (exact & wildcard) Default Action Statistics

31 Flow Entry A flow entry consists of Match fields Match against packets Action Modify the action set or pipeline processing Stats Update the matching packets Match Fields Action Stats In Port Src MAC Dst MAC Eth Type Vlan Id IP Tos IP Proto IP Src IP Dst TCP Src Port TCP Dst Port Layer 2 Layer 3 Layer 4 1. Forward packet to port(s) 2. Encapsulate and forward to controller 3. Drop packet 4. Send to normal processing pipeline 1. Packet 2. Byte counters

32 Examples Switching Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * 00:1f:.. * * * * * * * port6 Flow Switching Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action port3 00: :1f vlan port6 Firewall Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * * * * * * * * 22 drop 32

33 Examples Routing Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * * * * * * * * port6 VLAN Switching Switch Port * MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport * 00:1f.. * vlan1 * * * * * TCP dport Action port6, port7, port9 33

34 OpenFlow Usage Controller OpenFlow Switch Rule Action Statistics Peter s code PC OpenFlow Protocol OpenFlow Switch OpenFlow Switch Rule Action Statistics Rule Action Statistics OpenFlowSwitch.org Peter

35 Usage examples Peter s code: Static VLANs His own new routing protocol: unicast, multicast, multipath, loadbalancing Network access control Home network manager Mobility manager Energy manager Packet processor (in controller) IPvPeter Network measurement and visualization

36 Separate VLANs for Production and Research Traffic Controller Research VLANs Production VLANs Flow Table Normal L2/L3 Processing

37 Dynamic Flow Aggregation on an OpenFlow Scope Network Different Networks want different flow granularity (ISP, Backbone, ) Switch resources are limited (flow entries, memory) Network management is hard Current Solutions : MPLS, IP aggregation

38 Dynamic Flow Aggregation on an OpenFlow How do OpenFlow Help? Dynamically define flow granularity by wildcarding arbitrary header fields Granularity is on the switch flow entries, no packet rewrite or encapsulation Create meaningful bundles and manage them using your own software (reroute, monitor) Network

39 Virtualizing OpenFlow Network operators Delegate control of subsets of network hardware and/or traffic to other network operators or users Multiple controllers can talk to the same set of switches Imagine a hypervisor for network equipments Allow experiments to be run on the network in isolation of each other and production traffic

40 Switch Based Virtualization Exists for NEC, HP switches but not flexible enough Research VLAN 2 Research VLAN 1 Production VLANs Flow Table Flow Table Normal L2/L3 Processing Controller Controller 40

41 FlowVisor A network hypervisor developed by Stanford A software proxy between the forwarding and control planes of network devices

42 FlowVisor-based Virtualization Topology discovery is per slice Aaron s Controller Heidi s Controller Craig s Controller OpenFlow Protocol OpenFlow Switch OpenFlow FlowVisor & Policy Control OpenFlow Protocol OpenFlow Switch OpenFlow Switch 42

43 FlowVisor-based Virtualization Separation not only by VLANs, but any L1-L4 pattern Broadcast Multicast http Load-balancer dl_dst=ffffffffffff OpenFlow Protocol tp_src=80, or tp_dst=80 OpenFlow Switch OpenFlow FlowVisor & Policy Control OpenFlow Protocol OpenFlow Switch OpenFlow Switch 43

44 FlowVisor Slicing Slices are defined using a slice definition policy The policy language specifies the slice s resource limits, flowspace, and controller s location in terms of IP and TCP port-pair FlowVisor enforces transparency and isolation between slices by inspecting, rewriting, and policing OpenFlow messages as they pass

45 FlowVisor Resource Limits FV assigns hardware resources to Slices Topology Network Device or Openflow Instance (DPID) Physical Ports Bandwidth Each slice can be assigned a per port queue with a fraction of the total bandwidth CPU Employs Course Rate Limiting techniques to keep new flow events from one slice from overrunning the CPU Forwarding Tables Each slice has a finite quota of forwarding rules per device

46 Slicing

47 FlowVisor FlowSpace FlowSpace is defined by a collection of packet headers and assigned to Slices Source/Destination MAC address VLAN ID Ethertype IP protocol Source/Destination IP address ToS/DSCP Source/Destination port number

48 FlowSpace: Maps Packets to Slices

49 FlowVisor Slicing Policy FV intercepts OF messages from devices FV only sends control plane messages to the Slice controller if the source device is in the Slice topology. Rewrites OF feature negotiation messages so the slice controller only sees the ports in it s slice Port up/down messages are pruned and only forwarded to affected slices

50 FlowVisor Slicing Policy FV intercepts OF messages from controllers Rewrites flow insertion, deletion & modification rules so they don t violate the slice definition Flow definition ex. Limit Control to HTTP traffic only Actions ex. Limit forwarding to only ports in the slice Expand Flow rules into multiple rules to fit policy Flow definition ex. If there is a policy for John s HTTP traffic and another for Uwe s HTTP traffic, FV would expand a single rule intended to control all HTTP traffic into 2 rules. Actions ex. Rule action is send out all ports. FV will create one rule for each port in the slice. Returns action is invalid error if trying to control a port outside of the slice

51 FlowVisor Message Handling Alice Controller Bob Controller Cathy Controller Rule Policy Check: Is this rule allowed? Full Line Rate Forwarding OpenFlow FlowVisor OpenFlow OpenFlow Firmware Exception Policy Check: Who controls this packet? Packet Data Path

52 Introduction Motivation Concept Open Flow Virtual Switch SOFTWARE DEFINED NETWORK

53 INTRODUCTION Due to the cloud computing service, the number of virtual switches begins to expand dramatically Management complexity, security issues and even performance degradation Software/hardware based virtual switches as well as integration of open-source hypervisor with virtual switch technology is exhibited 53

54 Software-Based Virtual Switch The hypervisors implement vswitch Each VM has at least one virtual network interface cards (vnics) and shared physical network interface cards (pnics) on the physical host through vswitch Administrators don t have effective solution to separate packets from different VM users For VMs reside in the same physical machine, their traffic visibility is a big issue 54

55 Issues of Traditional vswitch The traditional vswitches lack of advanced networking features such as VLAN, port mirror, port channel, etc. Some hypervisor vswitch vendors provide technologies to fix the above problems OpenvSwitch may be superior in quality for the reasons 55

56 A software-based solution Open vswitch Resolve the problems of network separation and traffic visibility, so the cloud users can be assigned VMs with elastic and secure network configurations Flexible Controller in User-Space Fast Datapath in Kernel Server Open vswitch Controller Open vswitch Datapath

57 Open vswitch Concepts Multiple ports to physical switches A port may have one or more interfaces Bonding allows more than once interface per port Packets are forwarded by flow Visibility NetFlow sflow Mirroring (SPAN/RSPAN/ERSPAN) IEEE 802.1Q Support Enable virtual LAN function By attaching VLAN ID to Linux virtual interfaces, each user will have its own LAN environment separated from other users

58 Open vswitch Concepts Fine-grained ACLs and QoS policies L2- L4 matching Actions to forward, drop, modify, and queue HTB and HFSC queuing disciplines Centralized control through OpenFlow Works on Linux-based hypervisors: Xen XenServer KVM VirtualBox

59 Open vswitch Contributors(Partial)

60 Packets are Managed as Flows A flow may be identied by any combination of Input port VLAN ID (802.1Q) Ethernet Source MAC address Ethernet Destination MAC address IP Source MAC address IP Destination MAC address TCP/UDP/... Source Port TCP/UDP/... Destination Port

61 Packets are Managed as Flows The 1st packet of a flow is sent to the controller The controller programs the datapath's actions for a flow Usually one, but may be a list Actions include: Forward to a port or ports mirror Encapsulate and forward to controller Drop And returns the packet to the datapath Subsequent packets are handled directly by the datapath

62 Migration KVM and Xen provide Live Migration With bridging, IP address migration must occur with in the same L2 network Open vswitch avoids this problem using GRE tunnels

63 Hardware-Based Virtual Switch Why hardware-based? Software virtual switches consume CPU and memory usage Possible inconsistence of network and server configurations may cause errors and is very hard to troubleshooting and maintenance Hardware-based virtual switch solution emerges for better resource utilization and configuration consistency 63

64 Virtual Ethernet Port Aggregator A standard led by HP, Extreme, IBM, Brocade, Juniper, etc. An emerging technology as part of IEEE 802.1Qbg Edge Virtual Bridge (EVB) standard The main goal of VEPA is to allow traffic of VMs to exit and re-enter the same server physical port to enable switching among VMs 64

65 Virtual Ethernet Port Aggregator VEPA software update is required for host servers in order to force packets to be transmitted to external switches An external VEPA enabled switch is required for communications between VMs in the same server VEPA supports hairpin mode which allows traffic to hairpin back out the same port it just received it from--- requires firmware update to existing 65 switches

66 Pros. and Cons. for VEPA Pros Minor software/firmware update, network configuration maintained by external switches Cons VEPA still consumes server resources in order to perform forwarding table lookup 66

67 با تشکر