← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1417595] Re: Bare metal ports cannot be mapped to networks

 

duplicate of https://bugs.launchpad.net/nova/+bug/1405131

** Changed in: nova
       Status: New => 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/1417595

Title:
  Bare metal ports cannot be mapped to networks

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  See https://bugs.launchpad.net/ironic/+bug/1405131 for an equivalent
  bug in ironic that describes the issue.

  The bug itself resides in nova, but requires cooperation from ironic
  in order to fix it.

  I have attached a patch that we are using internally to resolve the
  issue. It requires that ironic ports are tagged with the name of the
  'physical_network' to which they are attached. The name maps directly
  to neutron's 'provider:physical_network' network property. The tag is
  added as a key/value in the ironic ports' 'extra' metadata.

  The nova patch requires some further work before submission as it is a
  little hairy in places. In particular, the return value for
  macs_for_instance really deserves it's own type, representing the
  physical ports. Perhaps this would actually be better as a new method
  entirely as the name no longer fully describes the method.

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


References