Multiple node compute resize bug

[Brian Elliott]

Commit 885cf0949ab2e116da39143c2f6469362367ec7d introduced a bug where compute resource tracking numbers are broken after resize operations because the instance node field never gets updated to the new value of hypervisor_hostname on the destination compute_node.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/17001
Committed: http://github.com/openstack/nova/commit/edd52974e2cdfc96088617ac19d860f55fcb6209
Submitter: Jenkins
Branch: master

commit edd52974e2cdfc96088617ac19d860f55fcb6209
Author: Brian Elliott <email address hidden>
Date: Tue Nov 27 13:12:18 2012 +0000

    Migration model update for multi-node resize fix.

    Adds source_node and dest_node to Migration model records for
    compatibility with multi-node resizes.

    The accompanying database migration:
    * Adds source and dest node information to existing Migration records
    * Fixes the node field on Instance records that have been resized.

    bug 1081355

    Change-Id: I4b58821174a262ed7885aba1fc79b3b67c9aa859

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/17002
Committed: http://github.com/openstack/nova/commit/8a3c7d30914c7cd1f85583316980ece3c33ed3d1
Submitter: Jenkins
Branch: master

commit 8a3c7d30914c7cd1f85583316980ece3c33ed3d1
Author: Brian Elliott <email address hidden>
Date: Tue Nov 27 16:49:58 2012 +0000

    Make resize and multi-node work properly together

    Added node support to migrations and update node properly in
    'resize_instance'.

    bug 1081355

    Change-Id: I003d34e3f7ed9ce2feda19ee5ce210ed4ba7eaa1