| 2016-01-07 22:21:22 |
JF |
description |
URL of the API page affected: http://developer.openstack.org/api-ref-compute-v2.1.html
Specifically the #os-quota-sets-v2.1 section.
In OpenStack Kilo, using the API as directed doesn't work properly. Specifically two things:
1- a PUT on /v2.1/{tenant_id}/os-quota-sets returns a "Not found" error.
2- a GET on /v2.1/{tenant_id}/os-quota-sets/detail does not return the current values of the quota, it always returns the same things as /v2.1/{tenant_id}/os-quota-sets/default
The correct API documentation was actually present on this page: http://developer.openstack.org/api-ref-compute-v2.html
But that page was "unlinked" for some reason from your API docs and replaced with the incorrect implementation details.
The correct API usage should be as described on that page (api-ref-compute-v2), and it also works with compute-v2.1:
1- PUT should be on /v2.1/{admin-tenant-id}/os-quota-sets/{tenant-id}
2- GET should be on the same, /v2.1/{admin-tenant-id}/os-quota-sets/{tenant-id}
It is weird to have to specify the admin tenant id, but that's how the API seems to work....
I was able to find these details by debugging the openstack python client. |
URL of the API page affected: http://developer.openstack.org/api-ref-compute-v2.1.html
Specifically the #os-quota-sets-v2.1 section.
In OpenStack Kilo, using the API as directed doesn't work properly. Specifically two things:
1- a PUT on /v2.1/{tenant_id}/os-quota-sets returns a "Not found" error.
2- a GET on /v2.1/{tenant_id}/os-quota-sets/detail does not return the current values of the quota, it always returns the same things as /v2.1/{tenant_id}/os-quota-sets/default
The correct API documentation was actually present on this page: http://developer.openstack.org/api-ref-compute-v2-ext.html
But that page was "unlinked" for some reason from your API docs and replaced with the incorrect implementation details.
The correct API usage should be as described on that page (api-ref-compute-v2), and it also works with compute-v2.1:
1- PUT should be on /v2.1/{admin-tenant-id}/os-quota-sets/{tenant-id}
2- GET should be on the same, /v2.1/{admin-tenant-id}/os-quota-sets/{tenant-id}
It is weird to have to specify the admin tenant id, but that's how the API seems to work....
I was able to find these details by debugging the openstack python client. |
|
