According to the api-ref [1], the used amount of keypairs is not in the response body. That's why the python-novaclient shows a "-" instead of a zero. In Horizon (the other consumer of the nova REST API) you will see that there is no pie-chart in "Project -> Compute -> Overview".
This means this report doesn't describe a faulty behavior but more a feature request (include the amount of used keypairs in the REST API). Feature requests for nova are done with blueprints [2] and with specs [3]. I'll recommend to read [4] if not yet done. To focus here on bugs which are a failures/errors/faults I close this one as "Invalid". The effort to implement the requested feature is then driven only by the blueprint (and spec). If there are any questions left, feel free to contact me (markus_z) in the IRC channel #openstack-nova References: [1] http://developer.openstack.org/api-ref-compute-v2.1.html#limits-v2.1 [2] https://blueprints.launchpad.net/nova/ [3] https://github.com/openstack/nova-specs [4] https://wiki.openstack.org/wiki/Blueprints ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1556756 Title: nova limits does not show correct quota usage Status in OpenStack Compute (nova): Invalid Bug description: I am running liberty based setup. I have two keypairs in nova. I have assigned one keypair to one of my instance but when I say $nova --debug limits --tenant <tenantid> {"limits": {"rate": [], "absolute": {"maxServerMeta": 100, "maxPersonality": 5, "totalServerGroupsUsed": 0, "maxImageMeta": 100, "maxPersonalitySize": 10240, "maxTotalKeypairs": 100, "maxSecurityGroupRules": 20, "maxServerGroups": 10, "totalCoresUsed": 2, "totalRAMUsed": 1024, "totalInstancesUsed": 2, "maxSecurityGroups": 10, "totalFloatingIpsUsed": 0, "maxTotalCores": 8, "maxServerGroupMembers": 10, "maxTotalFloatingIps": 10, "totalSecurityGroupsUsed": 1, "maxTotalInstances": 13, "maxTotalRAMSize": 50176}}} +--------------------+------+-------+ | Name | Used | Max | +--------------------+------+-------+ | Cores | 2 | 8 | | FloatingIps | 0 | 10 | | ImageMeta | - | 100 | | Instances | 2 | 13 | | Keypairs | - | 100 | | Personality | - | 5 | | Personality Size | - | 10240 | | RAM | 1024 | 50176 | | SecurityGroupRules | - | 20 | | SecurityGroups | 1 | 10 | | Server Meta | - | 100 | | ServerGroupMembers | - | 10 | | ServerGroups | 0 | 10 | +--------------------+------+-------+ Have a look at keypair row, in used column it is still 0 but it is not the case. There are total two keypairs created in nova out of which one is used by a VM. For a user to use the API, There is no clue if there are any keypairs created or not. Even If it is created it is used or not. So, I think this API has to be reworked and keypair should have the value two as two keypairs are created in nova. There is also no entry for server metadata items & fixed IPs in the output. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1556756/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
