Bug 970996

Prerequisites to test:

Install OpenStack with Neutron enabled and a backend that supports quotas (e.g. openvswitch).

In Horizon's local_settings.py, make sure 'enable_quotas' is set to True and restart httpd.

OPENSTACK_NEUTRON_NETWORK = {
    'enable_quotas': True,
}

What changed:

1. In the Default quotas, Floating IPs and Fixed IPs are not shown anymore (unfortunately, reading the Neutron default quotas via an API is not possible at this stage, so the Neutron quotas cannot be shown (cf. LP#1204956))

2. When updating a Project, the correct quotas coming from Neutron are shown.

3. (Maybe outside the scope of this bug, since the bug title is about showing?) They can also be updated via Modify Quotas via Admin -> Project.


Note this only covers the Floating IPs quotas. Security groups-related Neutron quotas will be handled separately and haven't been fixed upstream yet (cf. LP#1212600).

Also, about #3, if you want to test updates make sure to use a Neutron quota driver that supports updates (e.g. neutron.db.quota_db.DbQuotaDriver, see https://bugs.launchpad.net/neutron/+bug/1189671)

*** Bug 891309 has been marked as a duplicate of this bug. ***

More testing related information:

The places affected are the floating IPs graph on the Overview, the Project Quotas in the admin, and in the default quotas you shouldn't see the IP related quotas (e.g. no fixed IPs), as Neutron doesn't have an API yet for reading default quotas. The floating IP allocation screen in Access & Security also shows the quota.

Other paths interesting to test:

 * Nova-networking and related quotas should still work normally, when Neutron isn't installed

 * Possibly of interest (I don't know if it's one of our supported configurations): testing with a Neutron backend that doesn't support quotas. This can be 'faked' by having Neutron enabled and setting 'enable_quotas' to False. The assumption made here is that no quota support is equivalent to infinite quotas i.e. no limit, and the graphs should reflect this.

Verified NVR: python-django-horizon-2013.2-5.el6ost.noarch

Tested 3 Configurations:

1. Neutron with quotas enabled:
   - Floating IPs graph on Project Overview:
     Visible - Floating IPs Used 0 of 50

   - Project Quotas in the admin tab: 
     Admin Tab --> Projects --> <Project Name> --> Modify Quotas
     Listed network related quotas:
      Security Groups
      Security Group Rules
      Floating IPs
      Networks
      Ports
      Routers
      Subnets

     * Quotas matched to the output of neutron quota-show command.
     * I managed to update the quota via horizon (verified with neutron quota-show via CLI)

   - Default Quotas:
     As expected No IP related quotas are present in the list.

   - Project --> Access & Security --> Floating  IPs --> Allocate IP To Project
     Indication of '50' Available floating IPs is present.


2. Neutron with quotas disabled:
   - Floating IPs graph on Project Overview: 
     Visible - Floating IPs Used 0 of inf

   - Project Quotas in the admin tab:
     Admin Tab --> Projects --> <Project Name> --> Modify Quotas
     Network related quotas are not listed (as expected).

   - Default Quotas:
     As expected No IP related quotas are present in the list.

   - Project --> Access & Security --> Floating  IPs --> Allocate IP To Project
     Indication of 'No Limit' Available floating IPs is present.


3. Nova-Network:
   - Floating IPs graph on Project Overview: 
     Visible - Floating IPs Used 0 of 10

   - Project Quotas in the admin tab:
     Admin Tab --> Projects --> <Project Name> --> Modify Quotas
     Listed network related quotas:
      Floating IPs
      Fixed IPs
      Security Groups
      Security Group Rules

   - Default Quotas:
     Listed network related quotas:
      Fixed IPs
      Security Groups

   - Project --> Access & Security --> Floating  IPs --> Allocate IP To Project
     Indication of '10' Available floating IPs is present.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1859.html