Workshop on Enabling Innovations in
Your Network with OpenFlow
8:45 - 9:00am Welcome
9:00 - 9:30am State of OpenFlow and E-GENI
9:30 - 10:00am
Stanford E-GENI/OpenFlow Demonstrations
10:00 - 10:30am
Break
10:30 - 11:00am
NOX: OpenFlow Controller and Creating New Network
Capabilities 11:00 - 11:30am
Google perspective on OpenFlow and its potential
11:30 - 11:40am
OpenFlow as a Networking Substrate for GENI
11:40 - 12:00noon
General Q & A
Software-defined Networking
and OpenFlow
Campus Trials Workshop
Stanford, Aug 27 2009
Nick McKeown
nickm@stanford.edu
Supported by NSF, Stanford Clean Slate Program, Cisco, DoCoMo, DT, Ericsson, NEC, Xilinx
In a nutshell
A revolution is just starting in networking
Driven by cost and control
It started in data centers…. and is spreading
Trend is towards an open-source,
software-defined network
Why the revolution
Example: New data center
Cost
Control
500,000 servers
Fanout of 50  10,000 switches
$10k commercial switch  $100M
$1k custom-built switch  $10M
1.Optimize for features needed
2.Customize for services & apps
3.Quickly improve and innovate
Savings in 10 data centers = $900M
Software-defined Network
Data Centers
Cost and control
Network & Cellular operators
Bit-pipe avoidance
Cost and control
Security and mobility
Researchers
GENI, FIRE, …
Owners, operators,
administrators, developers,
…improve, update, fix,
experiment, share,
build-upon, and version
their own network.
Process of innovation
Deployment
Idea/Feature
Standardize
Wait 10 years
What is the role of standardization in an open world?
What form might it take?
What form might it take?
1.
Hardware abstraction:
A simple low-cost hardware substrate
A clean separation between the substrate
and an open programming environment
Very few preconceived ideas about how
the substrate will be programmed
Strong isolation between features
But most of all….
Open-source will play
a large role
App
App
Linux
(OS)
x86
(Computer)
App
App
App
NOX
(Network OS)
OpenFlow
Hardware substrate below
+ Programmability
+ Strong isolation model
+ Competition above
 Faster innovation
App
Researchers have an opportunity
Shape the future network
Or at least ride the wave
Hence the GENI Campus Trials
Put another way…
The train is about to leave the station.
Are we driving the train, are we passengers,
or are we left on the platform?
Researchers will need simple
App
App
App
Windows
Windows
Windows
(OS)
(OS)
(OS)
Linux
Linux
Linux
Virtualization
x86
(Computer)
App
App
App
Mac
Mac
Mac
OS
OS
OS
Controller
Controller
NOX
11OS)
(Network
Controller
Controller
Network
22 OS
Virtualization (FlowVisor)
OpenFlow
OpenFlow as a
sliceable substrate
Step 1:
Separate intelligence from datapath
Operators, users, 3rd party developers, researchers, …
New function!
Step 2: Cache decisions in minimal
flow-based datapath
“If header = x, send to port 4”
“If header = y, overwrite header with z, send to ports 5,6”
“If header = ?, send to me”
Flow
Table
Slicing
Slicing
Slicing dimensions
Traffic: “Flowspace”
Link bandwidth
Switch CPU bandwidth
Method 1: Slicing using VLANs
Sliced OpenFlow Switch
Controller C
C VLANs
B VLANs
A VLANs
Controller B
Flow Table
Controller A
Flow Table
Flow Table
(Legacy VLANs)
Normal L2/L3 Processing
Some prototype OpenFlow switches do this…
Method 2: FlowVisor
WiMax-WiFi Tricast Lossless
Handover
Handover
Learning
switch
Mobile VMs
Alices’s
FlowVisor
Production
Network
Controller
GENI
New BGP
Bob’s
FlowVisor
GENI’s
FlowVisor
OpenFlow Protocol
OpenFlow Protocol
OpenFlow
Switch
OpenFlow
Switch
OpenFlow
Switch
GENI
Aggregate Manager
College Campus Trials
College Campus Trials
Seven campuses (+ Stanford)
Clemson, Georgia Tech, Indiana, Princeton,
Rutgers, U Washington, UW-Madison
Expect 5-10 additional campuses
Growth
Efforts starting in Japan, EU, Korea
Goal: 100 campuses in 3-5 years
Interconnection
Small OpenFlow backbone in Internet2 & NLR
Switches, routers,
APs, and Basestations
Switches/routers
Arista, Cisco, HP, Juniper, NEC, Toroki
Quanta/Stanford, NetFPGA
Linux switch
Open vSwitch
Wireless
WiFi: PC Engines (Linux), Linksys (OpenWrt)
WiMAX: NEC
Outreach
Use
r
Timeline
Expected researchers:
50+
Expected Users: 1000+
Expected researchers: 300+
Expected Users: 10000+
Select 20
campuses
Demo
Tutorials, Demos, and Add to Online Tools and Presence
Deploy
Plan Multi-campus Demo
Small deployments at 7 campuses
Small scale demo
Capstone Demo
Scale deployments at 7
campuses
Integrate larger
deployments with GENI
Build
Continue to work with vendors to support OpenFlow in their select products
Continue to develop and thoroughly test EGENI
components
0
6
Continue to build network services and deploy them
Upgrade OpenFlow components as necessary
12
18
24
Learn more
http://OpenFlowSwitch.org