VMware cluster driver does not favor shared datastores over unshared ones

[Vui Lam]

For a cluster, especially one that is managed by DRS, placing a new VM on a datastore accessible to the largest number of the cluster's hosts enables capabilities like vMotion, increases resource management flexibility by DRS; whereas placing it in a datastore that is local only to one host has the opposite effect, as it essentially pins the VM to that one host. Hence the driver should by default favor datastores that are more accessible to the cluster's hosts over those that are not. Having this behavior will likely reduce the number of situations when the datastore_regex has to be configured by the administrator to specify allowed datastores. In the degenerate case where there is only one host in the cluster, a local datastore can still be picked for placement.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/60010

[Tracy Jones (tjones-i)]

all reviews are abandoned for this and it has not been updated in a long time. moving back to triaged. Please set to in progress if you plan on working on it

[Tracy Jones (tjones-i)]

https://review.openstack.org/289631

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/289631
Reason: This review is > 6 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Sujitha (sujitha-neti)]

The patch submitted for this bug is abandoned and there is no progress since a long time. To signal that to other contributors which might provide patches for this bug, I'm removing the assignee. Please assign to yourself if you plan to work on it.