Fei Long Wang fbb1eb9285 Fix return error when resource can't be found
By current implement, the HTTP request for /v2/resources/<resource_id>
will return 500 if there is no coresponding resource or the resource id
is invalid. And the response is as below:

{"error_message": "{"debuginfo": null, "faultcode": "Server",
"faultstring": "list index out of range"}"}

After fixed, the response will be like this:

{"error_message": "{"debuginfo": null, "faultcode": "Client",
"faultstring": "Invalid input for field/attribute resource_id.
Value: '9'. Unknown resource"}"}

Fixes bug: 1195925

Change-Id: I73c73fb3ba57bc6cbbf421f9ac5ec3cdb68ce784
2013-07-02 00:12:12 +08:00
2013-06-12 14:41:41 +02:00
2013-05-18 18:06:38 +10:00
2012-11-11 19:13:08 +00:00
2013-05-18 18:06:38 +10:00
2013-05-11 12:44:54 -04:00
2013-03-15 14:25:48 +00:00
2013-05-11 12:44:54 -04:00
2012-12-05 10:22:43 +01:00
2013-05-11 12:44:54 -04:00

ceilometer

See the ReleaseNotes document and the project home for more info.

http://launchpad.net/ceilometer

Description
OpenStack Telemetry (Ceilometer) Alarming
Readme 21 MiB
Languages
Python 98%
Shell 1.8%
Mako 0.2%