Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Resize on same host from STOPPED instance

If I'm resizing an instance on the same host and it's initial state is STOPPED, should it be in STOPPED state after the resize is done (go back to the original state) or should it be left in ACTIVE state? Assume I've confirmed the resize.

Resize on same host from STOPPED instance

If I'm resizing an instance on the same host and it's initial state is STOPPED, should it be in STOPPED state after the resize is done (go back to the original state) or should it be left in ACTIVE state? Assume I've confirmed the resize.

I've looked at the compute Admin guide for resize but the example is using an instance already in ACTIVE state rather than STOPPED state (but I've looked at the code to know that the resize operation can start from either ACTIVE or STOPPED).

http://docs.openstack.org/trunk/openstack-compute/admin/content/nova_cli_resize.html

I'm running on stable/grizzly.

Resize on same host from STOPPED instance

If I'm resizing an instance on the same host and it's initial state is STOPPED, should it be in STOPPED state after the resize is done (go back to the original state) or should it be left in ACTIVE state? Assume I've confirmed the resize.

I've looked at the compute Admin guide for resize but the example is using an instance already in ACTIVE state rather than STOPPED state (but I've looked at the code to know that the resize operation can start from either ACTIVE or STOPPED).

http://docs.openstack.org/trunk/openstack-compute/admin/content/nova_cli_resize.html

I'm running on stable/grizzly.