yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1959567@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

According to the OVS faq https://docs.openvswitch.org/en/latest/faq/qos/

Q: I configured Quality of Service (QoS) in my OpenFlow network by adding
   records to the QoS and Queue table, but the results aren’t what I expect.

A: Did you install OpenFlow flows that use your queues? This is the primary
   way to tell Open vSwitch which queues you want to use. If you don’t do this,
   then the default queue will be used, which will probably not have the effect
   you want.


According to info from the OVS developer, Ilya Maximets "OVS doesn't define what the "default queue" is. [...] So, using the set_queue action is a correct way to configure QoS, even if the queue 0 is currently a "default queue".  It's not guaranteed that it always will be."

Because of that Neutron OVS agent should configure correct OF rules to
send traffic to the required QoS queue always.

** Affects: neutron
     Importance: Medium
     Assignee: Slawek Kaplonski (slaweq)
         Status: Confirmed


** Tags: ovs qos

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

Title:
  QoS Ingress bandwidth limit with OVS backend may not work as expected

Status in neutron:
  Confirmed

Bug description:
  According to the OVS faq
  https://docs.openvswitch.org/en/latest/faq/qos/

  Q: I configured Quality of Service (QoS) in my OpenFlow network by adding
     records to the QoS and Queue table, but the results aren’t what I expect.

  A: Did you install OpenFlow flows that use your queues? This is the primary
     way to tell Open vSwitch which queues you want to use. If you don’t do this,
     then the default queue will be used, which will probably not have the effect
     you want.

  
  According to info from the OVS developer, Ilya Maximets "OVS doesn't define what the "default queue" is. [...] So, using the set_queue action is a correct way to configure QoS, even if the queue 0 is currently a "default queue".  It's not guaranteed that it always will be."

  Because of that Neutron OVS agent should configure correct OF rules to
  send traffic to the required QoS queue always.

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