Open daylight a_year_in_the_life_2014.10.08
•Télécharger en tant que PPT, PDF•
4 j'aime•779 vues
An overview of the first year to 18 months of the OpenDaylight project.
Recommandé
Contenu connexe
Tendances
Tendances (12)
Similaire à Open daylight a_year_in_the_life_2014.10.08
Similaire à Open daylight a_year_in_the_life_2014.10.08 (20)
Dernier
Dernier (20)
Open daylight a_year_in_the_life_2014.10.08
- 1. www.opendaylight.org The OpenDaylight Project August 2014 @OpenDaylightSDN #OpenSDN Christopher Price, Ericsson ODL TSC Member & ODL Ambassador
- 3. www.opendaylight.org Why Open Source? 3 • 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 Flexibility Choice Innovation Control
- 5. www.opendaylight.org Community and Governance 6 Developer Community Open to all Board of Directors Technical Steering Committee Transparency Meritocracy
- 6. www.opendaylight.org Contributions up – 25 proposals Committer diversity – 6 companies represented in Service Chaining proposal Community labs – 1 in US, 1 in APAC https://wiki.opendaylight.org/view/Main_Page Community Activity 7
- 7. www.opendaylight.org Community activity in stats! 8
- 10. www.opendaylight.org 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 OpenStack Integration 11 OpenDaylight DOVE Provider VTN Provider Neutron Service OpenStack Neutron OVSDB Provider Neutron ML2 MechanismDriver OpenDaylight APIs (REST)
- 11. www.opendaylight.org 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 OpenDaylight User Group (ODLUG) 12
- 12. www.opendaylight.org 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 Developer Resources 13
Notes de l'éditeur
- 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.
- 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.
- 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 [email_address] 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.
- Network Apps & Orchestration: The top layer consists of business and network logic applications that control and monitor network behavior. In addition, more complex solution orchestration applications needed for cloud and NFV thread services together and engineer network traffic in accordance with the needs of those environments. Controller Platform: The middle layer is the framework in which the SDN abstractions can manifest, providing a set of common APIs to the application layer (commonly referred to as the northbound interface) while implementing one or more protocols for command and control of the physical hardware within the network (typically referred to as the southbound interface). Physical & Virtual Network Devices: The bottom layer consists of the physical & virtual devices, switches, routers, etc., that make up the connective fabric between all endpoints within the network.
- ML2 Driver available in Icehouse release! Supports VXLAN and GRE tunnel networks devstack support merged upstream Run OpenDaylight as a top-level service in devstack! OpenStack Neutron API Service available now in OpenDaylight provides Neutron API handling for multiple implementations Initial ML2 plugin focused on core Neutron functionality Still uses Neutron [DHCP, L3] agents
- More information and to join: www.opendaylight.org [email_address] Keep informed and join the conversation @OpenDaylightSDN #OpenDaylight #ODSummit