- A snapshot can be rolled back only to its source disk. Rollback to another disk is not possible.
- If you have reinstalled or changed the ECS OS, snapshots of the system disk are automatically deleted. Snapshots of the data disks can be used as usual.
- A snapshot can only be rolled back to its source disk. Rolling back to another disk is not supported.
- If you have reinstalled or changed the ECS OS, snapshots of the system disk are automatically deleted. Snapshots of the data disks can be used as usual.
- The snapshot data is stored with the disk data to facilitate rapid data back up and restoration.
- You can create snapshots to rapidly save disk data as it was at specified points in time. You can also use snapshots to create new disks so that the created disks will contain the snapshot data in the beginning.
Backing Up an ECS
-Scenarios
CBR enhances data integrity and service continuity. For example, if an ECS or EVS disk is faulty or a misoperation causes data loss, you can use data backups to quickly restore data. This section describes how to back up ECSs and EVS disks.
-For more information, CBR Architecture, Backup Mechanism, and Backup Options.
+Scenarios
Cloud Backup and Recovery (CBR) enhances data integrity and service continuity. For example, if an ECS or EVS disk is faulty or a misoperation causes data loss, you can use data backups to quickly restore data. This section describes how to back up ECSs and EVS disks.
+For more information, see CBR Architecture, Backup Mechanism, and Backup Options.
- 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.
tasksel install desktop gnome-desktop
The installation takes a long time. Please wait.
After GUI desktop component is installed on the ECS, you cannot log in to the Debian OS as user root user. Therefore, you need to add a member account for logging in to the GUI desktop.
+After the GUI desktop component is installed on the ECS, you cannot log in to the Debian OS as user root user. Therefore, you need to add a member account for logging in to the GUI desktop.
Run the following command to add user user01:
adduser user01
Set a password for user01 as prompted.
@@ -38,7 +38,7 @@ Is the information correct? [Y/n] YQuota Adjustment
-What Is Quota?
Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.
+What Is Quota?
Quotas can limit the number or amount of resources available to users, such as the maximum number of ECS or EVS disks that can be created.
If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.
How Do I View My Quotas?
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - In the upper right corner of the page, click
.The Service Quota page is displayed.
+diff --git a/docs/ecs/umn/en-us_topic_0000001234175322.html b/docs/ecs/umn/en-us_topic_0000001234175322.html index 7dae2776..e4cd4aa3 100644 --- a/docs/ecs/umn/en-us_topic_0000001234175322.html +++ b/docs/ecs/umn/en-us_topic_0000001234175322.html @@ -1,18 +1,15 @@ - -How Do I View My Quotas?
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- In the upper right corner of the page, click .
The Quotas page is displayed.
- View the used and total quota of each type of resources on the displayed page.
If a quota cannot meet service requirements, apply for a higher quota.
Key Pairs
- -+Key Pairs
+-diff --git a/docs/ecs/umn/en-us_topic_0000001234335274.html b/docs/ecs/umn/en-us_topic_0000001234335274.html index 802f5111..02aaa6fe 100644 --- a/docs/ecs/umn/en-us_topic_0000001234335274.html +++ b/docs/ecs/umn/en-us_topic_0000001234335274.html @@ -1,7 +1,7 @@ -- Application Scenarios for Using Key Pairs
- (Recommended) Creating a Key Pair on the Management Console
- - Creating a Key Pair Using PuTTYgen
+ - Creating a Key Pair Using PuTTY Key Generator
- Importing a Key Pair
@@ -21,7 +18,7 @@
-Parent topic: Passwords and Key Pairs Management+Parent topic: Passwords and Key PairsCreating a Key Pair Using PuTTYgen
-diff --git a/docs/ecs/umn/en-us_topic_0018078507.html b/docs/ecs/umn/en-us_topic_0018078507.html index 455e5e94..0d551eb8 100644 --- a/docs/ecs/umn/en-us_topic_0018078507.html +++ b/docs/ecs/umn/en-us_topic_0018078507.html @@ -5,7 +5,7 @@Scenarios
You can use PuTTYgen to create a key pair and store the public key and private key locally.
+Creating a Key Pair Using PuTTY Key Generator
+@@ -15,7 +15,7 @@Scenarios
You can use puttygen.exe to create a key pair and store both the public key and private key locally.
Key pairs created using puttygen.exe must be imported by referring to Importing a Key Pair before they are used.
- Copy the public key to a .txt file and save it to a local directory.
Do not save the public key by clicking Save public key because this operation will change the format of the public key content and cause the public key to fail to be imported to the management console.
- Save the private key and keep it secure. The private key can be downloaded only once.
The format in which to save your private key file varies depending on application scenarios.
-- When using PuTTY to log in to a Linux ECS:Save the private key file in the .ppk format.
- On the PuTTY Key Generator page, choose File > Save private key.Figure 3 Saving a private key+
- When using PuTTY Key Generator to log in to a Linux ECS:
- When using Xshell to log in to a Linux ECS or obtaining the password for logging in to a Windows ECS:Save the private key file in the .pem format.
- Choose Conversions > Export OpenSSH key.
If you use this private file to obtain the password for logging in to a Windows ECS, do not specify Key passphrase for Export OpenSSH key so that you can obtain the password successfully.
diff --git a/docs/ecs/umn/en-us_topic_0000001278335673.html b/docs/ecs/umn/en-us_topic_0000001278335673.html index efc53f4e..90a04e82 100644 --- a/docs/ecs/umn/en-us_topic_0000001278335673.html +++ b/docs/ecs/umn/en-us_topic_0000001278335673.html @@ -5,7 +5,8 @@A key pair consists of a public key and a private key. Key Pair Service (KPS) stores the public key and you store the private key. If you have imported a public key into a Linux ECS, you can use the corresponding private key to log in to the ECS without a password. You do not need to worry about password interception, cracking, or leakage.
-Scenarios
When purchasing an ECS, you are advised to select the key pair login mode. For Windows ECSs, key pairs are required to decrypt the passwords so that you can use the decrypted password to log in.
-- Logging in to a Linux ECSYou can directly use a key pair to log in.
- When you are creating the ECS, select the key pair login mode. For details, see "Set Login Mode" in Step 3: Configure Advanced Settings.
- After the ECS is created, bind a key pair to the ECS by referring to "Binding a Key Pair" in the Data Encryption Workshop User Guide.
- Logging in to a Linux ECS
You can directly use a key pair to log in a Linux ECS.
+- During the ECS creation, select the key pair login mode. For details, see "Set Login Mode" in Step 3: Configure Advanced Settings.
- After the ECS is created, bind a key pair to the ECS by referring to "Binding a Key Pair" in the Data Encryption Workshop User Guide.
Creating a Key Pair
You can create a key pair or use an existing one for remote login authentication.
-- Creating a key pairYou can create a key pair using either of the following method:
- Follow the instructions in (Recommended) Creating a Key Pair on the Management Console. The public key is automatically stored in the system, and the private key is stored locally.
- Follow the instructions in Creating a Key Pair Using PuTTYgen. Both the public and private keys are stored locally.
After the key pair is created, import the key pair following the instructions provided in Importing a Key Pair so that you can use it.
+- Creating a key pairYou can create a key pair using either of the following methods:
- Follow the instructions in (Recommended) Creating a Key Pair on the Management Console. The public key is automatically stored in the system, and the private key is stored locally.
- Follow the instructions in Creating a Key Pair Using PuTTY Key Generator. Both the public and private keys are stored locally.
After the key pair is created, import the key pair following the instructions provided in Importing a Key Pair so that you can use it.
- Using an existing key pair
If an existing key pair (created using PuTTYgen, for example) is available, you can import the public key by referring to Importing a Key Pair on the management console to let the system maintain your public key.
@@ -22,7 +23,7 @@
- Creating a key pair
diff --git a/docs/ecs/umn/en-us_topic_0000001278734873.html b/docs/ecs/umn/en-us_topic_0000001278734873.html index 81bb0c73..ea72ec44 100644 --- a/docs/ecs/umn/en-us_topic_0000001278734873.html +++ b/docs/ecs/umn/en-us_topic_0000001278734873.html @@ -9,7 +9,7 @@Constraints
- Key pairs can be used to remotely log in to Linux ECSs only.
- SSH-2 key pairs created on the console support only the RSA-2048 cryptographic algorithms.
- Key pairs are only for one user but they can be imported to other users.
- Key pairs can be used only for ECSs in the same region.
- Imported key pairs support the following cryptographic algorithms:
- RSA-1024
- RSA-2048
- RSA-4096
Notes and Constraints
- Key pairs can be used to remotely log in to Linux ECSs only.
- SSH-2 key pairs created on the console support only the RSA-2048 cryptographic algorithms.
- Key pairs are only for one user but they can be imported to other users.
- Key pairs can be used only for ECSs in the same region.
- Imported key pairs support the following cryptographic algorithms:
- RSA-1024
- RSA-2048
- RSA-4096
- Store your private key in a secure place because you need to use it to prove your identity when logging in to your ECS. The private key can be downloaded once only.
Procedure
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose Key Pair.
- On the Key Pair Service page, click Import Key Pair.Figure 1 Import Public Key-
- Use either of the following methods to import the key pair:
- Selecting a file
- In the Import Key Pair dialog box of the management console, click Select File and select the locally stored public key file (for example, the .txt file saved in 3 in Creating a Key Pair Using PuTTYgen).diff --git a/docs/ecs/umn/en-us_topic_0018073218.html b/docs/ecs/umn/en-us_topic_0018073218.html index b36dd4ef..13f79748 100644 --- a/docs/ecs/umn/en-us_topic_0018073218.html +++ b/docs/ecs/umn/en-us_topic_0018073218.html @@ -8,7 +8,7 @@
Make sure that the file to be imported is a public key file.
+- Use either of the following methods to import the key pair:
- Selecting a file
- In the Import Key Pair dialog box of the management console, click Select File and select the locally stored public key file (for example, the .txt file saved in 3 in Creating a Key Pair Using PuTTY Key Generator).
Make sure that the file to be imported is a public key file.
- Click OK.
After the public key is imported, you can change its name.
- In the Import Key Pair dialog box of the management console, click Select File and select the locally stored public key file (for example, the .txt file saved in 3 in Creating a Key Pair Using PuTTY Key Generator).
diff --git a/docs/ecs/umn/en-us_topic_0000001630328828.html b/docs/ecs/umn/en-us_topic_0000001630328828.html index dfa7b961..1c8efc1e 100644 --- a/docs/ecs/umn/en-us_topic_0000001630328828.html +++ b/docs/ecs/umn/en-us_topic_0000001630328828.html @@ -104,7 +104,7 @@-Parent topic: ECS Creation+Parent topic: ECS Creation FAQExample 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.
- 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.
diff --git a/docs/ecs/umn/en-us_topic_0000001987515176.html b/docs/ecs/umn/en-us_topic_0000001987515176.html index a01b9a7f..f1db661d 100644 --- a/docs/ecs/umn/en-us_topic_0000001987515176.html +++ b/docs/ecs/umn/en-us_topic_0000001987515176.html @@ -1,7 +1,7 @@ -Data Backup and Restoration
+Data Backup and Restoration FAQ
diff --git a/docs/ecs/umn/en-us_topic_0013771089.html b/docs/ecs/umn/en-us_topic_0013771089.html index b54f2033..e98d72cc 100644 --- a/docs/ecs/umn/en-us_topic_0013771089.html +++ b/docs/ecs/umn/en-us_topic_0013771089.html @@ -35,7 +35,7 @@Windows
Use the remote login function available on the management console.
- +No EIP is required.
General Operations
+Modifying Individual ECS Specifications
-@@ -8,10 +8,10 @@Scenarios
If ECS specifications do not meet service requirements, you can modify the ECS specifications, including vCPUs and memory. Certain ECSs allow you to change their types when you modify their specifications.
- On the page providing details about the ECS, view the ECS specifications.Figure 1 Viewing ECS specifications
- Check the specifications tables in ECS Types for the virtualization type.
Notes
- Downgrading ECS specifications (vCPU or memory) will reduce performance.
- Certain ECS types do not support specifications modification currently. For details about available ECS types and functions, see ECS Types. For details about restrictions on using different types of ECSs, see their notes.
- When the disk status is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.
- Before modifying the specifications of a Windows ECS, modify the SAN policy by following the instructions provided in Why Does a Disk Attached to a Windows ECS Go Offline? to prevent disks from going offline after the specifications are modified.
- Before modifying specifications, make sure that the ECS has been stopped.
-Notes
- The ECS needs to be stopped during the the specification modification, so you are advised to perform this operation during off-peak hours.
- During the specification modification, do not perform any operation on the ECS, such as stopping or restarting the ECS. Otherwise, the modification will fail.
- Downgrading ECS specifications (vCPU or memory) will reduce performance.
- Certain ECS types do not support specifications modification currently. For details about available ECS types and functions, see ECS Types. For details about restrictions on using different types of ECSs, see their notes.
- When the disk status is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.
- Before modifying the specifications of a Windows ECS, modify the SAN policy by following the instructions provided in Why Does a Disk Attached to a Windows ECS Go Offline? to prevent disks from going offline after the specifications are modified.
- Before modifying specifications, make sure that the ECS has been stopped.
Step 1: Modify Specifications
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, view the status of the target ECS.
If the ECS is not in Stopped state, click More in the Operation column and select Stop.
- - Click More in the Operation column and select Modify Specifications.
The Modify ECS Specifications page is displayed.
+Step 1: Modify Specifications
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, view the status of the target ECS.
If the ECS is not in Stopped state, choose More > Stop in the Operation column.
+ - Choose More > Modify Specifications in the Operation column.
The Modify ECS Specifications page is displayed.
- Select the new ECS type, vCPUs, and memory as prompted.Figure 2 Modifying specifications
- (Optional) Set DeH.
If the ECS is created on a DeH, the system allows you to change the DeH.
To do so, select the target DeH from the drop-down list. If no DeH is available in the drop-down list, remaining DeH resources are insufficient and cannot be used to create the ECS with specifications modified.
@@ -27,14 +27,14 @@
Follow-up Procedure
Perform the following operations in the event of a specifications modification failure:
-- Log in to the management console.
- Under Management & Deployment, choose Cloud Trace Service.
- In the navigation pane on the left, choose Trace List.
- In the Trace Name column, locate the resizeServer event by resource ID.
The resource ID is the ID of the ECS on which the specifications modification failed.
+- Log in to the management console.
- Under Management & Deployment, choose Cloud Trace Service.
- In the navigation pane on the left, choose Trace List.
- In the Trace Name column, locate the resizeServer event by resource ID.
The resource ID is the ID of the ECS on which the specifications modification failed.
- Click View Trace in the Operation column to view the failure cause.
If the fault cannot be rectified based on logs, contact customer service.
diff --git a/docs/ecs/umn/en-us_topic_0013771097.html b/docs/ecs/umn/en-us_topic_0013771097.html index 5ae1a5e6..1f92ea33 100644 --- a/docs/ecs/umn/en-us_topic_0013771097.html +++ b/docs/ecs/umn/en-us_topic_0013771097.html @@ -10,9 +10,9 @@-Parent topic: Modifying ECS Specifications+Parent topic: Modifying ECS Specifications (vCPUs and Memory)- Managing GPU Drivers of GPU-accelerated ECSs
-
- Managing ECSs
+- Managing ECS Configurations
-
- Modifying ECS Specifications
+- Modifying ECS Specifications (vCPUs and Memory)
- Reinstalling or Changing the OS
diff --git a/docs/ecs/umn/en-us_topic_0013771101.html b/docs/ecs/umn/en-us_topic_0013771101.html index ac4035e3..36b8969d 100644 --- a/docs/ecs/umn/en-us_topic_0013771101.html +++ b/docs/ecs/umn/en-us_topic_0013771101.html @@ -4,41 +4,41 @@
diff --git a/docs/ecs/umn/en-us_topic_0013771102.html b/docs/ecs/umn/en-us_topic_0013771102.html index 17771945..0b631914 100644 --- a/docs/ecs/umn/en-us_topic_0013771102.html +++ b/docs/ecs/umn/en-us_topic_0013771102.html @@ -5,7 +5,7 @@-
-
- ECS Overview
+ - Product Consulting FAQ
- - ECS Creation
+ - ECS Creation FAQ
- - ECS Deletion
+ - ECS Deletion and Unsubscription FAQ
- - Login and Connection
+ - Remote Login FAQ
- - Regions and AZs
+ - Region and AZ FAQ
- - GUI Installation FAQs
+ - OS FAQ
- - Disk Management
+ - Disk Partition, Attachment, and Expansion FAQ
- - Data Backup and Restoration
+ - Data Backup and Restoration FAQ
- - Network Configurations
+ - Network Configuration FAQ
- - EIPs
+ - EIP FAQ
- - Passwords and Key Pairs
+ - Password and Key Pair FAQ
- - Database Applications
+ - Application Deployment and Software Installation FAQ
- - File Upload/Data Transfer
+ - File Upload/Data Transfer FAQ
- - Usage Errors
+ - ECS Failure FAQ
- - Resource Monitoring
+ - Slow ECS Response FAQ
- - Modifying Specifications
+ - Specification Modification FAQ
- - OS Management
+ - OS Change FAQ
- - Resource Management and Tags
+ - Resource Management and Tag FAQ
diff --git a/docs/ecs/umn/en-us_topic_0013771110.html b/docs/ecs/umn/en-us_topic_0013771110.html index 339bc7a1..fafecdf8 100644 --- a/docs/ecs/umn/en-us_topic_0013771110.html +++ b/docs/ecs/umn/en-us_topic_0013771110.html @@ -3,19 +3,22 @@-Parent topic: ECS Overview+Parent topic: Product Consulting FAQStarting and Stopping ECSs
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.
++ For bare metal ECSs (with physical flavors) such as C7t ECSs, do not run commands such as shutdown, poweoff, or half in the OS because the commands may be invalid or the ECS may fail to be started after being stopped.
+-Starting ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Start in the upper left corner of the list.
- In the displayed window, click OK.
Contact the administrator if the ECS has been in the Starting state for more than 30 minutes.
Stopping ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Stop in the upper left corner of the list.
- In the displayed dialog box, select Forcibly stop the preceding ECSs based on your service requirements.
After an ECS is forcibly stopped, unsaved data on the ECS will be lost.
+Stopping ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Stop in the upper left corner of the list.
- In the displayed dialog box, select Forcibly stop the preceding ECSs based on your service requirements.-
After an ECS is forcibly stopped, unsaved data on the ECS will be lost.
+ECSs with physical flavors, such as C7t ECSs, only support the force stop option. Ensure that you have saved all files on those ECSs.
- Click Yes to stop the ECSs. -
Contact the administrator if the ECS has been in the Stopping state for more than 30 minutes.
+- Click OK to stop the ECSs.
Contact the administrator if the ECS has been in the Stopping state for more than 30 minutes.
Restarting ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Restart in the upper left corner of the list.
After an ECS is forcibly restarted, unsaved data on the ECS will be lost.
+Restarting ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Restart in the upper left corner of the list.-
After an ECS is forcibly restarted, unsaved data on the ECS will be lost.
- Click Yes to stop the ECSs. @@ -26,7 +29,7 @@
Contact the administrator if the ECS has been in the Restarting state for more than 30 minutes.
+- Click OK 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_0013771112.html b/docs/ecs/umn/en-us_topic_0013771112.html index 06ebf00f..aa254823 100644 --- a/docs/ecs/umn/en-us_topic_0013771112.html +++ b/docs/ecs/umn/en-us_topic_0013771112.html @@ -10,7 +10,7 @@-Parent topic: Managing ECSs+Parent topic: Managing ECS Configurations - Click OK to stop the ECSs.
diff --git a/docs/ecs/umn/en-us_topic_0017130261.html b/docs/ecs/umn/en-us_topic_0017130261.html index 12e28452..f8e9fd3a 100644 --- a/docs/ecs/umn/en-us_topic_0017130261.html +++ b/docs/ecs/umn/en-us_topic_0017130261.html @@ -1,7 +1,7 @@Access Methods
You can access ECS through the web-based management console or HTTPS-based application programming interfaces (APIs).- Accessing ECSs through APIs
Use this method if you intend to integrate ECSs into a third-party system for secondary development. For details, see Elastic Cloud Server API Reference.
- Accessing ECSs through the management console
Use this method if you are not required to integrate ECSs with a third-party system.
-Log in to the management console with your account and choose Elastic Cloud Server on the homepage.
+Log in to the management console with your account and choose Elastic Cloud Server on the homepage.
Viewing ECS Details (List View)
-Scenarios
After obtaining ECSs, you can view and manage them on the management console. This section describes how to view detailed ECS configurations, including its name, image, system disk, data disks, VPC, NIC, security group, and EIP.
+Scenarios
After obtaining ECSs, you can view and manage them on the management console. This section describes how to view ECS configuration details, including its name, image, system disk, data disks, VPC, network interfaces, security group, EIP address, and bandwidth.
To view the private IP address of an ECS, view it on the Elastic Cloud Server page.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
The Elastic Cloud Server page is displayed. On this page, you can view your ECSs and the basic information about the ECSs, such as their specifications, images, and IP addresses.
diff --git a/docs/ecs/umn/en-us_topic_0017955381.html b/docs/ecs/umn/en-us_topic_0017955381.html index a7916219..2bfdde3f 100644 --- a/docs/ecs/umn/en-us_topic_0017955381.html +++ b/docs/ecs/umn/en-us_topic_0017955381.html @@ -22,7 +22,7 @@
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 Remotely Logging In to a Windows ECS (Using VNC).
+- Log in to the Windows ECS using VNC.
For details, see 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.
- Log in to the Windows ECS using VNC.
diff --git a/docs/ecs/umn/en-us_topic_0018073214.html b/docs/ecs/umn/en-us_topic_0018073214.html index 0e084ef7..8ad25f80 100644 --- a/docs/ecs/umn/en-us_topic_0018073214.html +++ b/docs/ecs/umn/en-us_topic_0018073214.html @@ -5,7 +5,7 @@-Parent topic: ECS Creation+Parent topic: ECS Creation FAQdiff --git a/docs/ecs/umn/en-us_topic_0018073215.html b/docs/ecs/umn/en-us_topic_0018073215.html index f8a14f4f..1dbd07cb 100644 --- a/docs/ecs/umn/en-us_topic_0018073215.html +++ b/docs/ecs/umn/en-us_topic_0018073215.html @@ -20,7 +20,7 @@-Parent topic: ECS Overview+Parent topic: Product Consulting FAQ59
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.
- Click OK to stop the ECSs.
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.
diff --git a/docs/ecs/umn/en-us_topic_0018073216.html b/docs/ecs/umn/en-us_topic_0018073216.html index 5556c6f3..94d8f511 100644 --- a/docs/ecs/umn/en-us_topic_0018073216.html +++ b/docs/ecs/umn/en-us_topic_0018073216.html @@ -57,7 +57,7 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQ - Use either of the following methods to import the key pair:
- In the Import Key Pair dialog box of the management console, click Select File and select the locally stored public key file (for example, the .txt file saved in 3 in Creating a Key Pair Using PuTTYgen).
- Selecting a file
diff --git a/docs/ecs/umn/en-us_topic_0018073221.html b/docs/ecs/umn/en-us_topic_0018073221.html index 812aefe0..90d21dac 100644 --- a/docs/ecs/umn/en-us_topic_0018073221.html +++ b/docs/ecs/umn/en-us_topic_0018073221.html @@ -6,7 +6,7 @@-Parent topic: ECS Deletion+Parent topic: ECS Deletion and Unsubscription FAQ - Logging in to a Linux ECS
diff --git a/docs/ecs/umn/en-us_topic_0018078501.html b/docs/ecs/umn/en-us_topic_0018078501.html index f3d3fdda..adf43476 100644 --- a/docs/ecs/umn/en-us_topic_0018078501.html +++ b/docs/ecs/umn/en-us_topic_0018078501.html @@ -5,7 +5,7 @@-Parent topic: ECS Deletion+Parent topic: ECS Deletion and Unsubscription FAQ - Choose Conversions > Export OpenSSH key.
diff --git a/docs/ecs/umn/en-us_topic_0018078503.html b/docs/ecs/umn/en-us_topic_0018078503.html index 4e162e18..9771c834 100644 --- a/docs/ecs/umn/en-us_topic_0018078503.html +++ b/docs/ecs/umn/en-us_topic_0018078503.html @@ -5,7 +5,7 @@-Parent topic: Network Configurations+Parent topic: Network Configuration FAQ - On the PuTTY Key Generator page, choose File > Save private key.
diff --git a/docs/ecs/umn/en-us_topic_0018078505.html b/docs/ecs/umn/en-us_topic_0018078505.html index badde532..9c0d9253 100644 --- a/docs/ecs/umn/en-us_topic_0018078505.html +++ b/docs/ecs/umn/en-us_topic_0018078505.html @@ -12,7 +12,7 @@-Parent topic: Network Configurations+Parent topic: Network Configuration FAQdiff --git a/docs/ecs/umn/en-us_topic_0018078509.html b/docs/ecs/umn/en-us_topic_0018078509.html index e6c5c43c..ff13939c 100644 --- a/docs/ecs/umn/en-us_topic_0018078509.html +++ b/docs/ecs/umn/en-us_topic_0018078509.html @@ -5,7 +5,7 @@-Parent topic: Database Applications+Parent topic: Application Deployment and Software Installation FAQdiff --git a/docs/ecs/umn/en-us_topic_0018078520.html b/docs/ecs/umn/en-us_topic_0018078520.html index 55e6e9d5..b3c073ea 100644 --- a/docs/ecs/umn/en-us_topic_0018078520.html +++ b/docs/ecs/umn/en-us_topic_0018078520.html @@ -6,7 +6,7 @@-Parent topic: Database Applications+Parent topic: Application Deployment and Software Installation FAQ
Do ECSs Support GUI?
Windows ECSs are managed through a GUI but Linux ECSs are managed through the CLI. You can configure a GUI if required.
-Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GiB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
+Before installing a GUI on an ECS, ensure that the memory is no less than 2 GB to prevent GUI installation or ECS startup failures.
Network Configurations
+Network Configuration FAQ
- How Can I Configure the NTP and DNS Servers for an ECS?
- - Configuring DNS
+ - How Do I Configure DNS for an ECS?
- Can the ECSs of Different Accounts Communicate over an Intranet?
- Will ECSs That I Purchased Deployed in the Same Subnet?
- - How Can I Configure Port Redirection?
+ - How Do I Configure Port Mapping?
- How Can I Obtain the MAC Address of My ECS?
diff --git a/docs/ecs/umn/en-us_topic_0018124786.html b/docs/ecs/umn/en-us_topic_0018124786.html
index 051b87c7..c5278f5b 100644
--- a/docs/ecs/umn/en-us_topic_0018124786.html
+++ b/docs/ecs/umn/en-us_topic_0018124786.html
@@ -1,6 +1,6 @@
- - What Is an AZ?
+ - What Is AZ and How Can I Select and View an AZ?
- Is Data Transmission Between AZs Billed?
diff --git a/docs/ecs/umn/en-us_topic_0018196906.html b/docs/ecs/umn/en-us_topic_0018196906.html
index 3fb4382a..3dc13b11 100644
--- a/docs/ecs/umn/en-us_topic_0018196906.html
+++ b/docs/ecs/umn/en-us_topic_0018196906.html
@@ -1,16 +1,16 @@
- - If the error message contains only the information that an identity authentication failure occurs and that the desired function is not supported, rectify the fault by following the instructions provided in Solution.
- If the error message shows that the fault was caused by "CredSSP Encryption Oracle Remediation", as shown in Figure 1, the fault may be caused by a security patch released by Microsoft in March 2018. This patch may affect RDP-based CredSSP connections. As a result, setting up RDP-based connections to ECSs failed. Rectify the fault by following the instructions provided in official Microsoft document.
+
- If the error message contains only the information that an identity authentication failure occurs and that the desired function is not supported, rectify the fault by following the instructions provided in Solution.
- If the error message shows that the fault was caused by "CredSSP Encryption Oracle Remediation", as shown in Figure 1, the fault may be caused by a security patch released by Microsoft in March 2018. This patch may affect RDP-based CredSSP connections. As a result, setting up RDP-based connections to ECSs failed. Rectify the fault by following the instructions provided in the official Microsoft document CredSSP updates for CVE-2018-0886.
- The password is forgotten.
- The password has expired.
- A temporary Linux ECS which runs Ubuntu 14.04 or later and locates in the same AZ as the target ECS is available.
- You have bound an EIP to the temporary ECS and configured the apt-get source.
- You have used either of the following methods to install ntfs-3g and chntpw software packages on the temporary ECS:
Method 1:
+Prerequisites
- A temporary Linux ECS running Ubuntu 14.04 or later is available. It is located in the same AZ and has the same CPU architecture as the target ECS.
- You have bound an EIP to the temporary ECS and configured the apt-get source.
- You have used either of the following methods to install ntfs-3g and chntpw software packages on the temporary ECS:
Method 1:
Run the following command to install the ntfs-3g and chntpw software packages:
sudo apt-get install ntfs-3g chntpw
Method 2:
@@ -15,7 +15,7 @@Procedure
- Stop the original ECS and detach the system disk.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Stop the original Windows ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the Windows ECS. Otherwise, password reset may fail.
- Locate the row containing the system disk to be detached and click Detach to detach the system disk from the ECS.
- Attach the system disk to the temporary ECS.
- On the page providing details about the temporary ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the system disk detached in step 1.e and attach it to the temporary ECS.
- Remotely log in to the temporary ECS.
- Run the following command to view the directory of the system disk detached from the original Windows ECS now attached to the temporary ECS:
fdisk -l
+ - Attach the system disk to the temporary ECS.
- On the temporary ECS details page, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the system disk detached in step 1.e and attach it to the temporary ECS.
- Remotely log in to the temporary ECS.
- Run the following command to view the directory of the system disk detached from the original Windows ECS now attached to the temporary ECS:
fdisk -l
- Run the following command to mount the file system of the detached system disk to the temporary ECS:
mount -t ntfs-3g /dev/Result obtained in step 2.d /mnt/
For example, if the result obtained in step 2.d is xvde2, run the following command:
mount -t ntfs-3g /dev/xvde2 /mnt/
@@ -43,31 +43,15 @@ Hives that have changed: Write hive files? (y/n) [n] : y 0<SAM> - OK
- Stop the temporary ECS, detach the system disk, and attach the system disk to the original Windows 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 temporarily attached in step 2.b.
- On the page providing details about the original Windows ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the data disk detached in step 4.b and device name /dev/sda.
- Start the original Windows ECS and set a new login password.
- Click Start to start the original Windows ECS. After the status becomes Running, click Remote Login in the Operation column.
- Click Start. Enter CMD in the search box and press Enter.
- Run the following command to change the password (the new password must meet the requirements described in Table 1):
net user Administrator New password
- -+
-Table 1 Password complexity requirements Parameter
-Requirement
-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 start with a slash (/) for Windows ECSs.
- Stop the temporary ECS, detach the system disk, and attach the system disk to the original Windows ECS.
- Stop the temporary ECS, go to the ECS details page, and click the Disks tab.
- Click Detach to detach the data disk temporarily attached in step 2.b.
- On the original Windows ECS details page, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the data disk detached in step 4.b and attach it to the original ECS as the system disk.
- Start the original Windows ECS and set a new login password.
- Click Start to start the original Windows ECS. After the status becomes Running, click Remote Login in the Operation column.
- Click Start. Enter CMD in the search box and press Enter.
- Run the following command to set a new password. The new password must meet the password complexity requirements described in Application Scenarios for Using Passwords.
net user Administrator New password
- Stop the original ECS and detach the system disk.
diff --git a/docs/ecs/umn/en-us_topic_0021427650.html b/docs/ecs/umn/en-us_topic_0021427650.html index 2c81b259..9812700d 100644 --- a/docs/ecs/umn/en-us_topic_0021427650.html +++ b/docs/ecs/umn/en-us_topic_0021427650.html @@ -5,14 +5,14 @@-Parent topic: Passwords+Parent topic: Password Reset- The password is forgotten.
- The password has expired.
This section describes how to reset the password of user root. After resetting the password, you can log in to the ECS, and change the private key or reset the password of a non-root user.
- A temporary Linux ECS which locates in the same AZ as the target ECS is available.
- You have bound an EIP to the temporary ECS.
- A temporary Linux ECS is available. It is located in the same AZ and has the same CPU architecture as the target ECS.
- You have bound an EIP to the temporary ECS.
- Download the script for resetting the password and upload the script to the temporary ECS.
Contact customer service to obtain the password reset script. Use a connection tool, such as WinSCP, to upload the obtained changepasswd.sh script to the temporary ECS.
To download WinSCP, log in at https://winscp.net/.
- - Stop the original Linux ECS, detach the system disk from it, and attach the system disk to the temporary ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Stop the original ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the original ECS. Otherwise, password reset may fail.
+- Stop the original Linux ECS, detach the system disk from it, and attach the system disk to the temporary ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Stop the original ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the original ECS. Otherwise, password reset may fail.
- Locate the row containing the system disk to be detached and click Detach to detach the system disk from the ECS.
- Attach the system disk to the temporary ECS.
- On the page providing details about the temporary ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the system disk detached in step 2.e and attach it to the temporary ECS.
- Attach the system disk to the temporary ECS.
- On the page providing details about the temporary ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the system disk detached in step 2.e and attach it to the temporary ECS.
- Log in to the temporary ECS remotely and reset the password.
- Locate the row containing the temporary ECS and click Remote Login in the Operation column.
- Run the following command to view the directory of the system disk detached from the original Linux ECS now attached to the temporary ECS:
fdisk -l
Figure 1 Viewing the directory of the system disk
- Run the following commands in the directory where the changepasswd.sh script is stored to run the script for resetting the password:
chmod +x changepasswd.sh
@@ -29,13 +29,13 @@ - 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 AllowUsers root at the end of the file.
-
- 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.
- 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 temporarily attached in step 3.
- 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 427cc2a1..88a608b4 100644 --- a/docs/ecs/umn/en-us_topic_0024911405.html +++ b/docs/ecs/umn/en-us_topic_0024911405.html @@ -10,15 +10,15 @@-Parent topic: Passwords+Parent topic: Password Reset - Stop the original Linux ECS, detach the system disk from it, and attach the system disk to the temporary ECS.
- The target ECS is stopped.
- The target ECS has a system disk attached.
- 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.
+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: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- (Optional) Select a License Type (Use license from the system or Bring your own license (BYOL)) if the reinstalled OS running on your ECS is billed. For more details, see License Types.
The following OSs are billed:
- SUSE Linux Enterprise Server
- Oracle Enterprise Linux
- Red Hat Enterprise Linux
- Select the login mode.
If the target ECS uses key pair authentication, you can replace the original key pair.
-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.
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.
+Figure 1 Reinstalling an OS+- Click OK.
- In the ECS OS Reinstallation dialog box, confirm the settings, and click Submit.
diff --git a/docs/ecs/umn/en-us_topic_0024912311.html b/docs/ecs/umn/en-us_topic_0024912311.html index 116e7146..b845053a 100644 --- a/docs/ecs/umn/en-us_topic_0024912311.html +++ b/docs/ecs/umn/en-us_topic_0024912311.html @@ -5,7 +5,7 @@After the request is submitted, the status Reinstalling is displayed. When this status disappears, the reinstallation is complete. During the reinstallation process, a temporary ECS is created. After the reinstallation is complete, this ECS will be automatically deleted. Do not perform any operation on the temporary ECS during the reinstallation process.
diff --git a/docs/ecs/umn/en-us_topic_0025445670.html b/docs/ecs/umn/en-us_topic_0025445670.html index 9c74d99f..27dc6e68 100644 --- a/docs/ecs/umn/en-us_topic_0025445670.html +++ b/docs/ecs/umn/en-us_topic_0025445670.html @@ -5,7 +5,7 @@-Parent topic: OS Management+Parent topic: OS Change FAQdiff --git a/docs/ecs/umn/en-us_topic_0027157850.html b/docs/ecs/umn/en-us_topic_0027157850.html index f4980448..a678e78e 100644 --- a/docs/ecs/umn/en-us_topic_0027157850.html +++ b/docs/ecs/umn/en-us_topic_0027157850.html @@ -7,43 +7,48 @@-Parent topic: Network Configurations+Parent topic: Network Configuration FAQ-Prerequisites
- A proxy ECS with an EIP bound is available.
- The IP address of the proxy ECS is in the same network and same security group as the ECSs that need to access the Internet.
Linux Proxy ECS
In this example, the proxy ECS runs CentOS 6.5.
+Linux Proxy ECS
The following uses a proxy ECS running CentOS 6.5 as an example. For details about other OSs and versions, see the official help documentation.
- 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 proxy ECS name for search.
- Click the name of the proxy ECS. The page providing details about the ECS is displayed.
- On the NICs tab, click
. Then, disable Source/Destination Check.Figure 1 Disabling source/destination check
By default, the source/destination check function is enabled. When this function is enabled, the system checks whether source IP addresses contained in the packets sent by ECSs are correct. If the IP addresses are incorrect, the system does not allow the ECSs to send the packets. This mechanism prevents packet spoofing, thereby improving system security. However, this mechanism prevents the packet sender from receiving returned packets. Therefore, disable the source/destination check.
- Log in to the proxy ECS.
For more details, see Login Overview (Linux).
- - Run the following command to check whether the proxy ECS can access the Internet:
ping www.google.com
+ - Check whether the proxy ECS can access the Internet.
ping www.google.com
The proxy ECS can access the Internet if information similar to the following is displayed:
64 bytes from 220.181.111.148: icmp_seq=1 ttl=51 time=9.34 ms 64 bytes from 220.181.111.148: icmp_seq=2 ttl=51 time=9.11 ms 64 bytes from 220.181.111.148: icmp_seq=3 ttl=51 time=8.99 ms
- - Run the following command to check whether IP forwarding is enabled on the proxy ECS:
cat /proc/sys/net/ipv4/ip_forward
- - - Run the following command to open the IP forwarding configuration file in the vi editor: +
- Install iptables. +
- Set the automatic startup of iptables.
+
systemctl enable iptables
+ - Disable the firewall.
+
systemctl disable firewalld
+ - Check whether IP forwarding is enabled on the proxy ECS.
cat /proc/sys/net/ipv4/ip_forward
+ + - Open the IP forwarding configuration file in the vi editor.
- Press i to enter editing mode.
- Set the net.ipv4.ip_forward value to 1.
Set the net.ipv4.ip_forward value to 1.
If the sysctl.conf file does not contain the net.ipv4.ip_forward parameter, run the following command to add it:
echo net.ipv4.ip_forward=1 >> /etc/sysctl.conf
- Press Esc, type :wq, and press Enter.
The system saves the configurations and exits the vi editor.
- - Run the following command to make the modification take effect: -
- Run the following commands to configure default iptables rules:
iptables -P INPUT ACCEPT
+ - Apply the modification. +
- Configure default iptables rules.
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
-
Running iptables -P INPUT ACCEPT will set default INPUT policy to ACCEPT, which poses security risks. You are advised to set security group rules to restrict inbound access.
- Run the following command to configure source network address translation (SNAT) to enable ECSs in the same network segment to access the Internet through the proxy ECS:
iptables -t nat -A POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
+ - Configure source network address translation (SNAT) to enable ECSs in the same network segment to access the Internet through the proxy ECS.
iptables -t nat -A POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
For example, if the proxy ECS is in network 192.168.125.0, the subnet mask has 24 bits, and the private IP address is 192.168.125.4, run the following command:
iptables -t nat -A POSTROUTING -o eth0 -s 192.168.125.0/24 -j SNAT --to 192.168.125.4
- diff --git a/docs/ecs/umn/en-us_topic_0027268511.html b/docs/ecs/umn/en-us_topic_0027268511.html index fea31575..4159cd59 100644 --- a/docs/ecs/umn/en-us_topic_0027268511.html +++ b/docs/ecs/umn/en-us_topic_0027268511.html @@ -1,6 +1,6 @@ -To retain the preceding configuration even after the ECS is restarted, run the vi /etc/rc.local command to edit the rc.local file. Specifically, copy the rule described in step 16 into rc.local, press Esc to exit Insert mode, and enter :wq to save the settings and exit.
+- To retain the preceding configuration even after the ECS is restarted, run the vi /etc/rc.local command to edit the rc.local file. Specifically, copy the rule described in step 19 into rc.local, press Esc to exit Insert mode, and enter :wq to save the settings and exit.
- Run the following commands to save the iptables configuration and make it start up automatically upon ECS startup: +
- Save the iptables configuration and set the automatic startup of iptables.
chkconfig iptables on
-- Run the following command to check whether SNAT has been configured: +
- 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
+ - Delete the added iptables rules as needed.
iptables -t nat -D POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
For example, if the proxy ECS is in network segment 192.168.125.0, the subnet mask has 24 bits, and the private IP address is 192.168.125.4, run the following command:
iptables -t nat -D POSTROUTING -o eth0 -s 192.168.125.0/24 -j SNAT --to 192.168.125.4
Remotely Logging In to a Windows ECS (Using VNC)
+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.
diff --git a/docs/ecs/umn/en-us_topic_0027371530.html b/docs/ecs/umn/en-us_topic_0027371530.html index 9a8d00ed..298bf96e 100644 --- a/docs/ecs/umn/en-us_topic_0027371530.html +++ b/docs/ecs/umn/en-us_topic_0027371530.html @@ -17,7 +17,7 @@-Parent topic: Monitoring+Parent topic: Monitoring Using Cloud Eyediff --git a/docs/ecs/umn/en-us_topic_0027371531.html b/docs/ecs/umn/en-us_topic_0027371531.html index 43926afc..624b811b 100644 --- a/docs/ecs/umn/en-us_topic_0027371531.html +++ b/docs/ecs/umn/en-us_topic_0027371531.html @@ -15,7 +15,7 @@-Parent topic: Monitoring+Parent topic: Monitoring Using Cloud Eyediff --git a/docs/ecs/umn/en-us_topic_0029792884.html b/docs/ecs/umn/en-us_topic_0029792884.html index 649bec90..fee8d03b 100644 --- a/docs/ecs/umn/en-us_topic_0029792884.html +++ b/docs/ecs/umn/en-us_topic_0029792884.html @@ -7,7 +7,7 @@-Parent topic: Monitoring+Parent topic: Monitoring Using Cloud Eye
diff --git a/docs/ecs/umn/en-us_topic_0029806525.html b/docs/ecs/umn/en-us_topic_0029806525.html index 3149b73d..8f66a252 100644 --- a/docs/ecs/umn/en-us_topic_0029806525.html +++ b/docs/ecs/umn/en-us_topic_0029806525.html @@ -15,7 +15,7 @@-Parent topic: ECS Deletion+Parent topic: ECS Deletion and Unsubscription FAQdiff --git a/docs/ecs/umn/en-us_topic_0030013188.html b/docs/ecs/umn/en-us_topic_0030013188.html index 6f4320c8..8c5573d5 100644 --- a/docs/ecs/umn/en-us_topic_0030013188.html +++ b/docs/ecs/umn/en-us_topic_0030013188.html @@ -3,14 +3,14 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQCan an ECS Without an EIP Bound Access the Internet?
diff --git a/docs/ecs/umn/en-us_topic_0030828257.html b/docs/ecs/umn/en-us_topic_0030828257.html index 8e1b39eb..ab45583b 100644 --- a/docs/ecs/umn/en-us_topic_0030828257.html +++ b/docs/ecs/umn/en-us_topic_0030828257.html @@ -4,7 +4,7 @@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.
-VPC
Virtual Private Cloud (VPC) allows you to create customized virtual networks in your logically isolated AZ. Such networks are dedicated zones that are logically isolated, providing secure network environments for your ECSs. You can define security groups, virtual private networks (VPNs), IP address segments, and bandwidth for a VPC. This facilitates internal network configuration and management and allows you to change your network in a secure and convenient network manner. You can also customize the ECS access rules within a security group and between security groups to improve ECS security.
For more information about VPC, see Virtual Private Cloud User Guide.
Subnet
A subnet is a range of IP addresses in your VPC and provides IP address management and DNS resolution functions for ECSs in it. The IP addresses of all ECSs in a subnet belong to the subnet.
+Subnets
A subnet is a range of IP addresses in your VPC and provides IP address management and DNS resolution functions for ECSs in it. The IP addresses of all ECSs in a subnet belong to the subnet.
By default, ECSs in all subnets of the same VPC can communicate with each other, while ECSs in different VPCs cannot.
Security Group
A security group is a collection of access control rules for ECSs that have the same security protection requirements and that are mutually trusted. By adding an ECS to a security group, you apply all the rules defined for this security group to this ECS.
diff --git a/docs/ecs/umn/en-us_topic_0030828258.html b/docs/ecs/umn/en-us_topic_0030828258.html index 923d2563..1e1e6603 100644 --- a/docs/ecs/umn/en-us_topic_0030828258.html +++ b/docs/ecs/umn/en-us_topic_0030828258.html @@ -1,10 +1,10 @@ -Modifying ECS Specifications
+Modifying ECS Specifications (vCPUs and Memory)
diff --git a/docs/ecs/umn/en-us_topic_0030831990.html b/docs/ecs/umn/en-us_topic_0030831990.html index 20aded25..47925372 100644 --- a/docs/ecs/umn/en-us_topic_0030831990.html +++ b/docs/ecs/umn/en-us_topic_0030831990.html @@ -6,7 +6,7 @@- Login Overview (Linux)
- - Remotely Logging In to a Linux ECS (Using VNC)
+ - Logging In to a Linux ECS Using VNC
- Logging In to a Linux ECS Using an SSH Key Pair
diff --git a/docs/ecs/umn/en-us_topic_0030878383.html b/docs/ecs/umn/en-us_topic_0030878383.html
index 05f4540a..34189033 100644
--- a/docs/ecs/umn/en-us_topic_0030878383.html
+++ b/docs/ecs/umn/en-us_topic_0030878383.html
@@ -8,7 +8,7 @@
- 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.
- Click the Security Groups tab, expand the information of the security group, and view security group rules.
- Click the security group ID.
The system automatically switches to the security group details page.
- Configure required parameters.
You can click + to add more inbound rules.
-Figure 1 Add Inbound Rule+
Figure 1 Add Inbound Rule
Table 1 Inbound rule parameter description Parameter
- Configure required parameters.
You can click + to add more outbound rules.
-Figure 2 Add Outbound Rule+
Figure 2 Add Outbound Rule-
Table 2 Outbound rule parameter description Parameter
+-Table 2 Outbound rule parameter description Parameter
Description
+Description
Example Value
- Login Overview (Windows)
- - Remotely Logging In to a Windows ECS (Using VNC)
+ - Logging In to a Windows ECS Using VNC
- Logging In to a Windows ECS Using MSTSC
diff --git a/docs/ecs/umn/en-us_topic_0030911465.html b/docs/ecs/umn/en-us_topic_0030911465.html
index b83fd75c..e406c6dc 100644
--- a/docs/ecs/umn/en-us_topic_0030911465.html
+++ b/docs/ecs/umn/en-us_topic_0030911465.html
@@ -338,7 +338,7 @@
- Remote Logins
- - Logins Through the Management Console
+ - VNC Login
- Remote Login Errors on Windows
diff --git a/docs/ecs/umn/en-us_topic_0030932496.html b/docs/ecs/umn/en-us_topic_0030932496.html
index e68c5cc3..5531ebd7 100644
--- a/docs/ecs/umn/en-us_topic_0030932496.html
+++ b/docs/ecs/umn/en-us_topic_0030932496.html
@@ -5,7 +5,7 @@
- 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.
@@ -23,7 +23,7 @@ - Application Scenarios for Using Passwords
- - Changing the Login Password on an ECS
+ - Resetting the Password for Logging In to an ECS in the OS
- Resetting the Password for Logging In to a Windows ECS
@@ -15,7 +15,7 @@
- Obtain the private key file (.pem file) used when you created the ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Get Password.Figure 1 Get Password+
diff --git a/docs/ecs/umn/en-us_topic_0031523135.html b/docs/ecs/umn/en-us_topic_0031523135.html index e2f51c5f..a35920ea 100644 --- a/docs/ecs/umn/en-us_topic_0031523135.html +++ b/docs/ecs/umn/en-us_topic_0031523135.html @@ -21,9 +21,9 @@Obtaining the Password Through the Management Console
- Obtain the private key file (.pem file) used when you created the ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Get Password.Figure 1 Get Password
- Use either of the following methods to obtain the password through the key file:
- Click Select File and upload the key file from a local directory.
- Copy the key file content to the text field.
- Click Get Password to obtain a random password.
- 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.
- 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+
Figure 1 Changing an OS - (Optional) Select the Encryption option to encrypt the system disk during OS change.
To enable encryption, click Create Xrole to assign KMS access permissions to EVS. If you have rights granting 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: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Configure the login mode.
If the target ECS uses key pair authentication, you can replace the original key pair.
- Click OK.
- In the Change ECS OS dialog box, confirm the specifications, and click Submit.
After the application is submitted, the status Changing OS is displayed. When this status disappears, the OS change is complete.
- diff --git a/docs/ecs/umn/en-us_topic_0031734664.html b/docs/ecs/umn/en-us_topic_0031734664.html index f01f542a..934feac6 100644 --- a/docs/ecs/umn/en-us_topic_0031734664.html +++ b/docs/ecs/umn/en-us_topic_0031734664.html @@ -15,7 +15,7 @@A temporary ECS is created during the OS change process. After the process is complete, this ECS will be automatically deleted.
+ During the OS change process, a temporary ECS is created. After the OS change is complete, this ECS will be automatically deleted.
diff --git a/docs/ecs/umn/en-us_topic_0031736846.html b/docs/ecs/umn/en-us_topic_0031736846.html index e651a395..ef33ca7b 100644 --- a/docs/ecs/umn/en-us_topic_0031736846.html +++ b/docs/ecs/umn/en-us_topic_0031736846.html @@ -1,6 +1,6 @@ --Parent topic: Passwords and Key Pairs+Parent topic: Password and Key Pair FAQWhy Does the System Display a Message Indicating that the Password for Logging In to a Windows ECS Cannot Be Obtained?
+Why Does the System Display a Message Indicating that the Password for Logging In to an ECS Cannot Be Obtained?
Symptom
Password authentication is required to log in to a Windows ECS. Therefore, you require a key file to obtain the initial password for logging in to the ECS. However, after you click Get Password (see Obtaining the Password for Logging In to a Windows ECS), the system displays a message indicating that the password could not be obtained, resulting in an ECS login failure.
Possible Causes
Possible causes vary depending on the image used to create the Windows ECS.
diff --git a/docs/ecs/umn/en-us_topic_0032380449.html b/docs/ecs/umn/en-us_topic_0032380449.html index f8b49596..ac532768 100644 --- a/docs/ecs/umn/en-us_topic_0032380449.html +++ b/docs/ecs/umn/en-us_topic_0032380449.html @@ -1,6 +1,6 @@ -Passing User Data to ECSs
+Passing User Data
@@ -63,7 +63,7 @@Scenarios
Specify User Data to pass user data to ECSs to:
- Simplify ECS configuration.
- Initialize the ECS OS configuration.
- Upload your scripts to ECSs during ECS creation.
- Perform other tasks using scripts.
- How can I view the customized user data passed to a Linux ECS?
- Log in to the ECS.
- Run the following command to view the customized user data as user root:
curl http://169.254.169.254/openstack/latest/user_data
- Script usage examples
This section describes how to inject scripts in different formats into Linux ECSs and view script execution results.
+- Script usage examples
This section describes how to pass scripts in different formats into Linux ECSs and view script execution results.
Example 1: Inject a user-data script.
When creating an ECS, set User Data to As text and enter the customized user data script.
#!/bin/bash @@ -71,7 +71,7 @@ echo "Hello, the time is now $(date -R)" | tee /root/output.txt
After the ECS is created, start it and run the cat [file] command to check the script execution result.
[root@XXXXXXXX ~]# cat /root/output.txt Hello, the time is now Mon, 16 Jul 2016 16:03:18+0800
-Example 2: Inject a Cloud-Config data script.
+Example 2: Inject a Cloud-Config data script.
When creating an ECS, set User Data to As text and enter the customized user data script.
#cloud-config bootcmd: @@ -107,9 +107,9 @@ bootcmd:
diff --git a/docs/ecs/umn/en-us_topic_0030930805.html b/docs/ecs/umn/en-us_topic_0030930805.html index 239e66d0..f836643e 100644 --- a/docs/ecs/umn/en-us_topic_0030930805.html +++ b/docs/ecs/umn/en-us_topic_0030930805.html @@ -1,6 +1,6 @@ --Parent topic: Monitoring+Parent topic: Monitoring Using Cloud EyeECS Overview
+Product Consulting FAQ
-
diff --git a/docs/ecs/umn/en-us_topic_0030930806.html b/docs/ecs/umn/en-us_topic_0030930806.html
index 01dd5d7d..e3eb77d8 100644
--- a/docs/ecs/umn/en-us_topic_0030930806.html
+++ b/docs/ecs/umn/en-us_topic_0030930806.html
@@ -1,6 +1,6 @@
-
EIPs
+EIP FAQ
diff --git a/docs/ecs/umn/en-us_topic_0030930807.html b/docs/ecs/umn/en-us_topic_0030930807.html index c97b81f9..1f2b470b 100644 --- a/docs/ecs/umn/en-us_topic_0030930807.html +++ b/docs/ecs/umn/en-us_topic_0030930807.html @@ -1,12 +1,12 @@ -Login and Connection
+Remote Login FAQ
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 Remotely Logging In to a Linux ECS (Using VNC).
+For instructions about how to configure the keyboard language for a Linux ECS, see Logging In to a Linux ECS Using VNC.
Procedure
diff --git a/docs/ecs/umn/en-us_topic_0030932497.html b/docs/ecs/umn/en-us_topic_0030932497.html index 5f954183..2e6d016d 100644 --- a/docs/ecs/umn/en-us_topic_0030932497.html +++ b/docs/ecs/umn/en-us_topic_0030932497.html @@ -1,11 +1,13 @@-Parent topic: Logins Through the Management Console+Parent topic: VNC LoginWhat Should I Do If the Page Does not Respond After I Log In to an ECS Using VNC and Do Not Perform Any Operation for a Long Period of Time?
-If your computer is running Windows 7 and you logged in to the ECS using Internet Explorer 10 or 11, click AltGr twice on the VNC page to activate the page.
+If you log in to an ECS running Windows 7 through VNC using Internet Explorer 10 or 11 and do not perform any operation for a long time, the VNC page may not respond.
+In this case, you can click AltGr twice on the VNC page to activate the page.
+If the fault persists, contact technical support.
diff --git a/docs/ecs/umn/en-us_topic_0030932499.html b/docs/ecs/umn/en-us_topic_0030932499.html index 793944b6..ee64626f 100644 --- a/docs/ecs/umn/en-us_topic_0030932499.html +++ b/docs/ecs/umn/en-us_topic_0030932499.html @@ -1,11 +1,13 @@-Parent topic: Logins Through the Management Console+Parent topic: VNC LoginWhat Should I Do If I Cannot View Data After Logging In to an ECS Using VNC?
-After you log in to an ECS using VNC and view data, for example, play videos or run the cat command to view large files, VNC may become unavailable due to the high memory usage of the browser. In such a case, use another browser and log in to the ECS again.
+After you log in to an ECS using VNC and view data, for example, play videos or run the cat command to view large files in Linux OSs, VNC may become unavailable due to the high memory usage of the browser.
+In such a case, use another browser and log in to the ECS again.
+If the fault persists, contact technical support.
diff --git a/docs/ecs/umn/en-us_topic_0030932500.html b/docs/ecs/umn/en-us_topic_0030932500.html index 7a2a1a9b..7ad6745f 100644 --- a/docs/ecs/umn/en-us_topic_0030932500.html +++ b/docs/ecs/umn/en-us_topic_0030932500.html @@ -12,7 +12,7 @@-Parent topic: Logins Through the Management Console+Parent topic: VNC Logindiff --git a/docs/ecs/umn/en-us_topic_0031073513.html b/docs/ecs/umn/en-us_topic_0031073513.html index 7b1da2c8..91a7cacf 100644 --- a/docs/ecs/umn/en-us_topic_0031073513.html +++ b/docs/ecs/umn/en-us_topic_0031073513.html @@ -1,12 +1,12 @@ --Parent topic: Logins Through the Management Console+Parent topic: VNC LoginPasswords
+Password Reset
diff --git a/docs/ecs/umn/en-us_topic_0031107266.html b/docs/ecs/umn/en-us_topic_0031107266.html index 08a7fa40..83fdcaf0 100644 --- a/docs/ecs/umn/en-us_topic_0031107266.html +++ b/docs/ecs/umn/en-us_topic_0031107266.html @@ -4,7 +4,7 @@-Parent topic: Passwords and Key Pairs Management+Parent topic: Passwords and Key Pairs-Scenarios
Password authentication is required to log in to a Windows ECS. You must use the key file used when you created the ECS to obtain the administrator password generated during ECS creation. The administrator user is Administrator or the user configured using Cloudbase-Init. This password is randomly generated, offering high security.
You can obtain the initial password for logging in to a Windows ECS through the management console or APIs. For details, see this section.
-Obtaining the Password Through the Management Console
Procedure
- How can I view the customized user data passed into a Windows ECS?
- Log in to the ECS.
- Access the following URL in the address box of the browser and view the user data: +
- How can I view the customized user data passed into a Windows ECS? -
- Script usage examples
This section describes how to inject scripts in different formats into Windows ECSs and view script execution results.
+ - Script usage examples
This section describes how to inject scripts in different formats into Windows ECSs and view script execution results.
Example 1: Inject a batch-processing program script.
When creating an ECS, set User Data to As text and enter the customized user data script.
rem cmd @@ -143,16 +143,16 @@ write_files: -
Table 3 Password complexity requirements Parameter
+Table 3 Password complexity requirements Parameter
Requirement
+Requirement
Password
+Password
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- 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.
- 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.)
-The new password must meet the password complexity requirements listed in Table 4.
Table 4 Password complexity requirements Parameter
+Table 4 Password complexity requirements Parameter
Requirement
+Requirement
Password
+Password
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- 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.
- 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.)
diff --git a/docs/ecs/umn/en-us_topic_0032850906.html b/docs/ecs/umn/en-us_topic_0032850906.html index 7625a5a2..c39ca820 100644 --- a/docs/ecs/umn/en-us_topic_0032850906.html +++ b/docs/ecs/umn/en-us_topic_0032850906.html @@ -2,11 +2,12 @@-Parent topic: Usage Errors+Parent topic: ECS Failure FAQWhy Does a Blank Screen Appear After I Attempted to Log In to an ECS Using VNC?
The blank screen means that another user has logged in to this ECS using VNC, so you were logged out.
-Only one user can be logged in to an ECS using VNC at a time. If you are already logged in and another user logs in to the same ECS, you will be automatically logged out. You can log back in, but that will kick the other user out.
+Only one user can be logged in to an ECS using VNC at a time. If you are already logged in and another user logs in to the same ECS, you will be automatically logged out.
+You can log back in, but that will kick the other user out.
diff --git a/docs/ecs/umn/en-us_topic_0032980085.html b/docs/ecs/umn/en-us_topic_0032980085.html index 047510cd..e06ddb8c 100644 --- a/docs/ecs/umn/en-us_topic_0032980085.html +++ b/docs/ecs/umn/en-us_topic_0032980085.html @@ -14,19 +14,19 @@-Parent topic: Logins Through the Management Console+Parent topic: VNC Login-Adding an ECS to an ECS Group
To improve service reliability, you can add ECSs to an ECS group so that these ECSs in this group can run on different hosts.
- - After an ECS is added to an ECS group, the system reallocates a host to run this ECS to ensure that ECSs in this group are running on different hosts. When the ECS is being restarted, the startup may fail due to insufficient resources. In such a case, remove the ECS from the ECS group and try to restart the ECS again.
- ECSs that have local disks attached can be added to an ECS group only during the creation process. Once created, they can no longer be added to any ECS groups.
- ECSs that have local disks, GPU cards, or FPGA cards attached can be added to an ECS group only during the creation process. Once created, they can no longer be added to any ECS groups.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the row that contains the target ECS group and click Add ECS in the Operation column.
- On the Add ECS page, select an ECS to be added.
- Click OK. The ECS is added to the ECS group.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the row that contains the target ECS group and click Add ECS in the Operation column.
- On the Add ECS page, select an ECS to be added.
- Click OK. The ECS is added to the ECS group.
Removing an ECS from an ECS Group
After an ECS is removed from an ECS group, the ECS does not comply with the anti-affinity policy anymore.
-- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Expand the ECS group information and view the ECSs in the ECS group.
- Locate the ECS to be removed and click Remove in the Operation column.
- In the displayed dialog box, click Yes.
The ECS is removed from the ECS group.
+Removing an ECS from an ECS Group
After an ECS is removed from an ECS group, the ECS does not comply with the ECS group policy anymore.
+- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Expand the ECS group information and view the ECSs in the ECS group.
- Locate the ECS to be removed and click Remove in the Operation column.
- In the displayed dialog box, click Yes.
The ECS is removed from the ECS group.
Deleting an ECS Group
After an ECS group is deleted, the policy does not apply to the ECSs in the ECS group anymore.
-- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the ECS group to be deleted and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the ECS group to be deleted and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
diff --git a/docs/ecs/umn/en-us_topic_0035470096.html b/docs/ecs/umn/en-us_topic_0035470096.html index 3d5b917f..7d7df437 100644 --- a/docs/ecs/umn/en-us_topic_0035470096.html +++ b/docs/ecs/umn/en-us_topic_0035470096.html @@ -17,7 +17,7 @@-Parent topic: Managing ECSs+Parent topic: Managing ECS ConfigurationsNetwork 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.
+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 received and 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.
- Maximum supplementary NICs: indicates the maximum number of supplementary 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 7954635b..bb7370b2 100644 --- a/docs/ecs/umn/en-us_topic_0035470099.html +++ b/docs/ecs/umn/en-us_topic_0035470099.html @@ -181,27 +181,27 @@ - For instructions about how to test PPS, see How Can I Test the Network Performance of Linux ECSs?.
- 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.
CentOS
- CentOS Stream 8.6 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
- CentOS Stream 9.6 64bit
- CentOS Stream 8.6 64bit
- CentOS 8.5 64bit
- CentOS 8.4 64bit
- CentOS 8.3 64bit
- CentOS 8.2 64bit
- CentOS 8.1 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
Debian
- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
- Debian GNU/Linux 12.0.0 64bit
- Debian GNU/Linux 11.7.0 64bit
- Debian GNU/Linux 11.6.0 64bit
- Debian GNU/Linux 11.5.0 64bit
- Debian GNU/Linux 11.4.0 64bit
- Debian GNU/Linux 11.3.0 64bit
- Debian GNU/Linux 11.2.0 64bit
- Debian GNU/Linux 11.1.0 64bit
- Debian GNU/Linux 11.0.0 64bit
- Debian GNU/Linux 10.13.0 64bit
- Debian GNU/Linux 10.12.0 64bit
- Debian GNU/Linux 10.11.0 64bit
- Debian GNU/Linux 10.10.0 64bit
- Debian GNU/Linux 10.9.0 64bit
- Debian GNU/Linux 10.8.0 64bit
- Debian GNU/Linux 10.7.0 64bit
- Debian GNU/Linux 10.6.0 64bit
- Debian GNU/Linux 10.5.0 64bit
- Debian GNU/Linux 10.4.0 64bit
- Debian GNU/Linux 10.3.0 64bit
- Debian GNU/Linux 10.2.0 64bit
- Debian GNU/Linux 10.1.0 64bit
- Debian GNU/Linux 10 64bit
EulerOS
EulerOS 2.5 64bit
+- EulerOS 2.12 64bit
- EulerOS 2.11 64bit
- EulerOS 2.10 64bit
- EulerOS 2.8 64bit
- EulerOS 2.7 64bit
- EulerOS 2.5 64bit
Fedora
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 39 64bit
- Fedora 38 64bit
- Fedora 37 64bit
- Fedora 36 64bit
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 32 64bit
- Fedora 31 64bit
OpenSUSE
OpenSUSE 15.3 64bit
+- OpenSUSE 15.5 64bit
- OpenSUSE 15.4 64bit
- OpenSUSE 15.3 64bit
- OpenSUSE 15.2 64bit
Oracle Linux
@@ -211,32 +211,32 @@Red Hat
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
- Red Hat Enterprise Linux 9.1 64bit
- Red Hat Enterprise Linux 9.0 64bit
- Red Hat Enterprise Linux 8.7 64bit
- Red Hat Enterprise Linux 8.6 64bit
- Red Hat Enterprise Linux 8.5 64bit
- Red Hat Enterprise Linux 8.4 64bit
- Red Hat Enterprise Linux 8.3 64bit
- Red Hat Enterprise Linux 8.2 64bit
- Red Hat Enterprise Linux 8.1 64bit
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
Rocky
Rocky 8 64bit
+- 9.2 64bit
- 9.1 64bit
- 9.0 64bit
- 8.8 64bit
- 8.7 64bit
- 8.6 64bit
- 8.5 64bit
- 8.4 64bit
- 8.3 64bit
- 8 64bit
SUSE
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP5 64bit
- Novell SUSE Linux Enterprise Server 15 SP4 64bit
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 22.04 Server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2022 Standard 64bit
- Windows Server 2022 Datacenter 64bit
- Windows Server 2019 Datacenter 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
openEuler
openEuler 20.03 64bit
+- openEuler 22.03 SP1 64bit
- openEuler 22.03 64bit
- openEuler 20.03 SP3 64bit
- openEuler 20.03 SP2 64bit
- openEuler 20.03 SP1 64bit
- openEuler 20.03 64bit
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.
+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 the scenarios where vCPU performance is not often (or always) used but is occasionally used.
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
@@ -1098,27 +1098,27 @@CentOS
- CentOS Stream 8.6 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
- CentOS Stream 9.6 64bit
- CentOS Stream 8.6 64bit
- CentOS 8.5 64bit
- CentOS 8.4 64bit
- CentOS 8.3 64bit
- CentOS 8.2 64bit
- CentOS 8.1 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
Debian
- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
- Debian GNU/Linux 12.0.0 64bit
- Debian GNU/Linux 11.7.0 64bit
- Debian GNU/Linux 11.6.0 64bit
- Debian GNU/Linux 11.5.0 64bit
- Debian GNU/Linux 11.4.0 64bit
- Debian GNU/Linux 11.3.0 64bit
- Debian GNU/Linux 11.2.0 64bit
- Debian GNU/Linux 11.1.0 64bit
- Debian GNU/Linux 11.0.0 64bit
- Debian GNU/Linux 10.13.0 64bit
- Debian GNU/Linux 10.12.0 64bit
- Debian GNU/Linux 10.11.0 64bit
- Debian GNU/Linux 10.10.0 64bit
- Debian GNU/Linux 10.9.0 64bit
- Debian GNU/Linux 10.8.0 64bit
- Debian GNU/Linux 10.7.0 64bit
- Debian GNU/Linux 10.6.0 64bit
- Debian GNU/Linux 10.5.0 64bit
- Debian GNU/Linux 10.4.0 64bit
- Debian GNU/Linux 10.3.0 64bit
- Debian GNU/Linux 10.2.0 64bit
- Debian GNU/Linux 10.1.0 64bit
- Debian GNU/Linux 10 64bit
EulerOS
EulerOS 2.5 64bit
+- EulerOS 2.12 64bit
- EulerOS 2.11 64bit
- EulerOS 2.10 64bit
- EulerOS 2.8 64bit
- EulerOS 2.7 64bit
- EulerOS 2.5 64bit
Fedora
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 39 64bit
- Fedora 38 64bit
- Fedora 37 64bit
- Fedora 36 64bit
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 32 64bit
- Fedora 31 64bit
OpenSUSE
OpenSUSE 15.3 64bit
+- OpenSUSE 15.5 64bit
- OpenSUSE 15.4 64bit
- OpenSUSE 15.3 64bit
- OpenSUSE 15.2 64bit
Oracle Linux
@@ -1128,32 +1128,32 @@Red Hat
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
- Red Hat Enterprise Linux 9.1 64bit
- Red Hat Enterprise Linux 9.0 64bit
- Red Hat Enterprise Linux 8.7 64bit
- Red Hat Enterprise Linux 8.6 64bit
- Red Hat Enterprise Linux 8.5 64bit
- Red Hat Enterprise Linux 8.4 64bit
- Red Hat Enterprise Linux 8.3 64bit
- Red Hat Enterprise Linux 8.2 64bit
- Red Hat Enterprise Linux 8.1 64bit
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
Rocky
Rocky 8 64bit
+- 9.2 64bit
- 9.1 64bit
- 9.0 64bit
- 8.8 64bit
- 8.7 64bit
- 8.6 64bit
- 8.5 64bit
- 8.4 64bit
- 8.3 64bit
- 8 64bit
SUSE
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP5 64bit
- Novell SUSE Linux Enterprise Server 15 SP4 64bit
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 22.04 Server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2022 Standard 64bit
- Windows Server 2022 Datacenter 64bit
- Windows Server 2019 Datacenter 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
openEuler
openEuler 20.03 64bit
+- openEuler 22.03 SP1 64bit
- openEuler 22.03 64bit
- openEuler 20.03 SP3 64bit
- openEuler 20.03 SP2 64bit
- openEuler 20.03 SP1 64bit
- openEuler 20.03 64bit
CentOS
- CentOS Stream 8.6 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
- CentOS Stream 9.6 64bit
- CentOS Stream 8.6 64bit
- CentOS 8.5 64bit
- CentOS 8.4 64bit
- CentOS 8.3 64bit
- CentOS 8.2 64bit
- CentOS 8.1 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
Debian
- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
- Debian GNU/Linux 12.0.0 64bit
- Debian GNU/Linux 11.7.0 64bit
- Debian GNU/Linux 11.6.0 64bit
- Debian GNU/Linux 11.5.0 64bit
- Debian GNU/Linux 11.4.0 64bit
- Debian GNU/Linux 11.3.0 64bit
- Debian GNU/Linux 11.2.0 64bit
- Debian GNU/Linux 11.1.0 64bit
- Debian GNU/Linux 11.0.0 64bit
- Debian GNU/Linux 10.13.0 64bit
- Debian GNU/Linux 10.12.0 64bit
- Debian GNU/Linux 10.11.0 64bit
- Debian GNU/Linux 10.10.0 64bit
- Debian GNU/Linux 10.9.0 64bit
- Debian GNU/Linux 10.8.0 64bit
- Debian GNU/Linux 10.7.0 64bit
- Debian GNU/Linux 10.6.0 64bit
- Debian GNU/Linux 10.5.0 64bit
- Debian GNU/Linux 10.4.0 64bit
- Debian GNU/Linux 10.3.0 64bit
- Debian GNU/Linux 10.2.0 64bit
- Debian GNU/Linux 10.1.0 64bit
- Debian GNU/Linux 10 64bit
EulerOS
EulerOS 2.5 64bit
+- EulerOS 2.12 64bit
- EulerOS 2.11 64bit
- EulerOS 2.10 64bit
- EulerOS 2.8 64bit
- EulerOS 2.7 64bit
- EulerOS 2.5 64bit
Fedora
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 39 64bit
- Fedora 38 64bit
- Fedora 37 64bit
- Fedora 36 64bit
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 32 64bit
- Fedora 31 64bit
OpenSUSE
OpenSUSE 15.3 64bit
+- OpenSUSE 15.5 64bit
- OpenSUSE 15.4 64bit
- OpenSUSE 15.3 64bit
- OpenSUSE 15.2 64bit
Oracle Linux
@@ -616,32 +616,32 @@Red Hat
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
- Red Hat Enterprise Linux 9.1 64bit
- Red Hat Enterprise Linux 9.0 64bit
- Red Hat Enterprise Linux 8.7 64bit
- Red Hat Enterprise Linux 8.6 64bit
- Red Hat Enterprise Linux 8.5 64bit
- Red Hat Enterprise Linux 8.4 64bit
- Red Hat Enterprise Linux 8.3 64bit
- Red Hat Enterprise Linux 8.2 64bit
- Red Hat Enterprise Linux 8.1 64bit
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
Rocky
Rocky 8 64bit
+- 9.2 64bit
- 9.1 64bit
- 9.0 64bit
- 8.8 64bit
- 8.7 64bit
- 8.6 64bit
- 8.5 64bit
- 8.4 64bit
- 8.3 64bit
- 8 64bit
SUSE
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP5 64bit
- Novell SUSE Linux Enterprise Server 15 SP4 64bit
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 22.04 Server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2022 Standard 64bit
- Windows Server 2022 Datacenter 64bit
- Windows Server 2019 Datacenter 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
openEuler
openEuler 20.03 64bit
+- openEuler 22.03 SP1 64bit
- openEuler 22.03 64bit
- openEuler 20.03 SP3 64bit
- openEuler 20.03 SP2 64bit
- openEuler 20.03 SP1 64bit
- openEuler 20.03 64bit
+ N/A
NOTE:The reference is for Windows or Linux ECSs.
@@ -32,16 +32,16 @@Background
Table 2 shows the ECS password complexity requirements.
-Table 2 Password complexity requirements Parameter
+-Table 2 Password complexity requirements Parameter
Requirement
+Requirement
Password
+Password
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- 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.
- 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.)
diff --git a/docs/ecs/umn/en-us_topic_0036046828.html b/docs/ecs/umn/en-us_topic_0036046828.html index b78cb7c7..973905f9 100644 --- a/docs/ecs/umn/en-us_topic_0036046828.html +++ b/docs/ecs/umn/en-us_topic_0036046828.html @@ -132,7 +132,7 @@ diff --git a/docs/ecs/umn/en-us_topic_0036068717.html b/docs/ecs/umn/en-us_topic_0036068717.html index 15ce6735..b45caf5d 100644 --- a/docs/ecs/umn/en-us_topic_0036068717.html +++ b/docs/ecs/umn/en-us_topic_0036068717.html @@ -72,7 +72,7 @@ STARTMODE="onboot"-Parent topic: Passwords+Parent topic: Password Resetdiff --git a/docs/ecs/umn/en-us_topic_0037470901.html b/docs/ecs/umn/en-us_topic_0037470901.html index 11a533f0..71e1ef1d 100644 --- a/docs/ecs/umn/en-us_topic_0037470901.html +++ b/docs/ecs/umn/en-us_topic_0037470901.html @@ -4,17 +4,19 @@-Parent topic: Network Configurations+Parent topic: Network Configuration FAQ-Scenarios
Disk-intensive ECSs can use both local disks and EVS disks to store data. Local disks are generally used to store service data and feature higher throughput than EVS disks.
Disk-intensive ECSs do not support specifications modification. When the capacity of local disks is insufficient, you can create a new disk-intensive ECS with higher specifications for capacity expansion. The data stored in the original ECS can be migrated to the new ECS through EVS.
diff --git a/docs/ecs/umn/en-us_topic_0037633087.html b/docs/ecs/umn/en-us_topic_0037633087.html index 293302fe..d4c3687c 100644 --- a/docs/ecs/umn/en-us_topic_0037633087.html +++ b/docs/ecs/umn/en-us_topic_0037633087.html @@ -18,7 +18,7 @@Procedure
- Create an EVS disk according to the volume of data to be migrated.
- Attach the EVS disk to the disk-intensive ECS for which you want to expand the capacity.
- Back up the data stored in the local disks to the EVS disk that is newly attached to the disk-intensive ECS.
- Detach the EVS disk from the ECS.
- On the Elastic Cloud Server page, select this disk-intensive ECS and ensure that it has been stopped.
If the ECS is running, choose More > Stop to stop the ECS.
- - Click the name of the disk-intensive ECS. The page providing details about the ECS is displayed.
- Click the Disks tab. Locate the row containing the EVS data disk and click Detach to detach the disk from the ECS.
- On the Elastic Cloud Server page, select this disk-intensive ECS and ensure that it has been stopped.
- Ensure that a new disk-intensive ECS with higher specifications than the original one is available.
The local disk capacity is sufficient enough to meet your requirements.
+Procedure
- Create an EVS disk according to the volume of data to be migrated.
- Attach the EVS disk created in 1 to the disk-intensive ECS for which you want to expand the capacity.
- Back up local disk data.
Back up the data stored in the local disks to the EVS disk that is newly attached to the disk-intensive ECS.
+- For Windows ECSs, directly copy the data to be backed up to the EVS disk.
- For Linux ECSs, run the cp command to copy the data to be backed up to the EVS disk.
- Detach the EVS disk from the ECS.
- On the Elastic Cloud Server page, select this disk-intensive ECS and ensure that it has been stopped.
If the ECS is running, choose More > Stop to stop the ECS.
+ - Click the name of the disk-intensive ECS to go to the ECS details page.
- Click the Disks tab. Locate the row containing the EVS data disk and click Detach to detach the disk from the ECS.
- On the Elastic Cloud Server page, select this disk-intensive ECS and ensure that it has been stopped.
- Prepare a new disk-intensive ECS with higher specifications and larger capacity than the original one.
Ensure that the local disk capacity can meet your requirements.
- Attach the EVS disk to the new disk-intensive ECS.
On the Elastic Cloud Server page, click the name of the ECS described in step 5 to view details.
- - Click the Disks tab. Then, click Attach Disk.
In the displayed dialog box, select the EVS disk detached in step 4 and the device name.
- - Migrate the data from the EVS disk to the local disks of the new disk-intensive ECS.
- Click the Disks tab. Then, click Attach Disk.
In the displayed dialog box, select the EVS disk detached in step 4 and the device name.
+- Migrate the data from the EVS disk in 7 to the local disks of the new disk-intensive ECS.
diff --git a/docs/ecs/umn/en-us_topic_0038024694.html b/docs/ecs/umn/en-us_topic_0038024694.html index 1f9de848..a3438913 100644 --- a/docs/ecs/umn/en-us_topic_0038024694.html +++ b/docs/ecs/umn/en-us_topic_0038024694.html @@ -178,22 +178,22 @@-Parent topic: Passwords and Key Pairs+Parent topic: Password and Key Pair FAQCentOS
- CentOS 7.9 64bit
- CentOS 7.7 64bit
- CentOS 8.5 64bit
- CentOS 8.4 64bit
- CentOS 8.3 64bit
- CentOS 8.2 64bit
- CentOS 8.1 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
EulerOS
EulerOS 2.5 64bit
+- EulerOS 2.12 64bit
- EulerOS 2.11 64bit
- EulerOS 2.10 64bit
- EulerOS 2.8 64bit
- EulerOS 2.7 64bit
- EulerOS 2.5 64bit
Fedora
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 39 64bit
- Fedora 38 64bit
- Fedora 37 64bit
- Fedora 36 64bit
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 32 64bit
- Fedora 31 64bit
OpenSUSE
OpenSUSE 15.3 64bit
+- OpenSUSE 15.5 64bit
- OpenSUSE 15.4 64bit
- OpenSUSE 15.3 64bit
- OpenSUSE 15.2 64bit
Oracle Linux
@@ -203,22 +203,23 @@Red Hat
Red Hat Enterprise Linux 7.9 64bit
+- Red Hat Enterprise Linux 9.1 64bit
- Red Hat Enterprise Linux 9.0 64bit
- Red Hat Enterprise Linux 8.7 64bit
- Red Hat Enterprise Linux 8.6 64bit
- Red Hat Enterprise Linux 8.5 64bit
- Red Hat Enterprise Linux 8.4 64bit
- Red Hat Enterprise Linux 8.3 64bit
- Red Hat Enterprise Linux 8.2 64bit
- Red Hat Enterprise Linux 8.1 64bit
- Red Hat Enterprise Linux 7.9 64bit
SUSE
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP5 64bit
- Novell SUSE Linux Enterprise Server 15 SP4 64bit
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 22.04 server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
Why Does the Failures Area Show an ECS Creation Failure But the ECS List Displays the Created ECS?
-Symptom
After you created an ECS bound with an EIP on the management console, the ECS creation was successful but binding the EIP failed due to insufficient EIPs. Although the Failures area showed that the ECS creation failed, the ECS was displayed in the ECS list. The results of the ECS creation task were inconsistent.
+Symptom
When you attempt to create an ECS with an EIP bound on the management console, the ECS creation was successful but the EIP binding failed due to insufficient EIPs. Although the Failures area showed that the ECS creation failed, the ECS was displayed in the ECS list. The results of the ECS creation task were inconsistent.
Root Cause
- The ECS list displays created ECSs.
- The Failures area shows the ECS creation status, including the statuses of subtasks, such as creating ECS resources and binding an EIP. Only when all subtasks are successful, the ECS is created.
If the ECS is created but EIP binding failed, the task failed. However, the ECS you created is temporarily displayed in the list. After the system rolls back, the ECS is removed from the list.
@@ -9,7 +9,7 @@diff --git a/docs/ecs/umn/en-us_topic_0039588795.html b/docs/ecs/umn/en-us_topic_0039588795.html index 7160f3fd..e00e6d1d 100644 --- a/docs/ecs/umn/en-us_topic_0039588795.html +++ b/docs/ecs/umn/en-us_topic_0039588795.html @@ -4,7 +4,7 @@-Parent topic: ECS Creation+Parent topic: ECS Creation FAQScenarios
After submitting the request for creating an ECS, you can view the creation status. This section describes how to view the creation status of an ECS.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- After creating an ECS, view the creation status above the ECS list beside the common operations (Start, Stop, Restart, and Delete).Figure 1 ECS creation status-
- Click the number displayed above Creating and view task details.
- An ECS that is being created is in one of the following states:
- Creating: The ECS is being created.
- Faulty: Creating the ECS failed. In such a case, the system automatically rolls back the task and displays an error code on the GUI, for example, Ecs.0013 Insufficient EIP quota.
- Running: The request of creating the ECS has been processed, and the ECS is running properly. An ECS in this state can provide services for you.
See How Do I Handle Error Messages Displayed on the Management Console? for troubleshooting.
+ - Click the number displayed above Creating and view task details.diff --git a/docs/ecs/umn/en-us_topic_0040630518.html b/docs/ecs/umn/en-us_topic_0040630518.html index 61b5bffa..967a9efd 100644 --- a/docs/ecs/umn/en-us_topic_0040630518.html +++ b/docs/ecs/umn/en-us_topic_0040630518.html @@ -15,7 +15,7 @@
- An ECS that is being created is in one of the following states:
- Creating: The ECS is being created.
- Faulty: Creating the ECS failed. In such a case, the system automatically rolls back the task and displays an error code on the GUI, for example, Ecs.0013 Insufficient EIP quota.
- Running: The request of creating the ECS has been processed, and the ECS is running properly. An ECS in this state can provide services for you.
See How Do I Handle Error Messages Displayed on the Management Console? for troubleshooting.
- If you find that the task status area shows an ECS creation failure but the ECS has been created successfully and displayed in the ECS list, see Why Does the Failures Area Show an ECS Creation Failure But the ECS List Displays the Created ECS?
- An ECS that is being created is in one of the following states:
- Run the following command to check whether the /etc/localtime file is available on the ECS:
ls /etc/localtime
- Run the following command to delete the existing /etc/localtime file:
rm /etc/localtime
- - Run the following command to create a symbolic link between /etc/localtime and your time zone file so that the ECS can find this time zone file when it references the local time:
ln -sf /usr/share/zoneinfo/Asia/city1/etc/localtime
+ - Run the following command to create a symbolic link between /etc/localtime and your time zone file so that the ECS can find this time zone file when it references the local time:
ln -sf /usr/share/zoneinfo/Asia/city1 /etc/localtime
- Run the following command to restart the ECS so that all services and applications running on the ECS use the new time zone:
- Log in to the ECS again and run the following command as user root to check whether the time zone has been changed:
ls -lh /etc/localtime
The following information is displayed:
@@ -31,7 +31,7 @@ lrwxrwxrwx 1 root root 33 Nov 27 11:01 /etc/localtime -> /usr/share/zoneinfo/
diff --git a/docs/ecs/umn/en-us_topic_0040863659.html b/docs/ecs/umn/en-us_topic_0040863659.html index d3e58c02..96eb2912 100644 --- a/docs/ecs/umn/en-us_topic_0040863659.html +++ b/docs/ecs/umn/en-us_topic_0040863659.html @@ -6,7 +6,7 @@-Parent topic: Managing ECSs+Parent topic: Managing ECS Configurationsdiff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html index 8b0465b6..54477bcd 100644 --- a/docs/ecs/umn/en-us_topic_0041169567.html +++ b/docs/ecs/umn/en-us_topic_0041169567.html @@ -8,7 +8,16 @@ --Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQ2024-08-20
+2024-09-04
+Modified the following content:
+Deleted expired actions in Permissions Management.
+Added I3m ECSs in A Summary List of ECS Specifications and Ultra-high I/O ECSs.
+Added the description about starting and stoping ECSs with physical flavors in Starting and Stopping ECSs.
+Updated the supported OS list in General-Purpose ECSs and Large-Memory ECSs.
+2024-08-20
Added the following content:
@@ -60,7 +69,7 @@2023-09-13
Added the following content:
-- Starting and Stopping ECSs
- Overview
- Dynamically Assigning IPv6 Addresses
- Overview
- Unbinding an EIP
- What Is an AZ?
- Is Data Transmission Between AZs Billed?
- What Should I Do If the ECS Resources to Be Purchased Are Sold Out?
- What Is the Creation Time and Startup Time of an ECS?
- What Do I Do If I Selected an Incorrect Image for My ECS?
- How Can I Manage ECSs by Group?
- Can a Deleted ECS Be Restored?
- How Do I Delete or Restart an ECS?
- What Should I Do If Error Code 1006 or 1000 Is Displayed When I Log In to an ECS Through the Management Console?
- Why No Audio File Can Be Properly Played on My Windows ECS Logged In Using VNC?
- How Can I Change the Resolution of a Windows ECS?
- How Can I Install a GUI on an ECS Running CentOS 6?
- How Can I Install a GUI on an ECS Running CentOS 7?
- How Can I Install a GUI on an ECS Running Ubuntu?
- How Can I Install a GUI on an ECS Running Debian?
- Why Cannot My ECS OS Start Properly?
- How Can I Add an ECS with Local Disks Attached to an ECS Group?
- How Can I Use a Key Pair?
- What Should I Do If I Cannot Download a Key Pair?
- How Can I Configure the NTP and DNS Servers for an ECS?
- Starting and Stopping ECSs
- Overview
- Dynamically Assigning IPv6 Addresses
- Overview
- Unbinding an EIP
- What Is AZ and How Can I Select and View an AZ?
- Is Data Transmission Between AZs Billed?
- What Should I Do If the ECS Resources to Be Purchased Are Sold Out?
- What Is the Creation Time and Startup Time of an ECS?
- What Do I Do If I Selected an Incorrect Image for My ECS?
- How Can I Manage ECSs by Group?
- Can a Deleted ECS Be Restored?
- How Do I Delete or Restart an ECS?
- What Should I Do If Error Code 1006 or 1000 Is Displayed When I Log In to an ECS Through the Management Console?
- Why No Audio File Can Be Properly Played on My Windows ECS Logged In Using VNC?
- How Can I Change the Resolution of a Windows ECS?
- How Can I Install a GUI on an ECS Running CentOS 6?
- How Can I Install a GUI on an ECS Running CentOS 7?
- How Can I Install a GUI on an ECS Running Ubuntu?
- How Can I Install a GUI on an ECS Running Debian?
- Why Cannot My ECS OS Start Properly?
- How Can I Add an ECS with Local Disks Attached to an ECS Group?
- How Can I Use a Key Pair?
- What Should I Do If I Cannot Download a Key Pair?
- How Can I Configure the NTP and DNS Servers for an ECS?
2023-06-27
@@ -97,7 +106,7 @@2022-11-22
Modified the following content:
-Modified operations in General Operations.
+Modified operations in Modifying Individual ECS Specifications.
2022-10-14
@@ -128,7 +137,7 @@2022-04-20
Optimized the content in "Passwords and Key Pairs".
-- Added the following content:
- Application Scenarios for Using Passwords
- Application Scenarios for Using Key Pairs
- Creating a Key Pair Using PuTTYgen
- Importing a Key Pair
- Added the following content:
- Modified the content in (Recommended) Creating a Key Pair on the Management Console.
2020-11-12
Modified the following content:
-- Changed CSBS to CBR in ECS and Other Services.
- Added CBR to back up ECS data in Step 3: Configure Advanced Settings.
- Added CBR to back up ECS data in CBR.
- Added description in notes in Migrating an ECS, indicating that CBR backups are not affected by cold migrations.
- Added a solution of using CBR in Why Does It Take Longer to Create ECSs When I Use a Full-ECS Image?
- Changed CSBS to CBR in ECS and Other Services.
- Added CBR to back up ECS data in Step 3: Configure Advanced Settings.
- Added CBR to back up ECS data in Backup Using CBR.
- Added description in notes in Migrating an ECS to a DeH, indicating that CBR backups are not affected by cold migrations.
- Added a solution of using CBR in Why Does It Take Longer to Create ECSs When I Use a Full-ECS Image?
2020-10-09
@@ -250,13 +259,13 @@Added the following content:
- Added GPU Driver to describe GRID and Tesla drivers.
Modified the following content:
-- Optimized the operations for installing a Tesla driver and CUDA toolkit in Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS.
- Terminated the sections of installing a NVIDIA GPU driver and CUDA toolkit on P1, P2, and P2v ECSs and added Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS for installation.
- Optimized the operations for installing a Tesla driver and CUDA toolkit in Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- Terminated the sections of installing a NVIDIA GPU driver and CUDA toolkit on P1, P2, and P2v ECSs and added Manually Installing a Tesla Driver on a GPU-accelerated ECS for installation.
2019-12-26
Added the following content:
-- Added C4 series in Dedicated General-Purpose ECSs.
- Added M4 series in Memory-optimized ECSs.
- Added newly released E3 ECSs in Large-Memory ECSs.
- Added G6 ECSs in GPU-accelerated ECSs.
- Added P2v ECSs in GPU-accelerated ECSs.
- Added Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS.
- Added C4 series in Dedicated General-Purpose ECSs.
- Added M4 series in Memory-optimized ECSs.
- Added newly released E3 ECSs in Large-Memory ECSs.
- Added G6 ECSs in GPU-accelerated ECSs.
- Added P2v ECSs in GPU-accelerated ECSs.
- Added Manually Installing a Tesla Driver on a GPU-accelerated ECS.
Modified the following content:
- Changing a Xen ECS to a KVM ECS (Windows)
2019-03-06
Modified the following content:
-- Deleted metadata types that are not supported in Obtaining Metadata.
- Added use restrictions in Passing User Data to ECSs.
- Deleted metadata types that are not supported in Obtaining Metadata.
- Added use restrictions in Passing User Data.
2019-03-05
@@ -288,7 +297,7 @@2019-02-25
Modified the following content:
-- Adjusted the format of information display for the step "(Optional) Select the check box to confirm the ECS configuration" in General Operations.
- Adjusted the format of information display for the step "(Optional) Select the check box to confirm the ECS configuration" in Modifying Individual ECS Specifications.
2019-02-22
@@ -302,7 +311,7 @@Added the following content:
Modified the following content:
-- Why Are Certain Flavor Quotas Separately Displayed on the Quota Page?
- Changed the ECS types that support change from Xen to KVM in "Changing a Xen ECS to a KVM ECS (Windows)".
- Changed the ECS types that support changing from Xen to KVM and the command for downloading the driver installation script in "Automatically Changing a Xen ECS to a KVM ECS (Linux)".
- Added description about the impact on ECS backups and IDs after a cold migration in Migrating an ECS.
- Added the information that OTC Tools has been installed for public images in Basic ECS Metrics.
- Why Are Certain Flavor Quotas Separately Displayed on the Quota Page?
- Changed the ECS types that support change from Xen to KVM in "Changing a Xen ECS to a KVM ECS (Windows)".
- Changed the ECS types that support changing from Xen to KVM and the command for downloading the driver installation script in "Automatically Changing a Xen ECS to a KVM ECS (Linux)".
- Added description about the impact on ECS backups and IDs after a cold migration in Migrating an ECS to a DeH.
- Added the information that OTC Tools has been installed for public images in Basic ECS Metrics.
2019-02-13
@@ -326,7 +335,7 @@2019-01-30
Added the following content:
-- Added the FPGA-accelerated ECS type.
- Added Migrating an ECS.
- Added the FPGA-accelerated ECS type.
- Added Migrating an ECS to a DeH.
Modified the following content:
- Changed monitoring metric names in Basic ECS Metrics.
Deleted the following content:
@@ -350,7 +359,7 @@2018-12-12
Modified the following content:
-- Added description in GPU-accelerated ECSs because P1 and P2 ECSs do not support automatic recovery.
- (Optional) Configuring Mapping Between Hostnames and IP Addresses
- Installing a NVIDIA GPU Driver and CUDA Toolkit on a P1 ECS
- Installing a NVIDIA GPU Driver and CUDA Toolkit on a P2 ECS
- Added description in GPU-accelerated ECSs because P1 and P2 ECSs do not support automatic recovery.
- Configuring Mapping Between Hostnames and IP Addresses in the Same VPC
- Installing a NVIDIA GPU Driver and CUDA Toolkit on a P1 ECS
- Installing a NVIDIA GPU Driver and CUDA Toolkit on a P2 ECS
2018-12-10
@@ -404,21 +413,21 @@2018-07-31
Added the following content:
-- Changing the Login Password on an ECS
- Supported advanced disk enablement.
- What Should I Do If Cloud-Init Does Not Work After Python Is Upgraded?
- Why Does the System Display Error Code 0x112f When I Log In to a Windows ECS?
- How Can I Enable Virtual Memory on a Windows ECS?
- Resetting the Password for Logging In to an ECS in the OS
- Supported advanced disk enablement.
- What Should I Do If Cloud-Init Does Not Work After Python Is Upgraded?
- Why Does the System Display Error Code 0x112f When I Log In to a Windows ECS?
- How Can I Enable Virtual Memory on a Windows ECS?
Modified the following content:
-- Modified description in Large-Memory ECSs, Disk-intensive ECSs, and Can I Attach Multiple Disks to an ECS?, allowing an ECS to have up to 60 attached disks.
- Modified description in Overview, allowing the tags added during ECS creation to be automatically added to the created EIP and EVS disks.
- Modified description in CBR and Why Does It Take Longer to Create ECSs When I Use a Full-ECS Image? to support full-ECS images.
- Modified description in Large-Memory ECSs, Disk-intensive ECSs, and Can I Attach Multiple Disks to an ECS?, allowing an ECS to have up to 60 attached disks.
- Modified description in Overview, allowing the tags added during ECS creation to be automatically added to the created EIP and EVS disks.
- Modified description in Backup Using CBR and Why Does It Take Longer to Create ECSs When I Use a Full-ECS Image? to support full-ECS images.
2018-07-03
Modified the following content:
-- Added the rules for the device names of the disks mounted to a disk-intensive ECS in Attaching an EVS Disk to an ECS.
- Added the rules for the device names of the disks mounted to a disk-intensive ECS in Attaching a Disk to an ECS.
2018-07-01
Added the following content:
-- CTS
- How Can I Test the Network Performance of Linux ECSs?
- Why Does an Authentication Failure Occurs After I Attempt to Remotely Log In to a Windows ECS?
- Audit Using CTS
- How Can I Test the Network Performance of Linux ECSs?
- Why Does an Authentication Failure Occurs After I Attempt to Remotely Log In to a Windows ECS?
Modified the following content:
- Allowed to export certain ECSs in Exporting ECS Information.
- Modified prerequisites in Changing the OS, allowing you to change the OS of an ECS on which reinstalling the OS failed.
- Modified description in Changing a Security Group, allowing you to change the security group in the Operation column.
Added the following content:
- Added newly released FPGA-accelerated ECSs.
- Installing a NVIDIA GPU Driver and CUDA Toolkit on a P2 ECS
- Viewing Failed Tasks
Modified the following content:
-- Added newly released D2 ECSs in Disk-intensive ECSs.
- Added newly released P2 ECSs in GPU-accelerated ECSs.
- Modified description in General Operations, allowing you to check whether specifications have been modified.
- Added description in "Automatically Recovering ECSs", allowing KVM ECSs to support automatic recovery.
- Added newly released D2 ECSs in Disk-intensive ECSs.
- Added newly released P2 ECSs in GPU-accelerated ECSs.
- Modified description in Modifying Individual ECS Specifications, allowing you to check whether specifications have been modified.
- Added description in "Automatically Recovering ECSs", allowing KVM ECSs to support automatic recovery.
2018-03-30
@@ -483,7 +492,7 @@Added the following content:
- 6.7.2-Changing a General-Purpose ECS to an H1 ECS
- Installing a NVIDIA GPU Driver and CUDA Toolkit on a P1 ECS
- What Can I Do If Switching from a Non-root User to User root Times Out?
- Why Is the Memory of an ECS Obtained by Running the free Command Inconsistent with the Actual Memory?
Modified the following content:
-- Modified the document structure.
- Allowed to modify specifications between general-purpose (S1, C1, C2, or M1) ECSs and H1 ECSs in General Operations.
- Updated the description and screenshots for selecting ECS types during ECS creation because the GUI has been modified.
- Modified description in Can I Attach Multiple Disks to an ECS?, allowing you to attach up to 60 EVS disks to an ECS.
- Modified default configurations during ECS creation in Overview. Specifically, no built-in tags will be created for an ECS by default.
- Added "Follow-up Procedure" in General Operations.
- Modified the document structure.
- Allowed to modify specifications between general-purpose (S1, C1, C2, or M1) ECSs and H1 ECSs in Modifying Individual ECS Specifications.
- Updated the description and screenshots for selecting ECS types during ECS creation because the GUI has been modified.
- Modified description in Can I Attach Multiple Disks to an ECS?, allowing you to attach up to 60 EVS disks to an ECS.
- Modified default configurations during ECS creation in Overview. Specifically, no built-in tags will be created for an ECS by default.
- Added "Follow-up Procedure" in Modifying Individual ECS Specifications.
2018-01-26
@@ -527,9 +536,9 @@2017-09-30
Added the following content:
-- (Optional) Configuring Mapping Between Hostnames and IP Addresses
- How Can I Adjust System Disk Partitions?
- How Can I Add the Empty Partition of an Expanded System Disk to the End Root Partition Online?
- How Can I Add the Empty Partition of an Expanded System Disk to the Non-end Root Partition Online?
- Which ECSs Can Be Attached with SCSI EVS Disks?
- Configuring Mapping Between Hostnames and IP Addresses in the Same VPC
- How Can I Adjust System Disk Partitions?
- How Can I Add the Empty Partition of an Expanded System Disk to the End Root Partition Online?
- How Can I Add the Empty Partition of an Expanded System Disk to the Non-end Root Partition Online?
- Which ECSs Can Be Attached with SCSI EVS Disks?
Modified the following content:
-- Added S2 ECSs in General-Purpose ECSs.
- Added EVS disk device types in EVS Disks.
- Modified description in Reinstalling the OS and Changing the OS, allowing you to inject user data during ECS OS reinstallation or change.
- Modified the description of managing virtual IP addresses in General Operations.
- Allowed attaching up to 24 EVS disks to an ECS in Can I Attach Multiple Disks to an ECS?
- Added S2 ECSs in General-Purpose ECSs.
- Added EVS disk device types in EVS Disks.
- Modified description in Reinstalling the OS and Changing the OS, allowing you to inject user data during ECS OS reinstallation or change.
- Modified the description of managing virtual IP addresses in Modifying Individual ECS Specifications.
- Allowed attaching up to 24 EVS disks to an ECS in Can I Attach Multiple Disks to an ECS?
2017-09-18
@@ -568,13 +577,13 @@2017-06-05
Modified the following content:
-- Added the description of built-in tags in General Operations.
- Added the description of built-in tags in Modifying Individual ECS Specifications.
2017-05-30
Modified the following content:
-- Changed the OSs supported by large-memory ECSs in Large-Memory ECSs.
- Changed the OSs supported by disk-intensive ECSs in Disk-intensive ECSs.
- Added the InfiniBand NIC status metric in Basic ECS Metrics.
- Added the description of adding, viewing, modifying, and deleting tags in General Operations.
- Changed the OSs supported by large-memory ECSs in Large-Memory ECSs.
- Changed the OSs supported by disk-intensive ECSs in Disk-intensive ECSs.
- Added the InfiniBand NIC status metric in Basic ECS Metrics.
- Added the description of adding, viewing, modifying, and deleting tags in Modifying Individual ECS Specifications.
2017-05-19
@@ -611,7 +620,7 @@Added the following content:
Modified the following content:
-- Modified the method of using puttygen.exe to generate key pairs in Creating a Key Pair Using PuTTYgen.
- Added description in License Types, indicating that the system does not support dynamic license type changing.
- Modified the method of using puttygen.exe to generate key pairs in Creating a Key Pair Using PuTTY Key Generator.
- Added description in License Types, indicating that the system does not support dynamic license type changing.
2017-01-27
@@ -644,7 +653,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 Remotely Logging In to a Windows ECS (Using VNC), Logging In to a Linux ECS Using an SSH Key Pair, Logging In to a Linux ECS Using an SSH Password, and Logging In to a Windows ECS Using MSTSC.
- Added document links to the default keyboard types of the ECSs created using public images in 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.
- Added information for remotely logging in to ECSs in Logging In to a Windows ECS Using VNC, Logging In to a Linux ECS Using an SSH Key Pair, Logging In to a Linux ECS Using an SSH Password, and Logging In to a Windows ECS Using MSTSC.
- Added document links to the default keyboard types of the ECSs created using public images in Logging In to a Windows ECS Using VNC.
- Added notes on keyboard language settings for VNC-based ECS logins and the mapping between four types of keyboards in Logging In to a Windows ECS Using VNC. Provided configuration examples and links to related FAQs.
2016-09-30
@@ -666,13 +675,13 @@Added the following content:
Modified the following content:
-- Modified the instructions for configuring keyboard languages in VNC logins in Remotely Logging In to a Windows ECS (Using VNC).
- Modified the instructions for configuring keyboard languages in VNC logins in Logging In to a Windows ECS Using VNC.
2016-09-26
Modified the following content:
-- Added the instructions for configuring keyboard languages in VNC logins in Remotely Logging In to a Windows ECS (Using VNC).
- Added the instructions for configuring keyboard languages in VNC logins in Logging In to a Windows ECS Using VNC.
2016-09-23
@@ -680,7 +689,7 @@Added the following content:
Modified the following content:
-- Added encryption algorithms and the method of using PuTTYgen to generate key pairs in Creating a Key Pair Using PuTTYgen.
- Added encryption algorithms and the method of using PuTTYgen to generate key pairs in Creating a Key Pair Using PuTTY Key Generator.
2016-09-18
@@ -694,7 +703,7 @@2016-08-25
Added the following content:
-- GPU-accelerated ECSs
- Disk-intensive ECSs
- Why Is the NIC Not Working?
- High-Performance Computing ECSs
- Detaching an EVS Disk from a Running ECS
- What Browser Version Is Required to Remotely Log In to an ECS?
- Why Does the Login to My Linux ECS Using a Key File Fail?
- Why Does the System Display a Message Indicating that the Password for Logging In to a Windows ECS Cannot Be Obtained?
- GPU-accelerated ECSs
- Disk-intensive ECSs
- Why Is the NIC Not Working?
- High-Performance Computing ECSs
- Detaching an EVS Disk from a Running ECS
- What Browser Version Is Required to Remotely Log In to an ECS?
- Why Does the Login to My Linux ECS Using a Key File Fail?
- Why Does the System Display a Message Indicating that the Password for Logging In to an ECS Cannot Be Obtained?
2016-07-15
diff --git a/docs/ecs/umn/en-us_topic_0042400609.html b/docs/ecs/umn/en-us_topic_0042400609.html index f8a08475..4df65b00 100644 --- a/docs/ecs/umn/en-us_topic_0042400609.html +++ b/docs/ecs/umn/en-us_topic_0042400609.html @@ -48,7 +48,7 @@/user_data
Displays ECS user data.
-This metadata allows you to specify scripts and configuration files for initializing ECSs. For details, see Passing User Data to ECSs.
+This metadata allows you to specify scripts and configuration files for initializing ECSs. For details, see Passing User Data.
For password-authenticated Linux ECSs, this metadata is used to save password injection scripts.
- After disabling a CMK or scheduling the deletion of a CMK takes effect, the EVS disk encrypted using this CMK can still be used until the disk is detached from and then attached to an ECS again. During this process, the disk fails to be attached to the ECS because the CMK cannot be obtained, so the EVS disk becomes unavailable.
For details about KMS, see Key Management Service User Guide.
+For details about KMS, see Key Management Service User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0047272493.html b/docs/ecs/umn/en-us_topic_0047272493.html index a645020a..1a4f005a 100644 --- a/docs/ecs/umn/en-us_topic_0047272493.html +++ b/docs/ecs/umn/en-us_topic_0047272493.html @@ -23,7 +23,7 @@diff --git a/docs/ecs/umn/en-us_topic_0047624368.html b/docs/ecs/umn/en-us_topic_0047624368.html index 87b19e1e..ff29cfea 100644 --- a/docs/ecs/umn/en-us_topic_0047624368.html +++ b/docs/ecs/umn/en-us_topic_0047624368.html @@ -6,7 +6,7 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQdiff --git a/docs/ecs/umn/en-us_topic_0047654687.html b/docs/ecs/umn/en-us_topic_0047654687.html index c9ed8701..fa0e3ade 100644 --- a/docs/ecs/umn/en-us_topic_0047654687.html +++ b/docs/ecs/umn/en-us_topic_0047654687.html @@ -16,7 +16,7 @@-Parent topic: Logins Through the Management Console+Parent topic: VNC Logindiff --git a/docs/ecs/umn/en-us_topic_0048642616.html b/docs/ecs/umn/en-us_topic_0048642616.html index 2a5a503d..101f9d37 100644 --- a/docs/ecs/umn/en-us_topic_0048642616.html +++ b/docs/ecs/umn/en-us_topic_0048642616.html @@ -9,10 +9,10 @@-Parent topic: Passwords and Key Pairs+Parent topic: Password and Key Pair FAQAfter being installed in an image, Cloud-Init or Cloudbase-Init automatically configures initial attributes for the ECSs created using this image.
For more information, see Image Management Service User Guide.
-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:
- Login Overview (Linux)
- What Is the Cloudbase-Init Account in Windows ECSs Used for?
- Why Does the Login to My Linux ECS Using a Key File Fail?
- Why Does the System Display a Message Indicating that the Password for Logging In to a Windows ECS Cannot Be Obtained?
-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.
- If Cloud-Init is supported, ECSs do not support password authentication anymore. All newly created ECSs use key pair authentication. This change will influence your ECS logins. For details, see the following sections:
- If Cloud-Init is supported, you can view and use metadata to configure and manage running ECSs. For details, see Obtaining Metadata.
Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
+Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
Notes
- When using Cloud-Init, enable DHCP in the VPC which the ECS belongs to.
- When using Cloud-Init, ensure that security group rules for the outbound direction meet the following requirements:
- Protocol: TCP
- Port: 80
- Destination: 169.254.0.0/16
Modifying the Mapping Between the ECS Hostname and IP Address (Modifying the hosts File)
If you want to use the changed hostname as the preferred localhost and localhost.localdomain, update the mapping between the hostname and IP address after the hostname is changed and then save the configuration to the corresponding Cloud-Init configuration file so that the new hostname takes effect permanently.
The changed hostname is assumed to be new_hostname.
-- Modify the /etc/hostname configuration file.
- Run the following command to edit the configuration file:
+
- Modify the /etc/hostname configuration file. -
- Modify the /etc/sysconfig/network configuration file.
- Run the following command to edit the configuration file: -
- Change the HOSTNAME value to the new hostname.
HOSTNAME=Changed hostname
- If there is no HOSTNAME in the configuration file, manually add this parameter and set it to the changed hostname.
+- Modify the /etc/sysconfig/network configuration file.
- Run the following command to edit the configuration file: +
- Change the HOSTNAME value to the new hostname.
HOSTNAME=Changed hostname
+ If there is no HOSTNAME in the configuration file, manually add this parameter and set it to the changed hostname.
For example:
HOSTNAME=new_hostname
- Run the following command to save and exit the configuration file:
- Modify the /etc/cloud/cloud.cfg configuration file.
- Run the following command to edit the configuration file: -
- Use either of the following methods to modify the configuration file:
- Method 1: Change the preserve_hostname parameter value or add the preserve_hostname parameter to the configuration file.
If preserve_hostname: false is already available in the /etc/cloud/cloud.cfg configuration file, change it to preserve_hostname: true. If preserve_hostname is unavailable in the /etc/cloud/cloud.cfg configuration file, add preserve_hostname: true before cloud_init_modules.
-If you use method 1, the changed hostname still takes effect after the ECS is stopped or restarted. However, if the ECS is used to create a private image and the image is used to create a new ECS, the hostname of the new ECS is the hostname (new_hostname) used by the private image, and user-defined hostnames cannot be injected using Cloud-Init.
- - Method 2 (recommended): Delete or comment out - update_hostname.
If you use method 2, the changed hostname still takes effect after the ECS is stopped or restarted. If the ECS is used to create a private image and the image is used to create a new ECS, the changed hostname permanently takes effect, and user-defined hostnames (such as new_new_hostname) can be injected using Cloud-Init.
+ - Modify the /etc/cloud/cloud.cfg configuration file.
- Run the following command to edit the configuration file: +
- Use either of the following methods to modify the configuration file:
- Method 1: Change the preserve_hostname parameter value or add the preserve_hostname parameter to the configuration file.
If preserve_hostname: false is already available in the /etc/cloud/cloud.cfg configuration file, change it to preserve_hostname: true. If preserve_hostname is unavailable in the /etc/cloud/cloud.cfg configuration file, add preserve_hostname: true before cloud_init_modules.
+If you use method 1, the changed hostname still takes effect after the ECS is stopped or restarted. However, if the ECS is used to create a private image and the image is used to create a new ECS, the hostname of the new ECS is the hostname (new_hostname) used by the private image, and user-defined hostnames cannot be injected using Cloud-Init.
+ - Method 2 (recommended): Delete or comment out - update_hostname.
If you use method 2, the changed hostname still takes effect after the ECS is stopped or restarted. If the ECS is used to create a private image and the image is used to create a new ECS, the changed hostname permanently takes effect, and user-defined hostnames (such as new_new_hostname) can be injected using Cloud-Init.
- Method 1: Change the preserve_hostname parameter value or add the preserve_hostname parameter to the configuration file.
- Method 1: Change the preserve_hostname parameter value or add the preserve_hostname parameter to the configuration file.
- Update the mapping between the hostname and IP address in /etc/hosts to an entry starting with 127.0.0.1. Use new_hostname as your preferred localhost and localhost.localdomain. -
- Modify the /etc/cloud/cloud.cfg configuration file.
- Run the following command to edit the configuration file: +
- Modify the /etc/cloud/cloud.cfg configuration file. @@ -65,7 +65,7 @@
diff --git a/docs/ecs/umn/en-us_topic_0053287548.html b/docs/ecs/umn/en-us_topic_0053287548.html index 3a6a369e..fd264e51 100644 --- a/docs/ecs/umn/en-us_topic_0053287548.html +++ b/docs/ecs/umn/en-us_topic_0053287548.html @@ -13,7 +13,7 @@-Parent topic: Usage Errors+Parent topic: ECS Failure FAQdiff --git a/docs/ecs/umn/en-us_topic_0057711189.html b/docs/ecs/umn/en-us_topic_0057711189.html index 352de04c..cd81de78 100644 --- a/docs/ecs/umn/en-us_topic_0057711189.html +++ b/docs/ecs/umn/en-us_topic_0057711189.html @@ -43,7 +43,7 @@-Parent topic: Network Configurations+Parent topic: Network Configuration FAQ - Modify the /etc/sysconfig/network configuration file.
- Run the following command to edit the configuration file:
+
diff --git a/docs/ecs/umn/en-us_topic_0058758453.html b/docs/ecs/umn/en-us_topic_0058758453.html index 412fd82d..589b2a2d 100644 --- a/docs/ecs/umn/en-us_topic_0058758453.html +++ b/docs/ecs/umn/en-us_topic_0058758453.html @@ -1,7 +1,7 @@-Parent topic: Managing ECSs+Parent topic: Managing ECS ConfigurationsEnabling 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 packets per second (PPS) and I/O performance.
+Scenarios
With the increase of network I/O bandwidth, single-core CPUs face bottlenecks in handling network interrupts. NIC multi-queue assigns interrupts to different CPUs for higher packets per second (PPS) and bandwidth.
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,13 +146,13 @@
- An ECS that is being created is in one of the following states:
Importing the External Image File to the IMS Console
For details, see "Registering an Image File as a Private Image" in Image Management Service User Guide.
+Importing the External Image File to the IMS Console
For details, see "Registering an Image File as a Private Image" in Image Management Service User Guide.
Setting NIC Multi-Queue for the Image
Windows OSs have not commercially supported NIC multi-queue. If you enable NIC multi-queue in a Windows image, starting an ECS created using such an image may be slow.
Use one of the following methods to set the NIC multi-queue attribute:
-Method 1:-- Log in to the management console.
- Under Computing, click Image Management Service.
- Click the Private Images tab, locate the row containing the target image, click Modify in the Operation column.
- Set the NIC multi-queue attribute of the image.
Method 1:-- Log in to the management console.
- Under Computing, click Image Management Service.
- Click the Private Images tab, locate the row containing the target image, click Modify in the Operation column.
- Set the NIC multi-queue attribute of the image.
Method 2:diff --git a/docs/ecs/umn/en-us_topic_0072987316.html b/docs/ecs/umn/en-us_topic_0072987316.html index be33c224..9ff42072 100644 --- a/docs/ecs/umn/en-us_topic_0072987316.html +++ b/docs/ecs/umn/en-us_topic_0072987316.html @@ -1,6 +1,6 @@ -- Log in to the management console.
- Under Computing, click Image Management Service.
- Click the Private Images tab. In the image list, click the name of the target image to switch to the page providing details about the image.
- Click Modify in the upper right corner. In the displayed Modify Image dialog box, set the NIC multi-queue attribute.
Method 2:- Log in to the management console.
- Under Computing, click Image Management Service.
- Click the Private Images tab. In the image list, click the name of the target image to switch to the page providing details about the image.
- Click Modify in the upper right corner. In the displayed Modify Image dialog box, set the NIC multi-queue attribute.
Method 3: Add hw_vif_multiqueue_enabled to an image through the API.
- For instructions about how to obtain the token, see Token Authentication.
- For instructions about how to call an API to update image information, see "Updating Image Information (Native OpenStack API)" in Image Management Service API Reference.
- Add X-Auth-Token to the request header.
The value of X-Auth-Token is the token obtained in step 1.
@@ -273,7 +273,7 @@ done
Monitoring
+Monitoring Using Cloud Eye
-
diff --git a/docs/ecs/umn/en-us_topic_0074752335.html b/docs/ecs/umn/en-us_topic_0074752335.html
index 07795381..1c3bea5e 100644
--- a/docs/ecs/umn/en-us_topic_0074752335.html
+++ b/docs/ecs/umn/en-us_topic_0074752335.html
@@ -1,6 +1,6 @@
-
- Run the service ntp stop command to stop NTP.
- Run the systemctl disable ntp command to disable the function of automatically starting NTP upon ECS startup.
(Optional) Configuring Mapping Between Hostnames and IP Addresses
+Configuring Mapping Between Hostnames and IP Addresses in the Same VPC
ECSs in the same VPC can communicate with each other using hostnames. In such a case, you are required to configure the mapping between hostnames and IP addresses. The communication using hostnames is more convenient than that using IP addresses.
@@ -29,7 +29,7 @@Constraints
This method applies only to Linux ECSs.
diff --git a/docs/ecs/umn/en-us_topic_0074825901.html b/docs/ecs/umn/en-us_topic_0074825901.html index 373d7086..3ade6467 100644 --- a/docs/ecs/umn/en-us_topic_0074825901.html +++ b/docs/ecs/umn/en-us_topic_0074825901.html @@ -14,8 +14,8 @@-Parent topic: Managing ECSs+Parent topic: Managing ECS Configurations- Configure the DNS server for the ECS.
- Log in to the Linux ECS.
- Run the following command to switch to user root:
sudo su -
- - Run the following command to edit the resolv.conf configuration file:
vi /etc/resolv.conf
+ - Configure the DNS server for the ECS.
- Log in to the Linux ECS.
- Run the following command to switch to user root:
sudo su -
+ - Run the following command to edit the resolv.conf configuration file:
vi /etc/resolv.conf
- Add the following statement to configure the DNS server:
nameserver = IP addresses of the DNS servers
Example:
If the IP addresses of the DNS servers are 8.8.8.8 and 4.4.4.4, add the following statements:
@@ -45,7 +45,7 @@
diff --git a/docs/ecs/umn/en-us_topic_0076210995.html b/docs/ecs/umn/en-us_topic_0076210995.html index c670a32a..7c436162 100644 --- a/docs/ecs/umn/en-us_topic_0076210995.html +++ b/docs/ecs/umn/en-us_topic_0076210995.html @@ -102,7 +102,7 @@ Writing superblocks and filesystem accounting information: done-Parent topic: Network Configurations+Parent topic: Network Configuration FAQdiff --git a/docs/ecs/umn/en-us_topic_0077938284.html b/docs/ecs/umn/en-us_topic_0077938284.html index 69486354..bcffb236 100644 --- a/docs/ecs/umn/en-us_topic_0077938284.html +++ b/docs/ecs/umn/en-us_topic_0077938284.html @@ -5,7 +5,7 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQdiff --git a/docs/ecs/umn/en-us_topic_0078300749.html b/docs/ecs/umn/en-us_topic_0078300749.html index 1a9f2714..f84638c4 100644 --- a/docs/ecs/umn/en-us_topic_0078300749.html +++ b/docs/ecs/umn/en-us_topic_0078300749.html @@ -44,7 +44,7 @@ old_desc_blocks = 3, new_desc_blocks = 3-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQdiff --git a/docs/ecs/umn/en-us_topic_0078300750.html b/docs/ecs/umn/en-us_topic_0078300750.html index 1671c549..651d0ad7 100644 --- a/docs/ecs/umn/en-us_topic_0078300750.html +++ b/docs/ecs/umn/en-us_topic_0078300750.html @@ -111,7 +111,7 @@ old_desc_blocks = 3, new_desc_blocks = 3-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQdiff --git a/docs/ecs/umn/en-us_topic_0079176727.html b/docs/ecs/umn/en-us_topic_0079176727.html index 5880a49c..bbd92f21 100644 --- a/docs/ecs/umn/en-us_topic_0079176727.html +++ b/docs/ecs/umn/en-us_topic_0079176727.html @@ -16,7 +16,7 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQdiff --git a/docs/ecs/umn/en-us_topic_0081525053.html b/docs/ecs/umn/en-us_topic_0081525053.html index 3999e63f..7f8f6e23 100644 --- a/docs/ecs/umn/en-us_topic_0081525053.html +++ b/docs/ecs/umn/en-us_topic_0081525053.html @@ -10,7 +10,7 @@-Parent topic: Passwords and Key Pairs+Parent topic: Password and Key Pair FAQdiff --git a/docs/ecs/umn/en-us_topic_0085634796.html b/docs/ecs/umn/en-us_topic_0085634796.html index a93fbf04..9ccb28fc 100644 --- a/docs/ecs/umn/en-us_topic_0085634796.html +++ b/docs/ecs/umn/en-us_topic_0085634796.html @@ -7,7 +7,7 @@-Parent topic: Passwords and Key Pairs+Parent topic: Password and Key Pair FAQ- When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
-Procedure
- On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.
The Server Manager window is displayed.
diff --git a/docs/ecs/umn/en-us_topic_0085634797.html b/docs/ecs/umn/en-us_topic_0085634797.html index c8340a89..aeeff9a2 100644 --- a/docs/ecs/umn/en-us_topic_0085634797.html +++ b/docs/ecs/umn/en-us_topic_0085634797.html @@ -8,7 +8,7 @@ When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
-Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
-Creating and Mounting a Partition
The following example shows you how a new primary partition can be created on a new data disk that has been attached to a server. The primary partition will be created using fdisk, and MBR will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured to mount automatically at startup.
@@ -69,8 +69,8 @@ First sector (2048-209715199, default 2048): Using default value 2048 Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):Last sector indicates the end sector. The value ranges from 2048 to 209715199, and the default value is 209715199.
- - Select the default end sector 209715199 and press Enter.
The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.
+Last sector indicates the end sector. The value ranges from 2048 to 209715199, and the default value is 209715199.
+ - Select the default end sector 209715199 and press Enter.
The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.
Information similar to the following is displayed:
Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199): Using default value 209715199 diff --git a/docs/ecs/umn/en-us_topic_0085634798.html b/docs/ecs/umn/en-us_topic_0085634798.html index 7f8da5ec..8e4c8a34 100644 --- a/docs/ecs/umn/en-us_topic_0085634798.html +++ b/docs/ecs/umn/en-us_topic_0085634798.html @@ -8,7 +8,7 @@ When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Creating and Mounting a Partition
The following example shows you how a new partition can be created on a new data disk that has been attached to a server. The partition will be created using parted, and GPT will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured to mount automatically at startup.
@@ -143,8 +143,8 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0- After the server is restarted, the disk will not be automatically mounted. You can modify the /etc/fstab file to configure automount at startup. For details, see Configuring Automatic Mounting at System Start.
Configuring Automatic Mounting at System Start
The fstab file controls what disks are automatically mounted at server startup. You can configure the fstab file of a server that has data. This operation will not affect the existing data.
-The following example uses UUIDs to identify disks in the fstab file. You are advised not to use device names (like /dev/vdb1) to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after a server stop or start. This can even prevent your server from booting up.
+Configuring Automatic Mounting at System Start
The fstab file controls what disks are automatically mounted at ECS startup. You can configure the fstab file of an ECS that has data. This operation will not affect the existing data.
+The following example uses UUIDs to identify disks in the fstab file. You are advised not to use device names (like /dev/vdb1) to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after an ECS stop or start. This can even prevent your ECS from booting up.
UUIDs are the unique character strings for identifying partitions in Linux.
- Query the partition UUID.
blkid Disk partition
diff --git a/docs/ecs/umn/en-us_topic_0087382187.html b/docs/ecs/umn/en-us_topic_0087382187.html index 25b62561..2debfdfd 100644 --- a/docs/ecs/umn/en-us_topic_0087382187.html +++ b/docs/ecs/umn/en-us_topic_0087382187.html @@ -21,7 +21,7 @@ lrwxrwxrwx 1 root root 9 Dec 6 11:26 wwn-0x688860300001436b005014f890338280 -&
diff --git a/docs/ecs/umn/en-us_topic_0087622835.html b/docs/ecs/umn/en-us_topic_0087622835.html index 2c6d16d6..26b7a226 100644 --- a/docs/ecs/umn/en-us_topic_0087622835.html +++ b/docs/ecs/umn/en-us_topic_0087622835.html @@ -18,7 +18,7 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQdiff --git a/docs/ecs/umn/en-us_topic_0087680813.html b/docs/ecs/umn/en-us_topic_0087680813.html index 7754cdb6..c64c0b8c 100644 --- a/docs/ecs/umn/en-us_topic_0087680813.html +++ b/docs/ecs/umn/en-us_topic_0087680813.html @@ -142,7 +142,7 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQdiff --git a/docs/ecs/umn/en-us_topic_0087901488.html b/docs/ecs/umn/en-us_topic_0087901488.html index a24b308d..511ec6bc 100644 --- a/docs/ecs/umn/en-us_topic_0087901488.html +++ b/docs/ecs/umn/en-us_topic_0087901488.html @@ -140,7 +140,7 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQ
diff --git a/docs/ecs/umn/en-us_topic_0088241338.html b/docs/ecs/umn/en-us_topic_0088241338.html index f63ae9e4..e1bd6326 100644 --- a/docs/ecs/umn/en-us_topic_0088241338.html +++ b/docs/ecs/umn/en-us_topic_0088241338.html @@ -12,7 +12,7 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQ
diff --git a/docs/ecs/umn/en-us_topic_0091224748.html b/docs/ecs/umn/en-us_topic_0091224748.html index 5bc96b9c..542ee265 100644 --- a/docs/ecs/umn/en-us_topic_0091224748.html +++ b/docs/ecs/umn/en-us_topic_0091224748.html @@ -1041,27 +1041,27 @@-Parent topic: Usage Errors+Parent topic: ECS Failure FAQCentOS
- CentOS Stream 8.6 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
- CentOS Stream 9.6 64bit
- CentOS Stream 8.6 64bit
- CentOS 8.5 64bit
- CentOS 8.4 64bit
- CentOS 8.3 64bit
- CentOS 8.2 64bit
- CentOS 8.1 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
Debian
- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
- Debian GNU/Linux 12.0.0 64bit
- Debian GNU/Linux 11.7.0 64bit
- Debian GNU/Linux 11.6.0 64bit
- Debian GNU/Linux 11.5.0 64bit
- Debian GNU/Linux 11.4.0 64bit
- Debian GNU/Linux 11.3.0 64bit
- Debian GNU/Linux 11.2.0 64bit
- Debian GNU/Linux 11.1.0 64bit
- Debian GNU/Linux 11.0.0 64bit
- Debian GNU/Linux 10.13.0 64bit
- Debian GNU/Linux 10.12.0 64bit
- Debian GNU/Linux 10.11.0 64bit
- Debian GNU/Linux 10.10.0 64bit
- Debian GNU/Linux 10.9.0 64bit
- Debian GNU/Linux 10.8.0 64bit
- Debian GNU/Linux 10.7.0 64bit
- Debian GNU/Linux 10.6.0 64bit
- Debian GNU/Linux 10.5.0 64bit
- Debian GNU/Linux 10.4.0 64bit
- Debian GNU/Linux 10.3.0 64bit
- Debian GNU/Linux 10.2.0 64bit
- Debian GNU/Linux 10.1.0 64bit
- Debian GNU/Linux 10 64bit
EulerOS
EulerOS 2.5 64bit
+- EulerOS 2.12 64bit
- EulerOS 2.11 64bit
- EulerOS 2.10 64bit
- EulerOS 2.8 64bit
- EulerOS 2.7 64bit
- EulerOS 2.5 64bit
Fedora
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 39 64bit
- Fedora 38 64bit
- Fedora 37 64bit
- Fedora 36 64bit
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 32 64bit
- Fedora 31 64bit
OpenSUSE
OpenSUSE 15.3 64bit
+- OpenSUSE 15.5 64bit
- OpenSUSE 15.4 64bit
- OpenSUSE 15.3 64bit
- OpenSUSE 15.2 64bit
Oracle Linux
@@ -1071,32 +1071,32 @@Red Hat
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
- Red Hat Enterprise Linux 9.1 64bit
- Red Hat Enterprise Linux 9.0 64bit
- Red Hat Enterprise Linux 8.7 64bit
- Red Hat Enterprise Linux 8.6 64bit
- Red Hat Enterprise Linux 8.5 64bit
- Red Hat Enterprise Linux 8.4 64bit
- Red Hat Enterprise Linux 8.3 64bit
- Red Hat Enterprise Linux 8.2 64bit
- Red Hat Enterprise Linux 8.1 64bit
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
Rocky
Rocky 8 64bit
+- 9.2 64bit
- 9.1 64bit
- 9.0 64bit
- 8.8 64bit
- 8.7 64bit
- 8.6 64bit
- 8.5 64bit
- 8.4 64bit
- 8.3 64bit
- 8 64bit
SUSE
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP5 64bit
- Novell SUSE Linux Enterprise Server 15 SP4 64bit
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 22.04 Server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2022 Standard 64bit
- Windows Server 2022 Datacenter 64bit
- Windows Server 2019 Datacenter 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
openEuler
openEuler 20.03 64bit
+- openEuler 22.03 SP1 64bit
- openEuler 22.03 64bit
- openEuler 20.03 SP3 64bit
- openEuler 20.03 SP2 64bit
- openEuler 20.03 SP1 64bit
- openEuler 20.03 64bit
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 Remotely Logging In to a Windows ECS (Using VNC).
+ - Select a login method and log in to the ECS.
- Management console (VNC)
For details, see Logging In to a Windows ECS Using VNC.
- Remote desktop connection (MSTSC)
For details, see Logging In to a Windows ECS Using MSTSC.
- Management console (VNC)
- Management console (VNC)
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 Remotely Logging In to a Linux ECS (Using VNC).
+Select a login method and log in to the ECS.- VNC
For details, see 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 Logging In to a Linux ECS Using an SSH Key Pair.
Windows
Through the management console.
-For details, see Remotely Logging In to a Windows ECS (Using VNC).
+For details, see Logging In to a Windows ECS Using VNC.
No EIP is required.
NIC
+NICs
diff --git a/docs/ecs/umn/en-us_topic_0092499768.html b/docs/ecs/umn/en-us_topic_0092499768.html index 787f5797..8c692427 100644 --- a/docs/ecs/umn/en-us_topic_0092499768.html +++ b/docs/ecs/umn/en-us_topic_0092499768.html @@ -7,7 +7,7 @@-After creating the ECS, you can view the tags on the pages providing details about the ECS, EIP, and EVS disks.
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).
+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, usage, 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.
diff --git a/docs/ecs/umn/en-us_topic_0092499770.html b/docs/ecs/umn/en-us_topic_0092499770.html index 5f46bfa4..70e3de1f 100644 --- a/docs/ecs/umn/en-us_topic_0092499770.html +++ b/docs/ecs/umn/en-us_topic_0092499770.html @@ -1,13 +1,13 @@ -EVS Disks
+Disks
- Overview
- - Attaching an EVS Disk to an ECS
+ - Attaching a Disk to an ECS
- Detaching an EVS Disk from a Running ECS
diff --git a/docs/ecs/umn/en-us_topic_0093153741.html b/docs/ecs/umn/en-us_topic_0093153741.html
index 43896438..cd60f304 100644
--- a/docs/ecs/umn/en-us_topic_0093153741.html
+++ b/docs/ecs/umn/en-us_topic_0093153741.html
@@ -58,7 +58,7 @@ Configured Voltage: Unknown
diff --git a/docs/ecs/umn/en-us_topic_0093263550.html b/docs/ecs/umn/en-us_topic_0093263550.html index a7307243..d721c9c9 100644 --- a/docs/ecs/umn/en-us_topic_0093263550.html +++ b/docs/ecs/umn/en-us_topic_0093263550.html @@ -1,6 +1,6 @@ --Parent topic: Usage Errors+Parent topic: ECS Failure FAQRemotely Logging In to a Linux ECS (Using VNC)
+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.
Adding a NIC
-Scenarios
If your ECS requires multiple network interfaces (NICs), you can add them to your ECS.
+Scenarios
If your ECS requires multiple network interfaces, you can add them to your ECS.
diff --git a/docs/ecs/umn/en-us_topic_0093492519.html b/docs/ecs/umn/en-us_topic_0093492519.html index 5b41970e..8115e97c 100644 --- a/docs/ecs/umn/en-us_topic_0093492519.html +++ b/docs/ecs/umn/en-us_topic_0093492519.html @@ -1,19 +1,19 @@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.
- Click the name of the target ECS.
The page providing details about the ECS is displayed.
- On the NICs tab, click Add NIC.
- Set the subnet and security group for the NIC to be added.Figure 1 Configuring the subnet and security group@@ -27,7 +27,7 @@
Deleting a NIC
-diff --git a/docs/ecs/umn/en-us_topic_0094118976.html b/docs/ecs/umn/en-us_topic_0094118976.html index 93b4b9d6..ddf503a3 100644 --- a/docs/ecs/umn/en-us_topic_0094118976.html +++ b/docs/ecs/umn/en-us_topic_0094118976.html @@ -6,218 +6,341 @@Scenarios
An ECS can have up to 12 network interfaces, including one primary network interface that cannot be deleted and extension network interfaces. This section describes how to delete a network interface.
+diff --git a/docs/ecs/umn/en-us_topic_0093492522.html b/docs/ecs/umn/en-us_topic_0093492522.html index 3e8db7b5..800850ee 100644 --- a/docs/ecs/umn/en-us_topic_0093492522.html +++ b/docs/ecs/umn/en-us_topic_0093492522.html @@ -15,7 +15,7 @@Scenarios
An ECS can have up to 12 NICs, including one primary NIC that cannot be deleted. This section describes how to delete an extension NIC.
diff --git a/docs/ecs/umn/en-us_topic_0093492521.html b/docs/ecs/umn/en-us_topic_0093492521.html index 3dac9f36..3d91d77a 100644 --- a/docs/ecs/umn/en-us_topic_0093492521.html +++ b/docs/ecs/umn/en-us_topic_0093492521.html @@ -8,7 +8,7 @@Procedure
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, click the name of the target ECS.
The page providing details about the ECS is displayed.
- Click the NICs tab. Then, click Delete in the row of the target network interface.-
You are not allowed to delete the primary ECS network interface. By default, the primary ECS network interface is the first network interface displayed in the network interface list.
- In the displayed dialog box, click OK.diff --git a/docs/ecs/umn/en-us_topic_0093492520.html b/docs/ecs/umn/en-us_topic_0093492520.html index 51f201b1..127f5e73 100644 --- a/docs/ecs/umn/en-us_topic_0093492520.html +++ b/docs/ecs/umn/en-us_topic_0093492520.html @@ -12,7 +12,7 @@
Certain ECSs do not support network interface deletion when they are running. For details, see the GUI display. To delete a network interface from such an ECS, stop the ECS first.
+- In the displayed dialog box, click OK.
Certain ECSs do not support NIC deletion when they are running. For details, see the GUI display. To delete a NIC from such an ECS, stop the ECS first.
- In the displayed dialog box, click OK.
Scenarios
- Ultra-high I/O ECSs are suitable for high-performance relational databases.
- Ultra-high I/O ECSs are suitable for NoSQL databases (such as Cassandra and MongoDB) and ElasticSearch.
Specifications
-Table 1 I3 ECS specifications Flavor
++ +
+Table 1 I3m ECS specifications Flavor
vCPUs
+vCPUs
Memory
-(GiB)
+Memory
+(GiB)
Max./Assured Bandwidth
-(Gbit/s)
+Max./Assured Bandwidth
+(Gbit/s)
Max. PPS
-(10,000)
+Max. PPS
+(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Local Disks
+(GiB)
Local Disks
-(GiB)
+Max. NICs
Virtualization
+Virtualization
i3.2xlarge.4
+i3m.2xlarge.8
8
+8
32
+64
15/4.5
+2.5/2.5
150
+100
4
+4
4
+1 × 1,600 GiB NVMe
1 × 3,200 GiB NVMe
+4
KVM
+KVM
i3.4xlarge.4
+i3m.4xlarge.8
16
+16
64
+128
20/9
+5/5
280
+150
8
+4
8
+2 × 1,600 GiB NVMe
2 × 3,200 GiB NVMe
+8
KVM
+KVM
i3.8xlarge.4
+i3m.8xlarge.8
32
+32
128
+256
30/18
+10/10
550
+200
16
+8
8
+4 × 1,600 GiB NVMe
4 × 3,200 GiB NVMe
+8
KVM
+KVM
i3.12xlarge.4
+i3m.12xlarge.8
48
+48
192
+384
35/27
+15/15
750
+240
16
+8
8
+6 × 1,600 GiB NVMe
6 × 3,200 GiB NVMe
+8
KVM
+KVM
i3.16xlarge.4
+i3m.16xlarge.8
64
+64
256
+512
40/32
+25/25
1,000
+500
32
+16
8
+8 × 1,600 GiB NVMe
8 × 3,200 GiB NVMe
+8
KVM
+KVM
i3.2xlarge.8
+Table 2 I3 ECS specifications Flavor
+vCPUs
+Memory
+(GiB)
+Max./Assured Bandwidth
+(Gbit/s)
+Max. PPS
+(10,000)
+Max. NIC Queues
+Max. NICs
+Local Disks
+(GiB)
+Virtualization
+i3.2xlarge.4
8
+8
64
+32
15/4.5
+15/4.5
150
+150
4
+4
4
+4
1 × 3,200 GiB NVMe
+1 × 3,200 GiB NVMe
KVM
+KVM
i3.4xlarge.8
+i3.4xlarge.4
16
+16
128
+64
20/9
+20/9
280
+280
8
+8
8
+8
2 × 3,200 GiB NVMe
+2 × 3,200 GiB NVMe
KVM
+KVM
i3.8xlarge.8
+i3.8xlarge.4
32
+32
256
+128
30/18
+30/18
550
+550
16
+16
8
+8
4 × 3,200 GiB NVMe
+4 × 3,200 GiB NVMe
KVM
+KVM
i3.12xlarge.8
+i3.12xlarge.4
48
+48
384
+192
35/27
+35/27
750
+750
16
+16
8
+8
6 × 3,200 GiB NVMe
+6 × 3,200 GiB NVMe
KVM
+KVM
i3.16xlarge.8
+i3.16xlarge.4
64
+64
512
+256
40/32
+40/32
1,000
+1,000
32
+32
8
+8
8 × 3,200 GiB NVMe
+8 × 3,200 GiB NVMe
KVM
+KVM
+i3.2xlarge.8
+8
+64
+15/4.5
+150
+4
+4
+1 × 3,200 GiB NVMe
+KVM
+i3.4xlarge.8
+16
+128
+20/9
+280
+8
+8
+2 × 3,200 GiB NVMe
+KVM
+i3.8xlarge.8
+32
+256
+30/18
+550
+16
+8
+4 × 3,200 GiB NVMe
+KVM
+i3.12xlarge.8
+48
+384
+35/27
+750
+16
+8
+6 × 3,200 GiB NVMe
+KVM
+i3.16xlarge.8
+64
+512
+40/32
+1,000
+32
+8
+8 × 3,200 GiB NVMe
+KVM
Local Disk Performance
-Table 2 and Table 3 list the IOPS performance of local disks and specifications of a single local disk attached to an I3 ECS.
+Table 3 and Table 5 list the IOPS performance of local disks and specifications of a single local disk attached to an I3m ECS.
+Table 4 and Table 6 list the IOPS performance of local disks and specifications of a single local disk attached to an I3 ECS.
-Table 2 IOPS performance of local disks used by I3 ECSs Flavor
+-Table 3 IOPS performance of local disks used by I3m ECSs Flavor
Maximum IOPS for Random 4 KB Read
+Maximum IOPS for Random 4 KB Read
i3.2xlarge.4
+i3m.2xlarge.8
750,000
+750,000
i3.4xlarge.4
+i3m.4xlarge.8
1,500,000
+1,500,000
i3.8xlarge.4
+i3m.8xlarge.8
3,000,000
+3,000,000
i3.12xlarge.4
+i3m.12xlarge.8
4,500,000
+4,500,000
i3.16xlarge.4
+i3m.15xlarge.8
6,000,000
+5,250,000
i3.2xlarge.8
+i3m.16xlarge.8
750,000
-i3.4xlarge.8
-1,500,000
-i3.8xlarge.8
-3,000,000
-i3.12xlarge.8
-4,500,000
-i3.16xlarge.8
-6,000,000
+6,000,000
Table 3 Specifications of a single I3 local disk Metric
++ +
+Table 4 IOPS performance of local disks used by I3 ECSs Flavor
Performance
+Maximum IOPS for Random 4 KB Read
Disk capacity
+i3.2xlarge.4
1.6 TB
+750,000
IOPS for random 4 KB read
+i3.4xlarge.4
750,000
+1,500,000
IOPS for random 4 KB write
+i3.8xlarge.4
200,000
+3,000,000
Read throughput
+i3.12xlarge.4
2.9 GiB/s
+4,500,000
Write throughput
+i3.16xlarge.4
1.9 GiB/s
+6,000,000
Access latency
+i3.2xlarge.8
Within microseconds
+750,000
+i3.4xlarge.8
+1,500,000
+i3.8xlarge.8
+3,000,000
+i3.12xlarge.8
+4,500,000
+i3.16xlarge.8
+6,000,000
++ +
+Table 5 Specifications of a single I3m local disk Metric
+Performance
+Disk capacity
+1.6 TB
+IOPS for random 4 KB read
+750,000
+IOPS for random 4 KB write
+200,000
+Read throughput
+2.9 GiB/s
+Write throughput
+1.9 GiB/s
+Access latency
+Within microseconds
+-Table 6 Specifications of a single I3 local disk Metric
+Performance
+Disk capacity
+1.6 TB
+IOPS for random 4 KB read
+750,000
+IOPS for random 4 KB write
+200,000
+Read throughput
+2.9 GiB/s
+Write throughput
+1.9 GiB/s
+Access latency
+Within microseconds
Notes
- Table 4 lists the OSs supported by ultra-high I/O ECSs.
-
Table 4 Supported OS versions OS
+Notes
- Table 7 lists the OSs supported by ultra-high I/O ECSs.
+
Table 7 Supported OS versions OS
Version
CentOS
- CentOS Stream 8.6 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
- CentOS Stream 9.6 64bit
- CentOS Stream 8.6 64bit
- CentOS 8.5 64bit
- CentOS 8.4 64bit
- CentOS 8.3 64bit
- CentOS 8.2 64bit
- CentOS 8.1 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
Debian
- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
- Debian GNU/Linux 12.0.0 64bit
- Debian GNU/Linux 11.7.0 64bit
- Debian GNU/Linux 11.6.0 64bit
- Debian GNU/Linux 11.5.0 64bit
- Debian GNU/Linux 11.4.0 64bit
- Debian GNU/Linux 11.3.0 64bit
- Debian GNU/Linux 11.2.0 64bit
- Debian GNU/Linux 11.1.0 64bit
- Debian GNU/Linux 11.0.0 64bit
- Debian GNU/Linux 10.13.0 64bit
- Debian GNU/Linux 10.12.0 64bit
- Debian GNU/Linux 10.11.0 64bit
- Debian GNU/Linux 10.10.0 64bit
- Debian GNU/Linux 10.9.0 64bit
- Debian GNU/Linux 10.8.0 64bit
- Debian GNU/Linux 10.7.0 64bit
- Debian GNU/Linux 10.6.0 64bit
- Debian GNU/Linux 10.5.0 64bit
- Debian GNU/Linux 10.4.0 64bit
- Debian GNU/Linux 10.3.0 64bit
- Debian GNU/Linux 10.2.0 64bit
- Debian GNU/Linux 10.1.0 64bit
- Debian GNU/Linux 10 64bit
EulerOS
EulerOS 2.5 64bit
+- EulerOS 2.12 64bit
- EulerOS 2.11 64bit
- EulerOS 2.10 64bit
- EulerOS 2.8 64bit
- EulerOS 2.7 64bit
- EulerOS 2.5 64bit
Fedora
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 39 64bit
- Fedora 38 64bit
- Fedora 37 64bit
- Fedora 36 64bit
- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
- Fedora 32 64bit
- Fedora 31 64bit
OpenSUSE
OpenSUSE 15.3 64bit
+- OpenSUSE 15.5 64bit
- OpenSUSE 15.4 64bit
- OpenSUSE 15.3 64bit
- OpenSUSE 15.2 64bit
Oracle Linux
@@ -371,32 +575,32 @@Red Hat
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
- Red Hat Enterprise Linux 9.1 64bit
- Red Hat Enterprise Linux 9.0 64bit
- Red Hat Enterprise Linux 8.7 64bit
- Red Hat Enterprise Linux 8.6 64bit
- Red Hat Enterprise Linux 8.5 64bit
- Red Hat Enterprise Linux 8.4 64bit
- Red Hat Enterprise Linux 8.3 64bit
- Red Hat Enterprise Linux 8.2 64bit
- Red Hat Enterprise Linux 8.1 64bit
- Red Hat Enterprise Linux 7.9 64bit
- Red Hat Enterprise Linux 6.10 64bit
Rocky
Rocky 8 64bit
+- 9.2 64bit
- 9.1 64bit
- 9.0 64bit
- 8.8 64bit
- 8.7 64bit
- 8.6 64bit
- 8.5 64bit
- 8.4 64bit
- 8.3 64bit
- 8 64bit
SUSE
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP5 64bit
- Novell SUSE Linux Enterprise Server 15 SP4 64bit
- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 15 SP1 64bit
- Novell SUSE Linux Enterprise Server 15 64bit
- Novell SUSE Linux Enterprise Server 12 SP5 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 22.04 Server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2022 Standard 64bit
- Windows Server 2022 Datacenter 64bit
- Windows Server 2019 Datacenter 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
openEuler
openEuler 20.03 64bit
+- openEuler 22.03 SP1 64bit
- openEuler 22.03 64bit
- openEuler 20.03 SP3 64bit
- openEuler 20.03 SP2 64bit
- openEuler 20.03 SP1 64bit
- openEuler 20.03 64bit
diff --git a/docs/ecs/umn/en-us_topic_0095020344.html b/docs/ecs/umn/en-us_topic_0095020344.html index 60618cb5..0395edd3 100644 --- a/docs/ecs/umn/en-us_topic_0095020344.html +++ b/docs/ecs/umn/en-us_topic_0095020344.html @@ -11,7 +11,7 @@-Parent topic: Usage Errors+Parent topic: ECS Failure FAQdiff --git a/docs/ecs/umn/en-us_topic_0096293655.html b/docs/ecs/umn/en-us_topic_0096293655.html index e1352273..5894ebb9 100644 --- a/docs/ecs/umn/en-us_topic_0096293655.html +++ b/docs/ecs/umn/en-us_topic_0096293655.html @@ -1,7 +1,7 @@ --Parent topic: Data Backup and Restoration+Parent topic: Data Backup and Restoration FAQAttaching an EVS Disk to an ECS
-Scenarios
If the existing disks of an ECS fail to meet service requirements, for example, due to insufficient disk space or poor disk performance, you can attach more available EVS disks to the ECS, or create more disks (in Storage > Elastic Volume Service) and attach them to the ECS.
+Attaching a Disk to an ECS
+Scenarios
If the existing disks of an ECS fail to meet service requirements, for example, due to insufficient disk space or poor disk performance, you can attach more available EVS disks to the ECS, or create more disks (under Storage > Elastic Volume Service) and attach them to the ECS.
Prerequisites
- EVS disks are available.
For instructions about how to create an EVS disk, see "Creating an EVS Disk" in Elastic Volume Service User Guide.
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 diff --git a/docs/ecs/umn/en-us_topic_0096304614.html b/docs/ecs/umn/en-us_topic_0096304614.html index 4cc872e2..4df279e0 100644 --- a/docs/ecs/umn/en-us_topic_0096304614.html +++ b/docs/ecs/umn/en-us_topic_0096304614.html @@ -1,6 +1,6 @@ -
- 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.
@@ -22,7 +22,7 @@
CBR
+Backup Using CBR
-
diff --git a/docs/ecs/umn/en-us_topic_0097289624.html b/docs/ecs/umn/en-us_topic_0097289624.html
index e0fd5b0e..cde72874 100644
--- a/docs/ecs/umn/en-us_topic_0097289624.html
+++ b/docs/ecs/umn/en-us_topic_0097289624.html
@@ -9,7 +9,7 @@
- G series
- P series
- Computing-accelerated P3
- Computing-accelerated P2s (recommended)
- Computing-accelerated P2v
- Inference-accelerated Pi2 (recommended)
- 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.
- 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.
- GPU-accelerated ECSs do not support live migration.
Helpful links: +Images Supported by GPU-accelerated ECSs
@@ -152,7 +152,7 @@Notes
- 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.
+- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
Computing-accelerated P3
Overview
P3 ECSs use NVIDIA A100 GPUs and provide flexibility and ultra-high-performance computing. P3 ECSs have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics. Theoretically, the FP32 is 19.5 TFLOPS and the TF32 tensor core is 156 TFLOPS | 312 TFLOPS (sparsity enabled).
@@ -390,10 +390,10 @@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
-- 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.
+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.
- If a P3 ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
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.
@@ -535,12 +535,12 @@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- After a P2s ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately. -
Resources will be released after a P2s ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+Notes- After a P2s ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.-
Resources will be released after a P2s ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
- By default, P2s ECSs created using a Windows public image have the Tesla driver installed.
- If a P2s ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see 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.
- By default, P2s ECSs created using a Windows public image have the Tesla driver installed.
- If a P2s ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
Computing-accelerated P2v
Overview
+Computing-accelerated P2v
Overview
P2v ECSs use NVIDIA Tesla V100 GPUs and deliver high flexibility, high-performance computing, and high cost-effectiveness. These ECSs use GPU NVLink for direct communication between GPUs, improving data transmission efficiency. P2v ECSs provide outstanding general computing capabilities and have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics.
Specifications
@@ -678,9 +678,9 @@Supported Common Software
P2v ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P2v ECSs. P2v ECSs support the following commonly used software:-- Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- CUDA GPU rendering supported by RedShift for Autodesk 3dsMax and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
Notes- After a P2v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
Resources will be released after a P2v ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+Notes- After a P2v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.-
Resources will be released after a P2v ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
- By default, P2v ECSs created using a Windows public image have the Tesla driver installed.
- By default, P2v ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS.
- If a P2v ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see 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.
- By default, P2v ECSs created using a Windows public image have the Tesla driver installed.
- By default, P2v ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- If a P2v ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
Inference-accelerated Pi2
Overview
@@ -847,7 +847,7 @@- After a Pi2 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 Pi2 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.
- Pi2 ECSs support automatic recovery when the hosts accommodating such ECSs become faulty.
- By default, Pi2 ECSs created using a Windows public image have the Tesla driver installed.
- By default, Pi2 ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS.
- If a Pi2 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.
- Pi2 ECSs support automatic recovery when the hosts accommodating such ECSs become faulty.
- By default, Pi2 ECSs created using a Windows public image have the Tesla driver installed.
- By default, Pi2 ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- If a Pi2 ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
diff --git a/docs/ecs/umn/en-us_topic_0100005619.html b/docs/ecs/umn/en-us_topic_0100005619.html index 7cd01540..10efdd2b 100644 --- a/docs/ecs/umn/en-us_topic_0100005619.html +++ b/docs/ecs/umn/en-us_topic_0100005619.html @@ -1,6 +1,6 @@ -How Can I Log In to an ECS After Its System Disk Is Exchanged with That Attached to Another ECS Running the Same OS?
+How Can I Log In to an ECS After It Exchanged the System Disk with Another ECS Running the Same OS?
Symptom
Two ECSs run the same OS, for example, both run Windows or Linux. The system disks attached to the two ECSs are exchanged offline. After the exchanging, the login keys of the ECSs may change. In such a case, how can I log in to the ECSs?
Before stopping an ECS for disk detachment, release the IP address assigned to the ECS using DHCP so that ECS can correctly obtain an IP address later. To do so, perform the following operations:
- Log in to the Windows ECS.
- Run the following command to release the IP address: diff --git a/docs/ecs/umn/en-us_topic_0100756510.html b/docs/ecs/umn/en-us_topic_0100756510.html index 8d2a45ca..306c4123 100644 --- a/docs/ecs/umn/en-us_topic_0100756510.html +++ b/docs/ecs/umn/en-us_topic_0100756510.html @@ -14,7 +14,7 @@
diff --git a/docs/ecs/umn/en-us_topic_0101604498.html b/docs/ecs/umn/en-us_topic_0101604498.html index ee2ab5ec..2f94cdba 100644 --- a/docs/ecs/umn/en-us_topic_0101604498.html +++ b/docs/ecs/umn/en-us_topic_0101604498.html @@ -5,21 +5,21 @@-Parent topic: Logins Through the Management Console+Parent topic: VNC Login-Constraints
- Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
Procedure
- Run the following command to install the GUI desktop component:
# yum groupinstall "Server with GUI"
+Procedure
- Run the following command to install the GUI desktop component:
yum groupinstall "Server with GUI"
- If the following message is displayed after the installation is complete:
Failed : python -urllibs3.noarch 0:1.10.2-7.e17
Run the following command:
mv /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname.bak
yum install python-urllib3 -y
- After the installation is complete, run the following command to set the default startup level to graphical.target:
# systemctl set-default graphical.target
- - Run the following command to start graphical.target:
# systemctl start graphical.target
+ - After the installation is complete, run the following command to set the default startup level to graphical.target:
systemctl set-default graphical.target
+ - Run the following command to start graphical.target:
systemctl start graphical.target
- Restart the ECS.
- Log in to the ECS using VNC provided on the management console. Set the language, time zone, username, and password as prompted.
- Run the following command to install the GUI desktop component:
diff --git a/docs/ecs/umn/en-us_topic_0101604501.html b/docs/ecs/umn/en-us_topic_0101604501.html index 166e6328..f2b4c74d 100644 --- a/docs/ecs/umn/en-us_topic_0101604501.html +++ b/docs/ecs/umn/en-us_topic_0101604501.html @@ -14,7 +14,7 @@-Parent topic: GUI Installation FAQs+Parent topic: OS FAQdiff --git a/docs/ecs/umn/en-us_topic_0101604502.html b/docs/ecs/umn/en-us_topic_0101604502.html index 5fff7f9d..efff6e40 100644 --- a/docs/ecs/umn/en-us_topic_0101604502.html +++ b/docs/ecs/umn/en-us_topic_0101604502.html @@ -1,14 +1,16 @@-Parent topic: Resource Management and Tags+Parent topic: Resource Management and Tag FAQHow Do I Delete or Restart an ECS?
-Deleting an ECS
- Log in to the management console.
- Select the region where the ECS is located.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Delete in the Operation column.
-Deleting an ECS
- Log in to the management console.
- Select the region where the ECS is located.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Delete in the Operation column.
If you choose to delete the EIP and data disks associated with the ECS when deleting it, no charges will apply for the EIP and data disks. However, if they are not deleted, they will continue o incur fees.
+Restarting an ECS
- Log in to the management console.
- Select the region where the ECS is located.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Restart in the Operation column.
Restarting an ECS
- Log in to the management console.
- Select the region where the ECS is located.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Restart in the Operation column.
diff --git a/docs/ecs/umn/en-us_topic_0101604506.html b/docs/ecs/umn/en-us_topic_0101604506.html index 9a5add8a..0f51f446 100644 --- a/docs/ecs/umn/en-us_topic_0101604506.html +++ b/docs/ecs/umn/en-us_topic_0101604506.html @@ -23,7 +23,7 @@-Parent topic: ECS Deletion+Parent topic: ECS Deletion and Unsubscription FAQdiff --git a/docs/ecs/umn/en-us_topic_0101604507.html b/docs/ecs/umn/en-us_topic_0101604507.html index c9be73b3..fd216de1 100644 --- a/docs/ecs/umn/en-us_topic_0101604507.html +++ b/docs/ecs/umn/en-us_topic_0101604507.html @@ -1,7 +1,7 @@ --Parent topic: Network Configurations+Parent topic: Network Configuration FAQHow Can I Configure Port Redirection?
-Symptom
It is expected that the EIP and port on ECS 1 accessed from the Internet can be automatically redirected to the EIP and port on ECS 2.
+How Do I Configure Port Mapping?
+Symptom
It is expected that the EIP and port on ECS 1 accessed from the public network can be automatically redirected to the EIP and port on ECS 2.
Windows
For example, to redirect port 8080 on ECS 1 bound with EIP 192.168.10.43 to port 18080 on ECS 2 bound with EIP 192.168.10.222, perform the following operations on ECS 1.
- Ensure that the desired ports have been enabled on the ECS security group and firewall.
@@ -34,7 +34,7 @@diff --git a/docs/ecs/umn/en-us_topic_0101604508.html b/docs/ecs/umn/en-us_topic_0101604508.html index 37e3fe55..9fa1f3b9 100644 --- a/docs/ecs/umn/en-us_topic_0101604508.html +++ b/docs/ecs/umn/en-us_topic_0101604508.html @@ -5,7 +5,7 @@-Parent topic: Network Configurations+Parent topic: Network Configuration FAQ- System disk image: contains an OS and application software for running services. You can use a system disk image to create ECSs and migrate your services to the cloud.
- Data disk image: contains only service data. You can create a data disk image from an ECS data disk. You can also use a data disk image to create EVS disks and migrate your service data to the cloud.
- Full-ECS image: contains all the data of an ECS, including the data on the data disks attached to the ECS. A full-ECS image can be used to rapidly create ECSs with service data.
You can use a private image to change the OS. For instructions about how to create a private image, see Image Management Service User Guide.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, choose More > Manage Image/Backup > Create Image in the Operation column.
- Configure the following information:
Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, choose More > Manage Image/Backup > Create Image in the Operation column.
- Configure the following information:
Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
Table 1 Image type and source Parameter
diff --git a/docs/ecs/umn/en-us_topic_0101604511.html b/docs/ecs/umn/en-us_topic_0101604511.html index b5810f95..02feadc1 100644 --- a/docs/ecs/umn/en-us_topic_0101604511.html +++ b/docs/ecs/umn/en-us_topic_0101604511.html @@ -1,13 +1,13 @@-Parent topic: GUI Installation FAQs+Parent topic: OS FAQHow Long Does It Take to Change an ECS OS?
-Generally, the process of changing the OS of an ECS takes about 1 to 2 minutes to complete. On the ECS console, stop the ECS and choose More > Manage Image/Backup > Change OS in the Operation column.
+Generally, the process of changing the OS of an ECS takes about 1 to 2 minutes to complete. On the ECS console, stop the ECS and choose More > Manage Image/Backup > Change OS in the Operation column.
During this process, the ECS is in Changing OS state.
-Figure 1 OS Change+Figure 1 Changing an OSdiff --git a/docs/ecs/umn/en-us_topic_0101604512.html b/docs/ecs/umn/en-us_topic_0101604512.html index bc464ec9..7b4e62a3 100644 --- a/docs/ecs/umn/en-us_topic_0101604512.html +++ b/docs/ecs/umn/en-us_topic_0101604512.html @@ -2,13 +2,13 @@-Parent topic: OS Management+Parent topic: OS Change FAQHow Long Does It Take to Reinstall an ECS OS?
Generally, the process of reinstalling the OS of an ECS takes about 1 to 2 minutes to complete. On the ECS console, stop the ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
-During this process, the ECS is in Reinstalling OS state.
-Figure 1 Reinstall OS+During this process, the ECS is in Reinstalling OS state.
+Figure 1 Reinstalling an OSdiff --git a/docs/ecs/umn/en-us_topic_0102391480.html b/docs/ecs/umn/en-us_topic_0102391480.html index 9d5fc454..9ee36dd6 100644 --- a/docs/ecs/umn/en-us_topic_0102391480.html +++ b/docs/ecs/umn/en-us_topic_0102391480.html @@ -30,7 +30,7 @@-Parent topic: OS Management+Parent topic: OS Change FAQdiff --git a/docs/ecs/umn/en-us_topic_0103285575.html b/docs/ecs/umn/en-us_topic_0103285575.html index 4b9b7024..6d5e074b 100644 --- a/docs/ecs/umn/en-us_topic_0103285575.html +++ b/docs/ecs/umn/en-us_topic_0103285575.html @@ -2,7 +2,7 @@-Parent topic: ECS Creation+Parent topic: ECS Creation FAQHow Do I Obtain My Disk Device Name in the ECS OS Using the Device Identifier Provided on the Console?
Scenarios
You find that the device name displayed in the ECS OS is different from that displayed on the management console and you cannot determine which disk name is correct. This section describes how to obtain the disk name used in an ECS OS according to the device identifier on the console.
-For details about how to attach disks, see Attaching an EVS Disk to an ECS.
+For details about how to attach disks, see Attaching a Disk to an ECS.
Obtaining the Disk ID of an ECS on the Console
- Log in to the management console.
- Under Computing, choose Elastic Cloud Server.
- Click the target ECS name in the ECS list.
- Click the Disks tab and then click
to expand the disk information. - Check the device type and ID of the disk.diff --git a/docs/ecs/umn/en-us_topic_0105130172.html b/docs/ecs/umn/en-us_topic_0105130172.html index 12e11450..e782de76 100644 --- a/docs/ecs/umn/en-us_topic_0105130172.html +++ b/docs/ecs/umn/en-us_topic_0105130172.html @@ -7,7 +7,7 @@
If Device Identifier is not displayed on the page, stop the ECS and restart it.
@@ -86,7 +86,7 @@ lrwxrwxrwx 1 root root 9 May 21 20:22 -Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQIf the fault persists after you have ruled out a cause, check other causes.
Figure 1 Method of locating the failure to ping an EIP-
Table 1 Method of locating the failure to ping an EIP Possible Cause
+Table 1 Method of locating the failure to ping an EIP Possible Causes
Solution
Checking Security Group Rules
ICMP is used for the ping command. Check whether the security group accommodating the ECS allows ICMP traffic.
-- 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.
+- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose 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.
- Click the Security Groups tab, expand the information of the security group, and view security group rules.
- Click the security group ID.
The system automatically switches to the Security Group page.
- On the Outbound Rules page, click Add Rule. In the displayed dialog box, set required parameters to add an outbound rule.
Table 2 Security group rules Transfer Direction
@@ -57,7 +57,7 @@Protocol/Port Range
Source
+Destination
diff --git a/docs/ecs/umn/en-us_topic_0105169362.html b/docs/ecs/umn/en-us_topic_0105169362.html index f14ec2c5..f1660625 100644 --- a/docs/ecs/umn/en-us_topic_0105169362.html +++ b/docs/ecs/umn/en-us_topic_0105169362.html @@ -14,7 +14,7 @@-Parent topic: Network Configurations+Parent topic: Network Configuration FAQdiff --git a/docs/ecs/umn/en-us_topic_0105170210.html b/docs/ecs/umn/en-us_topic_0105170210.html index 260d2921..34886be4 100644 --- a/docs/ecs/umn/en-us_topic_0105170210.html +++ b/docs/ecs/umn/en-us_topic_0105170210.html @@ -11,7 +11,7 @@-Parent topic: Passwords and Key Pairs+Parent topic: Password and Key Pair FAQdiff --git a/docs/ecs/umn/en-us_topic_0105215483.html b/docs/ecs/umn/en-us_topic_0105215483.html index 99085183..81c7faf9 100644 --- a/docs/ecs/umn/en-us_topic_0105215483.html +++ b/docs/ecs/umn/en-us_topic_0105215483.html @@ -1,6 +1,6 @@ --Parent topic: Passwords and Key Pairs+Parent topic: Password and Key Pair FAQPasswords and Key Pairs
+Password and Key Pair FAQ
diff --git a/docs/ecs/umn/en-us_topic_0107659745.html b/docs/ecs/umn/en-us_topic_0107659745.html index d01f76ef..2ba77a4a 100644 --- a/docs/ecs/umn/en-us_topic_0107659745.html +++ b/docs/ecs/umn/en-us_topic_0107659745.html @@ -65,8 +65,8 @@Specifies the memory used by sockets for automatic optimization.
The first value is the minimum number of bytes allocated to the socket buffer for transmitting data.
-The second value is the default value, which is overwritten by wmem_default. The buffer size can increase to this value when the system load is not heavy.
-The third value is the maximum number of bytes allocated to the socket buffer for transmitting data. This value is overwritten by wmem_max.
+The second value is the default value, which is overwritten by wmem_default. The buffer size can increase to this value when the system load is not heavy.
+The third value is the maximum number of bytes allocated to the socket buffer for transmitting data. This value is overwritten by wmem_max.
net.ipv4.tcp_keepalive_time
@@ -121,7 +121,7 @@Allows fast recycle of TIME-WAIT sockets.
NOTE:This parameter is valid only when net.ipv4.tcp_timestamps is enabled.
-Do not set this parameter to 1 if NAT is enabled. Otherwise, an error will occur during remote ECS logins.
+Do not set this parameter to 1 if NAT is enabled. Otherwise, an error will occur during remote ECS logins.
Modifying Kernel Parameter Settings
- Method 1: Run the echo command in /proc/sys to modify the file for the target kernel parameters.
The parameter values changed using this method take effect only during the current running and will be reset after the system is restarted. To make the modification take effect permanently, see method 2.
-/proc/sys/ is a pseudo directory generated after the Linux kernel is started. The net folder in this directory stores all kernel parameters that have taken effect in the system. The directory tree structure is determined based on complete parameter names. For example, net.ipv4.tcp_tw_recycle corresponds to the /proc/sys/net/ipv4/tcp_tw_recycle file, and the content of the file is the parameter value.
+/proc/sys/ is a pseudo directory generated after the Linux kernel is started. The net folder in this directory stores all kernel parameters that have taken effect in the system. The directory tree structure is determined based on complete parameter names. For example, net.ipv4.tcp_tw_recycle corresponds to the /proc/sys/net/ipv4/tcp_tw_recycle file, and the content of the file is the parameter value.
Example:
To change the net.ipv4.tcp_tw_recycle value to 0, run the following command:
echo "0" > /proc/sys/net/ipv4/tcp_tw_recycle
@@ -239,7 +239,7 @@
diff --git a/docs/ecs/umn/en-us_topic_0114225937.html b/docs/ecs/umn/en-us_topic_0114225937.html index a9d5d940..04a75453 100644 --- a/docs/ecs/umn/en-us_topic_0114225937.html +++ b/docs/ecs/umn/en-us_topic_0114225937.html @@ -43,7 +43,7 @@-Parent topic: Network Configurations+Parent topic: Network Configuration FAQdiff --git a/docs/ecs/umn/en-us_topic_0115820205.html b/docs/ecs/umn/en-us_topic_0115820205.html index a301ae4f..85c24b81 100644 --- a/docs/ecs/umn/en-us_topic_0115820205.html +++ b/docs/ecs/umn/en-us_topic_0115820205.html @@ -382,7 +382,7 @@-Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQdiff --git a/docs/ecs/umn/en-us_topic_0116262067.html b/docs/ecs/umn/en-us_topic_0116262067.html index c81912ca..0f302e6e 100644 --- a/docs/ecs/umn/en-us_topic_0116262067.html +++ b/docs/ecs/umn/en-us_topic_0116262067.html @@ -124,7 +124,7 @@-Parent topic: Network Configurations+Parent topic: Network Configuration FAQdeleteAutoRecovery
Updating metadata/Setting metadata of a specified key
+Updating metadata or setting metadata of a specified key
ecs
diff --git a/docs/ecs/umn/en-us_topic_0116266206.html b/docs/ecs/umn/en-us_topic_0116266206.html index 81d5c189..48c7264c 100644 --- a/docs/ecs/umn/en-us_topic_0116266206.html +++ b/docs/ecs/umn/en-us_topic_0116266206.html @@ -1,6 +1,6 @@ --Parent topic: CTS+Parent topic: Audit Using CTSCTS
+Audit Using CTS
diff --git a/docs/ecs/umn/en-us_topic_0116266207.html b/docs/ecs/umn/en-us_topic_0116266207.html index 4967e940..4284c246 100644 --- a/docs/ecs/umn/en-us_topic_0116266207.html +++ b/docs/ecs/umn/en-us_topic_0116266207.html @@ -19,7 +19,7 @@diff --git a/docs/ecs/umn/en-us_topic_0116634723.html b/docs/ecs/umn/en-us_topic_0116634723.html index 22e0e457..38dd7a9c 100644 --- a/docs/ecs/umn/en-us_topic_0116634723.html +++ b/docs/ecs/umn/en-us_topic_0116634723.html @@ -5,15 +5,15 @@-Parent topic: CTS+Parent topic: Audit Using CTS-Constraints
- Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
Procedure
- Run the following command to obtain the installation component provided by the OS: -
diff --git a/docs/ecs/umn/en-us_topic_0117490178.html b/docs/ecs/umn/en-us_topic_0117490178.html index ac3a061f..9e465b47 100644 --- a/docs/ecs/umn/en-us_topic_0117490178.html +++ b/docs/ecs/umn/en-us_topic_0117490178.html @@ -7,7 +7,7 @@-Parent topic: GUI Installation FAQs+Parent topic: OS FAQ- When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Procedure
- On the desktop of the server, click the start icon in the lower left corner.
The Windows Server window is displayed.
@@ -17,7 +17,7 @@Figure 2 Computer Management
- Choose Storage > Disk Management.Disks are displayed in the right pane. If there is a disk that is not initialized, the system will prompt you with the Initialize Disk dialog box.-Figure 3 Disk list
- In the Initialize Disk dialog box, the to-be-initialized disk is selected. Select a disk partition style and click OK. In this example, GPT (GUID Partition Table) is selected.The Computer Management window is displayed.Figure 4 Computer Management+
- In the Initialize Disk dialog box, the to-be-initialized disk is selected. Select a disk partition style and click OK. In this example, GPT (GUID Partition Table) is selected.
The Computer Management window is displayed.Figure 4 Computer Management The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is greater than 2 TiB.
If the partition style is changed after the disk has been used, all data on the disk will be lost, so take care to select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.
diff --git a/docs/ecs/umn/en-us_topic_0118224527.html b/docs/ecs/umn/en-us_topic_0118224527.html index d3612d28..ff7affc4 100644 --- a/docs/ecs/umn/en-us_topic_0118224527.html +++ b/docs/ecs/umn/en-us_topic_0118224527.html @@ -13,7 +13,7 @@diff --git a/docs/ecs/umn/en-us_topic_0120795668.html b/docs/ecs/umn/en-us_topic_0120795668.html index 761875c1..d775423b 100644 --- a/docs/ecs/umn/en-us_topic_0120795668.html +++ b/docs/ecs/umn/en-us_topic_0120795668.html @@ -6,9 +6,9 @@-Parent topic: Passwords and Key Pairs+Parent topic: Password and Key Pair FAQ-Possible Causes
The ECS memory is insufficient.
Solution
- Method 1 (recommended)
Modify the ECS specifications to increase the vCPUs and memory size. For instructions about how to modify ECS specifications, see General Operations.
+Solution
- Method 1 (recommended)
Modify the ECS specifications to increase the vCPUs and memory size. For instructions about how to modify ECS specifications, see Modifying Individual ECS Specifications.
- Method 2
Enable virtual memory on the ECS to obtain its idle memory.
-For instructions about how to enable virtual memory, see How Can I Enable Virtual Memory on a Windows ECS?
+For details, see How Can I Enable Virtual Memory on a Windows ECS?
This method will deteriorate the disk I/O performance, so use this method only when necessary.
How Can I Enable Virtual Memory on a Windows ECS?
-Enabling ECS virtual memory will deteriorate I/O performance. If the memory is insufficient, you are advised to expand the memory by referring to Modifying ECS Specifications. If you really need to enable virtual memory, see the operations described below.
+Enabling ECS virtual memory will deteriorate I/O performance. If the memory is insufficient, you are advised to expand the memory by referring to Modifying ECS Specifications (vCPUs and Memory). If you really need to enable virtual memory, see the operations described below.
If the memory usage is excessively high and the I/O performance is not as good as expected, you are not advised to enable virtual memory. The reason is as follows: The excessively high memory usage limits the system performance improvement. Furthermore, frequent memory switching requires massive additional I/O operations, which will further deteriorate the I/O performance and the overall system performance.
The operations described in this section are provided for the ECSs running Windows Server 2008 or later.
@@ -17,7 +17,7 @@diff --git a/docs/ecs/umn/en-us_topic_0122627689.html b/docs/ecs/umn/en-us_topic_0122627689.html index 1dda492b..0b2e03cf 100644 --- a/docs/ecs/umn/en-us_topic_0122627689.html +++ b/docs/ecs/umn/en-us_topic_0122627689.html @@ -1,22 +1,22 @@ --Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQChanging the Login Password on an ECS
-Scenarios
This section describes how to change the password for logging in to an ECS when the password is about to expire, the password is forgotten, or you are logging in to the ECS for the first time. It is a good practice to change the initial password upon the first login.
+Resetting the Password for Logging In to an ECS in the OS
+Scenarios
This section describes how to reset the password for logging in to an ECS in the OS when the password is about to expire, the password is forgotten, or you are logging in to the ECS for the first time. It is a good practice to change the initial password upon the first login.
Prerequisites
The ECS can be logged in.
Background
Table 1 shows the ECS password complexity requirements.
-Table 1 Password complexity requirements Parameter
+Table 1 Password complexity requirements Parameter
Requirement
+Requirement
Password
+Password
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- 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.
- 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.)
Windows
- Log in to the ECS.
For details, see Login Overview (Windows).
- - Press Win+R to start the Run dialog box.
- Enter cmd to open the command-line interface (CLI) window.
- Run the following command to change the password (the new password must meet the requirements described in Table 1):
net user Administrator New password
+ - Press Win+R to start the Run dialog box.
- Enter cmd to open the command-line interface (CLI) window.
- Enter a new password that meets the requirements listed in Table 1.
net user Administrator New password
Linux
- Use the existing key file to log in to the ECS as user root through SSH.
For details, see Logging In to a Linux ECS Using an SSH Key Pair.
- Run the following command to reset the password of user root:
passwd
To reset the password of another user, replace passwd with passwd username.
- - Enter the new password as prompted. Ensure that the new password meets the requirements described in Table 1.
New password: +
- Enter a new password that meets the requirements listed in Table 1 as prompted.
New password: Retype new password:
If the following information is displayed, the password has been changed:@@ -39,7 +39,7 @@ Retype new password:passwd: all authentication tokens updates successfully
diff --git a/docs/ecs/umn/en-us_topic_0133339807.html b/docs/ecs/umn/en-us_topic_0133339807.html index e1741678..26fd68cb 100644 --- a/docs/ecs/umn/en-us_topic_0133339807.html +++ b/docs/ecs/umn/en-us_topic_0133339807.html @@ -5,7 +5,7 @@-Parent topic: Passwords+Parent topic: Password Reset-Constraints
- The ECS must be stopped.
- If a virtual IP address or DNAT rule has been configured for the NIC, cancel the configuration before modifying the private IP address.
- If the NIC has an IPv6 address, its private IP address (IPv4 or IPv6 address) cannot be modified.
- To change the private IP address for a backend server of a load balancer, remove the backend server from the backend server group first.
Procedure
- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
- Click the name of the target ECS.
The ECS details page is displayed.
+Procedure
- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
- Click the name of the target ECS.
The ECS details page is displayed.
- Click the NICs tab. Locate the row containing the network interface and click Modify Private IP.
The Modify Private IP dialog box is displayed.
Figure 1 Modifying the private IP address
- Change the subnet and private IP address of the NIC as required. diff --git a/docs/ecs/umn/en-us_topic_0133365988.html b/docs/ecs/umn/en-us_topic_0133365988.html index dca49dbe..8fa785e4 100644 --- a/docs/ecs/umn/en-us_topic_0133365988.html +++ b/docs/ecs/umn/en-us_topic_0133365988.html @@ -1,23 +1,23 @@ -
Subnets can be changed only within the same VPC.
@@ -16,7 +16,7 @@Migrating an ECS
+Migrating an ECS to a DeH
Scenarios
ECSs can be migrated:
- Between Dedicated Hosts (DeHs)
- From a DeH to a public resource pool
- From a public resource pool to a DeH
This section describes how to migrate ECSs from a public resource pool to a DeH.
+This section describes how to migrate an ECS from a public resource pool to a DeH.
-Constraints
- Only stopped ECSs can be migrated.
- To ensure that the migration is successful, there must be an available DeH.
- CBR and CSBS backups are not affected by migrations.
- ECS IDs remain unchanged after a migration.
diff --git a/docs/ecs/umn/en-us_topic_0140313881.html b/docs/ecs/umn/en-us_topic_0140313881.html index 1f291504..fec441f6 100644 --- a/docs/ecs/umn/en-us_topic_0140313881.html +++ b/docs/ecs/umn/en-us_topic_0140313881.html @@ -1,11 +1,11 @@ -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.
- Locate the row that contains the target ECS and choose More > Migrate ECS in the Operation column.
- In the displayed dialog box, select the target DeH.diff --git a/docs/ecs/umn/en-us_topic_0140313880.html b/docs/ecs/umn/en-us_topic_0140313880.html index 490fd393..a12f3e61 100644 --- a/docs/ecs/umn/en-us_topic_0140313880.html +++ b/docs/ecs/umn/en-us_topic_0140313880.html @@ -9,7 +9,7 @@
If no DeHs are available, create a DeH first. For details, see Allocating DeHs in the Dedicated Host User Guide.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More In the Operation column of the ECS to be migrated, choose More > Migrate ECS in the Operation column.
- In the displayed dialog box, select the target DeH.
If no DeHs are available, create a DeH first. For details, see Allocating DeHs in the Dedicated Host User Guide.
- Click OK.
diff --git a/docs/ecs/umn/en-us_topic_0133513874.html b/docs/ecs/umn/en-us_topic_0133513874.html index 20d49355..f7af044b 100644 --- a/docs/ecs/umn/en-us_topic_0133513874.html +++ b/docs/ecs/umn/en-us_topic_0133513874.html @@ -11,7 +11,7 @@-Parent topic: Managing ECSs+Parent topic: Managing ECS Configurations- Manually Installing a GRID Driver on a GPU-accelerated ECS
-
- Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS
+- Manually Installing a Tesla Driver on a GPU-accelerated ECS
diff --git a/docs/ecs/umn/en-us_topic_0136777354.html b/docs/ecs/umn/en-us_topic_0136777354.html index 94cc8fa5..3fe0c4c1 100644 --- a/docs/ecs/umn/en-us_topic_0136777354.html +++ b/docs/ecs/umn/en-us_topic_0136777354.html @@ -1,6 +1,6 @@ -
Logins Through the Management Console
+VNC Login
@@ -24,7 +24,7 @@diff --git a/docs/ecs/umn/en-us_topic_0140313879.html b/docs/ecs/umn/en-us_topic_0140313879.html index 7b6d7dac..4d04b964 100644 --- a/docs/ecs/umn/en-us_topic_0140313879.html +++ b/docs/ecs/umn/en-us_topic_0140313879.html @@ -7,12 +7,12 @@-Parent topic: Login and Connection+Parent topic: Remote Login FAQ-Parent topic: Managing ECSs+Parent topic: Managing ECS Configurations
Passwords and Key Pairs Management
+Passwords and Key Pairs
-
-
- Passwords
+ - Password Reset
- Key Pairs
diff --git a/docs/ecs/umn/en-us_topic_0140313883.html b/docs/ecs/umn/en-us_topic_0140313883.html
index f1b5d530..827b47a2 100644
--- a/docs/ecs/umn/en-us_topic_0140313883.html
+++ b/docs/ecs/umn/en-us_topic_0140313883.html
@@ -1,6 +1,6 @@
- - You cannot delete the default security group, but you can modify existing rules or add rules to the group.
- The default security group is automatically created to simplify the process of creating an instance for the first time. The default security group denies all external requests. To log in to an instance, add a security group rule by referring to Remotely Logging In to an ECS from a Local Server.
- Enable IPv6 for the ECS.
- Run the following command to check whether IPv6 is enabled for the kernel:
- If a command output is displayed, IPv6 is enabled.
- If no information is displayed, IPv6 is disabled. Go to 2.b to load the IPv6 module.
- Run the following command to load the IPv6 module: -
- Add the following content to the /etc/sysctl.conf file:
net.ipv6.conf.all.disable_ipv6=0
+ - Add the following content to the /etc/sysctl.conf file:
net.ipv6.conf.all.disable_ipv6=0
- Save the configuration and exit. Then, run the following command to load the configuration:
- Run the following command to check whether IPv6 is enabled for the kernel:
- Enable dynamic IPv6 address assignment for the ECS.
- Ubuntu 18.04/20.04
- Run the following command to access /etc/netplan/:
cd /etc/netplan
@@ -195,22 +195,22 @@ DHCPV6C=yes- CentOS 6.x:
- Run the following command to edit the dhclient.conf file:
vi /etc/dhcp/dhclient.conf
- Press i to enter editing mode and add the timeout attribute to the file.
timeout 30;
- Enter :wq to save the settings and exit.
- Run the following command to edit the dhclient.conf file:
- Debian 7.5:
- Run the following command to edit the networking file:
vi /etc/init.d/networking
+ - Debian 7.5:
- Run the following command to edit the networking file:
vi /etc/init.d/networking
- Press i to enter editing mode and add the timeout attribute.Figure 20 Modification 1
Figure 21 Modification 2
- Run the following command to edit the networking file:
- Debian 8.2.0/8.8.0
- Run the following command to edit the network-pre.conf file:
vi /lib/systemd/system/networking.service.d/network-pre.conf
+ - Debian 8.2.0/8.8.0
- Run the following command to edit the network-pre.conf file:
vi /lib/systemd/system/networking.service.d/network-pre.conf
- Press i to enter editing mode and add the timeout attribute to the file.
[Service] TimeoutStartSec=30
- Run the following command to edit the network-pre.conf file:
- Debian 9.0
- Run the following command to edit the networking.service file:
vi /etc/system/system/network-online.target.wants/networking.service
+ - Debian 9.0
- Run the following command to edit the networking.service file:
vi /etc/system/system/network-online.target.wants/networking.service
- Press i to enter editing mode and change TimeoutStartSec=5min to TimeoutStartSec=30.
- Run the following command to edit the networking.service file:
- Run the following command to edit the networking.service file:
- Run the following command to edit the network-pre.conf file:
- Run the following command to edit the networking file:
Changing ECS Names
-Scenarios
The name of a created ECS can be changed to meet your service requirements.
+diff --git a/docs/ecs/umn/en-us_topic_0145756657.html b/docs/ecs/umn/en-us_topic_0145756657.html index dabf4a83..403c6b20 100644 --- a/docs/ecs/umn/en-us_topic_0145756657.html +++ b/docs/ecs/umn/en-us_topic_0145756657.html @@ -17,7 +17,7 @@Scenarios
After an ECS is created, you can change its name as needed.
Multiple ECS names can be changed in a batch. After the change, the ECS names are the same.
Changing the Name of a Single ECS
diff --git a/docs/ecs/umn/en-us_topic_0144542149.html b/docs/ecs/umn/en-us_topic_0144542149.html index 5cb2cf73..cff5476d 100644 --- a/docs/ecs/umn/en-us_topic_0144542149.html +++ b/docs/ecs/umn/en-us_topic_0144542149.html @@ -8,7 +8,7 @@-Parent topic: Managing ECSs+Parent topic: Managing ECS Configurationsdiff --git a/docs/ecs/umn/en-us_topic_0149470468.html b/docs/ecs/umn/en-us_topic_0149470468.html index 70a71f8c..a0adf89b 100644 --- a/docs/ecs/umn/en-us_topic_0149470468.html +++ b/docs/ecs/umn/en-us_topic_0149470468.html @@ -1,6 +1,6 @@ --Parent topic: Logins Through the Management Console+Parent topic: VNC LoginInstalling a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS
+Manually Installing a Tesla Driver on a GPU-accelerated ECS
Scenarios
Before using a GPU-accelerated ECS, make sure that the desired Tesla driver and CUDA toolkit have been installed on the ECS for computing acceleration.
- A computing-accelerated (P series) ECS created using a Windows public image has had a Tesla driver of a specified version installed by default.
- A computing-accelerated (P series) ECS created using a Linux public image does not have a Tesla driver installed by default. After the ECS is created, install a driver on it for computing acceleration.
- After a GPU-accelerated ECS is created using a private image, it must have a Tesla driver installed. Otherwise, computing acceleration will not take effect.
This section describes how to install a Tesla driver and CUDA toolkit on a GPU-accelerated ECS.
@@ -65,14 +65,14 @@ options nouveau modeset=0Installing the CUDA Toolkit on a Linux ECS
The following uses Ubuntu 16.04 64bit as an example to describe how to install the CUDA 10.1 toolkit on a GPU-accelerated ECS.
-- Log in to the ECS.
- Update the system software based on the OS.
- Ubuntu
Update the software installation source: apt-get -y update
-Install necessary programs: apt-get install gcc g++ make
- - CentOS
Update the software installation source: yum -y update --exclude=kernel* --exclude=centos-release* --exclude=initscripts*
+- Log in to the ECS.
- Update the system software based on the OS.
- Ubuntu
Update the software installation source: apt-get -y update
+Install necessary programs: apt-get install gcc g++ make
+ - CentOS
Update the software installation source: yum -y update --exclude=kernel* --exclude=centos-release* --exclude=initscripts*
Install the desired program: yum install -y kernel-devel-`uname -r` gcc gcc-c++
- Ubuntu
- On the CUDA download page, set parameters according to the information shown in Obtaining a Tesla Driver and CUDA Toolkit.Figure 16 Selecting a CUDA version
- Find the link for downloading CUDA 10.1 and copy the link.Figure 17 Copying the link for downloading CUDA-
- Run the following command on the ECS to download CUDA:
wget Copied link
+
- Run the following command on the ECS to download CUDA:
wget Copied link
For example, wget https://developer.nvidia.com/compute/cuda/10.1/Prod/local_installers/cuda_10.1.105_418.39_linux.run
Figure 18 Downloading CUDA
- Install CUDA.Follow the instructions provided on the official NVIDIA website.Figure 19 Installing CUDAdiff --git a/docs/ecs/umn/en-us_topic_0149610914.html b/docs/ecs/umn/en-us_topic_0149610914.html index f1db85d0..fe70c626 100644 --- a/docs/ecs/umn/en-us_topic_0149610914.html +++ b/docs/ecs/umn/en-us_topic_0149610914.html @@ -102,7 +102,7 @@
Deploying and Configuring the License Server
The following uses an ECS running CentOS 7.5 as an example to describe how to deploy and configure the license server on the ECS.
- - The target ECS must have at least 2 vCPUs and 4 GiB of memory.
- Ensure that the MAC address of the target ECS has been recorded.
- If the license server is used in the production environment, deploy it in high availability mode. For details, see official NVIDIA documentation for license server high availability.
- Configure the network.
- If the license server is to be accessed using the VPC, ensure that the license server and the GPU-accelerated ECS with the GRID driver installed are in the same VPC subnet.
- If the license server is to be accessed using a public IP address, configure the security group which license server belongs to and add inbound rules for TCP 7070 and TCP 8080.
- Configure the network.
- If the license server is to be accessed using the VPC, ensure that the license server and the GPU-accelerated ECS with the GRID driver installed are in the same VPC subnet.
- If the license server is to be accessed using a public IP address, configure the security group which the license server belongs to and add inbound rules for TCP 7070 and TCP 8080.
- Install the license server.
- Run the following command to decompress the installation package. The Installer.zip in the command indicates the name of the software package obtained in 10.
unzip Installer.zip
- Run the following command to assign execution permissions to the installer:
- Run the installer as user root:
sudo ./setup.bin -i console
diff --git a/docs/ecs/umn/en-us_topic_0152643976.html b/docs/ecs/umn/en-us_topic_0152643976.html index d6c32ae6..a3c7a382 100644 --- a/docs/ecs/umn/en-us_topic_0152643976.html +++ b/docs/ecs/umn/en-us_topic_0152643976.html @@ -23,7 +23,7 @@ lrwxrwxrwx. 1 root root 10 Nov 16 19:40 virtio-842dbfd3-9f2c-4273-9-part1 ->
- Run the following command to decompress the installation package. The Installer.zip in the command indicates the name of the software package obtained in 10.
diff --git a/docs/ecs/umn/en-us_topic_0155136013.html b/docs/ecs/umn/en-us_topic_0155136013.html index 01874c0b..74969790 100644 --- a/docs/ecs/umn/en-us_topic_0155136013.html +++ b/docs/ecs/umn/en-us_topic_0155136013.html @@ -1,8 +1,11 @@ --Parent topic: Disk Management+Parent topic: Disk Partition, Attachment, and Expansion FAQGUI Installation FAQs
-+ +OS FAQ
+ ++- Do ECSs Support GUI?
diff --git a/docs/ecs/umn/en-us_topic_0155136016.html b/docs/ecs/umn/en-us_topic_0155136016.html index af0b61fd..a795771a 100644 --- a/docs/ecs/umn/en-us_topic_0155136016.html +++ b/docs/ecs/umn/en-us_topic_0155136016.html @@ -97,7 +97,7 @@ Alias=myservice.service
diff --git a/docs/ecs/umn/en-us_topic_0160672219.html b/docs/ecs/umn/en-us_topic_0160672219.html index 45e2f724..370ace05 100644 --- a/docs/ecs/umn/en-us_topic_0160672219.html +++ b/docs/ecs/umn/en-us_topic_0160672219.html @@ -6,7 +6,7 @@-Parent topic: GUI Installation FAQs+Parent topic: OS FAQdiff --git a/docs/ecs/umn/en-us_topic_0163572591.html b/docs/ecs/umn/en-us_topic_0163572591.html index 98b6b152..a4713981 100644 --- a/docs/ecs/umn/en-us_topic_0163572591.html +++ b/docs/ecs/umn/en-us_topic_0163572591.html @@ -24,7 +24,7 @@-Parent topic: ECS Creation+Parent topic: ECS Creation FAQ- To use functions listed in Advanced Options, select Configure now. Otherwise, do not select it.
- User Data
You can specify the user data. The user data will be automatically passed to the ECS when the ECS starts for the first time. This configuration is optional.
- As text: allows you to enter the user data in the text box.
- As file: enables the text to automatically inject a script file or other files into a specified directory on an ECS when you create the ECS.
For example, if you activate user root permission by passing a script file to an ECS, you can log in to the ECS as user root.
-For detailed operations, see Passing User Data to ECSs.
+For detailed operations, see Passing User Data.
- Tag
This configuration is optional. You can tag an ECS to facilitate identification and management. You can add up to 10 tags to an ECS.
Tags added during ECS creation will also be added to the created EIP and EVS disks (including the system disk and data disks) of the ECS. If the ECS uses an existing EIP, the tags will not be added to the EIP.
After creating the ECS, you can view the tags on the pages providing details about the ECS, EIP, and EVS disks.
diff --git a/docs/ecs/umn/en-us_topic_0166284970.html b/docs/ecs/umn/en-us_topic_0166284970.html index 0c0d93bf..679273ac 100644 --- a/docs/ecs/umn/en-us_topic_0166284970.html +++ b/docs/ecs/umn/en-us_topic_0166284970.html @@ -19,7 +19,7 @@diff --git a/docs/ecs/umn/en-us_topic_0166284971.html b/docs/ecs/umn/en-us_topic_0166284971.html index 86649aaa..ffc4a2b4 100644 --- a/docs/ecs/umn/en-us_topic_0166284971.html +++ b/docs/ecs/umn/en-us_topic_0166284971.html @@ -17,7 +17,7 @@-Parent topic: File Upload/Data Transfer+Parent topic: File Upload/Data Transfer FAQdiff --git a/docs/ecs/umn/en-us_topic_0167429328.html b/docs/ecs/umn/en-us_topic_0167429328.html index 799dc191..a9705e6c 100644 --- a/docs/ecs/umn/en-us_topic_0167429328.html +++ b/docs/ecs/umn/en-us_topic_0167429328.html @@ -23,9 +23,9 @@-Parent topic: File Upload/Data Transfer+Parent topic: File Upload/Data Transfer FAQTroubleshooting
Before the troubleshooting, check whether the processes or drivers leading to the high CPU or bandwidth usage are normal, and handle the issue accordingly.
Suggestions for non-malicious processes
- If your ECS runs Windows Server 2008 or 2012, ensure that the available memory is 2 GiB or larger.
- Check whether Windows Update is running.
- Check whether the antivirus software is scanning files and programs on the backend.
- Check whether any applications requiring high CPU or bandwidth resources are running on the ECS. If yes, modify ECS specifications or increase bandwidth.
- If the ECS configuration meets the application requirements, deploy applications separately. For example, deploy the database and applications separately.
Suggestions for malicious processes
+Suggestions for malicious processes
If the high CPU or bandwidth usage is caused by viruses or Trojan horses, manually stop the affected processes. You are advised to troubleshoot the issue as follows:
-- Use the commercial-edition antivirus software or install Microsoft Safety Scanner to scan for viruses in security mode.
- Install the latest patches for Windows.
- Run MSconfig to disable all drivers that are not delivered with Microsoft and check whether the fault is rectified. For details, see How to perform a clean boot in Windows.
- Use the commercial-edition antivirus software or install Microsoft Safety Scanner to scan for viruses in security mode.
- Install the latest patches for Windows.
- Run MSconfig to disable all drivers that are not delivered with Microsoft and check whether the fault is rectified. For details, see the official Microsoft document How to perform a clean boot in Windows.
Suggestions for drivers from unknown sources
Some viruses and Trojan horses are loaded through the filter drivers of the system. If you find a driver from an unknown source, you are advised to uninstall it. You can also use commercial antivirus software or third-party security management tools to delete it.
If an unknown driver cannot be deleted, or will appear again after being deleted, it is usually a virus or Trojan horse driver. If the driver cannot be completely deleted using commercial antivirus software or third-party security management tools, you are advised to reinstall the OS and back up data before the reinstallation.
@@ -33,7 +33,7 @@diff --git a/docs/ecs/umn/en-us_topic_0167429329.html b/docs/ecs/umn/en-us_topic_0167429329.html index 20b43f61..e45dadbc 100644 --- a/docs/ecs/umn/en-us_topic_0167429329.html +++ b/docs/ecs/umn/en-us_topic_0167429329.html @@ -63,7 +63,7 @@-Parent topic: Resource Monitoring+Parent topic: Slow ECS Response FAQ
diff --git a/docs/ecs/umn/en-us_topic_0170135967.html b/docs/ecs/umn/en-us_topic_0170135967.html index a589e99e..a4de30c6 100644 --- a/docs/ecs/umn/en-us_topic_0170135967.html +++ b/docs/ecs/umn/en-us_topic_0170135967.html @@ -1,6 +1,6 @@ --Parent topic: Resource Monitoring+Parent topic: Slow ECS Response FAQFile Upload/Data Transfer
+File Upload/Data Transfer FAQ
-
diff --git a/docs/ecs/umn/en-us_topic_0170139796.html b/docs/ecs/umn/en-us_topic_0170139796.html
index 2a019e26..a30332f8 100644
--- a/docs/ecs/umn/en-us_topic_0170139796.html
+++ b/docs/ecs/umn/en-us_topic_0170139796.html
@@ -40,7 +40,7 @@ X11Forwarding no
diff --git a/docs/ecs/umn/en-us_topic_0170139797.html b/docs/ecs/umn/en-us_topic_0170139797.html index 538f781c..cb6769e8 100644 --- a/docs/ecs/umn/en-us_topic_0170139797.html +++ b/docs/ecs/umn/en-us_topic_0170139797.html @@ -12,7 +12,7 @@-Parent topic: File Upload/Data Transfer+Parent topic: File Upload/Data Transfer FAQ
- Ubuntu
diff --git a/docs/ecs/umn/en-us_topic_0170139798.html b/docs/ecs/umn/en-us_topic_0170139798.html index ff16e09c..5c8d5baa 100644 --- a/docs/ecs/umn/en-us_topic_0170139798.html +++ b/docs/ecs/umn/en-us_topic_0170139798.html @@ -8,7 +8,7 @@-Parent topic: File Upload/Data Transfer+Parent topic: File Upload/Data Transfer FAQPossible Causes
When NAT is enabled on the FTP server, the FTP client must connect to the FTP server in passive mode. In such a case, the public IP address (EIP) of the server cannot be accessed from the router. You need to add the EIP to the public IP address list on the server. Additionally, set the port range to limit the number of ports with data forwarded by the router.
Solution
The EIP must be associated with the private IP address using NAT, so the server must be configured accordingly.
-- Configure the public IP address of the server.
+
- Set the public IP address of the server.
Figure 1 Setting the public IP address
- Choose Passive mode settings, set the port range (for example, 50000-50100) for transmitting data, and enter the target EIP.Figure 2 Setting the range of ports for data transmission
- Click OK.
- Allow traffic on TCP ports 50000-50100 and 21 in the security group in the inbound direction.
- Test the connection on the client.
- Set the public IP address of the server.
diff --git a/docs/ecs/umn/en-us_topic_0170158381.html b/docs/ecs/umn/en-us_topic_0170158381.html index e5287b9f..32cb5932 100644 --- a/docs/ecs/umn/en-us_topic_0170158381.html +++ b/docs/ecs/umn/en-us_topic_0170158381.html @@ -6,7 +6,7 @@-Parent topic: File Upload/Data Transfer+Parent topic: File Upload/Data Transfer FAQdiff --git a/docs/ecs/umn/en-us_topic_0170232209.html b/docs/ecs/umn/en-us_topic_0170232209.html index 3fead162..682bf891 100644 --- a/docs/ecs/umn/en-us_topic_0170232209.html +++ b/docs/ecs/umn/en-us_topic_0170232209.html @@ -270,7 +270,7 @@-Parent topic: ECS Deletion+Parent topic: ECS Deletion and Unsubscription FAQ - CentOS 6.x:
- Run the following command to access /etc/netplan/:
- Ubuntu 18.04/20.04
- IAM Service Overview
- Creating a User and Granting ECS Permissions
- Permissions Policies and Supported Actions in Elastic Cloud Server API Reference
- IAM Service Overview
- Creating a User and Granting ECS Permissions
- Permissions Policies and Supported Actions in Elastic Cloud Server API Reference
- Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing ECS resources.
- Grant only the permissions required for users to perform a specific task.
- Delegate access to other accounts or cloud services for efficient O&M.
- Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing ECS resources.
- Grant only the permissions required for users to perform a specific task.
- Delegate access to other accounts or cloud services for efficient O&M.
- Create a user group and assign permissions.
Create a user group on the IAM console and assign the ECS ReadOnlyAccess permissions to the group.
- Create a user and add the user to the user group.
Create a user on the IAM console and add the user to the group created in 1.
- Log in to the management console as the created user.
In the authorized region, perform the following operations:
-- Choose Compute > Elastic Cloud Server in Service List. On the ECS console, click Create ECS. If the creation attempt failed, the ECSReadOnlyAccess policy has already taken effect.
- Choose any service other than ECS in Service List. If a message appears indicating that you have insufficient permissions to access the service, the ECSReadOnlyAccess policy has already taken effect.
- Choose Compute > Elastic Cloud Server in the service list. On the ECS console, click Create ECS. If the creation attempt failed, the ECSReadOnlyAccess policy has already taken effect.
- Choose any service other than ECS in the service list. If a message appears indicating that you have insufficient permissions to access the service, the ECSReadOnlyAccess policy has already taken effect.
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
- Changing ECS Names
- - Migrating an ECS
+ - Migrating an ECS to a DeH
- Managing ECS Groups
- Obtaining ECS Console Logs
- - (Optional) Configuring Mapping Between Hostnames and IP Addresses
+ - Configuring Mapping Between Hostnames and IP Addresses in the Same VPC
- Starting and Stopping ECSs
diff --git a/docs/ecs/umn/en-us_topic_0177457773.html b/docs/ecs/umn/en-us_topic_0177457773.html
index cc9fc5ff..21ad31e5 100644
--- a/docs/ecs/umn/en-us_topic_0177457773.html
+++ b/docs/ecs/umn/en-us_topic_0177457773.html
@@ -1,7 +1,7 @@
EIP
+EIPs
diff --git a/docs/ecs/umn/en-us_topic_0140323154.html b/docs/ecs/umn/en-us_topic_0140323154.html index 11b57823..6218fea8 100644 --- a/docs/ecs/umn/en-us_topic_0140323154.html +++ b/docs/ecs/umn/en-us_topic_0140323154.html @@ -7,7 +7,7 @@-- Table 1 describes the rules in the default security group.
+Table 1 describes the rules in the default security group.
Table 1 Default security group rules Direction
Helpful Links
Helpful Links
ECS FullAccess Policy Content
{ "Version": "1.1", @@ -325,19 +325,9 @@ "ecs:*:start", "ecs:*:stop", "ecs:*:reboot", - "ecs:blockDevice:use", - "ecs:cloudServerFpgaImages:relate", - "ecs:cloudServerFpgaImages:register", - "ecs:cloudServerFpgaImages:delete", - "ecs:cloudServerFpgaImags:unrelate", - "ecs:cloudServers:setAutoRecovery", - "ecs:cloudServerPasswords:reset", - "ecs:cloudServerPorts:modify", - "ecs:cloudServers:vnc", "ecs:diskConfigs:use", "ecs:securityGroups:use", "ecs:serverGroups:manage", - "ecs:serverFloatingIps:use", "ecs:serverKeypairs:*", "ecs:serverPasswords:manage", "ecs:servers:createConsole", diff --git a/docs/ecs/umn/en-us_topic_0170265913.html b/docs/ecs/umn/en-us_topic_0170265913.html index 1cb89e2f..7d34d488 100644 --- a/docs/ecs/umn/en-us_topic_0170265913.html +++ b/docs/ecs/umn/en-us_topic_0170265913.html @@ -2,8 +2,8 @@Creating a User and Granting ECS Permissions
diff --git a/docs/ecs/umn/en-us_topic_0170265914.html b/docs/ecs/umn/en-us_topic_0170265914.html index c83f4869..b323bbc8 100644 --- a/docs/ecs/umn/en-us_topic_0170265914.html +++ b/docs/ecs/umn/en-us_topic_0170265914.html @@ -1,7 +1,7 @@Use IAM to implement fine-grained permissions control over your ECSs. With IAM, you can:
-If your account does not need individual IAM users, skip this section.
+If your account does not require individual IAM users, you can skip this section.
This section describes the procedure for granting permissions (see Process Flow).
Prerequisites
Before assigning permissions to user groups, you should learn about system policies supported by ECS and select the policies based on service requirements.
For more information about system policies supported by ECS, see Permissions Management.
@@ -13,7 +13,7 @@ECS Custom Policies
-diff --git a/docs/ecs/umn/en-us_topic_0176502615.html b/docs/ecs/umn/en-us_topic_0176502615.html index 92c21f97..b6cbcde4 100644 --- a/docs/ecs/umn/en-us_topic_0176502615.html +++ b/docs/ecs/umn/en-us_topic_0176502615.html @@ -1,6 +1,6 @@ -Custom policies can be created to supplement the system-defined policies of ECS. For the actions that can be added to custom policies, see "Permissions Policies and Supported Actions" in "Elastic Cloud Server API Reference".
+Custom policies can be created to supplement the system-defined policies of ECS. For the actions that can be added to custom policies, see "Permissions and Supported Actions" in "Elastic Cloud Server API Reference".
You can create custom policies in either of the following ways:
For details, see Creating a Custom Policy. The following provides examples of common ECS custom policies.
diff --git a/docs/ecs/umn/en-us_topic_0170880184.html b/docs/ecs/umn/en-us_topic_0170880184.html index b1e5445c..d2cf9fe7 100644 --- a/docs/ecs/umn/en-us_topic_0170880184.html +++ b/docs/ecs/umn/en-us_topic_0170880184.html @@ -6,7 +6,7 @@diff --git a/docs/ecs/umn/en-us_topic_0174917535.html b/docs/ecs/umn/en-us_topic_0174917535.html index 1efa1f6b..6fac8e2e 100644 --- a/docs/ecs/umn/en-us_topic_0174917535.html +++ b/docs/ecs/umn/en-us_topic_0174917535.html @@ -14,7 +14,7 @@-Parent topic: ECS Creation+Parent topic: ECS Creation FAQManaging ECSs
+Managing ECS Configurations
@@ -11,13 +11,13 @@Overview
-Image
An image is an ECS or BMS template that contains an OS or service data. It may also contain proprietary software and application software, such as database software. Images are classified into public, private, and shared images.
+Image
An image is an ECS or BMS template that contains an OS or service data. It may also contain proprietary software and application software, such as database software. Images are classified into public, private, and shared images.
Image Management Service (IMS) allows you to easily create and manage images. You can create an ECS using a public image, private image, or shared image. You can also use an existing ECS or external image file to create a private image.
Public Image
A public image is a standard, widely used image that contains a common OS, such as Ubuntu, CentOS, or Debian, and preinstalled public applications. This image is available to all users. Select your desired public image. Alternatively, create a private image based on a public image to copy an existing ECS or rapidly create ECSs in a batch. You can customize a public image by configuring the application environment or software.
diff --git a/docs/ecs/umn/en-us_topic_0177512565.html b/docs/ecs/umn/en-us_topic_0177512565.html index b7a5d189..957624c1 100644 --- a/docs/ecs/umn/en-us_topic_0177512565.html +++ b/docs/ecs/umn/en-us_topic_0177512565.html @@ -2906,218 +2906,341 @@Ultra-high I/O
-Table 13 I3 ECS specifications Flavor
++ +
+Table 13 I3m ECS specifications Flavor
vCPUs
+vCPUs
Memory
-(GiB)
+Memory
+(GiB)
Max./Assured Bandwidth
-(Gbit/s)
+Max./Assured Bandwidth
+(Gbit/s)
Max. PPS
-(10,000)
+Max. PPS
+(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Local Disks
+(GiB)
Local Disks
-(GiB)
+Max. NICs
Virtualization
+Virtualization
i3.2xlarge.4
+i3m.2xlarge.8
8
+8
32
+64
15/4.5
+2.5/2.5
150
+100
4
+4
4
+1 × 1,600 GiB NVMe
1 × 3,200 GiB NVMe
+4
KVM
+KVM
i3.4xlarge.4
+i3m.4xlarge.8
16
+16
64
+128
20/9
+5/5
280
+150
8
+4
8
+2 × 1,600 GiB NVMe
2 × 3,200 GiB NVMe
+8
KVM
+KVM
i3.8xlarge.4
+i3m.8xlarge.8
32
+32
128
+256
30/18
+10/10
550
+200
16
+8
8
+4 × 1,600 GiB NVMe
4 × 3,200 GiB NVMe
+8
KVM
+KVM
i3.12xlarge.4
+i3m.12xlarge.8
48
+48
192
+384
35/27
+15/15
750
+240
16
+8
8
+6 × 1,600 GiB NVMe
6 × 3,200 GiB NVMe
+8
KVM
+KVM
i3.16xlarge.4
+i3m.16xlarge.8
64
+64
256
+512
40/32
+25/25
1,000
+500
32
+16
8
+8 × 1,600 GiB NVMe
8 × 3,200 GiB NVMe
+8
KVM
+KVM
i3.2xlarge.8
+Table 14 I3 ECS specifications Flavor
+vCPUs
+Memory
+(GiB)
+Max./Assured Bandwidth
+(Gbit/s)
+Max. PPS
+(10,000)
+Max. NIC Queues
+Max. NICs
+Local Disks
+(GiB)
+Virtualization
+i3.2xlarge.4
8
+8
64
+32
15/4.5
+15/4.5
150
+150
4
+4
4
+4
1 × 3,200 GiB NVMe
+1 × 3,200 GiB NVMe
KVM
+KVM
i3.4xlarge.8
+i3.4xlarge.4
16
+16
128
+64
20/9
+20/9
280
+280
8
+8
8
+8
2 × 3,200 GiB NVMe
+2 × 3,200 GiB NVMe
KVM
+KVM
i3.8xlarge.8
+i3.8xlarge.4
32
+32
256
+128
30/18
+30/18
550
+550
16
+16
8
+8
4 × 3,200 GiB NVMe
+4 × 3,200 GiB NVMe
KVM
+KVM
i3.12xlarge.8
+i3.12xlarge.4
48
+48
384
+192
35/27
+35/27
750
+750
16
+16
8
+8
6 × 3,200 GiB NVMe
+6 × 3,200 GiB NVMe
KVM
+KVM
i3.16xlarge.8
+i3.16xlarge.4
64
+64
512
+256
40/32
+40/32
1,000
+1,000
32
+32
8
+8
8 × 3,200 GiB NVMe
+8 × 3,200 GiB NVMe
KVM
+KVM
+i3.2xlarge.8
+8
+64
+15/4.5
+150
+4
+4
+1 × 3,200 GiB NVMe
+KVM
+i3.4xlarge.8
+16
+128
+20/9
+280
+8
+8
+2 × 3,200 GiB NVMe
+KVM
+i3.8xlarge.8
+32
+256
+30/18
+550
+16
+8
+4 × 3,200 GiB NVMe
+KVM
+i3.12xlarge.8
+48
+384
+35/27
+750
+16
+8
+6 × 3,200 GiB NVMe
+KVM
+i3.16xlarge.8
+64
+512
+40/32
+1,000
+32
+8
+8 × 3,200 GiB NVMe
+KVM
GPU-accelerated
-Table 14 G7 ECS specifications Flavor
+-Table 15 G7 ECS specifications Flavor
vCPUs
Table 15 G6 ECS specifications Flavor
+-Table 16 G6 ECS specifications Flavor
vCPUs
Table 16 P3 ECS specifications Flavor
+Table 17 P3 ECS specifications
- Method 1 (recommended)
- In the Initialize Disk dialog box, the to-be-initialized disk is selected. Select a disk partition style and click OK. In this example, GPT (GUID Partition Table) is selected.
- Method 1: Run the echo command in /proc/sys to modify the file for the target kernel parameters.
- After a P2v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- After a P2s ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- After a P3 ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- Table 7 lists the OSs supported by ultra-high I/O ECSs.
+
- VNC
- Login Overview (Windows)
Procedure
Disk Management
+Disk Partition, Attachment, and Expansion FAQ
-
diff --git a/docs/ecs/umn/en-us_topic_0018124788.html b/docs/ecs/umn/en-us_topic_0018124788.html
index 52e68a47..61d6ff83 100644
--- a/docs/ecs/umn/en-us_topic_0018124788.html
+++ b/docs/ecs/umn/en-us_topic_0018124788.html
@@ -1,6 +1,6 @@
-
OS Management
+OS Change FAQ
-
diff --git a/docs/ecs/umn/en-us_topic_0018124789.html b/docs/ecs/umn/en-us_topic_0018124789.html
index cbcf848c..4b95b73a 100644
--- a/docs/ecs/umn/en-us_topic_0018124789.html
+++ b/docs/ecs/umn/en-us_topic_0018124789.html
@@ -1,6 +1,6 @@
-
Database Applications
+Application Deployment and Software Installation FAQ
-
diff --git a/docs/ecs/umn/en-us_topic_0018196896.html b/docs/ecs/umn/en-us_topic_0018196896.html
index 7ecd7907..eb3924fb 100644
--- a/docs/ecs/umn/en-us_topic_0018196896.html
+++ b/docs/ecs/umn/en-us_topic_0018196896.html
@@ -1,11 +1,11 @@
-
Regions and AZs
+Region and AZ FAQ
-
-
What Is an AZ?
-AZ
An availability zone (AZ) is a physical region where resources use independent power supplies and networks. AZs are physically isolated but interconnected through an internal network.
+What Is AZ and How Can I Select and View an AZ?
+What Is an AZ?
An availability zone (AZ) is a physical region where resources use independent power supplies and networks. AZs are physically isolated but interconnected through an internal network.
There are multiple AZs in each region. If one AZ becomes faulty, other AZs in the same region continue to provide services.
AZs in the same region can communicate with each other through an internal network.
Selecting an AZ
You can select an AZ when you are purchasing an ECS. After the ECS is created, the AZ cannot be changed. If there is only one AZ displayed in a region, it means the region only provides one AZ.
+How Do I Select an AZ
You can select an AZ when you are purchasing an ECS. After the ECS is created, the AZ cannot be changed. If there is only one AZ displayed in a region, it means the region only provides one AZ.
Why Does an Authentication Failure Occurs After I Attempt to Remotely Log In to a Windows ECS?
Symptom
When a local computer running Windows attempts to access a Windows ECS using RDP (for example, MSTSC), an identity authentication failure occurs and the desired function is not supported.
-
Solution
Modify the remote desktop connection settings on the Windows ECS:
diff --git a/docs/ecs/umn/en-us_topic_0019883415.html b/docs/ecs/umn/en-us_topic_0019883415.html index 152f460a..e95a9c0d 100644 --- a/docs/ecs/umn/en-us_topic_0019883415.html +++ b/docs/ecs/umn/en-us_topic_0019883415.html @@ -6,7 +6,7 @@The method described in this section can only be used to change the password of a local Windows account, but not the password of a domain account.
