6. Software-Defined Networking (SDN)
is a shift in network-based computing
based on breaking existing physical
boundaries on switches, routers, and
controllers through well-defined APIs.
7. This makes it possible to dynamically
define all aspects of a network through
software.
13. In an OpenFlow network, routing and control
work can be done by software running
anywhere in the datacenter. SDN controllers
drive these changes into the switching layers.
14. SDN Controller
OpenFlow API
OpenFlow Switch OpenFlow Switch OpenFlow Switch
15. It can be helpful to think of the SDN as being
made up of elements, controllers, and apps.
16. App A App B App C App D
SDN Controller
OpenFlow Switch OpenFlow Switch OpenFlow Switch
17. App A
apps
App B App C App D
controllers
SDN Controller
OpenFlow Switch
elements
OpenFlow Switch OpenFlow Switch
18. The element is where the packet processing
happens and must run at line rate.
20. Controllers have built-in features and talk to
switches via the OpenFlow API. They also
have APIs to enable new features that run
outside the controller.
21. SDN Controller
Northbound API
Feature Feature Feature
Operating System
23. SDN Controller
Northbound API
Feature Feature Feature
Operating System
OpenFlow API
OpenFlow Switch OpenFlow Switch OpenFlow Switch
24. Just like APIs in the programmable web, the
more apps that depend on them, the stickier
the SDN Controller is.
25. App A App B App C App D
Datacenter Operating System
SDN Controller A SDN Controller B
OpenFlow API
packets OpenFlow Switch packets
OpenFlow API
Flow Table Flow Table Flow Table
26. Expanding new features running elsewhere in
the datacenter increases the agility of the
software-defined network.
27. App A App B App C App D
Datacenter Operating System
Northbound API
SDN Controller A SDN Controller B
OpenFlow API
packets OpenFlow Switches packets
28. End of Quarter Intrusion Energy
Route to Sandbox
SLA Detection Management
Datacenter Operating System
Northbound API
SDN Controller A SDN Controller B
OpenFlow API
packets OpenFlow Switches packets
29. SDN controllers are made by multiple vendors,
each with their own northbound APIs. New
features have to work with every controller.
30. App A App B App C App D
Datacenter Operating System
Northbound API A Northbound API B
SDN Controller A SDN Controller B
OpenFlow API
packets OpenFlow Switch packets
34. The software that defines the network does
so via APIs.
While virtualization is a systems model, APIs
are an abstract model.
An API is a programming model.
35. One thing that is significantly different from
APIs in the programmable web is that in SDN
each API has multiple instances.
This is because each controller from a given
vendor is implementing the same API but
there are many copies of that controller
running in the same environment.
36. One thing that could move SDN forward is to
have a single API that interoperates with each
of the various SDN controller APIs.
37. App A App B App C App D
Common Northbound API
Datacenter Operating System
Northbound API A Northbound API B
SDN Controller A SDN Controller B
OpenFlow API
packets OpenFlow Switch packets
38. What if we had a single view of the
software-defined network?
39. Policy-based Intrusion Network
Application QoS
Routing Detection Management System
Common
Northbound API
SDN Controller A SDN Controller B
OpenFlow Switch OpenFlow Switch OpenFlow Switch
OpenFlow Switch OpenFlow Switch
40. This is an enormous opportunity for the
DevOps movement.
You get control over the network on top of
your existing control over the servers.
And you will speed the disintegration of NMS.
41. How far could we take the system towards
perfecting user experience of our services?
42. Policy-based Intrusion Network Management
Application QoS
Routing Detection System
Common
Northbound API
SDN Controller A SDN Controller B
OpenFlow Switch OpenFlow Switch OpenFlow Switch
OpenFlow Switch OpenFlow Switch