Managing Cloud Servers
Renaming Cloud Servers
Renaming Cloud Servers in the Control Panel
Follow these steps to rename a cloud server in the Control panel:
- Go to the Servers section in the project.
- Select the required server and click Rename in its (⋮) context menu.
- Enter a new name and confirm the changes.
Please note that you can also rename a server in the (⋮) server menu of the server page.
Renaming Cloud Servers through CLI
Learn more about getting started with the OpenStack CLI.
To rename a cloud server, run the following:
openstack server set --name <new name> <server>
Both the server name and its ID can be used in the <server> parameter.
Rebooting Cloud Servers
There are two types of server reboot: software and hard (via shutdown).
Rebooting Cloud Servers in the Control Panel
To reboot a cloud server in the Control panel:
-
Go to the Servers section in the project.
-
Select the required server and from its (⋮) context menu:
- click Software reboot for a software reboot;
- click Hard reboot for a hard reboot.
Please note that you can also reboot a server in the (⋮) menu on the server page.
Rebooting Cloud Servers through CLI
Learn more about getting started with the OpenStack CLI.
To view a list of cloud servers, run the following:
openstack server list
For a software reboot, run:
openstack server reboot <server>
For a hard reboot, run:
openstack server reboot --hard <server>
Both the server name and its ID can be used in the <server> parameter.
Starting and Stopping Cloud Servers
Starting and Stopping Cloud Servers in the Control Panel
To manage the cloud server power in the Control panel:
- Go to the Servers section in the project.
- Select the required server and click Turn on server or Turn off server in its (⋮) context menu. The started server can be paused by clicking Pause.
Please note that you can also manage the cloud server power on the server page in the (⋮) server menu by using the toggle switch. There are two server states — ACTIVE (started) and SHUTOFF (stopped).
Starting and Stopping Cloud Servers through CLI
Learn more about getting started with the OpenStack CLI.
To view a list of servers, run the following:
openstack server list
To start a server, run:
openstack server start <server>
To stop a server, run:
openstack server stop <server>
Using Rescue Mode on a Cloud Server
If it is impossible to connect to the server (when regular access to the server is lost, or you cannot perform diagnostics using OS tools), you can reboot it to Rescue mode. The system that works in RAM and does not use the server’s local disks will boot.
Booting to Rescue Mode
To boot to Rescue in the Control panel:
- Go to the Servers section in the project.
- Select the required server and click Rescue in the (⋮) context menu.
- Open the console by clicking on the Console icon.
Please note that you can also boot to Rescue in the (⋮) server menu on the server page. The console can be opened on the Console tab or by clicking on the corresponding icon.
After rebooting to Rescue, the cloud server can be managed via SSH.
To exit Rescue mode, select Exit Rescue from the (⋮) menu of the server.
Learn more about booting the server to Rescue. Please note that the actions are the same when using Rescue mode with dedicated and cloud servers.
Connecting to the Cloud Server via SSH in Rescue
To connect via SSH, run the following command:
ssh root@<server IP>
Where <server IP> — is the external IP address of the server. Learn more in the instructions for Connecting a server to the Internet.
The system will request the password that can be found in the SSH root password is: xxxxxx line in the console.
When you first log in to the server, the SSH key is saved to the ~/.ssh/known_hosts file. When reconnecting, the REMOTE HOST IDENTIFICATION HAS CHANGED error may appear. To fix it, you need to delete the host information by IP address by running the following command:
ssh-keygen -f "/home/<user>/.ssh/known_hosts" -R "<server IP>"
Where <user> is the username of the account on the local computer from which the connection is made (in most cases, it is displayed in the command line).
If you get an error connecting to the cloud server, you can also connect using the following command:
ssh -o UserKnownHostsFile=/dev/null root@<server IP>