Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-18011

QoS policies with max bandwidth only not enforced for physical network

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • rhos-18.0.6
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      .QoS policies not enforced when only maximum bandwidth (egress) rules present, on ports in physical networks, when the physical interface is a bond

      A port connected to a physical network (VLAN, flat), with maximum-bandwidth-only QoS rules and egress direction uses the physical network interface to enforce the QoS rule, via TC commands.

      In previous versions, Neutron enforced the bandwidth limit rule using the OVN policer, regardless of the network type and rule direction.

      Now, starting with RHOSO 18.0.6, if the environment uses a bond to connect the physical bridge to the physical network, there will be no QoS enforcement. For more information, see https://issues.redhat.com/browse/OSPRH-18010.
      Show
      .QoS policies not enforced when only maximum bandwidth (egress) rules present, on ports in physical networks, when the physical interface is a bond A port connected to a physical network (VLAN, flat), with maximum-bandwidth-only QoS rules and egress direction uses the physical network interface to enforce the QoS rule, via TC commands. In previous versions, Neutron enforced the bandwidth limit rule using the OVN policer, regardless of the network type and rule direction. Now, starting with RHOSO 18.0.6, if the environment uses a bond to connect the physical bridge to the physical network, there will be no QoS enforcement. For more information, see https://issues.redhat.com/browse/OSPRH-18010 .
    • Known Issue
    • Proposed

      Since [1][2], the QoS rules of a port in a physical network and egress direction, are defined in the physical interface. This is a problem in environments with a bond interface because the TC commands won't have any effect.

      This is a regression from 17.1. In this version, only max-bw rules were possible. The BW QoS enforcement was done inside OVS (OVN policers), instead of trying to do the enforcement in the physical interface. This is a regression that needs to be documented, for any deployment up to 18.0.8.

       

      [1]https://issues.redhat.com/browse/OSPRH-11045

      [2]https://gitlab.cee.redhat.com/eng/openstack/neutron/-/merge_requests/11

       

              jamsmith@redhat.com James Smith
              rodolfo_alonso Rodolfo Alonso
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: