yahoo-eng-team team mailing list archive

[John Davidge <john.davidge@xxxxxxxxxxxxx>]

Devref docs were included with the patch, but references to the removed
config options will need to be removed from the config-guide:

https://github.com/openstack/openstack-manuals/blob/master/doc/config-
reference/source/tables/neutron-qos.rst

** Also affects: openstack-manuals
   Importance: Undecided
       Status: New

** Tags added: config-reference

** Changed in: openstack-manuals
       Status: New => Confirmed

** Changed in: openstack-manuals
   Importance: Undecided => Medium

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

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

Title:
      Linux Bridge: driver support for QoS egress minimum bandwidth

Status in neutron:
  Invalid
Status in openstack-manuals:
  Confirmed

Bug description:
  https://review.openstack.org/357865
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 84b3ae3ae9111e241352bdccad238c9fd37b83df
  Author: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@xxxxxxxxx>
  Date:   Tue Aug 16 08:50:35 2016 +0100

      Linux Bridge: driver support for QoS egress minimum bandwidth
      
      This patch provides the Linux Bridge agent driver the ability to control
      Linux Traffic Control (TC) to set the minimum required transmission rate
      for an interface.
      
      The TC library is refactored to use HTB qdiscs. This allows TC to
      define, for several flows in the same interface, the maximum and the
      minimum network bandwidth and the burst size.
      
      To be able to do traffic shaping (instead of policing) for ingress
      traffic, a new element, the Intermediate Functional Block device (IFB)
      is introduced.
      
      DocImpact
      Partial-Bug: #1560963
      
      Change-Id: I4d4db54519f1435068d1af38819404d1e5d9cd52

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