rackspace-specific "cloudserversFault" name should be generic

While I agree this may not be ideal, it does mean it breaks any APIs that expectt that fault name. I don't see any harm in just keeping it as is, and maybe in the next rev we can redo fault names if needed. The current OpenStack API implementation should keep it for backwards compatibility.

Deleted my branch & merge proposal as Michael already has one with the fixes (if it's decided to use them).

2010/11/23 Eric Day <email address hidden>:
> While I agree this may not be ideal, it does mean it breaks any APIs
> that expectt that fault name. I don't see any harm in just keeping it as
> is, and maybe in the next rev we can redo fault names if needed. The
> current OpenStack API implementation should keep it for backwards
> compatibility.

I just want to mention that I share this concern.

--
Soren Hansen
Ubuntu Developer    http://www.ubuntu.com/
OpenStack Developer http://www.openstack.org/

Fix released based on LGTMs in the mergeprop.

Luckily, the name "cloudServersFault" only appears if an unknown 500 error occurs, as opposed to itemNotFoundFault for 404s, etc.

I'm not really worried, since
the number of organizations deploying Austin times
the chance of an unexpected 500 times
the chance that someone wrote a client that expects 'cloudServersFault' and uses that word when parsing a 500 times
the chance that this mis-parsing will have noticeable consequences for the customer
is rather low :)