From e1af0645c020d8a9a0b07853b51b162fbd61712a Mon Sep 17 00:00:00 2001 From: Vipin Balachandran Date: Mon, 3 Feb 2014 18:42:15 +0530 Subject: [PATCH] vmware: Updates in data store selection section The VMDK driver was selecting datastores for volume creation based on space utilization. After the fix for bug 1250816, the datastore which is connected to maximum number of hosts is selected for volume creation. Ties are broken based on space utilization; datastore with low space utilization is preferred. This fix updates the data store selection section in the VMDK driver configuration to reflect this selection logic. Closes-Bug: #1253595 Change-Id: Ia562c452e8cf6bb1c8be6afd868f4b0b2ce0b006 --- .../block-storage/drivers/vmware-vmdk-driver.xml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml b/doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml index ce2fa889d8..d2b3ce28c1 100644 --- a/doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml +++ b/doc/config-reference/block-storage/drivers/vmware-vmdk-driver.xml @@ -171,12 +171,13 @@ Data store selection When creating a volume, the driver chooses a data store - that has sufficient free space and has the highest - freespace/totalspace metric - value. - When a volume is attached to an instance, the driver - attempts to place the volume under the instance's ESX host - on a data store that is selected using the strategy - above. + which is connected to maximum number of hosts. This is + meant to reduce the number of volume migrations while + attaching the volume to instances. The volume needs to be + migrated if the instance's ESX host cannot access the + data store containing the volume. In case of ties, the + data store with lowest space utilization is selected, where + space utilization is defined by the metric + (1 - freespace/totalspace).