nova baremetal requires manual neutron setup for metadata access
Bug #1239481 reported by
Robert Collins
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Invalid
|
Low
|
Unassigned | ||
OpenStack Compute (nova) |
Won't Fix
|
Low
|
Unassigned | ||
neutron |
Expired
|
Undecided
|
Unassigned | ||
tripleo |
Invalid
|
Low
|
Unassigned |
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=
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.
Changed in ironic: | |
status: | New → Confirmed |
Changed in ironic: | |
importance: | Undecided → Medium |
Changed in ironic: | |
importance: | Medium → Undecided |
Changed in ironic: | |
importance: | Undecided → Low |
To post a comment you must log in.
Relatedly, and possibly a different bug - we should be able to use neutron to configure the physical switches to handle 169.254.169.254 correctly and thus handle multi-subnet baremetal clouds trivially.