yahoo-eng-team team mailing list archive

[John Garbutt <john@xxxxxxxxxxxxxxx>]

So the problem here is keypairs are owned by the user, and not owned by
the tenant.

The API you mention lists what a tenant has used, and any limits that
apply to the tenant.

So in this case, the API is saying for every user in the tenant they are
allowed 100 keypairs. In a similar way, every server group is allowed 10
members. In neither case does it make sense to say how much the tenant
has used, because the usage is not related to a tenant.

As such, this bug is invalid.


** Changed in: nova
       Status: In Progress => 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/1580967

Title:
  nova limits does not show keypair count properly

Status in OpenStack Compute (nova):
  Invalid

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