Reviewed: https://review.openstack.org/227278 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=23fd0389f0e23e7969644079f4b1ad8504cbb8cb Submitter: Jenkins Branch: master
commit 23fd0389f0e23e7969644079f4b1ad8504cbb8cb Author: Pawel Koniszewski <pawel.koniszew...@intel.com> Date: Wed Feb 10 13:09:44 2016 +0100 Allow block live migration of an instance with attached volumes Since libvirt 1.2.17 it is possible to select which block devices should be migrated to destination host. Block devices that are not provided will not be migrated. It means that it is possible to exclude volumes from block migration and therefore prevent volumes from being copied to themselves. This patch implements new check of libvirt version. If version is higher or equal to 1.2.17 it is possible to block live migrate vm with attached volumes. Co-Authored-By: Bartosz Fic <bartosz....@intel.com> Change-Id: I8fcc3ef3cb5d9fd3a95067929c496fdb5976fd41 Closes-Bug: #1398999 Partially implements: blueprint block-live-migrate-with-attached-volumes ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1398999 Title: Block migrate with attached volumes copies volumes to themselves Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) juno series: Fix Released Status in libvirt package in Ubuntu: Fix Released Status in nova package in Ubuntu: Triaged Status in libvirt source package in Trusty: Confirmed Status in nova source package in Trusty: Triaged Status in libvirt source package in Utopic: Won't Fix Status in nova source package in Utopic: Won't Fix Status in libvirt source package in Vivid: Confirmed Status in nova source package in Vivid: Triaged Status in libvirt source package in Wily: Fix Released Status in nova source package in Wily: Triaged Bug description: When an instance with attached Cinder volumes is block migrated, the Cinder volumes are block migrated along with it. If they exist on shared storage, then they end up being copied, over the network, from themselves to themselves. At a minimum, this is horribly slow and de- sparses a sparse volume; at worst, this could cause massive data corruption. More details at http://lists.openstack.org/pipermail/openstack- dev/2014-June/038152.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1398999/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp