yahoo-eng-team team mailing list archive

[Jim Rollenhagen <jim@xxxxxxxxxxxxxxxxxx>]

While this is an ironic-specific problem, I don't believe the fix here
is in ironic.

Seems that Neutron and/or ML2 mechanisms need to set a proper route for
this in the physical switch, but I'm not sure which layer that would be
in. (I assume usually the agent on the host does it)

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1239481

Title:
  nova baremetal requires manual neutron setup for metadata access

Status in Ironic:
  Invalid
Status in neutron:
  Expired
Status in OpenStack Compute (nova):
  Won't Fix
Status in tripleo:
  Incomplete

Bug description:
  a subnet setup with host routes can use a bare metal gateway as long as there is a metadata server on the same network:
  neutron subnet-create ... (network, dhcp settings etc) ----host_routes type=dict list=true destination=169.254.169.254/32,nexthop=<nova metadata server> --gateway_ip=<actual gateway>

  But this requires manual configuration - it would be nice if nova
  could configure this as part of bringing up the network for a given
  node.

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