libvirt: take account of disks in migration data size

[OpenStack Infra]

https://review.openstack.org/206632
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

[Tom Fifield (fifieldt)]

autogenerate-config-docs should pick this up - nothing else needed

[Tom Fifield (fifieldt)]

(apart from release notes)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/219987
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=be704530212092ee777ff4181a444ff7ec4daf9d
Submitter: Jenkins
Branch: master

commit be704530212092ee777ff4181a444ff7ec4daf9d
Author: Atsushi SAKAI <email address hidden>
Date: Thu Sep 3 13:24:40 2015 +0900

    Update Config reference for nova

    Partial-Bug: #1407581
    Closes-Bug: 1478544
    Closes-Bug: 1483231
    Closes-Bug: 1483192
    Closes-Bug: 1489638

    Change-Id: I46b990567343dbeed4b99c06c1c006555f3ea645

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.