1 / 11

Software Defined Networking

Software Defined Networking. Paul Evans. Storage Architect at Daystrom. March 2014. What SDN is:. OR. A Software-to-Infrastructure interface that allows applications to drive network actions.

pakuna
Download Presentation

Software Defined Networking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Defined Networking Paul Evans Storage Architect at Daystrom March 2014

  2. What SDN is: OR... A Software-to-Infrastructure interface that allows applications to drive network actions • Using an independent 'control plane'to enable dynamic configuration of a network to respond (quickly) to application, compute and/or traffic needs

  3. It is not 'Software Implemented Networking', which uses stand-alone software running on independent networking or compute platforms, or within a virtualization platform (like VMware or KVM), to directly switch, route and otherwise control packet flows What SDN is NOT

  4. SDN has been ‘enabled’ by standards based flow-control mechanisms, notably OpenFlow, which itself came from various research projects and ‘bright ideas’ (chief among them SANE and Ethane). NOX from Nicira was/is an early ‘controller’ of OpenFlow systems. Where did SDN come from?

  5. What Problems does SDN solve? • The 'compute' elements in both Enterprise and Cloud environments have become abstracted to the point where they can be easily coordinated and managed using rules and policies under the control of a compute orchestration layer - vSphere being a notable example of a 'control plane' optimizing the virtual workloads across potentially dynamic physical infrastructure. And, while networks have been 'virtualized' since the 90's (VLANs and MPLS), the automation of such virtualization remains relatively backwards in comparison. Storage is in much the same boat. 

  6. What Problems does SDN Not solve? • SDN does not appear to resolve much of the complexity and alphabet-soup that the NetEng crowed calls 'standards', nor does it resolve some of the underlying physical network challenges like trunks/LAGs or distributed routing protocols. 

  7. What is needed to deploy SDN? • *Control Plane for making reliable and accurate changes to the Physical Network rules • *Applications and Network Monitor systems capable of expressing their needs to the Control Plane for evaluation and possible implementation *Physical Layer that is capable of being programmed from end-to-end

  8. What are some reasons why SDN may be successful? There are STANDARDS!•…but that has not necessarily been a panacea for the networking world•There is a compelling need: networking continue to increase in size, and with out competent automation there just won't be enough engineers to manage them. As things stand now, it can take weeks or months to get networking changes implemented - and sometimes it requires a forklift upgrade to accomplish it. 

  9. What are the major roadblocks to SDN adoption?... Complexity•The old adage: "to err is human, but to really foul things up requires a computer"

  10. Who makes SDN Stuff? Any firm supporting OpenFlow•Any firm making Controllers (like: Big Switch)•Any firm that makes network management software that can analyze traffic flows and calculate improvements that can be implemented by SDN systems

  11. Thanks!

More Related