Difference between revisions of "Resizing an Instance"
(Added image of Resize Instance dialog.) |
|||
(5 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
+ | '''WARNING:''' Resizing an instance in the "Active" state will '''''reboot''''' the instance, so be sure to save any active work before attempting. | ||
+ | |||
+ | |||
+ | |||
A variety of [[OpenStack#Instances|instance sizes]] are available on [[Red Cloud]]. The instance size (or type) defines how much memory (RAM) is available, the amount of per-instance storage (typically available through /dev/vdb in [[Red Cloud Linux Instances | Linux instances]]), and the number of CPU cores available. | A variety of [[OpenStack#Instances|instance sizes]] are available on [[Red Cloud]]. The instance size (or type) defines how much memory (RAM) is available, the amount of per-instance storage (typically available through /dev/vdb in [[Red Cloud Linux Instances | Linux instances]]), and the number of CPU cores available. | ||
− | Resizing an instance allows you to | + | Resizing an instance allows you to control your work process dynamically. During periods of heavy development, you may only want a small instance type to develop on, but during periods of heavy computational activity, a large instance (or multiple large instances) may be desirable. |
+ | |||
+ | '''Note:''' A GPU instance cannot be resized to a non-GPU instance flavor or a flavor with a different GPU type. If you need to modify an instance, you can create a snapshot of a GPU instance and create a new instance from that snapshot following the procedure for [[Volumes#Create_a_Bigger_Copy_of_the_Root_Volume|resizing a boot volume]]. Select the desired new flavor while configuring the new instance. | ||
The options can be found by clicking on the Resize Instance option in the menu for the instance on the right side of the instances listing page: | The options can be found by clicking on the Resize Instance option in the menu for the instance on the right side of the instances listing page: | ||
− | [[File:White_square.png| | + | [[File:White_square.png|100px|frameless]][[File:Resize Instance Menu.png|150px|frameless|border]] |
− | This option is only available | + | This option is only available for instances whose [[OpenStack#Instance States|state]] is either "Active" or "Stopped". The dialog for resizing the instance type is shown below: |
− | + | [[File:Resize Instance Dialog.png|500px|frameless|border]] | |
Simply select the new flavor you would like and then select "Resize". | Simply select the new flavor you would like and then select "Resize". |
Latest revision as of 11:51, 20 December 2021
WARNING: Resizing an instance in the "Active" state will reboot the instance, so be sure to save any active work before attempting.
A variety of instance sizes are available on Red Cloud. The instance size (or type) defines how much memory (RAM) is available, the amount of per-instance storage (typically available through /dev/vdb in Linux instances), and the number of CPU cores available.
Resizing an instance allows you to control your work process dynamically. During periods of heavy development, you may only want a small instance type to develop on, but during periods of heavy computational activity, a large instance (or multiple large instances) may be desirable.
Note: A GPU instance cannot be resized to a non-GPU instance flavor or a flavor with a different GPU type. If you need to modify an instance, you can create a snapshot of a GPU instance and create a new instance from that snapshot following the procedure for resizing a boot volume. Select the desired new flavor while configuring the new instance.
The options can be found by clicking on the Resize Instance option in the menu for the instance on the right side of the instances listing page:
This option is only available for instances whose state is either "Active" or "Stopped". The dialog for resizing the instance type is shown below:
Simply select the new flavor you would like and then select "Resize".