Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1041068 - [RFE][nova]: VMware: support for vSAN datastores
[RFE][nova]: VMware: support for vSAN datastores
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
unspecified
Unspecified Unspecified
low Severity low
: Upstream M2
: 7.0 (Kilo)
Assigned To: Matthew Booth
Jaroslav Henner
https://blueprints.launchpad.net/nova...
upstream_milestone_kilo-2 upstream_st...
: FutureFeature, OtherQA, TestOnly, Triaged
Depends On:
Blocks: 1055536
  Show dependency treegraph
 
Reported: 2013-12-12 08:33 EST by RHOS Integration
Modified: 2016-04-26 17:47 EDT (History)
8 users (show)

See Also:
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 09:10:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1548 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2015-08-05 13:07:06 EDT

  None (edit)
Description RHOS Integration 2013-12-12 08:33:35 EST
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 09:10:38 EDT
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

Note You need to log in before you can comment on or make changes to this bug.