Businesses love OpenStack. After only three years, OpenStack corporate backers and users now include Cisco, Red Hat, Rackspace, IBM, Intel, HP, etc., etc. You get the idea. That's all very nice and well, but where does OpenStack go from here?
We know that the next release,, won't include that many new features. From where I sit, the two big ones are:
- Metering: For central collection of metering/monitoring data for use in for billing systems and the like.
- Orchestration: Code-named Heat, this is is a template-based orchestration engine It will orchestrate cloud infrastructure resources such as storage, networking, instances, and applications into a repeatable running environment
And, that's pretty much it.
We also know that Load-balancer-as-a-Service (LbaaS) will see some improvements. As Jim Curry, one of OpenStack's founders and today Rackspace's general manager of private cloud, told me recently, " ." Instead, "It will be much more about continuing to stabilize it and make it more manageable and even better for real deployments."
Despite Cloudscaling CEO Randy Bias telling the OpenStack community that it should put its efforts behind Amazon Web Services (AWS) cloud application programming interface (API) compatibility, we can be pretty certain that isn't going to happen.
Mega-tech blogger and OpenStack startup liaison officer Robert Scoble replied on Google+ that after "meeting with a raft of Amazon customers" … he didn't find "a single startup has told me that they won't go with OpenStack because of API compatibility issues. Rather they say they don't see an innovation alternative yet to Amazon."
Bias has since publicly replied that he doesn't want for OpenStack to stop innovating by any means but that "Amazon compatibility must happen in addition to all other OpenStack innovations." Based on my discussions with OpenStack insiders I think I can safely say that isn't going to be happening.
What will be happening in future releases, based on what OpenStack users want, is a variety of small features that add up to some big improvements.
- Simplify installation and configuration.
- Enable rolling migrations, aka upgrades with minimal downtime.
- Improve documentation, which is always an issue for open-source projects.
- Add Secure-Socket Layer (SSL) security to all OpenStack network communications.
- Add out of the box high availability (HA) for OpenStack components and virtual machine (VM) re-starts.
- Incorporate Active Directory (AD).
- Ensure compatibility across different OpenStack implementations.
Put it all together and it sure won't get as many headlines as AWS API compatibility, but it may just lead to a better OpenStack cloud.