Stephen Finucane 70a4054f86 docs: Update resize doc

- Remove references to configuration options (which end-users will not
  be able to set)
- Switch from the '--confirm' and '--revert' flags to the top-level
  commands
- You can't revert a failed resize so don't suggest otherwise
- Fix some wrapping

Change-Id: I934e7ca327ff4c9bb9b00d1df3323df05da956d9
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Depends-On: I733796d3bda6c3755a3d3548bbe695abb474a6a0

2019-09-25 13:36:26 +00:00

2.2 KiB

Raw Blame History

Resize an instance

You can change the size of an instance by changing its flavor. This rebuilds the instance and therefore results in a restart.

To list the VMs you want to resize, run:

$ openstack server list

Once you have the name or UUID of the server you wish to resize, resize it using the openstack server resize command:

$ openstack server resize --flavor FLAVOR SERVER

Note

By default, the openstack server resize command gives the guest operating system a chance to perform a controlled shutdown before the instance is powered off and the instance is resized. This behavior can be configured by the administrator but it can also be overridden on a per image basis using the os_shutdown_timeout image metadata setting. This allows different types of operating systems to specify how much time they need to shut down cleanly. See Useful image properties <admin/useful-image-properties> for details.

Resizing can take some time. During this time, the instance status will be RESIZE:

$ openstack server list
+----------------------+----------------+--------+-----------------------------------------+
| ID                   | Name           | Status | Networks                                |
+----------------------+----------------+--------+-----------------------------------------+
| 67bc9a9a-5928-47c... | myCirrosServer | RESIZE | admin_internal_net=192.168.111.139      |
+----------------------+----------------+--------+-----------------------------------------+

When the resize completes, the instance status will be VERIFY_RESIZE. You can now confirm the resize to change the status to ACTIVE:

$ openstack server resize confirm SERVER

Note

The resized server may be automatically confirmed based on the administrator's configuration of the deployment.

If the resize does not work as expected, you can revert the resize. This will revert the instance to the old flavor and change the status to ACTIVE:

$ openstack server resize revert SERVER

2.2 KiB Raw Blame History

Resize an instance

2.2 KiB

Raw Blame History