yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

*** This bug is a duplicate of bug 1186354 ***
    https://bugs.launchpad.net/bugs/1186354

I've marked this as a duplicate against bug 1186354 since there is a lot
of history around that one and it's what we tracked the blueprint for
fixing this against:

https://blueprints.launchpad.net/nova/+spec/limits-quota-usage-from-
neutron

There is ML discussion around that one too, and we have the (now
abandoned but should be resurrected) spec:

https://review.openstack.org/#/c/206735/

** This bug has been marked a duplicate of bug 1186354
   Limits API doesn't work with Neutron

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

Title:
  Nova shouldn't return limits for resources it doesn't manage

Status in OpenStack Compute (nova):
  New

Bug description:
  The various Nova limits APIs return a set of resources:

  nova absolute-limits
  +--------------------+------+-------+
  | Name | Used | Max |
  +--------------------+------+-------+
  | Cores | 2 | 20 |
  | FloatingIps | 0 | 10 |
  | ImageMeta | - | 128 |
  | Instances | 1 | 10 |
  | Keypairs | - | 100 |
  | Personality | - | 5 |
  | Personality Size | - | 10240 |
  | RAM | 4096 | 51200 |
  | SecurityGroupRules | - | 20 |
  | SecurityGroups | 1 | 10 |
  | Server Meta | - | 128 |
  | ServerGroupMembers | - | 10 |
  | ServerGroups | 0 | 10 |
  +--------------------+------+-------+

  The resources that relate to networking are always inaccurate when
  talking to neutron. When "use_neutron" is in effect, we should
  probably not return information about Neutron limits, as they are
  always inaccurate, and the nova limits should only be used to address
  limits enforced by nova.

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