yahoo-eng-team team mailing list archive

[Alexandra Settle <a.settle@xxxxxxxxxxx>]

** Also affects: neutron
   Importance: Undecided
       Status: New

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

** Changed in: openstack-manuals
       Status: Triaged => Won't Fix

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

Title:
  Scenario: Provider networks with Linux bridge in Networking Guide

Status in neutron:
  Confirmed
Status in openstack-manuals:
  Won't Fix

Bug description:
  Not so much a bug than feedback. The page is not clear whether each
  node has a single Linux Bridge or several. Somebody with good
  networking skills might consider this common knowledge, but if you are
  not that versed in the field of datacenter networking (I am certainly
  not), you may be a bit lost. At some point, the page talks about the
  Linux Bridge Agent managing "switches" (plural; and why "switches" and
  not "bridges"?), but elsewhere there is only talk about one bridge
  named qbr (and sometimes brq. Better name it consistently!).

  I suggest the following change:
  - make it clear that there is one bridge per provider network, not a single bridge per compute and control node. Or am I wrong? (see, I am confused!)
  And these minor changes:
  - label the bridges consistently
  - if you call Linux Bridges "switches", explain why

  -----------------------------------
  Release: 0.9 on 2016-05-25 13:08
  SHA: 0671dca2730c636eaaca64f3880513bf7242e4b4
  Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/networking-guide/source/scenario-provider-lb.rst
  URL: http://docs.openstack.org/mitaka/networking-guide/scenario-provider-lb.html

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