Bug 1041271

Summary: [RFE][nova]: Group baremetal nodes for scheduling
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/grouping-baremetal-nodes-for-scheduling
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_drafting
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:50:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 14:13:30 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/grouping-baremetal-nodes-for-scheduling.

Description:

Right now in Nova we have a way to determine which machines or groups of machines to send instance boot requests using host aggregates.  This works by creating a host aggregate in nova and registering nova service hosts with this host aggregate. matching data in key:value form can be added to things like flavors and host aggregates.  The scheduler can then pick this up and determine where to send instance boot requests.

This method of grouping nodes breaks down a little when we start thinking about nova baremetal nodes.  Many nova baremetal nodes can be registered with a single host and there is no way to group different types of hardware (unless a new service host is created, which is less than ideal and also limits the number of host aggs a host can be associated with).

It would be nice to have a similar way of grouping and matching nodes for nova baremetal, but rather than being associated with service hosts the grouping is based on actually baremetal nodes.

One example use case for this is in TripleO Tuskar where we would like to group nodes based on hardware type and deploy specific services onto different types of hardware.

Specification URL (additional information):

None