Successfully reported this slideshow.

API Management for Software Defined Network (SDN)

5,810 views

Published on

  • Be the first to comment

API Management for Software Defined Network (SDN)

  1. 1. SDN and APIsNetworking Innovation Through SoftwareSam Ramji @sramjiBrian Pagano @brianpagano
  2. 2. groups.google.com/group/api-craft
  3. 3. youtube.com/apigee
  4. 4. slideshare.net/apigee
  5. 5. SOFTWARE-DEFINEDNETWORKING:Defined
  6. 6. Software-Defined Networking (SDN)is a shift in network-based computingbased on breaking existing physicalboundaries on switches, routers, andcontrollers through well-defined APIs.
  7. 7. This makes it possible to dynamicallydefine all aspects of a network throughsoftware.
  8. 8. A BRIEF OVERVIEWOF SDN
  9. 9. Originally networking was a difficult manualprocess.
  10. 10. In a pre-OpenFlow network, all routing andcontrol work was done by a single proprietaryproduct.All features were shipped by the vendor.
  11. 11. packets Router/Switch packets Feature Feature Feature Policy-based routing Examples Operating System JunOS, Cisco IOS Packet Forwarding Hardware Broadcom, Marvell
  12. 12. In an OpenFlow network, routing and controlwork can be done by software runninganywhere in the datacenter. SDN controllersdrive these changes into the switching layers.
  13. 13. SDN Controller OpenFlow APIOpenFlow Switch OpenFlow Switch OpenFlow Switch
  14. 14. It can be helpful to think of the SDN as beingmade up of elements, controllers, and apps.
  15. 15. App A App B App C App D SDN ControllerOpenFlow Switch OpenFlow Switch OpenFlow Switch
  16. 16. App A apps App B App C App D controllers SDN ControllerOpenFlow Switch elements OpenFlow Switch OpenFlow Switch
  17. 17. The element is where the packet processinghappens and must run at line rate.
  18. 18. packets OpenFlow Switch packets OpenFlow APIFlow Table Flow Table Flow Table
  19. 19. Controllers have built-in features and talk toswitches via the OpenFlow API. They alsohave APIs to enable new features that runoutside the controller.
  20. 20. SDN Controller Northbound APIFeature Feature Feature Operating System
  21. 21. These are called “Northbound APIs” andenable programmability.
  22. 22. SDN Controller Northbound API Feature Feature Feature Operating System OpenFlow APIOpenFlow Switch OpenFlow Switch OpenFlow Switch
  23. 23. Just like APIs in the programmable web, themore apps that depend on them, the stickierthe SDN Controller is.
  24. 24. 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
  25. 25. Expanding new features running elsewhere inthe datacenter increases the agility of thesoftware-defined network.
  26. 26. 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
  27. 27. End of Quarter Intrusion EnergyRoute to Sandbox SLA Detection Management Datacenter Operating System Northbound API SDN Controller A SDN Controller B OpenFlow API packets OpenFlow Switches packets
  28. 28. SDN controllers are made by multiple vendors,each with their own northbound APIs. Newfeatures have to work with every controller.
  29. 29. 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
  30. 30. A few examples of northbound APIs
  31. 31. http://www.openflowhub.org/display/floodlightcontroller/ Floodlight+Documentationhttp://docs.openstack.org/api/openstack-network/2.0/content/ http://www.vyatta.com/downloads/documentation/VC6.3/ Vyatta_RemoteAccessAPI2.0_R6.3_v01.pdf
  32. 32. APIs IN THESDN REVOLUTION
  33. 33. The software that defines the network doesso via APIs.While virtualization is a systems model, APIsare an abstract model.An API is a programming model.
  34. 34. One thing that is significantly different fromAPIs in the programmable web is that in SDNeach API has multiple instances.This is because each controller from a givenvendor is implementing the same API butthere are many copies of that controllerrunning in the same environment.
  35. 35. One thing that could move SDN forward is tohave a single API that interoperates with eachof the various SDN controller APIs.
  36. 36. 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
  37. 37. What if we had a single view of thesoftware-defined network?
  38. 38. Policy-based Intrusion NetworkApplication QoS Routing Detection Management System Common Northbound API SDN Controller A SDN Controller B OpenFlow Switch OpenFlow Switch OpenFlow Switch OpenFlow Switch OpenFlow Switch
  39. 39. This is an enormous opportunity for theDevOps movement.You get control over the network on top ofyour existing control over the servers.And you will speed the disintegration of NMS.
  40. 40. How far could we take the system towardsperfecting user experience of our services?
  41. 41. Policy-based Intrusion Network ManagementApplication QoS Routing Detection System Common Northbound API SDN Controller A SDN Controller B OpenFlow Switch OpenFlow Switch OpenFlow Switch OpenFlow Switch OpenFlow Switch
  42. 42. THANK YOUSubscribe to API webcasts at:youtube.com/apigee
  43. 43. THANK YOUQuestions and ideas to:groups.google.com/group/api-craft
  44. 44. THANK YOUQuestions and ideas to:@sramji@brianpagano

×