Currently the format of error message returned by quota extension was
different with quantum other resource. Other resource will return as
json(eg, '{"QuantumError": "error message"}'). But quota extension only
return messages without any format.
'quantum.api.v2.resource.Resource' provider error messages processing.
So wrap quota controller with it.
By the way, fix some small stuff:
* Use specific exception 'QuotaTenantNotFound' instead of generic exception.
* Correct error message.
* Use attribute mapping checking the request body.
Reviewed: https:/ /review. openstack. org/21197 github. com/openstack/ quantum/ commit/ 987b1a35cdb3631 ab759b5ee6b63ad 6ecb8e1753
Committed: http://
Submitter: Jenkins
Branch: master
commit 987b1a35cdb3631 ab759b5ee6b63ad 6ecb8e1753
Author: He Jie Xu <email address hidden>
Date: Tue Feb 5 19:05:53 2013 +0800
Wrap quota controller with resource.Resource
Fixes bug 1116137
Currently the format of error message returned by quota extension was api.v2. resource. Resource' provider error messages processing.
different with quantum other resource. Other resource will return as
json(eg, '{"QuantumError": "error message"}'). But quota extension only
return messages without any format.
'quantum.
So wrap quota controller with it.
By the way, fix some small stuff: Found' instead of generic exception.
* Use specific exception 'QuotaTenantNot
* Correct error message.
* Use attribute mapping checking the request body.
Change-Id: I71261198aa79e9 ed8e0ae672de325 52abdbf45c1