yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1416444] Re: PUBLIC and PHYSICAL BRIDGE should use same datapath as INTEGRATION bridge

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Sergey Vilgelm <svilgelm@xxxxxxxxxxxx>
Date: Wed, 17 Jun 2015 09:51:14 -0000
Reply-to: Bug 1416444 <1416444@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug is related to devstack.

** 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/1416444

Title:
  PUBLIC and PHYSICAL BRIDGE should use same datapath as INTEGRATION
  bridge

Status in devstack - openstack dev environments:
  Fix Released
Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  Currently only INTEGRATION (br-int) BRIDGE is set to datapath
  specified in $OVS_DATAPATH_TYPE. Having PUBLIC(br-ex) and PHYSICAL(br-
  phys) bridges on a different datapath will prevent them to communicate
  with  INTEGRATION bridge via patchports. Also, when using 'netdev'
  datapath for all bridges dependency on 'openvswitch' kernel module is
  removed.

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