Anúncio

Delivering Network Innovation with SDN - Tom Nadeau

19 de Jul de 2016
Anúncio

Mais conteúdo relacionado

Apresentações para você(20)

Anúncio

Similar a Delivering Network Innovation with SDN - Tom Nadeau (20)

Mais de scoopnewsgroup(20)

Anúncio

Delivering Network Innovation with SDN - Tom Nadeau

  1. © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION Delivering Network Innovation with SDN
  2. Networks Have Not Adapted to Demands Over the last 20 years… © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 2 • Massively increased scale (# of endpoints, switches, bytes, flows, etc.) • Static endpoints (weeks–months) to dynamic endpoints (hours–days) • Mostly north-south traffic to mostly east-west traffic Radically Shifting Network Demands • Link speeds have gone up, but… • Still largely manage networks device- by-device via the CLI • If you’re lucky, orchestration at the granularity of a few devices Networks Haven’t Changed Much
  3. Things Need to Change © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 3HTTP://WWW.THENEWIP.NET/DOCUMENT.ASP?DOC_ID=711461 This is the rise of open source networking Device-by-device Network-wide Open Standards Open Standards + Open Source Proprietary Software Open Source Networking, Storage, Compute Converged IT Hardware Software
  4. Solution: Disaggregation and Open Software © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 4 Logically Centralized SDN Controller Northbound API Industry Standard Control/Management Protocols • Network-wide operation • Open control, management and orchestration using open control protocols/modeling langs • Independent innovation at each layer of the stack • Device-by-device operation • Proprietary, vendor-specific vertical stacks for control, management and orchestration • Limited innovation in individual silos control mgmt Vendor A Vendor B control mgmt Vendor C control mgmt Vendor A control mgmt Vendor B control mgmt Vendor C control mgmtStandard Modeling Language
  5. What a Controller Does © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 5 CONTROLLER PLATFORM Applications and Services Allows software developers to innovate applications that get information from the network and control the network Network—Switches and Routers Allows network equipment suppliers to create plugins and information models for their equipment that improve manageability and lowers costs Service Abstraction LayerCommon Services Standardized REST API Standard Interfaces and Plugins BGP-LS PCE-P Customer Developed Applications Vendor Developed Applications NETCONF YANG OVSDBSNMP OpenFlow 1.0 / 1.3 Neutron Plugin Vendor-Specific Plugins
  6. What a Controller Does © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 6 CONTROLLER PLATFORM Applications and Services Allows software developers to innovate applications that get information from the network and control the network Network—Switches and Routers Allows network equipment suppliers to create plugins and information models for their equipment that improve manageability and lowers costs Service Abstraction LayerCommon Services Standardized REST API Standard Interfaces and Plugins BGP-LS PCE-P Customer Developed Applications Vendor Developed Applications NETCONF YANG OVSDBSNMP OpenFlow 1.0 / 1.3 Neutron Plugin Vendor-Specific Plugins
  7. Why Open Source? • Avoid vendor lock-in © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 7HTTPS://18F.GSA.GOV/2014/11/26/HOW-TO-USE-MORE-OPEN-SOURCE/ “It's important that every Federal CIO, CTO, Architect, and Program Manager seeking to build or procure new IT projects understand that open source exists, that it can be of high quality and highly reusable, and how to use it securely.” • Have a seat at the table • Faster innovation • Easier integration
  8. Open Source SDN Projects of Note Programmable s/w in the Linux kernel [data plane] © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 8HTTP://WWW.JEDELMAN.COM/HOME/OPEN-SOURCE-NETWORKING Open vSwitch OpenDaylight OpenStack Industry-wide SDN controller [control/mgmt plane] • Many, many others: Open Network Linux, ONOS, CloudRouter, Quagga, OVN, ONIE, Open Compute, Prescriptive Topology Manager, SocketPlane, Weave, Akanda, MidoNet, OpenContrail • IT-wide orch. (Neutron for networks) [orchestration]
  9. Open Source vs. Open Standards © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 9 • Define interfaces well – In human-readable documents • Define behavior with some ambiguity • Usually move slowly • Leave interoperability testing to others, e.g., users, integrators • Sometimes provide open source implementations Open Standards • Define interfaces well – In code • Define behavior in code so it can be tested and understood • Move and adapt quickly • Can do interoperability testing as part of development • Often implement open standards Open Source Projects
  10. Is Open Source Secure? • In general, open source is considered to be more secure than closed source software – “Given enough eyeballs, all bugs are shallow” –Linus • Very strong security response process – Fixed critical vulnerabilities and shipped a new release in <4 days • Device/user interfaces can be secured – OF over SSL, NETCONF over SSH, RESTCONF over HTTPS w/auth • Starting with Lithium, releases will be cryptographically signed © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 10
  11. Is Open Source Secure? • In general, open source is considered to be more secure than closed source software – “Given enough eyeballs, all bugs are shallow” (Linus) • Very strong security response process – Fixed critical vulnerabilities and shipped a new release in <4 days • Device/user interfaces can be secured – OF over SSL, NETCONF over SSH, RESTCONF over HTTPS w/auth • Starting with Lithium, releases will be cryptographically signed © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 11
  12. Is Open Source Secure? • In general, open source is considered to be more secure than closed source software – “Given enough eyeballs, all bugs are shallow” (Linus) • Very strong security response process – Fixed critical vulnerabilities and shipped a new release in <4 days • Device/user interfaces can be secured – OF over SSL, NETCONF over SSH, RESTCONF over HTTPS w/auth • Starting with Lithium, releases will be cryptographically signed © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 12
  13. Defining “Open” in Open Source © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 13 HTTP://WWW.OPENDAYLIGHT.ORG/BLOGS/2014/03/DEGREES-OPEN HTTP://WWW.NETWORKCOMPUTING.COM/50-SHADES-OF-OPEN-SDN/A/D-ID/1234771 • Who can contribute? • Who does contribute? • How are decisions made? Who can comment? Who can vote? • What license does it use? As about Projects • Does it integrate with other solutions from other vendors? • Does it have an API? • Does it follow open standards? • Is it based on open source components? • Does it upstream to open source projects? Ask about Products “Simply stated, OpenDaylight is as open as open gets.”
  14. What Is OpenDaylight? © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 14 OpenDaylight is an Open Source Software project under the Linux Foundation with the goal of furthering the adoption and innovation of Software Defined Networking (SDN) through the creation of a common industry supported platform. To create a robust, extensible, open source code base that covers the major common components required to build an SDN solution Code To get broad industry acceptance amongst vendors and users: • Using it directly or through vendor products • Vendors using OpenDaylight in commercial products Acceptance To have a thriving and growing technical community contributing to the code base, using the code in commercial products, and adding value above, below and around. Community
  15. Who Is OpenDaylight? © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 16HTTPS://WWW.OPENHUB.NET/P/OPENDAYLIGHT • ~300 code commits/week over last 12 months from 324 devs – 150 developers in last 30 days – 15,000+ commits in 12 months SILVERPLATINUM GOLD
  16. OpenDaylight as the Common Platform Companies that have announced products based on OpenDaylight © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 17
  17. Analysts See Momentum © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 18 “ OpenDaylight is quickly evolving into something formidable with good potential for mainstream relevancy.” “ OpenDaylight may be the third center of gravity.” – Andrew Lerner, Gartner “ OpenDaylight is making steady progress cultivating a growing community of developers and users interested in adopting an open, common SDN controller platform.” – Brad Casemore, IDC Research Director for Datacenter Networks “ An open source approach to software- defined networking (SDN) moved several steps closer this week to becoming a de facto standard.” – Mike Vizard, IT Business Edge
  18. SDN Use Cases © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 19 Custom Analytics and Compliance Big Data Security QoS and Traffic Management Network Virtualization Service Configuration and Policy Research and New Protocols Fault and Disaster Recovery WAN Optimization
  19. Security © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 20 • Historically, policy is mostly – Rigidly enforced by the physical topology, e.g., firewall at the gateway – Configured “dynamically” via box-by-box Access Control Lists (ACLs) • New policy efforts are changing this – Network Function Virtualization (NFV) and Service Function Chaining (SFC) – Automatically generated ACLs based on network-wide policy • OpenDaylight is a proving ground for at least 3 policy-oriented projects – Service Function Chaining, Group-Based Policy, and Network Intent Composition Network-wide policy monitoring and enforcement
  20. OpenDaylight OpenStack Neutron Network Virtualization OpenDaylight integration with OpenStack Neutron © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 21 • OpenDaylight has a common Neutron “northbound” provider – 3 implementations in Helium – 4+ planned in Lithium • Supports network virt. and – Distributed L3 forwarding – Security Groups – {LB,VPN}aaS OpenContrail Provider VTN Provider Neutron Service OVSDB Provider Neutron ML2 MechanismDriver OpenDaylight APIs (REST)
  21. SDN Is Critical to IT-wide Innovation © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 22 LevelofProgrammability Scope of Domain Network Element Network IT Infrastructure PythonRESTCLIScripting Classic Network Management Tools Neutron DevOps Tools
  22. SDN Is Here; It’s Time to Use It © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 23 • SDN is the key to modernizing today’s networks – Enables flexibility and choice – Unlocks self-service innovation • Open source is the force multiplier that makes SDN possible – Community leverage accomplishes more than any single supplier – Open philosophy shifts control from the suppliers to the consumer • Commercial versions of open source controllers are production-ready with support – e.g., the Brocade Vyatta Controller based on unmodified OpenDaylight – Brocade upstreams all changes to to OpenDayilght
  23. • Figure out what infrastructure you have that is SDN-ready – Some key protocols: NETCONF, OpenFlow, OVSDB – Make current/future acquisitions call for this • Ask your suppliers hard questions about software, agility, and openness—it’s not just open standards anymore • Download the code and start testing/deploying it – http://www.opendaylight.org/software/downloads – http://www.brocade.com/products/all/software-defined-networking/ brocade- vyatta-controller/index.page What to Do Next © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION 24
  24. © 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATION Thank you

Notas do Editor

  1. [Premise: Open source SDN will deliver the innovation networks need.] [Scott’s Notes on topics to cover: Software-Defined Networking (SDN) is paving the way for self-service innovation, enabling higher levels of access and control over networks and their resources. In this session, you’ll hear about how SDN architecture decouples the control and data elements of the network to provide an open, flexible, and centralized management model. Software Defined Networking is starting to deliver on the promises of a highly automated and programmable network that is open and standards based. In this session, hear about how SDN architecture decouples the control and data elements of the network to provide an open, flexible, and centralized management model, learn about the SDN landscape, open projects and standards that are impacting the industry. Hear about technologies available today that will move your physical networking infrastructure towards an SDN enabled environment. * Industry overview – who is investing in SDN and how they are doing it. Commercial and Open Project overview – open source projects like OVS and ODL. * SDN Controllers – OpenDayLight overview – physical and NFV capabilities * Expansion of Software Defined beyond the network – SDN to SDX –the expansion towards SDX – software defined everything.]
  2. We’ve been hearing all day that the world of IT is changing. The scale is increasing across nearly all dimensions and the needs are increasingly dynamic. By contrast the network hasn’t changed much
  3. Device-by-device => Network-wide Open Standards => Open Standards + Open Source Proprietary Software => Open Source Networking, Storage, Compute => Converged IT Hardware => Software Device-by-device  Network-wide Open Standards  Open Standards + Open Source Proprietary Software  Open Source Networking, Storage, Compute  Converged IT Hardware  Software To a large extent, this is the rise of open source networking
  4. So, what does this look like? Well, right now, as we’ve said, networks are very device centric with operation taking place on a device-by-device basis. Further, each device is not just the Innovation is limited both by Architecture because most changes need to happen across silos Economics because there’s limited incentive to fix things if you’re locked into a silo Also talk about cost: capex/opex
  5. Avoid vendor lock-in: multiple suppliers of the same code base Have a seat at the table: development is open to user input Faster innovation: more and more diverse contributors Easier integration: combine multiple solutions if they share an open source base
  6. Mention why these three are called out: exemplars at different layers
  7. Something like the difference between an RFP and the proposals that come back.
  8. Explain the difference between membership levels from the point of view of customers.
  9. Key point here is that multiple people are actually selling it. Mention differences between ways of productizing Using some pieces of OpenDaylight in a product Basing your product on OpenDaylight Opens up cool ways for vendors to partner more easily to provide solutions
  10. Read one outloud.
  11. [Needs work.]
  12. [Needs to have the colors in the diagram made less ugly]
  13. Use this slide to talk about SDN => SDX This will enhance the whole data center, change the title to reflect that.
  14. [Maybe drop this slide since it’s very close to marketing.]
Anúncio