yahoo-eng-team team mailing list archive

[Mark McClain <1288641@xxxxxxxxxxxxxxxxxx>]

aliases are for addressing... the underlying device is still the same.
The proper way to simulate multiple external networks is to create a
bridge and use tap devices

** Changed in: neutron
       Status: In Progress => 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/1288641

Title:
  ethernet name parsing doesn't support ethernet alias

Status in OpenStack Neutron (virtual network service):
  Won't Fix

Bug description:
  I set up a testbed for Neutron ML2 LinuxBridge. I'd like to set two external networks which is implemented by ethernet alias:
  eth0:0 and eth0:1. I bind the ethernet name to provider network: phynet1 and phynet2. However, it is not working.

  The LinuxBridge agent is terminated and throws an exception:
  2014-03-06 16:41:48.675 6793 ERROR neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent [-] Parsing physical_interface_mappings failed: Invalid mapping: 'phynet1:eth0:0'. Agent terminated!

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