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: OpenStack Infra <1416444@xxxxxxxxxxxxxxxxxx>
Date: Tue, 16 Jun 2015 19:44:41 -0000
Reply-to: Bug 1416444 <1416444@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Reviewed:  https://review.openstack.org/159885
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=d4c89289f9d4bf88c065dca85a46c9b08464b56c
Submitter: Jenkins
Branch:    master

commit d4c89289f9d4bf88c065dca85a46c9b08464b56c
Author: Waldemar Znoinski <waldemar.znoinski@xxxxxxxxx>
Date:   Thu May 7 17:14:21 2015 +0100

    Set datapath to $OVS_DATAPATH_TYPE for bridges
    
    This change extends devstack to configure the br-ex,
    br-<phy> and Xenserver's br-$GUEST_INTERFACE_DEFAULT
    datapaths when OVS_DATAPATH_TYPE is set.
    
    Change-Id: I71e590de86e7526e8423140463752d6b3ad14214
    Closes-Bug: #1416444


** Changed in: devstack
       Status: In Progress => Fix Released

-- 
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):
  New

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