diff options
| author | Rafi Khardalian <rafi@metacloud.com> | 2012-09-04 13:37:46 +0000 |
|---|---|---|
| committer | Rafi Khardalian <rafi@metacloud.com> | 2012-11-20 22:09:35 +0000 |
| commit | 99b5e96795b8475f14d53bbc3845e7bace730963 (patch) | |
| tree | 0cfc5c71e3fc7bb59f2ea51e00e39bc142b267d4 /nova/openstack | |
| parent | e984c20f1611d3aa5e7b4607a2232ee25112ab47 (diff) | |
| download | nova-99b5e96795b8475f14d53bbc3845e7bace730963.tar.gz nova-99b5e96795b8475f14d53bbc3845e7bace730963.tar.xz nova-99b5e96795b8475f14d53bbc3845e7bace730963.zip | |
Allow VMs to be resumed after a hypervisor reboot
Fixes bug 1052696.
Update the compute manager to pass network_info and block_device_info
to the driver.resume() and update all virtualization drivers to accept
the new arguments.
For libvirt, change resume() to use _create_domain_and_network()
rather than _create_domain(). This eliminates the assumption that the
network and block device connections remained in place from the period
between the VM being suspended and resumed. Instead, all the
networking and block connections will be rebuilt on resume (in case
they are missing) as is the case after a hypervisor reboot.
Change-Id: I6e19ec42f7e929678abce8f276c0a6e91f1fa8af
Diffstat (limited to 'nova/openstack')
0 files changed, 0 insertions, 0 deletions