PPJ #4

Virtualization & Software Defined Networking

http://eueung.github.io/EL5244/

Dr.-Ing. Eueung Mulyana | 2015H2

 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).
SDN Applications
 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
Example SDN/OF Applications
 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
 #1
Load Balancing
 Server Load Balancing
• Pre-install load-balancing policy
• Split traffic based on source IP

src=0*

src=1*
 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
Server Load Balancing
Current Load Balancer:
it can choose only the
lightly loaded server

KEMP Technologies
LoadMasterTM 2400
Data Center
 WAN
Experiment
GENI
 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
Server Load Balancing
Nikhil’s Experiment:
<500 lines of code
 #2
Seamless Mobility
Seamless Mobility
• See host sending traffic at new
location
• Modify rules to reroute the traffic
 Using all the wireless capacity
around us

KK Yap, Masayoshi Kobayashi, Yiannis Yiakoumis, TY Huang

 #3
Network Virtualization
 Network Virtualization
Controller #1 Controller #2 Controller #3

Partition the space of packet headers

 Experiment Experiment Experiment
NOX Experiment
NOX NOX
Slicing
Network
Layer:OS:
FlowVisor
NOX

Packet
Forwarding Packet
Forwarding

Packet
Packet Forwarding
Forwarding
Packet
Forwarding
 #4
Access Control
Dynamic Access Control
• Inspect first packet of a connection
• Consult the access control policy
• Install rules to block or route traffic
 AC with Virtualization
Operator’s goal: prevent A’s packets from reaching B

Control program does so with access control entries:

Global
• Control program must respond to topology/routing
changes
Network View
• Makes it hard to write correct control program

AB drop

AB drop

B
A
AC with Virtualization
AB Abstract
B
drop Network View
Global
Network View

AB drop
Hypervisor then
inserts flow
entries as AB drop
needed

B
 Virtual Topology

Network Hypervisor

Global Network View

Network OS
SDN @ Industry & Research
 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)
 SDN in Development
Domains Products
• Data Centers • Switches, routers: …
• Enterprise/Campus vendors
• Cellular Backhaul • Software: … vendors and
• Enterprise WiFi startups
• WANs
A Major Trend in Networking

Entire backbone

runs on SDN

Bought for $1.2 x 109

(mostly cash)
 How SDN Shaping Industry?
• Open Networking Foundation (ONF)

• OpenDaylight (ODL)
– Led by IBM and Cisco
– Mission is to develop open source SDN platform
 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, …
 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

 How SDN Shaping Industry?
Telco Operators
• Global IP traffic growing 40-
50% per year SDN enables industry to reduce
• End-customer monthly bill OPEX and CAPEX
remains unchanged
…and to create new
• Therefore, CAPEX and OPEX differentiating services
need to reduce 40-50% per
Gb/s per year
• But in practice, reduces by
~20% per year
 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
• …
 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
…
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
 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
 How SDN Shaping Research?
• Research activities (TBU)
– Open Networking Summit started in 2011
– ACM HotSDN workshop started in 2012
– ACM SIGCOMM, USENIX NSDI sessions
 SDN Research Areas
Controller scalability
• multi-controller
Traffic Management/QoS

SDN applications
•
SDN architecture

reduce messages sent to controller

• Flow scheduling
• switch/CPU design approaches
• Load balancing
• Transport protocol

Network Updates
Monitoring

Programming
Security

Testing/Debugging
 Consequences for Standards
The role of standards will
change:
• Network owners will define
network behavior Standards will define the
• Features will be adopted interfaces
without standards

Programming world
• Good software is adopted,
not standardized
Notes
SDN “Implementations” (SW/HW)
Forwarding Model Controller compliant with
• OpenFlow OpenFlow std.
• ForCES • POX
• NOX
Software Switches compliant • MUL
with OpenFlow std. • Maestro
• Open vSwitch
• Pantou/OpenWRT
• Ofsoftswitch13
• Indigo
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
What Should I Remember About
SDN?
 Four Crucial Points
• SDN is merely set of • …on an abstract network
abstractions for control plane – Can ignore actual physical
– Not a specific set of infrastructure
mechanisms
– OpenFlow is least interesting • Network virtualization is the
aspect of SDN, technically
“killer app”
– Already virtualized compute,
• SDN involves computing a storage; network is next
function….
– NOS handles distribution of
state
Does SDN have larger implications?
Aside from providing easier network management,
how will SDN change the world of networking?
Control/Data Planes Become Separate
• Changes the deployment and
Currently control business models
plane tied to data – Can buy the control plane
plane separately from the switches
– Enabling commodity hardware and
3rd party software
NOS runs on
servers:
observes/controls • Changes the testing model
data plane – Simulator to analyze large-scale
control planes
 Networking Becomes Edge-Oriented
Can implement most control Let edge handle all complexity
functionality at edge • Complicated matching, actions
• Access control, QoS, mobility, • “Overlay” networking via
migration, monitoring… tunnels

This has two important

Network core merely delivers implications
packets edge-to-edge
• Current protocols do a good
job (mostly)
(1) Makes SDN Incrementally Deployable
Host software often has OpenFlow Enables incremental deployment of
switch SDN
• Open vSwitch (OVS) in Linux, • Might never need OpenFlow in
Xen,… hardware switches….

The edge becomes a software switch

• Core of network can be legacy
hardware
(2) Networking Becomes SW-Oriented
All complicated We are programming the network, not
forwarding done in designing it
software (edge) • Focus on modularity and abstractions,
not packet headers
And control plane is a
program (on a server)… Innovation at software, not hardware,
• …not a protocol (on a speeds
closed proprietary
switch/router) Software lends itself to clean abstractions
SDN Vision: Networks Become “Normal”
• Hardware: Cheap, • Functionality: Mostly
interchangeable, Moore’s driven by SW
Law – Edge (software switch)
– Control program
• Software: Frequent
releases, decoupled from
HW • Solid intellectual
foundations
Recap - The network is changing
Feature Feature
Network OS
Feature Feature

OS
Feature Feature
Custom Hardware
OS
Feature Feature
Custom Hardware
OS Feature Feature
Custom Hardware
OS
Feature Feature
Custom Hardware

OS
Custom Hardware
 Recap - Software Defined Network (SDN)
3. Consistent, up-to-date global network view 2. At least one Network OS
probably many.
Control Program 1 Control Program 2
Open- and closed-source
Network OS
1. Open interface to packet forwarding

Packet
Forwarding Packet
Forwarding

Packet
Packet Forwarding
Forwarding
Packet
Forwarding
Important!
 Virtualization is Killer App for SDN
Consider a multi-tenant datacenter
• Want to allow each tenant to specify virtual
topology This is what people are
• This defines their individual policies and paying money for….
requirements
Enabled by SDN’s ability
Datacenter’s network hypervisor compiles these to virtualize the
virtual topologies into set of switch configurations network
• Takes 1000s of individual tenant virtual
topologies
• Computes configurations to implement all
simultaneously
 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