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

Bug 1041068

Summary:	[RFE][nova]: VMware: support for vSAN datastores
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, jhenner, markmc, ndipanov, sgordon, tjones, yeylon
Target Milestone:	Upstream M2	Keywords:	FutureFeature, OtherQA, TestOnly, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/vmware-vsan-support
Whiteboard:	upstream_milestone_kilo-2 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 vSAN data stores. These stores allow you to use vMotion while simultaneously using hypervisor-local storage for instances.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:10:38 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 2013-12-12 13:33:35 UTC

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

Description:

Currently the vmwareapi compute driver only support deploying instances to
NFS, and VMFS datastores. This blueprint proposes to add support for using vSAN
storage as well.

The main difference visible to the compute driver when employing vSAN over
existing datastore types that is is that virtual disk data files are not
directly addressable as datastore paths. This means that existing code that
maniuplate disk data files has to be modified to account for that. In
particular disk images will have to be imported to a vSAN datastore along as a
shadow VM (a VM container to hold a reference to the base disk disk, and is not
meant to be powered on) using the ImportVApp API, and exported out of vSAN
(e.g. during nova snapshot) using the ExportVm API. The above-mentioned APIs
only works with VMDK disk of the 'streamOptimized' format.  Hence, the driver
will be modified recognize Glance vmdk images tagged with the property
vmware_disktype='streamOptimized' as disks of such format. Images not tagged
with the streamOptimized disk type will not be deployed on vSAN.

The set of changes can be roughly broken down to:

1. Add support for the shadow VM import/export workflow
2. Allow datastores of vSAN type be selectable as storage candidates

Specification URL (additional information):

None

Comment 8 errata-xmlrpc 2015-08-05 13:10:38 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