yahoo-eng-team team mailing list archive

[Rodolfo Alonso <2115952@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Since [1], the enforcement of the QoS rules in a port located in a
physical network (VLAN, flat) and egress rules, is done in the physical
interface of the physical network bridge.

That patch allowed to have min-bw rules in ML2/OVS. However, that
introduces a regression in some scenarios. For example, when max-bw
*only* QoS policies are used and the physical bridge is connected to a
bond interface. In this case, OVS cannot apply the TC commands to the
multiple interfaces that participate in the bond.

The goal of this bug is to partially revert this behaviour. If we have
QoS policies with max-bw only (it is important this observation, the QoS
policy must have only max-bw rules), the ML2/OVS extension should use
the OVN policer to enforce the BW limit.

I'm setting the importance to "medium", because this is indeed a bug
(regression) but for a very specific scenario.

[1]https://review.opendev.org/c/openstack/neutron/+/934418

Jira reference: https://issues.redhat.com/browse/OSPRH-18010

** Affects: neutron
     Importance: Low
         Status: New

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

** Description changed:

  Since [1], the enforcement of the QoS rules in a port located in a
  physical network (VLAN, flat) and egress rules, is done in the physical
  interface of the physical network bridge.
  
  That patch allowed to have min-bw rules in ML2/OVS. However, that
  introduces a regression in some scenarios. For example, when max-bw
  *only* QoS policies are used and the physical bridge is connected to a
  bond interface. In this case, OVS cannot apply the TC commands to the
  multiple interfaces that participate in the bond.
  
  The goal of this bug is to partially revert this behaviour. If we have
  QoS policies with max-bw only (it is important this observation, the QoS
  policy must have only max-bw rules), the ML2/OVS extension should use
  the OVN policer to enforce the BW limit.
  
+ I'm setting the importance to "medium", because this is indeed a bug
+ (regression) but for a very specific scenario.
+ 
  [1]https://review.opendev.org/c/openstack/neutron/+/934418
+ 
+ Jira reference: https://issues.redhat.com/browse/OSPRH-18010

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

Title:
  [OVN][QoS] Allow max-bw only QoS policies to use the OVN policer

Status in neutron:
  New

Bug description:
  Since [1], the enforcement of the QoS rules in a port located in a
  physical network (VLAN, flat) and egress rules, is done in the
  physical interface of the physical network bridge.

  That patch allowed to have min-bw rules in ML2/OVS. However, that
  introduces a regression in some scenarios. For example, when max-bw
  *only* QoS policies are used and the physical bridge is connected to a
  bond interface. In this case, OVS cannot apply the TC commands to the
  multiple interfaces that participate in the bond.

  The goal of this bug is to partially revert this behaviour. If we have
  QoS policies with max-bw only (it is important this observation, the
  QoS policy must have only max-bw rules), the ML2/OVS extension should
  use the OVN policer to enforce the BW limit.

  I'm setting the importance to "medium", because this is indeed a bug
  (regression) but for a very specific scenario.

  [1]https://review.opendev.org/c/openstack/neutron/+/934418

  Jira reference: https://issues.redhat.com/browse/OSPRH-18010

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