yahoo-eng-team team mailing list archive

[Rodolfo Alonso <2092278@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When the LS QoS rules are updated or deleted, there are tow different methods to add or remove them. Instead of this, we should be able to call a single method (``qos_update`` for example) with the needed parameters (same as ``qos_add``).
* If the QoS register does not exist, it is created as is now with the parameters provided.
* If the QoS register exists:
** If any rule type (rate, burst, dscp) is missing in the update call, it will be removed from the QoS register.
** If any rule type is new, compared to the existing QoS register, it will be added (as is now).

** Affects: neutron
     Importance: Medium
     Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
         Status: Confirmed

** Changed in: neutron
   Importance: Undecided => Medium

** Changed in: neutron
     Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)

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

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

Title:
  [OVN] QoS extension, implement a NB ``qos_update`` method

Status in neutron:
  Confirmed

Bug description:
  When the LS QoS rules are updated or deleted, there are tow different methods to add or remove them. Instead of this, we should be able to call a single method (``qos_update`` for example) with the needed parameters (same as ``qos_add``).
  * If the QoS register does not exist, it is created as is now with the parameters provided.
  * If the QoS register exists:
  ** If any rule type (rate, burst, dscp) is missing in the update call, it will be removed from the QoS register.
  ** If any rule type is new, compared to the existing QoS register, it will be added (as is now).

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