gigabytes and volumes still present in nova command line client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-novaclient |
Fix Released
|
High
|
Nikola Đipanov |
Bug Description
trying latest devstack, i can see quotas for volumes and gigabytes as shown below. these were removed as part of https:/
Note that os-quota-sets API changed as a result as well, we can no longer get/set gigabytes and gigabytes using that API
root@dims-
+------
| Property | Value |
+------
| cores | 20 |
| floating_ips | 10 |
| gigabytes | None |
| injected_
| injected_files | 5 |
| instances | 10 |
| metadata_items | 128 |
| ram | 51200 |
| volumes | None |
+------
root@dims-
+------
| Property | Value |
+------
| cores | 20 |
| floating_ips | 10 |
| gigabytes | None |
| injected_
| injected_files | 5 |
| instances | 10 |
| metadata_items | 128 |
| ram | 51200 |
| volumes | None |
+------
root@dims-
usage: nova quota-update [--instances <instances>] [--cores <cores>]
error: too few arguments
Try 'nova help quota-update' for more information.
quick browse of python client code shows that it still has support for volumes and gigabytes:
https:/
Changed in python-novaclient: | |
status: | New → Confirmed |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in python-novaclient: | |
importance: | Undecided → High |
Changed in python-novaclient: | |
status: | Fix Committed → Fix Released |
Looks like maxTotalVolumeG igabytes and maxTotalVolumes are AWOL from "v2/{tenant_ id}/limits" as well
# curl -i http:// 127.0.0. 1:8774/ v2/cf4b48af9297 4d0c803d3e3eba7 06728/limits -X GET -H "X-Auth-Project-Id: demo" -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: bbf73c9dea0b435 4baea5bc6e7f73d a3" Request- Id: req-d9ef5e32- a2ed-42d9- 8f76-5f3a5eb6f0 fa
HTTP/1.1 200 OK
X-Compute-
Content-Type: application/json
Content-Length: 1126
Date: Mon, 12 Nov 2012 21:31:43 GMT
{"limits": {"rate": [{"regex": ".*", "limit": [{"next-available": "2012-11- 12T21:31: 42Z", "unit": "MINUTE", "verb": "POST", "remaining": 10, "value": 10}, {"next-available": "2012-11- 12T20:55: 44Z", "unit": "MINUTE", "verb": "PUT", "remaining": 9, "value": 10}, {"next-available": "2012-11- 12T21:31: 42Z", "unit": "MINUTE", "verb": "DELETE", "remaining": 100, "value": 100}], "uri": "*"}, {"regex": "^/servers", "limit": [{"next-available": "2012-11- 12T21:31: 42Z", "unit": "DAY", "verb": "POST", "remaining": 50, "value": 50}], "uri": "*/servers"}, {"regex": ".*changes- since.* ", "limit": [{"next-available": "2012-11- 12T21:31: 42Z", "unit": "MINUTE", "verb": "GET", "remaining": 3, "value": 3}], "uri": "*changes- since*" }], "absolute": {"maxServerMeta": 128, "maxPersonality": 5, "maxImageMeta": 128, "maxPersonality Size": 10240, "maxSecurityGro upRules" : 20, "maxTotalKeypairs": 100, "totalRAMUsed": 0, "totalInstances Used": 0, "maxSecurityGro ups": 10, "maxTotalCores": 20, "totalSecurityG roupsUsed" : 0, "maxTotalFloati ngIps": 10, "totalKeyPairsU sed": 0, "maxTotalInstan ces": 10, "totalCoresUsed": 0, "maxTotalRAMSize": 51200}}}
are we not supporting those 2 quota's any more?