PPJ-04

PPJ-04 SDN Applications
http://eueung.github.io/EL5244/
Software Defined Networking

1. PPJ #4 Virtualization & Software Defined Networking http://eueung.github.io/EL5244/ Dr.-Ing. Eueung Mulyana | 2015H2
2. This material is mainly a derivative and remix work. Most of the texts and illustrations are taken from the talks/lectures given by the referenced networking professors/gurus/ninjas (Credits at the end of the Slide).
3. SDN Applications
4. Example SDN/OF Applications • OSPF - RFC 2328: 245 pages • Distributed System - Builds consistent, up-to-date map of the network: 101 pages • Dijkstra’s Algorithm - Operates on map: 4 pages
5. Example SDN/OF Applications
6. Example SDN/OF Applications • Server load balancing • Seamless mobility and migration • Network virtualization • Dynamic access control • Using multiple wireless access points • Energy-efficient networking • Adaptive traffic monitoring • Denial-of-Service attack detection
7. Load Balancing #1
8. Server Load Balancing • Pre-install load-balancing policy • Split traffic based on source IP src=0* src=1*
9. Server Load Balancing Optimal Load Balancer: Ideally each HTTP request would be sent over a path which is lightly loaded to a server which is lightly loaded in order to minimize the request
10. Server Load Balancing KEMP Technologies LoadMasterTM 2400 Current Load Balancer: it can choose only the lightly loaded server
11. Data Center
12. WAN Experiment
13. GENI
14. Server Load Balancing N. Handigol, S. Seetharaman, M. Flajslik, R. Johari, and N. McKeown. Aster*x: Load-balancing as a network primitive. 9th GENI Engineering Conference (Plenary), November 2010
15. Server Load Balancing Nikhil’s Experiment: <500 lines of code
16. Seamless Mobility #2
17. Seamless Mobility • See host sending traffic at new location • Modify rules to reroute the traffic
18. Using all the wireless capacity around us KK Yap, Masayoshi Kobayashi, Yiannis Yiakoumis, TY Huang
20. Network Virtualization #3
21. Network Virtualization Partition the space of packet headers Controller #1 Controller #2 Controller #3
22. Experiment Network OS: NOX Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Slicing Layer: FlowVisor Experiment NOX Experiment NOX Experiment NOX
23. Access Control #4
24. Dynamic Access Control • Inspect first packet of a connection • Consult the access control policy • Install rules to block or route traffic
25. AC with Virtualization A B Global Network View AB drop AB drop Operator’s goal: prevent A’s packets from reaching B Control program does so with access control entries: • Control program must respond to topology/routing changes • Makes it hard to write correct control program
26. AC with Virtualization A B Global Network View AB drop AB drop A B Abstract Network View AB drop Hypervisor then inserts flow entries as needed
27. Network OS Global Network View Virtual Topology Network Hypervisor
28. SDN @ Industry & Research
29. SDN/OF in the Wild • Open Networking Foundation – Google, Facebook, Microsoft, Yahoo, Verizon, Deutsche Telekom, and many other companies • Commercial OpenFlow switches – Intel, HP, NEC, Quanta, Dell, IBM, Juniper, … • Network operating systems (NOS/Controller) – NOX, Beacon, Floodlight, Nettle, ONIX, POX, Frenetic • Network deployments – Eight campuses, and two research backbone networks – Commercial deployments (e.g., Google backbone)
30. SDN in Development Domains • Data Centers • Enterprise/Campus • Cellular Backhaul • Enterprise WiFi • WANs Products • Switches, routers: … vendors • Software: … vendors and startups
31. A Major Trend in Networking Entire backbone runs on SDN Bought for $1.2 x 109 (mostly cash)
32. How SDN Shaping Industry? • Open Networking Foundation (ONF) • OpenDaylight (ODL) – Led by IBM and Cisco – Mission is to develop open source SDN platform
33. How SDN Shaping Industry? ONF • New non-profit standards organization (Mar 2011) • Defining standards for SDN, starting with OpenFlow Board of Directors • Google, Facebook, Microsoft, Yahoo, DT, Verizon 39 Member Companies (2011) • Cisco, VMware, IBM, Juniper, HP, Broadcom, Citrix, NTT, Intel, Ericsson, Dell, Huawei, …
34. How SDN Shaping Industry? Cellular Industry • Recently made transition to IP • Billions of mobile users • Need to securely extract payments and hold users accountable • IP is bad at both, yet hard to change SDN enables industry to customize their network
35. How SDN Shaping Industry? Telco Operators • Global IP traffic growing 40- 50% per year • End-customer monthly bill remains unchanged • Therefore, CAPEX and OPEX need to reduce 40-50% per Gb/s per year • But in practice, reduces by ~20% per year SDN enables industry to reduce OPEX and CAPEX …and to create new differentiating services
36. How SDN Shaping Industry? Big Companies • Google B4: deployed SDN to manage cross data center traffic • Microsoft SWAN: software defined WAN • Facebook: infrastructure team exploring SDN • VMware: Nicira, overlay approach to SDN • Intel: OpenFlow switch • Cisco: OpenFlow switch • AT&T: Domain 2.0 • …
37. How SDN Shaping Industry? Startups • Affirmed Networks: virtualized subscriber and content management tools for mobile operators • Big Switch Networks: OpenFlow-based SDN switches, controllers and monitoring tools • Embrane: layer 3-7 SDN services to enterprises and service providers • Accelera: software defined wireless networks funded by Stanford Professor Andrea Goldsmith …
38. Example: New Data Center Cost 200,000 servers Fanout of 20  10,000 switches $5k vendor switch = $50M $1k commodity switch = $10M Savings in 10 data centers = $400M Control More flexible control Tailor network for services Quickly improve and innovate
39. How SDN Shaping Research? Ease of trying new ideas – Existing tools: Floodlight, NOX, Beacon, Switches, Mininet – More rapid technology transfer – GENI, FIND and many more A stronger foundation to build upon – Provable properties of forwarding – New languages and specification tools
40. How SDN Shaping Research? • Research activities (TBU) – Open Networking Summit started in 2011 – ACM HotSDN workshop started in 2012 – ACM SIGCOMM, USENIX NSDI sessions
41. SDN Research Areas SDN applications Controller scalability • multi-controller • reduce messages sent to controller • switch/CPU design approaches Network Updates Programming Testing/Debugging Traffic Management/QoS • Flow scheduling • Load balancing • Transport protocol Monitoring Security SDN architecture
42. Consequences for Standards The role of standards will change: • Network owners will define network behavior • Features will be adopted without standards Programming world • Good software is adopted, not standardized Standards will define the interfaces
43. Notes
44. SDN “Implementations” (SW/HW) Forwarding Model • OpenFlow • ForCES Software Switches compliant with OpenFlow std. • Open vSwitch • Pantou/OpenWRT • Ofsoftswitch13 • Indigo Controller compliant with OpenFlow std. • POX • NOX • MUL • Maestro
45. SDN “Implementations” (SW/HW) Available Commodity Switches compliant with OpenFlow std. • Hewlett-Packard 8200zl, 6600, 6200zl, • Brocade 5400zl, and 3500/3500yl • IBM NetIron CES 2000 Series
46. What Should I Remember About SDN?
47. Four Crucial Points • SDN is merely set of abstractions for control plane – Not a specific set of mechanisms – OpenFlow is least interesting aspect of SDN, technically • SDN involves computing a function…. – NOS handles distribution of state • …on an abstract network – Can ignore actual physical infrastructure • Network virtualization is the “killer app” – Already virtualized compute, storage; network is next
48. Does SDN have larger implications? Aside from providing easier network management, how will SDN change the world of networking?
49. Control/Data Planes Become Separate Currently control plane tied to data plane NOS runs on servers: observes/controls data plane • Changes the deployment and business models – Can buy the control plane separately from the switches – Enabling commodity hardware and 3rd party software • Changes the testing model – Simulator to analyze large-scale control planes
50. Networking Becomes Edge-Oriented Can implement most control functionality at edge • Access control, QoS, mobility, migration, monitoring… Network core merely delivers packets edge-to-edge • Current protocols do a good job (mostly) Let edge handle all complexity • Complicated matching, actions • “Overlay” networking via tunnels This has two important implications
51. (1) Makes SDN Incrementally Deployable Host software often has OpenFlow switch • Open vSwitch (OVS) in Linux, Xen,… The edge becomes a software switch • Core of network can be legacy hardware Enables incremental deployment of SDN • Might never need OpenFlow in hardware switches….
52. (2) Networking Becomes SW-Oriented All complicated forwarding done in software (edge) And control plane is a program (on a server)… • …not a protocol (on a closed proprietary switch/router) We are programming the network, not designing it • Focus on modularity and abstractions, not packet headers Innovation at software, not hardware, speeds Software lends itself to clean abstractions
53. SDN Vision: Networks Become “Normal” • Hardware: Cheap, interchangeable, Moore’s Law • Software: Frequent releases, decoupled from HW • Functionality: Mostly driven by SW – Edge (software switch) – Control program • Solid intellectual foundations
54. Recap - The network is changing Custom Hardware Custom Hardware Custom Hardware Custom Hardware Custom Hardware OS OS OS OS OS Network OS Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature
55. Recap - Software Defined Network (SDN) Control Program 1 Network OS 1. Open interface to packet forwarding 3. Consistent, up-to-date global network view Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Control Program 2 2. At least one Network OS probably many. Open- and closed-source
56. Important!
57. Virtualization is Killer App for SDN Consider a multi-tenant datacenter • Want to allow each tenant to specify virtual topology • This defines their individual policies and requirements Datacenter’s network hypervisor compiles these virtual topologies into set of switch configurations • Takes 1000s of individual tenant virtual topologies • Computes configurations to implement all simultaneously This is what people are paying money for…. Enabled by SDN’s ability to virtualize the network
58. Credit • Scott Shenker, The Future of Networking and the Past of Protocols • Nick McKeown, Stanford University, Many Talks/Articles • Jennifer Rexford, COS 597E, Princeton University • Mike Freedman, COS 461, Princeton University • Nick Feamster, https://www.coursera.org/course/sdn • Li Erran Li, COMS 6998-10, Univ. of Columbia • Marco Cello, SDN Talk @ CNR, Univ. Genova • Guido Appenzeller, Network Virtualization in Multi- tenant Datacenters, VMware