Cisco celebrated OpenStack’s 3rd birthday recently by releasing the Cisco OpenStack Installer for Grizzly. This blog post has more details.
The OpenStack foundation organizes a four-day OpenStack Summit every six months for contributors, enterprise users, service providers, application developers and ecosystem members. It facilitates the community to gather, discuss and present on several different streams ranging from keynote presentations and general sessions to workshops and developer sessions for planning the next OpenStack release. The next OpenStack Summit will be held in Hong Kong from November 5th to the 8th 2013 at the Asia World-Expo. The number of attendees for the Summit is expected to be around 5000 people. More information on the Summit and how you can register to attend is available here.
Speaking proposals are submitted by the community from anyone with an idea or topic they would like to present. The proposals are voted on by the community to secure a slot in session track. Submissions for the OpenStack summit general sessions closed on July 31st 2013 and are now available for vote.
As compared to the Portland summit that had 250 proposal submissions [you can view session videos from OpenStack Portland Summit here, the Hong Kong summit has more than 600 submissions. There are a lot of great proposals but only the best and most popular will make it to the Summit. The approved sessions typically get recorded and are available for viewing online as well.
Cisco’s OpenStack team submitted several proposals that highlight our involvement and contributions to OpenStack. The table below lists the proposals along with a link to the abstract and speaker details.
Community voting is open now and if you are interested in any (or all) of the above proposals, please vote for them here. The voting is open until Sunday, August 25th 2013. Please note that you do need to be an OpenStack Community member in order to vote; If you are not currently a member, you can easily register for membership via the OpenStack website.
Stay tuned for more updates, as we get closer to the OpenStack summit.
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!
Thanks to SDN, the “Controller” word pops up in many network architecture discussions these days. In networking alone, we’re already surrounded by many “controllers” and we’re busy introducing more as we speak: For example, Session Border Controllers or Wireless LAN Controllers have been around for quite some time, and have recently announced the OpenDaylight Controller, the Cisco XNC, or the Cloupia Unified Infrastructure Controller. So what is a “Controller” in networking terms, and how many do we need in emerging network architectures?
I admit it. I’ve grown weary of the debate about whether SDN includes network programmability or whether or not SDN can only be accomplished through NfV, or the relative merits of control plane / dataplane separation. I will leave those debates to others more focused on the technology itself. Personally, I have been more fascinated with what I see as the new business opportunities emerging around SDN.
Certainly there is a raft of opportunities for start-up companies in the controller space or in the virtualization of various networking functions. Many innovative new companies are re-examining existing network functions within the SDN paradigm; that will lead to some potentially new and useful approaches that may be cheaper/easier/faster than current designs. No doubt many customers will see value in these new ways of doing things, and everybody will benefit.
But that’s not what I find fascinating about SDN. What I am starting to see are ideas that are completely out of the box, and would likely not be thought of by typical network technologists working alone. Let me discuss a few categories of things I have seen possible with the emerging technologies.
The Network as a Compute Resource
It turns out Read More »
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.