OS API /limits resource

Bug #728587 reported by Brian Lamar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Brian Lamar

Bug Description

The API specifies the ability to hit /limits in OpenStack API and receive a listing. For a complete example of what this should look like, see http://docs.openstack.org/openstack-compute/developer/content/ch03s09.html (Examples 3.18 and 3.19)

Related branches

Brian Lamar (blamar)
Changed in nova:
assignee: nobody → Brian Lamar (blamar)
status: New → In Progress
Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Medium
Revision history for this message
Brian Lamar (blamar) wrote :

To be clear, the reason this diff is so long is because when writing this controller I made so many changes to make everything work this is what amounts to a re-write of Limits in the OpenStack API.

What this gets us that we didn't have before:

1) /limits now returns information about applicable limits correctly serialized into JSON or XML

2) Limits in general have been improved to support:
        -Arbitrary regular expressions
        -Improved testability (no more `time.sleep` inaccuracies in tests)
        -Improved test coverage for limits

3) RateLimitingMiddleware returns correct fault with HTTP 403 and not HTTP 413 correctly serialized to JSON or XML.

4) The first tests in OpenStack API to test XML serialized results. (Surprising!)

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → 2011.2
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.