- Routine data backup
You can create snapshots for disks on a timely basis and use snapshots to recover your data in case that data loss or data inconsistency occurred due to unintended actions, viruses, or attacks.
+- Routine data backup
You can create snapshots for disks on a timely basis and use snapshots to recover your data in case that data is lost or inconsistent due to unintended actions, viruses, or attacks.
- Rapid data restoration
You can create a snapshot or multiple snapshots before an application software upgrade or a service data migration. If an exception occurs during the upgrade or migration, service data can be rapidly restored to the time point when the snapshot was created.
For example, if ECS A cannot be started due to a fault occurred in system disk A, you can create disk B using an existing snapshot of system disk A and attach disk B to a properly running ECS, for example ECS B. In this case, ECS B can read the data of system disk A from the disk B.
- Rapid deployment of multiple services
You can use a snapshot to create multiple EVS disks containing the same initial data, and these disks can be used as data resources for various services, for example data mining, report query, and development and testing.
diff --git a/docs/ecs/umn/en-us_topic_0000001128604648.html b/docs/ecs/umn/en-us_topic_0000001128604648.html index 208ce85eb..bf13c8325 100644 --- a/docs/ecs/umn/en-us_topic_0000001128604648.html +++ b/docs/ecs/umn/en-us_topic_0000001128604648.html @@ -6,7 +6,7 @@You can back up ECS data using Cloud Server Backup or Cloud Disk Backup.-- Cloud Server Backup (recommended): Use this backup function if you want to back up the data of all EVS disks (system and data disks) on an ECS. This prevents data inconsistency caused by time difference in creating a backup.
- Cloud Disk Backup: Use this backup function if you want to back up the data of one or more EVS disks (system or data disk) on an ECS. This minimizes backup costs on the basis of data security.
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 in the Operation column.
- 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 in the Operation column.
- 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 in the Operation column.
- 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 in the Operation column.
- 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 page, if the status of the backup is Available, the backup task is successful.
diff --git a/docs/ecs/umn/en-us_topic_0000001630328828.html b/docs/ecs/umn/en-us_topic_0000001630328828.html new file mode 100644 index 000000000..5e46ceaae --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0000001630328828.html @@ -0,0 +1,123 @@ + + +Searching for ECSs
+++Scenarios
After purchasing an ECS, you can use the search function on the management console to search for ECSs in the current region. You can search for ECSs by name, ID, AZ, status, flavor name, image ID, EIP, private IP address, creation time, VPC ID, enterprise project, or resource tag.
++
Searching by enterprise project is only available for enterprise users.
++Search Syntax
A variety of ECS search types are available. For details, see Table 1.
++ + - For certain properties, if you enter complete values, the system can automatically identity the property type and search for them.
- The following properties only support exact search and you need to enter complete values: ID, image ID, EIP, VPC ID, and enterprise project.
- The private IP address must be in the following CIDR blocks: 10.0.0.0/8-24, 172.16.0.0/12-24, and 192.168.0.0/16-24.
- You can search by tag key-value pair. You can add one or more tags. If keys are different, the tags are automatically joined with AND. If the keys are the same but the values are different, the tags are also automatically joined with AND.
- You cannot use both the private IP address and EIP for a combination of search.
+
+Table 1 Search syntax Search Type
+Supported Property
+Format
+Example
+Description
+Attribute value
+Automatic property matching
+ID
+Flavor name
+EIP
+Private IP address
+Complete property value
+ID: 4a79dfec-f0d8-4181-9bef-495b8b7220e1
+Flavor Name: s2.xlarge.4
+Private IP Address: 192.168.99.231
+When you search by keyword, enter a complete property value instead of selecting a property. The system can automatically match the property type for search.
+Attribute value
+Fuzzy search
+Name
+Private IP address
+Flavor name
+Incomplete property value
+Name: ecs-c
+Flavor name: s7n
+Private IP address: 192.168.0
+Select a property, and enter or choose the corresponding property value.
+Single property
+All properties on the console
+Attribute: Value
+Private IP Address: 192.168.99.231
+Select a property, and enter or choose the corresponding property value.
+The following properties only support exact search and you need to enter complete values for them: ID, EIP, image ID, and VPC ID.
+Multiple properties
+All properties on the console
+Attribute 1: Value Attribute 2: Value
+Private IP Address: 192.168.99.231 Name: ecs-c
+You can search by multiple properties and the properties are in AND relationship.
+The following properties only support exact search and you need to enter complete values for them: ID, EIP, image ID, and VPC ID.
++Procedure
- Log in to the management console.
- Under Computing, click 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.
- Click the search box and select a property.
+Example 1: Searching by Attribute Value
After you enter a complete property value, the system automatically identifies the property type and search for it.
+ ++Example 2: Searching by a Single Attribute
Select a property, and enter or choose the corresponding property value.
+The following properties only support exact search and you need to enter complete values for them: ID, EIP, image ID, and VPC ID.
+- Fuzzy search by private IP address
- Select Private IP Address in the search box.
- Enter a private IP address and press Enter to search. Private IP addresses can be used for fuzzy search. For example, you can enter 192.168.0 to search for all ECSs that use the 192.168.0 IP address.
- Exact search by ID
- Select ID in the search box.
- Enter a complete ECS ID and press Enter to search.
+Example 3: Searching by Multiple Properties
You can search by multiple properties and the properties are in AND relationship.
+The following properties only support exact search and you need to enter complete values for them: ID, EIP, image ID, and VPC ID.
+In this example, use Name and Private IP Address for a combination of search.
+- Select Name and enter an ECS name in the search box for fuzzy search.
- Select Private IP Address and enter a private IP address for fuzzy search.
+Example 4: Searching by Tags
You can search by tag key-value pair.
+You can add one or more tags. If keys are different, the tags are automatically joined with AND.
+If the keys are the same but the values are different, the tags are also automatically joined with AND.
+ +++ diff --git a/docs/ecs/umn/en-us_topic_0013771089.html b/docs/ecs/umn/en-us_topic_0013771089.html index 8b5fc7f56..7ce15fe31 100644 --- a/docs/ecs/umn/en-us_topic_0013771089.html +++ b/docs/ecs/umn/en-us_topic_0013771089.html @@ -35,7 +35,7 @@++Parent topic: Resources and Tags+Windows
Use the remote login function available on the management console.
- +No EIP is required.
Starting and Stopping ECSs
-You can start, stop, restart, and delete ECSs.
-- To prevent load increase when starting or stopping a large number of ECSs at the same time, you are advised to select a small number of ECSs for each batch.
- 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.
Procedure
- 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.
- Above the list, click Start, Stop, or choose More > Restart or Delete.
- In the displayed window, click Yes.
Contact the administrator if an ECS has been in any of the following intermediate states for more than 30 minutes:
-- Starting
- Stopping
- Restarting
- Forcibly restarting
- Deleting
You can start, stop, restart, or delete the ECS.
+- 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.
+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 Yes.+
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.
+ - Click Yes to stop the 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.
+ - Click Yes to stop the ECSs.+
Contact the administrator if the ECS has been in the Restarting 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 91874aa5f..2008184b2 100644 --- a/docs/ecs/umn/en-us_topic_0017130261.html +++ b/docs/ecs/umn/en-us_topic_0017130261.html @@ -5,7 +5,7 @@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.
To view the private IP address of an ECS, view it on the Elastic Cloud Server page.
diff --git a/docs/ecs/umn/en-us_topic_0017955380.html b/docs/ecs/umn/en-us_topic_0017955380.html index ab546656f..16e322251 100644 --- a/docs/ecs/umn/en-us_topic_0017955380.html +++ b/docs/ecs/umn/en-us_topic_0017955380.html @@ -1,6 +1,6 @@ -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.
- - 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 click
. Alternatively, click Search by Tag above the upper right corner of the ECS list and search for an ECS by tag key and value. - Click the name of the target ECS.
The page providing details about the ECS is displayed.
+ - 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, Adding a Network Interface, Adding Tags, and Binding an EIP.
Login Using an SSH Key
+Remotely 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).
PuTTYgen is a key generator, which is used to create a key pair that consists of a public key and a private key for PuTTY.
- Run PuTTYgen.
- In the Actions pane, click Load and import the private key file that you stored during ECS creation.
Ensure that the format of All files (*.*) is selected.
-- Click Save private key.
- Save the converted private key, for example, kp-123.ppk, to the local computer.
- Double-click PUTTY.EXE. The PuTTY Configuration page is displayed.
- Choose Session and enter the EIP of the ECS under Host Name (or IP address).
Figure 1 Configuring the EIP-
- Choose Connection > Data. Enter the image username in Auto-login username.
- If a public image is used, see Public Images Introduction for the image username.
- If a private image is used, use the username of the private image.
Figure 1 Importing the private key file+
- In the Actions area, click Save private key.
- Save the converted private key, for example, kp-123.ppk, to the local computer.
- Double-click PUTTY.EXE. The PuTTY Configuration page is displayed.
- Choose Session and enter the EIP of the ECS under Host Name (or IP address).
Figure 2 Configuring the EIP+- Choose Connection > Data. Enter the image username in Auto-login username.
Figure 3 Entering the username+
- - If a public image is used, see Public Images Introduction for the image username.
- If a private image is used, use the username of the private image.
- Choose Connection > SSH > Auth. In the last configuration item Private key file for authentication, click Browse and select the private key converted in step 6.
- Click Open to log in to the ECS.
+- Choose Connection > SSH > Auth > Credentials. In the configuration item Private key file for authentication, click Browse and select the private key converted in step 6.
Figure 4 Importing the private key file+
- Click Open to log in to the ECS.
Method 2: Use Xshell to log in to the ECS.
- Start the Xshell tool.
- Run the following command using the EIP to remotely log in to the ECS through SSH:
ssh Username@EIP
- - If a public image is used, see Public Images Introduction for the image username.
- If a private image is used, use the username of the private image.
- (Optional) If the system displays the SSH Security Warning dialog box, click Accept & Save.Figure 2 SSH Security Warning+
- (Optional) If the system displays the SSH Security Warning dialog box, click Accept & Save.Figure 5 SSH Security Warning
- Select Public Key and click Browse beside the user key text box.
- In the user key dialog box, click Import.
- Select the locally stored key file and click Open.
- Click OK to log in to the ECS.
Logging In to a Linux ECS from a Local Linux Server
To log in to the Linux ECS from local Linux, perform the operations described in this section. The following operations use private key file kp-123.pem as an example to log in to the ECS. The name of your private key file may differ.- On the Linux CLI, run the following command to change operation permissions:
diff --git a/docs/ecs/umn/en-us_topic_0017955381.html b/docs/ecs/umn/en-us_topic_0017955381.html
index 8e61f3b45..5ebfd1d05 100644
--- a/docs/ecs/umn/en-us_topic_0017955381.html
+++ b/docs/ecs/umn/en-us_topic_0017955381.html
@@ -1,6 +1,6 @@
-
Login Using MSTSC
+Remotely 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.
Enabling RDP
For your first login, use VNC to log in and enable RDP for your ECS. Then, use MSTSC to log in.- By default, RDP has been enabled on the ECSs created using a public image.
- Log in to the Windows ECS using VNC.
For details, see Login Using VNC.
+- Log in to the Windows ECS using VNC.
For details, see Remotely Logging In to a Windows ECS (Using VNC).
- Click Start in the task bar and choose Control Panel > System and Security > System > Remote settings.
The System Properties dialog box is displayed.
Figure 6 System Properties
- Click the Remote tab and select Allow remote connections to this computer.
- Click OK.
Login Using an SSH Password
+Remotely Logging In to a Linux ECS (Using an SSH Password)
Scenarios
This section describes how to remotely log in to a Linux ECS using an SSH password from a Windows and a Linux server, respectively.
@@ -9,7 +9,7 @@ Logging in to a Linux ECS using SSH password authentication is disabled by default. If you require password authentication, configure it after logging in to the ECS. To ensure system security, reset the common user password for logging in to the Linux ECS after configuring SSH password authentication.
- Access to port 22 is allowed in the inbound direction of the security group to which the ECS belongs. 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.
- You have obtained the SSH login permission and reset the common user password for logging in to the Linux ECS. For details, see Configuring the Login Permission Using SSH Password Authentication.
Configuring the Login Permission Using SSH Password Authentication
Assigning the remote login permission using SSH key authentication
-- Use the SSH key to log in to the Linux ECS. For details, see Login Using an SSH Key.
- Run the following command to change the value of PasswordAuthentication in /etc/ssh/sshd_config to yes:
sudo vi /etc/ssh/sshd_config
+- Use the SSH key to log in to the Linux ECS. For details, see Remotely Logging In to a Linux ECS (Using an SSH Key Pair).
- Run the following command to change the value of PasswordAuthentication in /etc/ssh/sshd_config to yes:
sudo vi /etc/ssh/sshd_config
For the ECSs running the SUSE or OpenSUSE OSs, ensure that the values of PasswordAuthentication, ChallengeResponseAuthentication, and UsePAM in /etc/ssh/sshd_config are all yes.
- Run the following command to change the ssh_pwauth value to 1 or true in /etc/cloud/cloud.cfg:
sudo vi /etc/cloud/cloud.cfg
diff --git a/docs/ecs/umn/en-us_topic_0018073215.html b/docs/ecs/umn/en-us_topic_0018073215.html index 8925f3419..edf3fc8e0 100644 --- a/docs/ecs/umn/en-us_topic_0018073215.html +++ b/docs/ecs/umn/en-us_topic_0018073215.html @@ -20,7 +20,7 @@59
VBD disks + SCSI disks ≤ 60 (This constraint does not apply to local disks.)
-The number of local disks is determined based on the ECS flavor.
+The number of local disks is determined based on the ECS flavor.
- Log in to the Windows ECS using VNC.
D2
@@ -30,7 +30,7 @@30
VBD disks + SCSI disks ≤ 54 (This constraint does not apply to local disks.)
-The number of local disks is determined based on the ECS flavor.
+The number of local disks is determined based on the ECS flavor.
What Happens After I Click the Delete Button?
After you click Delete, the selected ECSs will be deleted. You can also choose to delete the EVS disks and EIPs together with the selected ECSs. If you do not delete them, they will be retained. If necessary, you can manually delete them later.
To delete selected ECSs, perform the following operations:
-- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
- Select the ECSs to be deleted.
- Above the ECS list, choose Delete.Figure 1 Deleting selected ECSs+
- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
- Select the ECSs to be deleted.
- Above the ECS list, choose Delete.Figure 1 Deleting selected ECSs
diff --git a/docs/ecs/umn/en-us_topic_0021426802.html b/docs/ecs/umn/en-us_topic_0021426802.html index 51889f617..9ea09164f 100644 --- a/docs/ecs/umn/en-us_topic_0021426802.html +++ b/docs/ecs/umn/en-us_topic_0021426802.html @@ -57,7 +57,7 @@ Write hive files? (y/n) [n] : yPassword
- 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.)
- 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.)
- Cannot start with a slash (/) for Windows ECSs.
YNbUwp!dUc9MClnv
NOTE:The example password is generated randomly. Do not use it.
diff --git a/docs/ecs/umn/en-us_topic_0021427650.html b/docs/ecs/umn/en-us_topic_0021427650.html index 3e6472e47..5887ab518 100644 --- a/docs/ecs/umn/en-us_topic_0021427650.html +++ b/docs/ecs/umn/en-us_topic_0021427650.html @@ -23,11 +23,11 @@- Enter the new password and the directory obtained in step 4.b as prompted.
-If the following information is displayed, the password has been changed:set password success.
- (Optional) For a non-root user, perform the following operations to enable the login permissions for user root:
vi /etc/ssh/sshd_config
-Modify the following parameters:
-- Change PasswordAuthentication no to PasswordAuthentication yes.
Alternatively, delete the comment tag (#) before PasswordAuthentication yes.
- - Change PermitRootLogin no to PermitRootLogin yes.
Alternatively, delete the comment tag (#) before PermitRootLogin yes.
- - Change the value of AllowUsers to root.
Search for AllowUsers in the file. If AllowUsers is unavailable, add it at the end of the file.
+ - (Optional) Enable remote root login for non-root users.
+
Modify the following settings:
+- Change PasswordAuthentication no to PasswordAuthentication yes.
Alternatively, uncomment PasswordAuthentication yes.
+ - Change PermitRootLogin no to PermitRootLogin yes.
Alternatively, uncomment PermitRootLogin yes.
+ - Change the value of AllowUsers to root.
Search for AllowUsers in the file. If AllowUsers is missing, add it at the end of the file.
- Change PasswordAuthentication no to PasswordAuthentication yes.
- Stop the temporary ECS, detach the system disk, attach the system disk to the original Linux ECS, and restart the original Linux ECS.
- Stop the temporary ECS, switch to the page providing details about the ECS, and click the Disks tab.
- Click Detach to detach the data disk attached in step 2.
- On the page providing details about the original Linux ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the data disk detached in 6.b.
- Restart the original Linux ECS. diff --git a/docs/ecs/umn/en-us_topic_0024911405.html b/docs/ecs/umn/en-us_topic_0024911405.html index 8f046d2e7..6c89615ea 100644 --- a/docs/ecs/umn/en-us_topic_0024911405.html +++ b/docs/ecs/umn/en-us_topic_0024911405.html @@ -3,21 +3,21 @@
- After the OS is reinstalled, the IP and MAC addresses of the ECS remain unchanged.
- Reinstalling the OS clears the data in all partitions of the EVS system disk, including the system partition. Therefore, back up data before reinstalling the OS.
- Reinstalling the OS does not affect data disks.
- Do not perform any operations on the ECS immediately after its OS is reinstalled. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- After the OS is reinstalled, the password for logging in to the ECS will be 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 Login Using an SSH Key.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
Notes
- After the OS is reinstalled, the IP and MAC addresses of the ECS remain unchanged.
- Reinstalling the OS clears the data in all partitions of the EVS system disk, including the system partition. Therefore, back up data before reinstalling the OS.
- Reinstalling the OS does not affect data disks.
- Do not perform any operations on the ECS immediately after its OS is reinstalled. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- After the OS is reinstalled, the password for logging in to the ECS will be 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 Remotely 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.
- You can choose to encrypt the system disk of an ECS during OS reinstallation.
Constraints
- The EVS disk quotas must be greater than 0.
- If the target ECS is created using a private image, ensure that the private image is available.
- If an ECS OS is to be reinstalled using a full-ECS image, the ECS system disk can be encrypted.
-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 Encryption 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 permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights 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 assign KMS access permissions to EVS. If you have rights granting permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights to assign the 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: EVSAccessKMS: specifies 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.
-Figure 1 Reinstall OS+
Figure 1 Reinstall OS
- Click OK.
- On the ECS OS Reinstallation page, confirm the settings, and click Submit.After the request is submitted, the status Reinstalling is displayed. When this status disappears, the reinstallation is complete.diff --git a/docs/ecs/umn/en-us_topic_0027157850.html b/docs/ecs/umn/en-us_topic_0027157850.html index 0ce9408ce..24318fed7 100644 --- a/docs/ecs/umn/en-us_topic_0027157850.html +++ b/docs/ecs/umn/en-us_topic_0027157850.html @@ -40,7 +40,7 @@
A temporary ECS is created during the reinstallation process. After reinstallation, this ECS will be automatically deleted. Do not perform any operation on the temporary ECS during the reinstallation process.
- Run the following command to 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.
- To delete the added iptables rules, run the following command:
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_0027268511.html b/docs/ecs/umn/en-us_topic_0027268511.html index 30305ca2e..fea315759 100644 --- a/docs/ecs/umn/en-us_topic_0027268511.html +++ b/docs/ecs/umn/en-us_topic_0027268511.html @@ -1,6 +1,6 @@ -Login Using VNC
+Remotely Logging In to a Windows ECS (Using VNC)
Scenarios
This section describes how to use VNC provided on the management console to log in to an ECS. This function applies to emergency O&M. In other scenarios, you are advised to log in to ECSs using SSH or MSTSC.
Constraints
- The remote login function is implemented using customized ports. Therefore, before attempting to log in remotely, ensure that the port to be used is not blocked by the firewall. For example, if the remote login link is xxx:8002, ensure that port 8002 is not blocked by the firewall.
- If the client OS uses a local proxy and the firewall port cannot be configured on the local proxy, disable the proxy mode and then try logging in remotely.
- Certain G-series ECSs do not support remote login from the console. If you need to remotely log in to the ECSs, install the VNC server on them. For details, see GPU-accelerated ECSs. You are suggested to log in to the ECSs using MSTSC.
Log In to a Windows 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.
- Obtain the password for logging in to the ECS.
Before logging in to the ECS, you must have the login password.
For instructions about how to obtain the password for logging in to a Windows ECS, see Obtaining the Password for Logging In to a Windows ECS.
- - 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 keyboard that suits your language.
- When logging in to the ECS using VNC for the first time, select the default English keyboard. The ECS OS uses the English keyboard by default.
- If you have changed the keyboard language of the ECS OS, select the keyboard language to which you have changed.
- 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 keyboard that suits your language.
- When logging in to the ECS using VNC for the first time, select the default English keyboard. The ECS OS uses the English keyboard by default.
- If you have changed the keyboard language of the ECS OS, select the keyboard language to which you have changed.
Figure 5 Keyboard layout configuration-
- Click Remote Login.
- (Optional) If you have changed the system language, in the dialog box that is displayed, click Remote Login.Figure 6 Remote Login+
- Click Remote Login.
- (Optional) If you have changed the system language, in the dialog box that is displayed, click 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
- (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 7, and the changed OS keyboard language are all the same.
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.
What Is Elastic Volume Service?
Elastic Volume Service (EVS) offers scalable block storage for ECSs. With high reliability, high performance, and rich specifications, EVS disks can be used for distributed file systems, development and test environments, data warehouses, and high-performance computing (HPC) scenarios to meet diverse service requirements.
Disk Types
EVS disk types differ in performance. Choose a disk type based on your requirements.
-For more information about EVS disk specifications and performance, see Elastic Volume Service User Guide.
+For more information about EVS disk specifications and performance, see Elastic Volume Service User Guide.
Device Types
EVS disks have two device types, Virtual Block Device (VBD) and Small Computer System Interface (SCSI).- VBD
When you create an EVS disk on the management console, Device Type of the EVS disk is VBD by default. VBD EVS disks support only simple SCSI read/write commands.
- SCSI
You can create EVS disks whose Device Type is SCSI on the management console. These EVS disks support transparent SCSI command transmission, allowing ECS OS to directly access underlying storage media. SCSI EVS disks support both basic and advanced SCSI commands.
diff --git a/docs/ecs/umn/en-us_topic_0030828257.html b/docs/ecs/umn/en-us_topic_0030828257.html index d3f1cabbd..06d4a4823 100644 --- a/docs/ecs/umn/en-us_topic_0030828257.html +++ b/docs/ecs/umn/en-us_topic_0030828257.html @@ -56,7 +56,7 @@Figure 2 Accessing the Internet using an EIP
Network QoS
Network QoS uses basic technologies to improve the quality of network communication. A network with QoS enabled offers predictable network performance and effectively allocates network bandwidth to use network resources.
-To obtain the QoS data of an ECS flavor, including the maximum bandwidth, assured bandwidth, maximum PPS, and NIC multi-queue, see A Summary List of ECS Specifications.
+To obtain the QoS data of an ECS flavor, including the maximum bandwidth, assured bandwidth, maximum packets per second (PPS), and NIC multi-queue, see A Summary List of ECS Specifications.
The intranet bandwidth and PPS of an ECS are determined by its flavor.- Assured intranet bandwidth: indicates the guaranteed bandwidth allocated to an ECS.
- Maximum intranet bandwidth: indicates the maximum bandwidth that can be allocated to an ECS.
- Maximum intranet PPS: indicates the maximum ECS capability in transmitting and receiving packets.
- NIC multi-queue: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth.
- For instructions about how to test PPS, see How Can I Test Network Performance?
- For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
- Login Overview
- - Login Using VNC
+ - Remotely Logging In to a Linux ECS (Using VNC)
- - Login Using an SSH Key
+ - Remotely Logging In to a Linux ECS (Using an SSH Key Pair)
- - Login Using an SSH Password
+ - Remotely Logging In to a Linux ECS (Using an SSH Password)
- Configure required parameters.
You can click + to add more inbound rules.
Figure 1 Add Inbound Rule-
Table 1 Inbound rule parameter description Parameter
+Table 1 Inbound rule parameter description Parameter
Description
+Description
Example Value
- Configure required parameters.
You can click + to add more outbound rules.
Figure 2 Add Outbound Rule-
Table 2 Outbound rule parameter description Parameter
+Table 2 Outbound rule parameter description Parameter
Description
+Description
Example Value
Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example:
- IP address:
- Single IP address: 192.168.10.10/32
- All IP addresses: 0.0.0.0/0
- IP address range: 192.168.1.0/24
- Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
- IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
- Security group: The destination is from another security group. You can select a security group in the same region under the current account from the drop-down list. For example, instance A is in security group A and instance B is in security group B. If security group A has an outbound rule with Action set to Allow and Destination set to security group B, access from instance A is allowed to instance B.
- IP address group: A collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
+0.0.0.0/0
- Login Overview
- - Login Using VNC
+ - Remotely Logging In to a Windows ECS (Using VNC)
- - Login Using MSTSC
+ - Remotely Logging In to a Windows ECS (Using MSTSC)
- - Logging In to a Windows ECS from a Linux Computer
+ - Remotely Logging In to a Windows ECS (from a Linux Computer)
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.
-
+
- How Can I Change a Remote Login Port?
+
+ - Why Can't I Obtain the Password for Logging In to My Windows ECS Authenticated Using a Key Pair?
+
+ - What Browser Version Is Required to Remotely Log In to an ECS?
+
+ - How Can I Log In to an ECS After Its System Disk Is Exchanged with That Attached to Another ECS Running the Same OS?
+
+ - Why Does the System Display a Message Indicating that the Password for Logging In to a Windows ECS Cannot Be Obtained?
+ - Why Are Characters Entered Through VNC Still Incorrect After the Keyboard Language Is Switched?
- What Should I Do If I Cannot Use the German Keyboard to Enter Characters When I Log In to a Linux ECS Using VNC?
@@ -22,16 +32,6 @@ - How Can I Change the Resolution of a Windows ECS?
- - How Can I Change a Remote Login Port?
-
- - Why Can't I Obtain the Password for Logging In to My Windows ECS Authenticated Using a Key Pair?
-
- - What Browser Version Is Required to Remotely Log In to an ECS?
-
- - How Can I Log In to an ECS After Its System Disk Is Exchanged with That Attached to Another ECS Running the Same OS?
-
- - Why Does the System Display a Message Indicating that the Password for Logging In to a Windows ECS Cannot Be Obtained?
- - Why Does an Authentication Failure Occurs After I Attempt to Remotely Log In to a Windows ECS?
- Why Can't I Use the Local Computer to Connect to My Windows ECS?
diff --git a/docs/ecs/umn/en-us_topic_0030932496.html b/docs/ecs/umn/en-us_topic_0030932496.html index a694e46e3..280361eaa 100644 --- a/docs/ecs/umn/en-us_topic_0030932496.html +++ b/docs/ecs/umn/en-us_topic_0030932496.html @@ -5,7 +5,7 @@loadkeys keymapfile
keymapfile is the name of the file for the mapping between keys and displayed characters.
For example, if the name of a German keyboard mapping file is de, run the loadkeys de command.
-For instructions about how to configure the keyboard language for a Linux ECS, see Login Using VNC.
+For instructions about how to configure the keyboard language for a Linux ECS, see Remotely Logging In to a Linux ECS (Using VNC).
Procedure
- For all Linux ECSs, characters â, ê, ô, û, and î cannot be entered properly. To enter such characters, use either of the following methods:
Method 1: Press ^+Space+Letter key.
Method 2: Click ^° on the VNC page and then press the suitable key on the keyboard.
diff --git a/docs/ecs/umn/en-us_topic_0031523135.html b/docs/ecs/umn/en-us_topic_0031523135.html index ca81d12b1..741098461 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 10 to 20 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 pair. Otherwise, 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.
- 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.
- Do not perform any operations on the ECS immediately after its OS is changed. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- 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 Login Using an SSH Key.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
@@ -21,7 +21,7 @@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.
- 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.
- Do not perform any operations on the ECS immediately after its OS is changed. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- 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 Remotely 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 more details, see Creating an ECS.
Figure 1 OS Change
- (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 permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights to assign the KMS access permissions. For details, see Can All Users Use the Encryption Feature?
diff --git a/docs/ecs/umn/en-us_topic_0032380449.html b/docs/ecs/umn/en-us_topic_0032380449.html index 5d981eeaa..6a0c91fa5 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.txtAfter 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: @@ -154,7 +154,7 @@ write_files:
Password
- 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.)
- 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.)
- Cannot start with a slash (/) for Windows ECSs.
YNbUwp!dUc9MClnv
NOTE:The example password is generated randomly. Do not use it.
@@ -194,7 +194,7 @@ echo 'root:$6$V6azyeLwcD3CHlpY$BN3VVq18fmCkj66B4zdHLWevqcxlig' | chpasswd -e;Password
- 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.)
- 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.)
- Cannot start with a slash (/) for Windows ECSs.
YNbUwp!dUc9MClnv
NOTE:-The example password is generated randomly. Do not use it.
@@ -229,7 +229,7 @@ yum update -y service httpd start chkconfig httpd onCase 6
This case illustrates how to use the user data passing function to assign user root permissions for remotely logging in to a Linux ECS. After passing the file to an ECS, you can log in to the ECS as user root using SSH key pair authentication.
+Case 6
This case illustrates how to pass the user data to assign user root permissions for remotely logging in to a Linux ECS. After passing the file to an ECS, you can log in to the ECS as user root using SSH key pair authentication.
User data example:
#cloud-config disable_root: false diff --git a/docs/ecs/umn/en-us_topic_0035470096.html b/docs/ecs/umn/en-us_topic_0035470096.html index 5071167e5..e26a8b6cb 100644 --- a/docs/ecs/umn/en-us_topic_0035470096.html +++ b/docs/ecs/umn/en-us_topic_0035470096.html @@ -17,7 +17,7 @@
Network QoS
Network QoS uses basic technologies to improve the quality of network communication. A network with QoS enabled offers predictable network performance and effectively allocates network bandwidth to use network resources.
To obtain the QoS data of an ECS flavor, including the maximum bandwidth, assured bandwidth, maximum intranet PPS, and NIC multi-queue, see A Summary List of ECS Specifications.
The intranet bandwidth and PPS of an ECS are determined by the ECS flavor.- Assured intranet bandwidth: indicates the guaranteed bandwidth allocated to an ECS when there is a network bandwidth contention in the entire network.
- Maximum intranet bandwidth: indicates the maximum bandwidth that can be allocated to an ECS when the ECS does not compete for network bandwidth (other ECSs on the host do not have high requirements on network bandwidth).
- Maximum intranet PPS: indicates the maximum ECS capability in sending and receiving packets.
PPS: packets per second, indicates the number of packets sent per second. It is usually used to measure the network performance.
- - NIC multi-queues: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth
- Maximum NICs: indicates the maximum number of NICs that can be attached to an ECS.- diff --git a/docs/ecs/umn/en-us_topic_0035470099.html b/docs/ecs/umn/en-us_topic_0035470099.html index dfac86a98..4a244f137 100644 --- a/docs/ecs/umn/en-us_topic_0035470099.html +++ b/docs/ecs/umn/en-us_topic_0035470099.html @@ -140,7 +140,7 @@
- For instructions about how to test PPS, see How Can I Test Network Performance?
- For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
- The maximum bandwidth is the total bandwidth allocated to an ECS. If an ECS has multiple NICs, the sum of the maximum bandwidths allocated to all NICs cannot exceed the maximum bandwidth allocated to the ECS.
- NIC multi-queues: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth
- Maximum NICs: indicates the maximum number of NICs that can be attached to an ECS.
- For instructions about how to test PPS, see How Can I Test Network Performance?.
- For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
- The maximum bandwidth is the total bandwidth allocated to an ECS. If an ECS has multiple NICs, the sum of the maximum bandwidths allocated to all NICs cannot exceed the maximum bandwidth allocated to the ECS.
- Application scenarios
Big data computing, network file systems, data processing, MapReduce, Hadoop, and data-intensive computing
D2 ECS Features
- D2 ECSs use local disks to provide high sequential read/write performance and low latency, improving file read/write performance.
- D2 ECSs provide powerful and stable computing capabilities, ensuring efficient data processing.
- D2 ECSs with a vCPU/memory ratio of 1:8 process large volumes of data.
- D2 ECSs provide high intranet performance, including high intranet bandwidth and PPS, meeting requirements for data exchange between ECSs during peak hours.
- Each D2 ECS supports a maximum configuration of 24 local disks, 60 vCPUs, and 540 GiB memory.
D2 ECS Features
- D2 ECSs use local disks to provide high sequential read/write performance and low latency, improving file read/write performance.
- D2 ECSs provide powerful and stable computing capabilities, ensuring efficient data processing.
- D2 ECSs with a vCPU/memory ratio of 1:8 process large volumes of data.
- D2 ECSs provide high intranet performance, including high intranet bandwidth and packets per second (PPS), meeting requirements for data exchange between ECSs during peak hours.
- Each D2 ECS supports a maximum configuration of 24 local disks, 60 vCPUs, and 540 GiB memory.
Table 2 Specifications of a Single SAS HDD Disk Attached to a D2 ECS Metric
General-Purpose ECSs
-Overview
General-purpose ECSs provide a balance of compute, memory, and networking resources and a baseline level of vCPU performance with the ability to burst above the baseline. These ECSs are suitable for applications with general workloads, such as web servers, enterprise R&D, and small-scale databases.
+S7n ECSs use the 3rd generation Intel® Xeon® Scalable processors and 25GE high-speed intelligent NICs to provide high network bandwidth and packets per second (PPS) at the lowest possible price.
S3 ECSs are suitable for applications that require moderate performance generally but occasionally burstable high performance, such as light-workload web servers, enterprise R&D and testing environments, and low- and medium-performance databases.
S2 ECSs use Intel® Xeon® Scalable processors, which significantly improve the comprehensive performance. They provide a balance of compute, memory, and networking resources and a baseline level of vCPU performance with the ability to burst above the baseline. These ECSs are suitable for many applications.
Scenarios
- Applications
General-purpose ECSs are suitable for applications that have no special requirements on vCPUs, memory, disk capacities, or bandwidth, but have high requirements on security and reliability. The initial investment and maintenance costs are low.
- - Application scenarios
Enterprise website deployment, enterprise office environment setup, enterprise R&D and testing activities, web servers, R&D and testing environments, and small-scale databases
+Scenarios
- Applications
General-purpose ECSs are suitable for applications that have no special requirements on CPU performance, memory, disk capacity, or bandwidth, but have high requirements on security and reliability. Example applications include web servers, R&D and testing environments, and small-scale databases. They feature low initial investment and maintenance costs.
+ - Application scenarios
Enterprise website deployment, enterprise office environment setup, and enterprise R&D and testing activities
Specifications
-Table 1 S3 ECS specifications Flavor
++ +
+Table 1 S7n ECS specifications Flavor
+vCPUs
+Memory
+(GiB)
+Max./Assured Bandwidth
+(Gbit/s)
+Max. PPS
+(10,000)
+Max. NIC Queues
+Max. NICs
+Max. Supplementary NICs
+Virtualization
+s7n.small.1
+1
+1
+0.8/0.1
+10
+1
+2
+4
+KVM
+s7n.medium.2
+1
+2
+0.8/0.1
+10
+1
+2
+4
+KVM
+s7n.large.2
+2
+4
+1.5/0.2
+15
+1
+2
+8
+KVM
+s7n.xlarge.2
+4
+8
+2/0.35
+25
+1
+2
+16
+KVM
+s7n.2xlarge.2
+8
+16
+3/0.75
+50
+2
+2
+32
+KVM
+s7n.medium.4
+1
+4
+0.8/0.1
+10
+1
+2
+4
+KVM
+s7n.large.4
+2
+8
+1.5/0.2
+15
+1
+2
+8
+KVM
+s7n.xlarge.4
+4
+16
+2/0.35
+25
+1
+2
+16
+KVM
+s7n.2xlarge.4
+8
+32
+3/0.75
+50
+2
+2
+32
+KVM
+-Table 2 S3 ECS specifications Flavor
vCPUs
Table 2 S2 ECS specifications Flavor
+-Table 3 S2 ECS specifications Flavor
vCPUs
Notes
Table 3 lists the OSs supported by general-purpose ECSs.
+Notes
Table 4 lists the OSs supported by general-purpose ECSs.
-Table 3 Supported OS versions OS
+Table 4 Supported OS versions OS
Version
Memory-optimized ECSs
-Overview
- M4 ECSs use the second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable computing performance. Using 25GE high-speed intelligent NICs, M4 ECSs provide a maximum memory size of 512 GiB based on DDR4 for memory-intensive applications with high requirements on network bandwidth and Packets Per Second (PPS).
- M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in the memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing mechanism to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive computing applications.
- M2 ECSs use Intel Xeon E5-2690 v4 CPUs and are designed for memory-optimized applications.
Overview
- M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced computing, security, and stability. Each M7n ECS can have a maximum number of 96 vCPUs and a memory speed of 3,200 MHz, and provide a secure and trusted cloud environment for memory-intensive computing applications.
- M4 ECSs use the second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable computing performance. Using 25GE high-speed intelligent NICs, M4 ECSs provide a maximum memory size of 512 GiB based on DDR4 for memory-intensive applications with high requirements on network bandwidth and Packets Per Second (PPS).
- M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in the memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing mechanism to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive computing applications.
- M2 ECSs use Intel Xeon E5-2690 v4 CPUs and are designed for memory-optimized applications.
Specifications
-Table 1 M4 ECS specifications Flavor
++ +
+Table 1 M7n ECS specifications Flavor
+vCPUs
+Memory
+(GiB)
+Max./Assured Bandwidth
+(Gbit/s)
+Max. PPS
+(10,000)
+Max. NIC Queues
+Max. NICs
+Virtualization
+m7n.large.8
+2
+16
+4/0.8
+40
+2
+2
+KVM
+m7n.xlarge.8
+4
+32
+8/1.6
+80
+2
+3
+KVM
+m7n.2xlarge.8
+8
+64
+15/3
+150
+4
+4
+KVM
+m7n.3xlarge.8
+12
+96
+17/5
+200
+4
+6
+KVM
+m7n.4xlarge.8
+16
+128
+20/6
+280
+8
+8
+KVM
+m7n.6xlarge.8
+24
+192
+25/9
+400
+8
+8
+KVM
+m7n.8xlarge.8
+32
+256
+30/12
+550
+16
+8
+KVM
+m7n.12xlarge.8
+48
+384
+35/18
+750
+16
+8
+KVM
+m7n.16xlarge.8
+64
+512
+36/24
+800
+28
+8
+KVM
+m7n.24xlarge.8
+96
+768
+40/36
+850
+32
+8
+KVM
+-Table 2 M4 ECS specifications Flavor
vCPUs
Table 2 M3 ECS specifications Flavor
+-Table 3 M3 ECS specifications Flavor
vCPUs
Table 3 M2 ECS specifications Flavor
+Table 4 M2 ECS specifications Flavor
vCPUs
-Scenarios
- High-performance relational (MySQL) and NoSQL (MongoDB and Cassandra) databases
- Distributed web scale cache stores that provide in-memory caching of key-value type data (Memcached and Redis)
- Applications processing big unstructured data in real time (financial services, Hadoop/Spark clusters)
- High-performance computing (HPC) and electronic design automation (EDA)
Notes
Table 4 lists the OSs supported by memory-optimized ECSs.
+Notes
Table 5 lists the OSs supported by memory-optimized ECSs.
-Table 4 Supported OS versions OS
+-Table 5 Supported OS versions OS
Version
Password
- 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.)
- 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.)
- Cannot start with a slash (/) for Windows ECSs.
YNbUwp!dUc9MClnv
NOTE:diff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html index 1834a19cc..18239966c 100644 --- a/docs/ecs/umn/en-us_topic_0041169567.html +++ b/docs/ecs/umn/en-us_topic_0041169567.html @@ -8,12 +8,24 @@The example password is generated randomly. Do not use it.
diff --git a/docs/ecs/umn/en-us_topic_0037633087.html b/docs/ecs/umn/en-us_topic_0037633087.html index a280ccb7a..26b0753a8 100644 --- a/docs/ecs/umn/en-us_topic_0037633087.html +++ b/docs/ecs/umn/en-us_topic_0037633087.html @@ -11,8 +11,8 @@For example, in "Administrator:500:C8825DB10F2590EAAAD3B435B51404EE:683020925C5D8569C23AA724774CE9CC:::",
- 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 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 ecs01
2023-12-18
+2024-01-30
+Added the following content:
+ +2023-12-18
Modified the following content:
- Added G7v ECSs in GPU-accelerated ECSs.
2023-12-15
+Modified the following content:
+- Added S7n ECSs in General-Purpose ECSs.
- Added C7n ECSs in Dedicated General-Purpose ECSs.
- Added M7n ECSs in Memory-optimized ECSs.
2023-10-31
Modified the following content:
@@ -607,7 +619,7 @@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?
Modified the following content:
-- Added information for remotely logging in to ECSs in Login Using VNC, Login Using an SSH Key, Login Using an SSH Password, and Login Using MSTSC.
- Added document links to the default keyboard types of the ECSs created using public images in Login Using VNC.
- Added notes on keyboard language settings for VNC-based ECS logins and the mapping between four types of keyboards in Login Using VNC. Provided configuration examples and links to related FAQs.
- Added information for remotely logging in to ECSs in Remotely Logging In to a Windows ECS (Using VNC), Remotely Logging In to a Linux ECS (Using an SSH Key Pair), Remotely Logging In to a Linux ECS (Using an SSH Password), and Remotely Logging In to a Windows ECS (Using MSTSC).
- Added document links to the default keyboard types of the ECSs created using public images in Remotely 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 Remotely Logging In to a Windows ECS (Using VNC). Provided configuration examples and links to related FAQs.
2016-09-30
@@ -629,13 +641,13 @@Added the following content:
Modified the following content:
-- Modified the instructions to configure keyboard languages in VNC logins in Login Using VNC.
- Modified the instructions to configure keyboard languages in VNC logins in Remotely Logging In to a Windows ECS (Using VNC).
2016-09-26
Modified the following content:
-- Added the instructions to configure keyboard languages in VNC logins in Login Using VNC.
- Added the instructions to configure keyboard languages in VNC logins in Remotely Logging In to a Windows ECS (Using VNC).
2016-09-23
diff --git a/docs/ecs/umn/en-us_topic_0048642616.html b/docs/ecs/umn/en-us_topic_0048642616.html index f70b74c7f..94191fb03 100644 --- a/docs/ecs/umn/en-us_topic_0048642616.html +++ b/docs/ecs/umn/en-us_topic_0048642616.html @@ -12,7 +12,7 @@-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 Passing User Data to ECSs.
- 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 to which the ECS belongs.
- 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
Enabling NIC Multi-Queue
-Scenarios
Single-core CPU performance cannot meet the requirement of processing NIC interruptions incurred with the increase of network I/O bandwidth. NIC multi-queue enables multiple CPUs to process ECS NIC interruptions, thereby improving PPS and I/O performance.
+Scenarios
Single-core CPU performance cannot meet the requirement of processing NIC interruptions incurred with the increase of network I/O bandwidth. NIC multi-queue enables multiple CPUs to process ECS NIC interruptions, thereby improving packets per second (PPS) and I/O performance.
The ECS described in this section is assumed to comply with the requirements on specifications and virtualization type.
- If the ECS was created using a public image listed in Support of NIC Multi-Queue, NIC multi-queue has been enabled on the ECS by default. Therefore, you do not need to perform the operations described in this section.
- If the ECS was created using a private image and the OS of the external image file is listed in Support of NIC Multi-Queue, perform the following operations to enable NIC multi-queue: @@ -146,7 +146,7 @@
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:
diff --git a/docs/ecs/umn/en-us_topic_0085634796.html b/docs/ecs/umn/en-us_topic_0085634796.html index ff54b2565..71449d174 100644 --- a/docs/ecs/umn/en-us_topic_0085634796.html +++ b/docs/ecs/umn/en-us_topic_0085634796.html @@ -15,7 +15,7 @@- Disks are displayed in the right pane. In the Disk 1 area, right-click Offline and choose Online from the shortcut menu to online the disk.
Figure 2 Online the disk-
If the disk is offline, you need to online the disk before initializing it.
+ If the disk is offline, you need to bring it online before initializing it.
- After making the disk online, the disk status changes from Offline to Not Initialized. Right-click the disk status and choose Initialize Disk from the shortcut menu, as shown in Figure 3.
- In the Initialize Disk dialog box, select the target disk, click MBR (Master Boot Record) or GPT (GUID Partition Table), and click OK, as shown in Figure 4. @@ -26,10 +26,10 @@
- Right-click at the unallocated space and choose New Simple Volume from the shortcut menu, as shown in Figure 5.
- On the displayed New Simple Volume Wizard window, click Next.
Figure 6 New Simple Volume Wizard
- Specify the volume size and click Next. The default value is the maximum size.
Figure 7 Specify Volume Size-
- Assign the driver letter and click Next.
Figure 8 Assign Driver Letter or Path+
- Assign the drive letter and click Next.
Figure 8 Assign Drive Letter or Path- On the displayed Format Partition page, click Format this volume with the following settings, set parameters based on the requirements, and select Perform a quick format. Then, click Next.
Figure 9 Format Partition
Figure 10 Completing the partition creation-
The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.
+ The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.
- Click Finish. Wait for the initialization to complete. When the volume status changes to Healthy, the initialization has finished successfully, as shown in Figure 11.
diff --git a/docs/ecs/umn/en-us_topic_0085634797.html b/docs/ecs/umn/en-us_topic_0085634797.html index 216126e46..d53571900 100644 --- a/docs/ecs/umn/en-us_topic_0085634797.html +++ b/docs/ecs/umn/en-us_topic_0085634797.html @@ -52,7 +52,7 @@ Partition type: e extendedThere are two types of disk partitions:- Choosing p creates a primary partition.
- Choosing e creates an extended partition.
diff --git a/docs/ecs/umn/en-us_topic_0091224748.html b/docs/ecs/umn/en-us_topic_0091224748.html index 303544088..01f443b15 100644 --- a/docs/ecs/umn/en-us_topic_0091224748.html +++ b/docs/ecs/umn/en-us_topic_0091224748.html @@ -1,19 +1,427 @@If the MBR partition style is used, a maximum of 4 primary partitions, or 3 primary partitions and 1 extended partition can be created. The extended partition cannot be used directly and must be divided into logical partitions before use.
+ If MBR is used, a maximum of 4 primary partitions, or 3 primary partitions plus 1 extended partition can be created. The extended partition must be divided into logical partitions before use.
Disk partitions created using GPT are not categorized.
Dedicated General-Purpose ECSs
-Overview
+-Overview
C7n ECSs use the third-generation Intel Xeon scalable processors to provide enhanced computing, security, and stability. Each C7n ECS can have a maximum number of 96 vCPUs and a memory speed of 3200 MHz, supports secure boot, and provides a secure, trusted cloud environment.
C7t ECSs support encryption using Intel® SGX to protect the confidentiality and integrity of key code and data from being damaged by malware. Based on the TPM/TCM chip, the boot chain from the underlying server hardware to the guest OS can be measured and verified to implement trusted boot.
-C4 ECSs use second-generation Intel® Xeon® Scalable processors to provide powerful and stable computing performance. By using 25GE high-speed intelligent NICs, C4 ECSs offer ultra-high network bandwidth and PPS.
+C4 ECSs use second-generation Intel® Xeon® Scalable processors to provide powerful and stable computing performance. By using 25GE high-speed intelligent NICs, C4 ECSs offer ultra-high network bandwidth and packets per second (PPS).
C3 ECSs use Intel® Xeon® Scalable processors, KVM virtualization, Data Plane Development Kit (DPDK) rapid packet processing mechanism, and high-performance NICs to deliver high and stable computing performance for enterprise-grade applications.
Scenarios
Scenarios
- C7n ECSs are suitable for:
- Medium- and heavy-load enterprise applications with strict requirements on computing and network performance, such as web applications, e-commerce platforms, short video platforms, online games, and insurance and finance.
- C7t ECSs are suitable for:
- Scenarios involving sensitive information such as personal identity information and healthcare, financial, and intellectual property data
- Confidential data sharing in multi-party computation
- Blockchain
- Confidential machine learning
- Scenarios with high security and trustworthy requirements, such as finance, government, and enterprises
- Enterprise-class applications of various types and scales
- C4 ECSs are suitable for:
- Websites and web applications that require high computing and network performance
- General databases
- Cache servers
- Medium- and heavy-load enterprise applications
- C3 ECSs are suitable for:
- Small- and medium-sized databases, cache clusters, and search clusters with high requirements on stability
- Enterprise-class applications of various types and scales
Specifications
-Table 1 C7t ECS specifications Flavor
++ +
+Table 1 C7n ECS specifications Flavor
+vCPUs
+Memory
+(GiB)
+Max./Assured Bandwidth
+(Gbit/s)
+Max. PPS
+(10,000)
+Max. NIC Queues
+Max. NICs
+Max. Supplementary NICs
+Virtualization
+c7n.large.2
+2
+4
+4/0.8
+40
+2
+2
+16
+KVM
+c7n.xlarge.2
+4
+8
+8/1.6
+80
+2
+3
+32
+KVM
+c7n.2xlarge.2
+8
+16
+15/3
+150
+4
+4
+64
+KVM
+c7n.3xlarge.2
+12
+24
+17/5
+200
+4
+6
+96
+KVM
+c7n.4xlarge.2
+16
+32
+20/6
+280
+8
+8
+128
+KVM
+c7n.6xlarge.2
+24
+48
+25/9
+400
+8
+8
+192
+KVM
+c7n.8xlarge.2
+32
+64
+30/12
+550
+16
+8
+256
+KVM
+c7n.12xlarge.2
+48
+96
+35/18
+750
+16
+8
+256
+KVM
+c7n.16xlarge.2
+64
+128
+36/24
+800
+28
+8
+256
+KVM
+c7n.24xlarge.2
+96
+192
+40/36
+850
+32
+8
+256
+KVM
+c7n.large.4
+2
+8
+4/0.8
+40
+2
+2
+16
+KVM
+c7n.xlarge.4
+4
+16
+8/1.6
+80
+2
+3
+32
+KVM
+c7n.2xlarge.4
+8
+32
+15/3
+150
+4
+4
+64
+KVM
+c7n.3xlarge.4
+12
+48
+17/5
+200
+4
+6
+96
+KVM
+c7n.4xlarge.4
+16
+64
+20/6
+280
+8
+8
+128
+KVM
+c7n.6xlarge.4
+24
+96
+25/9
+400
+8
+8
+192
+KVM
+c7n.8xlarge.4
+32
+128
+30/12
+550
+16
+8
+256
+KVM
+c7n.12xlarge.4
+48
+192
+35/18
+750
+16
+8
+256
+KVM
+c7n.16xlarge.4
+64
+256
+36/24
+800
+28
+8
+256
+KVM
+c7n.24xlarge.4
+96
+384
+40/36
+850
+32
+8
+256
+KVM
+-Table 2 C7t ECS specifications Flavor
vCPUs
Table 2 C4 ECS specifications Flavor
+-Table 3 C4 ECS specifications Flavor
vCPUs
Table 3 C3 ECS specifications Flavor
+-Table 4 C3 ECS specifications Flavor
vCPUs
Notes
Table 4 lists the OSs supported by dedicated general-purpose ECSs.
+Notes
Table 5 lists the OSs supported by dedicated general-purpose ECSs.
-Table 4 Supported OS versions OS
+Table 5 Supported OS versions OS
Version
Figure 1 Windows ECS login modes
- Obtain the password.
Use the password obtaining function provided by the management console to decrypt the key file to obtain a password.
For details, see Obtaining the Password for Logging In to a Windows ECS.
- - Select a login method and log in to the ECS.
- Management console (VNC)
For details, see Login Using VNC.
- - Remote desktop connection (MSTSC)
For details, see Login Using MSTSC.
+ - Select a login method and log in to the ECS.
- Management console (VNC)
For details, see Remotely Logging In to a Windows ECS (Using VNC).
+ - Remote desktop connection (MSTSC)
For details, see Remotely Logging In to a Windows ECS (Using MSTSC).
- Management console (VNC)
- Management console (VNC)
diff --git a/docs/ecs/umn/en-us_topic_0092494943.html b/docs/ecs/umn/en-us_topic_0092494943.html index 352f3345a..ee68406bd 100644 --- a/docs/ecs/umn/en-us_topic_0092494943.html +++ b/docs/ecs/umn/en-us_topic_0092494943.html @@ -22,7 +22,7 @@Logging In to a Linux ECS
You can log in to a Linux ECS using either VNC or SSH key provided on the management console.
Figure 2 Linux ECS login modes-
- Select a login method and log in to the ECS.
- VNC
For details, see Login Using VNC.
+- Select a login method and log in to the ECS.
- VNC
For details, see Remotely Logging In to a Linux ECS (Using VNC).
- SSH key
When you log in to the ECS using the SSH key, bind an EIP to the ECS.
-For details, see Login Using an SSH Key.
+For details, see Remotely Logging In to a Linux ECS (Using an SSH Key Pair).
- VNC
- Select a login method and log in to the ECS.
- VNC
Use MSTSC.
Click Start on the local computer. In the Search programs and files text box, enter mstsc to open the Remote Desktop Connection dialog box.
-For details, see Login Using MSTSC.
+For details, see Remotely Logging In to a Windows ECS (Using MSTSC).
The target ECS has had an EIP bound.
Linux
Install a remote connection tool, for example, rdesktop.
-For details, see Logging In to a Windows ECS from a Linux Computer.
+For details, see Remotely Logging In to a Windows ECS (from a Linux Computer).
Windows
Through the management console.
-For details, see Login Using VNC.
+For details, see Remotely Logging In to a Windows ECS (Using VNC).
No EIP is required.
+No EIP is required.
diff --git a/docs/ecs/umn/en-us_topic_0093263550.html b/docs/ecs/umn/en-us_topic_0093263550.html index 5783b0d60..d5b472179 100644 --- a/docs/ecs/umn/en-us_topic_0093263550.html +++ b/docs/ecs/umn/en-us_topic_0093263550.html @@ -1,6 +1,6 @@ -Basics of Tags
Tags are used to identify cloud resources. When you have many cloud resources of the same type, you can use tags to classify cloud resources by dimension (for example, use, owner, or environment).
- +Figure 1 shows how tags work. In this example, you assign two tags to each cloud resource. Each tag contains a key and a value that you define. The key of one tag is Owner, and the key of another tag is Usage. Each tag has a value.
You can quickly search for and filter specific cloud resources based on the tags added to them. For example, you can define a set of tags for cloud resources in an account to track the owner and usage of each cloud resource, making resource management easier.
Login Using VNC
+Remotely Logging In to a Linux ECS (Using VNC)
Scenarios
This section describes how to use VNC provided on the management console to log in to an ECS. This function applies to emergency O&M. In other scenarios, you are advised to log in to ECSs using SSH or MSTSC.
For instructions about how to copy and paste data on VNC pages after the ECS login, see Follow-up Procedure.
-Before using remote login (VNC) provided on the management console to log in to a Linux ECS authenticated using a key pair, log in to the ECS using an SSH key and set a login password.
@@ -187,9 +187,9 @@- (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+
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
- (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.
Managing Virtual IP Addresses
-Scenarios
A virtual IP address provides the second IP address for one or more ECS NICs, improving high availability between the ECSs.
++ + \ No newline at end of file diff --git a/docs/ecs/umn/en-us_topic_0096293655.html b/docs/ecs/umn/en-us_topic_0096293655.html index f0e1d8b6f..656a02a99 100644 --- a/docs/ecs/umn/en-us_topic_0096293655.html +++ b/docs/ecs/umn/en-us_topic_0096293655.html @@ -9,7 +9,7 @@+Configuring a Virtual IP Address for an ECS
Manually configure the virtual IP address bound to an ECS.
+The following OSs are used as examples here. For other OSs, see the help documents on their official websites.+- Linux: CentOS 7.2 64bit and Ubuntu 22.04 server 64bit
- Windows: Windows Server
Linux (CentOS 7.2 64bit is used as an example.)+- Obtain the NIC that the virtual IP address is to be bound and the connection of the NIC:
+
Information similar to the following is displayed:
+
+
The command output in this example is described as follows:
+- eth0 in the DEVICE column indicates the NIC that the virtual IP address is to be bound.
- Wired connection 1 in the NAME column indicates the connection of the NIC.
- Add the virtual IP address for the connection:
nmcli connection modify "Connection name of the NIC" +ipv4.addresses Virtual IP address
+Configure the parameters as follows:
+- Connection name of the NIC: The connection name of the NIC obtained in 1. In this example, the connection name is Wired connection 1.
- Virtual IP address: Enter the virtual IP address to be added. If you add multiple virtual IP addresses at a time, separate every two with a comma (,).
Example commands:+- Adding a single virtual IP address: nmcli connection modify "Wired connection 1" +ipv4.addresses 172.16.0.125
- Adding multiple virtual IP addresses: nmcli connection modify "Wired connection 1" +ipv4.addresses 172.16.0.125,172.16.0.126
- Make the configuration in 2 take effect:
nmcli connection up "Connection name of the NIC"
+In this example, run the following command:
+nmcli connection up "Wired connection 1"
+Information similar to the following is displayed:
+
+
- Check whether the virtual IP address has been bound:
+
Information similar to the following is displayed. In the command output, the virtual IP address 172.16.0.125 is bound to NIC eth0.
+
+
+ To delete an added virtual IP address, perform the following steps:
+- Delete the virtual IP address from the connection of the NIC:
nmcli connection modify "Connection name of the NIC" -ipv4.addresses Virtual IP address
+To delete multiple virtual IP addresses at a time, separate every two with a comma (,). Example commands are as follows:+- Deleting a single virtual IP address: nmcli connection modify "Wired connection 1" -ipv4.addresses 172.16.0.125
- Deleting multiple virtual IP addresses: nmcli connection modify "Wired connection 1" -ipv4.addresses 172.16.0.125,172.16.0.126
- Make the deletion take effect by referring to 3.
- Delete the virtual IP address from the connection of the NIC:
Linux (Ubuntu 22.04 server 64bit is used as an example.)
+If an ECS runs Ubuntu 22 or Ubuntu 20, perform the following operations:+- Obtain the NIC that the virtual IP address is to be bound:
+Information similar to the following is displayed. In this example, the NIC bound to the virtual IP address is eth0.+
root@ecs-X-ubantu:~# ifconfig +eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 + inet 172.16.0.210 netmask 255.255.255.0 broadcast 172.16.0.255 + inet6 fe80::f816:3eff:fe01:f1c3 prefixlen 64 scopeid 0x20<link> + ether fa:16:3e:01:f1:c3 txqueuelen 1000 (Ethernet) + RX packets 43915 bytes 63606486 (63.6 MB) + RX errors 0 dropped 0 overruns 0 frame 0 + TX packets 3364 bytes 455617 (455.6 KB) + TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 +...
+ - Switch to the /etc/netplan directory:
cd /etc/netplan
+ - Add a virtual IP address to the NIC.
- Open the configuration file 01-netcfg.yaml:
vim 01-netcfg.yaml
+ - Press i to enter the editing mode.
- In the NIC configuration area, add a virtual IP address.
In this example, add a virtual IP address for eth0:
+addresses:
+- 172.16.0.26/32
+The file content is as follows:+network: + version: 2 + renderer: NetworkManager + ethernets: + eth0: + dhcp4: true + addresses: + - 172.16.0.26/32 + eth1: + dhcp4: true + eth2: + dhcp4: true + eth3: + dhcp4: true + eth4: + dhcp4: true
+ - Press Esc, enter :wq!, save the configuration, and exit.
- Open the configuration file 01-netcfg.yaml:
- Make the configuration in 3 take effect:
netplan apply
+ - Check whether the virtual IP address has been bound:
+Information similar to the following is displayed. In the command output, the virtual IP address 172.16.0.26 is bound to NIC eth0.+ +
root@ecs-X-ubantu:/etc/netplan# ip a +... +2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 + link/ether fa:16:3e:01:f1:c3 brd ff:ff:ff:ff:ff:ff + altname enp0s3 + altname ens3 + inet 172.16.0.26/32 scope global noprefixroute eth0 + valid_lft forever preferred_lft forever + inet 172.16.0.210/24 brd 172.16.0.255 scope global dynamic noprefixroute eth0 + valid_lft 107999971sec preferred_lft 107999971sec + inet6 fe80::f816:3eff:fe01:f1c3/64 scope link + valid_lft forever preferred_lft forever
+
Windows OS (Windows Server is used as an example here.)
+- In Control Panel, click Network and Sharing Center, and click the corresponding local connection.
- On the displayed page, click Properties.
- On the Network tab page, select Internet Protocol Version 4 (TCP/IPv4).
- Click Properties.
- Select Use the following IP address and set IP address to the private IP address of the ECS, for example, 10.0.0.101.Figure 1 Configuring private IP address+
- Click Advanced.
- On the IP Settings tab, click Add in the IP addresses area.
Add the virtual IP address, for example, 10.0.0.154.
+Figure 2 Configuring virtual IP address+
- Click OK.
- In the Start menu, open the Windows command line window and run the following command to check whether the virtual IP address has been configured:
ipconfig /all
+In the command output, IPv4 Address is the virtual IP address 10.0.0.154, indicating that the virtual IP address of the ECS NIC has been correctly configured.
+ +
Scenarios
A virtual IP address provides the second IP address for one or more ECS NICs, improving high availability between the ECSs.
One NIC can be bound with up to 10 virtual IP addresses, and one virtual IP address can be bound to up to 10 NICs. Multiple ECSs deployed to work in active/standby mode can be bound with the same virtual IP address for disaster recovery.
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.
- On the Elastic Cloud Server page, click the name of the target ECS.
The page providing details about the ECS is displayed.
@@ -16,3 +110,10 @@
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 restrictions on attaching a disk, 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 restrictions on attaching a disk, 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.
diff --git a/docs/ecs/umn/en-us_topic_0097289624.html b/docs/ecs/umn/en-us_topic_0097289624.html index 917dbf293..a11e12be8 100644 --- a/docs/ecs/umn/en-us_topic_0097289624.html +++ b/docs/ecs/umn/en-us_topic_0097289624.html @@ -12,184 +12,262 @@
Images Supported by GPU-accelerated ECSs
++
+Table 1 Images supported by GPU-accelerated ECSs Category
+ECS Type
+Supported Image
+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
+- 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
+G6
+- EulerOS 2.5 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
Computing-accelerated
+P3
+- CentOS 8.2 64bit
- CentOS 8.1 64bit
- CentOS 8.0 64bit
- CentOS 7.9 64bit
- CentOS 7.8 64bit
- CentOS 7.7 64bit
- CentOS 7.6 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Computing-accelerated
+P2s
+- CentOS 7.9 64bit
- EulerOS 2.5 64bit
- Oracle Linux Server release 7.6 64bit
- Ubuntu 20.04 Server 64bit
- Ubuntu 18.04 Server 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
Computing-accelerated
+P2v
+- CentOS 7.9 64bit
- EulerOS 2.5 64bit
- Oracle Linux Server release 7.6 64bit
- Ubuntu 20.04 Server 64bit
- Ubuntu 18.04 Server 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
Computing-accelerated
+P2
+- CentOS 7.9 64bit
- EulerOS 2.5 64bit
- Oracle Linux Server release 7.6 64bit
- Ubuntu 20.04 Server 64bit
- Ubuntu 18.04 Server 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
Computing-accelerated
+P1
+- CentOS 7.9 64bit
- Ubuntu 20.04 Server 64bit
- Ubuntu 18.04 Server 64bit
- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
- Oracle Linux Server release 7.6 64bit
Inference-accelerated
+Pi2
+- CentOS 7.9 64bit
- Oracle Linux Server release 7.6 64bit
- Ubuntu 20.04 Server 64bit
- Ubuntu 18.04 Server 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
Graphics-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, G7v ECSs can provide 37.4 TFLOPS of FP32 peak performance and 74.8 TFLOPS (sparsity disabled) or 149.6 TFLOPS (sparsity enabled) of TF32 peak tensor performance. 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 1 G7v ECS specifications Flavor
+Table 2 G7v 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
g7v.2xlarge.8
+g7v.2xlarge.8
8
+8
64
+64
15/3
+15/3
100
+100
4
+4
4
+4
1 × NVIDIA-A40-8Q
+1 × NVIDIA-A40-8Q
8
+8
KVM
+KVM
g7v.4xlarge.8
+g7v.4xlarge.8
16
+16
128
+128
20/6
+20/6
150
+150
8
+8
8
+8
1 × NVIDIA-A40-16Q
+1 × NVIDIA-A40-16Q
16
+16
KVM
+KVM
g7v.6xlarge.8
+g7v.6xlarge.8
24
+24
192
+192
25/9
+25/9
200
+200
8
+8
8
+8
1 × NVIDIA-A40-24Q
+1 × NVIDIA-A40-24Q
24
+24
KVM
+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
- 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
-- G7v ECSs support the following OSs:
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- CentOS 8.2 64bit
- CentOS 7.6 64bit
- Ubuntu Server 20.04 64bit
- Ubuntu Server 18.04 64bit
- 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.
- 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.
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.
- 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.
- 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.
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, G7 ECSs provide 37.4 TFLOPS of FP32 peak performance and 74.8 TFLOPS (sparsity disabled) or 149.6 TFLOPS (sparsity enabled) of TF32 peak tensor performance. 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
G7 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 G7 ECSs. G7 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
-- G7 ECSs support the following OSs:
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- CentOS 8.2 64bit
- CentOS 7.6 64bit
- Ubuntu Server 20.04 64bit
- Ubuntu Server 18.04 64bit
- G7 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.
- If a G7 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.
- After a G7 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 G7 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.
+ - G7 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.
- If a G7 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.
- 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.
Graphics-accelerated Enhancement G6
Overview
G6 ECSs use NVIDIA Tesla T4 GPUs to support DirectX, OpenGL, and Vulkan and provide 16 GiB of GPU memory. The theoretical Pixel rate is 101.8 Gpixel/s and Texture rate 254.4 GTexel/s, meeting professional graphics processing requirements.
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
G6 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 G6 ECSs. G6 ECSs support the following commonly used graphics processing software:
- AutoCAD
- 3DS MAX
- MAYA
- Agisoft PhotoScan
- ContextCapture
Notes
-- Table 4 lists the OSs supported by G6 ECSs.
-+
-Table 4 Supported OS versions OS
-Version
-EulerOS
-EulerOS 2.5 64bit
-Windows
-- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- After a G6 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 G6 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.
+ - G6 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.
- If a G6 ECS is created using a private image, make sure that the GRID driver was installed during the private image creation. If not, install the driver for graphics acceleration after the ECS is created. -
- 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.
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, P3 ECSs provide 19.5 TFLOPS of FP32 single-precision performance and 156 TFLOPS (sparsity disabled) or 312 TFLOPS (sparsity enabled) of TF32 peak tensor performance.
Specifications
-Table 5 P3 ECS specifications Flavor
+Table 5 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 Caffee
- CUDA GPU rendering supported by RedShift for Autodesk 3dsMax and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
- More than 2,000 GPU-accelerated applications such as Amber, NAMD, and VASP
Notes
-- P3 ECSs support the following OSs:
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- CentOS 8.2 64bit
- CentOS 8.1 64bit
- CentOS 8.0 64bit
- CentOS 7.9 64bit
- CentOS 7.8 64bit
- CentOS 7.7 64bit
- CentOS 7.6 64bit
- If a P3 ECS is created using a private image, make sure that the Tesla driver has been installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated 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 Installing a Tesla Driver and CUDA Toolkit 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.
Computing-accelerated P2s
Overview
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 6 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 3dsMax and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
Notes- Table 7 lists the OSs supported by P2s ECSs. -
- Applications
Reinstalling the OS
-Scenarios
If the OS of an ECS fails to start or requires optimization, reinstall the OS.
Notes
- 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.
- Routine data backup
