Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1052804

Summary:	[RFE][nova]: VMware: Storage based policy support
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-nova	Assignee:	Matthew Booth <mbooth>
Status:	CLOSED ERRATA	QA Contact:	Jaroslav Henner <jhenner>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ddomingo, markmc, ndipanov, sgordon, tjones, yeylon
Target Milestone:	Upstream M1	Keywords:	FutureFeature, OtherQA, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/vmware-spbm-support
Whiteboard:	upstream_milestone_kilo-1 upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-nova-2015.1.0-10.el7ost	Doc Type:	Enhancement
Doc Text:	You can now use VMware storage policy to manage how storage is assigned to different instances. This can help you ensure that instances are assigned to the most appropriate storage in an environment where multiple data stores (of varying costs and performance properties) are attached to a VMware infrastructure.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:11:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1055536

Description RHOS Integration 2014-01-14 05:05:12 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/vmware-spbm-support.

Description:

The blueprint will add the ability to assign a storage policy to a instance. The datastore that is selected for the instance will match the predefined storage policy.

The blueprint with be implemented by Sabari Murugesan and Gary Kotton

TBD - post a link to the detailed design document

Specification URL (additional information):

None

Comment 8 errata-xmlrpc 2015-08-05 13:11:18 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548