yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1977752@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Related Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2093739

For minimum bandwidth, the OVS agent is create a QoS policy assigned to
the physical bridge interface. Any new port with a min-bw QoS rule will
create a queue attached to this QoS policy. OVS creates the
corresponding "tc" linux-htb policy in the interface, creating a root
class. Each new queue will be represented as a new child class on top of
the parent one (that represents the QoS policy).

The problem we have, as commented in [1], is that we are not providing
any "ceil" value (max-rate) in the parent class or the child ones. If no
"ceil" value is provided, 100Mbits/s will be assigned. Any child class
with a higher "rate" (min-rate) than "ceil" won't be able to set this
value.

[1]https://bugzilla.redhat.com/show_bug.cgi?id=2093739#c1

** 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/1977752

Title:
  [OVS][QoS] Minimum bandwidth backend enforcement does not provide max-
  rate values

Status in neutron:
  Confirmed

Bug description:
  Related Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2093739

  For minimum bandwidth, the OVS agent is create a QoS policy assigned
  to the physical bridge interface. Any new port with a min-bw QoS rule
  will create a queue attached to this QoS policy. OVS creates the
  corresponding "tc" linux-htb policy in the interface, creating a root
  class. Each new queue will be represented as a new child class on top
  of the parent one (that represents the QoS policy).

  The problem we have, as commented in [1], is that we are not providing
  any "ceil" value (max-rate) in the parent class or the child ones. If
  no "ceil" value is provided, 100Mbits/s will be assigned. Any child
  class with a higher "rate" (min-rate) than "ceil" won't be able to set
  this value.

  [1]https://bugzilla.redhat.com/show_bug.cgi?id=2093739#c1

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