Skip to main content
Manage the operation of the cloud server
Last update:

Manage the operation of the cloud server

You can manage the operation of the cloud server:

If the cloud server is shut down or suspended, all cloud platform resources continue to be paid for: vCPU, RAM, local and network disks, GPUs, public IP addresses, public subnets.

If the server is frozen, vCPU, RAM and GPU are not charged, all other resources are charged. Learn more about the cloud platform payment model in the article Cloud Server Payment Model and Pricing.

Shut down the server⁠

When shutting down the server, the operating system will shut down correctly. Next, the power will be turned off.

If the server does not respond within a certain time, the server will be stopped forcibly. In case of forced stop, unsaved data may be lost.

If the cloud server is turned off, all cloud platform resources continue to be paid for: vCPU, RAM, local and network disks, GPU, public IP addresses, public subnets. Learn more about the cloud platform payment model in the Cloud Server Payment Model and Pricing article.

  1. In the Control panel, on the top menu, click Products and select Cloud Servers.

  2. In the Control panel, on the top menu, click Products and select Cloud Servers.

  3. From the server's menu, select Disable. The server will switch to the SHUTOFF status.

Turn on the server⁠

If the server was shut down, when it is turned on, the operating system will reboot, disks and ports will be connected.

  1. In the Control panel, on the top menu, click Products and select Cloud Servers.

  2. In the dashboard, on the top menu, click Products and select Cloud Servers.

  3. From the server's menu, select Enable. The server will switch to the ACTIVE status.

Freeze the server⁠

Freezing is a cloud server shutdown where vCPU, RAM and GPU are transferred to a common resource pool and are no longer charged. At the same time, other cloud platform resources continue to be billed : network disks, public IP addresses, public subnets. Learn more about the cloud platform payment model.

You can only freeze cloud servers with a bootable network disk. Servers with a local disk cannot be frozen.

  1. In the dashboard, on the top menu, click Products and select Cloud Servers.

  2. From the server's menu, select Freeze. The server will go to the FROZEN status.

Resume server operation after a freeze⁠

When the server is reactivated, a cloud server is created with the same number of vCPUs, RAM, and GPUs that were available at the time of the freeze. The server is created if there are resources in the common pool.

  1. In the dashboard, on the top menu, click Products and select Cloud Servers.

  2. From the server's menu, select Resume. The server will go to the ACTIVE status.

Suspend the server⁠

For your information

You can only suspend the server through the OpenStack CLI.

The server will be paused. The state of the server and the system will be completely preserved, and the server can be resumed — it will continue to operate in the state it was in at the time of the pause.

If the cloud server is suspended, all cloud platform resources continue to be paid for: vCPU, RAM, local and network disks, GPU, public IP addresses, public subnets. Learn more about the cloud platform payment model in the Cloud Server Payment Model and Pricing article.

  1. Open the OpenStack CLI.

  2. Suspend the cloud server:

    openstack server pause <server>

    Specify <server> — server ID or name. The list can be viewed using the openstack server list command.

    The server will go to PAUSED status.

Resume server operation after suspension⁠

For your information

You can only resume the server after a suspension through the OpenStack CLI.

If the server has been suspended, when it is resumed, it will continue in the state it was in when it was suspended.

  1. Open the OpenStack CLI.

  2. Reactivate the cloud server:

    openstack server unpause <server>

    Specify <server> — server ID or name. The list can be viewed using the openstack server list command.

    The server will go into ACTIVE status.