yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

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

Title:
  ComputeCapabilitiesFilter does not play well with baremetal driver

Status in devstack - openstack dev environments:
  Fix Released
Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Manuals:
  Confirmed

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
  ComputeCapabilitiesFilter will not match the instance_type to any
  compute host that is not publishing all of the same extra_specs, and
  in the baremetal case, none of the compute hosts publish these
  deploy_kernel / deploy_ramdisk specs (precisely because they are
  properties of the flavor, not the compute host).

  The simple workaround for this is to disable the
  ComputeCapabilitiesFilter, while leaving all other default filters
  enabled.

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