Presentation on theme: "OpenFlow and Software Defined Networks. Outline o The history of OpenFlow o What is OpenFlow? o Slicing OpenFlow networks o Software Defined Networks."— Presentation transcript:
OpenFlow and Software Defined Networks
Outline o The history of OpenFlow o What is OpenFlow? o Slicing OpenFlow networks o Software Defined Networks o Industry interest
Original Question How can researchers on college campuses test out new ideas in a real network, at scale?
Problem Many good research ideas on college campuses… No way to test new ideas at scale, on real networks, with real user traffic Many good research ideas on college campuses… No way to test new ideas at scale, on real networks, with real user traffic Consequence: Almost no technology transfer
Research problems Well known problems Security, mobility, availability Well known problems Security, mobility, availability Incremental ideas Fixing BGP, multicast, access control, Mobile IP, data center networks. Incremental ideas Fixing BGP, multicast, access control, Mobile IP, data center networks. More radical changes Energy management, VM mobility, … More radical changes Energy management, VM mobility, …
How to build a test network with sufficient scale and realism?
Software Router PC + Multi-Port NIC Total capacity: Only ~5Gb/s
Difficult to develop, always behind industry Difficult to program, constrained environment Too expensive Custom Hardware
Million of lines of source code 6,000 RFCs Billions of gates BloatedPower Hungry Vertically integrated, complex, closed, proprietary Not suitable for experimental ideas Specialized Packet Forwarding Hardware Operating System Operating System Feature Routing, management, mobility management, access control, VPNs, … Modify Existing Equipment
The only test network large enough to evaluate future Internet technologies at scale, is the Internet itself.
OpenFlow Protocol Data Path (Hardware) Control PathOpenFlow Controller (Server Software) App
Slicing traffic All network traffic Untouched production traffic Research traffic Experiment #1 Experiment #2 … Experiment N
Research Experiments Step 1: Separate Control from Datapath
Step 2: Cache flow decisions in datapath If header = x, send to port 4 If header = ?, send to me If header = y, overwrite header with z, send to ports 5,6 Flow Table Flow Table
Plumbing Primitives Match arbitrary bits in headers: – 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 16 Header Data Match: 1000x01xx x
General Forwarding Abstraction Small set of primitives Forwarding instruction set Small set of primitives Forwarding instruction set Protocol independent Backward compatible Protocol independent Backward compatible Switches, routers, WiFi APs, basestations, TDM/WDM
Slicing an OpenFlow Network
Ways to use slicing Slice by feature Slice by user Slice by feature Slice by user Home-grown protocols Download new feature Versioning Home-grown protocols Download new feature Versioning
Research Examples (See openflow.org/Research for demo videos)
Broader interest in an evolvable Internet
Specialized Packet Forwarding Hardware Feature Specialized Packet Forwarding Hardware Operating System Operating System Operating System Operating System Operating System Operating System Operating System Operating System Operating System Operating System Network OS Feature Restructured Network
Feature Network OS 1. Open interface to packet forwarding 3. Well-defined open API 2. At least one Network OS probably many. Open- and closed-source Software-Defined Network Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding Packet Forwarding
Network OS Research – NOX (C++/Python) – Maestro (Rice University) – Helios (NEC) – Beacon (Java) coming soon. – Others in development Commercial – ONIX [OSDI 2010, Google, Nicira, NEC] – Expect others
Cellular industry Recently made transition to IP Billions of mobile users Need to securely extract payments and hold users accountable IP sucks at both, yet hard to change OpenFlow provides a way for the cellular industry to solve real problem plaguing their networks.
Telco Operators Global IP traffic growing 40-50% per year End-customer monthly bill remains unchanged Therefore, CAPEX and OPEX need to reduce % per Gb/s per year But in practice, reduces by ~20% per year And based on the same equipment as competitors OpenFlow allows telcos to reduce CAPEX, OPEX and to add new differentiating features to their networks.
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 Data center companies have been the first to deploy OpenFlow in their networks.
OpenFlow Standardization Version 1.0: Most widely used version Version 1.1: Released in February OpenFlow transferred to ONF in March 2011.