yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #47982
[Bug 1556756] [NEW] nova limits does not show correct quota usage
Public bug reported:
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.
Same is the case with security group.
** Affects: nova
Importance: Undecided
Status: New
** Description changed:
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,
+ {"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.
+
+ Same is the case with security group.
--
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):
New
Bug description:
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.
Same is the case with security group.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1556756/+subscriptions
Follow ups