The announcement today of OpenDaylight is big news. Industry leading companies are partnering via Open Source to serve an emerging set of market needs:
- Operators: want affordable real-time orchestration and operation of integrated virtual compute, application, and network.
- Application Developers: want a single simple interface to the network. Underlying details such as “router”, or “switch”, or “topology” can be a distraction they desire to abstract and simplify away.
- Equipment Vendors: want a stable forum to interwork a plethora of Application interfaces with a plethora of nascent Network Device programmatic interfaces.
OpenDaylight members understand Read More »
Tags: API, Daylight, I2RS, intent, open source, opendaylight, OpenFlow, orchestration, SDN, SDN controller, virtualization
It’s great to see Cisco and many companies across the industry make a major change in the use of Open Source via the newly form project hosted by the Linux Foundation called OpenDaylight. This consortium is an industry-wide, open and transparent effort to catalyze innovation and accelerate an application ecosystem for software-defined networking. With all the partners involved we are working to not only further development and adoption of SDN but also to foster a new developer community. A consortium like this has been long overdue and it’s great to finally see it come to fruition.
We are incredibly pleased to partner with Arista, Big Switch Networks, Brocade, Citrix, Dell, Ericsson, Fujitsu, HP, IBM, Intel, Juniper Networks, Microsoft, NEC, Nuage Networks, PLUMgrid, RedHat and VMware on the Project. This is the largest effort to date to drive Software-Defined Networking across the industry and into new markets. While the initial goal is to build a common, industry backed SDN Platform, the broader objective is to give rise to an entire ecosystem of developers that can freely utilize the code, contribute to the project and commercialize the offerings. I further expect the ecosystem to expand into areas like tools and services.
Cisco has donated our core “Cisco ONE” controller code to the project and has officially open sourced the code under the Eclipse Public License. The community has come together around this code to form the architecture (see below) for the Open SDN Framework. Beyond donations of code, Project members are supporting the project via both financial investment and via developers we are committing to work full-time on the project overall. Donations from other members of the Project can be seen here and we expect this list to only grow.
As Open Source increasingly becomes a standard for customers and developers, we look at this as a new way to meet our customer needs and also help developers innovate in new ways without the barriers of vendor lock-in. Open Source is increasingly important for our customers and developers as well and as they evolve, we evolve. Cisco to date has supported Open Source through efforts such as OpenStack and now OpenDaylight and we look at Open Source as a critical pillar in our software strategy moving forward. By allowing developers to freely use these solutions we hope to enable a new developer ecosystem for software-defined networking and more. We are fully committed to enabling developers, both current and new, to deliver innovating applications and services that will help customers across the board realize the value of SDN faster than before.
The OpenDaylight architecture and code offering to date includes a modular southbound plugin architecture for multi-vendor environments. In addition, OpenDaylight offers an extensible northbound framework with both Java & REST APIs to ensure multiple developer skill-sets can build applications to the platform. We are also planning to build a onePK plugin for OpenDaylight to enable multiple users to drive network intelligence into their SDN applications. As you can see from below we will also be supporting key standards with this effort, including OpenFlow.
It’s important to note that you don’t launch a community; you build one. By investing in OpenDaylight we hope that our customers, partners and developers across multiple industries will now have the ability to build applications that frankly make the network easier to use and more automated. As an industry we are moving in a new direction and further up the stack and OpenDaylight offers new opportunities for application creation and monetization beyond the networking layer.
It’s a true rarity when you see both partners and competitors come together for the good of the community, and contribute code for the universal good of the customer. All OpenDaylight participants have committed to open source guidelines that include open communication, ethical and honest behavior, code and roadmap transparency and more. An Open Source project is only as successful as the community of developers and the level of code quality, and OpenDaylight’s Board of Directors (which includes multiple parties cross-industry) will be ensuring that partners, code contributors and project committers all abide by the same guidelines for the success of the project over the success of their own company’s offerings.
For more information, please see www.opendaylight.org. Code will be available for download soon, and we are looking for interested individuals for commitments across the board – from technical offerings to application development, and we welcome contributions from both individuals and other organizations. All ideas are welcome, and we look forward to multiple new innovative solutions coming from this.
Congratulations to all our partners and individuals who helped to make this happen, including the hard work done by the Linux Foundation. It’s truly an amazing accomplishment and we expect to see much more in the near future.
Tags: arista, big switch networks, Brocade, Cisco SDN Controller, citrix, dell, ericsson, Fujitsu, HP, IBM, Intel, juniper, Microsoft, NEC, Nuage, open source, opendaylight, PLUMgrid, RedHat, SDN, VMware
So, after weeks of biting my tongue through what seemed like a constant drip of leaks and rumors, we can finally take the covers off OpenDaylight. So, lets cover some of the basics:
OpenDaylight is an open source project formed 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–essentially we are building a open source SDN stack.
This is the cool part–the Project has drawn members from across the industry. Its actually been pretty interesting working with all these companies towards a common goal over the last few weeks–kinda like an all-star team. This is an open project, so any company can join the project at any time and any developer can get involved.
Read More »
Tags: Cisco ONE, open source, OpenStack, SDN
In this week’s episode of Engineers Unplugged, Colin McNamara (Nexus IS, @colinmcnamara) and Joe Onisick (Insieme, @jonisick) take opposing viewpoints for the OpenStack, cage match. Let’s watch:
Welcome to Engineers Unplugged, where technologists talk to each other the way they know best, with a whiteboard. The rules are simple:
- Episodes will publish weekly (or as close to it as we can manage)
- Subscribe to the podcast here: engineersunplugged.com
- Follow the #engineersunplugged conversation on Twitter
- Submit ideas for episodes or volunteer to appear by Tweeting to @CommsNinja
- Practice drawing unicorns
The OpenStack Unicorn?
Where do you stand? Is OpenStack Enterprise ready? Thoughts, comments, or feedback? Join the conversation @CiscoDC.
OpenStack Cage Match with Colin McNamara and Joe Onisick
Tags: cloud, Colin McNamara, data center, engineers unplugged, Enterprise IT, joe onisick, open source, OpenStack
After a few months of work, I’m happy to announce Cisco has contributed the LISP protocol upstream into the Open vSwitch project. LISP is an open protocol developed by the IETF LISP Working Group. By getting LISP upstream into Open vSwitch, Cisco is continuing it’s tradition of enabling Open Standards by contributing to Open Source projects. What makes LISP interesting in the context of Open vSwitch is the fact it’s a pure L3 tunneling technology, the first in Open vSwitch. The current LISP code in Open vSwitch requires the use of static LISP tunnel endpoints. The instructions in the README file detail how to configure and use LISP tunnels in Open vSwitch. We have plans to remove the requirement for the static tunnels going forward. But for now, people who would like to experiment with LISP tunnels in Open vSwitch can use git to pull the latest master and give it a try. Feedback on the Open vSwitch dev mailing list is appreciated!
Tags: LISP, open source