Where does OpenStack go from here?

August 15, 2013

News

Where does OpenStack go from here?

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?

openstack_logo

We know that the next release, Havana, 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, “The next OpenStack version, Havana, which comes out in October, will not be adding much in the way of new features .” 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.

These are:

  • 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.

Related Stories:

Steven J. Vaughan-Nichols, aka sjvn, has been writing about technology and the business of technology since CP/M-80 was the cutting edge PC operating system. SJVN covers networking, Linux, open source, and operating systems.

http://www.zdnet.com/where-does-openstack-go-from-here-7000019397/

,

Subscribe

Subscribe to our RSS feed and social profiles to receive updates.

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: