We'll discuss what to do with this in E-4. This doesn't break any
existing applications that we know of, and apparently is how it worked
in Essex-2 as well (if I understand the bug report).
** Changed in: quantum
Milestone: essex-3 => essex-4
** Changed in: quantum
Assignee: Netstack (netstack) => Salvatore Orlando (salvatore-orlando)
--
You received this bug notification because you are a member of Netstack,
which is a bug assignee.
https://bugs.launchpad.net/bugs/921743
Title:
Quantum API 1.0 is broken in latest Quantum Essex trunk
Status in OpenStack Quantum (virtual network service):
New
Bug description:
As per our public Quantum 1.0 API specification, our success return
codes on create call is HTTP 200 OK
Reference - http://docs.openstack.org/incubation/openstack-
network/developer/quantum-api-1.0/quantum-api-guide-trunk.pdf
Current Behavior:
The success code is hard-coded in Quantum API, irrespective of API
version of 1.0 or 1.1, therefore the success response code while
correct for API v1.1, stands incorrect for API v1.0
Reference( Quantum Essex-2) -
https://github.com/openstack/quantum/blob/essex-2/quantum/api/api_common.py#L103
Recommended Solution:
We will need a mechanism to specify API version specific
'HeaderSerializer' class that contains correct response codes for that
particular version.
Thanks,
Somik
To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/921743/+subscriptions
--
Mailing list: https://launchpad.net/~netstack
Post to : [email protected]
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
