← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1370202] [NEW] nova absolute-limits does not work for tenant name

 

Public bug reported:

For example, the 'nova absolute-limits' will return different values
about used resources, with tenant name vs. tenant uuid.

nova absolute-limits --tenant vm-ops.us
+-------------------------+-------+
| Name                    | Value |
+-------------------------+-------+
| maxServerMeta           | 128   |
| maxPersonality          | 5     |
| maxImageMeta            | 128   |
| maxPersonalitySize      | 10240 |
| maxTotalRAMSize         | 12288 |
| maxSecurityGroupRules   | 20    |
| maxTotalKeypairs        | 100   |
| totalRAMUsed            | 0     |
| maxSecurityGroups       | 10    |
| totalFloatingIpsUsed    | 0     |
| totalInstancesUsed      | 0     |
| totalSecurityGroupsUsed | 0     |
| maxTotalFloatingIps     | 10    |
| maxTotalInstances       | 5     |
| totalCoresUsed          | 0     |
| maxTotalCores           | 6     |
+-------------------------+-------+

nova absolute-limits --tenant 6cee87e860224b038af979ce3bdac656
+-------------------------+-------+
| Name                    | Value |
+-------------------------+-------+
| maxServerMeta           | 128   |
| maxPersonality          | 5     |
| maxImageMeta            | 128   |
| maxPersonalitySize      | 10240 |
| maxTotalRAMSize         | 51200 |
| maxSecurityGroupRules   | 20    |
| maxTotalKeypairs        | 100   |
| totalRAMUsed            | 6144  |
| maxSecurityGroups       | 10    |
| totalFloatingIpsUsed    | 0     |
| totalInstancesUsed      | 3     |
| totalSecurityGroupsUsed | 1     |
| maxTotalFloatingIps     | 10    |
| maxTotalInstances       | 10    |
| totalCoresUsed          | 3     |
| maxTotalCores           | 20    |
+-------------------------+-------+

This is for nova 2014.1.2.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1370202

Title:
  nova absolute-limits does not work for tenant name

Status in OpenStack Compute (Nova):
  New

Bug description:
  For example, the 'nova absolute-limits' will return different values
  about used resources, with tenant name vs. tenant uuid.

  nova absolute-limits --tenant vm-ops.us
  +-------------------------+-------+
  | Name                    | Value |
  +-------------------------+-------+
  | maxServerMeta           | 128   |
  | maxPersonality          | 5     |
  | maxImageMeta            | 128   |
  | maxPersonalitySize      | 10240 |
  | maxTotalRAMSize         | 12288 |
  | maxSecurityGroupRules   | 20    |
  | maxTotalKeypairs        | 100   |
  | totalRAMUsed            | 0     |
  | maxSecurityGroups       | 10    |
  | totalFloatingIpsUsed    | 0     |
  | totalInstancesUsed      | 0     |
  | totalSecurityGroupsUsed | 0     |
  | maxTotalFloatingIps     | 10    |
  | maxTotalInstances       | 5     |
  | totalCoresUsed          | 0     |
  | maxTotalCores           | 6     |
  +-------------------------+-------+

  nova absolute-limits --tenant 6cee87e860224b038af979ce3bdac656
  +-------------------------+-------+
  | Name                    | Value |
  +-------------------------+-------+
  | maxServerMeta           | 128   |
  | maxPersonality          | 5     |
  | maxImageMeta            | 128   |
  | maxPersonalitySize      | 10240 |
  | maxTotalRAMSize         | 51200 |
  | maxSecurityGroupRules   | 20    |
  | maxTotalKeypairs        | 100   |
  | totalRAMUsed            | 6144  |
  | maxSecurityGroups       | 10    |
  | totalFloatingIpsUsed    | 0     |
  | totalInstancesUsed      | 3     |
  | totalSecurityGroupsUsed | 1     |
  | maxTotalFloatingIps     | 10    |
  | maxTotalInstances       | 10    |
  | totalCoresUsed          | 3     |
  | maxTotalCores           | 20    |
  +-------------------------+-------+

  This is for nova 2014.1.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370202/+subscriptions


Follow ups

References