Scenarios
CBR enhances data integrity and service continuity. For example, if an ECS or a 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.
-- 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.
- Cloud Server Backup (recommended): Use this backup function if you want to back up the data of all EVS disks (system and data disks) on an ECS. This prevents data inconsistency caused by time difference in creating a backup.
- Cloud Disk Backup: Use this backup function if you want to back up the data of one or more EVS disks (system or data disk) on an ECS. This minimizes backup costs on the basis of data security.
ECS Backup Procedure
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, click Elastic Cloud Server.
- Locate the row that contains the target ECS. Click More in the Operation column and select Manage Image/Disk > Create Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the ECS to be associated. The storage capacity used by the backup increases accordingly.
-ECS Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Locate the row that contains the target ECS. Click More in the Operation column and select Manage Image/Disk > Create Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the ECS to be associated. The storage capacity used by the backup increases accordingly.
- If the ECS is not associated with a vault, buy a vault first and then configure the backup information as prompted.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Click OK. The system automatically creates a backup for the ECS.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
The ECS can be restarted if the backup progress of an ECS exceeds 10%. However, to ensure data integrity, restart it after the backup is complete.
EVS Disk Backup 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. Click More in the Operation column and select Create Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default. Click
to view the disks attached to the ECSs. Select the disks to be backed up. - Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the disks to be associated. The storage capacity used by the backup increases accordingly.
EVS Disk Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Locate the row that contains the target ECS. Click More in the Operation column and select Create Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default. Click to view the disks attached to the ECSs. Select the disks to be backed up.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the disks to be associated. The storage capacity used by the backup increases accordingly.
- Server List: The ECS to be backed up is selected by default. Click
- If the ECS is not associated with a vault, buy a vault first and then configure the backup information as prompted.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Click OK. The system automatically creates a backup for the disk.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
diff --git a/docs/ecs/umn/en-us_topic_0000001210881033.html b/docs/ecs/umn/en-us_topic_0000001210881033.html index ae018dd0e..7a92a6363 100644 --- a/docs/ecs/umn/en-us_topic_0000001210881033.html +++ b/docs/ecs/umn/en-us_topic_0000001210881033.html @@ -10,7 +10,7 @@
-How Do I Apply for a Higher Quota?
The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.
Before dialing the hotline number or sending an email, make sure that the following information has been obtained:
-- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
+- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
- Quota information, which includes:
- Service name
- Quota type
- Required quota
Learn how to obtain the service hotline and email address.
diff --git a/docs/ecs/umn/en-us_topic_0000001234175322.html b/docs/ecs/umn/en-us_topic_0000001234175322.html new file mode 100644 index 000000000..37019601b --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0000001234175322.html @@ -0,0 +1,27 @@ + + + +Key Pairs
+ +++ +++ diff --git a/docs/ecs/umn/en-us_topic_0000001234183498.html b/docs/ecs/umn/en-us_topic_0000001234183498.html new file mode 100644 index 000000000..f6ee1f11c --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0000001234183498.html @@ -0,0 +1,18 @@ + + +-
+
- Application Scenarios for Using Key Pairs
+
+ - (Recommended) Creating a Key Pair on the Management Console
+
+ - Creating a Key Pair Using PuTTYgen
+
+ - Importing a Key Pair
+
+ - Obtaining and Deleting the Password of an Windows ECS
+
+
++Parent topic: Passwords and Key Pairs+Obtaining and Deleting the Password of an Windows ECS
+++++ diff --git a/docs/ecs/umn/en-us_topic_0000001234335274.html b/docs/ecs/umn/en-us_topic_0000001234335274.html new file mode 100644 index 000000000..802f5111b --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0000001234335274.html @@ -0,0 +1,42 @@ + + +-
+
- Obtaining the Password for Logging In to a Windows ECS
+
+ - Deleting the Initial Password for Logging In to a Windows ECS
+
+
++Parent topic: Key Pairs+Creating a Key Pair Using PuTTYgen
+++Scenarios
You can use PuTTYgen to create a key pair and store 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.
++Procedure
- Download and install PuTTY and PuTTYgen.
https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
++ PuTTYgen is a key generator, which is used to create a key pair that consists of a public key and a private key for PuTTY.
+ - Obtain the public and private keys.
- Double-click puttygen.exe to open PuTTY Key Generator.Figure 1 PuTTY Key Generator+
- Click Generate.
The key generator automatically generates a key pair that consists of a public key and a private key. The content shown in the red box in Figure 2 is the public key.
+ +
- Double-click puttygen.exe to open PuTTY Key Generator.
- 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: +
- 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.
+Figure 4 Saving a private key+
- Save the private key, for example, kp-123.pem, locally.
- Choose Conversions > Export OpenSSH key.
- After you have saved the key pair, import your public key to the ECS by referring to Importing a Key Pair.
++ + + \ No newline at end of file diff --git a/docs/ecs/umn/en-us_topic_0000001278335673.html b/docs/ecs/umn/en-us_topic_0000001278335673.html new file mode 100644 index 000000000..0048e495f --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0000001278335673.html @@ -0,0 +1,34 @@ + + +++Parent topic: Key Pairs+Application Scenarios for Using Key Pairs
+++Key Pairs
Key pairs are a set of security credentials for identity authentication when you remotely log in to ECSs.
+A key pair consists of a public key and a private key. ECS 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. Therefore, 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 creating an 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 Windows ECS
You can use the key pair to obtain a password for login. The password is randomly generated and therefore is more secure.
+For details, see Obtaining the Password for Logging In to a Windows ECS.
+
+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.
+
- 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 the public key for you.
++ If the public key of the existing key pair is stored by clicking Save public key on PuTTY Key Generator, the public key cannot be imported to the management console.
+If you want to use this existing key pair for remote login, see Why Does a Key Pair Created Using puttygen.exe Fail to Be Imported on the Management Console?
+
+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.
++ diff --git a/docs/ecs/umn/en-us_topic_0000001278350057.html b/docs/ecs/umn/en-us_topic_0000001278350057.html new file mode 100644 index 000000000..53d5a8305 --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0000001278350057.html @@ -0,0 +1,17 @@ + + +++Parent topic: Key Pairs+(Recommended) Creating a Key Pair on the Management Console
+++Scenarios
You can use the management console to create a key pair. ECS stores the public key and you store the private key.
++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 Create Key Pair.
- Enter a key pair name and click OK.
The default key pair name consists of KeyPair- and four random characters in the "KeyPair-xxxx" format. Change it to an easy-to-remember one, for example, KeyPair-xxxx_ecs.
+ - Manually or automatically download a .pem private key file with the name that you specify as the key name. Store it in a secure place and click OK.+
This is the only chance for you to save the private key file. Keep it secure. You'll need to provide the key pair name when you create an ECS, and the corresponding private key each time you connect to the ECS through SSH.
+
++ diff --git a/docs/ecs/umn/en-us_topic_0000001278734873.html b/docs/ecs/umn/en-us_topic_0000001278734873.html new file mode 100644 index 000000000..ece50c0c9 --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0000001278734873.html @@ -0,0 +1,35 @@ + + +++Parent topic: Key Pairs+Importing a Key Pair
+++Scenarios
You need to import a key pair in either of the following scenarios:
+- Create a key pair using PuTTYgen and import the public key to the ECS.
- Import the public key of an existing key pair to the ECS to let the system maintain your public key.+
If the public key of the existing key pair is stored by clicking Save public key on PuTTY Key Generator, the public key cannot be imported to the management console.
+If you want to use this existing key pair for remote login, see Why Does a Key Pair Created Using puttygen.exe Fail to Be Imported on the Management Console?
+
+ +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).+
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 PuTTYgen).
- Copying the public key content
- Copy the public key content from the locally stored .txt file into the Public Key Content text box.
- Click OK.
- Selecting a file
++ + + \ No newline at end of file diff --git a/docs/ecs/umn/en-us_topic_0000001351167793.html b/docs/ecs/umn/en-us_topic_0000001351167793.html new file mode 100644 index 000000000..545ec846d --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0000001351167793.html @@ -0,0 +1,17 @@ + + +++Parent topic: Key Pairs+Images
+ +++ diff --git a/docs/ecs/umn/en-us_topic_0013771092.html b/docs/ecs/umn/en-us_topic_0013771092.html index bd4e73e16..cd6120e74 100644 --- a/docs/ecs/umn/en-us_topic_0013771092.html +++ b/docs/ecs/umn/en-us_topic_0013771092.html @@ -8,9 +8,9 @@-
+
- Image Types
+
+ - Cloud-Init
+
+
++Parent topic: Service Overview+- 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.
- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Notes
- If ECS specifications are downgraded, the ECS performance will deteriorate.
- Certain ECSs do not support specifications modification currently. For details about available ECS types as well as their functions and usage, see "Notes" in ECS Types.
- 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
- If ECS specifications are downgraded, the ECS performance will deteriorate.
- Certain ECS types do not support specifications modification currently. For details about available ECS types as well as their functions and usage, see "Notes" in ECS Types.
- 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.
+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.
- Select the new ECS type, vCPUs, and memory as prompted.
- (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.
@@ -26,7 +26,7 @@
diff --git a/docs/ecs/umn/en-us_topic_0013771112.html b/docs/ecs/umn/en-us_topic_0013771112.html index e978ac716..6f405a893 100644 --- a/docs/ecs/umn/en-us_topic_0013771112.html +++ b/docs/ecs/umn/en-us_topic_0013771112.html @@ -3,6 +3,7 @@Follow-up Procedure
Perform the following operations in the event of a specifications modification failure:
-- Log in to the management console.
- Under Management & Deployment, click 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, click 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.
What Is ECS?
An Elastic Cloud Server (ECS) is a basic computing unit that consists of vCPUs, memory, OS, and Elastic Volume Service (EVS) disks. After an ECS is created, you can use it on the cloud similarly to how you would use your local PC or physical server.
ECSs support self-service creation, modification, and operation. You can create an ECS by specifying its vCPUs, memory, OS, and login mode. After an ECS is created, you can modify its specifications if necessary. ECS works with other services to provide a reliable, secure, efficient computing environment.
+- For details about the operating systems supported by ECS, see Image Types.
- For details about login modes, see Logging In to an ECS.
System Architecture
ECS works with other products and services to provide computing, storage, and network resources. You can quickly migrate and replicate existing ECSs using images.
- ECSs can be deployed in multiple availability zones (AZs) connected with each other through an internal network. If one AZ becomes faulty, other AZs in the same region will not be affected.
- With the Virtual Private Cloud (VPC) service, you can build your own dedicated network on the cloud. You can also set subnets and security groups within your VPC for further isolation. You can allow your VPC to communicate with the external network through an EIP (bandwidth support required).
- With the Image Management Service (IMS), you can use an image to create ECSs. Alternatively, you can use an existing ECS to create a private image and use the private image to create the same ECSs for rapid service deployment.
- Elastic Volume Service (EVS) provides storage space and Volume Backup Service (VBS) provides data backup and restoration functions.
- Cloud Eye lets you keep a close eye on the performance and resource utilization of ECSs, ensuring ECS reliability and availability.
- Volume Backup Service (VBS) allows you to create data backups for EVS disks and use the backups to restore the EVS disks. This maximizes user data correctness and security.
- Cloud Server Backup Service (CSBS) backs up all EVS disks of an ECS, including the system disk and data disks, and uses the backup to restore the ECS.
Figure 1 System architecturediff --git a/docs/ecs/umn/en-us_topic_0014250631.html b/docs/ecs/umn/en-us_topic_0014250631.html deleted file mode 100644 index 28eedf7a9..000000000 --- a/docs/ecs/umn/en-us_topic_0014250631.html +++ /dev/null @@ -1,67 +0,0 @@ - - -
Creating a Key Pair
---Overview
A key pair that consists of a public key and a private key is required for authentication when you log in to an ECS. Both the public and private keys are used for authentication. Therefore, you must use an existing key pair or create a new one for remote login authentication.
-- Creating a key pairIf no key pair is available, create one, in which the private key is used for login authentication. You can use either of the following methods to create a key pair:-
- (Recommended) Create a key pair on the management console. After the creation, the public key is automatically stored in the system, and the private key is manually stored in a local directory. For details, see Creating a Key Pair on the Management Console.
- Create a key pair using puttygen.exe. After the creation, both the public key and private key are stored locally. For details, see Creating a Key Pair Using puttygen.exe. After the creation, import the key pair by following the instructions provided in Importing a Key Pair. Then, the key pair can be used.
- Using an existing key pair
If a key pair is available locally, for example, generated using PuTTYgen, you can import the public key on the management console so that the system maintains the public key file. For details, see Importing a Key Pair.
-- If the public key of the existing key pair is stored by clicking Save public key of puttygen.exe, the public key cannot be imported to the management console.
-If this key pair must be used for remote authentication, see Why Does a Key Pair Created Using puttygen.exe Fail to Be Imported on the Management Console?
-
-Constraints
- ECSs support the following encryption algorithms:
- SSH-2 (RSA, 1024)
- SSH-2 (RSA, 2048)
- SSH-2 (RSA, 4096)
- The private key is one of the most important functions for protecting your ECS during remote login. Save the private key to your local directory and keep it secure. The private key can be downloaded only once.
-Creating a Key Pair on the Management Console
- 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 right side of the page, click Create Key Pair.
- Enter the key name and click OK.
An automatically allocated key name consists of KeyPair- and a 4-digit random number. Change it to an easy-to-remember one, for example, KeyPair-xxxx_ecs.
- - Manually or automatically download the private key file. The file name is the specified key pair name with a suffix of .pem. Securely store the private key file. In the displayed dialog box, click OK.-
This is the only opportunity for you to save the private key file. Keep it secure. When creating an ECS, provide the name of your desired key pair. Each time you log in to the ECS using SSH, provide the private key.
-
-Creating a Key Pair Using puttygen.exe
- Download and install PuTTY and PuTTYgen.
https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
-- PuTTYgen is a key generator, which is used to create a key pair that consists of a public key and a private key for PuTTY.
- - Obtain the public and private keys.
- Double-click puttygen.exe to switch to the PuTTY Key Generator page.Figure 1 PuTTY Key Generator-
- Click Generate.
The key generator automatically generates a key pair that consists of a public key and a private key. The public key is shown in the red box in Figure 2.
- -
- Double-click puttygen.exe to switch to the PuTTY Key Generator page.
- Copy the public key content to a .txt file and save the file in a local directory.-
Do not save the public key by clicking Save public key. Storing a public key by clicking Save public key of puttygen.exe will change the format of the public key content. Such a key cannot 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 varies depending on application scenarios:
-- Saving the private key in .ppk formatWhen you are required to log in to a Linux ECS using PuTTY, you must use the .ppk private key. To save the private key in .ppk format, perform the following operations:-
- On the PuTTY Key Generator page, choose File > Save private key.Figure 3 Save private key-
- Save the converted private key, for example, kp-123.ppk, in a local directory.
- On the PuTTY Key Generator page, choose File > Save private key.
- Saving the private key in .pem formatWhen you are required to log in to a Linux ECS using Xshell or attempt to obtain the password for logging in to a Windows ECS, you must use the .pem private key for authentication. To save the private key in .pem format, perform the following operations:-
- Choose Conversions > Export OpenSSH key.-
If you use this private file to obtain the password for logging in to a Windows ECS, when you choose Export OpenSSH key, do not configure Key passphrase. Otherwise, obtaining the password will fail.
-Figure 4 Export OpenSSH key-
- Save the private key, for example, kp-123.pem, in a local directory.
- Choose Conversions > Export OpenSSH key.
- Saving the private key in .ppk format
- Import the public key to the system. For details, see "Copying the public key content" in Importing a Key Pair.
- -Importing a Key Pair
If you store a public key by clicking Save public key of puttygen.exe, the format of the public key content will change. Such a key cannot be imported to the management console. To resolve this issue, obtain the public key content in correct format and import the content to the management console. For details, see Why Does a Key Pair Created Using puttygen.exe Fail to Be Imported on the Management Console?
-- 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 right side of the page, click Import Key Pair.Figure 5 Import Key Pair-
- Use either of the following methods to import the key pair:
- Selecting a file
- On the Import Key Pair page of the management console, click Select File and select the local public key file, for example, the .txt file saved in 3.-
When importing a key pair, ensure that the public key is imported. Otherwise, the importing will fail.
- - Click OK.
After the public key is imported, you can change its name.
-
- On the Import Key Pair page of the management console, click Select File and select the local public key file, for example, the .txt file saved in 3.
- Copying the public key content
- Copy the content of the public key in .txt file into the Public Key Content text box.
- Click OK.
- Selecting a file
-- - - \ No newline at end of file diff --git a/docs/ecs/umn/en-us_topic_0017130261.html b/docs/ecs/umn/en-us_topic_0017130261.html index 32731680c..37140b802 100644 --- a/docs/ecs/umn/en-us_topic_0017130261.html +++ b/docs/ecs/umn/en-us_topic_0017130261.html @@ -4,7 +4,7 @@--Parent topic: Passwords and Key Pairs--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.
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, click 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 private IP addresses.
+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.
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 private IP addresses.
- In the search box above the ECS list, enter the ECS name, IP address, or ID, and click
for search. Alternatively, click Search by Tag above the upper right corner of the ECS list and search for an ECS by tag key and value. - Click the name of the target ECS.
The page providing details about the ECS is displayed.
- View the ECS details.
You can modify ECS configurations, for example, change its security group, add a NIC or tag to it, or bind an EIP to it, by clicking corresponding links or buttons.
Login Using an SSH Key
-Scenarios
This section describes how to remotely log in to a Linux ECS using an SSH key pair from Windows and Linux, respectively.
Prerequisites
- You have obtained the private key file used during ECS creation.
- You have bound an EIP to the ECS. For details, see Viewing Details About an ECS.
Prerequisites
- You have obtained the private key file used for creating the ECS. For details about how to create a key pair, see (Recommended) Creating a Key Pair on the Management Console.
- You have bound an EIP to the ECS. For details, see Viewing Details About an ECS.
- You have configured the inbound rules of the security group. For details, see Configuring Security Group Rules.
- The network connection between the login tool (PuTTY) and the target ECS is normal. For example, the default port 22 is not blocked by the firewall.
-Logging In to the Linux ECS from Local Windows
To log in to the Linux ECS from local Windows, perform the operations described in this section.
diff --git a/docs/ecs/umn/en-us_topic_0017955633.html b/docs/ecs/umn/en-us_topic_0017955633.html index 1c31fcc4e..ba6d8afb3 100644 --- a/docs/ecs/umn/en-us_topic_0017955633.html +++ b/docs/ecs/umn/en-us_topic_0017955633.html @@ -5,7 +5,7 @@
Logging in to a Linux ECS using SSH password authentication is disabled by default. If you require password authentication, configure it after logging in to the ECS. To ensure system security, reset the common user password for logging in to the Linux ECS after configuring SSH password authentication.
diff --git a/docs/ecs/umn/en-us_topic_0018073218.html b/docs/ecs/umn/en-us_topic_0018073218.html index 5c0d463d4..29c592054 100644 --- a/docs/ecs/umn/en-us_topic_0018073218.html +++ b/docs/ecs/umn/en-us_topic_0018073218.html @@ -3,7 +3,7 @@Prerequisites
- The target ECS is running.
- You have bound an EIP to the ECS. For details, see Binding an EIP.
Prerequisites
- The target ECS is running.
- You have bound an EIP to the ECS. For details, see Binding an EIP.
- Access to port 22 is allowed in the inbound direction of the security group to which the ECS belongs. For details, see Configuring Security Group Rules.
- The network connection between the login tool (PuTTY) and the target ECS is normal. For example, the default port 22 is not blocked by the firewall.
- You have obtained the SSH login permission and reset the common user password for logging in to the Linux ECS. For details, see Configuring the Login Permission Using SSH Password Authentication.
Configuring the Login Permission Using SSH Password Authentication
Assigning the remote login permission using SSH key authentication
diff --git a/docs/ecs/umn/en-us_topic_0018073208.html b/docs/ecs/umn/en-us_topic_0018073208.html index 8f66377b0..c7cc0bab5 100644 --- a/docs/ecs/umn/en-us_topic_0018073208.html +++ b/docs/ecs/umn/en-us_topic_0018073208.html @@ -13,7 +13,7 @@- What Happens After I Click the Delete Button?
-
- Can I Provision an ECS I Deleted?
+- Can a Deleted ECS Be Provisioned Again?
- Can I Forcibly Restart or Stop an ECS?
diff --git a/docs/ecs/umn/en-us_topic_0018073215.html b/docs/ecs/umn/en-us_topic_0018073215.html index 4ebdc96ce..27c709af9 100644 --- a/docs/ecs/umn/en-us_topic_0018073215.html +++ b/docs/ecs/umn/en-us_topic_0018073215.html @@ -21,7 +21,7 @@
59
VBD disks + SCSI disks ≤ 60 (This constraint does not apply to local disks.)
-The number of local disks is determined based on the ECS flavor.
+The number of local disks is determined based on the ECS flavor.
D2
@@ -31,7 +31,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.
Example 2:
Based on example 1, if you are required to enable routing for default public network traffic through standby NIC eth1, perform the following operations to configure a route:
- Log in to the ECS.
- Run the following command to delete the default route:
+
Exercise caution when deleting the default route because this operation will interrupt the network and result in SSH login failures.
+ - Run the following command to configure a new default route:
ip route add 0.0.0.0/0 dev eth1 via 192.168.2.1
-In the preceding command, 192.168.2.1 is the gateway IP address of standby NIC eth1.
+In the preceding command, 192.168.2.1 is the gateway IP address of standby NIC eth1.
What Happens After I Click the Delete Button?
After you click Delete, the selected ECS is deleted. You can also choose to delete the EVS disk and EIP of the ECS. If you do not delete them, they will be retained. If necessary, you can manually delete them later.
To delete an ECS, perform the following operations:
-- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
- Select the ECS to be deleted.
- In the upper part of the ECS list, click Delete.
- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
- Select the ECS to be deleted.
- In the upper part of the ECS list, click Delete.
diff --git a/docs/ecs/umn/en-us_topic_0018073221.html b/docs/ecs/umn/en-us_topic_0018073221.html index 687b2af98..7119a5737 100644 --- a/docs/ecs/umn/en-us_topic_0018073221.html +++ b/docs/ecs/umn/en-us_topic_0018073221.html @@ -1,6 +1,6 @@ -Can I Provision an ECS I Deleted?
+Can a Deleted ECS Be Provisioned Again?
diff --git a/docs/ecs/umn/en-us_topic_0018078522.html b/docs/ecs/umn/en-us_topic_0018078522.html index 104756e2e..d5b4f80e1 100644 --- a/docs/ecs/umn/en-us_topic_0018078522.html +++ b/docs/ecs/umn/en-us_topic_0018078522.html @@ -1,7 +1,8 @@No. ECSs in the Deleted state cannot provide services and are soon removed from the system.
A deleted ECS is retained in the ECS list on the management console only for a short period of time before it is permanently removed from the system. You can create a new ECS with the same specifications again.
Can I Change the OS of an ECS?
-Yes. You can change the OS of an ECS.
+Yes, you can change the OS of an ECS.
+If the OS running on an ECS cannot meet service requirements, for example, a higher OS version is required, you can change the ECS OS.
For instructions about how to change an ECS OS, see Changing the OS.
diff --git a/docs/ecs/umn/en-us_topic_0018339851.html b/docs/ecs/umn/en-us_topic_0018339851.html index cea46337e..25cd03b66 100644 --- a/docs/ecs/umn/en-us_topic_0018339851.html +++ b/docs/ecs/umn/en-us_topic_0018339851.html @@ -2,7 +2,7 @@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.
-- 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. For details, see Unable to RDP to Virtual Machine: CredSSP Encryption Oracle Remediation. 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 Microsoft documents.
-Solution
Modify the remote desktop connection settings on the Windows ECS:
diff --git a/docs/ecs/umn/en-us_topic_0021426802.html b/docs/ecs/umn/en-us_topic_0021426802.html index 5ab57a5d4..4c1113454 100644 --- a/docs/ecs/umn/en-us_topic_0021426802.html +++ b/docs/ecs/umn/en-us_topic_0021426802.html @@ -10,11 +10,9 @@sudo apt-get install ntfs-3g chntpw
Method 2:
Download the ntfs-3g and chntpw software packages of the version required by the temporary ECS OS.
-To obtain the ntfs-3g software package, log in at www.tuxera.com/community/open-source-ntfs-3g/.
-To obtain the chntpw software package, log in at https://www.chntpw.com/download/.
Procedure
- Stop the original 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 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.
+Procedure
- Stop the original 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 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.
- 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.
- Log in to the temporary ECS remotely and attach the system disk.
- 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
@@ -30,7 +28,7 @@ Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.Back up the disk data, run the following command to rectify the NTFS file system inconsistency, and attach the system disk:
ntfsfix /dev/Result obtained in step 2.a
-For example, if the result obtained in step 2.a is xvde2, run the following command:
+For example, if the result obtained in step 2.a is xvde2, run the following command:
ntfsfix /dev/xvde2
- Run the following command to view the directory of the system disk detached from the original Windows ECS now attached to the temporary ECS:
- Change the password and clear the original password.
diff --git a/docs/ecs/umn/en-us_topic_0021427650.html b/docs/ecs/umn/en-us_topic_0021427650.html index e3319233e..452739ba7 100644 --- a/docs/ecs/umn/en-us_topic_0021427650.html +++ b/docs/ecs/umn/en-us_topic_0021427650.html @@ -33,7 +33,7 @@-Parent topic: Resetting a Login Password+Parent topic: Passwordsdiff --git a/docs/ecs/umn/en-us_topic_0024911405.html b/docs/ecs/umn/en-us_topic_0024911405.html index 2cb8b0363..b27089edf 100644 --- a/docs/ecs/umn/en-us_topic_0024911405.html +++ b/docs/ecs/umn/en-us_topic_0024911405.html @@ -6,12 +6,12 @@-Parent topic: Resetting a Login Password+Parent topic: Passwords-Notes
- After the OS is reinstalled, the IP and MAC addresses of the ECS remain unchanged.
- Reinstalling the OS clears the data in all partitions of the EVS system disk, including the system partition. Therefore, back up data before reinstalling the OS.
- Reinstalling the OS does not affect data disks.
- Do not perform any operations on the ECS immediately after its OS is reinstalled. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- After the OS is reinstalled, the password for logging in to the ECS will be reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Login Using an SSH Key.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
- You can choose to encrypt the system disk of an ECS during OS reinstallation.
Constraints
- The EVS disk quota must be greater than 0.
- If the target ECS is created using a private image, ensure that the private image is available.
- H2 ECSs do not support OS reinstallation.
- If an ECS OS is to be reinstalled using a full-ECS image, the ECS system disk can be encrypted.
Constraints
- The EVS disk quota must be greater than 0.
- If the target ECS is created using a private image, ensure that the private image is available.
- If an ECS OS is to be reinstalled using a full-ECS image, the ECS system disk can be encrypted.
-Prerequisites
- The target ECS is stopped.
- The target ECS has a system disk attached.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Locate the row containing the target ECS. Click More in the Operation column and select Manage Image/Disk > Reinstall OS.
Only stopped ECSs support OS reinstallation. If the ECS is not stopped, stop it before proceeding with reinstallation.
- - (Optional) Select the Encryption option to encrypt the system disk during OS reinstallation.
To enable encryption, click Create Xrole to assign KMS access permissions to EVS. If you have rights granting permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights to assign the KMS access permissions. For more details, see Can All Users Use the Encryption Feature?
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Locate the row containing the target ECS. Click More in the Operation column and select Manage Image/Disk > Reinstall OS.
Only stopped ECSs support OS reinstallation. If the ECS is not stopped, stop it before proceeding with reinstallation.
+ - (Optional) Select the Encryption option to encrypt the system disk during OS reinstallation.
To enable encryption, click Create Xrole to assign KMS access permissions to EVS. If you have rights granting permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights to assign the KMS access permissions. For more 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.
- 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.
- Xrole Name: EVSAccessKMS: specifies that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- 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 Type.
The following OSs are billed:
diff --git a/docs/ecs/umn/en-us_topic_0027157850.html b/docs/ecs/umn/en-us_topic_0027157850.html index 189759546..8c7bd9265 100644 --- a/docs/ecs/umn/en-us_topic_0027157850.html +++ b/docs/ecs/umn/en-us_topic_0027157850.html @@ -1,14 +1,14 @@Enabling Internet Connectivity for an ECS Without an EIP
-Scenarios
To ensure platform security and conserve EIPs, EIPs are assigned only to specified ECSs. ECSs without EIPs cannot access the Internet directly. If these ECSs need to access the Internet (for example, to perform a software upgrade or install a patch), you can select an ECS with an EIP bound to function as a proxy ECS, providing an access channel for these ECS.
+Scenarios
To ensure platform security and conserve EIPs, EIPs are assigned only to specified ECSs. ECSs without EIPs cannot access the Internet directly. If these ECSs need to access the Internet (for example, to perform a software upgrade or install a patch), you can select an ECS with an EIP bound to function as a proxy ECS, providing an access channel for these ECSs.
NAT Gateway is recommended, which provides both the SNAT and DNAT functions for your ECSs in a VPC and allows the ECSs to access or provide services accessible from the Internet.
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.
-- 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.
- Click the Network Interfaces tab and then
. Then, disable 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 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.
- Click the Network Interfaces tab and then . Then, disable 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.
- Run the following command to 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:
@@ -18,11 +18,11 @@ - 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: -
- Press i to enter editing mode.
- Set the net.ipv4.ip_forward value to 1.
Set the net.ipv4.ip_forward value to 1.
+ - 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.
+ - 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
iptables -P OUTPUT ACCEPT
@@ -32,14 +32,14 @@ - 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
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
- 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 the editing mode, and enter :wq to save and exit the file.
+ 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.
- Run the following commands to save the iptables configuration and make it start up automatically upon ECS startup:
chkconfig iptables on
- Run the following command to check whether SNAT has been configured:
SNAT has been configured if information similar to Figure 1 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.
- Select a VPC to which a route is to be added and click Route Tables. On the Route Tables 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 SNAT 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. On the displayed page, click a VPC which a route is to be added to. 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 SNAT ECS.
You can obtain the private IP address of the ECS on the Elastic Cloud Server page.
- To delete the added iptables rules, run the following command:
iptables -t nat -D POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
diff --git a/docs/ecs/umn/en-us_topic_0027268511.html b/docs/ecs/umn/en-us_topic_0027268511.html index 4956fd7e4..75e858e0d 100644 --- a/docs/ecs/umn/en-us_topic_0027268511.html +++ b/docs/ecs/umn/en-us_topic_0027268511.html @@ -188,9 +188,9 @@
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.
Monitoring ECSs
--Monitoring is key for ensuring ECS performance, reliability, and availability. Using monitored data, you can determine ECS resource utilization. The public cloud provides Cloud Eye to help you obtain the running statuses of your ECSs. You can use Cloud Eye to automatically monitor ECSs in real time and manage alarms and notifications to keep track of ECS performance metrics.
+diff --git a/docs/ecs/umn/en-us_topic_0027371530.html b/docs/ecs/umn/en-us_topic_0027371530.html index c53749f9c..9c3e77219 100644 --- a/docs/ecs/umn/en-us_topic_0027371530.html +++ b/docs/ecs/umn/en-us_topic_0027371530.html @@ -10,7 +10,7 @@Monitoring is key for ensuring ECS performance, reliability, and availability. Using monitored data, you can determine ECS resource utilization. The cloud service platform provides Cloud Eye to help you obtain the running statuses of your ECSs. You can use Cloud Eye to automatically monitor ECSs in real time and manage alarms and notifications to keep track of ECS performance metrics.
This section covers the following content:
- Viewing basic ECS metrics
- Customizing ECS alarm rules
- Viewing ECS running statuses for routine monitoring
- The target ECS has been properly running for at least 10 minutes.
The monitoring data and graphics are available for a new ECS after the ECS runs for at least 10 minutes.
diff --git a/docs/ecs/umn/en-us_topic_0027371531.html b/docs/ecs/umn/en-us_topic_0027371531.html index 28e73b4c0..b55c51fba 100644 --- a/docs/ecs/umn/en-us_topic_0027371531.html +++ b/docs/ecs/umn/en-us_topic_0027371531.html @@ -4,9 +4,9 @@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 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 Monitoring tab to view the monitoring data.
- In the ECS monitoring area, select a duration to view the monitoring data.
You can view the monitoring data of the ECS in the last 1, 3, or 12 hours.
+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 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 Monitoring tab to view the monitoring data.
- In the ECS monitoring area, select a duration to view the monitoring data.
You can view the monitoring data of the ECS in the last 1, 3, or 12 hours.
-Scenarios
Setting ECS alarm rules allows you to customize the monitored objects and notification policies so that you can closely monitor your ECSs.
This section describes how to set ECS alarm rules, including alarm rule names, monitoring objects, monitoring metrics, alarm thresholds, monitoring intervals, and notifications.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Management & Deployment, click Cloud Eye.
- In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the Alarm Rules page, click Create Alarm Rule to create an alarm rule, or modify an existing alarm rule.
The following operations use modifying an existing alarm rule as an example.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Click Service List. Under Management & Deployment, select Cloud Eye.
- In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the Alarm Rules page, click Create Alarm Rule to create an alarm rule, or modify an existing alarm rule.
The following uses modifying an existing alarm rule as an example.
- Click the target alarm rule.
- Click Modify in the upper right corner of the page.
- In the Modify Alarm Rule dialog box shown in Figure 1, set the parameters as prompted. -
- Click OK.
After an alarm rule is modified, the system automatically notifies you of an alarm when the alarm complying with the alarm rule is generated.
+ - Click Modify.
After an alarm rule is modified, the system automatically notifies you of an alarm when the alarm complying with the alarm rule is generated.
diff --git a/docs/ecs/umn/en-us_topic_0030013188.html b/docs/ecs/umn/en-us_topic_0030013188.html index bf825d36b..8da2287d3 100644 --- a/docs/ecs/umn/en-us_topic_0030013188.html +++ b/docs/ecs/umn/en-us_topic_0030013188.html @@ -3,7 +3,7 @@ For more information about ECS alarm rules, see Cloud Eye User Guide.
Can an ECS Without an EIP Access the Internet?
Yes.
- Method 1: Configure a SNAT server.
You can configure the SNAT server so that the ECS without an EIP bound can access the Internet.
-For details, see "Configuring an SNAT Server" in Virtual Private Cloud User Guide.
+For details, see "Configuring an SNAT Server" in Virtual Private Cloud User Guide.
- Method 2: Create a NAT gateway.
If a large number of concurrent connections are required, it is a good practice to use the NAT Gateway service provided by the cloud platform.
The NAT Gateway service offers the NAT function for ECSs in a VPC, allowing these ECSs to access the Internet using an EIP. For more information about NAT Gateway, see NAT Gateway User Guide.
Images
+Image Types
What Is Image?
An image is an ECS template that contains an OS and may also contain proprietary software and application software, such as database software. You can use images to create ECSs.
-Images can be public or private. Public images are provided by the system by default, and private images are manually created. You can use any type of image to create an ECS. You can also create a private image using an existing ECS or external image. This provides you with a simple and fast way to create ECSs tailored to your needs. For example, if you use web services, your image can contain web server configurations, static configurations, and dynamic page code. After you use this image to create an ECS, the web server will run on the newly created ECS.
+Images can be public or private. Public images are provided by the system by default, and private images are manually created. You can use any type of image to create an ECS. You can also create a private image using an existing ECS or external image. This provides you with a simple and fast way to create ECSs tailored to your needs. For example, if you use web services, your image can contain web server configurations, static configurations, and dynamic page code. After you use this image to create an ECS, the web server will run on the newly created ECS.
Image Types
Image Type
@@ -20,7 +20,7 @@A private image contains an OS or service data, preinstalled public applications, and a user's personal applications. Private images are only available to the users who created them.
A private image can be a system disk image, data disk image, or full-ECS image.
-- A system disk image contains an OS and pre-installed software for various services. You can use a system disk image to create ECSs and migrate your services to the cloud.
- A data disk image contains only service data. You can use a data disk image to create EVS disks and use them to migrate your service data to the cloud.
- A full-ECS image contains an OS, pre-installed software, and service data. A full-ECS image is created using differential backups and the creation takes less time than creating a system or data disk image of the same size.
- A system disk image contains an OS and preinstalled software for various services. You can use a system disk image to create ECSs and migrate your services to the cloud.
- A data disk image contains only service data. You can use a data disk image to create EVS disks and use them to migrate your service data to the cloud.
- A full-ECS image contains an OS, preinstalled software, and service data. A full-ECS image is created using differential backups and the creation takes less time than creating a system or data disk image of the same size.
Shared image
@@ -35,7 +35,7 @@diff --git a/docs/ecs/umn/en-us_topic_0030831989.html b/docs/ecs/umn/en-us_topic_0030831989.html index 6b024dd09..62ba5315f 100644 --- a/docs/ecs/umn/en-us_topic_0030831989.html +++ b/docs/ecs/umn/en-us_topic_0030831989.html @@ -8,7 +8,7 @@-Parent topic: Service Overview+Parent topic: Images- Initializing a Windows Data Disk (Windows Server 2008)
-
- Initializing a Windows Data Disk (Windows Server 2016)
+- Initializing a Windows Data Disk (Windows Server 2019)
- Initializing a Linux Data Disk (fdisk)
diff --git a/docs/ecs/umn/en-us_topic_0030878383.html b/docs/ecs/umn/en-us_topic_0030878383.html index b451da0af..86dda8577 100644 --- a/docs/ecs/umn/en-us_topic_0030878383.html +++ b/docs/ecs/umn/en-us_topic_0030878383.html @@ -5,14 +5,14 @@
- Inbound: Inbound rules allow external network traffic to be sent to the ECSs in the security group.
- Outbound: Outbound rules allow network traffic from the ECSs in the security group to be sent out of the security group.
For details about the default security group rules, see Virtual Private Cloud User Guide. For details about configuration examples for security group rules, see Security Group Configuration Examples.
-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.
+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 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.
- On the Inbound Rules tab, click Add Rule. In the displayed dialog box, set required parameters to add an inbound rule.
You can click + to add more inbound rules.
Figure 1 Add Inbound Rule-
Table 1 Inbound rule parameter description Parameter
+-Table 1 Inbound rule parameter description Parameter
Description
+Description
Example Value
Protocol & Port
Protocol: The network protocol. Currently, the value can be All, TCP, UDP, ICMP, GRE, or others.
+Protocol: The network protocol. Currently, the value can be All, TCP, UDP, ICMP, GRE, or others.
TCP
Port: The port or port range over which the traffic can reach your ECS. The value ranges from 1 to 65535.
+Port: The port or port range over which the traffic can reach your ECS. The value ranges from 1 to 65535.
22, or 22-30
Source
The source of the security group rule. The value can be a single IP address or a security group to allow access from the IP address or instances in the security group. For example:- xxx.xxx.xxx.xxx/32 (IPv4 address)
- xxx.xxx.xxx.0/24 (IP address range)
- 0.0.0.0/0 (all IP addresses)
- sg-abc (security group)
- xxx.xxx.xxx.xxx/32 (IPv4 address)
- xxx.xxx.xxx.0/24 (IPv4 address range)
- 0.0.0.0/0 (all IPv4 addresses)
- sg-abc (security group)
If the source is a security group, this rule will apply to all instances associated with the selected security group.
- On the Outbound Rules tab, click Add Rule. In the displayed dialog box, set required parameters to add an outbound rule.
You can click + to add more outbound rules.
+- On the Outbound Rules tab, click Add Rule. In the displayed dialog box, set required parameters to add an outbound rule.
You can click + to add more outbound rules.
Figure 2 Add Outbound Rule-
Table 2 Outbound rule parameter description Parameter
+Table 2 Outbound rule parameter description Parameter
Description
+Description
Example Value
Protocol & Port
Protocol: The network protocol. Currently, the value can be All, TCP, UDP, ICMP, GRE, or others.
+Protocol: The network protocol. Currently, the value can be All, TCP, UDP, ICMP, GRE, or others.
TCP
Port: The port or port range over which the traffic can leave your ECS. The value ranges from 1 to 65535.
+Port: The port or port range over which the traffic can leave your ECS. The value ranges from 1 to 65535.
22, or 22-30
Destination
The destination of the security group rule. The value can be a single IP address or a security group to allow access to the IP address or instances in the security group. For example:- xxx.xxx.xxx.xxx/32 (IPv4 address)
- xxx.xxx.xxx.0/24 (IP address range)
- 0.0.0.0/0 (all IP addresses)
- sg-abc (security group)
The destination of the security group rule. The value can be a single IP address or a security group to allow access to IP addresses or instances in the security group. For example:- xxx.xxx.xxx.xxx/32 (IPv4 address)
- xxx.xxx.xxx.0/24 (IPv4 address range)
- 0.0.0.0/0 (all IPv4 addresses)
- sg-abc (security group)
0.0.0.0/0
diff --git a/docs/ecs/umn/en-us_topic_0030911465.html b/docs/ecs/umn/en-us_topic_0030911465.html index f69535366..ca446234c 100644 --- a/docs/ecs/umn/en-us_topic_0030911465.html +++ b/docs/ecs/umn/en-us_topic_0030911465.html @@ -5,7 +5,7 @@-Namespace
SYS.ECS
ECS Metrics
ECS metrics vary depending on ECS OSs and types. For details, see Table 1. √ indicates that the metric is supported, and x indicates that the metric is not supported.
+ECS Metrics
ECS metrics vary depending on ECS OSs and types. For details, see Table 1. √ indicates that the metric is supported, and x indicates that the metric is not supported.
Table 1 ECS metrics Metric
@@ -109,7 +109,7 @@The monitoring intervals for the following ECSs with raw monitoring metrics are as follows:
- KVM ECS: 5 minutes
Table 2 Metric description Metric
+Table 2 Metric description Metric ID
Parameter
InfiniBand NIC status
Status of an InfiniBand NIC on an H2 ECS
-The system periodically checks the status and returns check results using value 0 or 1.
-- 0: The system is running properly. That is, the InfiniBand NIC is functional.
- 1: The system is not running properly. That is, the InfiniBand NIC malfunctions. When the physical NIC corresponding to a virtual NIC becomes faulty, for example, the network cable is not securely connected to the NIC, the switch or adapter is incompatible with the InfiniBand NIC, or the NIC is disabled, the returned value is 1.
The system periodically checks the status and returns check results using value 0 or 1.
+- 0: The system is running properly. That is, the InfiniBand NIC is functional.
- 1: The system is not running properly. That is, the InfiniBand NIC malfunctions. When the physical NIC corresponding to a virtual NIC becomes faulty, for example, the network cable is not securely connected to the NIC, the switch or adapter is incompatible with the InfiniBand NIC, or the NIC is disabled, the returned value is 1.
NOTE:Only Mellanox EDR 100 GB single-port InfiniBand NICs are supported.
Resetting a Login Password
+Passwords
-
+
- Application Scenarios for Using Passwords
+
+ - Changing the Login Password on an ECS
+ - Resetting the Password for Logging In to a Windows ECS
- Resetting the Password for Logging In to a Linux ECS
diff --git a/docs/ecs/umn/en-us_topic_0031107266.html b/docs/ecs/umn/en-us_topic_0031107266.html index 9ae0f8877..7606df1e4 100644 --- a/docs/ecs/umn/en-us_topic_0031107266.html +++ b/docs/ecs/umn/en-us_topic_0031107266.html @@ -4,11 +4,11 @@-Scenarios
Password authentication is required to log in to a Windows ECS. Therefore, 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
- 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.
- 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.
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.
- Use either of the following methods to obtain the password through the key file:
- Click Select File and upload the key file from a local directory.
- Copy the key file content to the text field.
- Click Get Password to obtain a random password.
Obtaining the Password Through APIs
- Obtain the private key file (.pem file) used when you created the ECS.
- Set up the API calling environment.
- Call APIs. For details, see API Usage Guidelines in Elastic Cloud Server API Reference.
- Obtain the ciphertext password.
Call the password obtaining APIs to obtain the ciphertext password of the public key encrypted using RSA. The API URI is in the format "GET /v2/{tenant_id}/servers/{server_id}/os-server-password".
-- For instructions about how to call the APIs, see Retrieving the Password for Logging In to a Windows ECS (Native OpenStack API) in Elastic Cloud Server API Reference.
+- Decrypt the ciphertext password.
Use the private key file used when you created the ECS to decrypt the ciphertext password obtained in step 4.
diff --git a/docs/ecs/umn/en-us_topic_0031107267.html b/docs/ecs/umn/en-us_topic_0031107267.html index 245fc5cdc..3384047ab 100644 --- a/docs/ecs/umn/en-us_topic_0031107267.html +++ b/docs/ecs/umn/en-us_topic_0031107267.html @@ -4,13 +4,13 @@-Parent topic: Passwords and Key Pairs+Parent topic: Obtaining and Deleting the Password of an Windows ECS--Scenarios
After you obtain the initial password, it is a good practice to delete it to ensure system security.
Deleting the initial password does not affect ECS operation or login. Once deleted, the password cannot be retrieved. Before you delete a password, it is a good practice to record it.
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, select the target ECS.
- In the Operation column, click More and select Delete Password.
The system displays a message, asking you whether you want to delete the password.
+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, select the target ECS.
- In the Operation column, click More and select Delete Password.
The system displays a message, asking you whether you want to delete the password.
- Click OK to delete the password.
diff --git a/docs/ecs/umn/en-us_topic_0031523135.html b/docs/ecs/umn/en-us_topic_0031523135.html index da637fa14..549a58d73 100644 --- a/docs/ecs/umn/en-us_topic_0031523135.html +++ b/docs/ecs/umn/en-us_topic_0031523135.html @@ -5,9 +5,9 @@-Parent topic: Passwords and Key Pairs+Parent topic: Obtaining and Deleting the Password of an Windows ECSIf the OS running on an ECS cannot meet service requirements, change the ECS OS.
The public cloud supports changing between image types (public images, private images, and shared images) and between OSs. You can change your OS by changing your ECS image.
Constraints
- The EVS disk quota must be greater than 0.
- H2 ECSs do not support OS change.
- If an ECS OS is to be changed using a full-ECS image, the ECS system disk can be encrypted.
-Constraints
- The EVS disk quota must be greater than 0.
- If an ECS OS is to be changed using a full-ECS image, the ECS system disk can be encrypted.
Notes
- After the OS is changed, the original OS is not retained, and the original system disk is deleted, including the data in all partitions of the system disk.
- Back up data before changing the OS. For details, see .
- Changing the OS does not affect data in data disks.
- After the OS is changed, your service running environment must be deployed in the new OS again.
- After the OS is changed, the ECS will be automatically started.
- After the OS is changed, the system disk type of the ECS cannot be changed.
- After the OS is changed, the IP and MAC addresses of the ECS remain unchanged.
- After the OS is changed, customized configurations, such as DNS and hostname of the original OS will be reset and require reconfiguration.
- It takes about 10 to 20 minutes to change the OS. During this process, the ECS is in Changing OS state.
- Do not perform any operations on the ECS immediately after its OS is changed. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- After the OS is changed, the password for logging in to the ECS is reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Login Using an SSH Key.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
@@ -16,12 +16,12 @@Notes
- After the OS is changed, the original OS is not retained, and the original system disk is deleted, including the data in all partitions of the system disk.
- Back up data before changing the OS.
- Changing the OS does not affect data in data disks.
- After the OS is changed, your service running environment must be deployed in the new OS again.
- After the OS is changed, the ECS will be automatically started.
- After the OS is changed, the system disk type of the ECS cannot be changed.
- After the OS is changed, the IP and MAC addresses of the ECS remain unchanged.
- After the OS is changed, customized configurations, such as DNS and hostname of the original OS will be reset and require reconfiguration.
- It takes about 10 to 20 minutes to change the OS. During this process, the ECS is in Changing OS state.
- Do not perform any operations on the ECS immediately after its OS is changed. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- After the OS is changed, the password for logging in to the ECS is reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Login Using an SSH Key.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
- The system disk capacity of an ECS with OS changed may change because the system disk capacity specified by the image of the changed OS may be changed.
- You can choose to encrypt the system disk of an ECS during OS change.
Prerequisites
- The target ECS is stopped.
- The target ECS has a system disk attached.
- Necessary data has been backed up. (Changing the OS clears the data in all partitions of the system disk, including the system partition.)
- If the original ECS uses password authentication while the new ECS uses key pair authentication, ensure that a key pair is available.
- If a private image is required for changing the ECS OS, create the desired private image by following the instructions provided in Image Management Service User Guide.
- If an ECS image is required, make sure that a private image has been created using the 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.
-Prerequisites
- The target ECS is stopped.
- The target ECS has a system disk attached.
- Necessary data has been backed up. (Changing the OS clears the data in all partitions of the system disk, including the system partition.)
- If the original ECS uses password authentication while the new ECS uses key pair authentication, ensure that a key pair is available.
- If a private image is required for changing the ECS OS, create the desired private image by following the instructions provided in Image Management Service User Guide.
- If the image of an ECS is required, make sure that a private image has been created using the ECS.
- If a local image file is required, make sure that the image file has been imported to the cloud platform and registered as a private image.
- If a private image from another region is required, make sure that the image has been copied.
- If a private image from another user account is required, make sure that the image has been shared with you.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Locate the row containing the target ECS. Click More in the Operation column and select Manage Image/Disk > Change OS.
Only stopped ECSs support OS changing. 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, click Elastic Cloud Server.
- Locate the row containing the target ECS. Click More in the Operation column and select Manage Image/Disk > Change OS.
Only stopped ECSs support OS changing. If the ECS is not stopped, stop it before proceeding with changing.
- Modify related ECS parameters, such as Image Type and Image, based on service requirements.
For more details, see Creating an ECS.
- - (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 more details, see Can All Users Use the Encryption Feature?
+ - (Optional) Select the Encryption option to encrypt the system disk during OS change.
To enable encryption, click Create Xrole to 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 more 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.
- 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.
- Xrole Name: EVSAccessKMS: specifies that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- (Optional) Select a License Type (Use license from the system or Bring your own license (BYOL)) if the changed OS running on your ECS is billed. For more details, see License Type.The following OSs are billed:
- SUSE Linux Enterprise Server
- Oracle Enterprise Linux
- Red Hat Enterprise Linux
Scripts, such as Shell and Python scripts, are used for custom configurations.
Methods pre-defined in Cloud-Init, such as the Yum source and SSH key, are used for configuring certain ECS applications.
+Methods pre-defined in Cloud-Init, such as the yum repository and SSH key, are used for configuring certain ECS applications.
- Decrypt the ciphertext password.
Format
@@ -71,7 +71,7 @@ echo "Hello, the time is now $(date -R)" | tee /root/output.txtAfter the ECS is created, start it and run the cat [file] command to check the script execution result.
[root@XXXXXXXX ~]# cat /root/output.txt Hello, the time is now Mon, 16 Jul 2016 16:03:18+0800
-Example 2: Inject a Cloud-Config data script.
+Example 2: Inject a Cloud-Config data script.
When creating an ECS, set User Data to As text and enter the customized user data script.
#cloud-config bootcmd: @@ -167,7 +167,7 @@ write_files:
User data example:
- Using a ciphertext password (recommended)
#!/bin/bash echo 'root:$6$V6azyeLwcD3CHlpY$BN3VVq18fmCkj66B4zdHLWevqcxlig' | chpasswd -e;
-In the preceding command output, $6$V6azyeLwcD3CHlpY$BN3VVq18fmCkj66B4zdHLWevqcxlig is the ciphertext password, which can be generated as follows:
+In the preceding command output, $6$V6azyeLwcD3CHlpY$BN3VVq18fmCkj66B4zdHLWevqcxlig is the ciphertext password, which can be generated as follows:
- Run the following command to generate an encrypted ciphertext value:
python -c "import crypt, getpass, pwd;print crypt.mksalt()"
The following information is displayed:
$6$V6azyeLwcD3CHlpY
diff --git a/docs/ecs/umn/en-us_topic_0032398121.html b/docs/ecs/umn/en-us_topic_0032398121.html index 0e5611fae..2f602bacc 100644 --- a/docs/ecs/umn/en-us_topic_0032398121.html +++ b/docs/ecs/umn/en-us_topic_0032398121.html @@ -44,7 +44,7 @@
- Run the following command to generate an encrypted ciphertext value:
System error. Try again later or contact customer service.
Adjust the request structure as directed in Elastic Cloud Server API Reference.
+Adjust the request structure as directed in Elastic Cloud Server API Reference.
Ecs.0010
diff --git a/docs/ecs/umn/en-us_topic_0032980085.html b/docs/ecs/umn/en-us_topic_0032980085.html index d9d9d716d..0217df1a3 100644 --- a/docs/ecs/umn/en-us_topic_0032980085.html +++ b/docs/ecs/umn/en-us_topic_0032980085.html @@ -1,14 +1,14 @@Managing ECS Groups
-Scenarios
An ECS group allows you to create ECSs on different physical servers, thereby improving service reliability. This function does not apply to existing ECSs. You cannot add existing ECSs to an ECS group.
+Scenarios
An ECS group allows you to create ECSs on different hosts, thereby improving service reliability. This function does not apply to existing ECSs. You cannot add existing ECSs to an ECS group.
-Notes
An existing ECS cannot be added to an ECS group.
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 ECS Group.
- On the ECS Group page, click Create ECS Group.
- Enter the name of the target ECS group.
The Anti-affinity policy is used by default.
+-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 ECS Group.
- On the ECS Group page, click Create ECS Group.
- Enter the name of the target ECS group.
- Click OK.
diff --git a/docs/ecs/umn/en-us_topic_0035470096.html b/docs/ecs/umn/en-us_topic_0035470096.html index f7cf4d7cd..8397fd5a7 100644 --- a/docs/ecs/umn/en-us_topic_0035470096.html +++ b/docs/ecs/umn/en-us_topic_0035470096.html @@ -12,7 +12,7 @@Follow-up Procedure
Add an ECS to an ECS group only when creating the ECS.
+Follow-up Procedure
Add an ECS to an ECS group only when creating the ECS.
To do so, expand Advanced Options and select the target ECS group.
Network QoS
Network QoS uses basic technologies to improve the quality of network communication. A network with QoS enabled offers predictable network performance and effectively allocates network bandwidth to use network resources.
To obtain the QoS data of an ECS flavor, including the maximum bandwidth, assured bandwidth, maximum PPS, and NIC multi-queue, see ECS Specifications.
-The intranet bandwidth and PPS of an ECS are determined based on ECS flavors.- Assured intranet bandwidth: guaranteed bandwidth allocated to the ECS
- Maximum intranet bandwidth: maximum bandwidth that can be allocated to the ECS
- Maximum intranet PPS: maximum number of packets that the ECS can transmit and receive per second
- NIC multi-queue: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth.
- For instructions about how to test PPS, see How Can I Test Network Performance?
- For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
The intranet bandwidth and PPS of an ECS are determined based on ECS flavors.diff --git a/docs/ecs/umn/en-us_topic_0035470099.html b/docs/ecs/umn/en-us_topic_0035470099.html index c366058ab..3e99dff0f 100644 --- a/docs/ecs/umn/en-us_topic_0035470099.html +++ b/docs/ecs/umn/en-us_topic_0035470099.html @@ -4,43 +4,47 @@- Assured intranet bandwidth: guaranteed bandwidth allocated to the ECS
- Maximum intranet bandwidth: maximum bandwidth that can be allocated to the ECS
- Maximum intranet PPS: maximum number of packets that the ECS can transmit and receive per second
- NIC multi-queues: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth
- Maximum NICs: maximum number of NICs that can be attached to an ECS.
- For instructions about how to test PPS, see How Can I Test Network Performance?
- For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
Overview
D2 ECSs are developed based on KVM virtualization. They use local storage and provide high storage performance and intranet bandwidth for distributed Hadoop computing, large data warehouse, distributed file system, and log/data processing.
Specifications
-Table 1 D2 ECS specifications Flavor
+-Table 1 D2 ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory
+(GiB)
Maximum/Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth
+(Gbit/s)
Maximum PPS (10,000)
+Max. PPS
+(10,000)
NIC Multi-Queue
+Max. NIC Queues
Virtualization Type
+Virtualization
Local Disks (GiB)
+Local Disks
+(GiB)
Hardware
+Hardware
d2.xlarge.8
+d2.xlarge.8
4
+4
32
+32
4/1.4
+4/1.4
40
+40
2
+2
KVM
+KVM
2×1675
+2×1675
CPU: Intel® Xeon® Gold 6151
+CPU: Intel® Xeon® Gold 6151
d2.2xlarge.8
@@ -163,7 +167,86 @@Notes on Using D2 ECSs
- Currently, the following operating systems are supported (subject to the information displayed on the console):
- CentOS 6.7/6.8/7.2/7.3/7.4 64bit
- SUSE Enterprise Linux Server 11 SP3/SP4 64bit
- SUSE Enterprise Linux Server 12 SP1/SP2 64bit
- Red Hat Enterprise Linux 6.8/7.3 64bit
- Windows Server 2008 R2 Enterprise 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2016 Standard 64bit
- Debian 8.7/9/9.0.0 64bit
- EulerOS 2.2 64bit
- Fedora 25/26 64bit
- OpenSUSE 42.2/42.3 64bit
Notes
- Table 3 lists the OSs supported by disk-intensive ECSs.
+
+Table 3 Supported OS versions OS
+Version
+Alma
+Alma 8 64bit
+CentOS
+- CentOS Stream 8.6 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
Debian
+- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
EulerOS
+EulerOS 2.5 64bit
+Fedora
+- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
OpenSUSE
+OpenSUSE 15.3 64bit
+Oracle Linux
+- Oracle Linux Server release 8.4 64bit
- Oracle Linux Server release 7.6 64bit
RedHat
+- Redhat Linux Enterprise 7.9 64bit
- Redhat Linux Enterprise 6.10 64bit
Rocky
+Rocky 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
SUSE-SAP
+- 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
Windows
+- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
openEuler
+openEuler 20.03 64bit
+ - When the physical host where a D2 ECS is deployed becomes faulty, the ECS cannot be migrated.
- To improve network performance, you can set the NIC MTU of a D2 ECS to 8888.
- D2 ECSs do not support modifying specifications.
- D2 ECSs do not support local disk snapshots or backups.
- D2 ECSs do not support OS reinstallation or change.
- D2 ECSs can use both local disks and EVS disks to store data. In addition, they can have EVS disks attached to provide a larger storage size. Use restrictions on the two types of storage media are as follows:
- Only an EVS disk, not a local disk, can be used as the system disk of a D2 ECS.
- Both EVS disks and local disks can be used as data disks of a D2 ECS.
- A maximum of 60 disks (including VBD, SCSI, and local disks) can be attached to a D2 ECS. Among the 60 disks, the maximum number of SCSI disks is 30, and the VBD disks (including the system disk) is 24. For details, see Can I Attach Multiple Disks to an ECS?
The maximum number of disks attached to an existing D2 ECS remains unchanged. To attach 60 disks, enable advanced disk. For details, see Enabling Advanced Disk.
- You are advised to use World Wide Names (WWNs), but not drive letters, in applications to perform operations on local disks to prevent drive letter drift (low probability) on Linux. Take local disk attachment as an example:
If the local disk WWN is wwn-0x50014ee2b14249f6, run the mount /dev/disk/by-id/wwn-0x50014ee2b14249f6 command.
diff --git a/docs/ecs/umn/en-us_topic_0035470100.html b/docs/ecs/umn/en-us_topic_0035470100.html index 9522f74d8..a2a372b43 100644 --- a/docs/ecs/umn/en-us_topic_0035470100.html +++ b/docs/ecs/umn/en-us_topic_0035470100.html @@ -5,115 +5,125 @@HL1 ECSs are the second generation of high-computing ECSs, featuring large memory capacity. They are interconnected with each other using 100 Gbit/s RDMA InfiniBand NICs and support 56 Gbit/s shared high I/O storage.
Specifications
-Table 1 H2 ECS specifications Flavor
+-Table 1 H2 ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory (GiB)
Maximum/Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth (Gbit/s)
Max. PPS (10,000)
+Max. PPS (10,000)
NIC Multi-Queue
+Max. NIC Queues
Virtualization Type
+Max. NICs
Local Disks
+Virtualization
Capacity of One Local Disk (TB)
+Local Disks
Network Type
+Local Disk (TB)
Hardware
+Network
+Hardware
h2.3xlarge.10
+h2.3xlarge.10
16
+16
128
+128
13/13
+13/13
90
+90
8
+8
KVM
+12
1
+KVM
3.2
+1
100 Gbit/s EDR InfiniBand
+3.2
CPU: Intel® Xeon® E5-2667 v4
+100 Gbit/s EDR InfiniBand
+CPU: Intel® Xeon® E5-2667 v4
h2.3xlarge.20
+h2.3xlarge.20
16
+16
256
+256
13/13
+13/13
90
+90
8
+8
KVM
+12
1
+KVM
3.2
+1
100 Gbit/s EDR InfiniBand
+3.2
+100 Gbit/s EDR InfiniBand
Table 2 HL1 ECS specifications Flavor
+Table 2 HL1 ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory (GiB)
Maximum/Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth (Gbit/s)
Max. PPS (10,000)
+Max. PPS (10,000)
NIC Multi-Queue
+Max. NIC Queues
Virtualization Type
+Max. NICs
Network Type
+Virtualization
Hardware
+Network
+Hardware
hl1.8xlarge.8
+hl1.8xlarge.8
32
+32
256
+256
9/9
+9/9
90
+90
8
+8
KVM
+12
100 Gbit/s EDR InfiniBand
+KVM
CPU: Intel® Xeon® Processor E5-2690 v4
+100 Gbit/s EDR InfiniBand
+CPU: Intel® Xeon® Processor E5-2690 v4
- HL1 ECSs support 56 Gbit/s shared high I/O storage.
-To support 56 Gbit/s shared high I/O storage, you only need to attach high I/O (performance-optimized I) or ultra-high I/O (latency-optimized) EVS disks to target HL1 ECSs.
Notes on Using H2 ECSs
- H2 ECSs do not support OS reinstallation or change.
- H2 ECSs do not support specifications modification.
- H2 ECSs do not support cold migration, live migration, or HA.
- H2 ECSs support the following OSs:
- For public images:
- CentOS 7.3 64bit
- SUSE Linux Enterprise Server 11 SP4 64bit
- SUSE Linux Enterprise Server 12 SP2 64bit
- For private images:
- CentOS 6.5 64bit
- CentOS 7.2 64bit
- CentOS 7.3 64bit
- SUSE Linux Enterprise Server 11 SP4 64bit
- SUSE Linux Enterprise Server 12 SP2 64bit
- Red Hat Enterprise Linux 7.2 64bit
- Red Hat Enterprise Linux 7.3 64bit
- For public images:
- H2 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.
- Each H2 ECS uses one PCIe 3.2 TB SSD card for temporary local storage.
- If an H2 ECS is created using a private image, install an InfiniBand NIC driver on the ECS after the ECS creation following the instructions provided by Mellanox. Download the required version (4.2-1.0.0.0) of InfiniBand NIC driver from the official Mellanox website and install the driver by following the instructions provided by Mellanox.
- InfiniBand NIC type: Mellanox Technologies ConnectX-4 Infiniband HBA (MCX455A-ECAT)
- Mellanox official website: http://www.mellanox.com/
- NIC driver download path: http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers
Notes on Using H2 ECSs
- H2 ECSs do not support OS reinstallation or change.
- H2 ECSs do not support specifications modification.
- H2 ECSs do not support cold migration, live migration, or HA.
- Table 3 lists the OSs supported by H2 ECSs.
++
+Table 3 Supported OS versions OS
+Version
+CentOS
+- CentOS 7.9 64bit
- CentOS 7.7 64bit
Oracle Linux
+- Oracle Linux Server release 8.4 64bit
- Oracle Linux Server release 7.6 64bit
RedHat
+Redhat Linux Enterprise 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 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- H2 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.
- Each H2 ECS uses one PCIe 3.2 TB SSD card for temporary local storage.
- If an H2 ECS is created using a private image, install an InfiniBand NIC driver on the ECS after the ECS creation following the instructions provided by Mellanox. Download the required version (4.2-1.0.0.0) of InfiniBand NIC driver from the official Mellanox website and install the driver by following the instructions provided by Mellanox.
- InfiniBand NIC type: Mellanox Technologies ConnectX-4 Infiniband HBA (MCX455A-ECAT)
- Mellanox official website: http://www.mellanox.com/
- NIC driver download path: https://network.nvidia.com/products/infiniband-drivers/linux/mlnx_ofed/
- For SUSE H2 ECSs, if IP over InfiniBand (IPoIB) is required, you must manually configure an IP address for the InfiniBand NIC after installing the InfiniBand driver. For details, see How Can I Manually Configure an IP Address for an InfiniBand NIC?
- After you delete an H2 ECS, the data stored in SSDs is automatically cleared. Therefore, do not store persistence data into SSDs during ECS running.
Notes on Using HL1 ECSs
- HL1 ECSs only support the attachment of high I/O (performance-optimized I) and ultra-high I/O (latency-optimized) EVS disks.
To support 56 Gbit/s shared high I/O storage, you only need to attach high I/O (performance-optimized I) or ultra-high I/O (latency-optimized) EVS disks to target HL1 ECSs.
- - HL1 ECSs do not support specifications modification.
- HL1 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.
- HL1 ECSs created using a private image must have the InfiniBand NIC driver installed. Download the required version (4.2-1.0.0.0) of InfiniBand NIC driver from the official Mellanox website and install the driver by following the instructions provided by Mellanox.
- InfiniBand NIC type: Mellanox Technologies ConnectX-4 Infiniband HBA (MCX455A-ECAT)
- Mellanox official website: http://www.mellanox.com/
- For SUSE HL1 ECSs, if IPoIB is required, you must manually configure an IP address for the InfiniBand NIC after installing the InfiniBand driver. For details, see How Can I Manually Configure an IP Address for an InfiniBand NIC?
- HL1 ECSs support the following OSs:
- For public images:
- CentOS 7.3 64bit
- SUSE Linux Enterprise Server 11 SP4 64bit
- SUSE Linux Enterprise Server 12 SP2 64bit
- For private images:
- CentOS 6.5 64bit
- CentOS 7.2 64bit
- CentOS 7.3 64bit
- SUSE Linux Enterprise Server 11 SP4 64bit
- SUSE Linux Enterprise Server 12 SP2 64bit
- Red Hat Enterprise Linux 7.2 64bit
- Red Hat Enterprise Linux 7.3 64bit
- For public images:
- HL1 ECSs do not support specifications modification.
- HL1 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.
- HL1 ECSs created using a private image must have the InfiniBand NIC driver installed. Download the required version (4.2-1.0.0.0) of InfiniBand NIC driver from the official Mellanox website and install the driver by following the instructions provided by Mellanox.
- InfiniBand NIC type: Mellanox Technologies ConnectX-4 Infiniband HBA (MCX455A-ECAT)
- Mellanox official website: http://www.mellanox.com/
- For SUSE HL1 ECSs, if IPoIB is required, you must manually configure an IP address for the InfiniBand NIC after installing the InfiniBand driver. For details, see How Can I Manually Configure an IP Address for an InfiniBand NIC?
- Table 4 lists the OSs supported by HL1 ECSs.
+
+Table 4 Supported OS versions OS
+Version
+CentOS
+- CentOS 7.9 64bit
- CentOS 7.7 64bit
Oracle Linux
+- Oracle Linux Server release 8.4 64bit
- Oracle Linux Server release 7.6 64bit
RedHat
+Redhat Linux Enterprise 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 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- Charging an HL1 ECS is stopped when it is stopped.
Related Links
- Enabling NIC Multi-Queue
- How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?
S2 ECSs use Intel® Xeon® Scalable processors, which significantly improve the comprehensive performance. They provide a balance of computing, memory, and network resources and a baseline level of vCPU performance with the ability to burst above the baseline. These ECSs are suitable for many applications.
Specifications
-Table 1 S3 ECS specifications Flavor
+-Table 1 S3 ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory
+(GiB)
Maximum/Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth
+(Gbit/s)
Max. PPS (10,000)
+Max. PPS
+(10,000)
NIC Multi-Queue
+Max. NIC Queues
Maximum NICs
+Max. NICs
Virtualization Type
+Virtualization
Hardware
+Hardware
s3.medium.1
+s3.medium.1
1
+1
1
+1
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
CPU: Intel® Xeon® Cascade Lake 6278
+CPU: Intel® Xeon® Cascade Lake 6278
s3.large.1
@@ -440,43 +443,46 @@Table 2 S2 ECS specifications Flavor
+Table 2 S2 ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory
+(GiB)
Maximum/Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth
+(Gbit/s)
Max. PPS (10,000)
+Max. PPS
+(10,000)
NIC Multi-Queue
+Max. NIC Queues
Maximum NICs
+Max. NICs
Virtualization Type
+Virtualization
Hardware
+Hardware
s2.medium.1
+s2.medium.1
1
+1
1
+1
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
CPU: Intel® Xeon® Skylake 6161
+CPU: Intel® Xeon® Skylake 6161
s2.large.1
@@ -878,7 +884,87 @@- Application scenarios
-Enterprise website deployment, enterprise office environment setup, enterprise R&D and testing activities, web servers, R&D and testing environments, and small-scale databases
Notes
- General-purpose ECSs support all released OSs.
Notes
Table 3 lists the OSs supported by general-purpose ECSs.
+ +
+Table 3 Supported OS versions OS
+Version
+Alma
+Alma 8 64bit
+CentOS
+- CentOS Stream 8.6 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
Debian
+- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
EulerOS
+EulerOS 2.5 64bit
+Fedora
+- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
OpenSUSE
+OpenSUSE 15.3 64bit
+Oracle Linux
+- Oracle Linux Server release 8.4 64bit
- Oracle Linux Server release 7.6 64bit
RedHat
+- Redhat Linux Enterprise 7.9 64bit
- Redhat Linux Enterprise 6.10 64bit
Rocky
+Rocky 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
SUSE-SAP
+- 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
Windows
+- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
openEuler
+openEuler 20.03 64bit
+diff --git a/docs/ecs/umn/en-us_topic_0035550301.html b/docs/ecs/umn/en-us_topic_0035550301.html index ba5dabd2c..3ddc66609 100644 --- a/docs/ecs/umn/en-us_topic_0035550301.html +++ b/docs/ecs/umn/en-us_topic_0035550301.html @@ -4,43 +4,46 @@Overview
- M4 ECSs use second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable computing performance. Using 25GE high-speed intelligent NICs, M4 ECSs provide a maximum memory size of 512 GiB based on DDR4 for memory-intensive applications with high requirements on network bandwidth and Packets Per Second (PPS).
- M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in the memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing mechanism to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive computing applications.
- M2 ECSs use Intel Xeon E5-2690 v4 CPUs and are designed for memory-optimized applications.
Specifications
-Table 1 M4 ECS specifications Flavor
+-Table 1 M4 ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory
+(GiB)
Maximum/Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth
+(Gbit/s)
Maximum PPS (10,000)
+Max. PPS
+(10,000)
NIC Multi-Queue
+Max. NIC Queues
Maximum NICs
+Max. NICs
Virtualization Type
+Virtualization
Hardware
+Hardware
m4.large.8
+m4.large.8
2
+2
16
+16
4/1.2
+4/1.2
40
+40
2
+2
2
+2
KVM
+KVM
CPU: Intel® Xeon® Cascade Lake 6266
+CPU: Intel® Xeon® Cascade Lake 6266
m4.xlarge.8
@@ -166,43 +169,46 @@Table 2 M3 ECS specifications Flavor
+-Table 2 M3 ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory
+(GiB)
Maximum/Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth
+(Gbit/s)
Maximum PPS (10,000)
+Max. PPS
+(10,000)
NIC Multi-Queue
+Max. NIC Queues
Maximum NICs
+Max. NICs
Virtualization Type
+Virtualization
Hardware
+Hardware
m3.large.8
+m3.large.8
2
+2
16
+16
1.5/0.6
+1.5/0.6
30
+30
2
+2
12
+12
KVM
+KVM
CPU: Intel® Xeon® Skylake 6151
+CPU: Intel® Xeon® Skylake 6151
m3.xlarge.8
@@ -294,39 +300,42 @@Table 3 M2 ECS specifications Flavor
+Table 3 M2 ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory
+(GiB)
Maximum/Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth
+(Gbit/s)
Maximum PPS (10,000)
+Max. PPS
+(10,000)
NIC Multi-Queue
+Max. NIC Queues
Virtualization Type
+Virtualization
Hardware
+Hardware
m2.4xlarge.8
+m2.4xlarge.8
16
+16
128
+128
8/5
+8/5
40
+40
4
+4
KVM
+KVM
CPU: Intel® Xeon® Processor E5-2690 v4
+CPU: Intel® Xeon® Processor E5-2690 v4
+Scenarios
- High-performance relational (MySQL) and NoSQL (MongoDB and Cassandra) databases
- Distributed web scale cache stores that provide in-memory caching of key-value type data (Memcached and Redis)
- Applications processing big unstructured data in real time (financial services, Hadoop/Spark clusters)
- High-performance computing (HPC) and electronic design automation (EDA)
Notes
Table 4 lists the OSs supported by memory-optimized ECSs.
+ ++
+Table 4 Supported OS versions OS
+Version
+Alma
+Alma 8 64bit
+CentOS
+- CentOS Stream 8.6 64bit
- CentOS 7.9 64bit
- CentOS 7.7 64bit
Debian
+- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
EulerOS
+EulerOS 2.5 64bit
+Fedora
+- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
OpenSUSE
+OpenSUSE 15.3 64bit
+Oracle Linux
+- Oracle Linux Server release 8.4 64bit
- Oracle Linux Server release 7.6 64bit
RedHat
+- Redhat Linux Enterprise 7.9 64bit
- Redhat Linux Enterprise 6.10 64bit
Rocky
+Rocky 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
SUSE-SAP
+- 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
Windows
+- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
openEuler
+openEuler 20.03 64bit
+diff --git a/docs/ecs/umn/en-us_topic_0035643949.html b/docs/ecs/umn/en-us_topic_0035643949.html new file mode 100644 index 000000000..d35232600 --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0035643949.html @@ -0,0 +1,63 @@ + + +Application Scenarios for Using Passwords
++The password for logging in to your ECS is important and please keep it secure. You can reset the password if it is forgotten or expires.
+Table 1 provides guidance on how to reset your password in different scenarios.
+ ++
+Table 1 Resetting a password Reference
+Prerequisites
++ +N/A
+NOTE:+The reference is for Windows or Linux ECSs.
++ +The password reset plug-ins have not been installed.
++ +The password reset plug-ins have not been installed.
++Background
Table 2 shows the ECS password complexity requirements.
+ ++
+Table 2 Password complexity requirements Parameter
+Requirement
+Example Value
+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.)
YNbUwp!dUc9MClnv
+NOTE:+The example password is generated randomly. Do not use it.
+++ diff --git a/docs/ecs/umn/en-us_topic_0037470901.html b/docs/ecs/umn/en-us_topic_0037470901.html index e8a99a8dd..488aa3ce3 100644 --- a/docs/ecs/umn/en-us_topic_0037470901.html +++ b/docs/ecs/umn/en-us_topic_0037470901.html @@ -4,7 +4,7 @@++Parent topic: Passwords+-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 modifying specifications. Therefore, when the idle capacity of the local disks of such an ECS is insufficient, you must create a new disk-intensive ECS with higher specifications for capacity expansion. In such a case, the data stored in the original ECS can be migrated to the new ECS through an EVS disk.
diff --git a/docs/ecs/umn/en-us_topic_0038024694.html b/docs/ecs/umn/en-us_topic_0038024694.html index 9dca1b4ea..2256c7582 100644 --- a/docs/ecs/umn/en-us_topic_0038024694.html +++ b/docs/ecs/umn/en-us_topic_0038024694.html @@ -3,93 +3,196 @@Procedure
- Create an EVS disk according to the volume of data to be migrated.
- Attach the EVS disk to the disk-intensive ECS.
- 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 is Stopped.
If the ECS is in the Running state, choose More > Stop to stop it.
+Procedure
- Create an EVS Disk according to the volume of data to be migrated.
- Attach the EVS disk to the disk-intensive ECS.
- 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 is Stopped.
If the ECS is in the Running state, choose More > Stop to stop it.
- 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 is Stopped.
- Ensure that a new disk-intensive ECS with higher specifications than the original one is available.
The idle local disk capacity of the new ECS must meet service 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. The page providing details about the ECS is displayed.
diff --git a/docs/ecs/umn/en-us_topic_0037633087.html b/docs/ecs/umn/en-us_topic_0037633087.html index 4c32b9a57..f586eaa58 100644 --- a/docs/ecs/umn/en-us_topic_0037633087.html +++ b/docs/ecs/umn/en-us_topic_0037633087.html @@ -12,7 +12,7 @@- Username: Administrator
- RID: 500
- LM-HASH value: C8825DB10F2590EAAAD3B435B51404EE
- NT-HASH value: 683020925C5D8569C23AA724774CE9CC
Use an image to create two ECSs, ecs01 and ecs02. Then, verify that the hash values of the cloudbase-init account for the two ECSs are different.
- LM-HASH and NTLM-HASH values of the cloudbase-init account for ecs01Figure 1 ecs01-
- LM-HASH and NTLM-HASH values of the cloudbase-init account for ecs02Figure 2 ecs02+
- LM-HASH and NTLM-HASH values of the cloudbase-init account for ecs02Figure 2 ecs02
- On the Elastic Cloud Server page, select this disk-intensive ECS and ensure that it is Stopped.
Large-Memory ECSs
Overview
Large-memory ECSs provide an even larger amount of memory than memory-optimized ECSs. They are used for applications that require a large amount of memory, rapid data switching, low latency, and process large volumes of data. Large-memory ECSs provide large memory and high computing, storage, and network performance.
Specifications
-Table 1 E3 ECS specifications Flavor
+-Table 1 E3 ECS specifications Flavor
vCPUs
+vCPUs
Memory (GiB)
+Memory
+(GiB)
Maximum/Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth
+(Gbit/s)
Maximum PPS (10,000)
+Max. PPS
+(10,000)
NIC Multi-Queue
+Max. NIC Queues
Virtualization Type
+Max. NICs
Hardware
+Virtualization
+Hardware
e3.7xlarge.12
+e3.7xlarge.12
28
+28
348
+348
25/12
+25/12
280
+280
8
+8
KVM
+8
CPU: Intel® Xeon® Skylake 6151
+KVM
+CPU: Intel® Xeon® Skylake 6151
e3.14xlarge.12
+e3.14xlarge.12
56
+56
696
+696
25/25
+25/25
500
+500
16
+16
KVM
+8
+KVM
+e3.26xlarge.14
+104
+1466
+30/20
+550
+16
+8
+KVM
+CPU: Intel® Xeon® Skylake 8176
+e3.52xlarge.14
+208
+2932
+40/40
+1000
+32
+8
+KVM
Notes
- Large-memory ECSs do not support NIC hot swapping.
- E3 ECSs support the following OSs that have been verified:
SUSE Enterprise Linux Server 12 SP2 64bit
-SUSE Enterprise Linux Server 12 SP3 64bit
- - E3 ECSs can use ultra-high I/O EVS disks as the system disk and data disks.
- The primary and extension NICs of a large-memory ECS have specified application scenarios. For details, see Table 2.
-
Table 2 Application scenarios of the NICs of a large-memory ECS NIC Type
+Notes
- Large-memory ECSs do not support NIC hot swapping.
- Specifications of large-memory ECSs can be modified only within the same flavor family.
- Affected by the memory loading speed, large-memory ECSs may take longer to start.
- Table 2 lists the OSs supported by large-memory ECSs.
+-
Table 2 Supported OS versions OS
Application Scenario
-Remarks
+Version
Primary NIC
+CentOS
Vertical layer 3 communication
-N/A
+- CentOS 7.9 64bit
- CentOS 7.7 64bit
Extension NIC
+EulerOS
Horizontal layer 2 communication
+EulerOS 2.5 64bit
To improve network performance, you can set the MTU of an extension NIC to 8888.
+Fedora
+- Fedora 35 64bit
- Fedora 34 64bit
- Fedora 33 64bit
OpenSUSE
+OpenSUSE 15.3 64bit
+Oracle Linux
+- Oracle Linux Server release 8.4 64bit
- Oracle Linux Server release 7.6 64bit
RedHat
+Redhat Linux Enterprise 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
SUSE-SAP
+- 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
Windows
+- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- An ECS can have a maximum of 60 attached disks, including the system disk. For details about constraints, see Can I Attach Multiple Disks to an ECS?
An example is provided as follows:
+ - Large-memory ECSs can use ultra-high I/O EVS disks as the system disk and data disks.
- The primary and extension NICs of a large-memory ECS have specified application scenarios. For details, see Table 3.
++
+Table 3 Application scenarios of the NICs of a large-memory ECS NIC Type
+Application Scenario
+Remarks
+Primary NIC
+Vertical layer 3 communication
+N/A
+Extension NIC
+Horizontal layer 2 communication
+To improve network performance, you can set the MTU of an extension NIC to 8888.
+ - An ECS can have a maximum of 60 attached disks, including the system disk. For details about constraints, see Can I Attach Multiple Disks to an ECS?
An example is provided as follows:
An E3 ECS is to be created. It can have a maximum of 60 attached disks, where:
- The number of system disks is 1.
- The number of EVS disks is at most 59.
The maximum number of disks attached to an existing large-memory ECS remains unchanged. To attach 60 disks, enable advanced disk. For details, see Enabling Advanced Disk.
diff --git a/docs/ecs/umn/en-us_topic_0039588795.html b/docs/ecs/umn/en-us_topic_0039588795.html index 6e0c8d021..4110dfb69 100644 --- a/docs/ecs/umn/en-us_topic_0039588795.html +++ b/docs/ecs/umn/en-us_topic_0039588795.html @@ -3,7 +3,7 @@Viewing ECS Creation Statuses
-Scenarios
After submitting the request for creating an ECS, you can view the creation status. This section describes how to view the creation status of an ECS.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- After creating an ECS, view the creation status in the task status area on the right side of common operations (Start, Stop, and More).
- Click the number displayed above Creating and view details about the tasks.
- An ECS that is being created is in one of the following states:
- Creating: The ECS is being created.
- Failures: Creating the ECS failed. In such a case, the system automatically rolls the task back 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.
+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, and More).
- Click the number displayed above Creating and view details about the tasks.diff --git a/docs/ecs/umn/en-us_topic_0040630518.html b/docs/ecs/umn/en-us_topic_0040630518.html index 3bcab9966..bef5d5f74 100644 --- a/docs/ecs/umn/en-us_topic_0040630518.html +++ b/docs/ecs/umn/en-us_topic_0040630518.html @@ -9,24 +9,18 @@
- An ECS that is being created is in one of the following states:
- Creating: The ECS is being created.
- Failures: Creating the ECS failed. In such a case, the system automatically rolls the task back 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 list displays the created ECS, 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 obtain the time zones supported by the ECS:
In the terminal display, the /user/share/zoneinfo directory contains a hierarchy of time zone data files. Use the directory structure to obtain your desired time zone file.
The directory structure shown in /user/share/zoneinfo includes both time zones and directories. The directories contain time zone files for specific cities. Locate the time zone for the city in which the ECS is located.
-For example:
-- If you are to use the time zone for Shanghai, China, run the ls /usr/share/zoneinfo/Asia command to obtain the directory /usr/share/zoneinfo/Asia/Shanghai.
- If you are to use the time zone for Paris, France, run the ls /usr/share/zoneinfo/Europe command to obtain the directory /usr/share/zoneinfo/Europe/Paris.
- Set the target time zone.
- Run the following command to open the /etc/sysconfig/clock file:
vim /etc/sysconfig/clock
- - Locate the ZONE entry and change its value to the name of the desired time zone file.
For example:
-- If the target time zone is for Shanghai, China, change the ZONE entry value as follows:
ZONE="Asia/Shanghai"
- - If the target time zone is for Paris, France, change the ZONE entry value as follows:
ZONE="Europe/Paris"
-
- If the target time zone is for Shanghai, China, change the ZONE entry value as follows:
- Run the following command to open the /etc/sysconfig/clock file:
- Locate the ZONE entry and change its value to the name of the desired time zone file.
- Press Esc. Then, run the following command to save and exit the /etc/sysconfig/clock file:
:wq
- 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/Shanghai /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:
# ls -lh /etc/localtime -lrwxrwxrwx 1 root root 33 Nov 27 11:01 /etc/localtime -> /usr/share/zoneinfo/Asia/Shanghai
+lrwxrwxrwx 1 root root 33 Nov 27 11:01 /etc/localtime -> /usr/share/zoneinfo/Asia/city1For Windows ECSs
- Log in to the ECS.
- Click the time display on the far right side of the task bar located at the bottom of your screen. In the dialog box that is displayed, click Change date and time settings.
The Date and Time page is displayed.
diff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html index f07242f06..f3ae22d8f 100644 --- a/docs/ecs/umn/en-us_topic_0041169567.html +++ b/docs/ecs/umn/en-us_topic_0041169567.html @@ -2,176 +2,232 @@Change History
-Released On
+-Released On
Description
+Description
2022-01-10
+2022-09-01
Modified the following content:
-Added "Maximum NICs" in the following sections: +Deleted ultra-high I/O ECSs.
+2022-07-20
+Added the following content:
+Ultra-high I/O ECSs
+Modified the following content:
+- Modified the constraints in Application Scenarios for Using Key Pairs.
- Modified operations in Adding Tags.
- Modified operations in Setting Alarm Rules and Viewing Audit Logs.
2022-07-11
+Modified the following content:
+- Deleted E6 ECSs and modified notes in Large-Memory ECSs.
- Added maximum NICs in High-Performance Computing ECSs.
- Modified the description in Can I Change the OS of an ECS?
2022-04-20
+Optimized the content in "Passwords and Key Pairs".
+- Added the following content: +
- Modified the content in (Recommended) Creating a Key Pair on the Management Console.
2022-04-13
+Modified the following content:
+Optimized the notes in Large-Memory ECSs.
+2022-04-07
+Modified the following content:
+Modified notes in Large-Memory ECSs.
+2022-04-02
+Modified the following content:
+Added the OSs supported by ECSs in ECS Specifications and Types.
+2022-03-11
+Modified the following content:
+Added E3 specifications e3.26xlarge.14 and e3.52xlarge.14 in Large-Memory ECSs.
+2022-03-01
+Modified the following content:
+Added the PI2 specification pi2.16xlarge.4 in GPU-accelerated ECSs.
+2022-01-19
+Modified the following content:
+Added E6 ECSs in Large-Memory ECSs.
+2022-01-10
+Modified the following content:
+Added "Max. NICs" in the following sections:2021-12-30
+2021-12-30
Modified the following content:
+Modified the following content:
- Deleted the description that the Windows Server OS supports BYOL in License Type.
- Added a note for the ECS name Step 3: Configure Advanced Settings.
2021-11-20
+2021-11-20
Added the following content:
+Added the following content:
Can ECSs Automatically Recover After the Physical Host Accommodating the ECSs Becomes Faulty?
Modified the following content:
-- Added image encryption and system disk encryption in User Encryption.
- Added description that ECSs can be created from encrypted images in ECS and Other Services.
- Added description that the system disk can be encrypted during ECS creation in Step 1: Configure Basic Settings.
- Added description that the system disk can be encrypted during OS reinstallation in Reinstalling the OS.
- Added description that the system disk can be encrypted during OS change in Changing the OS.
- Added random AZ allocation description in Step 1: Configure Basic Settings.
- Added image encryption and system disk encryption in User Encryption.
- Added description that ECSs can be created from encrypted images in ECS and Other Services.
- Added description that the system disk can be encrypted during ECS creation in Step 1: Configure Basic Settings.
- Added description that the system disk can be encrypted during OS reinstallation in Reinstalling the OS.
- Added description that the system disk can be encrypted during OS change in Changing the OS.
2021-10-20
+2021-10-20
Optimized descriptions in Step 1: Configure Basic Settings.
+Optimized descriptions in Step 1: Configure Basic Settings.
2021-09-10
+2021-09-10
- Modified the following content:
- Deleted description about Xen ECSs.
- Modified the following content:
- Deleted description about Xen ECSs.
- Deleted the following sections:
- Changing a General-Purpose ECS to an H1 ECS
- Changing a Xen ECS to a KVM ECS (Windows)
- Automatically Changing a Xen ECS to a KVM ECS (Linux)
- Manually Changing a Xen ECS to a KVM ECS (Linux)
2021-08-09
+2021-08-09
Modified the following content:
+Modified the following content:
- Added P2s ECSs in GPU-accelerated ECSs.
- Added the URL for downloading the CUDA toolkit for P2s ECSs in Obtaining a Tesla Driver and CUDA Toolkit.
2021-08-02
+2021-04-23
Modified the following content:
-Deleted descriptions about Marketplace images from Images and Step 1: Configure Basic Settings.
-2021-04-23
-Added the following content:
+Added the following content:
Added How Do I Configure atop and kdump on Linux ECSs for Performance Analysis?.
2020-11-12
+2020-11-12
Modified the following content:
+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?
2020-10-09
+2020-10-09
Added the following content:
+Added the following content:
Added the Windows Server 2019 Standard 64bit and Oracle Linux 7.6 64bit OSs supported by P2v ECSs in GPU-accelerated ECSs.
2020-09-08
+2020-09-08
Added the following content:- Added PI2 ECSs in GPU-accelerated ECSs.
Added the following content:- Added PI2 ECSs in GPU-accelerated ECSs.
Modified the following content:- Added CPU information for KVM ECSs in ECS Specifications.
- Terminated Windows OSs from the OSs supported by E1 and E2 ECSs in Large-Memory ECSs.
- Modified Basic ECS Metrics because the monitoring metric System Status Check Failed has been terminated.
2020-06-08
+2020-06-08
Modified the following content:
+Modified the following content:
Added the procedure for changing the OS keyboard language in What Should I Do If I Cannot Use the German Keyboard to Enter Characters When I Log In to a Linux ECS Using VNC?
2020-04-22
+2020-04-22
Modified the following content:
+Modified the following content:
- Added m2.4xlarge.8 in Memory-optimized ECSs.
2020-03-30
+2020-03-30
Added the following content:
+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.
2019-12-26
+2019-12-26
Added the following content:
+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.
Modified the following content:
- Changing a Xen ECS to a KVM ECS (Windows)
2019-03-13
+2019-03-13
Modified the following content:
+Modified the following content:
- Deleted E3 ECSs in Large-Memory ECSs because they have been terminated.
- Deleted "FPGA-accelerated ECSs" because such ECSs have been terminated.
2019-03-06
+2019-03-06
Modified the following content:
+Modified the following content:
- Deleted metadata types that are not supported in Obtaining Metadata.
- Added use restrictions in Passing User Data to ECSs.
2019-03-05
+2019-03-05
Deleted the following content:
+Deleted the following content:
- Deleted FAQ "Why Are Certain Flavor Quotas Separately Displayed on the Quota Page?"
- Deleted description of separately displayed quotas in Quota Adjustment.
2019-03-04
+2019-03-04
Modified the following content:
+Modified the following content:
- Modified the figure for ECS login modes in Logging In to an ECS.
- Modified the flowchart in sections "Changing a Xen ECS to a KVM ECS (Windows)" and "Automatically Changing a Xen ECS to a KVM ECS (Linux)".
2019-02-25
+2019-02-25
Modified the following content:
+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 for Modifying Specifications.
2019-02-22
+2019-02-22
Modified the following content:
+Modified the following content:
- Added operation limitations after the ECS state changes from Creating to Running in Creating an ECS.
2019-02-18
+2019-02-18
Added the following content:
+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 changing 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.
2019-02-13
+2019-02-13
Modified the following content:
+Modified the following content:
Added EulerOS and SUSE 11 to the OSs that support automatic script operations in "Automatically Changing a Xen ECS to a KVM ECS (Linux)".
2019-02-12
+2019-02-12
Modified the following content:
+Modified the following content:
- Changed the URL for downloading the PV driver and UVP VMTools in "Changing a Xen ECS to a KVM ECS (Windows)".
- Changed the URL for downloading the script in "Automatically Changing a Xen ECS to a KVM ECS (Linux)".
2019-02-03
+2019-02-03
Modified the following content:
+Modified the following content:
- Moved C3 ECSs to Dedicated General-Purpose ECSs.
2019-01-30
+2019-01-30
Added the following content:
+Added the following content:
- Added the FPGA-accelerated ECS type.
- Added Migrating an ECS.
Modified the following content:
- Changed monitoring metric names in Basic ECS Metrics.
- Terminated T series of general computing-basic ECSs.
2018-12-30
+2018-12-30
Added the following content:
+Added the following content:
- Added newly released T series of general computing-basic ECSs.
Modified the following content:
- Added newly released E3 ECSs in Large-Memory ECSs.
- Modified description in "Confirm Order" of Creating an ECS.
- Modified the Agency description in Creating an ECS.
- Modified order confirmation operations in Creating an ECS.
2018-12-22
+2018-12-22
Modified the following content:
+Modified the following content:
- Added DeH parameter description in Creating an ECS.
- Modified the flowchart and follow-up operations in "Changing a Xen ECS to a KVM ECS (Windows)".
- Modified the flowchart and follow-up operations in "Automatically Changing a Xen ECS to a KVM ECS (Linux)".
- Added UVP in Glossary.
2018-12-12
+2018-12-12
Modified the following content:
+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
2018-12-10
+2018-12-10
Added the following content:
+Added the following content:
- Changing a Xen ECS to a KVM ECS (Windows)
- Automatically Changing a Xen ECS to a KVM ECS (Linux)
Modified the following content:
- Adjusted the structure of the document.
- Modified the procedure for creating an ECS in Getting Started.
2018-11-22
+2018-11-22
KVM ECSs support automatic recovery.
+KVM ECSs support automatic recovery.
Added the following content:
- Automatically Recovering ECSs
Modified the following content:
2018-10-29
+2018-10-29
Added the following content:
+Added the following content:
- Why Are Certain Flavor Quotas Separately Displayed on the Quota Page?
2018-09-30
+2018-09-30
Modified the following content:
+Modified the following content:
- Updated supported images in Enabling NIC Multi-Queue.
2018-09-22
+2018-09-22
Modified the following content:
+Modified the following content:
- Optimized descriptions in Can I Attach Multiple Disks to an ECS?
2018-08-31
+2018-08-31
Accepted in OTC 3.2.
+Accepted in OTC 3.2.
2018-08-17
+2018-08-17
Added the following content:
+Added the following content:
Modified the following content:
- Added newly released E3 ECSs in ECS Types and Large-Memory ECSs.
- Modified description in Can I Attach Multiple Disks to an ECS?, allowing an ECS to have up to 60 attached disks.
- Added the procedure for restarting the ECS in How Can I Enable Virtual Memory on a Windows ECS?
2018-07-31
+2018-07-31
Added the following content:
+Added the following content:
- Changing the Login Password on an ECS
- Enabling Advanced Disk
- 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.
2018-07-03
+2018-07-03
Modified the following content:
+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.
2018-07-01
+2018-07-01
Added the following content:
+Added the following content:
- CTS
- How Can I Test Network Performance?
- 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.
2018-06-30
+2018-06-30
Accepted in OTC 3.1.
+Accepted in OTC 3.1.
2018-06-29
+2018-06-29
Modified the following content:
+Modified the following content:
- Terminated the full-ECS image function.
- Terminated FPGA-accelerated ECSs.
2018-06-22
+2018-06-22
Modified Elastic Cloud Server User Guide 38 according to review comments.
+Modified Elastic Cloud Server User Guide 38 according to review comments.
2018-06-14
+2018-06-14
Added the following content:
+Added the following content:
- Allowed to create ECSs using full-ECS images.
Modified the following content:
- Added description in Disk-intensive ECSs because D2 ECSs do not support automatic recovery.
2018-06-01
+2018-06-01
Modified the following content:
+Modified the following content:
- Modified FPGA-accelerated ECS specifications.
- Deleted the DSS information.
2018-05-23
+2018-05-23
Modified the following content:
+Modified the following content:
- Modified the specifications and functions of FPGA-accelerated ECSs.
- Modified the overview, specifications, and functions of D2 ECSs as well as notes on using them in Disk-intensive ECSs.
- Modified the description of automatic recovery.
- Added the description of viewing details about failed tasks in Viewing Failures.
- Added the FPGA, HDK, SDK, AEI, and DPDK terms in Glossary.
- Modified the functions of and notes on using P2 ECSs in GPU-accelerated ECSs.
- Added the OSs supported by P2 ECSs in installing a NVIDIA GPU driver and CUDA toolkit on the P2 ECSs.
- Replaced screenshots in How Do I Obtain My Disk Name in the ECS OS Using the Device Identifier Provided on the Console?
2018-04-28
+2018-04-28
Added the following content:
+Added the following content:
- Added newly released FPGA-accelerated ECSs.
- Installing a NVIDIA GPU Driver and CUDA Toolkit on a P2 ECS
- Viewing Failures
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 for Modifying 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
+2018-03-30
Added the following content:
+Added the following content:
- Added the mapping between device names and disks in How Do I Obtain My Disk Name in the ECS OS Using the Device Identifier Provided on the Console?
2018-02-07
+2018-02-07
Accepted in OTC 3.0.
+Accepted in OTC 3.0.
2018-02-03
+2018-02-03
Added the following content:
+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 for Modifying 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 General Operations for Modifying Specifications.
2018-01-26
+2018-01-26
Modified the following content:
+Modified the following content:
- Updated certain screenshots in this document.
- Added notes on using M3 ECSs.
2018-01-19
+2018-01-19
Modified the following content:
+Modified the following content:
2017-12-30
+2017-12-30
Added the following content:
+Added the following content:
- How Can I Rectify the Fault That May Occur on a Linux ECS with an NVMe SSD Disk Attached?
- Why Does the System Display a Question Mark When I Attempt to Obtain Console Logs?
Modified the following content:
- Modified notes in Enabling NIC Multi-Queue.
- Added C3, M3, and P1 ECSs in ECS Types.
- Added the function of creating a disk using DSS resources.
2017-10-27
+2017-10-27
Modified the following content:
+Modified the following content:
- Added computing I, computing II, and memory-optimized first-generation ECS types into the general-purpose ECS type in ECS Types.
2017-10-18
+2017-10-18
Modified the following content:
+Modified the following content:
- Changed the OSs supported by H2 and HL1 ECSs in High-Performance Computing ECSs.
2017-10-06
+2017-10-06
Modified the following content:
+Modified the following content:
- Added constraints on detaching an EVS disk from a running Windows ECS in Detaching an EVS Disk from a Running ECS.
2017-09-30
+2017-09-30
Added the following content:
+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?
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 for Modifying Specifications.
- Allowed attaching up to 24 EVS disks to an ECS in Can I Attach Multiple Disks to an ECS?
2017-09-18
+2017-09-18
Modified the following content:
+Modified the following content:
- Modified the overview, functions, and notes on using HL1 ECSs in High-Performance Computing ECSs.
- Modified notes in "Automatically Recovering ECSs".
- Added notes on using tools, such as ibstat in How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?
2017-09-06
+2017-09-06
Modified the following content:
+Modified the following content:
- Modified key description and added an image for the encryption process in User Encryption.
- Added the official website for downloading TightVNC in Login Overview.
- Added examples for configuring routing policies in Can I Bind Multiple EIPs to an ECS?
- Added description in Will NICs Added to an ECS Start Automatically?, indicating that only the NICs added to an ECS running the CentOS 7.0 OS requires manual activation.
- What Should I Do If I Cannot Use the German Keyboard to Enter Characters When I Log In to a Linux ECS Using VNC?
2017-08-22
+2017-08-22
Added the following content:
+Added the following content:
- Added automatic recovery.
Modified the following content:
- Modified description, indicating that SCSI EVS disks cannot be added during ECS creation.
- Deleted the description of exporting the ECS list.
- Changed the KVM ECS types to H2, M2, and HL1.
- Confirmed and modified all issues in this document.
2017-08-11
+2017-08-11
Added the following content:
+Added the following content:
- Supported the multi-project function in Project.
2017-06-07
+2017-06-07
Modified the following content:
+Modified the following content:
- Modified notes on using H2 ECSs in High-Performance Computing ECSs.
2017-06-05
+2017-06-05
Modified the following content:
+Modified the following content:
- Added the description of built-in tags in General Operations for Modifying Specifications.
2017-05-30
+2017-05-30
Modified the following content:
+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 for Modifying Specifications.
2017-05-19
+2017-05-19
Modified the following content:
+Modified the following content:
- Added Marketplace image to Image in Step 1: Configure Basic Settings.
2017-05-08
+2017-05-08
Added the following content:
+Added the following content:
2017-04-07
+2017-04-07
Added the following content:
+Added the following content:
Modified the following content:
- Added G2, M2, and H2 ECSs in ECS Types.
- Added the System Status Check Failed metric in Basic ECS Metrics.
2017-03-09
+2017-03-09
Modified the following content:
+Modified the following content:
- Changed the maximum number of tags that can be added to an ECS to 11, where 1 is automatically added by the system and the other 10 must be manually added.
- Changed one tag-related screenshot due to GUI optimization.
2017-02-03
+2017-02-03
Added the following content:
+Added the following content:
Modified the following content:
-- Modified the method of using puttygen.exe to generate key pairs in Creating a Key Pair.
- Added description in License Type, 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 PuTTYgen.
- Added description in License Type, indicating that the system does not support dynamic license type changing.
2017-01-27
+2017-01-27
Modified the following content:
+Modified the following content:
- Deleted Ubuntu from the OSs supporting BYOL in License Type.
2017-01-26
+2017-01-26
Modified the following content:
+Modified the following content:
- Added full names of acronyms in User Encryption.
- Changed the OSs supporting BYOL in License Type and Changing the OS.
- Added Red Hat Enterprise Linux.
- Added the scope of Windows OSs for using BYOL.
2017-01-20
+2017-01-20
Added the following content:
+Added the following content:
2017-01-16
+2017-01-16
Modified the following content:
-- Added Marketplace image in Images and Step 1: Configure Basic Settings.
Modified the following content:
+- Added Marketplace image in Image Types and Step 1: Configure Basic Settings.
2016-10-09
+2016-10-09
Added the following content:
+Added the following content:
- Managing ECS Groups
- Viewing ECS Creation Statuses
- Why Does the Failures Area Show an ECS Creation Failure But the ECS List Displays the Created ECS?
Modified the following content:
- Added information for remotely logging in to ECSs in Login Using VNC, Login Using an SSH Key, Login Using an SSH Password, and Login Using MSTSC.
- Added document links to the default keyboard types of the ECSs created using public images in Login Using VNC.
- Added notes on keyboard language settings for VNC-based ECS logins and the mapping between four types of keyboards in Login Using VNC. Provided configuration examples and links to related FAQs.
2016-09-30
+2016-09-30
Modified the following content:
+Modified the following content:
- Added constraints in Managing ECS Groups because ECS groups apply only to HANA ECSs and large-memory ECSs.
2016-09-28
+2016-09-28
Added the following content:
+Added the following content:
Modified the following content:
- Deleted the FAQ that is not required any more because the preset Linux ECS username has been changed after Cloud-Init is supported.
2016-09-27
+2016-09-27
Added the following content:
+Added the following content:
Modified the following content:
- Modified the instructions to configure keyboard languages in VNC logins in Login Using VNC.
2016-09-26
+2016-09-26
Modified the following content:
+Modified the following content:
- Added the instructions to configure keyboard languages in VNC logins in Login Using VNC.
2016-09-23
+2016-09-23
Added the following content:
+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.
- Added encryption algorithms and the method of using PuTTYgen to generate key pairs in Creating a Key Pair Using PuTTYgen.
2016-09-18
+2016-09-18
Added the following content:
+Added the following content:
- Expanding the Local Disks of a Disk-intensive ECS
- What Is the cloudbase-init Account in Windows ECSs Used for?
Modified the following content:
- Added the description of interactive password reset scripts in Resetting the Password for Logging In to a Linux ECS
- Added notes on using various ECSs in Memory-optimized ECSs, Disk-intensive ECSs, and High-Performance Computing ECSs.
2016-08-25
+2016-08-25
Added the following content:
+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 Viewed?
2016-07-15
+2016-07-15
Added the following content:
+Added the following content:
- Cloud-Init
- Forcible ECS shutdown
- Forcible ECS restarting
- OS changing
Modified the following content:
- ECS login modes
- OS reinstallation
2016-03-14
+2016-03-14
This issue is the first official release.
+This issue is the first official release.
curl http://169.254.169.254/latest/meta-data/instance-type
Windows:
Invoke-RestMethod http://169.254.169.254/latest/meta-data/instance-type
-s3.medium.1
+s6.medium.2
Local IPv4 (EC2 Compatible API)
Displays the fixed IP address of an ECS. If there are multiple NICs, only the IP address of the primary NIC is displayed.
diff --git a/docs/ecs/umn/en-us_topic_0046912051.html b/docs/ecs/umn/en-us_topic_0046912051.html index 927907c1c..42056bc8a 100644 --- a/docs/ecs/umn/en-us_topic_0046912051.html +++ b/docs/ecs/umn/en-us_topic_0046912051.html @@ -9,7 +9,7 @@EVS Disk Encryption
EVS disk encryption supports system disk encryption and data disk encryption.
- When creating an ECS, if you select an encrypted image, the system disk of the created ECS automatically has encryption enabled, and the encryption mode complies with the image encryption mode.
- When creating an ECS, you can encrypt its system disk.
- When creating an ECS, you can encrypt added data disks.
For more information about EVS disk encryption, see Elastic Volume Service User Guide.
+For more information about EVS disk encryption, see Elastic Volume Service User Guide.
@@ -53,7 +53,7 @@Impact on AS
If you use an encrypted ECS to create an Auto Scaling (AS) configuration, the encryption mode of the created AS configuration complies with the ECS encryption mode.
- 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. Therefore, 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_0047654687.html b/docs/ecs/umn/en-us_topic_0047654687.html index a7667459c..631aed4dc 100644 --- a/docs/ecs/umn/en-us_topic_0047654687.html +++ b/docs/ecs/umn/en-us_topic_0047654687.html @@ -4,13 +4,13 @@-diff --git a/docs/ecs/umn/en-us_topic_0048642616.html b/docs/ecs/umn/en-us_topic_0048642616.html index c41f24415..886e0a479 100644 --- a/docs/ecs/umn/en-us_topic_0048642616.html +++ b/docs/ecs/umn/en-us_topic_0048642616.html @@ -9,10 +9,10 @@Symptom
When you try to import a key pair that you created using puttygen.exe on the management console, the system displays a message indicating that the import failed.
Possible Causes
The format of the public key content does not meet system requirements.
-If you store a public key by clicking Save public key of puttygen.exe, the format of the public key content will change. Therefore, you cannot import the key on the management console.
+If you store a public key by clicking Save public key on PuTTY Key Generator, the format of the public key content will change. Therefore, you cannot import the key on the management console.
Solution
Use the locally stored private key and PuTTY Key Generator to restore the format of the public key content. Then, import the public key to the management console.
-- Double-click puttygen.exe to switch to the PuTTY Key Generator page.Figure 1 PuTTY Key Generator+
- Double-click puttygen.exe to open PuTTY Key Generator.Figure 1 PuTTY Key Generator
- Click Load and select the private key.
The system automatically loads the private key and restores the format of the public key content in PuTTY Key Generator. The content in the red box in Figure 2 is the public key whose format meets system requirements.
- - Copy the public key content to a .txt file and save the file in a local directory.
- Import the public key to the management console.
- 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 right side of the page, click Import Key Pair.
- Copy the public key content in the .txt file to Public Key Content and click OK.
- Copy the public key content to a .txt file and save the file in a local directory.
- Import the public key to the management console.
- 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 page, click Import Key Pair.
- Copy the public key content in the .txt file to Public Key Content and click OK.
- Double-click puttygen.exe to open PuTTY Key Generator.
After Cloud-Init or Cloudbase-Init is 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. Passing User Data to ECSsFor details, see Passing User Data to ECSs.
- If Cloud-Init is supported, ECSs do not support password authentication anymore. All newly created ECSs use key pair authentication. This change will influence your ECS logins. For details, see the following sections: -
- If Cloud-Init is supported, you can view and use metadata to configure and manage running ECSs. Obtaining MetadataFor more information, see Obtaining Metadata.
-Impact on ECS
- When creating an ECS, if the selected image supports Cloud-Init, you can use the User Data function to specify custom configuration, such as ECS login password to the ECS. Such custom settings will take effect upon ECS initialization. For details, see Passing User Data to ECSs.
- If Cloud-Init is supported, ECSs do not support password authentication anymore. All newly created ECSs use key pair authentication. This change will influence your ECS logins. For details, see the following sections: +
- If Cloud-Init is supported, you can view and use metadata to configure and manage running ECSs. For details, see Obtaining Metadata.
Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
+Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0058758453.html b/docs/ecs/umn/en-us_topic_0058758453.html index df4e44580..9966d6aae 100644 --- a/docs/ecs/umn/en-us_topic_0058758453.html +++ b/docs/ecs/umn/en-us_topic_0058758453.html @@ -146,13 +146,13 @@Notes
- When using Cloud-Init, enable DHCP in the VPC to which the ECS belongs.
- When using Cloud-Init, ensure that security group rules for the outbound direction meet the following requirements:
- Protocol: TCP
- Port: 80
- Destination: 169.254.0.0/16
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:- 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.
diff --git a/docs/ecs/umn/en-us_topic_0060610074.html b/docs/ecs/umn/en-us_topic_0060610074.html index dff7ef3c0..b12a9ba62 100644 --- a/docs/ecs/umn/en-us_topic_0060610074.html +++ b/docs/ecs/umn/en-us_topic_0060610074.html @@ -3,7 +3,7 @@Exporting ECS Information
-Scenarios
The information of all ECSs under your account can be exported in CSV format to a local directory. The file records the IDs, private IP addresses, and EIPs of your ECSs.
diff --git a/docs/ecs/umn/en-us_topic_0074752335.html b/docs/ecs/umn/en-us_topic_0074752335.html index 5a4b964f6..c8ea5f390 100644 --- a/docs/ecs/umn/en-us_topic_0074752335.html +++ b/docs/ecs/umn/en-us_topic_0074752335.html @@ -5,7 +5,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the upper right corner of the ECS list, click
.The system will automatically export all ECSs in the current region under your account to a local directory.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the upper right corner of the ECS list, click .
The system will automatically export all ECSs in the current region under your account to a local directory.
- In the lower left corner of your local computer desktop, obtain the exported file servers.csv.
Constraints
This method applies only to Linux ECSs.
Procedure
For example, there are two ECSs in a VPC, ecs-01 and ecs-02. Perform the following operations to enable communication using hostnames between ecs-01 and ecs-02:
-- Log in to ecs-01 and ecs-02 and obtain their private IP addresses.
- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, obtain the private IP address in the IP Address column.
For example, the obtained private IP addresses are as follows:
+- Log in to ecs-01 and ecs-02 and obtain their private IP addresses.
- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, obtain the private IP address in the IP Address column.
For example, the obtained private IP addresses are as follows:
ecs-01: 192.168.0.1
ecs-02: 192.168.0.2
ecs-01: hostname01
ecs-02: hostname02
- Log in to ecs-01 and ecs-02 and obtain their private IP addresses.
- Create mapping between the hostnames and IP addresses and add information about other ECSs in the same VPC.
- Log in to ecs-01.
- Run the following command to switch to user root:
sudo su -
+ - Create a mapping between the hostnames and IP addresses and add information about other ECSs in the same VPC.
- Log in to ecs-01.
- Run the following command to switch to user root:
sudo su -
- Run the following command to edit the hosts configuration file: -
- Press i to enter editing mode.
- Add the statement in the following format to set up the mapping: +
- Press i to enter editing mode.
- Add the statement in the following format to set up the mapping:
For example, add the following statement:
192.168.0.1 hostname01
192.168.0.2 hostname02
diff --git a/docs/ecs/umn/en-us_topic_0076210995.html b/docs/ecs/umn/en-us_topic_0076210995.html index 1122fc122..55f7b79ee 100644 --- a/docs/ecs/umn/en-us_topic_0076210995.html +++ b/docs/ecs/umn/en-us_topic_0076210995.html @@ -29,7 +29,7 @@ Command (m for help):Figure 3 Creating a new partition
- Enter the new partition's start cylinder number and press Enter.
The start cylinder number must be greater than the end cylinder numbers of existing partitions. In this example, use the default value for the new partition's start cylinder number and press Enter. Information similar to the following is displayed.
Figure 4 Specifying the new partition's start cylinder number-
- Enter the new partition's end cylinder number and press Enter.
In this example, use the default value for the new partition's end cylinder number and press Enter. Information similar to the following is displayed.
+ - Enter the new partition's end cylinder number and press Enter.
In this example, use the default value for the new partition's end cylinder number and press Enter. Information similar to the following is displayed.
Figure 5 Specifying the new partition's end cylinder number
- Enter p and press Enter to view the created partition.
Information similar to the following is displayed.
Figure 6 Viewing the created partition@@ -92,9 +92,9 @@ Writing superblocks and filesystem accounting information: done
- Press Esc, run the following command, and press Enter. The system saves the configurations and exits the vi editor.
:wq
If you want to detach a new disk for which automatic mounting upon system startup has been set, you must delete the automatic mounting configuration before you detach the disk. Otherwise, the ECS cannot be started after you detach the disk. To delete the automatic mounting configuration, perform the following operations:
-- Run the following command to open the fstab file using the vi editor:
vi /etc/fstab
+- Run the following command to open the fstab file using the vi editor:
vi /etc/fstab
- Press i to enter editing mode.
- Delete the following statement:
UUID=96e5e028-b0fb-4547-a82a-35ace1086c4f /root/new ext4 defaults 0 0
- - Press Esc, run the following command, and press Enter. The system saves the configurations and exits the vi editor.
:wq
+ - Press Esc, run the following command, and press Enter. The system saves the configurations and exits the vi editor.
:wq
- Run the following command to open the fstab file using the vi editor:
Initializing a Windows Data Disk (Windows Server 2008)
Scenarios
This section uses Windows Server 2008 R2 Enterprise 64bit to describe how to initialize a data disk attached to a server running Windows.
-The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. For details about disk partition styles, see Scenarios and Disk Partitions.
+The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. To learn more about disk partition styles, see Scenarios and Disk Partitions.
The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.
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.
- On the displayed New Simple Volume Wizard window, click Next.Figure 6 New Simple Volume Wizard
- Specify the volume size and click Next. The default value is the maximum size.Figure 7 Specify Volume Size
- Assign the driver letter and click Next.Figure 8 Assign Driver Letter or Path-
- Select Format this volume with the following settings, set parameters based on the actual requirements, and select Perform a quick format. Then, click Next.Figure 9 Format Partition+
- On the displayed Format Partition page, click Format this volume with the following settings, set parameters based on the requirements, and select Perform a quick format. Then, click Next.Figure 9 Format PartitionFigure 10 Completing the partition creation
diff --git a/docs/ecs/umn/en-us_topic_0085634797.html b/docs/ecs/umn/en-us_topic_0085634797.html index 4e0da7c6c..3e0e15387 100644 --- a/docs/ecs/umn/en-us_topic_0085634797.html +++ b/docs/ecs/umn/en-us_topic_0085634797.html @@ -2,16 +2,16 @@ The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.
Initializing a Linux Data Disk (fdisk)
Scenarios
This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.
-The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. In Linux, if you choose to use the GPT partition style, the fdisk partitioning tool cannot be used. Use the parted partitioning tool instead. For details about disk partition styles, see Scenarios and Disk Partitions.
+The maximum partition size that MBR supports is 2 TB and that GPT supports is 18 EB. If the disk size you need to partition is greater than 2 TB, partition the disk using GPT.
+The partitioning tool fdisk is suitable only for MBR partitions, and parted is suitable for both MBR and GPT partitions. For more information, see Scenarios and Disk Partitions.
The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.
-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 is the default partition style. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured with automatic mounting at system start.
+-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 with automatic mounting at system start.
- Run the following command to query information about the new data disk:
fdisk -l
-Information similar to the following is displayed:[root@ecs-test-0001 ~]# fdisk -l +
- fdisk -lInformation similar to the following is displayed:-
[root@ecs-test-0001 ~]# fdisk -l Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors Units = sectors of 1 * 512 = 512 bytes @@ -66,8 +66,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 @@ -132,6 +132,8 @@ Writing superblocks and filesystem accounting information: done - Run the following command to create a mount point:
mkdir Mount point
In this example, run the following command to create the /mnt/sdc mount point:
mkdir /mnt/sdc
+ The /mnt directory exists on all Linux systems. If the mount point fails to create, it may be that the /mnt directory has been accidentally deleted. Run the mkdir -p /mnt/sdc command to create the mount point.
+ - Run the following command to mount the new partition on the created mount point:
mount Disk partition Mount point
In this example, run the following command to mount the new partition /dev/vdb1 on /mnt/sdc:
mount /dev/vdb1 /mnt/sdc
@@ -162,7 +164,7 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0 /dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
The UUID of the /dev/vdb1 partition is displayed.
- Run the following command to open the fstab file using the vi editor:
vi /etc/fstab
-- Press i to enter the editing mode.
- Move the cursor to the end of the file and press Enter. Then, add the following information:
UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2
+- Press i to enter editing mode.
- Move the cursor to the end of the file and press Enter. Then, add the following information:
UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2
- Press Esc, enter :wq, and press Enter.
The system saves the configurations and exits the vi editor.
- Perform the following operations to verify the automatic mounting function:
- Run the following command to unmount the partition:
In this example, run the following command:
@@ -171,7 +173,7 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0 - Run the following command to query the file system mounting information:
In this example, run the following command:
mount | grep /mnt/sdc
-If information similar to the following is displayed, the automatic mounting function takes effect:
+If information similar to the following is displayed, automatic mounting has been configured:
root@ecs-test-0001 ~]# mount | grep /mnt/sdc /dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
Initializing a Linux Data Disk (parted)
Scenarios
This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.
-The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. In Linux, if you choose to use the GPT partition style, the fdisk partitioning tool cannot be used. Use the parted partitioning tool instead. For details about disk partition styles, see Scenarios and Disk Partitions.
+The maximum partition size that MBR supports is 2 TB and that GPT supports is 18 EB. If the disk size you need to partition is greater than 2 TB, partition the disk using GPT.
+The partitioning tool fdisk is suitable only for MBR partitions, and parted is suitable for both MBR and GPT partitions. For more information, see Scenarios and Disk Partitions.
The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.
-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 is used as the partition style. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured automatic mounting at system start.
+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 with automatic mounting at system start.
- Run the following command to query information about the new data disk:
lsblk
Information similar to the following is displayed:root@ecs-test-0001 ~]# lsblk @@ -120,6 +121,8 @@ Writing superblocks and filesystem accounting information: done
- Run the following command to create a mount point:
mkdir Mount point
In this example, run the following command to create the /mnt/sdc mount point:
mkdir /mnt/sdc
+ - Run the following command to create a mount point:
- fdisk -l
- An ECS that is being created is in one of the following states:
- Run the following commands to save the iptables configuration and make it start up automatically upon ECS startup:
- Stop the original ECS, detach the system disk from it, and attach the system disk to the temporary ECS.
- Server List: The ECS to be backed up is selected by default. Click
- If the ECS has been associated with a vault, configure the backup information as prompted.
- If the ECS has been associated with a vault, configure the backup information as prompted.
