(1)(2)
(3)
(4)
(5)
(6)
(7)(8)
(9)(10)(11)
Linkedin
(12)
Linkedin
(13)(14)
(15)(16)(17)(18)(19)
(20)
(21)
(22)
(23)(24)
SDN For Fun and Profit
•
Quick Overview
•
SDN for Fun and Profit – or how we got here
•
SDN Details
»
Evolution
»
Landscape
»
Opportunities
»
Myths
•
Questions and Answers
Agenda For Tonight
•
A. A bad situation in your
bathroom?
•
B. Geriatric medication for
constipated seniors?
•
C. The hottest new protocol
in networking that is a key
driver of the SDN movement
What is OpenFlow?
Copyright 2012. All Rights Reserved. 3
•
Why is SDN needed?
»
Social, mobile, cloud drives requirement for
more compute, storage and networking
power, delivered more flexibly
»
Compute and storage virtualized and
automated
»
But the network lagged….
•
What does SDN address?
»
Inflexibility and inefficiencies of today’s
network
»
Difficulty in manually scaling networks
»
Lack of innovation
First, Why SDN?
•
Our definition: an approach and framework that encompasses:
»
Centralization
of control of the network via the
»
Separation
of
control
logic to off-device compute, that
»
Enables
automation
and
orchestration
of network services via
»
Open
programmatic
interfaces
•
SDN Benefits
»
Efficiency:
optimize existing applications, services, and
infrastructure
»
Scale:
rapidly grow existing applications and services
»
Innovation:
create and deliver new types of applications and
services and business models
What is SDN and What are Its Benefits?
•
Makes networking
cool
again
•
Promises
revamp
of
network – from on-device distributed
control to centralized command
and control
•
Potentially enables
commoditization
of networking gear and poses a
threat to incumbents
•
Opens up networking platforms to
new software
application players,
without requiring large capital investment
Why is SDN so Hot?
Copyright 2012. All Rights Reserved. 6
SDN for Fun and Profit
www.sdncentral.com
www.wiretapventures.com
•
And a bunch of kids to feed
•
Matt Palmer
»
20+ years in cloud, networking and
security
»
Co-Founder/CEO Pareto (cloud
networking company bought by
Aerohive)
»
Managed $500M enterprise business
for Juniper
•
Roy Chua
»
20+ years in networking and security
»
Co-Founded Identity Engines (bought
by Avaya)
»
Co-Founded Caw Networks (acquired
by Spirent Communications)
Who is SDNCentral/Wiretap
Two Guys and a Dog
Copyright 2012. All Rights Reserved. 8
Custom
Solutions
Solutions
Tailored
Packaged
Software
Why Not Build SDN Products?
9
In the first stage of the typical enterprise software market journey
Copyright 2012. All Rights Reserved.
Early Market
Mature Market
Our 3 Businesses
Strategic and
Go-To-Market advisory
services to Vendors
SDN and network
virtualization
consultation,
integration and
custom solutions for
Enterprises and SPs
Independent
Community Site for
SDN and Network
Virtualization
•
Demographics:
»
30%: Buyers
»
10%: Vendors
»
20%: Channels
»
40%: Integrators
•
Key Stats:
»
50k+ monthly page views
»
12k+ monthly unique visitors
»
120+ companies profiled
»
35+ open source project profiled
The Independent Community for Network Virtualization
and SDN
0
5
10
15
20
25
30
35
40
45
Thousands
Web
@SDN_Tech
@SDN_News
Community Participants
Wiretap & SDNCentral Confidential
•
Featured Content:
»
Interviews
»
Products
»
Use Cases
»
Videos
»
Whitepapers
•
eNewsletter
»
Weekly Newsletter
•
Events
»
Webinars
»
Chats
»
Virtual Panels
•
Social Media
»
Tweets
»
SDNCentral
A platform for establishing and expanding SDN thought leadership
SDN Details, Opportunities,
Myths
www.sdncentral.com
www.wiretapventures.com
Evolution of OpenFlow
SANE
ETHANE
OpenFlow
NOX/
OpenFlow
1.0
OpenFlow
1.1
OpenFlow
1.2
OpenFlow
1.3
Stanford Clean Slate/Berkeley
•
Mar0n Casado
•
Nick McKeown
•
ScoC Shenker
•
And others…
RouteFlow
Beacon
POX
Trema
FlowScale
Frene0c
Indigo
FlowVisor
Pantou
Ryu
Copyright 2012. All Rights Reserved. 14
Contrail
Plumgrid
Plexxi
Vello
Pluribis
Cisco
Juniper
Packet-Forwarding Hardware Operating System L2/L3 L4-7 App App
Today’s Networks
Packet-Forwarding Hardware Operating System L2/L3 L4-7 App App Packet-Forwarding Hardware Operating System L2/L3 L4-7 App AppRouters
Switches
Remote-access devices
…
Central Network Controller/ Network Operating System
App
App
App
App
OpenFlow
Packet-Forwarding
Hardware
OpenFlow compliant OS
SDN-Powered Network
Packet-Forwarding
Hardware
OpenFlow compliant OS
Packet-Forwarding
Hardware
OpenFlow compliant OS
Well-‐defined
Open API
History of SDN: Before OpenFlow (BO)
The Distributed Control Plane is not new…..
Separated
Control &
Data Planes
Early ‘90’s
Distributed
Control Plane w/
in Switch
Mid-‐ ‘90’s
All Data w/in
Control Plane
Early ‘00’s
Separated Control
& Data Planes
Late ‘00’s
Past Experience to Draw On
Focused on centralized management &
wireless control-‐plane
Lack of northbound APIs
Control-‐plane/Data-‐plane Separa0on
Ethernet communica0ons channel
In-‐box only, proprietary
Controller-‐based wireless
switches & routers
Chassis-‐based
Opportunities for Market Disruptors
•
Merchant silicon, hardware commoditization
•
Virtual switches, routers, firewalls, etc
•
Orchestration platforms
•
Transition from hardware to software business
models
»
Pricing, support, marketing, sales
•
Network becomes a development
platform
»
Even if switches/controllers stay “linked”
•
Creates a new market for innovative software
•
The controller is not strategic…
Myth #1:
•
Open-source will save you from vendor lock in…
Myth #2
•
We have reference-able customers for your use case
•
Or our SDN is ready to deploy at scale
Myth #3
•
We have revenue
•
…followed by “we are cash flow positive”
Myth #4
•
Only we have the best, most proven SDN engineering
talent
Myth #5
•
Commoditization will kill Cisco
Myth #6
•
SDN will lower your TCO
Myth #7
Common SDN Myths
•
Limited developer communities / concentrated at few companies
•
Usually controlled by single commercial entity. Potentially risky
•
Lack of reference implementation slowing down OpenFlow
Open Source
•
Scrambling to claim everything new is ‘SDN’
•
Spotty and inconsistent support for SDN
•
Not one vendor / product fits all customers or specific problems.
Established
Vendors
•
Attempt to sell packaged products at a stage where value is created by custom
solutions
•
Few or no production customers
Start Ups
•
Early adopters looking to reap competitive advantage via SDN
•
Financials, Web 2.0, Service Providers
•
Most revenue is professional services driven
Customers
SDN Perspectives
21
Our learnings from client engagements & operating SDNCentral
1.
Attempting to Run before Crawling
»
Lack of clear business objective / problem statement
»
Failure to manage expectations
»
Failure to understand limitations of current software & hardware
2.
Believing people who say they know how to solve your problem
»
Usually set up to sell products
»
Product designed 2–3 years back before problems and use cases
are well understood
»
Forces you on a path with solution what was never designed for
the use case in mind
For End Customers, SDN Pitfalls to Avoid
22
