Updated openstack/openstack
Project: openstack/cinder  7268c4d091a360ea4ccd7b5fb8e691dea350e0f8
null
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
Updated openstack/openstack
Project: openstack/nova  89b7bdca038600869cfb74e004c1b0adbf39dc1c
null
Let drivers override default rebuild() behaviour

The rebuild compute method currently makes separate calls to destroy()
and spawn(), but this introduces race conditions with drivers where
another compute process could claim the VM resources between destroy
and spawn. This is a particular problem for baremetal where the
planned ephemeral preservation feature requires that the rebuild
happen on the same physical node.

Partial-Bug: #1174154
blueprint: baremetal-preserve-ephemeral
Co-Authored-By: Robert Collins <rbtcollins@hp.com>
Co-Authored-By: Joe Gordon <joe.gordon0@gmail.com>

Change-Id: I5fadc27207ed5725ecf0cf6bc34a52a95af42679