da224b3a05
Import the following files from the former config-reference [1]: api.rst cells.rst fibre-channel.rst hypervisor-basics.rst hypervisor-hyper-v.rst hypervisor-kvm.rst hypervisor-lxc.rst hypervisor-qemu.rst hypervisor-virtuozzo.rst hypervisor-vmware.rst hypervisor-xen-api.rst hypervisor-xen-libvirt.rst hypervisors.rst index.rst iscsi-offload.rst logs.rst resize.rst samples/api-paste.ini.rst samples/index.rst samples/policy.yaml.rst samples/rootwrap.conf.rst schedulers.rst The below files are skipped as they're already included, in slightly different forms, in the nova documentation. config-options.rst nova-conf-samples.rst nova-conf.rst nova.conf Part of bp: doc-migration Change-Id: I145e38149bf20a5e068f8cfe913f90c7ebeaad36
27 lines
958 B
ReStructuredText
27 lines
958 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 `OpenStack
|
|
End User Guide <https://docs.openstack.org/user-guide/
|
|
cli_change_the_size_of_your_server.html>`_.
|
|
|
|
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.
|