True Story: When my son was about 3, I took him to go see his first movie in an actual movie theater. They had just built a brand new theater near our home and he was suitably impressed with all the bright shiny lights. Anyway, we got our popcorn and grabbed our seats just as the lights were dimming (you never really go anywhere quickly when an inquisitive toddler is involved). We got through the movie trailers, then, to my surprise, my son popped out of his seat and said he was ready to go home. Being his first movie-going experience, he thought the trailers were the big deal and did not realize we had not yet gotten to the featured attraction.
I was reminded of this after watching some conversations around SDN and programmability unfold over the last few days. If you believe to some of the folks out there, SDN is a settled matter--the technology is done, use cases nailed, and winning vendors already crowned. All that’s left is for the janitors to sweep the popcorn off the floor.
Read More »
Tags: Cisco Open Network Environment, future, OpenFlow, OpenStack, SDN
In case you are still in denial, we entered the 3rd week of our 6 weeks long Unified Data Center IQ Challenge . Since Sunday midnight PST , you can find on www.Facebook.com/ciscodc , a new set of questions , focused this week on Cisco Intelligent Automation and OpenStack .
Don’t tell me that you can’t answer at least one question ! Remember that only one correct answer makes you eligible to participate to the raffle for the iPAD.
So now , let me help you a little bit more to thank you for being on this blog -- Why don’t you check the last blog of Rodrigo Flores about the announcement
Cisco Intelligent Automation for Cloud -- OpenStack support (And AWS, vCloud, vCenter) -- I bet it can’t hurt .
Read More »
Tags: Cisco, cloud, data center, intelligent automation, OpenStack, Unified Data Center IQ
With the recent news about the Cisco Edition of OpenStack, I wanted to take some time to write about the contributions Cisco has done in the OpenStack community. Cisco’s engineers have been active in many areas of OpenStack. Below is a sample of some of the work being done by engineers at Cisco.
- Cisco has been an active participant in the Quantum community since it’s creation. Cisco presented one of the original four blueprints which lead to the creation of Quantum at the Diablo Summit. The communities continued efforts have helped to ensure Quantum’s inclusion as a core project in the OpenStack Folsom release, and Cisco has been a key part of this work. The work Cisco has done here includes having multiple engineers on the Quantum core team doing code reviews, feature work, and bug fixes.
- Work on integrating Quantum into Horizon was initially done by engineers from Cisco. This work has led to an increased effort to expose Quantum functionality into Horizon.
- Cisco has contributed code and leadership around unit testing and integration. This is an increasingly important area to focus on. A project as large and distributed as OpenStack benefits highly from this type of infrastructure work.
- Cisco has had engineers working on Nova in various capacities, with a focus on Quantum integration issues and bug fixes.
In addition to these OpenStack projects, Cisco has also contributed code around some Open Source projects which OpenStack makes use of.
- Cisco worked with Nicira engineers to integrate support for Open vSwitch into libvirt. Cisco has continued to support and enhance this work going forward.
- Cisco has contributed bug fixes, code reviews, and some feature work on Open vSwitch.
Cisco expects to continue and increase its involvement in both OpenStack and other Open Source projects. We look forward to collaborating with you in these vibrant communities going forward!
Tags: libvirt, open source, Open vSwitch, OpenStack
So, with our announcements around OpenStack this week a few folks have asked me how OpenStack fits into our broader strategies like Cisco Open Network Environment. The short answer is “quite well, actually”, the longer answer follows.
If you look back our original introduction of the Cisco Open Network Environment, we made a couple of points—there is a plurality of use cases and as a result, there need to be a plurality of enabling technologies. While there are common objectives such as agility and programmability to better handle the macro trends like cloud and virtualization, the truth is, everyone has their own design objectives and priorities. To that sentiment, I might add that folks have varying operational objectives and priorities—the appetite for the amount of risk and complexity they want to take on.
With the three-pillar structure of the Open Network Environment, we feel like we have given folks the flexibility to choose the right technologies for the job. With initiatives like OpenStack we now support a different kind of flexibility.
While a segment of the market seems to want to start writing their own protocols and hand-wiring flow tables, a different segment of the market is moving in the other direction, expressing a desire to get out of the infrastructure business and focus their time and efforts on their apps and their users—this has traditionally been the Vblock and FlexPod crowd. With OpenStack, they now have another option—they get the programmability we talk about with the Open Network Environment, but at the stack level, instead of at the box level. The idea behind something like the Cisco Edition of OpenStack is simplify the task and reduce the risks of standing up a cloud stack. You have the full Folsom release of OpenStack, some Puppet recipes to simplify deployment and validation against the relevant Cisco hardware (follow that last link for details).
To get more insights into our OpenStack announcements this week, check our this blog by Lew Tucker, our VP/CTO for Cloud Computing and this post by Kyle Mestery, one of the many Cisco folks who has invested a great deal of time and effort in OpenStack.
One final thought. We are a long way from being done yet. In just the last few days, I blogged about how our Virtuata and vCider acquisitions fit into a multi-cloud strategy, we have had the aforementioned posts related to this week’s OpenStack announcements, and Rodrigo Flores just posted about our Multi-Cloud Acceleration Kits for our Intelligent Automation for Cloud solution. While cloud is the destination, there are many ways to get there as we have customers and we will continue to innovate and partner on a number of fronts and in a number of ways that will likely surprise some folks. Stay tuned.
Tags: Cisco Open Network Environment, Cloud Computing, FlexPod, OpenStack, programmability, SDN, Vblock, virtualization
As the OpenStack Summit in San Diego is about to start, I wanted to look back upon this past year and talk about Cisco’s future with OpenStack.
When first learning about Rackspace and NASA coming together to create OpenStack, we saw an opportunity for Cisco to contribute to an important open source project to build a new platform for cloud computing. Since then, we’ve seen the community grow and more companies get involved to build on OpenStack as a platform for their own cloud services.
During this time, our OpenStack@Cisco team has contributed expertise and code to advance the platform. Working with several other vendors at the Santa Clara design summit in 2011, we started the Quantum networking service as an incubation project which I’m pleased to say has now moved into core with the Folsom release. This project makes networking a first class citizen alongside compute (Nova), and storage (Horizon), representing a significant step forward in how cloud computing platforms are built and operated.
Read More »
Tags: Cisco ONE, cloud, OpenStack, WebEX