Comment 14 for bug 1429220

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/206632
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9d353e59ec4b8653738bc93b62a30c0888f6c3e5
Submitter: Jenkins
Branch: master

commit 9d353e59ec4b8653738bc93b62a30c0888f6c3e5
Author: Daniel P. Berrange <email address hidden>
Date: Tue Jul 28 13:18:25 2015 +0100

    libvirt: take account of disks in migration data size

    Currently migration is tuned based on the guest RAM size
    alone, but when doing block migration we must also look
    at the guest disk size to determine total data transfer.

    This change currently follows the (stupid) libvirt logic
    for deciding which disks are copied. In the future when
    we can use new libvirt which lets us specify a desired
    list of disks we'll update this logic.

    DocImpact: the amount of time a live migration can take
    is now configurable for the libvirt driver, and is
    based on a number of seconds per gigabyte of RAM and
    local disk.

    Closes-bug: #1429220
    Change-Id: I3d525e62c6686277c6a05f2a91edefad3230c73f