Bug 1042954

Summary: [RFE][oslo]: Additional verbosity information to standard API fault messages within OpenStack common project
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/oslo/+spec/additional-fault-verbos
Whiteboard: upstream_milestone_none upstream_status_not-started upstream_definition_drafting
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:14:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-13 16:46:58 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/additional-fault-verbos.

Description:

> This feature aims to allow adding more verbose details within a standard API fault messages, to let a client/user have more information in case of failures.
> Today, some of the standard failures will be well understood when using just the HTTP error codce, the 'message' and 'details' attributes (such as '404'/ 'Item Not found').
> But, in other cases, such as '500'/'Internal Erro', there might be scenarios in which we would like to give more verbose information regarding the failure, and the 'details' attribute won't be enough for that.
> This feature should be part of the common infrastructure within the Oslo project as all other project should refer and use it.
> More details can be found here: 
https://wiki.openstack.org/wiki/File:Verbosity20131020_1.pdf


Specification URL (additional information):

https://docs.google.com/file/d/0B3cJcVMtGJxKdnV6T2diUFhJWVE/edit