The OpenDaylight Project October 2014 @OpenDaylightSDN #OpenSDN

OpenDaylight SDN Platform Linux Foundation Open Source Collaboration Software Defined Networking Network Function Virtualization Daylight is an open source project under the Linux Foundation with the mutual goal of furthering the adoption and innovation of Software Defined Networking (SDN) through the creation of a common industry supported framework. OpenDaylight is a community-led, open, industry-supported framework, for accelerating adoption, fostering new innovation, reducing risk and creating a more transparent approach to Software-Defined Networking. As a collaborative project under The Linux Foundation, OpenDaylight is structured using open source development best practices, and is comprised of the leading organizations in the technology industry. Innovation

SDN, NFV and OpenDaylight New Revenue Open, Programmable APIs Service Agility Orchestration, Automation and MANO SDN NFV Software Defined Networking (SDN) separates the control plane from the data plane within the network, allowing the intelligence and state of the network to be managed centrally while abstracting the complexity of the underlying physical network. Great strides have been made within the industry toward this goal with standardized protocols such as OpenFlow. However, greater collaboration leveraging open source development best practices will significantly accelerate real, deployable solutions for the industry at large. Similarly, by evolving network services from an appliance model to one that leverages virtual compute, storage, and networking, Network Functions Virtualization (NFV) promises to drastically improve both the agility of when and where to run network functions as well as the cost structure of doing so. SDN and NFV are a new way of deploying network infrastructure. A software-defined network adapts to the requirements of applications deployed on the network. Current generation networks and architectures are statically configured and vertically integrated. New generation applications such as Hadoop, video delivery, and virtualized network functions require networks to be agile and to flexibly adapt to application requirements. Virtualization and Abstraction Layer Lower Cost

Why SDN? Software Defined Networking (SDN) resets business opportunities New architecture with separate Control and Data planes Open Programmable Networks and APIs New business models and revenue opportunities Efficiency in both capital and operational expenses Security, load balancing, etc. services Enterprise apps APIs Software-Defined Network (SDN) Platform Open protocols with enablement for proprietary extensions Focus Area for OpenDaylight Physical Network Physical Network 4 4

Why Open Source? Flexibility Innovation Choice Control Faster, lower cost and higher quality development through sharing of resources via collaboration Community decisions about new features and roadmaps A common environment for uses and App developers Ability to focus resources on differentiating development Open Source leverages contributions among collaborators. Open Source is good for non-differentiating infrastructure Degrees of Openness (Neela Jacques blog post) 0-2 Closed: This was the model 20 years ago, the idea of keeping your secret sauce secret. 2-4 Mostly Closed: At this point few companies remain in the primary category. Customers just won’t stand for it. Many, though, are only marginally more open, adding limited APIs. These are platforms that you find yourself committed to for a long, long time. 4-6 Open Plus: Proprietary software, built on top open source and/or open standards. MapR and Cloudera are examples of companies that offer solutions built on top of an open platform (Hadoop) but whose solutions include elements that are quite proprietary. In many cases end users here can experience the best of both worlds – the performance from a highly tuned, controlled piece of software, but the ability to migrate to another member of the ecosystem if technical requirements change. 6-8 Mostly Open: Open source commercial distributions take an open source code base and add testing, integration, services and support. You can migrate from one distribution to another, but few people do. Red Hat Enterprise Linux (RHEL) is a great example of this. The vast majority of what you’re getting is the Linux kernel. Most changes are upstreamed back into Linux and most changes/innovations to Linux will flow into RHEL. We have our first commercial distribution of OpenDaylight thanks to Inocybe Technologies. I believe we will see more. 8-10 Fully Open: Here we’re primarily talking about consuming open source in its most raw form. You get the code, you can change the code, you can deploy it, build a product or service around it, etc. etc. etc. The challenge of course is that to consume open source in its most raw form, you better have mad skills. Google does. So does Twitter. Most end users don’t.

Community and Governance Developer Community Open to all Transparency Meritocracy Membership open to all Business leadership: Board of Directors Governance, marketing, operations Technical leadership: Technical Steering Committee (TSC) Technical direction, project selection, technical decisions Meritocracy and transparency Project life-cycle management More information and to join: www.opendaylight.org info@opendaylight.org Keep informed and join the conversation @OpenDaylightSDN #OpenDaylight #ODSummit OpenDaylight is open to anyone. Anyone can develop and contribute code, get elected to the Technical Steering Committee, get voted onto the Board, or help steer the project forward in any number of ways. Developers who are elected to the Technical Steering Committee or who participate as project leaders will provide leadership regarding the technical direction of OpenDaylight. A Board of Directors will manage business leadership for OpenDaylight including governance, marketing and operational decisions. Board of Directors Technical Steering Committee

1.87M+ lines of code, 28 Projects, 256 Contributors Released October, 2014 1.87M+ lines of code, 28 Projects, 256 Contributors

OpenStack Integration OpenStack Neutron OpenDaylight exposes a single common OpenStack Service Northbound API exposed matches Neutron API precisely Multiple implementations of Neutron networks in OpenDaylight OpenDaylight OpenStack Neutron Plugin simply passes through Simplifies OpenStack plugin Pushes complexity to OpenDaylight Neutron ML2 MechanismDriver OpenDaylight OpenDaylight APIs (REST) Neutron Service VTN Provider DOVE Provider OVSDB Provider

Developer Community/Activity 23 291 13 154 1.9M lines of code since projects launch 10,411 total

Community Labs Lab Topology Integrate, Test, Verify SDN Apps OpenFlow Switch As the OpenDaylight platform and ecosystem continue to grow, so does the need for testing and integration to ensure interoperability between all the components. Two community labs are publicly available to allow developers to become familiar with the OpenDaylight platform, and help support the integration and testing of SDN and NFV innovations and applications. Ericsson Community Lab: Access the lab remotely or on-premises in San Jose. Details here or email CommunityLab-Ericsson@opendaylight.org to book the lab. Huawei Community Lab: Access the lab remotely. Details here, see the schedule or email CommunityLab-Huawei@opendaylight.org to book the lab. For more information on Community Labs, please visit the Community Labs wiki page. Lab Locations: San Jose, CA, USA and Shenzhen, China http://www.opendaylight.org/developers/community-labs

Continuous Growth to 41 Members

Adoption

EIG/Bluehost User Story Successfully utilizing SDN in data center for more than a year OpenStack and OpenDaylight embedded in 20,000 custom nodes for custom SDN solution *Image from Jun Park, Sr. Systems Architect of EIG/Bluehost, slideware from OpenDaylight Summit 2014

What People are Saying “OpenDaylight is quickly evolving into something formidable with good potential for mainstream relevancy.” – 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

OpenDaylight User Group (ODLUG) Regional, self-organized, informal associations that meet globally to discuss OpenDaylight Share knowledge, recruit and onboard new developers, discuss best practices and technical challenges, as well as create awareness www.opendaylight.org/software/opendaylight-user-groups-odlug

Developer Resources Pull the code and review documentation at wiki.opendaylight.org Connect with active developers in the community on the #opendaylight IRC channel at freenode.net Join the conversation through lists.opendaylight.org and ask.opendaylight.org Propose a new project at wiki.opendaylight.org/view/Project_Proposals:Main

Future Events July 27 – 31, 2015 (Santa Clara)

OpenDaylight Next Steps Adoption User Group Helium Sponsors Interfaces More information and to join: www.opendaylight.org info@opendaylight.org Keep informed and join the conversation @OpenDaylightSDN #OpenDaylight #ODSummit Community