Change cloud server configuration

You can change the cloud server configuration and the amount of resources:

• select a different lineup and fixed configuration (except for the GPU lineup);
• change a fixed configuration to a custom configuration (except for the GPU lineup);
• change the amount of resources in a fixed or custom configuration — vCPU, RAM, local disk size;
• change a custom configuration to a fixed one;
• configure dedicated cores for a cloud server, enable Hyper-Threading (SMT) and mandatory resource placement on a single NUMA node in the configuration.

A cloud server configuration with a local disk cannot be changed to a configuration without a local disk and vice versa.

You can add GPUs to custom configuration servers.

When changing the configuration, all data on the cloud server is preserved.

Change server configuration

carefully

During the configuration change, the cloud server will be unavailable.

Control panel

1. In the Control Panel, in the top menu, click Products and select Cloud Servers.

2. Open the server page → tab Configuration.

3. Click Change configuration.

4. In the Configuration block, select a new configuration. If you need to add a GPU to the cloud server, select the product line GPU.

5. Optional: you can configure settings if the cloud server is created in the segment of the multizone pool ru-6 or pool segments ru-3b, ru-7a, and ru-7b:

   5.1. Expand the block with the description of configuration settings.

   5.2. Optional: select the processor manufacturer. Choosing a manufacturer is not available in all pools.

   5.3. Optional: if you want the physical CPU cores to be dedicated to the cloud server vCPUs, select the Dedicated cores checkbox. Learn more in the Dedicated cores instructions. If the cloud server has dedicated cores and you need to disable them, clear the Dedicated cores checkbox. If the checkbox is unavailable, dedicated cores cannot be disabled.

   5.4. Optional: if the cloud server has dedicated cores and you want to enable Hyper-Threading, select the Hyper-Threading (SMT) checkbox. To disable multithreading, clear the checkbox Hyper-Threading (SMT).

   5.5. Optional: if the cloud server has dedicated cores and you want to place CPU resources on a single NUMA node, select the Strict NUMA node placement checkbox. If you do not want to place cloud server resources on a single NUMA node, clear the Strict NUMA node placement checkbox. If cloud server resources cannot be placed on a single node, the changed configuration will not be applied. Learn more in the Placement on a single NUMA node subsection of the Dedicated cores instructions.

6. Specify the required amount of resources.

7. Click Save and reboot.

8. If you did not change the configuration, but only changed the Hyper-Threading (SMT) setting in step 5.4, perform a hard reboot.

OpenStack CLI

1. Open the OpenStack CLI.

2. Change the cloud server configuration:

   openstack server resize --flavor <flavor> <server>

   Specify:

   • <flavor> — flavor ID or name. Flavors correspond to cloud server configurations and determine the number of vCPUs, RAM, and server local disk size. You can use fixed configuration flavors or create a flavor. The list of flavors can be viewed using the openstack flavor list command or in the List of fixed configuration flavors in all pools table;
   • <server> — server ID or name. You can view the list of servers using the openstack server list command.

3. Optional: if the cloud server flavor supports dedicated cores, you can configure Hyper-Threading (SMT) or mandatory resource placement on a single NUMA node:

   openstack server set \
       --property x_cloud_smt_enabled=<enable_value>
       --property x_cloud_numa_nodes=1
       <server>

   Specify:

   • --property x_cloud_smt_enabled=<enable_value> — Hyper-Threading (SMT) configuration. In the <enable_value> parameter, specify one of the following values:
     • false — disable Hyper-Threading (SMT);
     • true — enable Hyper-Threading (SMT);
   • --property x_cloud_numa_nodes=1 — placing resources on a single NUMA node. If cloud server resources cannot be placed on a single node, the changed configuration will not be applied. Learn more in the Placement on a single NUMA node subsection of the Dedicated cores instructions;
   • <server> — server ID or name. You can view the list of servers using the openstack server list command.

4. If you changed the Hyper-Threading setting in step 3, perform a hard reboot.