OpenStack Users are Ready to Move From Hypervisors
OpenStack Users are Ready to Move From Hypervisors
Join the DZone community and get the full member experience.Join For Free
I just got back from the OpenStack Paris Summit a couple weeks ago, and although this is a bit delayed in coming, I did do a talk on this with the OpenStack Online Meetup immediately following my return, but then decided to share my thoughts on the summit in writing as well, for those who missed it.
I simply continue to be blown away by how much this summit grows from event to event, but even more so by how many people are actually already using OpenStack, and are not just in the interested in hearing more camp, and especially in the way they’re consuming it. This has changed in areas that I wouldn’t have anticipated, like in the use of hypervisors, non-private cloud and more - but I’m jumping ahead of myself, I’ll get to that later.
I found the quote below to echo my sentiment exactly.
“It seems like that at the last few US events, people were coming to summits to figure out what OpenStack was. But it seems like everyone here that I talk to is using OpenStack. Some are here to get it more production ready, but they’re using it. They’re committed to it.” - Dave Wright, CEO of storage vendor SolidFire
It was interesting to note that most people also indicated on the ground much different sentiments for the adoption of OpenStack than the first summits I attended, with just a few hundred enthusiasts in attendance. If once upon a time people were adopting OpenStack with cost savings in mind, today most users will say that the leading driver for adoption for them, which is echoed in the recent user survey (released with every OpenStack version), is the ability to innovate.
In the long run after stabilizing and the initial R&D investments, OpenStack often times does introduce cost savings, however most users are actually turning to OpenStack for the nature of the open technology. This allows them to do much more innovative and unique things with OpenStack that is simply not possible with other closed technologies.
OpenStack orchestration - TOSCA + Cloudify. Check it out. Go
Main Themes Behind the Juno Release
One of the major focuses of the event, was of course the OpenStack Juno release, which is the 10th OpenStack release. Where the previous post discussed the major stats, I’d like to just quickly outline here the innovations that Juno brings with it.
From the case studies at the event, you can see that OpenStack is no longer just a niche technology - there are major players backing and adopting the technology and betting the success of their organizations on OpenStack, which is unprecedented to date. This is just a small snapshot of the companies who presented their stories at the summit.
The most notable and memorable story for me was the BMW story, who use OpenStack for the design of their new cars. It was interesting to hear their needs for high availability, where even 60 seconds of downtime represent the cost of a BMW i8 - the car they also flamboyantly displayed onstage.
Right now, OpenStack Juno is the most widely supported cloud platform to date, which has expanded significantly for testing and plugins. This can be seen on a few levels:
Storage policies for object storage
Federated identity enhancements
Laying the Foundation for NFV Support
I’d like to pause and focus a little on the added NFV support introduced in Juno, as I believe this is a game changer in the carrier and networking world. This was also the topic of my talk at the summit - Application and Network Orchestration Using HEAT & TOSCA. Where, just as an aside, I’ll share an anecdote that, for me, demonstrates the true readiness for real world use. In the talk, we had a demo of an NFV OpenStack Skype-like platform we built with Clearwater using Heat, TOSCA and Neutron, and throughout our talk we kept unexpectedly receiving calls by one of my team members who didn’t realize we were in the middle of our session. So this is just an honest to goodness real-life testimony to the incredible and robust technologies you can build on OpenStack.
This also correlates with the number of sessions events and participants, and even the number of questions that we answered at the end of our session about NFV and TOSCA, which demonstrates a real need and readiness to adopt these using OpenStack. NFV is clearly an area where OpenStack is a natural home for implementation, being able to drive an entire industry into cloud and virtualization by providing the control and flexibility of the infrastructure, and by bringing the networks and apps to collaborate together in the same community for the first time. This community brings application developers into the same room as network and infrastructure architects, as well as carriers that previously used to live in completely separate worlds.
The interesting part behind the NFV advancements and features that were released with Juno is the amazing fact that this focus group met for the first time, and outlined a plan at the OpenStack Summit in Atlanta in May. This is such a testament to the commitment and agility possible with open technology that recognizes a gap, and works toward bridging it.
New Data Processing Capabilities
OpenStack Juno introduced with it new data processing capabilities, and big data support. Mirantis summed up everything interesting in Sahara in this post - so I will just quote the highlights of the features introduced into Sahara with the Juno release as they outline it:
Two new provisioning plugins and the Cloudera Hadoop Distribution plugin are included.
Provisioning and EDP engines have been enhanced to support more cluster setups and job types.
Swift authorization offers better security.
The Sahara UI has been incorporated into the OpenStack Dashboard project.
Support for running in distributed mode is in alpha state.
Other updates are also available.
Below is a screenshot of the UI and the architecture of this big data project, and you’ll find more specific references to the project in the Mirantis post above.
How Users Are Using OpenStack
I mentioned the user survey released with every OpenStack version above, and we will be doing a dedicated post on these OpenStack statistics, like with previous surveys. However, I would like to highlight just a few stats that caught my attention and represent interesting trends to keep an eye out for.
When I look at survey data, I actually like to focus most on the mid-range numbers, as I believe these represent a growing trend that is worthwhile to keep monitoring. I find that these are usually only the beginning of an upward trajectory.
Users are getting more comfortable running OpenStack outside their private clouds.
Where once upon a time, OpenStack was perceived as a private cloud solution, many users are now beginning to explore the use of OpenStack for other use cases including hosted private cloud - where Mirantis and Rackspace are the first to offer such a service, through public and even hybrid cloud use of OpenStack.
30% users are on non-hypervisor VMS.
And here I come to possibly the most disruptive trend I’ve found with regards to OpenStack consumption. If before non-hypervisor usage was almost a blasphemy it looks like there is a growing trend of consuming OpenStack that not only is new to the OpenStacksphere, but is completely unique and possible only with an OpenStack environment - where controlling the infrastructure just isn’t currently supported with other clouds. For example, there are two ways to run Docker with Nova Compute or a Heat Resource. However, there is another option of running Docker on bare metal. This way of consuming OpenStack is why it is considered key to innovation right now.
New Kids on the Block
While Puppet still dominates, the interesting trend is actually what’s happening in production environments. You can see that Ansible has surpassed Chef in adoption for production environments.
Interoperability with other clouds is key for OpenStack users.
The use of multiple clouds is reality, with more than 80% of respondents noting the use of another public cloud. Nearly one fifth are making use of multiple other clouds. This shows that the consumer side of OpenStack cares and still needs interoperability with other clouds, as opposed to the developers of OpenStack who are quite often still focused on getting the stuff ready, and are less concerned by interoperability. This is a classic area in which the broad community of Paris can serve to bridge a gap, and where OpenStack needs to encourage external projects to support and embrace OpenStack.
Summing it Up
One of the advantage in working with an open community like Openstack is the ability to know directly from the source how people are using it. The survey provides a fairly effective measure on the level of maturity and also, the trends and tools in quantifiable metrics.
One of the most surprising indications in this report is the level of readiness of users to run OpenStack not just in pure private cloud environments like before, but also in hosted and public cloud environments. It was also quite surprising to me to see the level in which people are starting to deploy OpenStack on non-hypervisor technology. This last fact has the potential to entirely disrupt the way cloud infrastructure works, especially as we start to think of a cloud that runs purely on containers such as Docker or a combination of bare-metal and containers.Every time I attend an OpenStack Summit I’m repeatedly awestruck by the speed of the growth of the community and the truly innovative ways people are taking the technology and using it in the real world. I have grown immensely and discovered so much through this vibrant community. I’m already looking forward to the next summit.
Published at DZone with permission of Sharone Zitzman , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.