← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 897095] Re: Nova doesn't support bridge on bonded interfaces

 

Is this still valid?

** Changed in: nova
       Status: Confirmed => Invalid

** Changed in: nova
       Status: Invalid => Incomplete

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/897095

Title:
  Nova doesn't support bridge on bonded interfaces

Status in OpenStack Compute (Nova):
  Incomplete

Bug description:
  I setup a bonding network. 
  so, I modified a my nova.conf.
  --flat_interface=bond1
  --fixed_range=10.101.0.0/16

  When I execute 'nova-network', nova-network make a bridge(br100)

  nova@cn2:/$ ifconfig bond1
  bond1     Link encap:Ethernet  HWaddr 10:1f:74:2b:89:3c
            inet6 addr: fe80::121f:74ff:fe2b:893c/64 Scope:Link
            UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
            RX packets:14538 errors:0 dropped:370 overruns:0 frame:0
            TX packets:3353 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0
            RX bytes:1125692 (1.1 MB)  TX bytes:210490 (210.4 KB)

  nova@cn2:/$ ifconfig br100
  br100     Link encap:Ethernet  HWaddr 10:1f:74:2b:89:3c
            inet addr:10.101.0.6  Bcast:10.101.1.255  Mask:255.255.254.0
            inet6 addr: fe80::acd0:d6ff:fe13:e495/64 Scope:Link
            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
            RX packets:3254 errors:0 dropped:38 overruns:0 frame:0
            TX packets:352 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0
            RX bytes:170306 (170.3 KB)  TX bytes:28092 (28.0 KB)

  then, I try to pinging to other compute node. but It can't connect.

  In my search result, It maybe ARP problem for bridge on a bonded interface.
  http://ubuntuforums.org/showthread.php?t=835732

  There are some solutions for this problem by turn on stp for bridge.

  nova@cn2:/$ sudo brctl stp br100 on

  after that command, ping to other compute node is success.


  And I found nova source code about create a bride.
  It's in 'nova/network/linux_net.py', I commented a source for stp option.

   949         if not _device_exists(bridge):
   950             LOG.debug(_('Starting Bridge interface for %s'), interface)
   951             _execute('brctl', 'addbr', bridge, run_as_root=True)
   952             _execute('brctl', 'setfd', bridge, 0, run_as_root=True)
   953             # _execute('brctl setageing %s 10' % bridge, run_as_root=True)
   954             #commented by jslee
   955             #_execute('brctl', 'stp', bridge, 'off', run_as_root=True)
   956             _execute('brctl', 'stp', bridge, 'on', run_as_root=True)
   957             # (danwent) bridge device MAC address can't be set directly.
   958             # instead it inherits the MAC address of the first device on the
   959             # bridge, which will either be the vlan interface, or a
   960             # physical NIC.
   961             _execute('ip', 'link', 'set', bridge, 'up', run_as_root=True)

  A genuine source is turn off a stp option, Are there some reason to
  turn off stp option?

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