Journal Content
OpenStack at Risk of becoming Vendor Specific
Tags: cloud management, openstack, openstack api
Using Cloud for Disaster Recovery - Business Case - Best Practices and Lessons Learned
Tags: application dr, cloud dr, cloud dr business case, disaster recovery
Cloud Management – Various Solutions and Standards
Tags: cloud management, kaavo system definition, ovf, tosca
Who's Managing Your PaaS Apps?
Tags: app centric, application centric vs. infrastructure centric, application deployment, application-centric, cloud computing, cloud deployment, cloud management, cloud management software, deployment automation, disaster recovery, iaas, paas
Cloud Management – Why we selected an Agentless approach instead of using Agents?
Tags: cloud deployment, cloud management, cloud management software
Showing 1 - 5 of 37 results.
Page of 8
OpenStack at Risk of becoming Vendor Specific
Tags: cloud management, openstack, openstack api

OpenStack started with the primary objective to provide an open standard cloud computing platform and prevent vendor lock.  It has been almost three years since the launch of OpenStack.  During this time almost all major companies in the cloud computing space baring Amazon have gotten behind OpenStack.  I thought it would be interesting to review how OpenStack is doing in achieving its primary objective.

After working with various OpenStack based clouds we found that not all OpenStack based cloud are created equal and we have to account for the differences to be able to support application deployment and management across various OpenStack based clouds.

To see how standard OpenStack implementations are across various cloud vendors, as an example let’s compare  Rackspace Open Cloud and HP Cloud, two of the major OpenStack based clouds.  We found following differences.

Functional Differences
Some of the functional difference between HP Cloud and Rackspace Open Cloud are:

  • HP Cloud supports Security Groups, Rackspace Open Cloud doesn’t
  • Rackspace OpenStack Cloud doesn’t support Key-Pairs, HP Cloud does
  • HP Cloud supports floating IPs, Rackspace Cloud doesn’t
  • In HP Cloud public and private IPs for a server have to be identified by looking at the IP pattern e.g. on HP Cloud public IPs starts with 15.  Rackspace Open Cloud allows this determination through API.

Syntax Differences
There are also some annoying syntax differences:

  • Identity Service for OpenStack returns the list of endpoint URLs for the given service name.  In HP Cloud to get the list of compute service URL you have to pass “compute” as a parameter, in Rackspace Open Cloud you have to pass “cloudServersOpenStack” as a parameter.
  • Unlike Rackspace Open Cloud, in HP Cloud to get full service URLs tenant id has to be specified.

It will be interesting to see in future if various OpenStack implementations will converge to a single standard per OpenStack charter or if they will diverge and each vendor will try to implement their own flavor of OpenStack API to differentiate themselves.  Checkout the blog on Cloud APIs - Why all the fuss around Cloud API Standards? for additional information and thoughts.

If you want a standard interface for application and workload management across various OpenStack based clouds, checkout our integration with Rackspace Open Cloud, HP Cloud, and OpenStack Cloud (API version 2.0).  In addition to OpenStack we also support serveral other public and private clouds, checkout the list and details for using other supported clouds here.

/* */