Embed Size (px)
Citation preview
SDN is inevitable
Business reali<es of network operators + Technology trends
Telecom Networks
Core Network
Edge and Aggrega<on Network
Business Reali<es of Telecom Operators
Profit = Revenue – Capex – Opex
Revenue has been more or less flat
¡ Customers consume lot more bit but not willing to pay more for bits
¡ Crea<ng new revenue genera<ng services has been a challenge
Capex keeps growing
¡ Traffic has been doubling every year
¡ Unique appliances have been mul<plying
¡ Expensive proprietary switches/routers/appliances
Opex keeps growing
¡ Each device has its own management/opera<on
¡ Opera<on depends on device centric CLI and manual opera<on
¡ Minimal automa<on
Why is the situa<on so bleak?
Revenue: Limited Services (Connec<vity) ¡ Packet connec<vity ¡ 1Gbps to 10Gbps to 40Gbps
¡ WiFi and cellular wireless connec<vity ¡ Has been primary growth to offset other revenue loss
¡ Support for data, voice, and video ¡ Most complexity to support voice and video end to end
¡ Subscriber management, traffic engineering, VPNs
¡ Security and other capabili<es ¡ Firewall, IDS/DPI, load balancers
Customers not willing to pay more for connec<vity services è limited revenue…
Capex and Opex: Telecom Infrastructure: Core Building Blocks
Closed Proprietary Boxes è Higher Capex and Opex Difficult to program and to introduce services
Edge
Core
Proliferation of Appliances: Example Cellular Access Network:
Access
B
B
B
B
eNodeB
B
B
B
B
eNodeB
B
B
B
B
eNodeB
Firewall DPI
S-GW
IMS Carrier Grade NAT
CDN
SBC
P-GW
Monitor
Difficult to Support Virtual Networks on closed/proprietary not-programmable infrastructure
VM
VM
VM
VM
Lost revenue opportunity for network operators
Future of Computing
Virtual Network of VMs
Business Reali<es of Network Operators
Profit = Revenue – Capex – Opex
Revenue has been more or less flat
¡ Customers consume lot more bits but not willing to pay more for bits
¡ Crea<ng new revenue genera<ng services has been a challenge
Capex keeps growing
¡ Traffic has been doubling every year
¡ Unique appliances have been mul<plying
¡ Expensive proprietary switches/routers/appliances
Opex keeps growing
¡ Each device has its own management/opera<on
¡ Opera<on depends on device centric CLI and manual opera<on
¡ Minimal automa<on
Long term existence is a challenge è Willingness to consider a disrup<ve change
What is SDN? How does it help?
Rou<ng TE
Network OS
Open interface (OpenFlow) to Forwarding Abstrac<on: L1/L2/L3
Well-‐defined open API
Socware-‐Defined Network with Key Abstrac<ons in the Control Plane
Packet Forwarding
Packet Forwarding
Packet Forwarding
Separa<on of Data and Control Plane
Network Map Abstrac<on
Mobility
Programmable Basesta<on
Network OS
Open interface (OpenFlow) to Forwarding Abstrac<on: L1/L2/L3
SDN with Virtualiza<on
Packet Forwarding
Packet Forwarding
Packet Forwarding
Separa<on of Data and Control Plane
Programmable Basesta<on
Network OS Network OS Network OS
Network Virtualiza<on
How does SDN Help?
• Reduce Capex and OpEx Ø Simpler boxes based on merchant silicon
Ø Automa<on enabled by programma<c interfaces of control plane
• Support virtual infrastructure on-‐demand
Ø With customiza<on and “soc-‐appliances” for services
Ø Rapid provisioning Opportunity for revenue genera<ng services
• Enable innova<on Ø Revenue genera<ng services for infrastructure owners
Profit = Revenue – Capex – Opex
In Reality, SDN will Mean
White boxes using Merchant Silicon
Network OS
Network Control & Management Applications
Network of Closed Proprietary Boxes
“These networks are programmable and applica6on-‐aware, and far more flexible than
networks built around hardware,” Donovan said. “SDNs help us build a stronger, nimbler, more
addressable network.” John Donovan, AT&T Senior EVP
hIp://www.sdnzone.com/topics/soMware-‐defined-‐network/ar6cles/354624-‐aIs-‐doma-‐20-‐stands-‐improve-‐network-‐supply-‐cha.htm
Incumbents’ Approach to SDN?
17
Incumbents’ SDN Approach: Legacy Preserving
Forwarding
OS
Start with Closed Proprietary Ver<cally Integrated Complex Boxes Controller
OF Vendor Z
Provisioning Orchestration
Claimed Advantages? • Allows the customer to realize benefits of SDN on
the same infrastructure • Allows the vendor to build SDN on its exis<ng
products
So what is wrong?
What is Wrong with Incumbents Approach
Everything because it compromises all SDN principles and benefits
• Keeps distributed control plane embedded into
proprietary boxes • Adds another control plane: more cost & complexity • Does not help with capex, opex, and new services
except simple provisioning/orchestra<on
Forwarding
OS
Controller OF Vendor Z
Provisioning Orchestration
Perils of Marginal Cost Thinking
“But it’s [Marginal cost thinking is] a dangerous way of thinking. Almost always, such analysis shows that the marginal costs are
lower, and marginal profits are higher, than the full cost. This doctrine biases companies to leverage what they have put in
place to succeed in the past, instead of guiding them to create the capabilities they’ll need in the future.”
Clayton M. Christensen, James Allworth & Karen Dillon. “How Will You Measure Your Life?.” HarperCollins, 2012. iBooks.
This material may be protected by copyright.
Scaling of SDN Innova<on
Stanford/Berkeley SDN Ac<vi<es With Partners
2007 2011 2008 2009 2010
Ethane
Demo
Deploymen
t Plam
orm
Develop
men
t
OpenFlow Spec v0.8.9 v1.0 v1.1
Reference Switch NetFPGA Socware
Network OS NOX SNAC Beacon
Virtualiza<on FlowVisor FlowVisor (Java)
Tools Test Suite ocrace Mininet Measurement tools
GENI socware suite Expedient/Opt-‐in Manager/FOAM
Stanford University ~45 switch/APs ~25user In McKeown Group
CIS/EE Building Produc<on Network
US R&E Community GENI: 8 Universi<es + Internet2 + NLR Many other campuses
Other countries Over 68 countries (Europe, Japan, China, Korea, Brazil, etc.)
VM Migra<on (Best Demo)
Trans-‐Pacific VM Migra<on
Baby GENI Na<on Wide GENI “The OpenFlow Show” – IT World
SDN Concept (Best Demo)
SIGCOMM08 GEC3 SIGCOMM09 GEC6 GEC9 Interop 2011
+Broadcom
Where is SDN right now?
Now Early Adopters
Main Stream
ü Scalability ü High Availability ü Debuggability ü OpenFlow
optimized merchant silicon
ü More use cases
• SDN definitely represents a new paradigm of networking • Market Size: $25-30B in 2018, 30-40% of total spend in networking • SDN still requires many key capabilities to become main stream
Opportunity to Shape SDN and Future of Networking
Time
Ad
op
tion
Scaling of SDN Innova<on
Standardize OpenFlow and promote SDN 100+ Members from all parts of the industry
Bring best SDN content; facilitate high quality dialogue 3 successive sold out events; par<cipa<on of ecosys
Build strong intellectual founda<on Bring open source SDN tools/plamorms to community
SDN Academy
Bring best SDN training to companies to accelerate SDN development and adop<on
Scalability
Reliability
Debuggability
Flow Space
Network Map
Virtual Network
Logical Crossbar
Systems
Abstraction
Capabilities
OF Switch
OF
Switch
OF Switch
OF
Switch
OpenRadio
ONRC Research Agenda/Opportunities
Hierarchical SDN Control
Optimized OF Switch
Open Radio
Network Hypervisors
Troubleshooting Systems
Programming Systems
Domains of Use
Enterprise Networks
Datacenter Networks
Service Provider Networks
Cellular Networks
Home Networks
ONRC Research Agenda/Opportunities
Scalability
Reliability
Debuggability
Flow Space
Network Map
Virtual Network
Logical Crossbar
Systems
Abstraction
Capabilities
OF Switch
Hierarchical SDN Control
Optimized OF Switch
Open Radio
Edge-based Virtualization
Troubleshooting Programming
Systems
How does SDN Help?
White boxes using Merchant Silicon
Network OS
Network Control & Management Applications
Network of Closed Proprietary Boxes
ONF and OCP ONF and Chipmakers’ Advisory Board (CAB)
“The Chipmakers’ Advisory Board (CAB) serves as a forum for chipmakers to advise ONF on the best ways to promote the
hardware ecosystem and supply chain. In particular, the CAB sets expectations for new switch behavioral capabilities and open
interfaces to the chipsets.”
https://www.opennetworking.org/about/chipmakers-advisory-board
Open Computer Project: Networking
“The Networking project will focus on developing a specification and a reference box for an open, OS-agnostic top-of-rack
switch.”
http://www.opencompute.org/projects/networking/
SDN Silicon and Forwarding Devices • Silicon Ø “Design Principles for Packet Parsers” ANCS 2013 Ø “Forwarding Metamorphosis: Fast Programmable Match-‐Ac6on Processing in Hardware for SDN,”ACM SIGCOMM 2013
• OpenRadio – applying SDN ideas to radio networks Ø Sachin Kau and his group at Stanford hvp://snsg.stanford.edu/projects/openradio/
• SDN for Converged Packet/Op<cal networks Ø “Unified Control Architecture for Packet and Circuit Network Convergence,” Saurav Das, PhD Thesis, Stanford University, 2012
Ø Ciena, Infinera, Fujitsu, Brocade, ….
Open Source Network OS • Research
Ø NOX, POX, Beacon, Trema, …
• Commercial focus
Ø Open Daylight, Floodlight, OpenContrail, ….
Packet Forwarding
Packet Forwarding
Packet Forwarding
Programmable Base Sta<on
Openflow
Scale-‐out Design
Fault Tolerance
Global network view
Distributed Network OS: ONOS
Global Network View
Host
Host
Host
Titan Graph DB
Cassandra In-‐Memory DHT
Instance 1 Instance 2 Instance 3
Network Graph Eventually consistent
Distributed Registry Strongly Consistent Zookeeper
OpenFlow Controller+
OpenFlow Controller+
OpenFlow Controller+
ONOS High Level Architecture
+Floodlight Drivers
Demo: ONOS for Service Provider WAN ONS,April 2013
Distributed Network OS: Opportunity and Challenges
• How to build Network OS as a plamorm socware? Ø Open source components good for rapid prototyping but cannot get performance and op<mized feature set.
• The key building blocks – how to design and realize them Ø Low latency scale-‐out distributed data store Ø Low latency event framework: no<fica<on and processing Ø Appropriate consistency models for different types of network state Ø Programming abstrac<ons and models for different network control and management apps
• Opportunity to create an open source network OS for the community
SDN Academy • SDN is “the new paradigm” of networking
• SDN talent gap represents a huge barrier Ø SDN experQse becoming a strategic compeQQve advantage
• SDN Academy aims to close the talent gap Ø Principles, architecture, socware approach, use cases of the new paradigm
Ø Content from inventors, architects, and prac<<oners of SDN
Ø Aimed at developers, product managers, and net engineers
Less about protocols & bits; More about bringing “SDN Thinking” to companies
© 2013 SDN Academy, LLC™. All Rights Reserved.
Course Developers and Instructors
35
20+ years
SDN experience
PhD Candidates As of a few
months ago!
Brandon Heller editor of OpenFlow spec co-‐created Mininet, Netsight
David Erickson created Beacon, Virtue
Nikhil Handigol created Aster*x, co-‐created NetSight
Peyman Kazemian created HSA, NetPlumber co-‐created APTG
© 2013 SDN Academy, LLC™. All Rights Reserved.
SDN Academy Current Offerings
101 – SDN Essen<als (1 day)
102 – SDN for Developers (2 days)
103 – SDN Use-‐Cases and
Deployments (1 day)
36
• Socware Programmers • Socware Architects • Network Test & Debug
• Product Managers • Solu<on Architects • Sales and Network Engineers
Customized Courses In-‐Depth Techincal
Courses More coming Soon
Acknowledgements
Nick McKeown, Guido Appenzeller, Nick Bas<n, David Erickson, Glen Gibb, Nikhil Handigol, Brandon Heller, TY Huang, Peyman Kazemian, Masayoshi Kobayashi, Jad Naous, Johan van Reijendam, Srini Seetharaman, Rob Sherwood, Dan Talayco, Paul Weissman, Tatsuya Yabe, KK Yap, Yiannis Yiakoumis and many more.
With ScoU Shenker and team at Berkeley and MarQn Casado at Nicira
Team at Stanford
Team at ON.Lab
Johan, Masa, Ali Bob, Jo, Bill, Sumanth Pankaj, Rachel, Jono, Marc Pavlin, Suibin, Ping Ping, Nikhil KK, Sean, Karthik, Maveo, Brian
