ComputeCapabilitiesFilter does not play well with baremetal driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
aeva black | ||
devstack |
Fix Released
|
Undecided
|
aeva black | ||
openstack-manuals |
Fix Released
|
Medium
|
Tom Fifield |
Bug Description
When using the baremetal driver and the default nova scheduler filters, the scheduler will always fail to find a suitable host.
In order to provision baremetal instances, a separate deploy kernel & ramdisk are used. These may be specified on the flavor (instance_type) extra_specs so that an environment may support different deployment processes (eg, for multiple arch support). However, the ComputeCapabili
The simple workaround for this is to disable the ComputeCapabili
tags: | added: baremetal |
Changed in nova: | |
assignee: | nobody → Devananda van der Veen (devananda) |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → grizzly-rc1 |
Changed in openstack-manuals: | |
status: | New → Confirmed |
milestone: | none → grizzly |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in openstack-manuals: | |
assignee: | nobody → Tom Fifield (fifieldt) |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
It sounds like the baremetal driver is using instance_type extra_specs differently than the rest of nova and that is the bug here. What are your thoughts on fixing this to avoid the brute force workaround?