ECS Backup Procedure
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Server Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the ECS to be associated. The storage capacity used by the backup increases accordingly.
-ECS Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Server Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the ECS to be associated. The storage capacity used by the backup increases accordingly.
- If the ECS is not associated with a vault, buy a vault first and then configure the backup information as prompted.
For details, see Creating a Server Backup Vault.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Click OK. The system automatically creates a backup for the ECS.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
@@ -14,7 +14,7 @@After the backup is complete, you can restore server data or create images on the Backups tab page. For details, see Restoring from a Cloud Server Backup and Using a Backup to Create an Image.
EVS Disk Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Disk Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default. Click
to view the disks attached to the ECSs. Select the disks to be backed up. - Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the disks to be associated. The storage capacity used by the backup increases accordingly.
EVS Disk Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Disk Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default. Click to view the disks attached to the ECSs. Select the disks to be backed up.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the disks to be associated. The storage capacity used by the backup increases accordingly.
- Server List: The ECS to be backed up is selected by default. Click
- If the ECS is not associated with a vault, buy a vault first and then configure the backup information as prompted.
For details, see Creating a Disk Backup Vault.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Click OK. The system automatically creates a backup for the disk.
On the Backups tab of the CBR console, if the status of the backup is Available, the backup task is successful.
diff --git a/docs/ecs/umn/en-us_topic_0000001143214829.html b/docs/ecs/umn/en-us_topic_0000001143214829.html index 7e0f25e64..c44453b8c 100644 --- a/docs/ecs/umn/en-us_topic_0000001143214829.html +++ b/docs/ecs/umn/en-us_topic_0000001143214829.html @@ -44,7 +44,7 @@ LOGGENERATIONS=3Configuring atop for Ubuntu 20/22 and Debian 10/11
- Run the following command to install atop:
- Run the following command to modify the configuration file of atop:
Modify the following parameters, save the modification, and exit:
-- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGINTERVAL=15 +
- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGINTERVAL=15 LOGGENERATIONS=3
- Run the following command to start atop:
@@ -83,9 +83,9 @@ LOGGENERATIONS=3
Configuring atop for SUSE 12 or SUSE 15
- Run the following command to download the atop source package:
- Run the following command to install the package:
- Run the following command to install atop dependencies. -
- Run the following command to compile atop: +
- Run the following commands to compile atop:
rpmbuild -bb atop-2.6.0.spec
- - Run the following command to install atop: +
- Run the following commands to install atop:
cd /usr/src/packages/RPMS/x86_64
rpm -ivh atop-2.6.0-1.x86_64.rpm
- Run the following command to modify the configuration file of atop:
Modify the following parameters, save the modification, and exit:
@@ -105,7 +105,7 @@ LOGGENERATIONS=3If the version is 220 or later, go to the next step.
Otherwise, delete parameter --now from the Makefile of atop.
vi atop-2.6.0/Makefile
-Delete parameter --now following the systemctl command.
+Delete parameter --now following the systemctl command.
then /bin/systemctl disable atop 2> /dev/null; \ /bin/systemctl disable atopacct 2> /dev/null; \ /bin/systemctl daemon-reload; \ @@ -116,7 +116,7 @@ LOGGENERATIONS=3 - Installing command for EulerOS or Fedora
- Installing command for Debian 9, Debian 10, or Ubuntu
apt install make gcc zlib1g-dev libncurses5-dev libncursesw5-dev -y
- - Run the following commands to compile and install atop. +
- Compile and install atop.
make systemdinstall
- Modify the configuration file of atop.
Modify the following parameters, save the modification, and exit:
@@ -126,14 +126,14 @@ LOGGENERATIONS=3 LOGPATH=/var/log/atop
- Restart atop. -
- Run the following command to check the status of atop. active (running) indicates that atop is running properly.
systemctl status atop
+ - Check the status of atop. active (running) indicates that atop is running properly.
systemctl status atop
atop.service - Atop advanced performance monitor Loaded: loaded(/lib/systemd/system/atop.service; enabled) Active: active (running) since Sun2021-07-25 19:29:40 CST; 4s ago .
Analyzing atop Logs
After startup, atop stores collection records in /var/log/atop.
Run the following command to check the log file:
atop -r /var/log/atop/atop_2024XXXX
-- Common atop commandsAfter opening the log file, you can use the following commands to sort data.
- c: used to sort processes by CPU usage in descending order.
- m: used to sort processes by memory usage in descending order.
- d: used to sort processes by disk usage in descending order.
- a: used to sort processes by the overall resource usage in descending order.
- n: used to sort processes by network usage in descending order.
- t: used to go to the next monitoring collection point.
- T: used to go to the previous monitoring collection point.
- b: used to specify a time point in the format of YYYYMMDDhhmm.
- Common atop commandsAfter opening the log file, you can use the following commands to sort data:
- c: used to sort processes by CPU usage in descending order.
- m: used to sort processes by memory usage in descending order.
- d: used to sort processes by disk usage in descending order.
- a: used to sort processes by the overall resource usage in descending order.
- n: used to sort processes by network usage in descending order.
- t: used to go to the next monitoring collection point.
- T: used to go to the previous monitoring collection point.
- b: used to specify a time point in the format of YYYYMMDDhhmm.
- System resource monitoring fields
The following figure shows some monitoring fields and values. The values vary according to the sampling period and atop version. The figure is for reference only.
Figure 1 System resource monitoring fields@@ -174,7 +174,7 @@ GRUB_DISABLE_RECOVERY="true"
- Set the vmcore dump level.
Add the following content to file /etc/kdump.conf. If the content already exists, skip this step.
core_collector makedumpfile -d 31 -c
-where
+In the preceding command:
-c indicates compressing the vmcore file.
-d indicates leaving out irrelevant data. Generally, the value following -d is 31, which is calculated based on the following values. You can adjust the value if needed.
zero pages = 1 diff --git a/docs/ecs/umn/en-us_topic_0000001194242043.html b/docs/ecs/umn/en-us_topic_0000001194242043.html index 5365796b7..8b46ef17a 100644 --- a/docs/ecs/umn/en-us_topic_0000001194242043.html +++ b/docs/ecs/umn/en-us_topic_0000001194242043.html @@ -33,7 +33,7 @@
Enabling HSS
Host Security Service (HSS) is designed to improve the overall security for ECSs. It helps you identify and manage the assets on your servers, eliminate risks, and defend against intrusions and web page tampering. There are also advanced protection and security operations functions available to help you easily detect and handle threats.
-Before using the HSS service, install the HSS agent on your ECSs first so that your ECSs are protected by the HSS cloud protection center. You will be able to check the security statuses and risks (if any) of all ECSs in a region on the HSS console.
+Before using the HSS service, install the HSS agent on your ECSs first and you will be able to check the ECS security status and risks in a region on the HSS console.
We provide different methods for you to install the HSS agent depending on whether your ECSs are to be created or already exist.
- Scenario 1: An ECS is to be created.
When you use certain public images to create ECSs, you are advised to use HSS to protect your ECSs.
Select one of the following options:- Advanced HSS edition (paid): You can choose the enterprise edition and you need to pay for it.
- None: HSS is disabled and servers are not protected.
CBR enables you to back up ECSs and disks with ease. In case of a virus attack, accidental deletion, or software or hardware fault, you can restore data to any point in the past when the data was backed up. CBR protects your services by ensuring the security and consistency of your data.
To enable CBR when purchasing an ECS:
Set CBR when purchasing an ECS. The system will associate the ECS with a cloud backup vault and the selected backup policy to periodically back up the ECS.
-- Create new
- Set the name of the cloud backup vault, which consists of 1 to 64 characters, containing only letters, digits, underscores (_), and hyphens (-). For example, vault-f61e. The default naming rule is vault_xxxx.
- Enter the vault capacity, which is required for backing up the ECS. The vault capacity cannot be smaller than that of the ECS to be backed up. Its value ranges from the total capacity of the ECS to 10,485,760 in the unit of GB.
- Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one.
- Create new
- Enter the name of the cloud backup vault. The name consists of 1 to 64 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. For example, vault-f61e. The default naming rule is vault_xxxx.
- Enter the vault capacity, which is required for backing up the ECS. The vault capacity cannot be smaller than that of the ECS to be backed up. Its value ranges from the total capacity of the ECS to 10,485,760 in the unit of GB.
- Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one.
- Use existing
- Select an existing cloud backup vault from the drop-down list.
- Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one.
- Do not use
Skip this configuration if CBR is not required. If you need to enable CBR after creating an ECS, log in to the CBR console, locate the target vault, and bind the ECS to the vault.
+ - Do not use
Skip this configuration if CBR is not required. If you need to enable CBR after creating an ECS, log in to the CBR console, locate the target vault, and associate it with the ECS.
To back up data for a created ECS:
You can use the cloud server backup and cloud disk backup to back up your ECS data.
diff --git a/docs/ecs/umn/en-us_topic_0000001210472883.html b/docs/ecs/umn/en-us_topic_0000001210472883.html index 367291776..8bcf0f015 100644 --- a/docs/ecs/umn/en-us_topic_0000001210472883.html +++ b/docs/ecs/umn/en-us_topic_0000001210472883.html @@ -3,7 +3,7 @@How Can I Install a GUI on an ECS Running Debian?
-Scenarios
To provide a pure system, the ECSs running Debian do not have a GUI installed by default. You can install a GUI on such ECSs as needed.
Constraints
- The operations described in this section apply to ECSs running Debian 8, Debian 9, or Debian 10 only.
- Before installing a GUI on an ECS, ensure that the memory is no less than 2 GB to prevent GUI installation or ECS startup failures.
Constraints
- The operations described in this section apply to ECSs running Debian 8, Debian 9, or Debian 10 only.
- Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
Procedure
- Log in to the ECS and run the following command to update the software library:
- Run the following command to upgrade the software library: diff --git a/docs/ecs/umn/en-us_topic_0000001278335673.html b/docs/ecs/umn/en-us_topic_0000001278335673.html index 90a04e82f..3aeb3f856 100644 --- a/docs/ecs/umn/en-us_topic_0000001278335673.html +++ b/docs/ecs/umn/en-us_topic_0000001278335673.html @@ -6,7 +6,7 @@
Scenarios
When purchasing an ECS, you are advised to select the key pair login mode. For Windows ECSs, key pairs are required to decrypt the passwords so that you can use the decrypted password to log in.
- Logging in to a Linux ECS
You can directly use a key pair to log in a Linux ECS.
--- During the ECS creation, select the key pair login mode. For details, see "Set Login Mode" in Step 3: Configure Advanced Settings.
- After the ECS is created, bind a key pair to the ECS by referring to "Binding a Key Pair" in the Data Encryption Workshop User Guide.
- During the ECS creation, select the key pair login mode. For details, see "Set Login Mode" in Step 3: Configure Advanced Settings.
- After the ECS is created, bind a key pair to the ECS by referring to "Binding a Key Pair" in the Data Encryption Workshop User Guide.
- Logging in to a Windows ECS
You can use the key pair to obtain a password for login. The password is randomly generated and is more secure.
diff --git a/docs/ecs/umn/en-us_topic_0000001547370984.html b/docs/ecs/umn/en-us_topic_0000001547370984.html index 19d2b9938..66b03d689 100644 --- a/docs/ecs/umn/en-us_topic_0000001547370984.html +++ b/docs/ecs/umn/en-us_topic_0000001547370984.html @@ -26,13 +26,13 @@
inotify Watch Limit Reached
If inotify watches are used up, "No space left on device" will be displayed.
+Value of fs.inotify.max_user_watches Reached
If inotify watches are used up, "No space left on device" will be displayed.
Solution
- Run the following command to edit the /etc/sysctl.conf file:
vi /etc/sysctl.conf
- Add the following content to the file:
fs.inotify.max_user_watches = 524288
- Run the following command for the modification to take effect:
-
inotify is used to monitor file system events. By default, a maximum of 8192 files can be watched for each real user ID. You can run the following command to obtain the current limit:
+inotify is used to monitor file system events. By default, a maximum of 8,192 files can be watched for each real user ID. You can run the following command to obtain the current limit:
cat /proc/sys/fs/inotify/max_user_watches
If the limit is too low to watch all files, increase the limit.
diff --git a/docs/ecs/umn/en-us_topic_0000001597810477.html b/docs/ecs/umn/en-us_topic_0000001597810477.html index f60c32aa3..dfac7b215 100644 --- a/docs/ecs/umn/en-us_topic_0000001597810477.html +++ b/docs/ecs/umn/en-us_topic_0000001597810477.html @@ -3,7 +3,7 @@How Do I Fix File Creation Failures Due to Inode Exhaustion?
-Symptom
When you create a file or directory, you get the error message "No space left on device", "Cannot create directory", or "Couldn't create temporary archive name."
-Possible Cause
In Linux, both of the following use the disk space:
+Possible Causes
In Linux, both of the following use the disk space:
- Data
- Inode
diff --git a/docs/ecs/umn/en-us_topic_0000001630328828.html b/docs/ecs/umn/en-us_topic_0000001630328828.html index 0beebee3b..eddf11ab6 100644 --- a/docs/ecs/umn/en-us_topic_0000001630328828.html +++ b/docs/ecs/umn/en-us_topic_0000001630328828.html @@ -82,7 +82,7 @@
An inode (index node) stores metadata of a file system object, such as a file, directory, device file, socket, and pipe in the file system, but does not contain the object's data and filename.
Procedure
- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
The ECS console is displayed.
+Procedure
- Log in to the management console.
- Under Computing, choose Elastic Cloud Server.
The ECS console is displayed.
- In the search box, specify search criteria.
You can use either of the following methods:
- Directly enter a property value for search.
- Select a property first and specify the property value for search.
- Click the search box and select a property.Figure 1 Selecting a property
- Specify a property value and press Enter to search.
Modifying Specifications of Individual ECSs
-Scenarios
If the ECS specifications do not meet service requirements, you can modify the ECS specifications, including vCPUs and memory. Certain ECSs allow you to change their types when you modify their specifications.
+Scenarios
If the ECS specifications do not meet service requirements, you can modify the specifications, including vCPUs and memory. Certain ECSs allow you to change their types when you modify their specifications.
-Background
To obtain the virtualization type of an ECS, perform the following operations:
- On the page providing details about the ECS, view the ECS specifications.Figure 1 Viewing ECS specifications
- Check the specifications tables in ECS Types for the virtualization type.
Notes
- The ECS needs to be stopped during the specification modification, so you are advised to perform this operation during off-peak hours.
- During the specification modification, do not perform any operation on the ECS, such as stopping or restarting the ECS. Otherwise, the modification will fail.
- Downgrading ECS specifications (vCPUs or memory) will reduce performance.
- Certain ECS types do not support specifications modification. For details about available ECS types and functions, see ECS Types. For details about constraints on using different types of ECSs, see their notes.
- When the disk status is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.
- Before modifying the specifications of a Windows ECS, modify the SAN policy by following the instructions provided in Why Does a Disk Attached to a Windows ECS Go Offline? to prevent disks from going offline after the specifications are modified.
- Before modifying specifications, make sure that the ECS has been stopped.
Notes
- The ECS needs to be stopped during the specification modification, so you are advised to perform this operation during off-peak hours.
- During the specification modification, do not perform any operation on the ECS, such as stopping or restarting the ECS. Otherwise, the modification will fail.
- Downgrading ECS specifications (vCPUs or memory) will reduce performance.
- Certain ECS types do not support specifications modification. For details about ECS types and functions, see ECS Specifications. For details about constraints on using different types of ECSs, see their notes.
- When the disk status is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.
- Before modifying the specifications of a Windows ECS, modify the SAN policy by following the instructions provided in Why Does a Disk Attached to a Windows ECS Go Offline? to prevent disks from going offline after the specifications are modified.
- Before modifying specifications, make sure that the ECS has been stopped.
Step 1: Modify Specifications
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, view the status of the target ECS.
If the ECS is not in Stopped state, choose More > Stop in the Operation column.
- Choose More > Modify Specifications in the Operation column.
The Modify ECS Specifications page is displayed.
diff --git a/docs/ecs/umn/en-us_topic_0013771110.html b/docs/ecs/umn/en-us_topic_0013771110.html index df7de8616..9d0497f2d 100644 --- a/docs/ecs/umn/en-us_topic_0013771110.html +++ b/docs/ecs/umn/en-us_topic_0013771110.html @@ -5,24 +5,24 @@- To prevent a sudden load increase, you are advised to start or stop a small number of ECSs at a time.
- If an ECS remains in the Restarting or Stopping state for a long time, you can forcibly restart or stop it. In such a case, any unsaved data on the ECS will be lost. Therefore, exercise caution when forcibly restarting or stopping an ECS.
- For bare metal ECSs (with physical flavors) such as C7t ECSs, do not run commands such as shutdown, poweoff, or half in the OS because the commands may be invalid or the ECS may fail to be started after being stopped.
Starting ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Start in the upper left corner of the list.
- In the displayed window, click OK.
Contact the administrator if the ECS has been in the Starting state for more than 30 minutes.
+-Starting ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Start in the upper left corner of the list.
- In the displayed window, click OK to start the selected ECSs.
Contact the administrator if the ECS has been in the Starting state for more than 30 minutes.
Stopping ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Stop in the upper left corner of the list.
- In the displayed dialog box, select Forcibly stop the preceding ECSs based on your service requirements.
After an ECS is forcibly stopped, unsaved data on the ECS will be lost.
+Stopping ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Stop in the upper left corner of the list.
- In the displayed dialog box, select Forcibly stop the preceding ECSs based on your service requirements.-
After an ECS is forcibly stopped, unsaved data on the ECS will be lost.
ECSs with physical flavors, such as C7t ECSs, only support the force stop option. Ensure that you have saved all files on those ECSs.
- Click OK to stop the ECSs. -
Contact the administrator if the ECS has been in the Stopping state for more than 30 minutes.
+- Click OK to stop the selected ECSs.
Contact the administrator if the ECS has been in the Stopping state for more than 30 minutes.
Restarting ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Restart in the upper left corner of the list.
After an ECS is forcibly restarted, unsaved data on the ECS will be lost.
+Restarting ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Restart in the upper left corner of the list.-
After an ECS is forcibly restarted, unsaved data on the ECS will be lost.
- Click OK to stop the ECSs. -
Contact the administrator if the ECS has been in the Restarting state for more than 30 minutes.
+- Click OK to restart the selected ECSs.
Contact the administrator if the ECS has been in the Restarting state for more than 30 minutes.
Deleting an ECS
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Delete in the upper left corner of the list.
Contact the administrator if the ECS has been in the Deleting state for more than 30 minutes.
+diff --git a/docs/ecs/umn/en-us_topic_0017130261.html b/docs/ecs/umn/en-us_topic_0017130261.html index fcad0dc0e..5de55e914 100644 --- a/docs/ecs/umn/en-us_topic_0017130261.html +++ b/docs/ecs/umn/en-us_topic_0017130261.html @@ -1,10 +1,10 @@ -Deleting an ECS
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Choose More > Delete in the upper left corner of the list.
Contact the administrator if the ECS has been in the Deleting state for more than 30 minutes.
Viewing ECS Details (List View)
+Viewing ECS Details
-Scenarios
After obtaining ECSs, you can view and manage them on the management console. This section describes how to view ECS configuration details, including its name, image, system disk, data disks, VPC, network interfaces, security group, EIP address, and bandwidth.
To view the private IP address of an ECS, view it on the Elastic Cloud Server page.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
The Elastic Cloud Server page is displayed. On this page, you can view your ECSs and the basic information about the ECSs, such as their specifications, images, and IP addresses.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
The Elastic Cloud Server page is displayed. On this page, you can view the ECSs you have created as well as their details such as the specifications, images, and IP addresses.
- In the search box above the ECS list, select a filter (such as ECS name, ID, or private IP address), enter the corresponding information, and press Enter.
- Click the name of the target ECS.
The page providing details about the ECS is displayed.
- View the ECS details.
You can click the tabs and perform operations. For details, see Changing a Security Group, Attaching a Network Interface, Adding Tags, and Binding an EIP.
Logging In to a Linux ECS Using an SSH Key Pair
-Scenarios
This section describes how to use an SSH key pair to remotely log in to a Linux ECS from a Windows and a Linux server, respectively.
Prerequisites
- You have obtained the private key file used for creating the ECS. For details about how to create a key pair, see (Recommended) Creating a Key Pair on the Management Console.
- You have bound an EIP to the ECS. For details, see Viewing ECS Details (List View).
Prerequisites
- You have obtained the private key file used for creating the ECS. For details about how to create a key pair, see (Recommended) Creating a Key Pair on the Management Console.
- You have bound an EIP to the ECS. For details, see Viewing ECS Details.
- You have configured the inbound rules of the security group. For details, see Configuring Security Group Rules.
- The network connection between the login tool (PuTTY) and the target ECS is normal. For example, the default port 22 is not blocked by the firewall.
Logging In to a Linux ECS from a Local Windows Server
You have two methods to log in to a Linux ECS from a local Windows server.
diff --git a/docs/ecs/umn/en-us_topic_0017955381.html b/docs/ecs/umn/en-us_topic_0017955381.html index 2bfdde3f6..12c4d6035 100644 --- a/docs/ecs/umn/en-us_topic_0017955381.html +++ b/docs/ecs/umn/en-us_topic_0017955381.html @@ -3,20 +3,20 @@Logging In to a Windows ECS Using MSTSC
-Scenarios
This section describes how to use the remote login tool MSTSC to log in to a Windows ECS from a local computer.
Prerequisites
- The target ECS is running.
- You have obtained the password for logging in to the Windows ECS. For details, see Obtaining the Password for Logging In to a Windows ECS.
- You have bound an EIP to the ECS. For details, see Binding an EIP.
Prerequisites
- The target ECS is running.
- You have obtained the password for logging in to the Windows ECS. For details, see Obtaining the Password for Logging In to a Windows ECS.
- You have bound an EIP to the ECS. For details, see Binding an EIP.
- Access to port 3389 is allowed in the inbound direction of the security group which the ECS belongs to. For details, see Configuring Security Group Rules.
- The network connection between the login tool and the target ECS is normal. For example, the default port 3389 is not blocked by the firewall.
- Remote Desktop Protocol (RDP) needs to be enabled on the target ECS. For ECSs created using public images, RDP has been enabled by default. For instructions about how to enable RDP, see Enabling RDP.
Logging In to a Windows ECS Using MSTSC
If your local server runs Windows, you can use the remote desktop connection tool MSTSC delivered with the Windows OS to log in to a Windows ECS.
-- Click the start menu on the local server.
- In the Search programs and files text box, enter mstsc.
- In the Remote Desktop Connection dialog box, click Show Options.Figure 1 Show Options+
- Click the start menu on the local server.
- In the Search programs and files text box, enter mstsc.
- In the Remote Desktop Connection dialog box, click Show Options.Figure 1 Showing options
- Enter the EIP and username (Administrator by default) of the target ECS.
If you do not want to enter the username and password in follow-up logins, select Allow me to save credentials.
Figure 2 Remote Desktop Connection-
- (Optional) To use local server resources in a remote session, configure parameters on the Local Resources tab.To copy data from the local server to your ECS, select Clipboard.Figure 3 Clipboard+
- (Optional) To use local server resources in a remote session, configure parameters on the Local Resources tab.
To copy data from the local server to your ECS, select Clipboard.-Figure 3 ClipboardTo copy files from the local server to your ECS, click More and select your desired disks.diff --git a/docs/ecs/umn/en-us_topic_0018073212.html b/docs/ecs/umn/en-us_topic_0018073212.html index ab4bdf61b..bdee6b3dc 100644 --- a/docs/ecs/umn/en-us_topic_0018073212.html +++ b/docs/ecs/umn/en-us_topic_0018073212.html @@ -2,7 +2,7 @@Figure 4 Drives+
To copy files from the local server to your ECS, click More and select your desired disks.Figure 4 Drives- (Optional) Click the Display tab and then adjust the size of the remote desktop.
Figure 5 Adjusting the size of the desktop-
- Click Connect and enter the login password as prompted to log in to the ECS.
To ensure system security, change the login password after you log in to the ECS for the first time.
+- Click Connect and enter the login password as prompted to log in to the ECS.
To ensure system security, change the login password after you log in to the ECS for the first time.
- (Optional) Copy local files to the Windows ECS using clipboard. If the file size is greater than 2 GB, an error will occur.
To resolve this issue, see troubleshooting cases.
How Quickly Can I Obtain an ECS?
diff --git a/docs/ecs/umn/en-us_topic_0018073216.html b/docs/ecs/umn/en-us_topic_0018073216.html index c3357d1ee..4b2c72f67 100644 --- a/docs/ecs/umn/en-us_topic_0018073216.html +++ b/docs/ecs/umn/en-us_topic_0018073216.html @@ -2,7 +2,7 @@Obtaining an ECS can take as little as a few minutes.
-The time it takes to obtain an ECS depends on ECS specifications, available resources (such as EVS disks and EIPs), and system load.
+The time it takes to obtain an ECS depends on ECS specifications, available resources (such as EVS disks and EIPs), and system load.
If it takes a long time to obtain your ECS, contact customer service.
Can Multiple EIPs Be Bound to an ECS?
diff --git a/docs/ecs/umn/en-us_topic_0018073221.html b/docs/ecs/umn/en-us_topic_0018073221.html index 7fdef8e02..323805d20 100644 --- a/docs/ecs/umn/en-us_topic_0018073221.html +++ b/docs/ecs/umn/en-us_topic_0018073221.html @@ -3,7 +3,7 @@Scenarios
Multiple EIPs can be bound to an ECS, but this operation is not recommended.
-If an ECS has multiple NICs attached and you want to bind multiple EIPs to this ECS, you need to configure policy-based routes for these NICs so that these extension NICs can communicate with external networks. For details, see Configuration Example.
+If an ECS has multiple network interfaces attached and you want to bind multiple EIPs to this ECS, you need to configure policy-based routes for these network interfaces so that these extension network interfaces can communicate with external networks. For details, see Configuration Example.
Configuration Example
Table 1 lists ECS configurations.
@@ -51,7 +51,7 @@ Exercise caution when deleting the default route because this operation will interrupt the network and result in SSH login failures.
- Run the following command to configure a new default route:
ip route add 0.0.0.0/0 dev eth1 via 192.168.2.1
-In the preceding command, 192.168.2.1 is the gateway IP address of standby NIC eth1.
+In the preceding command, 192.168.2.1 is the gateway IP address of standby NIC eth1.
Can a Deleted ECS Be Provisioned Again?
No. ECSs in the Deleted state cannot provide services and are soon removed from the system.
A deleted ECS is retained in the ECS list on the management console only for a short period of time before it is permanently removed from the system.
-You can create a new ECS with the same specifications again.
+You can create another ECS of the same specifications.
diff --git a/docs/ecs/umn/en-us_topic_0018078503.html b/docs/ecs/umn/en-us_topic_0018078503.html index 7078a9c73..9cd791c28 100644 --- a/docs/ecs/umn/en-us_topic_0018078503.html +++ b/docs/ecs/umn/en-us_topic_0018078503.html @@ -3,7 +3,7 @@Will My ECSs Be Deployed in the Same Subnet?
You can configure whether ECSs are in the same subnet when creating them.
When creating ECSs, you can set a VPC and primary network interface to customize the subnet for the ECSs.
-You can also create a VPC and subnet in advance and deploy the ECSs in that subnet when creating ECSs.
+You can also create a VPC and subnet in advance and deploy the ECSs in that subnet when creating ECSs.
diff --git a/docs/ecs/umn/en-us_topic_0018078505.html b/docs/ecs/umn/en-us_topic_0018078505.html index a1fa832e9..1b75e7a8f 100644 --- a/docs/ecs/umn/en-us_topic_0018078505.html +++ b/docs/ecs/umn/en-us_topic_0018078505.html @@ -1,7 +1,7 @@Why Can I Remotely Access an ECS But Cannot Ping It?
-Symptom
You can remotely access an ECS but when you ping the EIP bound to the ECS, the ping operation fails.
+Symptom
You can remotely access an ECS, but when you ping the EIP bound to the ECS, the ping operation fails.
diff --git a/docs/ecs/umn/en-us_topic_0018078523.html b/docs/ecs/umn/en-us_topic_0018078523.html index 4c0cb35b4..1e71c96d7 100644 --- a/docs/ecs/umn/en-us_topic_0018078523.html +++ b/docs/ecs/umn/en-us_topic_0018078523.html @@ -2,7 +2,7 @@Possible Causes
A desired inbound rule is not added for the security group, and ICMP is not enabled.
Do ECSs Support GUI?
diff --git a/docs/ecs/umn/en-us_topic_0021831611.html b/docs/ecs/umn/en-us_topic_0021831611.html index 71871c6ab..18aaa37d2 100644 --- a/docs/ecs/umn/en-us_topic_0021831611.html +++ b/docs/ecs/umn/en-us_topic_0021831611.html @@ -1,6 +1,6 @@ -Windows ECSs are managed through a GUI but Linux ECSs are managed through the CLI. You can configure a GUI if required.
-Before installing a GUI on an ECS, ensure that the memory is no less than 2 GiB to prevent GUI installation or ECS startup failures.
+Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GiB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
For details about how to install a Linux OS on the GUI, see the following:Creating an ECS
+Creating an ECS
-
diff --git a/docs/ecs/umn/en-us_topic_0024911405.html b/docs/ecs/umn/en-us_topic_0024911405.html
index 95b38d719..2e053fa11 100644
--- a/docs/ecs/umn/en-us_topic_0024911405.html
+++ b/docs/ecs/umn/en-us_topic_0024911405.html
@@ -10,10 +10,10 @@
-Prerequisites
- The target ECS is stopped.
- The target ECS has a system disk attached.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
Only stopped ECSs support OS reinstallation. If the ECS is not stopped, stop it before proceeding with reinstallation.
- - (Optional) Select the Encrypted option to encrypt the system disk during OS reinstallation.
To enable encryption, click Create Xrole to assign KMS access permissions to EVS. If you have rights granting permissions, assign the KMS access permissions to EVS. If you do not have the required permissions, contact the user who has the Security Administrator permissions to assign the KMS access permissions. For details, see Can All Users Use the Encryption Feature?
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
Only stopped ECSs support OS reinstallation. If the ECS is not stopped, stop it before proceeding with reinstallation.
+ - (Optional) Select the Encrypted option to encrypt the system disk during OS reinstallation.
To enable encryption, click Create Xrole to grant KMS access permissions to EVS. If you have the granting permission, grant KMS access permissions to EVS. If you do not have the granting permission, contact the user who has the Security Administrator permissions to grant KMS access permissions. For details, see Can All Users Use the Encryption Feature?
Encryption parameters are as follows:
-- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- (Optional) Select a License Type (Use license from the system or Bring your own license (BYOL)) if the reinstalled OS running on your ECS is billed. For more details, see License Types.
The following OSs are billed:
- SUSE Linux Enterprise Server
- Oracle Enterprise Linux
- Red Hat Enterprise Linux
- Select the login mode.
If the target ECS uses key pair authentication, you can replace the original key pair.
diff --git a/docs/ecs/umn/en-us_topic_0027157850.html b/docs/ecs/umn/en-us_topic_0027157850.html index 0cd71a98a..778288663 100644 --- a/docs/ecs/umn/en-us_topic_0027157850.html +++ b/docs/ecs/umn/en-us_topic_0027157850.html @@ -30,7 +30,7 @@- If the sysctl.conf file does not contain the net.ipv4.ip_forward parameter, run the following command to add it:
echo net.ipv4.ip_forward=1 >> /etc/sysctl.conf
- Press Esc, type :wq, and press Enter.
The system saves the configurations and exits the vi editor.
+ - Press Esc, type :wq, and press Enter.
The system saves the configurations and exits the vi editor.
- Apply the change.
- Delete the original iptables rules.
- Configure source network address translation (SNAT) to enable ECSs in the same network segment to access the Internet through the proxy ECS.
iptables -t nat -A POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
@@ -43,7 +43,7 @@ - Check whether SNAT has been configured.
SNAT has been configured if information similar to Figure 2 is displayed.
- - Add a route.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Network, click Virtual Private Cloud.
- Choose Route Tables in the left navigation pane. In the route table list, click a target route table. On the displayed page, click Add Route.
- Set route information on the displayed page.
- Destination: indicates the destination network segment. The default value is 0.0.0.0/0.
- Next Hop: indicates the private IP address of the proxy ECS.
You can obtain the private IP address of the ECS on the Elastic Cloud Server page.
+ - Add a route.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Network, click Virtual Private Cloud.
- Choose Route Tables in the left navigation pane. In the route table list, click a target route table. On the displayed page, click Add Route.
- Set route information on the displayed page.
- Destination: indicates the destination network segment. The default value is 0.0.0.0/0.
- Next Hop: indicates the private IP address of the proxy ECS.
You can obtain the private IP address of the ECS on the Elastic Cloud Server page.
- Delete the added iptables rules as needed.
iptables -t nat -D POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
diff --git a/docs/ecs/umn/en-us_topic_0027371531.html b/docs/ecs/umn/en-us_topic_0027371531.html index 624b811b6..0308dff4e 100644 --- a/docs/ecs/umn/en-us_topic_0027371531.html +++ b/docs/ecs/umn/en-us_topic_0027371531.html @@ -4,8 +4,8 @@-Scenarios
Setting ECS alarm rules allows you to customize the monitored objects and notification policies so that you can closely monitor your ECSs.
This section describes how to set ECS alarm rules, including alarm rule names, monitoring objects, monitoring metrics, alarm thresholds, monitoring intervals, and notifications.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Management & Deployment, choose Cloud Eye.
- In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the Alarm Rules page, click Create Alarm Rule to create an alarm rule, or modify an existing alarm rule.
The following uses modifying an existing alarm rule as an example.
-- Click the target alarm rule.
- Click Modify in the upper right corner of the page.
- In the Modify Alarm Rule dialog box shown in Figure 1, set the parameters as prompted.
+
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Management & Deployment, choose Cloud Eye.
- In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the Alarm Rules page, click Create Alarm Rule to create an alarm rule, or modify an existing alarm rule.
The following uses modifying an existing alarm rule as an example.
+- Click the target alarm rule.
- Click Modify in the upper right corner of the page.
- In the Modify Alarm Rule dialog box shown in Figure 1, set the parameters as prompted.
- Click Modify.
After an alarm rule is modified, the system automatically notifies you of an alarm when the alarm complying with the alarm rule is generated.
For more information about ECS alarm rules, see Cloud Eye User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0030013188.html b/docs/ecs/umn/en-us_topic_0030013188.html index bba75e32e..7a181b5ee 100644 --- a/docs/ecs/umn/en-us_topic_0030013188.html +++ b/docs/ecs/umn/en-us_topic_0030013188.html @@ -3,9 +3,9 @@Can an ECS Without an EIP Bound Access the Internet?
Yes.
- Method 1: Configure a SNAT server.
You can configure the SNAT server so that the ECS without an EIP bound can access the Internet.
-For details, see "Configuring an SNAT Server" in Virtual Private Cloud User Guide.
+For details, see "Configuring an SNAT Server" in Virtual Private Cloud User Guide.
- Method 2: Create a NAT gateway.
If a large number of concurrent connections are required, it is a good practice to use the NAT Gateway service provided by the cloud platform.
-The NAT Gateway service offers the NAT function for ECSs in a VPC, allowing these ECSs to access the Internet using an EIP. For more information about NAT Gateway, see NAT Gateway User Guide.
+The NAT Gateway service offers the network address translation (NAT) function for ECSs in a VPC, allowing these ECSs to access the Internet using an EIP. The SNAT function provided by the NAT Gateway service allows the ECSs in a VPC to access the Internet without requiring an EIP. Additionally, SNAT supports a large number of concurrent connections for applications that have a large number of requests and connections. For more information about NAT Gateway, see NAT Gateway User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0030828254.html b/docs/ecs/umn/en-us_topic_0030828254.html index c98149c82..25867c66f 100644 --- a/docs/ecs/umn/en-us_topic_0030828254.html +++ b/docs/ecs/umn/en-us_topic_0030828254.html @@ -26,7 +26,7 @@Shared
A shared image is a private image another user has shared with you.
-For more information, see "Sharing Images" in Image Management Service User Guide.
+For more information, see "Sharing Images" in Image Management Service User Guide.
-
-
- Viewing ECS Creation Statuses
+ - Viewing the ECS Creation Status
- Viewing Failed Tasks
- - Viewing ECS Details (List View)
+ - Viewing ECS Details
- Exporting ECS Information
diff --git a/docs/ecs/umn/en-us_topic_0030911465.html b/docs/ecs/umn/en-us_topic_0030911465.html
index 276898de0..d219db721 100644
--- a/docs/ecs/umn/en-us_topic_0030911465.html
+++ b/docs/ecs/umn/en-us_topic_0030911465.html
@@ -5,7 +5,7 @@
-Namespace
SYS.ECS
Basic ECS Metrics
Basic ECS metrics vary depending on ECS OSs and types. For details, see Table 1.
+Basic ECS Metrics
Basic ECS metrics vary depending on ECS OSs and types. For details, see Table 1.
@@ -304,8 +304,8 @@ To monitor the memory usage and disk usage, you need to install the Agent on your ECS.- For details about how to install the Agent on a Windows ECS, see Installing and Configuring the Agent on a Windows Server.
- For details about how to install the Agent on a Linux ECS, see Installing the Agent on a Linux Server.
InfiniBand NIC status
Status of an InfiniBand NIC on an H2 ECS
-The system periodically checks the status and returns check results using value 0 or 1.
-- 0: The system is running properly. That is, the InfiniBand NIC is functional.
- 1: The system is not running properly. That is, the InfiniBand NIC malfunctions. When the physical NIC corresponding to a virtual NIC becomes faulty, for example, the network cable is not securely connected to the NIC, the switch or adapter is incompatible with the InfiniBand NIC, or the NIC is disabled, the returned value is 1.
The system periodically checks the status and returns check results using value 0 or 1.
+- 0: The system is running properly. That is, the InfiniBand NIC is functional.
- 1: The system is not running properly. That is, the InfiniBand NIC malfunctions. When the physical NIC corresponding to a virtual NIC becomes faulty, for example, the network cable is not securely connected to the NIC, the switch or adapter is incompatible with the InfiniBand NIC, or the NIC is disabled, the returned value is 1.
NOTE:Only Mellanox EDR 100 GB single-port InfiniBand NICs are supported.
Obtaining the Password for Logging In to a Windows ECS
-Scenarios
Password authentication is required to log in to a Windows ECS. You must use the key file used when you created the ECS to obtain the administrator password generated during ECS creation. The administrator user is Administrator or the user configured using Cloudbase-Init. This password is randomly generated, offering high security.
-You can obtain the initial password for logging in to a Windows ECS through the management console or APIs. For details, see this section.
+You can obtain the initial password for logging in to a Windows ECS through the management console or APIs. For details, see this section.
Obtaining the Password Through the Management Console
- Obtain the private key file (.pem file) used when you created the ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Get Password.Figure 1 Get Password+
+Prerequisites
You have obtained the private key file (.pem file) which was generated during the ECS creation.
+-Obtaining the Password Through the Management Console
- Obtain the private key file (.pem file) used when you created the ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Get Password.Figure 1 Get Password
- Use either of the following methods to obtain the password through the key file:
- Click Select File and upload the key file from a local directory.
- Copy the key file content to the text field.
- Click Get Password to obtain a random password.
Obtaining the Password Through APIs
- Obtain the private key file (.pem file) used when you created the ECS.
- Set up the API calling environment.
- Call APIs. For details, see API Usage Guidelines in Elastic Cloud Server API Reference.
- Obtain the ciphertext password.
Call the password obtaining APIs to obtain the ciphertext password of the public key encrypted using RSA. The API URI is in the format "GET /v2/{project_id}/servers/{server_id}/os-server-password".
+Obtaining the Password Through APIs
- Obtain the private key file (.pem file) used when you created the ECS.
- Set up the API calling environment.
- Call APIs. For details, see API Usage Guidelines in the Elastic Cloud Server API Reference.
- Obtain the ciphertext password.
Call the password obtaining APIs to obtain the ciphertext password of the public key encrypted using RSA. The API URI is in the format "GET /v2/{project_id}/servers/{server_id}/os-server-password".
- Decrypt the ciphertext password.
Use the private key file used when you created the ECS to decrypt the ciphertext password obtained in step 4.
diff --git a/docs/ecs/umn/en-us_topic_0031523135.html b/docs/ecs/umn/en-us_topic_0031523135.html index 64fe1c8fd..788f3a35f 100644 --- a/docs/ecs/umn/en-us_topic_0031523135.html +++ b/docs/ecs/umn/en-us_topic_0031523135.html @@ -7,7 +7,7 @@
-Constraints
- The OS change takes about 1 to 4 minutes During this process, the ECS status is Changing OS.
- Do not perform any operations on the ECS before the system injects the password or key, or the login will fail.
- The ECS for which you want to change the OS must be in any of the following states: Stopped, Reinstallation failed, or Failed to change the OS.
- The target ECS must have a system disk attached.
- The EVS disk quota must be greater than 0.
- The system disk type cannot be changed.
- The system disk can be encrypted.
- For details about the change between different OSs, see Notes on Change Between Windows and Linux.
- If an ECS OS is to be changed using a full-ECS image, the ECS system disk can be encrypted.
-Notes
- After the OS is changed, the original OS is not retained, and the original system disk is deleted, including the data in all partitions of the system disk.
- Changing the OS clears the data in all partitions of the system disk, including the system partition. Back up data before changing the OS.
- Changing the OS does not affect data in data disks.
- After the OS is changed, your service running environment must be deployed in the new OS again.
- After the OS is changed, the ECS will be automatically started.
- After the OS is changed, the system disk type of the ECS cannot be changed.
- After the OS is changed, the IP and MAC addresses of the ECS remain unchanged.
- After the OS is changed, customized configurations, such as DNS and hostname of the original OS will be reset and require reconfiguration.
- It takes about 10 to 20 minutes to change the OS. During this process, the ECS is in Changing OS state.
- After the OS is changed, the password for logging in to the ECS is reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Logging In to a Linux ECS Using an SSH Key Pair.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
@@ -21,16 +21,16 @@Notes
- After the OS is changed, the original OS is not retained, and the original system disk is deleted, including the data in all partitions of the system disk.
- Changing the OS clears the data in all partitions of the system disk, including the system partition. Back up data before changing the OS.
- Changing the OS does not affect data in data disks.
- After the OS is changed, your service running environment must be deployed in the new OS again.
- After the OS is changed, the ECS will be automatically started.
- After the OS is changed, the system disk type of the ECS cannot be changed.
- After the OS is changed, the IP and MAC addresses of the ECS remain unchanged.
- After the OS is changed, customized configurations, such as DNS and hostname of the original OS will be reset and require reconfiguration.
- An OS change takes about 1 to 4 minutes to complete. During this process, the ECS is in Changing OS state.
- After the OS is changed, the password for logging in to the ECS is reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Logging In to a Linux ECS Using an SSH Key Pair.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
- The system disk capacity of an ECS with OS changed may change because the system disk capacity specified by the image of the changed OS may be changed.
- You can choose to encrypt the system disk of an ECS during OS change.
- If you plan to use a private image to change the OS, ensure that a private image is available. For details about how to create a private image, see Image Management Service User Guide.
- If the image of a specified ECS is required, make sure that a private image has been created using this ECS.
- If a local image file is required, make sure that the image file has been imported to the cloud platform and registered as a private image.
- If a private image from another region is required, make sure that the image has been copied.
- If a private image from another user account is required, make sure that the image has been shared with you.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Change OS in the Operation column.
Only stopped ECSs support OS change. If the ECS is not stopped, stop it before proceeding with changing.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Change OS in the Operation column.
Only stopped ECSs support OS change. If the ECS is not stopped, stop it before proceeding with changing.
- Select the target image.
For details, see Creating an ECS.
Figure 1 Changing an OS-
- (Optional) Select the Encryption option to encrypt the system disk during OS change.
To enable encryption, click Create Xrole to assign KMS access permissions to EVS. If you have rights granting permissions, assign the KMS access permissions to EVS. If you do not have the required permissions, contact the user who has the Security Administrator permissions to assign the KMS access permissions. For details, see Can All Users Use the Encryption Feature?
+ - (Optional) Select the Encryption option to encrypt the system disk during OS change.
To enable encryption, click Create Xrole to grant KMS access permissions to EVS. If you have the granting permission, grant KMS access permissions to EVS. If you do not have the granting permission, contact the user who has the Security Administrator permissions to grant KMS access permissions. For details, see Can All Users Use the Encryption Feature?
Encryption parameters are as follows:
-- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- (Optional) Select a License Type (Use license from the system or Bring your own license (BYOL)) if the changed OS running on your ECS is billed. For more details, see License Types.The following OSs are billed:
- SUSE Linux Enterprise Server
- Oracle Enterprise Linux
- Red Hat Enterprise Linux
- Configure the login mode.
If the target ECS uses key pair authentication, you can replace the original key pair.
- - Click OK.
- In the Change ECS OS dialog box, confirm the specifications, and click Submit.
After the application is submitted, the status Changing OS is displayed. When this status disappears, the OS change is complete.
+ - Click OK.
- In the Change ECS OS dialog box, confirm the specifications, and click Submit.
After the application is submitted, the ECS status changes to Changing OS. When this status disappears, the OS change is complete.
During the OS change process, a temporary ECS is created. After the OS change is complete, this ECS will be automatically deleted.
diff --git a/docs/ecs/umn/en-us_topic_0032380449.html b/docs/ecs/umn/en-us_topic_0032380449.html index ad884d5d6..3200b18df 100644 --- a/docs/ecs/umn/en-us_topic_0032380449.html +++ b/docs/ecs/umn/en-us_topic_0032380449.html @@ -71,7 +71,7 @@ echo "Hello, the time is now $(date -R)" | tee /root/output.txtSolution
- If the issue is a result of cause 1, proceed as follows:
If a private image is created without Cloudbase-Init installed, the ECS configuration cannot be customized. As a result, you can log in to the ECS only using the original image password.
The original image password is the OS password configured when the private image was created.
- - If the issue is a result of cause 2, proceed as follows:
- Locate the row containing the target ECS, click More in the Operation column, and select Restart.
- Click More in the Operation column and select Get Password to check whether the password can be obtained.
- If you can obtain the password, no further action is required.
- If you cannot obtain the password, contact customer service.
- If the issue is a result of cause 2, proceed as follows:
- Locate the row containing the target ECS, click More in the Operation column, and select Restart.
- After the reset, click More in the Operation column and choose Get Password to check whether the password can be obtained.
- If you can obtain the password, no further action is required.
- If you cannot obtain the password, contact customer service.
After the ECS is created, start it and run the cat [file] command to check the script execution result.
[root@XXXXXXXX ~]# cat /root/output.txt Hello, the time is now Mon, 16 Jul 2016 16:03:18+0800
-Example 2: Inject a Cloud-Config data script.
+Example 2: Inject a Cloud-Config data script.
When creating an ECS, set User Data to As text and enter the customized user data script.
#cloud-config bootcmd: diff --git a/docs/ecs/umn/en-us_topic_0032398121.html b/docs/ecs/umn/en-us_topic_0032398121.html index 284ed43a1..16d60265a 100644 --- a/docs/ecs/umn/en-us_topic_0032398121.html +++ b/docs/ecs/umn/en-us_topic_0032398121.html @@ -44,7 +44,7 @@
System error. Try again later or contact customer service.
Adjust the request structure as directed in Elastic Cloud Server API Reference.
+Adjust the request structure as instructed in Elastic Cloud Server API Reference.
Ecs.0010
diff --git a/docs/ecs/umn/en-us_topic_0032980085.html b/docs/ecs/umn/en-us_topic_0032980085.html index e2a14f35a..066fce732 100644 --- a/docs/ecs/umn/en-us_topic_0032980085.html +++ b/docs/ecs/umn/en-us_topic_0032980085.html @@ -9,19 +9,19 @@- Removing an ECS from an ECS Group
- Deleting an ECS Group
Creating an ECS Group
Create an ECS group and associate the same policy to all group members. ECS groups are independent from each other.
-- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- On the ECS Group page, click Create ECS Group.
- Enter the name of an ECS group.
- Select a policy for the ECS group.
- Click OK.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- On the ECS Group page, click Create ECS Group.
- Enter the name of an ECS group.
- Select a policy for the ECS group.
- Click OK.
Adding an ECS to an ECS Group
To improve service reliability, you can add ECSs to an ECS group so that these ECSs in this group can run on different hosts.
- - After an ECS is added to an ECS group, the system reallocates a host to run this ECS to ensure that ECSs in this group are running on different hosts. When the ECS is being restarted, the startup may fail due to insufficient resources. In such a case, remove the ECS from the ECS group and try to restart the ECS again.
- ECSs that have local disks attached can be added to an ECS group only during the creation process. Once created, they can no longer be added to any ECS groups.
- ECSs that have local disks, GPU cards, or FPGA cards attached can be added to an ECS group only during the creation process. Once created, they can no longer be added to any ECS groups.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the row that contains the target ECS group and click Add ECS in the Operation column.
- On the Add ECS page, select an ECS to be added.
- Click OK. The ECS is added to the ECS group.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the row that contains the target ECS group and click Add ECS in the Operation column.
- On the Add ECS page, select an ECS to be added.
- Click OK. The ECS is added to the ECS group.
Removing an ECS from an ECS Group
After an ECS is removed from an ECS group, the ECS does not comply with the ECS group policy anymore.
-- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Expand the ECS group information and view the ECSs in the ECS group.
- Locate the ECS to be removed and click Remove in the Operation column.
- In the displayed dialog box, click Yes.
The ECS is removed from the ECS group.
+- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Expand the ECS group information and view the ECSs in the ECS group.
- Locate the ECS to be removed and click Remove in the Operation column.
- In the displayed dialog box, click Yes.
The ECS is removed from the ECS group.
Deleting an ECS Group
After an ECS group is deleted, the policy does not apply to the ECSs in the ECS group anymore.
-- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the ECS group to be deleted and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the ECS group to be deleted and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
diff --git a/docs/ecs/umn/en-us_topic_0035643949.html b/docs/ecs/umn/en-us_topic_0035643949.html index e2b1f3fd0..50d57e755 100644 --- a/docs/ecs/umn/en-us_topic_0035643949.html +++ b/docs/ecs/umn/en-us_topic_0035643949.html @@ -1,30 +1,32 @@Application Scenarios for Using Passwords
-The password for logging in to your ECS is important and please keep it secure. You can reset the password if it is forgotten or expires.
+Passwords are used to log in to ECSs. If you select the password login mode when creating an ECS, you can use the username and password to log in to your ECS. The password is very important. Keep it secure.
+You can reset the password when:
+- You forgot the password.
- The password has expired.
- You selected Set password later during the ECS creation.
Table 1 provides guidance on how to reset your password in different scenarios.
-Table 1 Resetting a password Reference
+Table 1 Resetting a password Scenario
Prerequisites
+Prerequisites
+ N/A
+N/A
NOTE:The reference is for Windows or Linux ECSs.
+ The password reset plug-in has not been installed.
+The password reset plug-in has not been installed.
+ The password reset plug-in has not been installed.
+The password reset plug-in has not been installed.
Background
Table 2 shows the ECS password complexity requirements.
-Table 2 Password complexity requirements Parameter
+Table 2 Password complexity requirements Parameter
Requirement
+Requirement
Password
+Password
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Cannot contain the username or the username spelled backwards.
- Cannot contain more than two consecutive characters in the same sequence as they appear in the username. (This requirement applies only to Windows ECSs.)
-Possible Causes
The NIC driver has not been correctly installed.
Solution
Disk-intensive and large-memory ECSs use passthrough NICs to improve network performance. You must install the passthrough NIC driver on the ECSs or the image that is used for creating the ECSs.
- If you mount the CD/DVD-ROM driver over a VPN, ensure that the VPN bandwidth is greater than 8 Mbit/s.
++Solution
Disk-intensive and large-memory ECSs use passthrough network interfaces to improve network performance. You must install the passthrough network interface driver on the ECSs or the image that is used for creating the ECSs.
+- If you mount the CD/DVD-ROM driver over a VPN, ensure that the VPN bandwidth is greater than 8 Mbit/s.
To install the passthrough NICE driver, do as follows:
- Obtain the passthrough NIC driver.
Passthrough NIC driver versions vary depending on the OS. For details, see Table 1.
-Table 1 NIC driver versions and OSs NIC Driver Version
+-Table 1 NIC driver versions and OSs NIC Driver Version
OS
+OS
How to Obtain
+How to Obtain
ixgbevf 2.16.4
+ixgbevf 2.16.4
CentOS 7.2 64bit
+CentOS 7.2 64bit
https://sourceforge.net/projects/e1000/files/ixgbevf%20stable/2.16.4/
+https://sourceforge.net/projects/e1000/files/ixgbevf%20stable/2.16.4/
Red Hat Enterprise Linux 7.2 64bit
+Red Hat Enterprise Linux 7.2 64bit
ixgbevf 2.16.1
+ixgbevf 2.16.1
SUSE Linux Enterprise Server 11 SP3 64bit
+SUSE Linux Enterprise Server 11 SP3 64bit
SUSE Linux Enterprise Server 11 SP4 64bit
https://sourceforge.net/projects/e1000/files/ixgbevf%20stable/2.16.1/
+https://sourceforge.net/projects/e1000/files/ixgbevf%20stable/2.16.1/
Procedure
- Create an EVS disk according to the volume of data to be migrated.
- Attach the EVS disk created in 1 to the disk-intensive ECS for which you want to expand the capacity.
- Back up local disk data.
Back up the data stored in the local disks to the EVS disk that is newly attached to the disk-intensive ECS.
- For Windows ECSs, directly copy the data to be backed up to the EVS disk.
- For Linux ECSs, run the cp command to copy the data to be backed up to the EVS disk.
- Detach the EVS disk from the ECS.
- On the Elastic Cloud Server page, select this disk-intensive ECS and ensure that it has been stopped.
If the ECS is running, choose More > Stop to stop the ECS.
+ - Detach the EVS disk from the ECS.
- On the Elastic Cloud Server page, select this disk-intensive ECS and ensure that it has been stopped.
If the ECS is running, choose More > Stop to stop the ECS.
- Click the name of the disk-intensive ECS to go to the ECS details page.
- Click the Disks tab. Locate the row containing the EVS data disk and click Detach to detach the disk from the ECS.
- On the Elastic Cloud Server page, select this disk-intensive ECS and ensure that it has been stopped.
- Prepare a new disk-intensive ECS with higher specifications and larger capacity than the original one.
Ensure that the local disk capacity can meet your requirements.
- Attach the EVS disk to the new disk-intensive ECS.
On the Elastic Cloud Server page, click the name of the ECS described in step 5 to view details.
- Click the Disks tab. Then, click Attach Disk.
In the displayed dialog box, select the EVS disk detached in step 4 and the device name.
- - Migrate the data from the EVS disk in 7 to the local disks of the new disk-intensive ECS.
- On the Elastic Cloud Server page, select this disk-intensive ECS and ensure that it has been stopped.
- Migrate the data from the EVS disk in step 7 to the local disks of the new disk-intensive ECS.
diff --git a/docs/ecs/umn/en-us_topic_0037633087.html b/docs/ecs/umn/en-us_topic_0037633087.html index aa9f5828f..a5894870a 100644 --- a/docs/ecs/umn/en-us_topic_0037633087.html +++ b/docs/ecs/umn/en-us_topic_0037633087.html @@ -12,7 +12,7 @@diff --git a/docs/ecs/umn/en-us_topic_0038024694.html b/docs/ecs/umn/en-us_topic_0038024694.html index e0979df3e..8d896f5ac 100644 --- a/docs/ecs/umn/en-us_topic_0038024694.html +++ b/docs/ecs/umn/en-us_topic_0038024694.html @@ -2,7 +2,7 @@- Username: Administrator
- RID: 500
- LM-HASH value: C8825DB10F2590EAAAD3B435B51404EE
- NT-HASH value: 683020925C5D8569C23AA724774CE9CC
Use an image to create two ECSs, ecs01 and ecs02. Then, verify that the hash values of the cloudbase-init account for the two ECSs are different.
- LM-HASH and NTLM-HASH values of the cloudbase-init account for ecs01Figure 1 ecs01-
- LM-HASH and NTLM-HASH values of the cloudbase-init account for ecs02Figure 2 ecs02+
- LM-HASH and NTLM-HASH values of the cloudbase-init account for ecs02Figure 2 ecs02
Large-Memory ECSs
diff --git a/docs/ecs/umn/en-us_topic_0039588795.html b/docs/ecs/umn/en-us_topic_0039588795.html index 60ee6f352..6cfd0a340 100644 --- a/docs/ecs/umn/en-us_topic_0039588795.html +++ b/docs/ecs/umn/en-us_topic_0039588795.html @@ -1,10 +1,10 @@ -Overview
Large-memory ECSs provide an even larger amount of memory than memory-optimized ECSs. They are used for applications that require a large amount of memory, rapid data switching, low latency, and capability of processing large volumes of data. Large-memory ECSs provide large memory and high computing, storage, and network performance.
-Viewing ECS Creation Statuses
+Viewing the ECS Creation Status
Scenarios
After submitting the request for creating an ECS, you can view the creation status. This section describes how to view the creation status of an ECS.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- After creating an ECS, view the creation status above the ECS list beside the common operations (Start, Stop, Restart, and Delete).Figure 1 ECS creation status-
- Click the number displayed above Creating and view task details.
- An ECS that is being created is in one of the following states:
- Creating: The ECS is being created.
- Faulty: Creating the ECS failed. In such a case, the system automatically rolls back the task and displays an error code on the GUI, for example, Ecs.0013 Insufficient EIP quota.
- Running: The request of creating the ECS has been processed, and the ECS is running properly. An ECS in this state can provide services for you.
See How Do I Handle Error Messages Displayed on the Management Console? for troubleshooting.
+ - Click the number displayed above Creating and view task details.diff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html index 02f6cb088..161f4a7a6 100644 --- a/docs/ecs/umn/en-us_topic_0041169567.html +++ b/docs/ecs/umn/en-us_topic_0041169567.html @@ -8,10 +8,22 @@ -
- An ECS that is being created is in one of the following states:
- Creating: The ECS is being created.
- Faulty: Creating the ECS failed. In such a case, the system automatically rolls back the task and displays an error code on the GUI, for example, Ecs.0013 Insufficient EIP quota.
- Running: The request of creating the ECS has been processed, and the ECS is running properly. An ECS in this state can provide services for you.
See How Do I Handle Error Messages Displayed on the Management Console? for troubleshooting.
- If you find that the task status area shows an ECS creation failure but the ECS has been created successfully and displayed in the ECS list, see Why Does the Failures Area Show an ECS Creation Failure But the ECS List Displays the Created ECS?
2025-02-10
+2025-04-02
+Modified the following content:
+Added i3m.15xlarge.8 to I3m flavors in Ultra-high I/O ECSs.
+2025-03-06
+Modified the following content:
+Added G7v ECSs in GPU-accelerated ECSs.
+2025-02-10
Modified the following content:
-Memory-optimized ECSs: Added m4.medium.8 to M4 flavors and m3.medium.8 to M3 flavors.
+Added m4.medium.8 to M4 flavors and m3.medium.8 to M3 flavors in Memory-optimized ECSs.
2025-01-06
@@ -101,7 +113,7 @@2023-06-27
+ 2023-06-13
@@ -678,7 +690,7 @@2016-10-09
Added the following content:
-- Managing ECS Groups
- Viewing ECS Creation Statuses
- Why Does the Failures Area Show an ECS Creation Failure But the ECS List Displays the Created ECS?
- Managing ECS Groups
- Viewing the ECS Creation Status
- Why Does the Failures Area Show an ECS Creation Failure But the ECS List Displays the Created ECS?
Modified the following content:
- Added information for remotely logging in to ECSs in Logging In to a Windows ECS Using VNC, Logging In to a Linux ECS Using an SSH Key Pair, Logging In to a Linux ECS Using an SSH Password, and Logging In to a Windows ECS Using MSTSC.
- Added document links to the default keyboard types of the ECSs created using public images in Logging In to a Windows ECS Using VNC.
- Added notes on keyboard language settings for VNC-based ECS logins and the mapping between four types of keyboards in Logging In to a Windows ECS Using VNC. Provided configuration examples and links to related FAQs.
iptables --append OUTPUT --proto tcp --destination 169.254.169.254 --match owner ! --uid-owner root --jump REJECT
-ECS Metadata Types
Table 1 does not contain the following metadata items: ami-id, ami-launch-index, ami-manifest-path, block-device-mapping/, instance-action, instance-id, reservation-id, ramdisk-id, and kernel-id. These metadata items are meaningless and are not recommended.
+-ECS Metadata Types
Table 1 does not contain the following EC2-compatible metadata items: ami-id, ami-launch-index, ami-manifest-path, block-device-mapping/, instance-action, instance-id, reservation-id, ramdisk-id, and kernel-id. These metadata items are meaningless and are not recommended.
Prerequisites
- The target ECS has been logged in.
- Security group rules in the outbound direction meet the following requirements:
- Protocol: TCP
- Port: 80
- Destination: 169.254.0.0/16
-Prerequisites
- The target ECS has been logged in.
- Security group rules in the outbound direction meet the following requirements:
- Protocol: TCP
- Port: 80
- Destination: 169.254.0.0/16
If you use the default security group rules for the outbound direction, the metadata can be accessed because the default rules meet the preceding requirements. For details about the default security group rules for the outbound direction, see Default Security Groups and Rules.
Security Key (OpenStack Metadata API)
This API is used to obtain temporary AKs and SKs.
- - If an ECS needs to obtain a temporary AK and SK, go to the ECS details page, and configure Agency for the ECS in the Management Information area so that the ECS is authorized on IAM.
- The validity period of a temporary AK and SK is one hour. The temporary AK and SK are updated 10 minutes ahead of the expiration time. During the 10 minutes, both the new and old temporary AKs and SKs can be used.
- When using temporary AKs and SKs, add 'X-Security-Token':{securitytoken} in the message header. securitytoken is the value returned when a call is made to the API.
Security Key (OpenStack Metadata API)
This API is used to obtain a temporary AK/SK.
+ - If an ECS needs to obtain a temporary AK/SK, you need to create and authorize an agency on the IAM console and then go to the ECS details page to configure Agency for the ECS in the Management Information area.
- The validity period of a temporary AK and SK is one hour. The temporary AK and SK are updated 10 minutes ahead of the expiration time. During the 10 minutes, both the new and old temporary AKs and SKs can be used.
- When using temporary AKs and SKs, add 'X-Security-Token':{securitytoken} in the message header. securitytoken is the value returned when a call is made to the API.
- URI
- Usage method
diff --git a/docs/ecs/umn/en-us_topic_0046852143.html b/docs/ecs/umn/en-us_topic_0046852143.html
index bc05ac862..5346e0e99 100644
--- a/docs/ecs/umn/en-us_topic_0046852143.html
+++ b/docs/ecs/umn/en-us_topic_0046852143.html
@@ -5,7 +5,7 @@
Method 1: Click AltGr on the VNC page and then press the suitable key on the keyboard twice.
Method 2: Press AltGr+~(`)+Space.
- For ECSs running Windows and Linux, the following characters cannot be input normally: #, {, [, |, \, ^, @, ], }, ¤, €
To input these characters, do as follows:
-Click AltGr on the VNC page and then press the suitable key on the keyboard.
+Click AltGr on the VNC page and then press the suitable key on the keyboard.
- No L'accent circonflexe or Le tréma can be input on characters A, E, I, O, and U using the physical keyboard.
To input these characters, do as follows:
Click ^: on the VNC page and then press the suitable key on the keyboard.
- No character can be input using the French keypad. diff --git a/docs/ecs/umn/en-us_topic_0046912051.html b/docs/ecs/umn/en-us_topic_0046912051.html index d6ac47145..ef5afaf47 100644 --- a/docs/ecs/umn/en-us_topic_0046912051.html +++ b/docs/ecs/umn/en-us_topic_0046912051.html @@ -53,7 +53,7 @@
- After disabling a CMK or scheduling the deletion of a CMK takes effect, the EVS disk encrypted using this CMK can still be used until the disk is detached from and then attached to an ECS again. During this process, the disk fails to be attached to the ECS because the CMK cannot be obtained, so the EVS disk becomes unavailable.
For details about KMS, see Key Management Service User Guide.
+For details about KMS, see Key Management Service User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0048642616.html b/docs/ecs/umn/en-us_topic_0048642616.html index 3a43add82..26b0b3a02 100644 --- a/docs/ecs/umn/en-us_topic_0048642616.html +++ b/docs/ecs/umn/en-us_topic_0048642616.html @@ -12,10 +12,10 @@-Impact on ECS
- When creating an ECS, if the selected image supports Cloud-Init, you can use the User Data function to specify custom configuration, such as ECS login password to the ECS. Such custom settings will take effect upon ECS initialization. For details, see Injecting User Data.
- If Cloud-Init is supported, ECSs do not support password authentication anymore. All newly created ECSs use key pair authentication. This change will influence your ECS logins. For details, see the following sections:
- If Cloud-Init is supported, you can view and use metadata to configure and manage running ECSs. For details, see Obtaining Metadata.
Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
+-Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
Notes
- When using Cloud-Init, enable DHCP in the VPC which the ECS belongs to.
- When using Cloud-Init, ensure that security group rules for the outbound direction meet the following requirements:
- Protocol: TCP
- Port: 80
- Destination: 169.254.0.0/16
Notes
- When using Cloud-Init, enable DHCP in the VPC which the ECS belongs to.
- When using Cloud-Init, ensure that security group rules for the outbound direction meet the following requirements:
- Protocol: TCP
- Port: 80
- Destination: 169.254.0.0/16
If you use the default security group rules for the outbound direction, the metadata can be accessed because the default rules meet the preceding requirements. For details about the default security group rules for the outbound direction, see Security Group.
Modifying the Mapping Between the ECS Hostname and IP Address (Modifying the hosts File)
If you want to use the changed hostname as the preferred localhost and localhost.localdomain, update the mapping between the hostname and IP address after the hostname is changed and then save the configuration to the corresponding Cloud-Init configuration file so that the new hostname takes effect permanently.
The changed hostname is assumed to be new_hostname.
-- Modify the /etc/hostname configuration file.
- Run the following command to edit the configuration file:
+
- Modify the /etc/hostname configuration file. -
- Modify the /etc/sysconfig/network configuration file.
- Run the following command to edit the configuration file: -
- Change the HOSTNAME value to the new hostname.
HOSTNAME=Changed hostname
- If there is no HOSTNAME in the configuration file, manually add this parameter and set it to the changed hostname.
+- Modify the /etc/sysconfig/network configuration file.
- Run the following command to edit the configuration file: +
- Change the HOSTNAME value to the new hostname.
HOSTNAME=Changed hostname
+ If there is no HOSTNAME in the configuration file, manually add this parameter and set it to the changed hostname.
For example:
HOSTNAME=new_hostname
- Run the following command to save and exit the configuration file:
- Modify the /etc/cloud/cloud.cfg configuration file.
- Run the following command to edit the configuration file: -
- Use either of the following methods to modify the configuration file:
- Method 1: Change the preserve_hostname parameter value or add the preserve_hostname parameter to the configuration file.
If preserve_hostname: false is already available in the /etc/cloud/cloud.cfg configuration file, change it to preserve_hostname: true. If preserve_hostname is unavailable in the /etc/cloud/cloud.cfg configuration file, add preserve_hostname: true before cloud_init_modules.
-If you use method 1, the changed hostname still takes effect after the ECS is stopped or restarted. However, if the ECS is used to create a private image and the image is used to create a new ECS, the hostname of the new ECS is the hostname (new_hostname) used by the private image, and user-defined hostnames cannot be injected using Cloud-Init.
- - Method 2 (recommended): Delete or comment out - update_hostname.
If you use method 2, the changed hostname still takes effect after the ECS is stopped or restarted. If the ECS is used to create a private image and the image is used to create a new ECS, the changed hostname permanently takes effect, and user-defined hostnames (such as new_new_hostname) can be injected using Cloud-Init.
+ - Modify the /etc/cloud/cloud.cfg configuration file.
- Run the following command to edit the configuration file: +
- Use either of the following methods to modify the configuration file:
- Method 1: Change the preserve_hostname parameter value or add the preserve_hostname parameter to the configuration file.
If preserve_hostname: false is already available in the /etc/cloud/cloud.cfg configuration file, change it to preserve_hostname: true. If preserve_hostname is unavailable in the /etc/cloud/cloud.cfg configuration file, add preserve_hostname: true before cloud_init_modules.
+If you use method 1, the changed hostname still takes effect after the ECS is stopped or restarted. However, if the ECS is used to create a private image and the image is used to create a new ECS, the hostname of the new ECS is the hostname (new_hostname) used by the private image, and user-defined hostnames cannot be injected using Cloud-Init.
+ - Method 2 (recommended): Delete or comment out - update_hostname.
If you use method 2, the changed hostname still takes effect after the ECS is stopped or restarted. If the ECS is used to create a private image and the image is used to create a new ECS, the changed hostname permanently takes effect, and user-defined hostnames (such as new_new_hostname) can be injected using Cloud-Init.
- Method 1: Change the preserve_hostname parameter value or add the preserve_hostname parameter to the configuration file.
- Method 1: Change the preserve_hostname parameter value or add the preserve_hostname parameter to the configuration file.
- Update the mapping between the hostname and IP address in /etc/hosts to an entry starting with 127.0.0.1. Use new_hostname as your preferred localhost and localhost.localdomain. -
- Modify the /etc/cloud/cloud.cfg configuration file.
- Run the following command to edit the configuration file: +
- Modify the /etc/cloud/cloud.cfg configuration file.
- Run the following command to edit the configuration file:
- Set manage_etc_hosts to manage_etc_hosts: false.
manage_etc_hosts: false
- Run the following command to save and exit the configuration file:
- For CentOS 6 and Red Hat 6, perform the following steps:
- Run the following command to open the configuration file:
- Locate the row that contains linux, linux16, or kernel (depending on the system), add console=ttyS0 to its end, and delete parameter rhgb quiet. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
- For CentOS 7, Red Hat 7, and Ubuntu 14, perform the following steps:
- Run the following command to open the configuration file: -
- Locate the row that contains linux, linux16, or kernel (depending on the system), add console=ttyS0 to its end, and delete parameter rhgb quiet. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
- Locate the row that contains linux, linux16, or kernel (depending on the system), add console=ttyS0 to its end, and delete parameter rhgb quiet. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
- For SUSE Linux 11, perform the following steps: +
- Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
- For SUSE Linux 12, openSUSE 13, and openSUSE 42, perform the following steps: +
- Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
- For Debian and Ubuntu 16, perform the following steps: +
- Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
- For Fedora, perform the following steps: +
- Locate the row that contains linux, linux16, or kernel (depending on the system) and add console=ttyS0 to its end. If console=ttyS0 already exists, you do not need to add it. Save the change and exit.
- For FreeBSD, perform the following steps: +
- Add console="comconsole". If console="comconsole" already exists, you do not need to add it. Save the change and exit.
- For CoreOS, perform the following steps:
- Run the following command to check whether ttyS0 has been configured:
cat /proc/cmdline | grep ttyS0
- If yes, ttyS0 has been configured.
- If no, ttyS0 has not been configured. Go to 2.b.
- Run the following command to open the configuration file to be edited: diff --git a/docs/ecs/umn/en-us_topic_0058758453.html b/docs/ecs/umn/en-us_topic_0058758453.html index d4bad6c37..2b9255551 100644 --- a/docs/ecs/umn/en-us_topic_0058758453.html +++ b/docs/ecs/umn/en-us_topic_0058758453.html @@ -146,7 +146,7 @@
- Modify the /etc/sysconfig/network configuration file.
- Run the following command to edit the configuration file:
+
- An ECS that is being created is in one of the following states:
- An ECS that is being created is in one of the following states:
Importing the External Image File to the IMS Console
For details, see "Registering an Image File as a Private Image" in Image Management Service User Guide.
+Importing the External Image File to the IMS Console
For details, see "Registering an Image File as a Private Image" in Image Management Service User Guide.
-Setting NIC Multi-Queue for the Image
Windows OSs have not commercially supported NIC multi-queue. If you enable NIC multi-queue in a Windows image, starting an ECS created using such an image may be slow.
Use one of the following methods to set the NIC multi-queue attribute:
@@ -172,7 +172,7 @@Creating an ECS Using a Private Image
You can create an ECS using a registered private image. For details, see Creating an ECS. Note the following when setting the parameters:- Region: Select the region where the private image is located.
- Image: Click Private image and then select the desired image from the drop-down list.
Creating an ECS Using a Private Image
You can create an ECS using a registered private image. For details, see Creating an ECS. Note the following when setting the parameters:- Region: Select the region where the private image is located.
- Image: Click Private image and then select the desired image from the drop-down list.
Enabling NIC Multi-Queue
KVM Windows ECSs use private images to support NIC multi-queue. For details, see "How Do I Set NIC Multi-queue Feature of an Image?" in Image Management Service User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0060610074.html b/docs/ecs/umn/en-us_topic_0060610074.html index 955193436..855fee6a1 100644 --- a/docs/ecs/umn/en-us_topic_0060610074.html +++ b/docs/ecs/umn/en-us_topic_0060610074.html @@ -1,9 +1,9 @@Exporting ECS Information
-Scenarios
The information of all ECSs under your account can be exported in a CSV file to a local directory. The file includes the IDs, private IP addresses, and EIPs of your ECSs.
+-Scenarios
The information of all ECSs in your account can be exported to a CSV file locally. The file includes the IDs, private IP addresses, and EIPs of your ECSs.
-Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the upper right corner above the ECS list, click
.The system will automatically export all ECSs in the current region under your account to a local directory.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the upper right corner above the ECS list, click .
The system will automatically export all ECSs in the current region under your account to a local directory.
Figure 1 Exporting ECS information
diff --git a/docs/ecs/umn/en-us_topic_0074825901.html b/docs/ecs/umn/en-us_topic_0074825901.html index 0a8feca0c..4799899f3 100644 --- a/docs/ecs/umn/en-us_topic_0074825901.html +++ b/docs/ecs/umn/en-us_topic_0074825901.html @@ -14,8 +14,8 @@ To export certain ECSs, select the target ECSs and click
in the upper right corner of the page.- Run the service ntp stop command to stop NTP.
- Run the systemctl disable ntp command to disable the function of automatically starting NTP upon ECS startup.
- Configure the DNS server for the ECS.
- Log in to the Linux ECS.
- Run the following command to switch to user root:
sudo su -
- - Run the following command to edit the resolv.conf configuration file:
vi /etc/resolv.conf
+ - Configure the DNS server for the ECS.
- Log in to the Linux ECS.
- Run the following command to switch to user root:
sudo su -
+ - Run the following command to edit the resolv.conf configuration file:
vi /etc/resolv.conf
- Add the following statement to configure the DNS server:
nameserver = IP addresses of the DNS servers
Example:
If the IP addresses of the DNS servers are 8.8.8.8 and 4.4.4.4, add the following statements:
@@ -36,7 +36,7 @@ - Select Internet Protocol Version 4 (TCP/IPv4) and click Properties, as shown in Figure 3.
- Select Use the following DNS server addresses and set the IP addresses of the DNS servers as prompted, as shown in Figure 4.
- Configure the NTP server for the ECS.
- Start the Run dialog box. Enter regedit and click OK.
- Modify the registry entries.
- In HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > TimeProviders > NtpClient, set the value of Enabled to 1, indicating that the NTP client is used.
- In HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > TimeProviders > NtpServer, set the value of Enabled to 0, indicating that the NTP server is stopped.
- Choose the HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > Parameters file and set the NtpServer data. Set the data of TYPE to NTP.
- In HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ W32Time \ TimeProviders \ NtpClient, set the value of SpecialPollInterval to 60 and that of Base to Decimal, indicating the clock synchronization cycle is 60s.
- In HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ W32Time \ config, set the values of MaxPosPhaseCorrection and MaxNegPhaseCorrection to ffffffff and that of Base to Hexadecimal.
- Configure the NTP server for the ECS.
- Start the Run dialog box. Enter regedit and click OK.
- Modify the registry entries.
- In HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > TimeProviders > NtpClient, set the value of Enabled to 1, indicating that the NTP client is used.
- In HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > TimeProviders > NtpServer, set the value of Enabled to 0, indicating that the NTP server is stopped.
- Choose the HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > W32Time > Parameters file and set the NtpServer data. Set the data of TYPE to NTP.
- In HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ W32Time \ TimeProviders \ NtpClient, set the value of SpecialPollInterval to 3600 and that of Base to Decimal, indicating the clock synchronization cycle is 3600s.
- In HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ W32Time \ config, set the values of MaxPosPhaseCorrection and MaxNegPhaseCorrection to ffffffff and that of Base to Hexadecimal.
- Open the Run dialog box, enter services.msc, and click OK. The Services window is displayed.
- View the service named Windows Time and set the Start Type to Automatic to synchronize time from the NTP server.
- Open the Run dialog box and run the following commands in sequence to restart the Windows Time service:
net stop w32time
net start w32time
- Manually change the time on the client to make it different from that on the NTP server. One minute later, check whether the time on the client is the same as that on the NTP server. If yes, the time is synchronized.
Figure 3 Creating a new partition
- Enter the new partition's start cylinder number and press Enter.
The start cylinder number must be greater than the end cylinder numbers of existing partitions. In this example, use the default value for the new partition's start cylinder number and press Enter. Information similar to the following is displayed.
Figure 4 Specifying the new partition's start cylinder number-
- Enter the new partition's end cylinder number and press Enter.
In this example, use the default value for the new partition's end cylinder number and press Enter. Information similar to the following is displayed.
+ - Enter the new partition's end cylinder number and press Enter.
In this example, use the default value for the new partition's end cylinder number and press Enter. Information similar to the following is displayed.
Figure 5 Specifying the new partition's end cylinder number
- Enter p and press Enter to view the created partition.
Information similar to the following is displayed.
Figure 6 Viewing the created partition@@ -92,9 +92,9 @@ Writing superblocks and filesystem accounting information: done
- Press Esc, run the following command, and press Enter. The system saves the configurations and exits the vi editor.
:wq
If you want to detach a new disk for which automatic mounting upon system startup has been set, you must delete the automatic mounting configuration before you detach the disk. Otherwise, the ECS cannot be started after you detach the disk. To delete the automatic mounting configuration, perform the following operations:
-- Run the following command to open the fstab file using the vi editor:
vi /etc/fstab
+- Run the following command to open the fstab file using the vi editor:
vi /etc/fstab
- Press i to enter editing mode.
- Delete the following statement:
UUID=96e5e028-b0fb-4547-a82a-35ace1086c4f /root/new ext4 defaults 0 0
- - Press Esc, run the following command, and press Enter. The system saves the configurations and exits the vi editor.
:wq
+ - Press Esc, run the following command, and press Enter. The system saves the configurations and exits the vi editor.
:wq
- Run the following command to open the fstab file using the vi editor:
Follow-up Procedure
- If you have added a data disk during ECS creation, you must initialize the data disk after logging in to the ECS.
For details, see Scenarios and Disk Partitions.
- - Certain ECSs require the installation of a driver after you log in to them. For details about available ECS types and functions, see ECS Types and their notes.
- Certain ECSs require the installation of a driver after you log in to them. For details about available ECS types and functions, see ECS Types.
diff --git a/docs/ecs/umn/en-us_topic_0092499768.html b/docs/ecs/umn/en-us_topic_0092499768.html index 8c6924274..26d9eb9ad 100644 --- a/docs/ecs/umn/en-us_topic_0092499768.html +++ b/docs/ecs/umn/en-us_topic_0092499768.html @@ -2,7 +2,7 @@Overview
Scenarios
A tag identifies an ECS. Adding tags to an ECS facilitates ECS identification and management.
-You can add a tag to an ECS during the ECS creation or after the ECS is created. You can add a maximum of 10 tags to each ECS.
+You can add tags to an ECS either during or after the ECS creation. A maximum of 10 tags can be added to an ECS.
diff --git a/docs/ecs/umn/en-us_topic_0093263550.html b/docs/ecs/umn/en-us_topic_0093263550.html index ed02f1356..ee56432ef 100644 --- a/docs/ecs/umn/en-us_topic_0093263550.html +++ b/docs/ecs/umn/en-us_topic_0093263550.html @@ -182,14 +182,14 @@ Tags added during the ECS creation will also be added to the EIP and EVS disks (including the system disk and data disks) of the ECS. If the ECS uses an existing EIP, the tags will not be added to the EIP.
After creating the ECS, you can view the tags on the pages providing details about the ECS, EIP, and EVS disks.
- If the password used when you create the ECS is entered using the English keyboard, you must use the English keyboard to enter the password when logging in to the ECS later.
-Logging In to an ECS Using an English Keyboard
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the search box above the upper right corner of the ECS list, enter the ECS name and click
for search. - Locate the row containing the ECS and click Remote Login in the Operation column.
- In the displayed Configure Keyboard Layout for Remote Login dialog box, select the English keyboard.Figure 1 Keyboard layout configuration-
- Click Remote Login.
- (Optional) If you have changed the system language, in the dialog box that is displayed, click Start Remote Login.Figure 2 Remote Login+
- Click Remote Login.
- (Optional) If you have changed the system language, in the displayed dialog box shown in Figure 2, click Start Remote Login.
- (Optional) When the system displays "Press CTRL+ALT+DELETE to log on", click Send CtrlAltDel in the upper part of the remote login page to log in to the ECS.Figure 3 Send CtrlAltDel
- (Optional) If you need your cursor to be displayed on the remote login page, click Local Cursor.Figure 4 Local Cursor
- Enter the ECS password as prompted.
Logging In to an ECS Using a Non-English Keyboard
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID, and click
for search. - Locate the row containing the ECS and click Remote Login in the Operation column.
- In the displayed Configure Keyboard Layout for Remote Login dialog box, select the English keyboard.Figure 5 Keyboard layout configuration-
- Click Remote Login.
- (Optional) If you have changed the system language, in the dialog box that is displayed, click Start Remote Login.Figure 6 Remote Login-
- (Optional) When the system displays "Press CTRL+ALT+DELETE to log on", click Send CtrlAltDel in the upper part of the remote login page to log in to the ECS.Figure 7 Send CtrlAltDel+
diff --git a/docs/ecs/umn/en-us_topic_0093492521.html b/docs/ecs/umn/en-us_topic_0093492521.html index c9ec3d18c..5ac5faf9c 100644 --- a/docs/ecs/umn/en-us_topic_0093492521.html +++ b/docs/ecs/umn/en-us_topic_0093492521.html @@ -1,9 +1,13 @@Logging In to an ECS Using a Non-English Keyboard
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID, and click for search.
- Locate the row containing the ECS and click Remote Login in the Operation column.
- In the displayed Configure Keyboard Layout for Remote Login dialog box, select the English keyboard.Figure 5 Keyboard layout configuration+
- Click Remote Login.
- (Optional) If you have changed the system language, in the displayed dialog box shown in Figure 6, click Start Remote Login. +
- (Optional) When the system displays "Press CTRL+ALT+DELETE to log on", click Send CtrlAltDel in the upper part of the remote login page to log in to the ECS.Figure 7 Send CtrlAltDel
- (Optional) If you need your cursor to be displayed on the remote login page, click Local Cursor.Figure 8 Local Cursor
- Enter the ECS password as prompted.
- When logging in to the ECS using VNC for the first time, use the English keyboard to enter the password. After you have logged in to the ECS, see Changing the OS Keyboard Language to change the keyboard language of the ECS OS. You can then select the keyboard language and enter the password the next time you log in.
- If you have changed the keyboard language of the ECS OS, ensure that the keyboard language in use, the keyboard language selected in step 6, and the changed OS keyboard language are all the same.
- Run either the ifup ethX command or the /etc/init.d/networking restart command to make the newly added network interface take effect.
X in the preceding command indicates the serial number of the network interface, for example, ifup eth2.
- Run the following command to check whether the network interface name obtained in step 2 is displayed in the command output:
ifconfig
For example, check whether eth2 is displayed in the command output.
-- If yes, the newly added network interface has been activated. No further action is required.
- If no, the newly added failed to be activated. Go to step 9.
- If yes, the newly added network interface has been activated. No further action is required.
- If no, the newly added network interface failed to be activated. Go to step 9.
- Log in to the management console. Locate the row containing the target ECS, click More in the Operation column, and select Restart.
- Run ifconfig again to check whether the network interface name obtained in step 2 is displayed in the command output:
- If yes, no further action is required.
- If no, contact customer service.
Modifying an EIP Bandwidth
-Scenarios
If an EIP has been bound to the ECS, the ECS can access the Internet using the bandwidth associated with the EIP. This section describes how to adjust the bandwidth of an ECS.
+-Scenarios
The bandwidth of an EIP enables data transfer between the public network and an ECS. If the bandwidth of the EIP does not meet your service requirements, you can adjust the bandwidth by referring to this section.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, locate the row containing the target ECS and choose More > Manage Network > Modify Bandwidth in the Operation column.
- Change the bandwidth name and size as prompted.
+Constraints
Reducing bandwidths may cause packet loss. Exercise caution when performing this operation.
++Prerequisites
An EIP has been bound to an ECS. For details, see Binding an EIP.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, locate the row containing the target ECS and choose More > Manage Network > Modify Bandwidth in the Operation column.
- Change the bandwidth name and size as prompted.
diff --git a/docs/ecs/umn/en-us_topic_0094118976.html b/docs/ecs/umn/en-us_topic_0094118976.html index ddf503a32..ddf802575 100644 --- a/docs/ecs/umn/en-us_topic_0094118976.html +++ b/docs/ecs/umn/en-us_topic_0094118976.html @@ -106,6 +106,25 @@KVM
i3m.15xlarge.8
+60
+512
+25/25
+500
+16
+7 × 1,600 GiB NVMe
+8
+KVM
+i3m.16xlarge.8
64
diff --git a/docs/ecs/umn/en-us_topic_0095020344.html b/docs/ecs/umn/en-us_topic_0095020344.html index e9562194a..9bc5f5799 100644 --- a/docs/ecs/umn/en-us_topic_0095020344.html +++ b/docs/ecs/umn/en-us_topic_0095020344.html @@ -4,7 +4,7 @@Yes. ECS can automatically recover if the physical host becomes faulty.
ECSs run on physical hosts. Although there are multiple mechanisms to ensure system reliability, fault tolerance, and high availability, host hardware might be damaged or power failures might occur. If physical hosts cannot be powered on or restarted due to damage, CPU and memory data will be lost and live migration cannot be used to recovery ECSs.
The cloud platform provides automatic recovery by default to restart ECSs through cold migration, ensuring high availability and dynamic ECS migration. If a physical host accommodating ECSs breaks down, the ECSs will automatically be migrated to a functional physical host to minimize the impact on your services. During the process, the ECSs will restart.
- - Automatic recovery does not ensure user data consistency.
- An ECS can be automatically recovered only if the physical server on which it is deployed becomes faulty. This function does not take effect if the fault is caused by the ECS itself.
- An ECS can be automatically recovered only after the physical server on which it is deployed is shut down. If the physical server is not shut down due to a fault, for example, a memory fault, automatic recovery fails to take effect.
- An ECS can be automatically recovered only once within 12 hours if the server on which it is deployed becomes faulty.
- ECS automatic recovery may fail in the following scenarios:
- No physical server is available for migration due to a system fault.
- The target physical server does not have sufficient temporary capacity.
diff --git a/docs/ecs/umn/en-us_topic_0096293655.html b/docs/ecs/umn/en-us_topic_0096293655.html index 85ffcac83..fe3b90e3c 100644 --- a/docs/ecs/umn/en-us_topic_0096293655.html +++ b/docs/ecs/umn/en-us_topic_0096293655.html @@ -1,15 +1,15 @@ - Auto recovery does not ensure user data consistency.
- An ECS can be automatically recovered only if the physical server on which it is deployed becomes faulty. This function does not take effect if the fault is caused by the ECS itself.
- An ECS can be automatically recovered only after the physical server on which it is deployed is shut down. If the physical server is not shut down due to a fault, for example, a memory fault, auto recovery fails to take effect.
- An ECS can be automatically recovered only once within 12 hours if the server on which it is deployed becomes faulty.
- ECS auto recovery may fail in the following scenarios:
- No physical server is available for migration due to a system fault.
- The target physical server does not have sufficient temporary capacity.
- An ECS with any of the following resources cannot be automatically recovered:
- Local disk
- Passthrough FPGA card
- Passthrough InfiniBand NIC
Attaching a Disk to an ECS
-Scenarios
If the existing disks of an ECS fail to meet service requirements, for example, due to insufficient disk space or poor disk performance, you can attach more available EVS disks to the ECS, or create more disks (under Storage > Elastic Volume Service) and attach them to the ECS.
+Scenarios
If the existing disks of an ECS fail to meet service requirements, for example, due to insufficient disk space or poor disk performance, you can attach more available EVS disks to the ECS, or create more disks (choosing Storage > Elastic Volume Service) and attach them to the ECS.
-Prerequisites
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID for search.
- Click the name of the target ECS.
The page providing details about the ECS is displayed.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID for search.
- Click the name of the target ECS.
The page providing details about the ECS is displayed.
- Click the Disks tab. Then, click Attach Disk.
The Attach Disk dialog box is displayed.
Figure 1 Attach Disk-
- Select the target disk and specify the disk as the system disk or data disk
- If no EVS disks are available, click Create Disk in the lower part of the list.
- For details about constraints on attaching disks, see What Are the Requirements for Attaching an EVS Disk to an ECS?
- The device names for the local disks and EVS disks attached to a disk-intensive ECS comply with the following rules:
- System disk: Use sda or vda.
- Local disk: Use the device name following sda or vda in alphabetical order.
- EVS disk: Use the device name added in alphabetical order following those used by local disks.
- Select the target disk and specify the disk as the system disk or data disk
- If no EVS disks are available, click Create Disk in the lower part of the list.
- For details about constraints on attaching disks, see What Are the Requirements for Attaching an EVS Disk to an ECS?
- The device names for the local disks and EVS disks attached to a disk-intensive ECS comply with the following rules:
- System disk: Use sda or vda.
- Local disk: Use the device name following sda or vda in alphabetical order.
- EVS disk: Use the device name added in alphabetical order following those used by local disks.
- Click OK.
After the disk is attached, you can view the information about it on the Disks tab.
@@ -17,7 +17,7 @@
Follow-up Procedure
If the attached disk is newly created, the disk can be used only after it is initialized.
-To learn how to initialize data disks, see Scenarios and Disk Partitions.
+For details about how to initialize a data disk, see Scenarios and Disk Partitions.
diff --git a/docs/ecs/umn/en-us_topic_0097289624.html b/docs/ecs/umn/en-us_topic_0097289624.html index 32b39cee3..8289f4037 100644 --- a/docs/ecs/umn/en-us_topic_0097289624.html +++ b/docs/ecs/umn/en-us_topic_0097289624.html @@ -6,7 +6,7 @@GPU-accelerated ECSs
Recommended: Computing-accelerated P2s, Inference-accelerated Pi2, and GPU-accelerated Enhancement G6
Available now: All GPU models except the recommended ones. If available ECSs are sold out, use the recommended ones.
-- G series
+
- G series
- P series
Helpful links: @@ -21,7 +21,14 @@
Graphics-accelerated
+Graphics-accelerated
+G7v
+- CentOS 8.2 64bit
- CentOS 7.6 64bit
- Ubuntu 20.04 Server 64bit
- Ubuntu 18.04 Server 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
Graphics-accelerated
G7
GPU-accelerated Enhancement G7v
Overview
+G7v ECSs use NVIDIA A40 GPUs and support DirectX, Shader Model, OpenGL, and Vulkan. Each GPU provides 48 GiB of GPU memory. Theoretically, the peak FP32 is 37.4 TFLOPS and the peak TF32 tensor is 74.8 TFLOPS | 149.6 TFLOPS (sparsity enabled). They deliver two times the rendering performance and 1.4 times the graphics processing performance of RTX6000 GPUs to meet professional graphics processing requirements.
+Select your desired GPU-accelerated ECS type and specifications.
+Specifications
+ ++
+Table 2 G7v ECS specifications Flavor
+vCPUs
+Memory
+(GiB)
+Max./Assured Bandwidth
+(Gbit/s)
+Max. PPS
+(10,000)
+Max. NIC Queues
+Max. NICs
+GPUs
+GPU Memory
+(GiB)
+Virtualization
+g7v.2xlarge.8
+8
+64
+15/3
+100
+4
+4
+1 × NVIDIA-A40-8Q
+8
+KVM
+g7v.4xlarge.8
+16
+128
+20/6
+150
+8
+8
+1 × NVIDIA-A40-16Q
+16
+KVM
+g7v.6xlarge.8
+24
+192
+25/9
+200
+8
+8
+1 × NVIDIA-A40-24Q
+24
+KVM
+G7v ECS Features
+- CPU: 3rd Generation Intel® Xeon® Scalable 6348 processors (3.0 GHz of base frequency and 3.5 GHz of turbo frequency)
- Graphics acceleration APIs
- DirectX 12.07, Direct2D, DirectX Video Acceleration (DXVA)
- Shader Model 5.17
- OpenGL 4.68
- Vulkan 1.18
- CUDA, DirectCompute, OpenACC, and OpenCL
- A single card is equipped with 10,752 CUDA cores, 84 second-generation RT cores, and 336 third-generation Tensor cores.
- Graphics applications accelerated
- Heavy-load CPU inference
- Application flow identical to common ECSs
- Automatic scheduling of G7v ECSs to AZs where NVIDIA A40 GPUs are used
- One NVENC (encoding) engine and two NVDEC (decoding) engines (including AV1 decoding) embedded
Supported Common Software
+G7v ECSs are used in graphics acceleration scenarios, such as video rendering, cloud desktop, and 3D visualization. If the software relies on GPU DirectX and OpenGL hardware acceleration, use G7v ECSs. G7v ECSs support the following commonly used graphics processing software:
+- AutoCAD
- 3ds Max
- MAYA
- Agisoft PhotoScan
- ContextCapture
- Adobe Premiere Pro
- Solidworks
- Unreal Engine
- Blender
- Vray
Notes
+- After a G7v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.+
Resources will be released after a G7v ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+ - G7v ECSs created using a public image have had the GRID driver of a specific version installed by default. However, you need to purchase and configure a GRID license by yourself. Ensure that the GRID driver version meets service requirements.
For details about how to configure a GRID license, see Manually Installing a GRID Driver on a GPU-accelerated ECS.
+ - If a G7v ECS is created using a private image, make sure that the GRID driver was installed during the private image creation. If the GRID driver has not been installed, install the driver for graphics acceleration after the ECS is created.
For details, see Manually Installing a GRID Driver on a GPU-accelerated ECS.
+ - GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
Graphics-accelerated Enhancement G7
Overview
G7 ECSs use NVIDIA A40 GPUs and support DirectX, Shader Model, OpenGL, and Vulkan. Each GPU provides 48 GiB of GPU memory. Theoretically, the peak FP32 is 37.4 TFLOPS and the peak TF32 tensor is 74.8 TFLOPS | 149.6 TFLOPS (sparsity enabled). They deliver two times the rendering performance and 1.4 times the graphics processing performance of RTX6000 GPUs to meet professional graphics processing requirements.
Select your desired GPU-accelerated ECS type and specifications.
Specifications
-Table 2 G7 ECS specifications Flavor
+Table 3 G7 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Virtualization
+Virtualization
g7.12xlarge.8
+g7.12xlarge.8
48
+48
384
+384
35/18
+35/18
750
+750
16
+16
8
+8
1 × NVIDIA-A40
+1 × NVIDIA-A40
1 × 48
+1 × 48
KVM
+KVM
g7.24xlarge.8
+g7.24xlarge.8
96
+96
768
+768
40/36
+40/36
850
+850
16
+16
8
+8
2 × NVIDIA-A40
+2 × NVIDIA-A40
2 × 48
+2 × 48
KVM
+KVM
Select your desired GPU-accelerated ECS type and specifications.
Specifications
-Table 3 G6 ECS specifications Flavor
+Table 4 G6 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Virtualization
+Virtualization
g6.4xlarge.4
+g6.4xlarge.4
16
+16
64
+64
25/15
+25/15
200
+200
8
+8
8
+8
1 × T4
+1 × T4
16
+16
KVM
+KVM
g6.10xlarge.7
+g6.10xlarge.7
40
+40
280
+280
25/15
+25/15
200
+200
16
+16
8
+8
1 × T4
+1 × T4
16
+16
KVM
+KVM
g6.20xlarge.7
+g6.20xlarge.7
80
+80
560
+560
30/30
+30/30
400
+400
32
+32
16
+16
2 × T4
+2 × T4
32
+32
KVM
+KVM
P5s ECSs use high-performance NVIDIA Tesla H100 PCIe and provide outstanding real-time inference.
Specifications
-Table 4 P5s ECS specifications Flavor
+Table 5 P5s ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory (GiB)
Max./Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth (Gbit/s)
Max. PPS (10,000)
+Max. PPS (10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory (GiB)
+GPU Memory (GiB)
Virtualization
+Virtualization
p5s.5xlarge.12
+p5s.5xlarge.12
20
+20
240
+240
16/4.5
+16/4.5
280
+280
8
+8
4
+4
1 * H100 PCIe
+1 * H100 PCIe
80
+80
KVM
+KVM
p5s.10xlarge.12
+p5s.10xlarge.12
40
+40
480
+480
24/9
+24/9
550
+550
16
+16
8
+8
2 * H100 PCIe
+2 * H100 PCIe
160
+160
KVM
+KVM
p5s.20xlarge.12
+p5s.20xlarge.12
80
+80
960
+960
32/18
+32/18
750
+750
32
+32
8
+8
4 * H100 PCIe
+4 * H100 PCIe
320
+320
KVM
+KVM
p5s.40xlarge.12
+p5s.40xlarge.12
160
+160
1920
+1920
40/36
+40/36
850
+850
32
+32
8
+8
8 * H100 PCIe
+8 * H100 PCIe
640
+640
KVM
+KVM
Supported Common Software
P5s ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P5s ECSs. The following commonly used software is supported:
- Common deep learning frameworks, such as TensorFlow, Spark, PyTorch, MXNet, and Caffe
- CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
- More than 2,000 GPU-accelerated applications such as Amber, NAMD, and VASP
Notes
+Notes
- P5s ECSs support automatic recovery when the hosts accommodating such ECSs become faulty.
- After a P5s ECS is stopped, basic resources (including vCPUs, memory, image, and encoding cards) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- Specifications of P5s ECSs can only be changed to other specifications of the same instance type.
- If you have attached a data disk to a P5s ECS during ECS creation, do not detach the data disk upon creation, or the detachment will fail.
Computing-accelerated P3
Overview
P3 ECSs use NVIDIA A100 GPUs and provide flexibility and ultra-high-performance computing. P3 ECSs have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics. Theoretically, the FP32 is 19.5 TFLOPS and the TF32 tensor core is 156 TFLOPS | 312 TFLOPS (sparsity enabled).
Specifications
-Table 5 P3 ECS specifications Flavor
+Table 6 P3 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth (Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Virtualization
+Virtualization
p3.2xlarge.8
+p3.2xlarge.8
8
+8
64
+64
10/4
+10/4
100
+100
4
+4
4
+4
1 × NVIDIA A100 80GB
+1 × NVIDIA A100 80GB
80
+80
KVM
+KVM
p3.4xlarge.8
+p3.4xlarge.8
16
+16
128
+128
15/8
+15/8
200
+200
8
+8
8
+8
2 × NVIDIA A100 80GB
+2 × NVIDIA A100 80GB
160
+160
KVM
+KVM
p3.8xlarge.8
+p3.8xlarge.8
32
+32
256
+256
25/15
+25/15
350
+350
16
+16
8
+8
4 × NVIDIA A100 80GB
+4 × NVIDIA A100 80GB
320
+320
KVM
+KVM
p3.16xlarge.8
+p3.16xlarge.8
64
+64
512
+512
36/30
+36/30
700
+700
32
+32
8
+8
8 × NVIDIA A100 80GB
+8 × NVIDIA A100 80GB
640
+640
KVM
+KVM
Supported Common Software
P3 ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P3 ECSs. P3 ECSs support the following commonly used software:
- Common deep learning frameworks, such as TensorFlow, Spark, PyTorch, MXNet, and Caffe
- CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
- More than 2,000 GPU-accelerated applications such as Amber, NAMD, and VASP
Notes
-- After a P3 ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately. @@ -527,129 +644,129 @@
Resources will be released after a P3 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+Notes
+- After a P3 ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
Resources will be released after a P3 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
- If a P3 ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
P2s ECSs use NVIDIA Tesla V100 GPUs to provide flexibility, high-performance computing, and cost-effectiveness. P2s ECSs provide outstanding general computing capabilities and have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics.
Specifications
-Table 6 P2s ECS specifications Flavor
+Table 7 P2s ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth (Gbit/s)
Max. PPS (10,000)
+Max. PPS (10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Connection
+GPU Connection
GPU Memory (GiB)
+GPU Memory (GiB)
Virtualization
+Virtualization
Hardware
+Hardware
p2s.2xlarge.8
+p2s.2xlarge.8
8
+8
64
+64
10/4
+10/4
50
+50
4
+4
4
+4
1 × V100
+1 × V100
PCIe Gen3
+PCIe Gen3
1 × 32 GiB
+1 × 32 GiB
KVM
+KVM
CPU: 2nd Generation Intel® Xeon® Scalable Processor 6278
+CPU: 2nd Generation Intel® Xeon® Scalable Processor 6278
p2s.4xlarge.8
+p2s.4xlarge.8
16
+16
128
+128
15/8
+15/8
100
+100
8
+8
8
+8
2 × V100
+2 × V100
PCIe Gen3
+PCIe Gen3
2 × 32 GiB
+2 × 32 GiB
KVM
+KVM
p2s.8xlarge.8
+p2s.8xlarge.8
32
+32
256
+256
25/15
+25/15
200
+200
16
+16
8
+8
4 × V100
+4 × V100
PCIe Gen3
+PCIe Gen3
4 × 32 GiB
+4 × 32 GiB
KVM
+KVM
p2s.16xlarge.8
+p2s.16xlarge.8
64
+64
512
+512
30/30
+30/30
400
+400
32
+32
8
+8
8 × V100
+8 × V100
PCIe Gen3
+PCIe Gen3
8 × 32 GiB
+8 × 32 GiB
KVM
+KVM
Supported Common Software
P2s ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P2s ECSs. P2s ECSs support the following commonly used software:-- Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
Notes- After a P2s ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately. -
Resources will be released after a P2s ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+Notes- After a P2s ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
Resources will be released after a P2s ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
- By default, P2s ECSs created using a Windows public image have the Tesla driver installed.
- If a P2s ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
Computing-accelerated P2v
Overview
+Computing-accelerated P2v
Overview
P2v ECSs use NVIDIA Tesla V100 GPUs and deliver high flexibility, high-performance computing, and high cost-effectiveness. These ECSs use GPU NVLink for direct communication between GPUs, improving data transmission efficiency. P2v ECSs provide outstanding general computing capabilities and have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics.
Specifications
-Table 7 P2v ECS specifications Flavor
+Table 8 P2v ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth (Gbit/s)
Max. PPS (10,000)
+Max. PPS (10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Connection
+GPU Connection
GPU Memory
+GPU Memory
(GiB)
Virtualization
+Virtualization
Hardware
+Hardware
p2v.2xlarge.8
+p2v.2xlarge.8
8
+8
64
+64
10/4
+10/4
50
+50
4
+4
4
+4
1 × V100
+1 × V100
N/A
+N/A
1 × 16 GiB
+1 × 16 GiB
KVM
+KVM
CPU: Intel® Xeon® Skylake-SP Gold 6151 v5
+CPU: Intel® Xeon® Skylake-SP Gold 6151 v5
p2v.4xlarge.8
+p2v.4xlarge.8
16
+16
128
+128
15/8
+15/8
100
+100
8
+8
8
+8
2 × V100
+2 × V100
NVLink
+NVLink
2 × 16 GiB
+2 × 16 GiB
KVM
+KVM
p2v.8xlarge.8
+p2v.8xlarge.8
32
+32
256
+256
25/15
+25/15
200
+200
16
+16
8
+8
4 × V100
+4 × V100
NVLink
+NVLink
4 × 16 GiB
+4 × 16 GiB
KVM
+KVM
p2v.16xlarge.8
+p2v.16xlarge.8
64
+64
512
+512
30/30
+30/30
400
+400
32
+32
8
+8
8 × V100
+8 × V100
NVLink
+NVLink
8 × 16 GiB
+8 × 16 GiB
KVM
+KVM
Supported Common Software
P2v ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P2v ECSs. P2v ECSs support the following commonly used software:-- Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
Notes- After a P2v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
Resources will be released after a P2v ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+Notes@@ -815,151 +932,151 @@- After a P2v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
Resources will be released after a P2v ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
- By default, P2v ECSs created using a Windows public image have the Tesla driver installed.
- By default, P2v ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- If a P2v ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
Pi2 ECSs use NVIDIA Tesla T4 GPUs dedicated for real-time AI inference. These ECSs use the T4 INT8 calculator for up to 130 TOPS of INT8 computing. The Pi2 ECSs can also be used for light-load training.
Specifications
-Table 8 Pi2 ECS specifications Flavor
+Table 9 Pi2 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Local Disks
+Local Disks
Virtualization
+Virtualization
Hardware
+Hardware
pi2.2xlarge.4
+pi2.2xlarge.4
8
+8
32
+32
10/4
+10/4
50
+50
4
+4
4
+4
1 × T4
+1 × T4
1 × 16 GiB
+1 × 16 GiB
N/A
+N/A
KVM
+KVM
CPU: Intel® Xeon® Skylake 6151 3.0 GHz or Intel® Xeon® Cascade Lake 6278 2.6 GHz
+CPU: Intel® Xeon® Skylake 6151 3.0 GHz or Intel® Xeon® Cascade Lake 6278 2.6 GHz
pi2.3xlarge.4
+pi2.3xlarge.4
12
+12
48
+48
12/6
+12/6
80
+80
6
+6
6
+6
1 × T4
+1 × T4
1 × 16 GiB
+1 × 16 GiB
N/A
+N/A
KVM
+KVM
pi2.4xlarge.4
+pi2.4xlarge.4
16
+16
64
+64
15/8
+15/8
100
+100
8
+8
8
+8
2 × T4
+2 × T4
2 × 16 GiB
+2 × 16 GiB
N/A
+N/A
KVM
+KVM
pi2.8xlarge.4
+pi2.8xlarge.4
32
+32
128
+128
25/15
+25/15
200
+200
16
+16
8
+8
4 × T4
+4 × T4
4 × 16 GiB
+4 × 16 GiB
N/A
+N/A
KVM
+KVM
pi2.16xlarge.4
+pi2.16xlarge.4
64
+64
256
+256
30/30
+30/30
400
+400
32
+32
8
+8
8 × T4
+8 × T4
8 × 16 GiB
+8 × 16 GiB
N/A
+N/A
KVM
+KVM
ecs_02 must be in Stopped state.
- Start ecs_02.
Locate the row containing ecs_02, click More in the Operation column, and select Start from the drop-down list. Then, in the Start ECS dialog box, click OK.
-- Obtain the password for logging in to ecs_02.
- Locate the row containing ecs_02, click More in the Operation column, and select Get Password from the drop-down list.
- Click Select File and upload private key file Keypair_02 of ecs_02.
- Click Get Password to obtain a new random password.
- Obtain the password for logging in to ecs_02.
- Locate the row that contains ecs_02, click More in the Operation column and choose Get Password.
- Click Select File and upload private key file Keypair_02 of ecs_02.
- Click Get Password to obtain a new random password.
- Use the random password obtained in step 3 to log in to ecs_02 with the system disk replaced.
diff --git a/docs/ecs/umn/en-us_topic_0101604502.html b/docs/ecs/umn/en-us_topic_0101604502.html index 48fd7cc4e..4cfccf5ed 100644 --- a/docs/ecs/umn/en-us_topic_0101604502.html +++ b/docs/ecs/umn/en-us_topic_0101604502.html @@ -1,11 +1,11 @@How Do I Delete or Restart an ECS?
-Deleting an ECS
- Log in to the management console.
- Select the region where the ECS is located.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Delete in the Operation column.
If you choose to delete the EIP and data disks associated with the ECS when deleting it, no charges will apply for the EIP and data disks. However, if they are not deleted, they will continue o incur fees.
+-Deleting an ECS
- Log in to the management console.
- Select the region where the ECS is located.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Delete in the Operation column.
If you choose to delete the EIP and data disks associated with the ECS when deleting it, no charges will apply for the EIP and data disks. However, if they are not deleted, they will continue to incur fees.
Restarting an ECS
- Log in to the management console.
- Select the region where the ECS is located.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Restart in the Operation column.
Restarting an ECS
- Log in to the management console.
- Select the region where the ECS is located.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Restart in the Operation column.
diff --git a/docs/ecs/umn/en-us_topic_0101604508.html b/docs/ecs/umn/en-us_topic_0101604508.html index 9fa1f3b9c..9210af25d 100644 --- a/docs/ecs/umn/en-us_topic_0101604508.html +++ b/docs/ecs/umn/en-us_topic_0101604508.html @@ -5,7 +5,7 @@-- System disk image: contains an OS and application software for running services. You can use a system disk image to create ECSs and migrate your services to the cloud.
- Data disk image: contains only service data. You can create a data disk image from an ECS data disk. You can also use a data disk image to create EVS disks and migrate your service data to the cloud.
- Full-ECS image: contains all the data of an ECS, including the data on the data disks attached to the ECS. A full-ECS image can be used to rapidly create ECSs with service data.
You can use a private image to change the OS. For instructions about how to create a private image, see Image Management Service User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0115820205.html b/docs/ecs/umn/en-us_topic_0115820205.html index 798bc6947..822f395a9 100644 --- a/docs/ecs/umn/en-us_topic_0115820205.html +++ b/docs/ecs/umn/en-us_topic_0115820205.html @@ -2,7 +2,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, choose More > Manage Image/Backup > Create Image in the Operation column.
- Configure the following information:
Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
+-Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, choose More > Manage Image/Backup > Create Image in the Operation column.
- Configure the following information:
Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
Table 1 Image type and source Parameter
How Long Does It Take to Reinstall an ECS OS?
-Generally, the process of reinstalling the OS of an ECS takes about 1 to 2 minutes to complete. On the ECS console, stop the ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
+Generally, the process of reinstalling the OS of an ECS takes about 1 to 2 minutes to complete. On the ECS console, stop the ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
During this process, the ECS is in Reinstalling OS state.
Figure 1 Reinstalling an OSdiff --git a/docs/ecs/umn/en-us_topic_0102391480.html b/docs/ecs/umn/en-us_topic_0102391480.html index fefa26c85..146f9d756 100644 --- a/docs/ecs/umn/en-us_topic_0102391480.html +++ b/docs/ecs/umn/en-us_topic_0102391480.html @@ -12,17 +12,17 @@
- For instructions about how to back up an ECS, see Cloud Backup and Recovery User Guide.
- For instructions about how create a full-ECS image, see Image Management Service User Guide.
- Scenario 2: The ECS based on which the target CSBS backup is created is unavailable.
- Use the full-ECS image to create an ECS.
- Use the ECS to create a CBR backup. -
- Use the CBR backup to create a full-ECS image.
For details, see Image Management Service User Guide.
-You can use the full-ECS image to rapidly create ECSs.
+ - Use the new CBR to create a full-ECS image.
For details, see Image Management Service User Guide.
+You can use the full-ECS image to rapidly create ECSs.
Solution (Using CSBS)
If you want to use a full-ECS image to rapidly create ECSs, ensure that the full-ECS image is created using a CSBS backup in the new format. The procedure is as follows:
- Scenario 1: The ECS based on which the target CSBS backup is created is available.
Back up the original ECS on the Cloud Server Backup Service page and use the new format to create a full-ECS image. You can use the full-ECS image to rapidly create ECSs.
-- For instructions about how to back up an ECS, see Cloud Server Backup Service User Guide.
- For instructions about how create a full-ECS image, see Image Management Service User Guide.
- For instructions about how to back up an ECS, see Cloud Server Backup Service User Guide.
- For instructions about how create a full-ECS image, see Image Management Service User Guide.
- Scenario 2: The ECS based on which the target CSBS backup is created is unavailable.
How Can I View and Modify Kernel Parameters of a Linux ECS?
This document describes common Linux kernel parameters and how to view and modify them.
-
Modify the kernel parameters only if the parameter settings affect your services. If the parameter settings must be modified,
+ Modify the kernel parameters only if the parameter settings affect your services. If the parameter settings must be modified, perform the following:
- Ensure that the target parameter settings meet service requirements.
- Modify the correct kernel parameters. For details about common kernel parameters, see Table 1.
- Back up key ECS data before modifying kernel parameter settings.
Background
@@ -67,8 +67,8 @@Specifies the memory used by sockets for automatic optimization.
The first value is the minimum number of bytes allocated to the socket buffer for transmitting data.
-The second value is the default value, which is overwritten by wmem_default. The buffer size can increase to this value when the system load is not heavy.
-The third value is the maximum number of bytes allocated to the socket buffer for transmitting data. This value is overwritten by wmem_max.
+The second value is the default value, which is overwritten by wmem_default. The buffer size can increase to this value when the system load is not heavy.
+The third value is the maximum number of bytes allocated to the socket buffer for transmitting data. This value is overwritten by wmem_max.
net.ipv4.tcp_keepalive_time
@@ -123,7 +123,7 @@Allows fast recycle of TIME-WAIT sockets.
NOTE:This parameter is valid only when net.ipv4.tcp_timestamps is enabled.
-Do not set this parameter to 1 if NAT is enabled. Otherwise, an error will occur during remote ECS logins.
+Do not set this parameter to 1 if NAT is enabled. Otherwise, an error will occur during remote ECS logins.
Modifying Kernel Parameter Settings
- Method 1: Run the echo command in /proc/sys to modify the file for the target kernel parameters.
The parameter values changed using this method take effect only during the current running and will be reset after the system is restarted. To make the modification take effect permanently, see method 2.
-/proc/sys/ is a pseudo directory generated after the Linux kernel is started. The net folder in this directory stores all kernel parameters that have taken effect in the system. The directory tree structure is determined based on complete parameter names. For example, net.ipv4.tcp_tw_recycle corresponds to the /proc/sys/net/ipv4/tcp_tw_recycle file, and the content of the file is the parameter value.
+/proc/sys/ is a pseudo directory generated after the Linux kernel is started. The net folder in this directory stores all kernel parameters that have taken effect in the system. The directory tree structure is determined based on complete parameter names. For example, net.ipv4.tcp_tw_recycle corresponds to the /proc/sys/net/ipv4/tcp_tw_recycle file, and the content of the file is the parameter value.
Example:
To change the net.ipv4.tcp_tw_recycle value to 0, run the following command:
echo "0" > /proc/sys/net/ipv4/tcp_tw_recycle
diff --git a/docs/ecs/umn/en-us_topic_0108255889.html b/docs/ecs/umn/en-us_topic_0108255889.html index 23435eec9..741e8415b 100644 --- a/docs/ecs/umn/en-us_topic_0108255889.html +++ b/docs/ecs/umn/en-us_topic_0108255889.html @@ -26,7 +26,7 @@
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- View Failures on the right side of common operations.Figure 1 Failures+
diff --git a/docs/ecs/umn/en-us_topic_0114225937.html b/docs/ecs/umn/en-us_topic_0114225937.html index 4e7d6635a..a04273771 100644 --- a/docs/ecs/umn/en-us_topic_0114225937.html +++ b/docs/ecs/umn/en-us_topic_0114225937.html @@ -37,7 +37,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- View Failures on the right side of common operations.Figure 1 Failures
- Click the number displayed in the Failures area to view task details.
- Creation Failures: show the failed ECS creation tasks.
- Operation Failures: show the tasks with failed operations and error codes, which help you troubleshoot the faults.
- Run the following command to view the SAN policy on the ECS:san-
- If the SAN policy is OnlineAll, run the exit command to exit DiskPart.
- If the SAN policy is not OnlineAll, go to step 5.
- Run the following command to change the SAN policy to OnlineAll:
san policy=onlineall
+ - Run the following command to change the SAN policy to OnlineAll:
san policy=onlineall
- (Optional) Use the ECS with the SAN policy changed to create a private image so that the configuration takes effect permanently. After an ECS is created using this private image, the disks attached to the ECS are online by default. You only need to initialize them.
How Can I Test the Network Performance of Linux ECSs?
Use netperf and iperf3 to test network performance between ECSs. The test operations include preparations, TCP bandwidth test, UDP PPS test, and latency test.
-Background
- Tested ECS: an ECS that is tested for network performance. Such an ECS functions as the client (TX end) or server (RX end) in netperf tests.
- Auxiliary ECS: an ECS that is used to exchange test data with the tested ECS. The auxiliary ECS functions as the client (TX end) or server (RX end) in netperf tests.
- Table 1 and Table 2 list the common netperf and iperf3 parameters.
+
Background
- Tested ECS: an ECS that is tested for network performance. Such an ECS functions as the client (TX end) or server (RX end) in netperf tests.
- Auxiliary ECSs: an ECS that is used to exchange test data with the tested ECS. The auxiliary ECS functions as the client (TX end) or server (RX end) in netperf tests.
- Table 1 and Table 2 list the common netperf and iperf3 parameters.
Table 1 Common netperf parameters Parameter
Description
@@ -71,7 +71,7 @@-l
Data packet size, which is suggested to be 16 in PPS tests
+Data packet size, which is suggested to be 16 in PPS tests
-A
@@ -323,23 +323,23 @@iperf3 -s -p 12005 -A 4 -i 60 &
iperf3 -s -p 12006 -A 5 -i 60 &
-##The port number is for the fourth auxiliary ECS.
+##The port number is for the fourth auxiliary ECS.
iperf3 -s -p 12007 -A 6 -i 60 &
iperf3 -s -p 12008 -A 7 -i 60 &
-##The port number is for the fifth auxiliary ECS.
+##The port number is for the fifth auxiliary ECS.
iperf3 -s -p 12009 -A 8 -i 60 &
iperf3 -s -p 12010 -A 9 -i 60 &
-##The port number is for the sixth auxiliary ECS.
+##The port number is for the sixth auxiliary ECS.
iperf3 -s -p 12011 -A 10 -i 60 &
iperf3 -s -p 12012 -A 11 -i 60 &
-##The port number is for the seventh auxiliary ECS.
+##The port number is for the seventh auxiliary ECS.
iperf3 -s -p 12013 -A 12 -i 60 &
iperf3 -s -p 12014 -A 13 -i 60 &
-##The port number is for the eighth auxiliary ECS.
+##The port number is for the eighth auxiliary ECS.
iperf3 -s -p 12015 -A 14 -i 60 &
iperf3 -s -p 12016 -A 15 -i 60 &
- Start the client process on all auxiliary ECSs. For details about common iperf3 parameters, see Table 2.
Log in to auxiliary ECS 1.
diff --git a/docs/ecs/umn/en-us_topic_0116262067.html b/docs/ecs/umn/en-us_topic_0116262067.html index a29a276bc..ddd90286d 100644 --- a/docs/ecs/umn/en-us_topic_0116262067.html +++ b/docs/ecs/umn/en-us_topic_0116262067.html @@ -1,6 +1,6 @@ -ECS Operations Supported by CTS
+Key Operations Supported by CTS
Scenarios
Cloud Trace Service (CTS) records user operations performed on ECSs and related resources for further query, auditing, and backtracking.
Prerequisites
CTS has been enabled.
diff --git a/docs/ecs/umn/en-us_topic_0116266206.html b/docs/ecs/umn/en-us_topic_0116266206.html index a09aa4f52..48c7264c6 100644 --- a/docs/ecs/umn/en-us_topic_0116266206.html +++ b/docs/ecs/umn/en-us_topic_0116266206.html @@ -5,7 +5,7 @@-
-
- ECS Operations Supported by CTS
+ - Key Operations Supported by CTS
- Viewing Traces
diff --git a/docs/ecs/umn/en-us_topic_0116634723.html b/docs/ecs/umn/en-us_topic_0116634723.html
index 2d3bf163f..abb2a33e0 100644
--- a/docs/ecs/umn/en-us_topic_0116634723.html
+++ b/docs/ecs/umn/en-us_topic_0116634723.html
@@ -3,7 +3,7 @@
- Before installing a GUI on an ECS, ensure that the memory is no less than 2 GB to prevent GUI installation or ECS startup failures.
- Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
- Run the following command to obtain the installation component provided by the OS:
- Run the following command to set the default startup level to 5 (GUI):
sed -i 's/id:3:initdefault:/id:5:initdefault:/' /etc/inittab
diff --git a/docs/ecs/umn/en-us_topic_0117006217.html b/docs/ecs/umn/en-us_topic_0117006217.html index ef6e402cc..2e20659f4 100644 --- a/docs/ecs/umn/en-us_topic_0117006217.html +++ b/docs/ecs/umn/en-us_topic_0117006217.html @@ -5,7 +5,9 @@- Log in to the ECS.
- Run the following command to switch to user root:
sudo su
- Run the following command to obtain the grub version:
Figure 1 Viewing the grub version-
- Change the timeout in the grub file to 0s.
- If the grub version is earlier than 2:
Open the /boot/grub/grub.cfg or /boot/grub/menu.lst file and change the timeout value to 0.
+ - Change the timeout in the grub file to 0s.+
This operation involves modifying the GRUB configuration file. Misoperations may cause the system to fail to start. Before the operation, back up the GRUB configuration file so that it can be restored in case of misoperations.
+- If the grub version is earlier than 2:
Open the /boot/grub/grub.cfg or /boot/grub/menu.lst file and change the timeout value to 0.
Why Does the System Display Error Code 0x112f When I Log In to a Windows ECS?
+Why Does the System Display Error Code 0x112f When I Log In to a Windows ECS?
diff --git a/docs/ecs/umn/en-us_topic_0122627689.html b/docs/ecs/umn/en-us_topic_0122627689.html index 0b2e03cff..14fd7c70d 100644 --- a/docs/ecs/umn/en-us_topic_0122627689.html +++ b/docs/ecs/umn/en-us_topic_0122627689.html @@ -30,7 +30,7 @@Symptom
When you log in to a Windows ECS, the system displays error code 0x112f, as shown in Figure 1.
Linux
- Use the existing key file to log in to the ECS as user root through SSH.
For details, see Logging In to a Linux ECS Using an SSH Key Pair.
- Run the following command to reset the password of user root:
passwd
To reset the password of another user, replace passwd with passwd username.
- - Enter a new password that meets the requirements listed in Table 1 as prompted.
New password: +
- Enter a new password that meets the requirements listed in Table 1 as prompted.
New password: Retype new password:
If the following information is displayed, the password has been changed:diff --git a/docs/ecs/umn/en-us_topic_0140313880.html b/docs/ecs/umn/en-us_topic_0140313880.html index a12f3e619..c93067196 100644 --- a/docs/ecs/umn/en-us_topic_0140313880.html +++ b/docs/ecs/umn/en-us_topic_0140313880.html @@ -1,10 +1,17 @@passwd: all authentication tokens updates successfully
Overview
-What Is Elastic Volume Service?
Elastic Volume Service (EVS) offers scalable block storage for
- If the grub version is earlier than 2:
- If the grub version is earlier than 2:
How Can I Install a GUI on an ECS Running CentOS 6?
-Scenarios
To provide a pure system, the ECSs running CentOS 6 do not have a GUI installed by default. You can install a GUI on such ECSs as needed.
Constraints
Constraints
Procedure
- Start the client process on all auxiliary ECSs. For details about common iperf3 parameters, see Table 2.
- After a P2v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- After a P2s ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- After a P3 ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- (Optional) To use local server resources in a remote session, configure parameters on the Local Resources tab.
- Click OK to restart the selected ECSs.
- Click OK to stop the selected ECSs.
- Click the search box and select a property.
- Server List: The ECS to be backed up is selected by default. Click
- If the ECS has been associated with a vault, configure the backup information as prompted.
- If the ECS has been associated with a vault, configure the backup information as prompted.
