yahoo-eng-team team mailing list archive

[OpenStack Hudson <1129485@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/25692
Committed: http://github.com/openstack/openstack-manuals/commit/cec20446b68f7ab1864117613f37910115178fc2
Submitter: Jenkins
Branch:    master

commit cec20446b68f7ab1864117613f37910115178fc2
Author: Tom Fifield <fifieldt@xxxxxxxxxxxxxx>
Date:   Fri Mar 29 16:11:17 2013 +0800

    note disable ComputeCapabilitiesFilter w baremetal
    
    As noted in the bug report, using ComputeCapabilitiesFilter
    with baremetal deployments breaks things. This patch adds a note
    requesting that users disable it in this scenario.
    
    fixes bug 1129485
    
    Change-Id: I0fb39fc2d2c2255b803502fb83b8d95b7b6188e8


** Changed in: openstack-manuals
       Status: In Progress => 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:
  Fix Released

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