Make ComputeCapabilitiesFilter work with Ironic

[OpenStack Infra]

https://review.openstack.org/105802

Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/ironic" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit c30cb24dac3968779d95e2d739705feb48497f3e
Author: Devananda van der Veen <email address hidden>
Date: Wed Jul 9 10:16:27 2014 -0700

    Make ComputeCapabilitiesFilter work with Ironic

    It is not currently possible to selectively associate a Nova flavor
    with certain nodes in Ironic, beyond variances in the cpu/ram/disk.

    The ComputeCapabilitiesFilter exists in Nova for just this purpose,
    but the nova.virt.ironic driver is not propagating the correct
    data up to the scheduler.

    This patch parses the node.properties['capabilities'] as a series of
    comma-separated k:v pairs and passes them up to Nova so that it can
    be matched against flavor.extra_specs['capabilities'] by the
    scheduler filter.

    Co-Author: Matthew Gilliard <email address hidden>
    DocImpact: adds the ability to specify multiple capabilities
               to a node for scheduling purposes
    Closes-bug: 1339816
    Change-Id: Ide39f4a2796b169025bf0083e021166ae35f30f8

[Gauvain Pocentek (gpocentek)]

Ironic is not yet documented.