yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1378705] Re: Neutron do not pick up existing physical device bridge

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Tom Fifield <1378705@xxxxxxxxxxxxxxxxxx>
Date: Wed, 08 Oct 2014 09:36:18 -0000
Reply-to: Bug 1378705 <1378705@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

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

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

Title:
  Neutron do not pick up existing physical device bridge

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Manuals:
  New

Bug description:
  Hello

  Maybe this is normal user story, but it is very inconvenient, when I
  have server with already configured bridge and I have to turn off
  network interface, so Neutron can create new one.

  For example I have configured br0 with eth0 port for libvirtd, which has ten virtual machines.
  If I decide to switch to Neutron, I will have to bring all of them down, delete bridge, start neutron, specify new bridge in libvirt network configuration XML. Such process implies big downtime, which is inconvenient.

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