Bug 1041231

Summary:	[RFE][nova]: Baremetal Node Availability Zone Provisioning
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/baremetal-availability-zones
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 17:00:27 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:01:00 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/baremetal-availability-zones.

Description:

This feature is intended to provide availability zone support for the provisioning of baremetal nodes.  As with the current implementation, availability zones for a baremetal node lie on the compute node that is managing it.  For many environments this is insufficient as the ratio of compute nodes to baremetal nodes can be quite small.  Similarly, workloads that are well suited for baremetal provisioning typically call for segregation in the form of things like rack awareness.

This change would be comprised of an additional column within the baremetal database's bm_nodes table, the accompanying changes to the baremetal api/novaclient, and a new filter for nova scheduler.  

Specification URL (additional information):

None