yahoo-eng-team team mailing list archive

[Vish Ishaya <vishvananda@xxxxxxxxx>]

The code is correct. The flag is used as an override so that one can
have heterogeneous nodes where the public_interface is different across
nodes.  For example:

Node 1:
  public_interface=eth0

Node 2:
  public_interface=eth1

If you want to use the interface from the database do not set
public_interface. That is why it defaults to None.

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

-- 
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/1089709

Title:
  floating ip association doesn't correctly assigned to interface
  specified

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  nova-network specific: [unknown if effects quantum] 
  Folsom: [looks to effect Grizzly as well]

  When creating floating IP pools, an interface is able to be specified.
  However, when associating the floating IP to an instance it doesn't
  get assigned to the correct interface. Due to the logic in the code,
  nova will decide to associate the floating IP the interface that is
  set as the FLAG public_interface over the interface that is specified
  when the pool is created.

  It would make more sense to switch the order of operations from "FLAG
  or database setting" to "database setting or FLAG" considering the
  database setting is more specific.

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