dd1a416bc9
This ensures we have version-specific references to other projects [1]. Note that this doesn't mean the URLs are actually valid - we need to do more work (linkcheck?) here, but it's an improvement nonetheless. [1] https://docs.openstack.org/openstackdocstheme/latest/#external-link-helper Change-Id: Ifb99e727110c4904a85bc4a13366c2cae300b8df
27 lines
946 B
ReStructuredText
27 lines
946 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.
|
|
|
|
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 the
|
|
:python-openstackclient-doc:`OpenStack CLI Guide
|
|
<cli/command-objects/server.html#server-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.
|