The document discusses software-defined networking (SDN), highlighting the decoupling of the network control plane from physical topology and its implications for organizations. It emphasizes the challenges of writing a custom control plane due to the complexity and required engineering resources, suggesting that most enterprises find in-house development unappealing. The benefits of SDN stem from its openness, enabling integration and customization of applications without the need for developing proprietary solutions.

3. Opening
Up
Your
Network
with
SDN
Guido
Appenzeller
Big
Switch
Networks

4. SDN/OPENFLOW ECOSYSTEM!
Timeline
2007
2008
2009
2010
2011
2012
OpenFlow
Switches
Research
Demos
Prototypes
Many
more!
0.2
OpenFlow
Standard
1.0
1.0
0.9
0.8.9
OF
1.1
OF
1.2
1.1
OF
1.X
OF
2.0
1.2

5. So>ware
defined
Networking
at
a
Crossroads
Open? Closed?
SDN

6. Why
does
this
maDer?

7. Wikipedia
DefiniFon:
„A network architecture in which the network
control plane is decoupled from the physical
topology.”
What
is
So>ware
Defined
Networking?
What
a
network
administrator
hears:
• (Yet)
another
vendor
in
your
mission
criFcal
network
• If
this
system
(the
SDN
controller)
goes
down,
so
does
the
enFre
network
• You
carry
all
the
integraFon
risk
• Did
I
menFon
this
is
brand
new
technology?

8.  SDN
allows
you
to
write
your
own
control
plane
 Is
this
aDracFve
for
organizaFons
deploying
SDN?
 Are
customers
going
to
write
their
own?
 They
won’t.
It’s
very
difficult,
requires
a
large
engineering
team
with
diverse
skills.
More
“features”
of
SDN…

9.  SDN
allows
you
to
write
your
own
control
plane
 Is
this
aDracFve
for
organizaFons
deploying
SDN?
 Are
customers
going
to
write
their
own?
 They
won’t.
It’s
very
difficult,
requires
a
large
engineering
team
with
diverse
skills.
More
“features”
of
SDN…
Actually,…

10.  SDN
allows
you
to
write
your
own
control
plane
 Is
this
aDracFve
for
organizaFons
deploying
SDN?
 Are
customers
going
to
write
their
own?
 In-­‐house
development
unaDracFve
for
most
Enterprises
 Sufficient
economies
of
scale
may
exist
for
Hyperscale
Data
Centers
and
certain
very
specialized
applicaFons
More
“features”
of
SDN…

11.  SDN
allows
you
to
write
your
own
control
plane
 Is
this
aDracFve
for
organizaFons
deploying
SDN?
 Are
customers
going
to
write
their
own?
 In-­‐house
development
unaDracFve
for
most
Enterprises
 Sufficient
economies
of
scale
may
exist
for
Hyperscale
Data
Centers
and
certain
very
specialized
applicaFons
 If
you
buy
a
closed
control
plane
from
a
single
vendor,
what
have
you
gained?
 Easier
for
vendors
to
deliver
certain
applicaFons
 Example:
Network
VirtualizaFon.
All
modern
implementaFons
(that
I
am
aware
of)
use
a
centralized
conrtol
plane.
More
“features”
of
SDN…

12. So
why
is
SDN
being
adopted?

13.  The
thing
that
changes
this
value
prop
is
SDN
being
open

SDN
is
not
about
wriFng
your
own
control
plane.
 That's
hard.
 Few
will
do
it.

Instead
this
is
mostly
about
integraFon
 You
don’t
need
to
write
your
own
 Build
your
own
(lightweight)
apps
on
an
exisFng
control
plane
 Modify
exisFng
Open
Source
Controller
 Mix
and
Match
ApplicaFons
Open
SDN

14.  Private
Cloud
 vArmour
 vSwitch/ToR
IntegraFon
Three
Examples

15. Source: team estimates based on interviews across 8 enterprise and university network professionals in planning,
pilots or production with private cloud architectures
~3-­‐6x
increase
in
networking
related
trouble
Fckets
per
month
a>er
moving
to
private
cloud
compuFng
model
The
hidden
headaches
of
moving
to
a
private
cloud
Networking
and
Server
VirtualizaFon

16. 1
4
Separate
administraFon
has
liDle
benefit
Example
1:
Private
Cloud
Cloud
OrchestraFon
Switch
Switch
Switch
Switch
Controller
Network
VirtualizaFon

17. Open
API
enables
automaFon
Example
1:
Private
Cloud
Cloud
OrchestraFon
Switch
Switch
Switch
Switch
Controller
Network
VirtualizaFon
API

18. Open
API
enables
automaFon
Example
1:
Private
Cloud
Cloud
OrchestraFon
Switch
Switch
Switch
Switch
Controller
Network
VirtualizaFon
API
Sample
API
Calls:
 Create Virtual Network
 New Host Location
 Notification if Unknown Host

19. Firewall
for
East/West
Traffic
Example
2:
vArmour
ToR
Switch
vSwitch
vSwitch
vSwitch
VM"
VM"
VM-1"
VM"
VM-2"
VM"
ToR
Switch
vSwitch
vSwitch
vSwitch
Firewall"
VM"
VM"
VM"
VM"
VM"
Physical
Server
ToR
Switch
vSwitch
VM"
VM"
AggregaFon
Switch
AggregaFon
Switch
AggregaFon
Switch
Physical
Server

20. Service
InserFon:
How
can
I
deploy
a
firewall?
Example
2:
vArmour"
ToR
Switch
vSwitch
vSwitch
vSwitch
VM"
VM"
VM-1"
VM"
VM-2"
VM"
ToR
Switch
vSwitch
vSwitch
vSwitch
Firewall"
VM"
VM"
VM"
VM"
VM"
Physical
Server
ToR
Switch
vSwitch
VM"
VM"
AggregaFon
Switch
AggregaFon
Switch
AggregaFon
Switch
Physical
Server
???

21. Floodlight
Open
Source
Controller
Example
2:
vArmour
Switch
Switch
Switch
Switch
Switch
Floodlight
Forwarding
Device
Manager
Topology

22. Open
Source
provided
easy
integraFon
and
maximum
flexibility
Example
2:
vArmour
Switch
Switch
Switch
Switch
Switch
Floodlight
Forwarding
Device
Manager
Topology
vArmour

23. Open
Source
allowed
easy
IntegraFon
Example
2:
vArmour
Switch
Switch
Switch
Switch
Switch
Floodlight
Forwarding
Device
Manager
Topology
vArmour
 Engineering
Advantages
 Open
Source
allows
full
access
to
integraFon
layer
 Core
applicaFons
can
be
augmented
if
needed
 Business
Model
 Customers
can
mix
and
match
applicaFons
from
different
vendors
 Choice
of
Open
Source
vs.
commercial
controller
 No
lock-­‐in
for
vArmour

24. Traffic
from
a
VM
to
a
physical
server
Example
3:
vSwitch/ToR
IntegraFon
ToR
Switch
vSwitch
vSwitch
vSwitch
VM"
VM"
VM"
VM"
VM"
VM"
ToR
Switch
vSwitch
vSwitch
vSwitch
VM"
VM"
VM"
VM"
VM"
VM"
Physical
Server
ToR
Switch
vSwitch
VM"
VM"
AggregaFon
Switch
AggregaFon
Switch
AggregaFon
Switch
Physical
Server

25. Different
soluFons
exist,
all
require
thight
Tor/vSwitch
integraton
Example
3:
vSwitch/ToR
IntegraFon
ToR
Switch
vSwitch
vSwitch
vSwitch
VM"
VM"
VM"
VM"
VM"
VM"
ToR
Switch
vSwitch
vSwitch
vSwitch
VM"
VM"
VM"
VM"
VM"
VM"
Physical
Server
ToR
Switch
vSwitch
VM"
VM"
AggregaFon
Switch
AggregaFon
Switch
AggregaFon
Switch
Physical
Server

26. Customer
pick
best-­‐of-­‐breed
vendors
Example
3:
vSwitch/ToR
IntegraFon
Physical
Network
Virtual
Network

27. Open
Protocols
allow
vSwitch/ToR
integraFon
Open
Protocols
vSwitch
vSwitch
vSwitch
ApplicaFon
A
Switch
Switch
Switch
ApplicaFon
B
Open
Protocols
Open
Protocols
Controller

28. With
closed
protocols
it
is
not
possible
Closed
Protocols
vSwitch
vSwitch
vSwitch
Controller
A
Switch
Switch
Switch
Controller
B
Closed
Protocol
B
Closed
Protocol
A
Physical
Network
Virtual
Network

29. 1) Open
APIs
2) Open
source
3) Open
Protocols
Open
SDN
Being
Open
is
criFcal
for
SDN’s
Success
Switch
Switch
Switch
Switch
Switch
Controller
ApplicaFon
ApplicaFon
ApplicaFon
ApplicaFon

30. See
it
live?
Please
visit
the
demos
of
our
partners
that
showcase
Open
SDN
by
Big
Switch
Networks.

31. Thank
you!