OpenFlow Brazil Tutorial SBRC Brandon Heller, Stanford/[CPqD] Masa Kobayashi, NEC/Stanford/[RNP]

Transcription

1 OpenFlow Brazil Tutorial SBRC 2010 Brandon Heller, Stanford/[CPqD] Masa Kobayashi, NEC/Stanford/[RNP]

2 Our IntroducLons

3 Your IntroducLons

4 Goals of this Tutorial By the end, everyone should know: what OpenFlow is how it s used and how you can use it where it s going how OpenFlow compares to other plauorms how OpenFlow fits in the (SoXware- Defined Networking) SDN spectrum Present a useful mix of hands- on and lecture- based content Have fun

5 Agenda Time 8:30am- 10:30am 10:30am- 11:00am 11:00am- 12:30pm 12:30pm- 2:00pm 2:00pm- 3:30pm 3:30pm- 4:00pm 4:00pm- 6:00pm Descrip5on Mo5va5on, History, Interface, Begin Hands- on Por5on Break SoFware- Defined Networking, Virtualiza5on, Demos Lunch Hardware Switches, Deployments Break Community, Evalua5ons

6 Why OpenFlow?

7 impact

8 Research StagnaLon Lots of innovalon in other areas OS: filesystems, schedulers, virtualizalon DS: DHTs, CDNs, MapReduce Compilers: JITs, vectorizalon Networks are largely the same as years ago Ethernet, IP, WiFi Rate of change of the network seems slower in comparison Need becer tools and abstraclons to demonstrate and deploy

9 Closed Systems (Vendor Hardware) Stuck with interfaces (CLI, SNMP, etc) Hard to meaningfully collaborate Vendors starlng to open up, but not usefully Need a fully open system a Linux equivalent

10 Open Systems Performance Fidelity Scale Real User Traffic? Complexity SimulaLon medium medium no medium yes EmulaLon medium low no medium yes SoXware Switches Open poor low yes medium yes NetFPGA high low yes high yes Network Processors Vendor Switches high medium yes high yes high high yes low no gap in the tool space none have all the desired acributes!

11 Ethane, a precursor to OpenFlow Centralized, reaclve, per- flow control Controller Flow Switch Flow Switch Flow Switch Host A Host B Flow Switch See Ethane SIGCOMM 2007 paper for details

12 OpenFlow: a pragmalc compromise + Speed, scale, fidelity of vendor hardware + Flexibility and control of soxware and simulalon Vendors don t need to expose implementalon Leverages hardware inside most switches today (ACL tables)

13 Ethernet Switch

14

15 OpenFlow Protocol (SSL/TCP)

16 OpenFlow Example Controller SoXware Layer OpenFlow Client PC Hardware Layer MAC src MAC dst Flow Table IP Src IP Dst TCP sport TCP dport AcLon * * * * * port 1 port 1 port 2 port 3 port

17 OpenFlow Basics Flow Table Entries Rule AcLon Stats Packet + byte counters 1. Forward packet to port(s) 2. Encapsulate and forward to controller 3. Drop packet 4. Send to normal processing pipeline 5. Modify Fields Switch Port VLAN ID MAC src MAC dst Eth type IP Src IP Dst IP Prot TCP sport TCP dport + mask what fields to match

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

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

20 Centralized vs Distributed Control Centralized Control Controller Distributed Control Controller OpenFlow Switch OpenFlow Switch Controller OpenFlow Switch OpenFlow Switch Controller OpenFlow Switch OpenFlow Switch

21 Flow RouLng vs. AggregaLon Both models are possible with OpenFlow Flow- Based Every flow is individually set up by controller Exact- match flow entries Flow table contains one entry per flow Good for fine grain control, e.g. campus networks Aggregated One flow entry covers large groups of flows Wildcard flow entries Flow table contains one entry per category of flows Good for large number of flows, e.g. backbone

22 ReacLve vs. ProacLve (pre- populated) Both models are possible with OpenFlow ReacLve First packet of flow triggers controller to insert flow entries Efficient use of flow table Every flow incurs small addilonal flow setup Lme If control conneclon lost, switch has limited ullity ProacLve Controller pre- populates flow table in switch Zero addilonal flow setup Lme Loss of control conneclon does not disrupt traffic EssenLally requires aggregated (wildcard) rules

23 Examples of OpenFlow in AcLon VM migralon across subnets energy- efficient data center network WAN aggregalon network slicing default- off network scalable Ethernet scalable data center network load balancing formal model solver verificalon distribulng FPGA processing Demo pictures/videos to come axer first coffee break!

24 What OpenFlow Can t Do (1) Non- flow- based (per- packet) networking ex: wireless protocols (CTP), per- packet processing (sample 1% of packets) yes, this is a fundamental limitalon BUT OpenFlow can provide the plumbing to connect these systems Use all tables on switch chips yes, a major limitalon (cross- product issue) BUT an upcoming OF version will expose these

25 What OpenFlow Can t Do (2) New forwarding primilves BUT provides a nice way to integrate them New packet formats/field definilons BUT a generalized OpenFlow (2.0) is on the horizon OpLcal Circuits BUT efforts underway to apply OpenFlow model to circuits Low- setup- Lme individual flows BUT can push down flows proaclvely to avoid delays Only a fundamental issue when speed- of- light delays are large

26 Where it s going OF v1.1: Extensions for WAN, late 2010 mullple tables: leverage addilonal tables tags and tunnels mullpath forwarding OF v2+ generalized matching and aclons: an instruclon set for networking

27 Tutorial Flow set up VM, learn tools, run provided hub turn hub into an Ethernet switch modify switch to push down flows add multiple switch support modify switch to handle IP forwarding on your own... OpenFlow tutorial flow add firewall capabilities to switch

28 Stuff you ll use NOX Reference Controller/Switch (OF v0.8.9) Mininet cbench iperf tcpdump Wireshark

29 Tutorial Layout OpenFlow Tutorial: 3-switch topology OF Switch s1 c0 s1-eth0 Controller port 6633 loopback ( ) ofprotocol (user-space process) netlink ofdatapath (kernel module) s1-eth1 s1-eth2 netlink dpctl (user-space process) h2-eth0 h virtual ethernet pairs h h3-eth0 h4-eth0 h

30 Where to get files Flash Drives (~10): use 1, pass it on DVDs (~10): use 1, pass it on Up- to- date InstrucLons at hcp:// Brazil_tutorial

31 Welcome! Ge ng Started Pick up a flash drive or DVD Copy to your hard disk from Flash Drive/: Corresponding files (terminal, X server, Vmware) for your plauorm (Win/Mac/Linux OpenFlowTutorial.vmwarevm.zip InstrucLons folder Pass it on! Then, unzip OpenFlowTutorial.vmwarevm.zip Username: mininet / Password: mininet Note mistake in Windows instruclons; login as mininet@[ip]

32 Get Started!!! Downloads: hcp:// /openflow/ InstrucLons: hcp:// Updates: keep going don t stop at any step you can install VMware tools if you d like it s not necessary Windows Users: if you DISPLAY not set when trying to launch an xterm, go to PuTTY- >ConnecLon- >X11 Forwarding- > Click on Enable X11 Forwarding Please refresh the instruclons page

33 SoXware- Defined Networking (SDN) and OpenFlow

34 Current Internet Closed to InnovaLons in the Infrastructure App App App Closed OperaLng System Specialized Packet Forwarding Hardware App App App OperaLng System App App App OperaLng System Specialized Packet Forwarding Hardware App App App OperaLng System Specialized Packet Forwarding Hardware App App App Specialized Packet Forwarding Hardware OperaLng System Specialized Packet Forwarding Hardware 34

35 SoXware Defined Networking approach to open it App App App Network OperaLng System App App App OperaLng System Specialized Packet Forwarding Hardware App App App OperaLng System App App App OperaLng System Specialized Packet Forwarding Hardware App App App OperaLng System Specialized Packet Forwarding Hardware App App App Specialized Packet Forwarding Hardware OperaLng System Specialized Packet Forwarding Hardware

36 The SoXware- defined Network 3. Well- defined open API App App App Network OperaLng System 2. At least one good operalng system Extensible, possibly open- source 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

37 Isolated slices Many operalng systems, or Many versions App App App App App App App App Network OperaLng System 1 Network OperaLng System 2 Network OperaLng System 3 Network OperaLng System 4 Open interface to hardware VirtualizaLon 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

38 Virtualizing OpenFlow

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

40 FLOWVISOR BASED VIRTUALIZATION" Aaron s Controller Heidi s Controller Craig s Controller OpenFlow Protocol OpenFlow Switch OpenFlow FlowVisor & Policy Control OpenFlow Protocol OpenFlow Switch OpenFlow Switch

41 Use Case: VLAN Based ParLLoning Basic Idea: ParLLon Flows based on Ports and VLAN Tags Traffic entering system (e.g. from end hosts) is tagged VLAN tags consistent throughout substrate Switch MAC Port src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport * * * * 1,2,3 * * * * * * * * * 4,5,6 * * * * * * * * * 7,8,9 * * * * *

42 FLOWVISOR BASED VIRTUALIZATION" Separation not only by VLANs, but any L1-L4 pattern" Broadcast Multicast http Load-balancer OpenFlow Protocol OpenFlow Switch OpenFlow FlowVisor & Policy Control OpenFlow Protocol OpenFlow Switch OpenFlow Switch

43 Use Case: New CDN - Turbo Coral ++ Basic Idea: Build a CDN where you control the enlre network All traffic to or from Coral IP space controlled by Experimenter All other traffic controlled by default roulng Topology is enlre network End hosts are automalcally added (no opt- in) Switch MAC Port src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

44 A new layer 3 protocol Replaces IP Defined by a new Ether Type Use Case: Aaron s IP Switch MAC Port src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport * * * AaIP * * * * * * * * *!AaIP * * * * * *

45 Demo Previews Note: acend Masa s talk tomorrow to see many of these live!

46 Demo Previews FlowVisor Plug- n- Serve AggregaLon OpenPipes OpenFlow Wireless MobileVMs ElasLcTree

47 Demo Infrastructure with Slicing WiMax WiFi APs OpenFlow switches Flows Packet processors The individual controllers and the FlowVisor are applicalons on commodity PCs (not shown) Be sure to check out the demos during the break!!

48 OpenFlow DemonstraLon Overview Topic Network Virtualization Hardware Prototyping Load Balancing Energy Savings Mobility Traffic Engineering Wireless Video Demo FlowVisor OpenPipes PlugNServe ElasticTree MobileVMs Aggregation OpenRoads

49 FlowVisor Creates Virtual Networks OpenPipes Demo OpenRoads Demo PlugNServe Load- balancer Each demo presented here runs in an isolated slice of Stanford s produclon network. OpenFlow Switch OpenFlow Protocol FlowVisor OpenFlow Protocol OpenPipes Policy OpenFlow Switch OpenFlow Switch FlowVisor slices OpenFlow networks, crealng mullple isolated and programmable logical networks on the same physical topology.

50 OpenPipes Plumbing with OpenFlow to build hardware systems Partition hardware designs Mix resources Test

51 Plug- n- Serve: Load- Balancing Web Traffic using OpenFlow Goal: Load- balancing requests in unstructured networks What we are showing OpenFlow- based distributed load- balancer Smart load- balancing based on network and server load Allows incremental deployment of addilonal resources OpenFlow means Complete control over traffic within the network Visibility into network condilons Ability to use exislng commodity hardware This demo runs on top of the FlowVisor, sharing the same physical network with other experiments and produc;on traffic.

52 Dynamic Flow AggregaLon on an OpenFlow Network Scope Different Networks want different flow granularity (ISP, Backbone, ) Switch resources are limited (flow entries, memory) Network management is hard Current SoluLons : MPLS, IP aggregalon How OpenFlow Helps? Dynamically define flow granularity by wildcarding arbitrary header fields Granularity is on the switch flow entries, no packet rewrite or encapsulalon Create meaningful bundles and manage them using your own soxware (reroute, monitor) Higher Flexibility, Be\er Control, Easier Management, Experimenta5on

53

54 InterconLnental VM MigraLon Moved a VM from Stanford to Japan without changing its IP. VM hosted a video game server with aclve network conneclons.

55 ElasLcTree: Reducing Energy in Data Center Networks Shuts off links and switches to reduce data center power Choice of oplmizers to balance power, fault tolerance, and BW OpenFlow provides network routes and port stalslcs The demo: Hardware- based 16- node Fat Tree Your choice of traffic pacern, bandwidth, oplmizalon strategy Graph shows live power and latency varialon demo credits: Brandon Heller, Srini Seetharaman, Yiannis Yiakoumis, David Underhill

56 Lunch is at 12:30 Back to hands- on Downloads: hcp:// /openflow/ InstrucLons: hcp:// Updates: Username and password are Mininet keep going don t stop at any step you can install VMware tools if you d like it s not necessary Windows Users: if you DISPLAY not set when trying to launch an xterm, go to PuTTY- >ConnecLon- >X11 Forwarding- > Click on Enable X11 Forwarding Please refresh the instruclons page Note: sudo dpctl show nl:0 nl short for NetLink, not N one May need to restart the regression tests once if nothing happens

57 Lunch Time!!!

58 OpenFlow ImplementaLons (Switch and Controller)

59 Stanford Reference Implementation Linux based Software Switch Release concurrently with specification Kernel and User Space implementations Note: no v1.0 kernel-space implementation Limited by host PC, typically 4x 1Gb/s Not targeted for real-world deployments Useful for development, testing Starting point for other implementations Available under the OpenFlow License (BSD Style) at

60 Wireless Access Points Two Flavors: OpenWRT based (Busybox Linux) v0.8.9 only Vanilla SoXware (Full Linux) Only runs on PC Engines Hardware Debian disk image Available from Stanford Both implementa;ons are so?ware only.

61 NetFPGA NetFPGA- based implementalon Requires PC and NetFPGA card Hardware accelerated 4 x 1 Gb/s throughput Maintained by Stanford University $500 for academics $1000 for industry Available at hcp://

62 Open vswitch Linux-based Software Switch Released after specification (v1.0 support 1 week old!) Not just an OpenFlow switch; also supports VLAN trunks, GRE tunnels, etc Kernel and User Space implementations Limited by host PC, typically 4x 1Gb/s Available under the Apache License (BSD Style) at

63 OpenFlow Vendor Hardware Core Router Prototype Cisco Catalyst 6k (prototype) Juniper MX- series (prototype) Product HP ProCurve 5400 and others Enterprise Campus Data Center Cisco Catalyst 3750 (prototype) Arista 7100 series (Q4 2010) Pronto NEC IP8800 Circuit Switch Ciena CoreDirector WiMAX (NEC) more to follow... Wireless 63

64 HP ProCurve 5400 Series (+ others) Chassis switch with up to 288 ports of 1G or 48x10G (+ other interfaces available) Line-rate support for OpenFlow Deployed in 23 wiring closets at Stanford Limited availability for Campus Trials Contact HP for support details Praveen Yalagandula Jean Tourrilhes Sujata Banerjee Rick McGeer Charles Clark

65 NEC IP x/48x 1GE + 2x 10 GE Line-rate support for OpenFlow Deployed at Stanford Available for Campus Trials Supported as a product Contact NEC for details: Don Clark (don.clark@necam.com) Atsushi Iwata (a-iwata@ah.jp.nec.com) Atsushi Iwata Hideyuki Shimonishi Jun Suzuki Masanori Takashima Nobuyuki Enomoto Philavong Minaxay Shuichi Saito (NEC/NICT) Tatsuya Yabe Yoshihiko Kanaumi (NEC/NICT)

66 Pronto Switch Broadcom based 48x1Gb/s + 4x10Gb/s Bare switch you add the software Supports Stanford Indigo and Toroki releases See openflowswitch.org blog post for more details

67 Stanford Indigo Firmware for Pronto Source available under OpenFlow License to parties that have NDA with BRCM in place Targeted for research use and as a baseline for vendor implementations (but not direct deployment) No standard Ethernet switching OpenFlow only! Hardware accelerated Supports v1.0 Contact Dan Talayco (dtalayco@stanford.edu)

68 Toroki Firmware for Pronto Fastpath-based OpenFlow Implementation Full L2/L3 management capabilities on switch Hardware accelerated Availability TBD

69 Ciena CoreDirector Circuit switch with experimental OpenFlow support Prototype only Demonstrated at Super Computing 2009

70 Juniper MX Series Up to 24-ports 10GE or 240-ports 1GE OpenFlow added via Junos SDK Hardware forwarding Deployed in Internet2 in NY and at Stanford Prototype Availability TBD Umesh Krishnaswamy Michaela Mezo Parag Bajaria James Kelly Bobby Vandalore

71 Cisco 6500 Series Various configurations available Software forwarding only Limited deployment as part of demos Availability TBD Work on other Cisco models in progress Pere Monclus Sailesh Kumar Flavio Bonomi

72 Stanford Reference Controller Comes with reference distribution Monolithic C code not designed for extensibility Ethernet flow switch or hub

73 NOX Controller Available at Open Source (GPL) Modular design, programmable in C++ or Python High-performance (usually switches are the limit) Deployed as main controller in Stanford MarLn Casado Scoc Shenker Teemu Koponen Natasha Gude JusLn Pe t

74 Simple Network Access Control (SNAC) Available at Policy + Nice GUI Branched from NOX long ago Available as a binary Part of Stanford deployment

75 Deployments

76 OpenFlow Deployment at Stanford Switches (23) APs (50) WiMax (1) 76

77 Live Stanford Deployment StaLsLcs hcp://yuba.stanford.edu/o allway/wide- right.html hcp://yuba.stanford.edu/o allway/wide- lex.html

78 GENI OpenFlow deployment (2010) 8 UniversiLes and 2 NaLonal Research Backbones

79 Three EU Projects similar to GENI: Ophelia, SPARC, CHANGE Pan-European experimental facility L2 Packet EmulaLon Wireless Content delivery L2 Packet Wireless RouLng L2 Packet OpLcs Content delivery L2 Packet Shadow networks L2 L3Packet OpLcs Content delivery 79

80 Other OpenFlow deployments Japan UniversiLes interconnected by JGN2plus Interest in Korea, China, Canada,

81 An Experiment of OpenFlow- enabled Network (Feb Sapporo Snow FesLval Video Transmission) Seoul OpenFlow Switch (Linux PC) Suwon NOX OpenFlow Controller TJB Daejeon Controller VLAN on KOREN Data Transmission TJB BroadcasLng Company KOREA OpenFlow Network Gwangju Deagu Busan A video clip of Sapporo snow feslval is transmiced to TJB (Daejeon, KOREA) via ABC server (Osaka, JAPAN). Japan OpenFlow Network Sapporo Studio Sapporo Japan Server Asahi BroadcasLng CooperaLon (ABC) at Osaka, Japan

82 Highlights of Deployments Stanford deployment McKeown group for a year: produclon and experiments To scale later this year to enlre building (~500 users) NaLon- wide trials and deployments 7 other universiles and BBN deploying now GEC9 in Nov, 2010 will showcase nalon- wide OF Internet 2 and NLR to deploy before GEC9 Global trials Over 60 organizalons experimenlng 2010 likely to be a big year for OpenFlow

83 Current Trials 68 trials/deployments spanning 13 countries

84 Hands- on Session Break at 3:30, be back at 4:00pm Downloads: hcp:// /openflow/ InstrucLons: hcp:// Updates: Username and password are Mininet keep going don t stop at any step you can install VMware tools if you d like it s not necessary Windows Users: if you DISPLAY not set when trying to launch an xterm, go to PuTTY- >ConnecLon- >X11 Forwarding- > Click on Enable X11 Forwarding Please refresh the instruclons page Note: sudo dpctl show nl:0 nl short for NetLink, not N one May need to restart the regression tests once if nothing happens

85 Ge ng Involved

86 Interest in OpenFlow

87 Live Website Access Stats

88 Ways to get involved Ask and answer queslons on mailing lists: openflow- discuss openflow- spec Share and update wiki content Submit bugreports and/or patches to OF reference implementalon

89

90 Are you innovalng in your network? Is Brazil innovalng in its networks?

91

92 Slide Credits Guido Appenzeller Nick McKeown Guru Parulkar Rob Sherwood Lots of others

93 More thanks! Marcos Salvador Michael Stanton ChrisLan Esteve

94 Thanks! hcp://