Restructure Quantum API error codes

Registered by Salvatore Orlando

The current Quantum API (1.0) uses HTTP response codes for communicating application-level errors (for instance 420 NetworkNotFound).

The goal of this blueprint is to improve the way in which error codes are returned, by:
1) Using only standard HTTP response codes, such as 400 Bad Request or 401 Unauthorized
2) Embedding Quantum-specific details into the response body
3) Updating the client library in order to reflect these changes

These changes will apply to the next release of the Quantum API only. Since these changes are likely to cause 1.0 client to be incompatible with the next release of the API, we should probably consider labelling the new release of the API as 2.0

The need for this change in the Quantum API arises from the following considerations:
1) Quantum clients might use libraries for RESTFul APIs which expect only standard HTTP response codes;
2) There's no guarantee in the future some error codes used by Quantum will be employed by the IETF for HTTP response codes
3) The other Openstack projects only use standard HTTP error codes.

Blueprint information

Status:
Complete
Approver:
dan wendlandt
Priority:
High
Drafter:
Salvatore Orlando
Direction:
Approved
Assignee:
Salvatore Orlando
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 2012.1
Started by
Salvatore Orlando
Completed by
dan wendlandt

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/api-error-codes,n,z

Addressed by: https://review.openstack.org/3101
    bp/api-error-codes Restructured API error codes for Quantum API v1.1 This changeset provides the following changes: - Only standard HTTP errors for Quantum API v1.1 - Customized fault response body formatting according to API version - Changes to unit tes

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.