- December 26, 2015
- Posted by: Nati Shalom
- Category: Uncategorized
Originally posted at @VMBlog
While this has been said many times, before, I believe that 2015 will likely be remembered as the year of the cloud, largely due to the most notable event of the year* (read: decade/century…), the whopping Dell/EMC deal, which clearly marks a change in era. This is a blatant demonstration that literally all the traditional IT players are now fighting for their survival, as I noted in a post titled, “The Disruption Cycle: A Dime a Dozen”.
This (r)evolution puts OpenStack in a fairly interesting spot, as many of these “enterprise” players – from Cisco to HP to IBM, are also some of the strongest driving forces behind OpenStack. New players such as Mirantis have established themselves as the *new* leaders with a second Intel investment of yet another $100M! While Red Hat is still big in the game and is pretty much using its Linux distribution as a way to lock in its existing customer-base.
Cloudify 3.3 has landed – and it’s awesome. Get it!
We have also seen new emerging startups such as Platform 9 and Stratoscale that are now aiming to disrupt not just the traditional incumbents, but also the new leaders i.e. Mirantis and Red Hat,… So bearing all this in mind, it definitely makes for a very interesting scene for my annual prediction exercise. 🙂
Before I jump into 2016 predictions let me start with a quick recap from my previous 2015 predictions.
My first prediction was that one of the core services in OpenStack (and any cloud), the compute service will go through a massive transformation from being hypervisor-centric to a shift into the container/bare metal combo.
Indeed, according to the latest OpenStack user survey a total of 31% are using a combination of bare metal, LXC and containers. That move became the main news for the OpenStack Tokyo summit, i.e. the fact that OpenStack can support all kinds of flavors of compute resources is clearly one of the biggest differentiators in the cloud space. This also fits well with Rob Whiteley’s, VP of Marketing at Hedvig, 2016 predictions which anticipate that Docker will become the #2 hypervisor in OpenStack.
In addition, the 2015 report saw the rise of NFV popularity within the OpenStack community, that is also part of a bigger convergence between Telecom and Enterprise IT.
The latest survey shows that containers and NFV are now considered the top areas of innovation within the OpenStack community even more than a PaaS (don’t worry..I’ll come back to that shortly…).
2014 was the year where Docker burst onto the scene, and basically disrupted everything in its path. It became too big for it to be controlled by a single owner. The latest move by Google and CoreOS in April of 2015 forced Docker to loosen its control over core engine behind Docker and open the rest of the stack to plugins in order to avoid competition from its own ecosystem. In June 2015 Docker announced that it established an industry coalition under the Linux Foundation.
In retrospect I think that my 2015 predictions weren’t a wild guess after all, which brings me to the topic of this post – 2016 OpenStack predictions. In the paraphrased words of Adrian Cockcroft, “follow developer adoption not IT spend. If you’re looking at spend over adoption, then you’re looking back in time”.
As in the previous case, I will use the OpenStack user survey in conjunction with a few other reports and predictions as the main basis for my analysis. (The list of resources is provided at the bottom of this post).
2016 OpenStack/Private Cloud Predictions
The elephant in the room –
I remember the days when OpenStack just started, and we used to compare it with the Linux project. Indeed there are lots of similarities – both are big open source projects that falls right in the heart of our data center architecture. After six years on this journey, I realized that this analogy may have a significant flaw. A cloud is a significantly more complex beast than an operating system, and the biggest challenge isn’t necessarily even a technology or cost challenge. In order to be successful in the cloud business you have to have the skillset and organizational structure and culture that is much closer to that of Amazon, Google and the likes. Clearly most of the enterprises, including those who run big data centers, don’t have that skillset and culture, and more importantly the ROI for building one isn’t clear
What that means is that the entire assumption behind building an OpenStack distro follows the same Linux distro model may be completely broken at its core. It assumes that enterprises have IT that will be able to operate the cloud by taking a distro and managing it in typical IT fashion with vendors like Red Hat, Ubuntu, Mirantis backing it up with support. The reality though, is that most IT organizations are not sufficiently skilled for such an undertaking, and the effort of transforming them into a cloud business doesn’t seem to have an apparent ROI behind it.
This was echoed by other predictions, such as the aforementioned Rob Whiteley predictions: Talent, not technology, is the No. 1 inhibitor to OpenStack success.
Another interesting indication that may point to this flaw is the declining number of small organizations that are adopting OpenStack vs. a growing number of large organizations, as demonstrated in the diagram below:
Given the current barriers for building any private cloud (OpenStack included), this trend makes sense – i.e. for small-sized organizations, it will be more economical to use a public cloud or a simple Docker-based infrastructure than investing in OpenStack. What’s more, is that even large organizations are still running fairly small-sized deployments of OpenStack as indicated in the diagram below, which makes the argument for OpenStack ROI questionable even for fairly sizable organizations.
Prediction 1: Opinionated OpenStack appliances and hosted deployment options will start to replace the plain distro model.
In the immediate/short-term that would mean that organizations will have to rely on others to provide a fully operational OpenStack environment. That means that we will start to see a bigger shift from delivering distros, to pre-packaged appliances that come with an opinionated version of OpenStack coupled with its hardware. Indeed Mirantis, HP, Cisco are leading the trend in this regard alongside new startups such as Stratoscale.
I expect that we will also see more organizations relying on a hosted version of OpenStack, in which case they will outsource the entire private cloud operation to external experts in this domain. RackSpace alongside traditional system integrators such as CSC, Accenture et al, will be leading this category.
Having said all that, the above solution may address the skill set challenge required to operate an OpenStack cloud, but it doesn’t come close to addressing the issue of why you would want to run OpenStack in the first place, which is often to increase business agility and reduce costs. In order for OpenStack to remain a relevant proposition, it needs to go beyond the boundaries of its software distribution and combine other low cost clouds. Which leads me to the next prediction…
Prediction 2 – The rise of new OpenStack platforms which use OpenStack as a universal abstraction on other private/public clouds
VMware has announced its support for OpenStack with VIO. The interesting thing about VIO is that it uses OpenStack as an abstraction layer on top of the traditional VMware stack, and thus allows VMware users to move to OpenStack while leveraging maturity of the VMware infrastructure. It will also allow those users to leverage their existing VMware skill set and this makes the transition to OpenStack from VMware a simpler task.
Platform 9 is a new and promising startup that offers an OpenStack service on top of Amazon, or any other cloud resources. What’s interesting about the Platform 9 approach is that it also reduces the barrier for running OpenStack significantly, and in addition, it leverages the maturity and cost benefit of other clouds such as AWS, GCE, VMware as the underlying cloud resources, and thus uses OpenStack as a universal abstraction for all those clouds.
Prediction 3: PaaS is Dead. Long live the new PaaS
Docker provides a ubiquitous deployment model which makes the traditional opinionated PaaS offering less attractive as I noted in the post “Do I Need PaaS if I Use Docker?. The recent OpenStack user survey shows that Kubernetes which was designed purely around Docker and microservices is gaining momentum quickly, alongside Docker Swarm, Mesos and Cloudify. What’s interesting about this list is that all of them represent a new and fairly different approach for application management and automation to that of the “Heroku” style PaaS. CloudFoundry is still in the lead with OpenShift coming in a close third, however both CloudFoundry and OpenShift had to pivot their entire product to fit the shift to containers. The most notable one is OpenShift that have been re-engineered around Kubernetes.
Another interesting observation about this list is that none of these projects is part of the OpenStack distribution. One possible explanation for the latter is that users tend to decouple their application platform from that of the infrastructure.
I expect that in 2016, all of the application platforms will have support for containers and Kubernetes. I also expect that Kubernetes will take a clear lead in this category. Mesos and Kubernetes have largely been considered complementary to one another so far. I expect that as the two platforms continue to grow up the stack the level of overlap between the two platforms will make them more competing alternatives than complementary ones. The uncertainty around Pivotal due to the Dell/EMC deal, along with the rise of Docker/Kubernetes will be the catalyst for a swift takeover of the adoption of Pivotal/CloudFoundry. I believe OpenShift is in a better position in this regard as it has already made moves to align itself with Kubernetes. Having said that, it remains to be seen whether the additional added value that OpenShift covers on top of Kubernetes is worth the risk of adding another layer of abstraction.
While we can see clear indications for widespread adoption of containers, I expect that the transition to a fully containerized world will take good couple of years, and even more so for microservices. I, therefore expect that in 2016 most of the deployments won’t be able to run the entire workload in microservices/Kubernetes style and would therefore, end up with a mixed workload environment. A good example for this is the use of Kubernetes as a deployment target for microservices and other orchestrations for running the database, big data, event processing and more complex workloads. Cloudify and OpenStack/Magnum are being positioned as the integration platforms that will allow the gluing of these different kinds of tools and workloads together as mentioned in this post Cloudify Meets Kubernetes
Prediction 4: Telecom companies are going to lead the adoption of OpenStack simply because they have no other choice.
While the case for OpenStack ROI in the enterprise domain is being challenged by public clouds for telecoms, OpenStack is probably the only possible option as they are in direct competition with many of the public cloud providers. That’s why we’re seeing a significant rise of Network Function Virtualization among OpenStack users as noted in the graph below:
I expect that by 2016 telecoms will be the clear leaders of OpenStack deployments over enterprises.
Prediction 5: 2nd generation of OpenStack? Using Docker natively with OpenStack will require more fundamental changes in the OpenStack core.
The approach for integrating Docker into OpenStack so far included the addition of Docker as a compute node, as well as adding support for the layers up the stack such as Kubernetes, Mesos using Magnum.
While this seem to be the right first step, it misses some of the fundamental values of containers which offer a complete alternative compute, network and storage stack.
To fully embrace containers, OpenStack will have to go beyond the current OpenStack core and think of a potentially new OpenStack core that will be designed with native support for containers. Red Hat seem to be ahead of the curve in this regard, and are offering a container native stack that has been announced in Tokyo. (Note that in this announcement there’s very little correlation to the current OpenStack services). I believe that in 2016 we’ll start to see a bigger push toward native integration of Docker into the core of OpenStack. I believe that the outcome of this thinking will set the groundwork for the next generation of OpenStack which will take a container native approach and will therefore become simpler and lighter than its predecessor.
Prediction 6: Hybrid cloud takes center stage (finally)
When OpenStack started, it was thought that it could be an alternative to AWS and other clouds.
In reality however, OpenStack is always used in conjunction with other clouds, the most popular one being VMware on the private side, and AWS on the public cloud front.
Having said that, most users have taken a fairly loose approach toward hybrid cloud in which they were operating OpenStack, VMware or Amazon completely differently with very little integration between the two environments. Part of the reason for that approach was that in reality building a hybrid cloud deployment was fairly hard.
There are three things that change this:
- Tooling – new orchestration frameworks and network virtualization now make it possible to automate the process of deployment of applications across multiple clouds.
- Containers provide portable packaging units which makes the ability to run the same software package on multiple clouds significantly simpler than before removing the dependency on a proprietary image format.
- Built-in support for containers by most major clouds provides a common substrate that makes it easier to move workloads between one cloud to another.
Another strong motivation for using a hybrid cloud strategy is the ROI. As I mentioned earlier, the cost for building OpenStack can be fairly high. One of the ways to reduce the cost of OpenStack infrastructure is by integrating OpenStack with other public clouds, which enables extensibility of private cloud instances with on-demand instances, and thus increases the business agility and reduces the overall cost.
All of the above leads me to believe that in 2016 the majority of OpenStack projects will take a tighter hybrid cloud approach as a barring requirement.
The use of containers and Kubernetes, in conjunction with the support of TOSCA by OpenStack, as demonstrated through the TOSCA Parser project, coupled with Cloudify will lead the way in this regard.
Final Notes: The only constant is change
In this dynamic world predictions become a fairly challenging task.
What I like about OpenStack is that I feel that it is certainly getting better at the way it listens and responds to its users demands. The investment in the OpenStack user survey is evidence to that. The latest user survey is by far the most comprehensive and insightful report. Kudos to the Foundation for a great delivery!
In this prediction exercise I relied on the user survey along with other prediction reports that I’ve listed below and hopefully the result of this process will yield more accurate predictions.
Regardless of all this, what’s clear is that the only constant is change – so if I have one piece of advice to give it would be – embrace change. When planning your 2016 OpenStack strategy make sure that your choices will allow you to adopt new technology faster, as your speed of innovation is going to be determined by the speed of adoption.
OpenStack User Survey