update api version controller

Bug #1004290 reported by dan wendlandt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
yong sheng gong

Bug Description

The API returns information about currently available versions when a tenant queries "/":

curl -H "Content-type: application/json" http://localhost:9696/
{"versions": [{"status": "CURRENT", "id": "v1.0", "links": [{"href": "http://localhost:9696/v1.0", "rel": "self"}]}, {"status": "PROPOSED", "id": "v1.1", "links": [{"href": "http://localhost:9696/v1.1", "rel": "self"}]}]}

This info is now out of date. v1.1 should be "CURRENT", and we very soon will need to add "v2.0" as "PROPOSED".

dan wendlandt (danwent)
Changed in quantum:
milestone: none → folsom-2
importance: Undecided → Medium
tags: added: low-hanging-fruit
Changed in quantum:
assignee: nobody → yong sheng gong (gongysh)
Changed in quantum:
status: New → In Progress
Revision history for this message
yong sheng gong (gongysh) wrote :
Changed in quantum:
status: In Progress → Fix Released
Revision history for this message
dan wendlandt (danwent) wrote :

please note: bugs that are merged should be "Fix Committed", not "Fix Released". ttx will change them to Fix Released when a milestone is dropped.

Changed in quantum:
status: Fix Released → Fix Committed
Thierry Carrez (ttx)
Changed in quantum:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in quantum:
milestone: folsom-2 → 2012.2
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.