yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1936408@xxxxxxxxxxxxxxxxxx>]

We discussed that RFE on today's drivers meeting https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.2021-08-06-14.03.log.html#l-14 and we all agreed that current behavior is actually a feature and we shouldn't change it. It also aligns with the comment #6 from Brian.
So we decided to reject that RFE.

** Tags removed: rfe-triaged
** Tags added: rfe

** Changed in: neutron
       Status: In Progress => Won't Fix

-- 
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:
  Won't Fix

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