[RFE] Limits and Counts for SecGroup and FIPs

Bug #1632877 reported by Ankur
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Triaged
Wishlist
Prince Nana Owusu Boateng

Bug Description

[Problem]

As stated in recently submitted bug to OpenStack Client:
OpenStack limits --absolute shows wrong count for 'totalSecurityGroupsUsed'. Despite creating multiple security groups still, the count shows as 1.

openstack security group create <name> uses neutron API to create security group
openstack limits show --absolute fetches the information from nova api. Since nova-network has been deprecated and current devstack installation runs with neutron as default, it's better to change the way how how openstack limits show fetches its information

[Proposal]

Similar to Mitaka feature of IP Capacity. Provide an admin only feature to return the number of Security Groups, Security Group Rules, Floating IPs used and their absolute limits.

[References]
Original OSC bug
https://bugs.launchpad.net/python-openstackclient/+bug/1632460

Paste of difference in nova limits support.
http://paste.openstack.org/show/585516/

Paste sample return of "openstack limits show --absolute"
http://paste.openstack.org/show/585518/

Tags: rfe-approved
Ankur (ankur-gupta-f)
Changed in neutron:
assignee: nobody → Ankur (ankur-gupta-f)
summary: - Limits and Counts for SecGroup and FIPs
+ [RFE] Limits and Counts for SecGroup and FIPs
tags: added: rfe
description: updated
Changed in neutron:
importance: Undecided → Wishlist
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

We seem to already track the needed data in QuotaUsage sqla model (per project_id; we would need to aggregate the data to provide absolute data). The proposal is to expose that data through API, and make OSC use it.

Is it correct?

Revision history for this message
Ankur (ankur-gupta-f) wrote :

Ihar: correct, for FIPs SecGroup, SecGroupRules

Revision history for this message
Kevin Benton (kevinbenton) wrote :

We need to be careful with using the QuotaUsage model. IIRC, it has a concept of 'dirty' that indicates the data is stale and needs to be recalculated. I think rather than query it directly, we should ask the quota engine itself to give us this info which can correctly trigger recalculations.

I think this should just be implemented as a general quota usage API. The request has come up in that context before. So expanding the existing API to return usage should cover this.

Changed in neutron:
status: New → Confirmed
Ankur (ankur-gupta-f)
Changed in neutron:
assignee: Ankur (ankur-gupta-f) → nobody
Changed in neutron:
assignee: nobody → Prince Nana Owusu Boateng (nanaboat)
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This sounds like an effort aimed at closing the OSC gap as well.

Changed in neutron:
status: Confirmed → Triaged
Revision history for this message
Ankur (ankur-gupta-f) wrote :

OSC, but also can help Horizon and their effort to improve how they handle Quotas

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
Changed in neutron:
milestone: none → pike-1
tags: added: rfe-approved
removed: rfe
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
Changed in neutron:
milestone: pike-1 → pike-2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.