Transcription
SDxCentral SDNController ReportBrocade 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.
Legal DisclosureNOTE: The appropriate confidentiality information should always be contained in the footer. Thistemplate’s footer is set up for internal audiences. If this presentation will be used for externalaudiences, please go to the Insert tab, click Header & Footer and replace the footer text, in bothSlides tab and Notes and Handouts tab, with the following (click Apply to All when done) : 2015 BROCADE COMMUNICATIONS SYSTEMS, INC. COMPANY PROPRIETARY INFORMATIONPLEASE SEE RISK FACTORS ON FORM 10-Q AND FORM 10-K FILEDWITH THE SECThis presentation, with prepared remarks, includes forward-looking statements regarding Brocade’s financial results, goals,plans, assumptions, strategy and business outlook, revenue, tax rate, cash, stock buybacks, OEM inventory, prospects, as wellas U.S. Federal spending and order flow, and IT spending, which are only predictions and involve risks and uncertainties suchthat actual results may vary significantly. These and other risks are set forth in more detail in our Form 10-K for the fiscal yearended October 26, 2013 and our Form 10-Q for the fiscal quarter ended August 2, 2014. These forward-looking statementsreflect beliefs, assumptions, outlook, estimates, and predictions as of today, and Brocade expressly assumes no obligation toupdate any such forward-looking statements whether as the result of new developments or otherwise.In addition, this presentation includes various third-party estimates regarding market share and other measures, which do notnecessarily reflect the views of Brocade. Further, Brocade does not guarantee the accuracy or reliability of any such informationor forecast.Certain financial information is presented on a non-GAAP basis. Management believes that non-GAAP financial measures usedin this presentation allow stakeholders to gain a better understanding of Brocade’s comparative operating performance bothfrom period to period, and to its competitors’ operating results. Management also believes these non-GAAP financial measureshelp indicate Brocade’s baseline performance before gains, losses or charges that are considered by management to beoutside of ongoing operating results. Accordingly, management uses these non-GAAP financial measures for planning andforecasting of future periods and in making decisions regarding operations performance and the allocation of resources. Themost directly comparable GAAP information and a reconciliation between the non-GAAP and GAAP figures are provided in theaccompanying press release, which has been furnished to the SEC on Form 8-K and posted on Brocade’s website, and isincluded in the appendix in this presentation. 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.2
Market Landscape for PlatformsGen1 Open Source Most are exclusivelyOpenFlow Academic experiments — nocurrent market traction“House” ControllersGen2 Open Source Strong market (Ops) interest/news coverage driven bycorporate sales/market strength Stated open source preferencein many sectors Relative product maturity Strong focus onprogrammability, interoperability Most focus on NW orchestration,not programmability Strong interest from developers& dev-heavy shops Some tied explicitly to vendor’sown platforms Some assembly currentlyrequired 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.3
What Is OpenDaylight?OpenDaylight is an Open Source Software project under the Linux Foundation withthe goal of furthering the adoption and innovation of Software Defined Networking(SDN) through the creation of a common industry supported platform.CodeAcceptanceCommunityTo create a robust,extensible, open source codebase that covers the majorcommon componentsrequired to build an SDNsolutionTo get broad industryacceptance amongst vendorsand users:To have a thriving andgrowing technical communitycontributing to the code base,using the code in commercialproducts, and adding valueabove, below and around. Using it directly or throughvendor products Vendors using OpenDaylightin commercial products 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.4
Defining “Open” in Open SourceAs about ProjectsAsk about Products Who can contribute? Does it integrate with other solutionsfrom other vendors? Who does contribute? How are decisions made? Whocan comment? Who can vote? What license does it use? Does it have an API? Does it follow open standards? Is it based on open sourcecomponents? Does it upstream to opensource projects?“Simply stated, OpenDaylight is as open as open gets.” pen-sdn/a/d-id/1234771 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.5
OpenDaylight Releases Hydrogen (February 2014)‒ 13 projects, 1.3m lines of code Helium (October 2014)‒‒‒‒Clustering, AAADLUX UIPolicy-related projectsKaraf containers to customize packages Lithium (June 2015)‒‒‒‒Improved OpenStack Neutron integrationInternet of ThingsService Function Chaining/NFVImproved security, release processes 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.6
Beryllium Release Planning Focuses on‒ S3P (Security, Stability, Scalability and Performance)‒ Migration‒ HA/clustering Balances maturity (the above) with feature velocity‒ Some projects will be mature‒ Some of the Karaf features in mature projects will be stable‒ Stable features meet S3P, Migration, and HA/clustering requirements‒ Stable and “normal” distribution; stable only has stable features Emphasis on documentation, user stories, other support materialsRelease Plan: https://wiki.opendaylight.org/view/Simultaneous Release:Beryllium Release Plan 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.7
Analysts See ingformidablewithgoodpoten alformainstreamrelevancy.”– Andrew Lerner, theLinuxofnetworkstacks:thefounda enera ensourceapproachtosoAware- BusinessEdge 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.8
OpenDaylight Users and Advisory BoardDeployed Users Telstra Tencent AT&T CERN Large Hadron Collider 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.9
OpenDaylight as the Common penDaylight 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.10
wrongOne way to build a release based on OpenDaylight Clone the OpenDaylight code (it’s public, after all!) Modify the code to customize / brand‒ Add new code into the existing projects for your proprietary logic Run the build Test, Ship and Sell it! Great, that was easy This is the first thing nearly everyone does‒ In practice, this results in a permanent fork of the codebase and eventuallydropping out of the community 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.11
Treat OpenDaylight as a Third Party Don’t Download the OpenDaylight Source Code!‒ Treat OpenDaylight as a collection of read-only third-party artifacts‒ Reference ODL artifacts, don’t build them‒ Use Maven to access, maintain and manage your third-partydependencies for you For example:‒ We don’t recompile the basic java.util.ArrayList Java class; wereference/use it‒ We certainly don’t modify the java.util.ArrayList source code locallyand build it 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.12
Leverage OpenDaylight ModularityIsolate Proprietary Code Keep your proprietary code isolated toyour own repositories, bundles, andKaraf features Leverage OSGi/Karaf/Maven to combineyour code with OpenDaylight Leverage YANG/MD-SAL/Config systemmodularity to load proprietaryimplementations into the bric OSGi is generally friendly with the EPLlicense**Note: we are not lawyers. Be sure to discuss any legal / licensing issues with your legal team 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.13
The Result A product which references OpenDaylight artifacts Proprietary code is isolated, and can be updated without affectingOpenDaylight code‒ Also potentially avoid legal/licensing pain (ASK YOUR LAWYERS!) Changing versions of OpenDaylight code is just an update to a version ina pom file‒ and some testing Allows for a stable OpenDaylight controller on which to build proprietaryimplementations 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.14
Brocade SDN Controller—How, Not WhatBuild the Foundation andFrame UpstreamCollaborative Innovationwith UsersGetting Started with SDN Continuous build from ODL Joint and custom development Contribute enhancements App design review, certification,and/or integration Stability and support for the wholecontroller environment No forking or proprietaryextensions Channel user requests intoODL workstream Architectural planning Developer tools and repo access– Support model assumes mixedvendor environment Developer community resources– Full documentation– GitHub and Brocadecommunity Specialized education foroperations and developers 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.15
Thank you (Red) 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.
Where We Have Been Where Are We Going?VPNMobileInternetSingle Service – Single Control PlaneMultiple Services – Multiple Control Planesca. 19601980’s – 2010’ishUbiquitousMultimedia Communications and ServicesPSTNMultimedia Communications and ServicesFixed Audio CommunicationsThe Control Plane EvolutionSoftware DefinedNetworkMultiple Services – Single Control PlaneToday – Tomorrow 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.17
Modern, Inclusive SDNNorthbound APILogicallyCentralizedSDN ControllerVendor AVendor BVendor ontrolVendor AVendor BIndustry elingLanguagecontrolVendor C Device-by-device operation Network-wide operation Proprietary, vendor-specific vertical stacksfor control, management and orchestration Open control, management andorchestration using open control protocols/modeling langs Limited innovation in individual silos Independent innovation at each layerof the stack 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.18
Why Open Source? Avoid vendor lock-in Have a seat at the table Faster Innovation Interop & Integration 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.19
- erNetwork ApplicationsOrchestrations &ServicesAAA AuthN FilterOpenDaylight APIs REST/RESTCONF/NETCONFOpenFlow Stats ManagerBase NetworkFunctionsService Function ChainingOVSDB NeutronNetwork Abstractions(Policy/Intent)OpenFlow Switch ManagerReservationDevice Discovery, Identification &Driver ManagementALTO Protocol ManagerNetwork ServicesOpenFlow Forwarding Rules MgrVirtual Private NetworkL2 SwitchVirtual Tenant Network Mgr.LISP ServiceNetwork Intent CompositionHost TrackerUnified Secure Channel MgrDOCSIS AbstractionGroup Based Policy ServiceTopology ProcessingLink Aggregation Ctl ProtocolSNMP4SDNOpenFlowOVSDBOpenFlow tication, Authorization &AccountingNeutron NorthboundController PlatformServices/ApplicationsPersistenceSDN Integration AggregatorTime Series Data RepositoryService Abstraction Layer/CoreDataStore(Config&Opera onal)Platform ServicesSXPSNMPUSCMessaging (Notifications / RPCs)SNBIHTTPOpen vSwitches 2015 BROCADE COMMUNICATIONS SYSTEMS, INC.CoAPLACPAdditional Virtual &Physical DevicesPCMM/COPSSouthboundInterfaces &Protocol PluginsData Plane Elements(Virtual/PhysicalSwitches/Devices)20
Brocade SDN Controller—How, Not What Build the Foundation and Frame Upstream Continuous build from ODL Contribute enhancements No forking or proprietary extensions Channel user requests into ODL workstream Getting Started with SDN Architectural planning Stability and support for the whole
