cinder/cinder/volume/drivers/vmware
Vipin Balachandran b85cc49588 VMDK:Using host mount info for datastore selection
Currently the VMDK driver picks a datastore for volume creation based
on space utilization. The shadow VM corresponding to the volume is
migrated to a different host and datastore if the volume is attached
to an instance created in a host which cannot access the volume's
current datastore. To reduce these migrations, this fix selects a
datastore which is connected to maximum number of hosts, provided
there is enough space to accommodate the volume. Ties are broken
based on space utilization; datastore with low space utilization
is preferred.

Closes-Bug: #1250816
Change-Id: I5ecf22d782857fca0889799229465c49afe188a0
2013-12-05 12:20:48 +05:30
..
__init__.py Implements APIs for VMDK driver 2013-08-30 03:44:41 -07:00
api.py Using HttpNfcLease to transfer vmdk files. 2013-11-14 12:24:29 +05:30
error_util.py Implements APIs for VMDK driver 2013-08-30 03:44:41 -07:00
io_util.py Using HttpNfcLease to transfer vmdk files. 2013-11-14 12:24:29 +05:30
read_write_util.py Using HttpNfcLease to transfer vmdk files. 2013-11-14 12:24:29 +05:30
vim.py VMware: Re-create session for RetrievePropertiesEx 2013-10-05 00:10:02 -07:00
vim_util.py VMware: Usng RetrvProprtisEx & does multi ESX scan 2013-09-29 22:05:43 -07:00
vmdk.py VMDK:Using host mount info for datastore selection 2013-12-05 12:20:48 +05:30
vmware_images.py Using HttpNfcLease to transfer vmdk files. 2013-11-14 12:24:29 +05:30
volumeops.py VMDK:Using host mount info for datastore selection 2013-12-05 12:20:48 +05:30