[Bug 1376316] Re: nova absolute-limits floating ip count is incorrect in a neutron based deployment

[Marian Horban]

The root cause of this problem is that we have different quota drivers for nova and for neutron. These quota drivers could use different DB tables. 
When we run command
    nova absolute-limits
nova uses it own quota driver. But when we allocate floating ip neutron's quota driver is used to decide if quota is exceeded.
Right now in nova we using nova quota driver directly nova/api/openstack/compute/contrib/used_limits.py:
    quotas = QUOTAS.get_project_quotas(context, project_id, usages=True)
This is not correct behavior for parameters like totalFloatingIpsUsed.
Interface class NetworkAPI(nova/network/base_api.py) should be used to get info about network configuration. Method NetworkAPI::get_floating_ips_by_project() clould be used to get totalFloatingIpsUsed parameter.
To return of maxTotalFloatingIps parameter I suppose additional method should be added in NetworkAPI class. Something like
    get_floating_ip_quota()
This method should be implemented for nova-network and for neutron.

** Changed in: nova
       Status: New => Confirmed

** Changed in: nova
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1376316

Title:
  nova absolute-limits floating ip count is incorrect in a neutron based
  deployment

Status in OpenStack Compute (nova):
  Confirmed
Status in nova package in Ubuntu:
  Triaged

Bug description:
  1.
  $ lsb_release -rd
  Description:	Ubuntu 14.04 LTS
  Release:	14.04

  2.
  $ apt-cache policy python-novaclient 
  python-novaclient:
    Installed: 1:2.17.0-0ubuntu1
    Candidate: 1:2.17.0-0ubuntu1
    Version table:
   *** 1:2.17.0-0ubuntu1 0
          500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
          100 /var/lib/dpkg/status

  3. nova absolute-limits should report the correct value of allocated floating ips
  4. nova absolute-limits shows 0 floating ips when I have 5 allocated

  $ nova absolute-limits | grep Floating
  | totalFloatingIpsUsed    | 0      |
  | maxTotalFloatingIps     | 10     |

  $ nova floating-ip-list
  +---------------+-----------+------------+---------+
  | Ip            | Server Id | Fixed Ip   | Pool    |
  +---------------+-----------+------------+---------+
  | 10.98.191.146 |           | -          | ext_net |
  | 10.98.191.100 |           | 10.5.0.242 | ext_net |
  | 10.98.191.138 |           | 10.5.0.2   | ext_net |
  | 10.98.191.147 |           | -          | ext_net |
  | 10.98.191.102 |           | -          | ext_net |
  +---------------+-----------+------------+---------+

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python-novaclient 1:2.17.0-0ubuntu1
  ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Oct  1 15:19:08 2014
  Ec2AMI: ami-00000001
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-00000002
  Ec2Ramdisk: ari-00000002
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: python-novaclient
  UpgradeStatus: No upgrade log present (probably fresh install)

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