3cd5198d5a
The admin config resize doc was linking to a now non-existent user guide doc which was deleted in pike. This change imports the resize user guide from the openstack-manuals stable/ocata branch, fixes the link, and updates the resize user doc to (1) link to our internal shutdown_timeout config option reference and (2) link to the image properties doc in glance for the os_shutdown_timeout image property. Change-Id: I9988abfd344d1d3b0b6eaf32b036369b51853965 Closes-Bug: #1784715
29 lines
980 B
ReStructuredText
29 lines
980 B
ReStructuredText
================
|
|
Configure resize
|
|
================
|
|
|
|
Resize (or Server resize) is the ability to change the flavor of a server, thus
|
|
allowing it to upscale or downscale according to user needs. For this feature
|
|
to work properly, you might need to configure some underlying virt layers.
|
|
|
|
.. todo:: This document needs to be updated for other virt drivers, shared
|
|
storage considerations, etc.
|
|
|
|
KVM
|
|
~~~
|
|
|
|
Resize on KVM is implemented currently by transferring the images between
|
|
compute nodes over ssh. For KVM you need hostnames to resolve properly and
|
|
passwordless ssh access between your compute hosts. Direct access from one
|
|
compute host to another is needed to copy the VM file across.
|
|
|
|
Cloud end users can find out how to resize a server by reading
|
|
:doc:`/user/resize`.
|
|
|
|
XenServer
|
|
~~~~~~~~~
|
|
|
|
To get resize to work with XenServer (and XCP), you need to establish a root
|
|
trust between all hypervisor nodes and provide an ``/image`` mount point to
|
|
your hypervisors dom0.
|