Align API implementation with specifcation

Bug #813433 reported by Salvatore Orlando
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Critical
Salvatore Orlando
quantum (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Precise by Yolanda Robla

Bug Description

There are currently several parts of the API implementation that are not aligned with the specification.
This happened as the specification was updated while the API was being implemented, and therefore the API code now does not reflect the specification.

These issues came out while developing code for API unit tests, and Somik has done a great job in pointing them out here:
https://code.launchpad.net/~netstack/quantum/quantum-unit-tests/+merge/68308

Fixing this issue involves both reviewing the current specification and updating the code. We should strive to comply as much as possible with standards adopted in the Openstack API; also we need to provide full specification for format of request/responses object, both in JSON and XML format; moreover, we probably need another round of review at the status codes. As far as code is concerned, we need to make sure that it implements exactly what is stated on the specification.

Related branches

Changed in quantum:
assignee: nobody → Salvatore Orlando (salvatore-orlando)
Changed in quantum:
importance: Undecided → Critical
Changed in quantum:
status: New → In Progress
Changed in quantum:
milestone: none → diablo-4
Changed in quantum:
status: In Progress → Fix Committed
dan wendlandt (danwent)
Changed in quantum:
status: Fix Committed → Fix Released
Changed in quantum (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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