Expose host capabilities

Registered by Claudiu Belu on 2015-09-10

Ensuring proper scheduling can be difficult task, especially when the instances
require several host features or capabilities. This would require the
administrators to know what features are available for a certain hypervisor
version and / or creating quite a few host aggregates, which can become

Blueprint information

John Garbutt
Claudiu Belu
Needs approval
Claudiu Belu
Pending Approval
Series goal:
Needs Code Review
Milestone target:
Started by
Claudiu Belu

Related branches



Gerrit topic: https://review.openstack.org/#q,topic:bp/s,n,z

Addressed by: https://review.openstack.org/222200
    Adds spec for exposing host capabilities

Gerrit topic: https://review.openstack.org/#q,topic:bp/expose-host-capabilities,n,z

Addressed by: https://review.openstack.org/228279
    Adds HostCapabilities database model and migration

Addressed by: https://review.openstack.org/228280
    Adds HostCapabilities object model

Addressed by: https://review.openstack.org/230812
    Adds host_capabilities CRUD API operations

Addressed by: https://review.openstack.org/250166
    Adds host_capabilities conf options group

Addressed by: https://review.openstack.org/254124
    driver: Adds get_hypervisor_capabilities method

Addressed by: https://review.openstack.org/254125
    WIP: Hyper-V: Adds get_hypervisor_capabilities implementation

Addressed by: https://review.openstack.org/254747
    Adds host_capabilities to HostState

Addressed by: https://review.openstack.org/255073
    WIP: scheduler: Adds host_capabilities filter

Sorry, we have now hit the Non-Priority Feature Freeze for Mitaka. For more details please see: http://docs.openstack.org/releases/schedules/mitaka.html#m-nova-npff and http://docs.openstack.org/developer/nova/process.html#non-priority-feature-freeze
--johnthetubaguy 2016.02.03

Addressed by: https://review.openstack.org/285378
    API: Exposes host capabilities via the nova hypervisor API

Addressed by: https://review.openstack.org/285856
    Adds HostCapabilities object model

Addressed by: https://review.openstack.org/285998
    WIP: scheduler: removes check for supported_instances from filter

Addressed by: https://review.openstack.org/285999
    WIP: drivers: Removes supported_instances from get_available_resource

Addressed by: https://review.openstack.org/286000
    WIP: objects: Removes supported_instances from compute_node

Addressed by: https://review.openstack.org/286001
    WIP: db: Removes supported_instances from compute_node table

Addressed by: https://review.openstack.org/286520
    Repropose expose-host-capabilities to Newton

Addressed by: https://review.openstack.org/322443
    Adds host capabilities related object models

This is likely superseded by the idea in https://review.openstack.org/#/c/538498/ to expose virt driver capabilities as traits on the compute node resource provider which we can then tie in with pre-request placement filters described in https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/placement-req-filter.html - I wonder if I should target that work against this blueprint? -- mriedem 20180313

Gerrit topic: https://review.openstack.org/#q,topic:bp/placement-req-filter,n,z

Addressed by: https://review.openstack.org/538498
    Convert driver supported capabilities to compute node provider traits


Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.