Bug 1041222

Summary:	[RFE][nova]: vmware datastore selection by scheduler filter/weighter
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/vmware-datastore-selection-by-scheduler-filter
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:15:47 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 13:59:38 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/vmware-datastore-selection-by-scheduler-filter.

Description:

Allow for Scheduler Filters or Weighters to make the decision as to which datastore the VMware Nova compute driver will use to place a newly provisioned VM.

The problem is that an ESXi host or Cluster of hosts may have access to multiple datastores in which to place their VMDK. When these datastores are all equal, there should be some mechanism to allow the scheduler to decide which datastore it wants to place an image / VMDK. Architecturally, in OpenStack policy level decisions (like which hypervisor to use) occur up at the Scheduler and not down at the driver. To preserve this logical separation of concerns, the driver should report its available datastores to the scheduler and the scheduler should be able to choose the appropriate datastore based on datastore statistics gathered by the driver.

NOTE: this feature should not prevent alternative mechanisms for choosing a datastore (should a user desire to set a parameter for the driver to only use stored named: ^OpenStack.*DataStore$ for example. This should be viewed as an additional feature to add to the stack. If an alternative mechanism is chosen via a setting, the filter's advice should be optionally ignored (with a warning message).

Specification URL (additional information):

None