[Yahoo-eng-team] [Bug 1580967] [NEW] nova limits does not show keypair count properly
Public bug reported: The keypair count with nova limits is the number of keypairs associated with the VMs, But it has to be number of keypair created for that tenant regardless of it is being used or not. $ nova limits ++--+---+ | Name | Used | Max | ++--+---+ | Cores | 0| 20| | FloatingIps| 0| 10| | ImageMeta | -| 128 | | Instances | 0| 10| | Keypairs | -| 100 | | Personality| -| 5 | | Personality Size | -| 10240 | | RAM| 0| 51200 | | SecurityGroupRules | -| 20| | SecurityGroups | 0| 10| | Server Meta| -| 128 | | ServerGroupMembers | -| 10| | ServerGroups | 0| 10| ++--+---+ There is a keypair created though it is not associated with any instance, It has to be counted when we do nova limits as for nova it is used. $nova keypair-list | Name | Type | Fingerprint | +--+--+-+ | test | ssh | c8:e8:3e:8f:98:89:18:90:80:c5:55:f9:21:49:59:d9 | +--+--+-+ The reverse happens for security groups, For security groups It is the number of security groups created in nova regardless of it is used or not. Which I feel is expected behaviour. ** Affects: nova Importance: Undecided Assignee: Ashish Singh (ashish-singh7) Status: Confirmed ** Changed in: nova Assignee: (unassigned) => Ashish Singh (ashish-singh7) -- 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/1580967 Title: nova limits does not show keypair count properly Status in OpenStack Compute (nova): Confirmed Bug description: The keypair count with nova limits is the number of keypairs associated with the VMs, But it has to be number of keypair created for that tenant regardless of it is being used or not. $ nova limits ++--+---+ | Name | Used | Max | ++--+---+ | Cores | 0| 20| | FloatingIps| 0| 10| | ImageMeta | -| 128 | | Instances | 0| 10| | Keypairs | -| 100 | | Personality| -| 5 | | Personality Size | -| 10240 | | RAM| 0| 51200 | | SecurityGroupRules | -| 20| | SecurityGroups | 0| 10| | Server Meta| -| 128 | | ServerGroupMembers | -| 10| | ServerGroups | 0| 10| ++--+---+ There is a keypair created though it is not associated with any instance, It has to be counted when we do nova limits as for nova it is used. $nova keypair-list | Name | Type | Fingerprint | +--+--+-+ | test | ssh | c8:e8:3e:8f:98:89:18:90:80:c5:55:f9:21:49:59:d9 | +--+--+-+ The reverse happens for security groups, For security groups It is the number of security groups created in nova regardless of it is used or not. Which I feel is expected behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1580967/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [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
{"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
- {"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
{"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 | -
[Yahoo-eng-team] [Bug 1477576] Re: No option to delete(reset to default) specific resources with nova quota delete
** Project changed: nova-hyper = nova -- 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/1477576 Title: No option to delete(reset to default) specific resources with nova quota delete Status in OpenStack Compute (nova): New Bug description: Hi All, There is no command in nova(or any other service) to delete specific resource. Nova quota delete command takes only project Id and resets all the resources corresponding to the service. Suppose I have updated ram to , vcpus to 10, cores to 5. Now after few days I want to reset ram and vcpus to default then i have to update ram and vcpus to default using nova quota update. If I do nova quota delete, there is no option to mention these resources(it takes only project_id). It will delete/reset all the resources for that project. I feel If nova quota delete also provides option to mention which resource to delete(reset to default) then it would be better. Thanks, Ashish. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1477576/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1411625] [NEW] Keystone not throwing any exception when there is no proper OS credentails.
Public bug reported: When we miss any of the environment variable, Keystone commands do not throw any error, it just simply output nothing. But when when we run nova command it outputs proper error message. So similarly even keystone should throw appropriate error message when any of the environment variable is missing. Steps to reproduce. root@ubuntu:~# unset OS_TENANT_NAME root@ubuntu:~# keystone user-list root@ubuntu:~# nova list ERROR (CommandError): You must provide a tenant name or tenant id via --os-tenant-name, --os-tenant-id, env[OS_TENANT_NAME] or env[OS_TENANT_ID] root@ubuntu:~# ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1411625 Title: Keystone not throwing any exception when there is no proper OS credentails. Status in OpenStack Identity (Keystone): New Bug description: When we miss any of the environment variable, Keystone commands do not throw any error, it just simply output nothing. But when when we run nova command it outputs proper error message. So similarly even keystone should throw appropriate error message when any of the environment variable is missing. Steps to reproduce. root@ubuntu:~# unset OS_TENANT_NAME root@ubuntu:~# keystone user-list root@ubuntu:~# nova list ERROR (CommandError): You must provide a tenant name or tenant id via --os-tenant-name, --os-tenant-id, env[OS_TENANT_NAME] or env[OS_TENANT_ID] root@ubuntu:~# To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1411625/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
