I completely forgot that this bug was raised....
so this how 'default quotas' are retrieved in nova:
GET /v2.1/d7960ca10de9478baa1cd2897e63011c/os-quota-sets/d7960ca10de9478baa1cd2897e63011c/defaults
Tenants get "quota sets" that override the default quotas. Neutron applies a similar concept, but it does not differentiate the overriden quotas from the default ones in the response.
Will return the quota for the tenant - which will be the tenant default quotas if quotas were never updated for the tenant.
In Neutron there are no tenant-specific defaults - only global ones.
Therefore you can actually leverage what could be regarded as a Neutron bug to get default quotas, doing something like the following:
I completely forgot that this bug was raised....
so this how 'default quotas' are retrieved in nova:
GET /v2.1/d7960ca10 de9478baa1cd289 7e63011c/ os-quota- sets/d7960ca10d e9478baa1cd2897 e63011c/ defaults
Tenants get "quota sets" that override the default quotas. Neutron applies a similar concept, but it does not differentiate the overriden quotas from the default ones in the response.
GET http:// 127.0.0. 1:9696/ v2.0/quotas/ d7960ca10de9478 baa1cd2897e6301 1c.json
Will return the quota for the tenant - which will be the tenant default quotas if quotas were never updated for the tenant.
In Neutron there are no tenant-specific defaults - only global ones.
Therefore you can actually leverage what could be regarded as a Neutron bug to get default quotas, doing something like the following:
GET http:// 127.0.0. 1:9696/ v2.0/quotas/ meh_i_do_ not_exist. json
Nevertheless, there is a need for a RFE to make Neutron quota mgmt API consistent with the other major openstack projects.