diff options
| author | Matt Riedemann <mriedem@us.ibm.com> | 2013-05-13 10:06:11 -0700 |
|---|---|---|
| committer | Matt Riedemann <mriedem@us.ibm.com> | 2013-05-30 07:53:14 -0700 |
| commit | 32372a62a89614d4ddc7f2bdc96f41c4d49bd131 (patch) | |
| tree | fb4932186453deb2c1a44fa25c8d982093cde8f5 /nova/utils.py | |
| parent | 1690a1ae8f2fdddebfb8ae50a8492aedf466b8e3 (diff) | |
| download | nova-32372a62a89614d4ddc7f2bdc96f41c4d49bd131.tar.gz nova-32372a62a89614d4ddc7f2bdc96f41c4d49bd131.tar.xz nova-32372a62a89614d4ddc7f2bdc96f41c4d49bd131.zip | |
Set resized instance back to original vm_state
You can resize an instance when it's in the ACTIVE or STOPPED state but
the code currently always finishes the resize (either confirmed or
rejected) by putting the instance into ACTIVE state. This change
saves the original vm_state and uses it to restore the state on the
instance after the resize is confirmed or rejected.
With this change, the resize flow will never automatically power on an
instance that is originally shutoff. The user, however, can manually
power on the resized instance to test it before confirming or rejecting
the resize. If the user powered on the instance and confirmed the
resize, then this change will leave the instance active. If the user
powered on the instance and then rejected the resize, this change will
stop the instance when it finishes the revert operation.
Related to bug 1177811
Change-Id: I19fa61d467edd5a7572040d084824972569ef65a
Diffstat (limited to 'nova/utils.py')
0 files changed, 0 insertions, 0 deletions