March is a rather event-laden month for Open Source and Open Standards in networking: the 89th IETF, EclipseCon 2014, RSA 2014, the Open Networking Summit, the IEEE International Conference on Cloud (where I’ll be talking about the role of Open Source as we morph the Cloud down to Fog computing) and my favorite, the one and only Open Source Think Tank where this year we dive into the not-so-small world (there is plenty of room at the bottom!) of machine-to-machine (m2m) and Open Source, that some call the Internet of Everything.
There is a lot more to March Madness, of course, in the case of Open Source, a good time to celebrate the 1st anniversary of “Meet Me on the Equinox“, the fleeting moment where daylight conquered the night the day that project Daylight became Open Daylight. As I reflect on how quickly it started and grew from the hearts and minds of folks more interested in writing code than talking about standards, I think about how much the Network, previously dominated, as it should, by Open Standards, is now beginning to run with Open Source, as it should. We captured that dialog with our partners and friends at the Linux Foundation in this webcast I hope you’ll enjoy. I hope you’ll join us in this month in one of these neat places.
As Open Source has become dominant in just about everything, Virtualization, Cloud, Mobility, Security, Social Networking, Big Data, the Internet of Things, the Internet of Everything, you name it, we get asked how do we get the balance right? How does one work with the rigidity of Open Standards and the fluidity of Open Source, particularly in the Network? There is only one answer, think of it as the Yang of Open Standards, the Yin of Open Source, they need each other, they can not function without the other, particularly in the Network. Open Source is just the other side, the wild side!
First Open Daylight Summit took place exactly one year since we’ve started the project, to the day! Ah, those memories of having to stay quietly patient, from our first meeting, February 4th, 2013, and longer… in hindsight, talking about it after the code actually started to flow was more appropriate, the 2013 Spring Equinox, as it should. The Open Daylight community has shown that code is the coin of the realm, as it should. To walk that talk, a million lines of code are flowing now and for a project with partners and committers as diverse as this, one cannot do that unless there is a strong tie that binds, the commitment that the best multi protocol controller will be open source: as Linux achieved that status in the OS world, OpenDaylight has a bright opportunity to do so in the network world. As for the bad news, there aren’t any: yes, we would like to see ourselves talk more about use, before we talk about our size, but for a one year old, I think we should be patient.
The outstanding news for this young project is the community diversity, energy and commitment: it brings the best protocol (SB) guys in the world with the best scientists and network (NB) developers in the world in a focused, collaborative, engaged community. Remember, in open source, community trumps code, which side by side with its project sovereignty, is nothing but a formula for success. That is what sets Open Daylight apart, and as long as we take care of those two things, it will be fine. As I said last week during the event, particularly good to see Google, Intel, Ericsson, Microsoft, Cisco, IBM, RedHat and others doing their presentations celebrating this event. I am proud of these guys, how they lead the way for any other Open Source project interested in leveraging the network (be it Open Stack, Open Compute Project, or others), Linux Foundation and Open Daylight is the best way to stay ahead, to stay engaged: if you are interesting in networking and open source, there is no other better place than this.
Last week at Cisco live! Milan, we announced another milestone in our OpenStack strategy with the availability this quarter of the Nexus 1000V virtual networking platform for Linux Kernel Virtual Machine (KVM) hypervisor and integration with the commercial OpenStack distribution from Canonical (Ubuntu Linux and OpenStack). I had a chance to sit down in Milan with John Zannos, VP of Global Alliances at Canonical, to talk about the Cisco-Canonical partnership, and what the integration of Nexus 1000V into their OpenStack architecture means for customers.
The Nexus 1000V on KVM brings to the OpenStack cloud a fully integrated network virtualization solution. The solution provides a full layer-2 feature set, feature-rich Layer-3 IOS router, security and QoS policies, VXLAN virtual overlays, vPath-enabled virtual services, and full monitoring and management capabilities. Enterprises and service providers may now deploy a full-featured virtual network infrastructure consistently across VMware, Microsoft, and Linux-based software platforms.
Nexus 1000V for Ubuntu Linux with OpenStack support is now available with full automation and orchestration of enablement of the solution via Juju/Charms. Juju provides both a command-line interface and an intuitive web app to design, build, configure, deploy and manage your infrastructure. Charms give Juju its power. They encapsulate application configurations, define how services are deployed, how they connect to other services and are scaled. Nexus 1000V support for Red Hat KVM and OpenStack is planned for later this year.
Additional details and data sheets can be found here.
And on a related note, if you are interested in Nexus 1000V-related items, we recently recorded a technical podcast with Greg Ferro and Ethan Banks of packetpushers.net on the Microsoft Hyper-V version of our virtual switch, which you can find here.
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.
Witnessing the advent and momentum of Open Source into the broader enterprise, and “the mainstream” Data Center, has been incredible. Many will look back and recall a time when Open Source was met first with a look of confusion, and following not too far behind, a reaction of fear. With that, consider how far we’ve evolved.
Taking a snapshot over the past few months, I reflect on some of the highlights from a Data Center and Cisco UCS perspective.
The Open Source Business Conference held not too long ago, centered the conversation around previously uncommon mates. “Open Source” and “Business” used in the same sentence once stirred some emotion, though not today. The notion now fuels curiosity and enablement, and both were alive and well in San Francisco with OSBC. Leaders in the space, spanning established household Data Center vendors were well represented in breakout sessions and thought provoking topics on the show floor, alongside the “up and coming” vendors in Open Source. Linux granddaddies Red Hat and SUSE also offered the Enterprise Linux perspective, with Red Hat CEO Jim Whitehurst taking the stage on the conference’s opening morning. Whitehurst acknowledged the event’s commendable 10th anniversary, and touted the innovation and collaborative successes of Open Source, while reflecting on Red Hat’s significance and market leadership. SUSE kept the Enterprise Linux subject current, presenting SUSE’s role in Big Data workloads, where attendees may have pondered “What would Big Data look like, and be today, without the success and progress of the Open Source movement?”
An “open cloud” panel featuring several notable figures in Open Source leadership for cloud infrastructure, including Marten Mickos of Eucalyptus Systems and Joshua McKenty of Piston Cloud, shared insight on how today’s generation of Open Source leaders are shaping the future of cloud software stacks, infrastructure, and API (read: interoperability). This proved to be a fascinating discussion on project governance, expectations of Open Source, and how customers leverage Open Source to deliver the applications of tomorrow.
Open Source @Cisco
Cisco Open Source Days provide an opportunity to share, learn and grow. Cisco engineers and product teams descend on the San Jose campus packed with an agenda to share knowledge and best practices, new developments in the community, exchange ideas and share successes, and inspire new ways of delivering software and products. This year featured a cornucopia of topics that would make any card-carrying Open Source geek blush. Typically there are multiple tracks and this year included Big Data and Analytics, Cloud, Internet of Everything and a few select topics in the Networking and Data Center interest areas. Cisco teams have an incredible opportunity to learn and collaborate, which ultimately benefit the Open Source community and our customers. Attendees enjoyed thought provoking and engaging presentations, including appearances by Chris Wright from Red Hat, and Troy Toman from Rackspace within the Cloud track, as well, our very own OpenStack leaders within Cisco. Overall there were great takeaways on collaboration and innovation, project participation and furthering common goals through upstream contribution, and solving market problems through emphasis on differentiation rather than upstream code nomination. Another memorable moment, I personally enjoyed Chris Wright’s comical reference to the IFC television comedy, “Portlandia”, referring to the popularity of API’s with “Put an API on it”.
Open Source in the Cisco UCS powered Data Center
One of the most exciting aspects in my role revolves around connecting Open Source innovations with Cisco’s UCS x86 based platforms. Software and API enable many integration use cases most people are not used to expect from server and infrastructure platforms. “Software Defined” is used quite liberally these days, with ” Software Defined __Fill_In_The_Blank__ ” found where it probably shouldn’t be. I digress, Open Source is at the core of these “Software Defined” possibilities, enabling vendor agnostic API structures and interfaces as an alternative to traditionally proprietary closed-configuration products.
The conversation with customers today is less “Oh, Cisco makes servers?” and more about, “Help me learn more about your software integration capability in my Data Center infrastructure.” Once customers deploy UCS, they quickly realize the efficiencies and power derived by the Cisco UCS Service Profile, and the level of control and manageability not available with other solutions. For Data Center management requiring a view into their systems’ availability, the UCS XML API provides that ability, where the customer’s software may retrieve, configure and automate infrastructure that previously required manual intervention. We truly feel this enables a unique “Software Defined Infrastructure” way of managing applications, availability and user workloads through software, previously not seen without custom hardware and software integration.
It’s an exciting time for Open Source, and for computing platforms like Cisco UCS which provide an open and extensible ability to deliver on business demands of tomorrow. Exciting times are definitely ahead as customers increasingly adopt Open Source, its flexibility, advances, and innovations, into the broader enterprise and mainstream computing spaces.