Now that OpenDaylight has arrived, it’s time to explain why I made the Open Source choices eventually embraced by its Founders and the community at large. One doesn’t often see such leaders as Cisco, IBM, Intel, HP, Juniper, RedHat, VMWare, NEC, Microsoft and others agree, share and collaborate on such key technologies, let alone the latter engaging in a Linux Foundation based community (some thought hell will freeze over before that would ever happen, though it got pretty cold at times last Spring).
For those of you not familiar with OpenDaylight (see “Meet Me On The Equinox”, not a homage to Death Cab for Cutie or my Transylvanian homeland), IBM and Cisco have actually started this with an amazing set of partners, nearly that ephemeral Equinox this year (~11am, March 20th) though we couldn’t quite brag about it until all our partners saw the daylight, which by now, we’re hoping everyone does. It was hard not to talk about all this as we saw those half baked, speculative stories before the Equinox – amazing how information flew, distorted as it were, but it did; I wish source code would be that “rapid”, we’d all be so much better for it…
The Open Source model for OpenDaylight is simple, it has only two parts: the community is hosted in the Linux Foundation and the license is Eclipse. The details are neatly captured in a white paper we wrote and published in the Linux Foundation. Dan Frye, my friend and fellow counterpart at IBM and I came up with the main points after two short meetings. It would have been one, but when you work for such giants as our parent companies and soon to be OpenDaylight partners, one has to spend a little more time getting everyone to see the daylight. It boils down to two things, which I am convinced are the quintessential elements of any successful open source project.
1) Community. Why? Because it trumps everything: code, money and everything else. A poor community with great code equals failure (plenty of examples of that). A great community with poor (or any) code equals success (plenty of examples of that too). Why? Because open source equals collaboration, of the highest kind: I share with you, and you with me, whatever I have, I contribute my time, my energy, my intellectual property, my reputation, etc.. And ultimately it becomes “ours”. And the next generation’s. Open Source is not a technology; it’s a development model. With more than 10 million open source developers world wide, it happens to be based on collaboration on a scale and diversity that humanity has never experienced before. Just think about what made this possible and the role some of the OpenDaylight partners have already played in it since the dawn of the Internet. Dan Frye and I agreed that the Linux Kernel community is the best in the world and so we picked the closest thing to it to model and support ours, the Linux Foundation.
2) Fragmentation, or anti-fragmentation, actually. Why? The biggest challenge of any open source project is how to avoid fragmentation (the opposite of collaboration). Just ask Andy Rubin and the Android guys what they fear the most. Just ask any open source project’s contributors, copyright holders, or high priests, how much they appreciate an open source parasite that won’t give back. Though we would have liked to go deeper, we settled on Eclipse, largely because of the actual language and technology we dealt with in the OpenDaylight Controller: most, if not all the initial code is Java, and though some are worried about that, I’m sure Jim Gosling is proud (btw, I’m not sure the Controller has to stay that way, I actually agree with Amin Vahdat), but we had to start somewhere. Plus having a more friendly language NB (northbound, as in the applications run on top of the Controller) is such a cool thing, we think that the #1 open source (Eclipse) and the #1 commercial (Microsoft) IDE’s are going to be very good to it, so why not? There are more reasons that pointed in the Eclipse direction, and other reasons for such wonderful alternatives (as APL or MPL, perhaps the subject of another post, some day). But when it comes to understanding the virtues of them all, no one understands them better than the amazing founders of these license models, most of them from IBM, of course (I wish they did that when I was there).
What happened between the Equinox and Solstice is a fascinating saga within the OpenDaylight community which I think played its course in the spirit of total and complete openness, inclusion, diversity, respect of the individual and the community, and most of all, that code rules – we do believe in running code and community consensus. I tip my hat to all my fellow colleagues that learned these two things along the way, the enormous talent at the Eclipse and Linux Foundation that helped us launch, and even the analysts who tried (and did incredibly well at times) to speculate the secret reasons why these partners came up with the model we did: there is no secret at all, my friends, we’re simply creating a community that is truly open, diverse, inclusive, and never fragmented. Just like a big, happy family. Welcome to OpenDaylight, we hope you’ll stay!
As part of the Cisco Open Network Environment approach, there’s a lot of news coming out of Orlando from this year’s Cisco Live US event, and a lot of it involves OpenStack. OpenStack has never been more prominent at Cisco Live – and there’s much more to come. This is significant not only because it demonstrates our continued commitment to OpenStack but also the progress of our ongoing product integration efforts.
We had multiple technical breakout sessions and technical seminars on OpenStack, delivered by Cisco OpenStack experts, throughout the event. Here are a few of them:
We’re also featuring six product demonstrations with OpenStack integration. If you are in Orlando this week, please visit the World of Solutions Expo and see them all:
OpenStack with Cisco Nexus 1000v
We’re showing an OpenStack deployment on UCS hardware that uses Nexus 1000v as the underlying host virtual switch. Nexus1000v solution on KVM hypervisor is going to be available soon. We’ve developed an OpenStack Networking (i.e. Neutron) plugin that communicates with the Nexus 1000v VSM module and also configures VEMs on the host. We have introduced network profile and port profile constructs in OpenStack Networking as well as provided enhancement to the OpenStack Horizon (GUI) for Nexus 1000v.
OpenStack Networking and Cisco Nexus plugin
Our OpenStack Networking Cisco Nexus plugin can provide isolated tenant network segments on Nexus physical hardware by provisioning and de-provisioning VLAN’s. The plugin works with Nexus 3K/5K/6K/7K line of switches. This data sheet captures more information.
OpenStack and Cisco Intelligent Automation for Cloud
Cisco Intelligent Automation for Cloud (Cisco IAC) turns OpenStack into a production-ready cloud platform – using our service catalog, orchestration, and cloud management software to complement and extend OpenStack functionality. At Cisco Live, we’re demonstrating how end users can order a virtual machine from the Cisco IAC portal, with OpenStack integration to Nova to fulfill this request.
Cisco UCS Manager and OpenStack
Cisco UCS Manager has extensive hardware provisioning and diagnostic capabilities that will soon be brought into OpenStack. What we’re showing this week is the ability of UCS Manager to detect chassis and blade hardware configurations and initiate an automated OpenStack node deployment. The UCS Manager OpenStack developer community information can be accessed here. Additionally, we also had a breakout session that walked through deploying OpenStack using our Cisco OpenStack Installer (COI): starting from bare-metal provisioning all the way through the deployment of the controller and compute nodes as well as storage, and networking. Visit here for COI setup instructions.
Cisco Dynamic Fabric Automation with OpenStack
The newly announced Cisco Dynamic Fabric Automation is our next generation network fabric solution that provides high performance converged networking across the data center. This week, we’re showing OpenStack Networking with Dynamic Fabric Automation to provision network overlay within the Fabric.
OpenStack integration with Cisco onePK
Cisco Open Network Environment (ONE) architecture expands the capabilities of OpenStack Networking by providing a onePK plugin. We’ll be showing how various Cisco ONE elements can be programmed through OpenStack Neutron and offer Layer 2 and Layer 3 services in an OpenStack deployment. See here for more information.
At the recent Red Hat Summit , OpenStack was also very prominent; the launch of their commercially supported distribution of OpenStack (Red Hat Enterprise Linux OpenStack Platform) filled one of the few remaining gaps for mainstream customer deployment. We’re continuing to work with the OpenStack community and partners like Red Hat to advance the adoption and success of this open source cloud platform. If you want to learn more about OpenStack and Red Hat on Cisco UCS, you can watch these videos from the Red Hat Summit.
This new level of project maturity as well integration with the Cisco Nexus and UCS platforms is accelerating customer adoption of OpenStack. Cisco Live is the obvious place to showcase our success and ongoing commitment to OpenStack.
Stay tuned for more from the OpenStack team at Cisco!
As we continue to expand on the conversation of the Cisco Open Network Environment (Cisco ONE), this week provides yet another educational opportunity (Register here) to discuss a topic that has become some what top of mind to customers, partners and even investors alike. This is the topic of open source in networked environments. While Cisco has always been known for open standards, it has now stepped up into the open source conversation in a fairly big way over the couple of years with its contributions to both OpenStack and the more recent OpenDaylight project under the Linux foundation.
Join me and my good friends Dan Frye and Jim Zemlin, Tuesday June 18th at 8:30 am Pacific, in a webcast as we discuss open source, networking, communities and projects, the opportunities entailed, the win-win-win model (or win-cube model as I like to call it, for the Authors, for the Community and for the Enterprise), and the recently announced Open Daylight project hosted by the Linux Foundation. Thank you, Shashi Kiran, for organizing a wonderful event and opportunity to talk about one of my favorite subjects, Open at Cisco.
While the topic of Open Source is not new, the topic of using open source in today’s networks has gained momentum in recent times, which, not surprisingly, coincides with the broader conversation of open networking. While there is considerable interest, there is also a lot of confusion. Several questions pop-up:
- What is Open Source vs. an Open Standard?
- How do Open Source consortiums work? What is the governance model?
- What are the security implications of Open Source based implementations?
- What are the likes of Cisco and IBM doing in this space?
- What is the Open Daylight project?
- Is open networking the same as open-source networking?
If you would like to get an overview of not only mechanics behind open source projects and communities, but also get a great overview of the recently announced OpenDaylight project from the Linux Foundation, I invite you to register for the 4th session of the Cisco Open Network Environment webcast series “Using Open Source in Networked Environments – Discover the Possibilities and Benefits” broadcasting on June 18th at 9 a.m. PST.
Joining me in this webcast as I host three industry luminaries in the Open Source community including Michael Enescu, Cisco Chief Technology Officer for Open Source Initiatives at Cisco, Daniel Frye, Vice president of Open Systems Development from IBM joining and Jim Zemlin the Executive Director of the Linux foundation.