Cisco highlighted its support for OpenStack at the recent OpenStack Summit in Atlanta, which hosted 4500+ attendees and included many more users, in addition to the developers and operators that have dominated past conferences. A common theme among keynote presentations was the speed and flexibility of IT required to support the clouds that will soon dominate commerce and communication worldwide. The effort underway to improve stability was also a recurring discussion topic.
OpenStack Summit, May 12-15 in Atlanta
From its beginning as an open source project at NASA, the OpenStack movement has grown as an open alternative to propriety cloud services and applications. The Summit serves as a forum for those interested in hashing out the direction and adoption of the model and standards, as well as a learning opportunity for those ready to build and deploy on them.
Keynote speakers from Wells Fargo and Disney helped transition the Summit from an academic exercise to a forum for learning how innovative companies are taking control of their cloud environments.
Glenn Ferguson, Head of Private Cloud Enablement for Wells Fargo, described the compliance, auditing and governance Wells requires in its private cloud, that aren’t available in public cloud offerings. Wells has designated OpenStack their “cloud infrastructure model” to facilitate rapid deployment of infrastructure to meet application developers’ needs and requires all IT vendors to work within the OpenStack specifications. “This is something we have to do to remain agile and competitive in this environment,” Ferguson said. “Our infrastructure needs to keep pace with the software.”
Chris Launey, Disney’s Director of Cloud Architectures and Services, was blunt in how he described the value of speed. “If you’re a business that deals in any kind of information, you need speed (to thrive.) “If you give (developers) their own ‘fast’, they’ll make their own ‘cheap’ by getting their product to market quickly and responding to customer demands. And (they’ll) make their own ‘good’ by shrinking development cycles and introducing improvements more often, until they reach a virtual continuous cycle of improvements.”
The OpenStack Foundation divides the work into individual projects focused on the various cloud components: servers, object-based storage, networking infrastructure, security, etc. Proponents are excited about the innovation that can be unleashed when developers are freed from having to worry about the complexities associated with underlying infrastructure and can focus on the innovation of cloud services and applications.
Cisco was highly visible at the Summit, drawing standing-room-only crowds to sessions in the Networking Track, as network stability and scalability are top-of-mind for users deploying critical applications and services to an open source cloud.
Lew Tucker, Cisco Vice President and CTO for Cloud Computing and Vice-Chair of the OpenStack Foundation, painted a picture of what is possible in his presentation “Open Stack and the Transformation of the Data Center.” He described how the data center is becoming a large, highly automated “fabric” consisting of interconnected physical systems and virtualized services. In this environment, OpenStack acts as a platform for building a highly efficient cloud, providing management of diverse infrastructure “below” and orchestration of a vast set of application services “above”.
Lew Tucker, Cisco VP and CTO of Cloud Computing
Cisco’s key contribution to OpenStack has been participation in the development of Neutron, the OpenStack Networking Service. There is clearly a need to have the same level of visibility and management flexibility that Cisco has been offering its customers in an open source cloud model. In addition to driving connectivity generally, Cisco has received approval on blueprints for plugins to integrate VPN- and Firewall-as-a-Service as part of OpenStack networking. (Referred to as Network Function Virtualization (NFV) plugins.) Cisco is also working on the integration of OpenStack Neutron with OpenDaylight, a separate project started to focus specifically on network programmability. Cisco’s extensive work in the open source community will bring even greater value to its existing customers by extending the ecosystem of solutions integrated with Cisco products.
In the Expo Hall, Cisco highlighted the integration of its networking, compute and management products with OpenStack APIs, demonstrating:
The OpenDaylight Project today announced that its first open source software release Hydrogen is now available for download. As the first simultaneous code release cross-community it has contributions across fifty organizations and includes over one million lines of code. Yes. ODL > 1MLOC. For those of you interested that’s approximately two hundred and thirty man-years of work completed in less than twelve months.
It was around this time last year that the media started to pick up on a few rumors that something may be in the works with software-defined networking and controllers. I remember our first meeting at Citrix where the community started to collaborate on The OpenDaylight Project and come to common ground on how to start something this large. We had multiple companies and academics in the room and many ideas of where we wanted this project to go but there was one thing we had in common: the belief and vision to drive networking software innovation to the Internet in a new way and accelerate SDN in the open; transparently and with diverse community support. Each of us had notions of what we could bring to the table, from controller offerings to virtualization solutions, SDN protocol plugins and apps to solve IT problems. Over two days at Citrix we looked at things from a customer perspective, a developer perspective and ultimately and arguably the most important, a community perspective. From there The OpenDaylight Project emerged under the Linux Foundation. As I look back I want to applaud and thank the companies, partners, developers, community members and the Linux Foundation for driving such a large vision from concept to reality in less than twelve months, which is an incredible feat in itself.
Hydrogen is truly a community release. Use cases span across enterprise, service provider, academia, data center, transport and NfV. There are multiple southbound protocols abstracted to a common northbound API for cross-vendor integration and interoperability and three editions have been created to ensure multi-domain support and application delivery as well as deployment modularity and flexibility for different domain-specific configurations. These packages have a consistent environment yet are tailored to domain and role-based needs of network engineers, developers and operators.
The Base Edition, which includes a scalable and multi-vendor SDN protocol based on OSGi, the latest (and backward compatible) OpenFlow 1.3 Plugin and Protocol Library, OVSDB, NetConf/Yang model driver SDN and Java-based YANG tooling for model-driven development.
The Virtualization Edition (which includes the Base Edition) and adds Affinity Metadata Service (essentially APIs to express workload relationships and service levels), Defense4All (DDoS detection & mitigation), Open DOVE, VTN, OpenStack Neutron NorthBound API support and a virtual tenant network offering.
The Service Provider Edition (again, including the Base Edition) that also offers the Metadata Services and Defense4All but includes BGP-LS and PCEP, LISP Flow Mapping and SNMP4SDN to manage routers, gateways switches.
More information can be found on the website with regards to the releases and projects themselves.
I want to stress the importance of how well the vision has been delivered to date. I’ve been involved in multiple standards-bodies and in open source discussions in the past but this is truly one of the largest undertakings I’ve seen come together in my entire career. OpenDaylight developers have been coding day and night to get this release out the door and it’s amazing to see the collaboration and coherency of the team as we unite to deliver on the industry’s first cross-vendor SDN and NfV Platform. In addition and frequently not mentioned is that many of the protocols listed in the Editions above are also standardized at organizations like the IETF during the same period. Code and specs at the same time. It’s been a long time since rough consensus and running code has been the norm.
Over here at Cisco we’re fully committed to OpenDaylight. We’re currently using it as a core component in our WAN Orchestration offering for service providers to allow intelligent network placement and automated capacity and workload planning. The ACI team (formerly Insieme) collaborated with IBM, Midokura and Plexxi to create a project in OpenDaylight that creates a northbound API that can set policy and be used across a wide range of network devices. And of course we’re bringing components of the OpenDaylight codebase into our own controllers and ensuring application portability for customers, partners and developers alike. From this I would expect to see more code donations going into the community moving forward as well. We made several announcements last week about our campus/branch controller that includes OpenDaylight technology.
At the end of the day an open source project is only as strong as its developers, its community and its code. As we as a community move forward with OpenDaylight I expect it to become stronger with more members joining with new project proposals as new code contributors coming onboard from different industries as well. As I look at our roadmap and upcoming release schedule I’m pumped for what’s next and so happy the community has catalyzed a developer community around networking.
Please do visit the site, download the code and take Hydrogen for a test-drive. We want to hear feedback on what we can make better, what features to add or how you’re going to utilize it. Moreover, we’d love you to participate. It’s a kick-ass community and I think you’ll have fun and the best part; you’ll see your hard work unleashed on the Internet and across multiple communities too.
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.
The OpenStack community recently reached a major milestone and celebrated its third birthday! The flagship open-source compute, storage and networking cloud platform has come a long way since the initial draft. Cisco is proud to be part of this community including participating as Vice Chair of the OpenStack Foundation and as Core Developer for Networking (Neutron).
Back in July, we celebrated OpenStack’s birthday with cake and the release of the Cisco OpenStack Installer for Grizzly. The Cisco OpenStack Installer makes it easy for customers to install, deploy and monitor OpenStack on Cisco UCS servers with networking plugins to the Nexus product line including the Nexus 3k, Nexus 5k, Nexus 6k and Nexus 7k. Watch this demo of how the Cisco Nexus plugin for Grizzly automates the upstream Cisco Nexus Top-of-Rack (ToR) switch:
More information on the Cisco OpenStack Installer for Grizzly can be found here.
We also celebrated OpenStack’s birthday by releasing the Cisco Reference Architecture for RedHat RDO OpenStack with UCS and Nexus. The Cisco OpenStack RDO Reference Architecture can be downloaded here.
Puppet is a key component of the Cisco OpenStack Installer. Cisco will be presenting an overview of Puppet and the Cisco OpenStack Installer at PuppetConf. Cisco will also be presenting details on how Puppet and OpenStack are key components of WebEx. PuppetConf will be held at the San Francisco Fairmont on August 22-23. Check out Cisco sessions at Puppet Conf here.
We would also like to thank everyone for the great interest and support in OpenStack at Cisco Live. David Yen’s keynote featured a demo of the new Dynamic Fabric Automation spine-and-leaf integration with OpenStack. Watch for the Dynamic Fabric Automation mention starting at 30:19 on this video.
The next OpenStack Summit is just around the corner! The OpenStack Summit will be held in Hong Kong on 11/5-11/9. Registration for the OpenStack Summit here.
We are looking forward to seeing everyone at PuppetConf and the OpenStack Summit.