← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1936408] Re: [RFE] Neutron quota change should check available existing resources

 

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/801470
Committed: https://opendev.org/openstack/neutron/commit/5a7a8db0d87c2027287e8fb074ee0f681e6369bb
Submitter: "Zuul (22348)"
Branch:    master

commit 5a7a8db0d87c2027287e8fb074ee0f681e6369bb
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Thu Aug 26 17:55:35 2021 +0000

    Check quota limits
    
    When "check_limit" parameter is passed in a quota update request,
    the Neutron server checks the current resource usage before updating
    the quota limit. If the new quota limit is below the resource usage,
    an exception is raised.
    
    This parameter was added in [1][2].
    
    [1]https://review.opendev.org/c/openstack/openstacksdk/+/806254
    [2]https://review.opendev.org/c/openstack/python-openstackclient/+/806016
    
    Closes-Bug: #1936408
    
    Change-Id: I5a6fb65694498dd7d8f403ea04dc1fe72b8c938d


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1936408

Title:
  [RFE] Neutron quota change should check available existing resources

Status in neutron:
  Fix Released

Bug description:
  Neutron quota change should check available existing resources. This
  is done, for example, in Nova. When a quota resource limit is changed,
  the available resource count is checked first. If the new quota upper
  limit (lower than the previous one) is lower than the amount of
  resources in use, the quota driver should raise an exception.

  This RFE implies a change in the Neutron quota current behaviour. Some
  users are expecting the new quota limit to be applied, regardless of
  being lower than the current resource usage.

  However, other users (Octavia) expect the quota driver to fail when
  lowering the quota limit under the existing resource usage. My
  recommendation is to use a config knob to decide the behaviour of the
  quota driver; by default, the current behaviour will prevail.

  Bugzilla reference:
  https://bugzilla.redhat.com/show_bug.cgi?id=1980728

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



References