What Is CBR?
Cloud Backup and Recovery (CBR) enables you to back up cloud servers and disks with ease. In case of a virus attack, accidental deletion, or software or hardware fault, you can restore data to any point in the past when the data was backed up.
+What Is CBR?
Cloud Backup and Recovery (CBR) enables you to back up cloud servers and disks with ease. In case of a virus attack, accidental deletion, or software or hardware fault, you can restore data to any point in the past when the data was backed up.
CBR protects your services by ensuring the security and consistency of your data.
What Are the Differences Between Backup, Snapshot, and Image?
You can use the cloud server backup function to create ECSs and the cloud disk backup function to create EVS disks.
@@ -95,7 +95,7 @@CBR Architecture
CBR consists of backups, vaults, and policies.
+CBR Architecture
CBR consists of backups, vaults, and policies.
- Backup
A backup is a copy of a particular chunk of data and is usually stored elsewhere so that it may be used to restore the original data in the event of data loss. CBR supports the following backup types:
- Cloud server backup: This type of backup uses the consistency snapshot technology for disks to protect data of ECSs and BMSs. The backups of servers without deployed databases are common server backups, and those of servers with deployed databases are application-consistent backups.
- Cloud disk backup: This type of backup provides snapshot-based data protection for EVS disks.
- Vault
CBR uses vaults to store backups. Before creating a backup, you need to create at least one vault and associate the resource you want to back up with the vault. Then the backup of the resource is stored in the associated vault.
@@ -164,7 +164,7 @@
Backing Up an ECS Data
+Backing Up an ECS
Scenarios
CBR enhances data integrity and service continuity. For example, if an ECS or EVS disk is faulty or a misoperation causes data loss, you can use data backups to quickly restore data. This section describes how to back up ECSs and EVS disks.
For more information, CBR Architecture, Backup Mechanism, and Backup Options.
- Cloud Server Backup (recommended): Use this backup function if you want to back up the data of all EVS disks (system and data disks) on an ECS. This prevents data inconsistency caused by time difference in creating a backup.
- Cloud Disk Backup: Use this backup function if you want to back up the data of one or more EVS disks (system or data disk) on an ECS. This minimizes backup costs on the basis of data security.
ECS Backup Procedure
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Server Backup in the Operation column.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the ECS to be associated. The storage capacity used by the backup increases accordingly.
-ECS Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Server Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the ECS to be associated. The storage capacity used by the backup increases accordingly.
- If the ECS is not associated with a vault, buy a vault first and then configure the backup information as prompted.
For details, see Creating a Server Backup Vault.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Click OK. The system automatically creates a backup for the ECS.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
@@ -14,10 +14,10 @@After the backup is complete, you can restore server data or create images on the Backups tab page. For details, see Restoring from a Cloud Server Backup and Using a Backup to Create an Image.
EVS Disk Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Disk Backup in the Operation column.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default. Click
to view the disks attached to the ECSs. Select the disks to be backed up. - Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the disks to be associated. The storage capacity used by the backup increases accordingly.
EVS Disk Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Disk Backup.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default. Click to view the disks attached to the ECSs. Select the disks to be backed up.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the disks to be associated. The storage capacity used by the backup increases accordingly.
- Server List: The ECS to be backed up is selected by default. Click
- If the ECS is not associated with a vault, buy a vault first and then configure the backup information as prompted.
For details, see Creating a Disk Backup Vault.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Click OK. The system automatically creates a backup for the disk.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
+ - Click OK. The system automatically creates a backup for the disk.
On the Backups tab of the CBR console, if the status of the backup is Available, the backup task is successful.
If some files are deleted from the disk during the backup, the deleted files may fail to be backed up. Therefore, to ensure data integrity, delete the target data after the backup is complete.
After the backup is complete, you can restore disk data on the Backups tab page. For details, see Restoring from a Cloud Disk Backup.
diff --git a/docs/ecs/umn/en-us_topic_0000001138811177.html b/docs/ecs/umn/en-us_topic_0000001138811177.html index 6f08dcb7..6577cbc7 100644 --- a/docs/ecs/umn/en-us_topic_0000001138811177.html +++ b/docs/ecs/umn/en-us_topic_0000001138811177.html @@ -6,8 +6,8 @@-Parent topic: Backup Using CBR+Parent topic: CBRRoot Cause
Run the following command on the Linux ECS configured with a static IP address:
# ip route| grep 169.254
The route with the destination of 169.254.169.254 does not exist, but the route with the destination of 169.254.0.0/16 exists.
-Figure 1 Route information-
After the network is restarted, the original route with the destination of 169.254.169.254 is changed to the route with the destination of 169.254.0.0/16 without a next hop. As a result, the Linux ECS cannot obtain metadata.
+ +After the network is restarted, the original route with the destination of 169.254.169.254 is changed to the route with the destination of 169.254.0.0/16 without a next hop, as shown in Figure 1. As a result, the Linux ECS cannot obtain metadata.
Solution
- Add the route with the destination of 169.254.169.254, and specify the next hop (gateway) and the output device (primary NIC of the Linux ECS). The following is an example:
# ip route add 169.254.169.254 via 192.168.1.1 dev eth0
192.168.1.1 is the gateway address of the subnet that the primary NIC resides, and eth0 is the primary NIC.
diff --git a/docs/ecs/umn/en-us_topic_0000001210881033.html b/docs/ecs/umn/en-us_topic_0000001210881033.html index 57b31714..44598bdc 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_0000001278335673.html b/docs/ecs/umn/en-us_topic_0000001278335673.html index fc22220d..efc53f4e 100644 --- a/docs/ecs/umn/en-us_topic_0000001278335673.html +++ b/docs/ecs/umn/en-us_topic_0000001278335673.html @@ -2,13 +2,13 @@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. Key Pair Service (KPS) stores the public key and you store the private key. If you have imported a public key into a Linux ECS, you can use the corresponding private key to log in to the ECS without a password. Therefore, you do not need to worry about password interception, cracking, or leakage.
+A key pair consists of a public key and a private key. Key Pair Service (KPS) stores the public key and you store the private key. If you have imported a public key into a Linux ECS, you can use the corresponding private key to log in to the ECS without a password. You do not need to worry about password interception, cracking, or leakage.
@@ -16,7 +16,7 @@Scenarios
When purchasing an ECS, you are advised to select the key pair login mode. For Windows ECSs, key pairs are required to decrypt the passwords so that you can use the decrypted password to log in.
- Logging in to a Linux ECSYou can directly use a key pair to log in.
- When you are creating the ECS, select the key pair login mode. For details, see "Set Login Mode" in Step 3: Configure Advanced Settings.
- After the ECS is created, bind a key pair to the ECS by referring to "Binding a Key Pair" in the Data Encryption Workshop User Guide.
- Logging in to a Windows ECS
You can use the key pair to obtain a password for login. The password is randomly generated and therefore is more secure.
+- Logging in to a Windows ECS
You can use the key pair to obtain a password for login. The password is randomly generated and is more secure.
For details, see Obtaining the Password for Logging In to a Windows ECS.
- Logging in to a Windows ECS
- 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.
+ - Using an existing key pair
If an existing key pair (created using PuTTYgen, for example) is available, you can import the public key by referring to Importing a Key Pair on the management console to let the system maintain your public key.
diff --git a/docs/ecs/umn/en-us_topic_0000001278350057.html b/docs/ecs/umn/en-us_topic_0000001278350057.html index 3d49ce3e..cc2b0453 100644 --- a/docs/ecs/umn/en-us_topic_0000001278350057.html +++ b/docs/ecs/umn/en-us_topic_0000001278350057.html @@ -3,7 +3,7 @@
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?
(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 displayed page, click Create Key Pair.
- Enter a key pair name.
A key pair name consists of two parts: KeyPair and four random digits (KeyPair-xxxx).
+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 displayed page, click Create Key Pair.
- Enter a key pair name.
A key pair name consists of two parts: KeyPair and four random digits (KeyPair-xxxx).
- Click OK.
- 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_0018078523.html b/docs/ecs/umn/en-us_topic_0018078523.html index 365de379..cd8a78c1 100644 --- a/docs/ecs/umn/en-us_topic_0018078523.html +++ b/docs/ecs/umn/en-us_topic_0018078523.html @@ -2,7 +2,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose Key Pair.
- On the Key Pair Service page, click Import Key Pair.Figure 1 Import Public 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 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.
diff --git a/docs/ecs/umn/en-us_topic_0000001630328828.html b/docs/ecs/umn/en-us_topic_0000001630328828.html index 5e46ceaa..0328e192 100644 --- a/docs/ecs/umn/en-us_topic_0000001630328828.html +++ b/docs/ecs/umn/en-us_topic_0000001630328828.html @@ -21,7 +21,7 @@ -Attribute value
+Property value
Automatic property matching
ID
@@ -38,7 +38,7 @@When you search by keyword, enter a complete property value instead of selecting a property. The system can automatically match the property type for search.
Attribute value
+Property value
Fuzzy search
Name
@@ -58,7 +58,7 @@All properties on the console
Attribute: Value
+Property: Value
Private IP Address: 192.168.99.231
All properties on the console
Attribute 1: Value Attribute 2: Value
+Property 1: Value Property 2: Value
Private IP Address: 192.168.99.231 Name: ecs-c
Example 1: Searching by Attribute Value
After you enter a complete property value, the system automatically identifies the property type and search for it.
+-Example 1: Searching by Property Value
After you enter a complete property value, the system automatically identifies the property type and search for it.
Example 2: Searching by a Single Attribute
Select a property, and enter or choose the corresponding property value.
+Example 2: Searching by a Single Property
Select a property, and enter or choose the corresponding property value.
The following properties only support exact search and you need to enter complete values for them: ID, EIP, image ID, and VPC ID.
- Fuzzy search by private IP address
- Select Private IP Address in the search box.
- Enter a private IP address and press Enter to search. Private IP addresses can be used for fuzzy search. For example, you can enter 192.168.0 to search for all ECSs that use the 192.168.0 IP address.
- Exact search by ID
- Select ID in the search box.
- Enter a complete ECS ID and press Enter to search.
General Operations
-Scenarios
If ECS specifications do not meet service requirements, you can modify the ECS specifications, including vCPUs and memory. Certain ECSs allow you to change their types when you modify their specifications.
+-Scenarios
If ECS specifications do not meet service requirements, you can modify the ECS specifications, including vCPUs and memory. Certain ECSs allow you to change their types when you modify their specifications.
-Background
To obtain the virtualization type of an ECS, perform the following operations:
- On the page providing details about the ECS, view the ECS specifications.Figure 1 Viewing ECS specifications
- Check the specifications tables in ECS Types for the virtualization type.
Notes
- Downgrading ECS specifications (vCPU or memory) will reduce performance.
- Certain ECS types do not support specifications modification currently. For details about available ECS types as well as their functions and usage, see "NOTE" 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
- Downgrading ECS specifications (vCPU or memory) will reduce performance.
- Certain ECS types do not support specifications modification currently. For details about available ECS types and functions, see ECS Types. For details about restrictions on using different types of ECSs, see their notes.
- When the disk status is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.
- Before modifying the specifications of a Windows ECS, modify the SAN policy by following the instructions provided in Why Does a Disk Attached to a Windows ECS Go Offline? to prevent disks from going offline after the specifications are modified.
- Before modifying specifications, make sure that the ECS has been stopped.
Step 1: Modify Specifications
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, view the status of the target ECS.
If the ECS is not in Stopped state, click More in the Operation column and select Stop.
- - Click More in the Operation column and select Modify Specifications.
The Modify ECS Specifications page is displayed.
+Step 1: Modify Specifications
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, view the status of the target ECS.
If the ECS is not in Stopped state, 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.Figure 2 Modifying specifications
- (Optional) Set DeH.
If the ECS is created on a DeH, the system allows you to change the DeH.
To do so, select the target DeH from the drop-down list. If no DeH is available in the drop-down list, remaining DeH resources are insufficient and cannot be used to create the ECS with specifications modified.
@@ -27,7 +27,7 @@
diff --git a/docs/ecs/umn/en-us_topic_0013771101.html b/docs/ecs/umn/en-us_topic_0013771101.html index cf10ac81..20b32028 100644 --- a/docs/ecs/umn/en-us_topic_0013771101.html +++ b/docs/ecs/umn/en-us_topic_0013771101.html @@ -12,6 +12,8 @@Follow-up Procedure
Perform the following operations in the event of a specifications modification failure:
-- Log in to the management console.
- Under Management & Deployment, choose Cloud Trace Service.
- In the navigation pane on the left, choose Trace List.
- In the Trace Name column, locate the resizeServer event by resource ID.
The resource ID is the ID of the ECS on which the specifications modification failed.
+- Log in to the management console.
- Under Management & Deployment, choose Cloud Trace Service.
- In the navigation pane on the left, choose Trace List.
- In the Trace Name column, locate the resizeServer event by resource ID.
The resource ID is the ID of the ECS on which the specifications modification failed.
- Click View Trace in the Operation column to view the failure cause.
If the fault cannot be rectified based on logs, contact customer service.
- Login and Connection
+ - Usage Errors
+ - ECS Management
- OS Management
diff --git a/docs/ecs/umn/en-us_topic_0013771110.html b/docs/ecs/umn/en-us_topic_0013771110.html index bf715d2a..339bc7a1 100644 --- a/docs/ecs/umn/en-us_topic_0013771110.html +++ b/docs/ecs/umn/en-us_topic_0013771110.html @@ -7,19 +7,19 @@
Stopping ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Stop in the upper left corner of the list.
- In the displayed dialog box, select Forcibly stop the preceding ECSs based on your service requirements.
After an ECS is forcibly stopped, unsaved data on the ECS will be lost.
+-Stopping ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Stop in the upper left corner of the list.
- In the displayed dialog box, select Forcibly stop the preceding ECSs based on your service requirements.
After an ECS is forcibly stopped, unsaved data on the ECS will be lost.
- Click Yes to stop the ECSs.
Contact the administrator if the ECS has been in the Stopping state for more than 30 minutes.
Restarting ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Restart in the upper left corner of the list.
After an ECS is forcibly restarted, unsaved data on the ECS will be lost.
+-Restarting ECSs
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Restart in the upper left corner of the list.
After an ECS is forcibly restarted, unsaved data on the ECS will be lost.
- Click Yes to stop the ECSs.
Contact the administrator if the ECS has been in the Restarting state for more than 30 minutes.
Deleting an ECS
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Delete in the upper left corner of the list. -
Contact the administrator if the ECS has been in the Deleting state for more than 30 minutes.
+diff --git a/docs/ecs/umn/en-us_topic_0013771112.html b/docs/ecs/umn/en-us_topic_0013771112.html index 90f4c840..06ebf00f 100644 --- a/docs/ecs/umn/en-us_topic_0013771112.html +++ b/docs/ecs/umn/en-us_topic_0013771112.html @@ -8,7 +8,7 @@Deleting an ECS
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Delete in the upper left corner of the list.
Contact the administrator if the ECS has been in the Deleting state for more than 30 minutes.
- You can deploy ECSs across different availability zones (AZs) that are connected over an intranet. If one AZ becomes unavailable, ECSs in other AZs can continue to provide services.
- Virtual Private Cloud (VPC) helps you build your own dedicated network on the cloud. You can set subnets and security groups within your VPC for further isolation. You can also bind an EIP to your ECSs for Internet access.
- With the Image Management Service (IMS), you can use an image to create ECSs. You can also 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. Volume Backup Service (VBS) provides data backup and restoration.
- 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.
- Backup protection: You can back up all EVS disks (including the system disk and data disks) attached to an ECS and use the backup to restore the ECS data.
Figure 1 System architecture
Access Methods
You can access ECS through the web-based management console or HTTPS-based application programming interfaces (APIs).- Accessing ECSs through APIs
Use this method if you intend to integrate ECSs into a third-party system for secondary development. For details, see Elastic Cloud Server API Reference.
+Access Methods
You can access ECS through the web-based management console or HTTPS-based application programming interfaces (APIs).- Accessing ECSs through APIs
Use this method if you intend to integrate ECSs into a third-party system for secondary development. For details, see Elastic Cloud Server API Reference.
- Accessing ECSs through the management console
Use this method if you are not required to integrate ECSs with a third-party system.
Log in to the management console with your account and choose Elastic Cloud Server on the homepage.
-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, choose Elastic Cloud Server.
The Elastic Cloud Server page is displayed. On this page, you can view your ECSs and the basic information about the ECSs, such as their specifications, images, and IP addresses.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
The Elastic Cloud Server page is displayed. On this page, you can view your ECSs and the basic information about the ECSs, such as their specifications, images, and IP addresses.
- In the search box above the ECS list, select a filter (such as ECS name, ID, or private IP address), enter the corresponding information, and press Enter.
- Click the name of the target ECS.
The page providing details about the ECS is displayed.
- View the ECS details.
You can click the tabs and perform operations. For details, see Changing a Security Group, Adding a Network Interface, Adding Tags, and Binding an EIP.
Remotely Logging In to a Windows ECS (Using MSTSC)
-Scenarios
This section describes how to use the remote login tool MSTSC to log in to a Windows ECS from a local computer.
Prerequisites
- The target ECS is running.
- You have obtained the password for logging in to the Windows ECS. For details, see Obtaining the Password for Logging In to a Windows ECS.
- You have bound an EIP to the ECS. For details, see Binding an EIP.
Prerequisites
- The target ECS is running.
- You have obtained the password for logging in to the Windows ECS. For details, see Obtaining the Password for Logging In to a Windows ECS.
- You have bound an EIP to the ECS. For details, see Binding an EIP.
- Access to port 3389 is allowed in the inbound direction of the security group to which the ECS belongs. For details, see Configuring Security Group Rules.
- The network connection between the login tool and the target ECS is normal. For example, the default port 3389 is not blocked by the firewall.
- Remote Desktop Protocol (RDP) needs to be enabled on the target ECS. For ECSs created using public images, RDP has been enabled by default. For instructions about how to enable RDP, see Enabling RDP.
-Logging In to a Windows ECS Using MSTSC
If your local server runs Windows, you can use the remote desktop connection tool MSTSC delivered with the Windows OS to log in to a Windows ECS.
@@ -13,10 +13,10 @@Figure 2 Remote Desktop Connection
- (Optional) To use local server resources in a remote session, configure parameters on the Local Resources tab.
To copy data from the local server to your ECS, select Clipboard.-Figure 3 Clipboard
To copy files from the local server to your ECS, click More and select your desired disks.diff --git a/docs/ecs/umn/en-us_topic_0017955633.html b/docs/ecs/umn/en-us_topic_0017955633.html index 03afd54b..ae7cd27c 100644 --- a/docs/ecs/umn/en-us_topic_0017955633.html +++ b/docs/ecs/umn/en-us_topic_0017955633.html @@ -5,7 +5,7 @@Figure 4 Drives+
To copy files from the local server to your ECS, click More and select your desired disks.Figure 4 Drives- (Optional) Click the Display tab and then adjust the size of the remote desktop.
Figure 5 Adjusting the size of the desktop-
- Click Connect and enter the login password as prompted to log in to the ECS.
To ensure system security, change the login password after you log in to the ECS for the first time.
+- Click Connect and enter the login password as prompted to log in to the ECS.
To ensure system security, change the login password after you log in to the ECS for the first time.
- (Optional) Copy local files to the Windows ECS using clipboard. If the file size is greater than 2 GB, an error will occur.
To resolve this issue, see troubleshooting cases.
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.
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
@@ -15,10 +15,10 @@- Run the following command to change the ssh_pwauth value to 1 or true in /etc/cloud/cloud.cfg:
sudo vi /etc/cloud/cloud.cfg
- Run the following command to reload the sshd service:
-To ensure system security, reset the common user password for logging in to the Linux ECS.
+To ensure system security, reset the common user password for logging in to the Linux ECS.
- Run the following command to reset the ECS password:
If the ECS username is linux, run the following command:
sudo passwd linux
- To remotely log in to an ECS as user root, perform the following operations:
+ To remotely log in to an ECS as user root, perform the following operations:
- Run the following command to change the disable_root value to 0 or false and the ssh_pwauth value to 1 or true in /etc/cloud/cloud.cfg:
sudo vi /etc/cloud/cloud.cfg
- Run the following command to set the user root password:
sudo passwd root
Logging In to a Linux ECS from a Local Windows Server
To log in to a Linux ECS from a local Windows server, perform the operations below.
The following operations use PuTTY as an example to log in to the ECS.
- Visit the following website and download PuTTY and PuTTYgen:
https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
- - Run PuTTY.
- Choose Session.
- Host Name (or IP address): Enter the EIP bound to the ECS.
- Port: Enter 22.
- Connection type: Click SSH.
- Saved Sessions: Enter the task name, which can be clicked for remote connection when you use PuTTY next time.Figure 1 Session+
- Run PuTTY.
- Choose Session.
- Host Name (or IP address): Enter the EIP bound to the ECS.
- Port: Enter 22.
- Connection type: Click SSH.
- Saved Sessions: Enter the task name, which can be clicked for remote connection when you use PuTTY next time.Figure 1 Session
- Choose Window. Then, select UTF-8 for Received data assumed to be in which character set: in Translation.
- Click Open.
If you log in to the ECS for the first time, PuTTY displays a security warning dialog box, asking you whether to accept the ECS security certificate. Click Yes to save the certificate to your local registry.
- After the SSH connection to the ECS is set up, enter the username and password as prompted to log in to the ECS.
How Quickly Can I Obtain an ECS?
diff --git a/docs/ecs/umn/en-us_topic_0018073215.html b/docs/ecs/umn/en-us_topic_0018073215.html index edf3fc8e..f8a14f4f 100644 --- a/docs/ecs/umn/en-us_topic_0018073215.html +++ b/docs/ecs/umn/en-us_topic_0018073215.html @@ -20,7 +20,7 @@Obtaining an ECS can take as little as a few minutes.
-The time it takes to obtain an ECS depends on ECS specifications, available resources (such as EVS disks and EIPs), and system load.
+The time it takes to obtain an ECS depends on ECS specifications, available resources (such as EVS disks and EIPs), and system load.
If it takes a long time to obtain your ECS, contact customer service.
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.
- Run the following command to change the disable_root value to 0 or false and the ssh_pwauth value to 1 or true in /etc/cloud/cloud.cfg:
- Accessing ECSs through APIs
D2
@@ -30,13 +30,13 @@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.
- Fuzzy search by private IP address
- In the Import Key Pair dialog box of the management console, click Select File and select the locally stored public key file (for example, the .txt file saved in 3 in Creating a Key Pair Using PuTTYgen).
- Selecting a file
diff --git a/docs/ecs/umn/en-us_topic_0018073216.html b/docs/ecs/umn/en-us_topic_0018073216.html index aa5e13c4..8d468c99 100644 --- a/docs/ecs/umn/en-us_topic_0018073216.html +++ b/docs/ecs/umn/en-us_topic_0018073216.html @@ -51,7 +51,7 @@- The system disk of an ECS is of VBD type. Therefore, the maximum number of SCSI disks is 59.
- For a D-series KVM ECS, its local disks use two SCSI controllers, indicating that 30 SCSI drive letters are used. Therefore, a maximum of 30 SCSI disks can be attached to such an ECS.
- The system disk of an ECS is of VBD type. The maximum number of SCSI disks is 59.
- For a D-series KVM ECS, its local disks use two SCSI controllers, indicating that 30 SCSI drive letters are used. A maximum of 30 SCSI disks can be attached to such an ECS.
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.
Do ECSs Support GUI?
Windows ECSs are managed through a GUI but Linux ECSs are managed through the CLI. You can configure a GUI if required.
-Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
+Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GiB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
diff --git a/docs/ecs/umn/en-us_topic_0021426802.html b/docs/ecs/umn/en-us_topic_0021426802.html index 9ea09164..c925e901 100644 --- a/docs/ecs/umn/en-us_topic_0021426802.html +++ b/docs/ecs/umn/en-us_topic_0021426802.html @@ -1,6 +1,6 @@ -diff --git a/docs/ecs/umn/en-us_topic_0018124785.html b/docs/ecs/umn/en-us_topic_0018124785.html index 48bef142..0f7a2950 100644 --- a/docs/ecs/umn/en-us_topic_0018124785.html +++ b/docs/ecs/umn/en-us_topic_0018124785.html @@ -8,7 +8,7 @@- Can an ECS Without an EIP Bound Access the Internet?
-
- Why Can't an EIP Be Pinged?
+- What Should I Do If an EIP Cannot Be Pinged?
- Why Can I Remotely Access an ECS But Cannot Ping It?
@@ -18,10 +18,6 @@
- Will NICs Added to an ECS Start Automatically?
-
- How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?
-
-- How Can I Manually Configure an IP Address for an InfiniBand NIC?
-- Why Is the NIC Not Working?
- How Can I Handle the Issue that a Windows 7 ECS Equipped with an Intel 82599 NIC Reports an Error in SR-IOV Scenarios?
diff --git a/docs/ecs/umn/en-us_topic_0018124786.html b/docs/ecs/umn/en-us_topic_0018124786.html index efc477d0..051b87c7 100644 --- a/docs/ecs/umn/en-us_topic_0018124786.html +++ b/docs/ecs/umn/en-us_topic_0018124786.html @@ -14,8 +14,6 @@- How Can I Enable Virtual Memory on a Windows ECS?
-
- Why Is the Memory of an ECS Obtained by Running the free Command Inconsistent with the Actual Memory?
-- 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?
diff --git a/docs/ecs/umn/en-us_topic_0018339851.html b/docs/ecs/umn/en-us_topic_0018339851.html index b41fe727..0ed6a65a 100644 --- a/docs/ecs/umn/en-us_topic_0018339851.html +++ b/docs/ecs/umn/en-us_topic_0018339851.html @@ -6,7 +6,7 @@Solution
Modify the remote desktop connection settings on the Windows ECS:
-- Log in to the ECS.
- Click Start in the lower left corner, right-click Computer, and choose Properties from the shortcut menu.
- In the navigation pane on the left, choose Remote settings.
- Click the Remote tab. In the Remote Desktop pane, select Allow connections from computers running any version of Remote Desktop (less secure).Figure 2 Remote settings+
- Log in to the ECS.
- Click Start in the lower left corner, right-click Computer, and choose Properties from the shortcut menu.
- In the left navigation pane, choose Remote settings.
- Click the Remote tab. In the Remote Desktop pane, select Allow connections from computers running any version of Remote Desktop (less secure).Figure 2 Remote settings
- Click OK.
Resetting the Password for Logging In to a Windows ECS
+Resetting the Password for Logging In to a Windows ECS
-Scenarios
You can reset your ECS password if:
- The password is forgotten.
- The password has expired.
The method described in this section can only be used to change the password of a local Windows account, but not the password of a domain account.
@@ -12,7 +12,7 @@Download the ntfs-3g and chntpw software packages of the version required by the temporary ECS OS.
Procedure
- Stop the original ECS and detach the system disk.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Stop the original Windows ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the Windows ECS. Otherwise, password reset may fail.
+-Procedure
- Stop the original ECS and detach the system disk.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Stop the original Windows ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the Windows ECS. Otherwise, password reset may fail.
- Locate the row containing the system disk to be detached and click Detach to detach the system disk from the ECS.
- Attach the system disk to the temporary ECS.
- On the page providing details about the temporary ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the system disk detached in step 1.e and attach it to the temporary ECS.
- Remotely log in to the temporary ECS.
- Run the following command to view the directory of the system disk detached from the original Windows ECS now attached to the temporary ECS:
fdisk -l
@@ -46,23 +46,17 @@ Write hive files? (y/n) [n] : y - Stop the temporary ECS, detach the system disk, and attach the system disk to the original Windows ECS.
- Stop the temporary ECS, switch to the page providing details about the ECS, and click the Disks tab.
- Click Detach to detach the data disk temporarily attached in step 2.b.
- On the page providing details about the original Windows ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the data disk detached in step 4.b and device name /dev/sda.
- Start the original Windows ECS and set a new login password.
- Click Start to start the original Windows ECS. After the status becomes Running, click Remote Login in the Operation column.
- Click Start. Enter CMD in the search box and press Enter.
- Run the following command to change the password (the new password must meet the requirements described in Table 1):
net user Administrator New password
-Table 1 Password complexity requirements Parameter
+
diff --git a/docs/ecs/umn/en-us_topic_0021427650.html b/docs/ecs/umn/en-us_topic_0021427650.html index 5887ab51..2c81b259 100644 --- a/docs/ecs/umn/en-us_topic_0021427650.html +++ b/docs/ecs/umn/en-us_topic_0021427650.html @@ -9,7 +9,7 @@Table 1 Password complexity requirements Parameter
Requirement
-Example Value
+Requirement
Password
+Password
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Cannot contain the username or the username spelled backwards.
- Cannot contain more than two consecutive characters in the same sequence as they appear in the username. (This requirement applies only to Windows ECSs.)
- Cannot start with a slash (/) for Windows ECSs.
YNbUwp!dUc9MClnv
-NOTE:-The example password is generated randomly. Do not use it.
-
Procedure
- Download the script for resetting the password and upload the script to the temporary ECS.
Contact customer service to obtain the password reset script. Use a connection tool, such as WinSCP, to upload the obtained changepasswd.sh script to the temporary ECS.
To download WinSCP, log in at https://winscp.net/.
- - Stop the original Linux ECS, detach the system disk from it, and attach the system disk to the temporary ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Stop the original ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the original ECS. Otherwise, password reset may fail.
+- Stop the original Linux ECS, detach the system disk from it, and attach the system disk to the temporary ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Stop the original ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the original ECS. Otherwise, password reset may fail.
- Locate the row containing the system disk to be detached and click Detach to detach the system disk from the ECS.
- Attach the system disk to the temporary ECS.
- On the page providing details about the temporary ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the system disk detached in step 2.e and attach it to the temporary ECS.
Modify the following settings:
- Change PasswordAuthentication no to PasswordAuthentication yes.
Alternatively, uncomment PasswordAuthentication yes.
- Change PermitRootLogin no to PermitRootLogin yes.
Alternatively, uncomment PermitRootLogin yes.
- - Change the value of AllowUsers to root.
Search for AllowUsers in the file. If AllowUsers is missing, add it at the end of the file.
+ - Change the value of AllowUsers to root.
Search for AllowUsers in the file. If AllowUsers is missing, add AllowUsers root at the end of the file.
- Stop the temporary ECS, detach the system disk, attach the system disk to the original Linux ECS, and restart the original Linux ECS.
- Stop the temporary ECS, switch to the page providing details about the ECS, and click the Disks tab.
- Click Detach to detach the data disk attached in step 2.
- On the page providing details about the original Linux ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the data disk detached in 6.b.
- Restart the original Linux ECS.
diff --git a/docs/ecs/umn/en-us_topic_0024911405.html b/docs/ecs/umn/en-us_topic_0024911405.html index 6c89615e..424b0c51 100644 --- a/docs/ecs/umn/en-us_topic_0024911405.html +++ b/docs/ecs/umn/en-us_topic_0024911405.html @@ -1,7 +1,7 @@Reinstalling the OS
-Scenarios
If the OS of an ECS fails to start or requires optimization, reinstall the OS.
+Scenarios
If the OS of an ECS fails to start or requires optimization, reinstall the OS.
Notes
- After the OS is reinstalled, the IP and MAC addresses of the ECS remain unchanged.
- Reinstalling the OS clears the data in all partitions of the EVS system disk, including the system partition. Therefore, back up data before reinstalling the OS.
- Reinstalling the OS does not affect data disks.
- Do not perform any operations on the ECS immediately after its OS is reinstalled. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- After the OS is reinstalled, the password for logging in to the ECS will be reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Remotely Logging In to a Linux ECS (Using an SSH Key Pair).
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
- You can choose to encrypt the system disk of an ECS during OS reinstallation.
-Prerequisites
- The target ECS is stopped.
- The target ECS has a system disk attached.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
Only stopped ECSs support OS reinstallation. If the ECS is not stopped, stop it before proceeding with reinstallation.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
Only stopped ECSs support OS reinstallation. If the ECS is not stopped, stop it before proceeding with reinstallation.
- (Optional) Select the Encrypted option to encrypt the system disk during OS reinstallation.
To enable encryption, click Create Xrole to assign KMS access permissions to EVS. If you have rights granting permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights to assign the KMS access permissions. For details, see Can All Users Use the Encryption Feature?
Encryption parameters are as follows:
-- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: EVSAccessKMS: specifies that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- (Optional) Select a License Type (Use license from the system or Bring your own license (BYOL)) if the reinstalled OS running on your ECS is billed. For more details, see License Types.
The following OSs are billed:
- SUSE Linux Enterprise Server
- Oracle Enterprise Linux
- Red Hat Enterprise Linux
- Select the login mode.
If the target ECS uses key pair authentication, you can replace the original key pair.
Figure 1 Reinstall OS-
- Click OK.
- On the ECS OS Reinstallation page, confirm the settings, and click Submit.After the request is submitted, the status Reinstalling is displayed. When this status disappears, the reinstallation is complete. -
A temporary ECS is created during the reinstallation process. After reinstallation, this ECS will be automatically deleted. Do not perform any operation on the temporary ECS during the reinstallation process.
+- Click OK.
- On the ECS OS Reinstallation page, confirm the settings, and click Submit.
diff --git a/docs/ecs/umn/en-us_topic_0027157850.html b/docs/ecs/umn/en-us_topic_0027157850.html index 24318fed..85e83445 100644 --- a/docs/ecs/umn/en-us_topic_0027157850.html +++ b/docs/ecs/umn/en-us_topic_0027157850.html @@ -8,7 +8,7 @@After the request is submitted, the status Reinstalling is displayed. When this status disappears, the reinstallation is complete. A temporary ECS is created during the reinstallation process. After reinstallation, this ECS will be automatically deleted. Do not perform any operation on the temporary ECS during the reinstallation process.
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.
diff --git a/docs/ecs/umn/en-us_topic_0027371530.html b/docs/ecs/umn/en-us_topic_0027371530.html index 907bfca8..9a8d00ed 100644 --- a/docs/ecs/umn/en-us_topic_0027371530.html +++ b/docs/ecs/umn/en-us_topic_0027371530.html @@ -11,7 +11,7 @@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.
- On the Network Interfaces tab, click
. Then, disable Source/Destination Check.Figure 1 Disabling 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.
- On the Network Interfaces tab, click . Then, disable Source/Destination Check.Figure 1 Disabling source/destination check
By default, the source/destination check function is enabled. When this function is enabled, the system checks whether source IP addresses contained in the packets sent by ECSs are correct. If the IP addresses are incorrect, the system does not allow the ECSs to send the packets. This mechanism prevents packet spoofing, thereby improving system security. However, this mechanism prevents the packet sender from receiving returned packets. Therefore, disable the source/destination check.
- Log in to the proxy ECS.
For more details, see Login Overview.
- Run the following command to check whether the proxy ECS can access the Internet:
ping www.google.com
@@ -40,7 +40,7 @@ - Run the following command to check whether SNAT has been configured:
SNAT has been configured if information similar to Figure 2 is displayed.
- - Add a route.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Network, click Virtual Private Cloud.
- Choose Route Tables in the left navigation pane. In the route table list, click a target route table. On the displayed page, click Add Route.
- Set route information on the displayed page.
- Destination: indicates the destination network segment. The default value is 0.0.0.0/0.
- Next Hop: indicates the private IP address of the proxy ECS.
You can obtain the private IP address of the ECS on the Elastic Cloud Server page.
+ - Add a route.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Network, click Virtual Private Cloud.
- Choose Route Tables in the left navigation pane. In the route table list, click a target route table. On the displayed page, click Add Route.
- Set route information on the displayed page.
- Destination: indicates the destination network segment. The default value is 0.0.0.0/0.
- Next Hop: indicates the private IP address of the proxy ECS.
You can obtain the private IP address of the ECS on the Elastic Cloud Server page.
- To delete the added iptables rules, run the following command:
iptables -t nat -D POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
@@ -51,7 +51,7 @@
- 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 18f0b85b..43926afc 100644 --- a/docs/ecs/umn/en-us_topic_0027371531.html +++ b/docs/ecs/umn/en-us_topic_0027371531.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 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 hour, last 3 hours, last 12 hours, last 1 day, or last 7 days.
+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 hour, last 3 hours, last 12 hours, last 1 day, or last 7 days.
This section describes how to set ECS alarm rules, including alarm rule names, monitoring objects, monitoring metrics, alarm thresholds, monitoring intervals, and notifications.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Management & Deployment, choose Cloud Eye.
- In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the Alarm Rules page, click Create Alarm Rule to create an alarm rule, or modify an existing alarm rule.
The following uses modifying an existing alarm rule as an example.
-- Click the target alarm rule.
- Click Modify in the upper right corner of the page.
- In the Modify Alarm Rule dialog box shown in Figure 1, set the parameters as prompted.
+
- Click the target alarm rule.
- Click Modify in the upper right corner of the page.
- In the Modify Alarm Rule dialog box shown in Figure 1, set the parameters as prompted.
- Click Modify.
After an alarm rule is modified, the system automatically notifies you of an alarm when the alarm complying with the alarm rule is generated.
For more information about ECS alarm rules, see Cloud Eye User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0030013188.html b/docs/ecs/umn/en-us_topic_0030013188.html index 2699f845..d219d712 100644 --- a/docs/ecs/umn/en-us_topic_0030013188.html +++ b/docs/ecs/umn/en-us_topic_0030013188.html @@ -3,7 +3,7 @@Can an ECS Without an EIP Bound Access the Internet?
Yes.
- Method 1: Configure a SNAT server.
You can configure the SNAT server so that the ECS without an EIP bound can access the Internet.
-For details, see "Configuring an SNAT Server" in Virtual Private Cloud User Guide.
+For details, see "Configuring an SNAT Server" in Virtual Private Cloud User Guide.
- Method 2: Create a NAT gateway.
If a large number of concurrent connections are required, it is a good practice to use the NAT Gateway service provided by the cloud platform.
The NAT Gateway service offers the NAT function for ECSs in a VPC, allowing these ECSs to access the Internet using an EIP. For more information about NAT Gateway, see NAT Gateway User Guide.
- Stop the original Linux ECS, detach the system disk from it, and attach the system disk to the temporary ECS.
Public image
+Public
A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users. Public images are very stable and their OS and any included software have been officially authorized for use. If a public image does not contain the environments or software you need, you can use a public image to create an ECS and then deploy the required environments or software on it.
Private image
+Private
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 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.
- 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 that has the same disk capacity.
Shared image
+Shared
A shared image is a private image another user has shared with you.
-For more information about shared images, see "Sharing Images" in Image Management Service User Guide.
+For more information about shared images, see "Sharing Images" in Image Management Service User Guide.
What Is Elastic Volume Service?
Elastic Volume Service (EVS) offers scalable block storage for ECSs. With high reliability, high performance, and rich specifications, EVS disks can be used for distributed file systems, development and test environments, data warehouses, and high-performance computing (HPC) scenarios to meet diverse service requirements.
Disk Types
EVS disk types differ in performance. Choose a disk type based on your requirements.
-For more information about EVS disk specifications and performance, see Elastic Volume Service User Guide.
+For more information about EVS disk specifications and performance, see Elastic Volume Service User Guide.
Device Types
EVS disks have two device types, Virtual Block Device (VBD) and Small Computer System Interface (SCSI).- VBD
When you create an EVS disk on the management console, Device Type of the EVS disk is VBD by default. VBD EVS disks support only simple SCSI read/write commands.
- SCSI
You can create EVS disks whose Device Type is SCSI on the management console. These EVS disks support transparent SCSI command transmission, allowing ECS OS to directly access underlying storage media. SCSI EVS disks support both basic and advanced SCSI commands.
diff --git a/docs/ecs/umn/en-us_topic_0030828257.html b/docs/ecs/umn/en-us_topic_0030828257.html index 06d4a482..16da6d33 100644 --- a/docs/ecs/umn/en-us_topic_0030828257.html +++ b/docs/ecs/umn/en-us_topic_0030828257.html @@ -7,7 +7,7 @@-Subnet
A subnet is a range of IP addresses in your VPC and provides IP address management and DNS resolution functions for ECSs in it. The IP addresses of all ECSs in a subnet belong to the subnet.
By default, ECSs in all subnets of the same VPC can communicate with each other, while ECSs in different VPCs cannot.
Security Group
A security group is a collection of access control rules for ECSs that have the same security protection requirements and that are mutually trusted. By adding an ECS to a security group, you apply all the rules defined for this security group to this ECS.
+Security Group
A security group is a collection of access control rules for ECSs that have the same security protection requirements and that are mutually trusted. By adding an ECS to a security group, you apply all the rules defined for this security group to this ECS.
Your account automatically comes with a default security group. The default security group allows all outbound data, denies all inbound data, and allows all data between ECSs in the group. Your ECSs in the security group can communicate with each other without the need to add rules.
Figure 1 Default security group@@ -51,7 +51,7 @@
EIP
The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways, or load balancers.
+diff --git a/docs/ecs/umn/en-us_topic_0030831623.html b/docs/ecs/umn/en-us_topic_0030831623.html index 989ed64a..61a8efb8 100644 --- a/docs/ecs/umn/en-us_topic_0030831623.html +++ b/docs/ecs/umn/en-us_topic_0030831623.html @@ -2,44 +2,44 @@EIP
The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways or load balancers.
Each EIP can be used by only one cloud resource at a time.
Figure 2 Accessing the Internet using an EIP
Scenarios and Disk Partitions
If you have added a data disk during ECS creation, you must initialize the data disk after logging in to the ECS.
-Scenarios
After a disk is attached to a server, you need to log in to the server to initialize the disk, that is, format the disk. You must initialize a disk before accessing it.- System disk
A system disk does not require manual initialization because it is automatically created and initialized upon server creation. The default partition style is master boot record (MBR).
- - Data disk
- If a data disk is created along with a server, it will be automatically attached to the server.
- If a data disk is created separately, you need to manually attach it to a server.
In both cases, you must initialize the data disk before using it. Choose an appropriate partition style based on your service plan.
+Scenarios
After a disk is attached to a server, you need to log in to the server to initialize the disk, that is, format the disk. You must initialize a disk before accessing it.- System disk
A system disk does not require manual initialization because it is automatically created and initialized upon server creation. The default partition style is master boot record (MBR).
+ - Data disk
- If a data disk is created along with a server, it will be automatically attached to the server.
- If a data disk is created separately, you need to manually attach it to a server.
In both cases, you must initialize the data disk before using it. Choose an appropriate partition style based on your service plan.
Partitioning Operation Guide
Table 1 lists the common disk partition styles. In Linux, different disk partition styles require different partitioning tools.
-Table 1 Disk partition styles Disk Partition Style
+Table 1 Disk partition styles Disk Partition Style
Maximum Disk Capacity Supported
+Maximum Disk Capacity Supported
Maximum Number of Partitions Supported
+Maximum Number of Partitions Supported
Linux Partitioning Tool
+Linux Partitioning Tool
Master Boot Record (MBR)
+Master Boot Record (MBR)
2 TiB
+2 TiB
- 4 primary partitions
- 3 primary partitions and 1 extended partition
With MBR, you can create several primary partitions and one extended partition. The extended partition must be divided into logical partitions before use. For example, if 6 partitions need to be created, you can create them in the following two ways:- 3 primary partitions and 1 extended partition, with the extended partition divided into 3 logical partitions
- 1 primary partition and 1 extended partition, with the extended partition divided into 5 logical partitions
- 4 primary partitions
- 3 primary partitions and 1 extended partition
With MBR, you can create several primary partitions and one extended partition. The extended partition must be divided into logical partitions before use. For example, if 6 partitions need to be created, you can create them in the following two ways:- 3 primary partitions and 1 extended partition, with the extended partition divided into 3 logical partitions
- 1 primary partition and 1 extended partition, with the extended partition divided into 5 logical partitions
- fdisk
- parted
- fdisk
- parted
GUID Partition Table (GPT)
+GUID Partition Table (GPT)
18 EiB
-1 EiB = 1048576 TiB
+18 EiB
+1 EiB = 1048576 TiB
Unlimited
-Disk partitions created using GPT are not categorized.
+Unlimited
+Disk partitions created using GPT are not categorized.
parted
+parted
- 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.
- - Configure required parameters.
You can click + to add more inbound rules.
-Figure 1 Add Inbound Rule+
- Configure required parameters.
You can click + to add more inbound rules.
+Figure 1 Add Inbound Rule-
Table 1 Inbound rule parameter description Parameter
+-Table 1 Inbound rule parameter description Parameter
Description
+Description
Example Value
+Example Value
Protocol & Port
+Protocol
The network protocol used to match traffic in a security group rule.
-Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.
+The network protocol used to match traffic in a security group rule.
+Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.
TCP
+TCP
Port: The port or port range over which traffic can reach your ECS. The value can be from 1 to 65535.
+Port
22, or 22-30
+The port or port range over which traffic can reach your ECS. The value can be from 1 to 65535.
+22, or 22-30
Type
+Type
Source IP address version. You can select:- IPv4
- IPv6
- IPv4
- IPv6
IPv4
+IPv4
Source
+Source
Source of the security group rule. The value can be an IP address, a security group, or an IP address group to allow access from IP addresses or instances in the security group. For example:- IP address:
- Single IP address: 192.168.10.10/32
- All IP addresses: 0.0.0.0/0
- IP address range: 192.168.1.0/24
- Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
- IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
- IP address:
- Single IP address: 192.168.10.10/32
- All IP addresses: 0.0.0.0/0
- IP address range: 192.168.1.0/24
- Security group: The source is from another security group. You can select a security group in the same region from the drop-down list. If there is instance A in security group A and instance B in security group B, and the inbound rule of security group A allows traffic from security group B, traffic is allowed from instance B to instance A.
If the source is a security group, this rule will apply to all instances associated with the selected security group.
+If the source is a security group, this rule will apply to all instances associated with the selected security group.
0.0.0.0/0
+0.0.0.0/0
Description
+Description
Supplementary information about the security group rule. This parameter is optional.
-The security group rule description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
+Supplementary information about the security group rule. This parameter is optional.
+The security group rule description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
N/A
+N/A
- Configure required parameters.
You can click + to add more outbound rules.
-Figure 2 Add Outbound Rule+
- Configure required parameters.
You can click + to add more outbound rules.
+Figure 2 Add Outbound Rule-
Table 2 Outbound rule parameter description Parameter
+Table 2 Outbound rule parameter description Parameter
Description
+Description
Example Value
+Example Value
Protocol & Port
- +Protocol
The network protocol used to match traffic in a security group rule.
-Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.
+The network protocol used to match traffic in a security group rule.
+Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.
TCP
+TCP
Port: The port or port range over which traffic can leave your ECS. The value can be from 1 to 65535.
+Port
22, or 22-30
+The port or port range over which traffic can leave your ECS. The value can be from 1 to 65535.
+22, or 22-30
Type
+Type
Source IP address version. You can select:- IPv4
- IPv6
- IPv4
- IPv6
IPv4
+IPv4
Destination
+Destination
Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example:
-- IP address:
- Single IP address: 192.168.10.10/32
- All IP addresses: 0.0.0.0/0
- IP address range: 192.168.1.0/24
- Security group: The destination is from another security group. You can select a security group in the same region under the current account from the drop-down list. For example, instance A is in security group A and instance B is in security group B. If security group A has an outbound rule with Action set to Allow and Destination set to security group B, access from instance A is allowed to instance B.
- IP address group: A collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group.
+- IP address:
- Single IP address: 192.168.10.10/32
- All IP addresses: 0.0.0.0/0
- IP address range: 192.168.1.0/24
- Security group: The source is from another security group. You can select a security group in the same region from the drop-down list. If there is instance A in security group A and instance B in security group B, and the inbound rule of security group A allows traffic from security group B, traffic is allowed from instance B to instance A.
0.0.0.0/0
+0.0.0.0/0
Description
+Description
Supplementary information about the security group rule. This parameter is optional.
-The security group rule description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
+Supplementary information about the security group rule. This parameter is optional.
+The security group rule description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
N/A
+N/A
-Namespace
SYS.ECS
Basic ECS Metrics
Basic ECS metrics vary depending on ECS OSs and types. For details, seeTable 1. √ indicates that the metric is supported, and x indicates that the metric is not supported.
+Basic ECS Metrics
Basic ECS metrics vary depending on ECS OSs and types. For details, see Table 1.
@@ -304,8 +304,8 @@ To monitor the memory usage and disk usage, you need to install the Agent on your ECS.- For details about how to install the Agent on a Windows ECS, see Installing and Configuring the Agent on a Windows Server.
- For details about how to install the Agent on a Linux ECS, see Installing the Agent on a Linux Server.
InfiniBand NIC status
Status of an InfiniBand NIC on an H2 ECS
-The system periodically checks the status and returns check results using value 0 or 1.
-- 0: The system is running properly. That is, the InfiniBand NIC is functional.
- 1: The system is not running properly. That is, the InfiniBand NIC malfunctions. When the physical NIC corresponding to a virtual NIC becomes faulty, for example, the network cable is not securely connected to the NIC, the switch or adapter is incompatible with the InfiniBand NIC, or the NIC is disabled, the returned value is 1.
The system periodically checks the status and returns check results using value 0 or 1.
+- 0: The system is running properly. That is, the InfiniBand NIC is functional.
- 1: The system is not running properly. That is, the InfiniBand NIC malfunctions. When the physical NIC corresponding to a virtual NIC becomes faulty, for example, the network cable is not securely connected to the NIC, the switch or adapter is incompatible with the InfiniBand NIC, or the NIC is disabled, the returned value is 1.
NOTE:Only Mellanox EDR 100 GB single-port InfiniBand NICs are supported.
- Why Does the System Display Error Code 0x1104 When I Log In to a Windows ECS?
-
- Why Does the System Display Error Code 122.112.. When I Log In to a Windows ECS?
+- Why Does the System Display Error Code 122.112... When I Log In to a Windows ECS?
- Why Does the System Display Invalid Certificate or Associated Chain When I Log In to a Windows ECS from a Mac?
diff --git a/docs/ecs/umn/en-us_topic_0031107266.html b/docs/ecs/umn/en-us_topic_0031107266.html index f6c60ceb..b14c0669 100644 --- a/docs/ecs/umn/en-us_topic_0031107266.html +++ b/docs/ecs/umn/en-us_topic_0031107266.html @@ -1,10 +1,10 @@
Obtaining the Password for Logging In to a Windows ECS
-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.
+-Scenarios
Password authentication is required to log in to a Windows ECS. You must use the key file used when you created the ECS to obtain the administrator password generated during ECS creation. The administrator user is Administrator or the user configured using Cloudbase-Init. This password is randomly generated, offering high security.
You can obtain the initial password for logging in to a Windows ECS through the management console or APIs. For details, see this section.
Obtaining the Password Through the Management Console
- Obtain the private key file (.pem file) used when you created the ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Get Password.Figure 1 Get Password+
diff --git a/docs/ecs/umn/en-us_topic_0031107267.html b/docs/ecs/umn/en-us_topic_0031107267.html index 37b73f8f..baac2342 100644 --- a/docs/ecs/umn/en-us_topic_0031107267.html +++ b/docs/ecs/umn/en-us_topic_0031107267.html @@ -4,7 +4,7 @@Obtaining the Password Through the Management Console
- Obtain the private key file (.pem file) used when you created the ECS.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Get Password.Figure 1 Get Password
- Use either of the following methods to obtain the password through the key file:
- Click Select File and upload the key file from a local directory.
- Copy the key file content to the text field.
- Click Get Password to obtain a random password.
-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.
+diff --git a/docs/ecs/umn/en-us_topic_0031523135.html b/docs/ecs/umn/en-us_topic_0031523135.html index 74109846..deee01fd 100644 --- a/docs/ecs/umn/en-us_topic_0031523135.html +++ b/docs/ecs/umn/en-us_topic_0031523135.html @@ -5,9 +5,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.
- 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.
Figure 1 Delete Password
- Click OK to delete the password.
If the OS running on an ECS cannot meet service requirements, change the ECS OS.
The cloud platform 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 OS change takes about 10 to 20 minutes During this process, the ECS status is Changing OS.
- Do not perform any operations on the ECS before the system injects the password or key pair. Otherwise, the login will fail.
- The ECS for which you want to change the OS must be in any of the following states: Stopped, Reinstallation failed, or Failed to change the OS.
- The target ECS must have a system disk attached.
- The EVS disk quota must be greater than 0.
- The system disk type cannot be changed.
- The system disk can be encrypted.
- For details about the change between different OSs, see Notes on Change Between Windows and Linux.
- If an ECS OS is to be changed using a full-ECS image, the ECS system disk can be encrypted.
-Constraints
- The OS change takes about 10 to 20 minutes During this process, the ECS status is Changing OS.
- Do not perform any operations on the ECS before the system injects the password or key. Otherwise, the login will fail.
- The ECS for which you want to change the OS must be in any of the following states: Stopped, Reinstallation failed, or Failed to change the OS.
- The target ECS must have a system disk attached.
- The EVS disk quota must be greater than 0.
- The system disk type cannot be changed.
- The system disk can be encrypted.
- For details about the change between different OSs, see Notes on Change Between Windows and Linux.
- If an ECS OS is to be changed using a full-ECS image, the ECS system disk can be encrypted.
Notes
- After the OS is changed, the original OS is not retained, and the original system disk is deleted, including the data in all partitions of the system disk.
- Back up data before changing the OS.
- Changing the OS does not affect data in data disks.
- After the OS is changed, your service running environment must be deployed in the new OS again.
- After the OS is changed, the ECS will be automatically started.
- After the OS is changed, the system disk type of the ECS cannot be changed.
- After the OS is changed, the IP and MAC addresses of the ECS remain unchanged.
- After the OS is changed, customized configurations, such as DNS and hostname of the original OS will be reset and require reconfiguration.
- It takes about 10 to 20 minutes to change the OS. During this process, the ECS is in Changing OS state.
- Do not perform any operations on the ECS immediately after its OS is changed. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- After the OS is changed, the password for logging in to the ECS is reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Remotely Logging In to a Linux ECS (Using an SSH Key Pair).
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
@@ -18,19 +18,19 @@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.
- After the OS is changed, the password for logging in to the ECS is reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Remotely Logging In to a Linux ECS (Using an SSH Key Pair).
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
- The system disk capacity of an ECS with OS changed may change because the system disk capacity specified by the image of the changed OS may be changed.
- You can choose to encrypt the system disk of an ECS during OS change.
-Prerequisites
- The data is backed up.
- If you want to change the login authentication mode from password to key pair during the OS change, create a key file in advance.
For details, see (Recommended) Creating a Key Pair on the Management Console.
- - If you plan to use a private image to change the OS, ensure that a private image is available. For details about how to create a private image, see Image Management Service User Guide.
- If the image of a specified ECS is required, make sure that a private image has been created using this ECS.
- If a local image file is required, make sure that the image file has been imported to the cloud platform and registered as a private image.
- If a private image from another region is required, make sure that the image has been copied.
- If a private image from another user account is required, make sure that the image has been shared with you.
- If you plan to use a private image to change the OS, ensure that a private image is available. For details about how to create a private image, see Image Management Service User Guide.
- If the image of a specified ECS is required, make sure that a private image has been created using this ECS.
- If a local image file is required, make sure that the image file has been imported to the cloud platform and registered as a private image.
- If a private image from another region is required, make sure that the image has been copied.
- If a private image from another user account is required, make sure that the image has been shared with you.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Change OS in the Operation column.
Only stopped ECSs support OS change. If the ECS is not stopped, stop it before proceeding with changing.
+-Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Change OS in the Operation column.
Only stopped ECSs support OS change. If the ECS is not stopped, stop it before proceeding with changing.
- Select the target image.
For more details, see Creating an ECS.
Figure 1 OS Change
- (Optional) Select the Encryption option to encrypt the system disk during OS change.
To enable encryption, click Create Xrole to assign KMS access permissions to EVS. If you have rights granting permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights to assign the KMS access permissions. For details, see Can All Users Use the Encryption Feature?
Encryption parameters are as follows:
-- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: EVSAccessKMS: specifies that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- (Optional) Select a License Type (Use license from the system or Bring your own license (BYOL)) if the changed OS running on your ECS is billed. For more details, see License Types.The following OSs are billed:
- SUSE Linux Enterprise Server
- Oracle Enterprise Linux
- Red Hat Enterprise Linux
- Configure the login mode.
If the target ECS uses key pair authentication, you can replace the original key pair.
- - Click OK.
- On the Change ECS OS page, confirm the specifications, and click Submit.
After the application is submitted, the status Changing OS is displayed. When this status disappears, the OS change is complete.
+ - Click OK.
- On the Change ECS OS page, confirm the specifications, and click Submit.
After the application is submitted, the status Changing OS is displayed. When this status disappears, the OS change is complete.
A temporary ECS is created during the OS change process. After the process is complete, this ECS will be automatically deleted.
Figure 1 User data injection
- The created ECS automatically runs Cloud-Init/Cloudbase-Init and reads the user data script upon startup.
User Data Scripts of Linux ECSs
Customized user data scripts of Linux ECSs are based on the open-source Cloud-Init architecture. This architecture uses ECS metadata as the data source for automatically configuring the ECSs. The customized script types are compatible with open-source Cloud-Init. For details about Cloud-Init, see http://cloudinit.readthedocs.io/en/latest/topics/format.html.
+User Data Scripts of Linux ECSs
Customized user data scripts of Linux ECSs are based on the open-source Cloud-Init architecture. This architecture uses ECS metadata as the data source for automatically configuring the ECSs. The customized script types are compatible with open-source Cloud-Init. For details about Cloud-Init, see http://cloudinit.readthedocs.io/en/latest/topics/format.html.
- Script execution time: A customized user data script is executed after the status of the target ECS changes to Running and before /etc/init is executed.
By default, the scripts are executed as user root.
After the ECS is created, start it and run the cat [file] command to check the script execution result.
[root@XXXXXXXX ~]# cat /root/output.txt Hello, the time is now Mon, 16 Jul 2016 16:03:18+0800
-Example 2: Inject a Cloud-Config data script.
+Example 2: Inject a Cloud-Config data script.
When creating an ECS, set User Data to As text and enter the customized user data script.
#cloud-config bootcmd: @@ -143,23 +143,17 @@ write_files: -
Table 3 Password complexity requirements Parameter
+-
@@ -183,23 +177,17 @@ echo 'root:$6$V6azyeLwcD3CHlpY$BN3VVq18fmCkj66B4zdHLWevqcxlig' | chpasswd -e;Table 3 Password complexity requirements Parameter
Requirement
-Example Value
+Requirement
Password
+Password
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Cannot contain the username or the username spelled backwards.
- Cannot contain more than two consecutive characters in the same sequence as they appear in the username. (This requirement applies only to Windows ECSs.)
- Cannot start with a slash (/) for Windows ECSs.
YNbUwp!dUc9MClnv
-NOTE:-The example password is generated randomly. Do not use it.
-
The new password must meet the password complexity requirements listed in Table 4.
Table 4 Password complexity requirements Parameter
+
diff --git a/docs/ecs/umn/en-us_topic_0032398121.html b/docs/ecs/umn/en-us_topic_0032398121.html index fc74cfc9..da5e9b9f 100644 --- a/docs/ecs/umn/en-us_topic_0032398121.html +++ b/docs/ecs/umn/en-us_topic_0032398121.html @@ -26,7 +26,7 @@Table 4 Password complexity requirements Parameter
Requirement
-Example Value
+Requirement
Password
+Password
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Cannot contain the username or the username spelled backwards.
- Cannot contain more than two consecutive characters in the same sequence as they appear in the username. (This requirement applies only to Windows ECSs.)
- Cannot start with a slash (/) for Windows ECSs.
YNbUwp!dUc9MClnv
-NOTE:-The example password is generated randomly. Do not use it.
-
Ecs.0001
The maximum number of ECSs or EVS disks has been reached. Contact the customer service and request an ECS quota increase.
+The maximum number of ECSs or EVS disks has been reached. Contact customer service and request an ECS quota increase.
Contact customer service and request an ECS quota increase.
NOTE:Before requesting for increasing your ECS quota, consider the number of to-be-added ECSs, vCPUs, and memory capacity required.
@@ -70,7 +70,7 @@Ecs.0013
Contact customer service and request an EIP quota increase.
+Contact customer service and request an EIP quota increase.
Contact customer service and request an EIP quota increase.
diff --git a/docs/ecs/umn/en-us_topic_0032980085.html b/docs/ecs/umn/en-us_topic_0032980085.html index 5b0bf595..047510cd 100644 --- a/docs/ecs/umn/en-us_topic_0032980085.html +++ b/docs/ecs/umn/en-us_topic_0032980085.html @@ -9,19 +9,19 @@-Parent topic: ECS Management+Parent topic: Usage Errors- Removing an ECS from an ECS Group
- Deleting an ECS Group
Creating an ECS Group
Create an ECS group and associate the same policy to all group members. ECS groups are independent from each other.
-- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- On the ECS Group page, click Create ECS Group.
- Enter the name of an ECS group.
- Select a policy for the ECS group.
- Click OK.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- On the ECS Group page, click Create ECS Group.
- Enter the name of an ECS group.
- Select a policy for the ECS group.
- Click OK.
Adding an ECS to an ECS Group
To improve service reliability, you can add ECSs to an ECS group so that these ECSs in this group can run on different hosts.
- - After an ECS is added to an ECS group, the system reallocates a host to run this ECS to ensure that ECSs in this group are running on different hosts. When the ECS is being restarted, the startup may fail due to insufficient resources. In such a case, remove the ECS from the ECS group and try to restart the ECS again.
- ECSs that have local disks attached can be added to an ECS group only during the creation process. Once created, they can no longer be added to any ECS groups.
- ECSs that have local disks, GPU cards, or FPGA cards attached can be added to an ECS group only during the creation process. Once created, they can no longer be added to any ECS groups.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the row that contains the target ECS group and click Add ECS in the Operation column.
- On the Add ECS page, select an ECS to be added.
- Click OK. The ECS is added to the ECS group.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the row that contains the target ECS group and click Add ECS in the Operation column.
- On the Add ECS page, select an ECS to be added.
- Click OK. The ECS is added to the ECS group.
Removing an ECS from an ECS Group
After an ECS is removed from an ECS group, the ECS does not comply with the anti-affinity policy anymore.
-- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Expand the ECS group information and view the ECSs in the ECS group.
- Locate the ECS to be removed and click Remove in the Operation column.
- In the displayed dialog box, click Yes.
The ECS is removed from the ECS group.
+- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Expand the ECS group information and view the ECSs in the ECS group.
- Locate the ECS to be removed and click Remove in the Operation column.
- In the displayed dialog box, click Yes.
The ECS is removed from the ECS group.
Deleting an ECS Group
After an ECS group is deleted, the policy does not apply to the ECSs in the ECS group anymore.
-- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the ECS group to be deleted and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the ECS group to be deleted and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
diff --git a/docs/ecs/umn/en-us_topic_0035470096.html b/docs/ecs/umn/en-us_topic_0035470096.html index e26a8b6c..e92890dd 100644 --- a/docs/ecs/umn/en-us_topic_0035470096.html +++ b/docs/ecs/umn/en-us_topic_0035470096.html @@ -6,20 +6,21 @@ECS Flavor Naming Rules
ECS flavors are named in the "AB.C.D" format.
Example: s2.medium.4
The format is defined as follows:
-- A specifies the ECS type. For example, s indicates a general-purpose ECS, c a general computing-plus ECS, and m a memory-optimized ECS.
- B specifies the type ID. For example, 3 in s3 indicates the third-generation general-purpose ECS.
- C specifies the flavor size, such as medium, large, xlarge, 2xlarge, 4xlarge, or 8xlarge.
- D specifies the ratio of memory to vCPUs expressed in a digit. For example, value 4 indicates that the ratio of memory to vCPUs is 4.
- A specifies the ECS type. For example, s indicates a general-purpose ECS, c a general computing-plus ECS, and m a memory-optimized ECS.
- B specifies the type ID. For example, 3 in s3 indicates the third-generation general-purpose ECS.
- C specifies the flavor size, such as medium, large, xlarge, 2xlarge, 4xlarge, or 8xlarge.
- D specifies the ratio of memory to vCPUs expressed in a digit. For example, value 4 indicates that the ratio of memory to vCPUs is 4.
-How Do I Know My ECS Flavor?
When creating an ECS, you can view the flavors in the flavor list.
Figure 1 ECS flavors
vCPU
The processor uses the hyper-threading technology. The CPU exposes two execution contexts per physical core. This means that one physical core now works like two "logical cores" that can handle different software threads.
-For example, a 10-core physical CPU contains 20 vCPUs (threads).
+vCPU
ECS supports hyper-threading, which enables two threads to run concurrently on a single CPU core. Each thread is represented as a virtual CPU (vCPU) and a CPU core contains two vCPUs (logical cores).
+Hyper-threading is enabled for most ECS flavors by default. If hyper-threading is disabled during the ECS creation or flavor change, the number of vCPUs queried from the ECS is half of the number of vCPUs defined by the ECS flavor.
+For example, a 2-core physical CPU contains 4 vCPUs (threads).
Network QoS
Network QoS uses basic technologies to improve the quality of network communication. A network with QoS enabled offers predictable network performance and effectively allocates network bandwidth to use network resources.
To obtain the QoS data of an ECS flavor, including the maximum bandwidth, assured bandwidth, maximum intranet PPS, and NIC multi-queue, see A Summary List of ECS Specifications.
The intranet bandwidth and PPS of an ECS are determined by the ECS flavor.diff --git a/docs/ecs/umn/en-us_topic_0035470100.html b/docs/ecs/umn/en-us_topic_0035470100.html deleted file mode 100644 index c93bcf48..00000000 --- a/docs/ecs/umn/en-us_topic_0035470100.html +++ /dev/null @@ -1,221 +0,0 @@ - - -- Assured intranet bandwidth: indicates the guaranteed bandwidth allocated to an ECS when there is a network bandwidth contention in the entire network.
- Maximum intranet bandwidth: indicates the maximum bandwidth that can be allocated to an ECS when the ECS does not compete for network bandwidth (other ECSs on the host do not have high requirements on network bandwidth).
- Maximum intranet PPS: indicates the maximum ECS capability in sending and receiving packets.
PPS: packets per second, indicates the number of packets sent per second. It is usually used to measure the network performance.
- - NIC multi-queues: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth
- Maximum NICs: indicates the maximum number of NICs that can be attached to an ECS.
- For instructions about how to test PPS, see How Can I Test Network Performance?.
- For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
- The maximum bandwidth is the total bandwidth allocated to an ECS. If an ECS has multiple NICs, the sum of the maximum bandwidths allocated to all NICs cannot exceed the maximum bandwidth allocated to the ECS.
- NIC multi-queues: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth
- Maximum NICs: indicates the maximum number of NICs that can be attached to an ECS.
- Maximum supplementary NICs: indicates the maximum number of supplementary NICs that can be attached to an ECS.
+- - For instructions about how to test PPS, see How Can I Test Network Performance?.
- For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
- The maximum bandwidth is the total bandwidth allocated to an ECS. If an ECS has multiple NICs, the sum of the maximum bandwidths allocated to all NICs cannot exceed the maximum bandwidth allocated to the ECS.
High-Performance Computing ECSs
---Overview
H2 ECSs are designed to meet high-end computational needs, such as molecular modeling and computational fluid dynamics. In addition to the substantial CPU power, the H2 ECSs offer diverse options for low-latency RDMA networking using EDR InfiniBand NICs to support memory-intensive computational requirements.
-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 shared high I/O storage.
--Specifications
-- -
-Table 1 H2 ECS specifications Flavor
-vCPUs
-Memory (GiB)
-Max./Assured Bandwidth (Gbit/s)
-Max. PPS (10,000)
-Max. NIC Queues
-Max. NICs
-Virtualization
-Local Disks
-Local Disk (TB)
-Network
-Hardware
-h2.3xlarge.10
-16
-128
-13/13
-90
-8
-12
-KVM
-1
-3.2
-100 Gbit/s EDR InfiniBand
-CPU: Intel® Xeon® E5-2667 v4
-h2.3xlarge.20
-16
-256
-13/13
-90
-8
-12
-KVM
-1
-3.2
-100 Gbit/s EDR InfiniBand
--
-Table 2 Hl1 ECS specifications Flavor
-vCPUs
-Memory (GiB)
-Max./Assured Bandwidth (Gbit/s)
-Max. PPS (10,000)
-Max. NIC Queues
-Max. NICs
-Virtualization
-Network
-Hardware
-hl1.8xlarge.8
-32
-256
-9/9
-90
-8
-12
-KVM
-100 Gbit/s EDR InfiniBand
-CPU: Intel® Xeon® Processor E5-2690 v4
--Scenarios
- Applications
H2 and Hl1: High-performance computing (HPC), big data, and Artificial Intelligence (AI)
- - Application scenarios
-
- High-performance hardware: The ratio of memory to vCPU is 8:1, and a large number of multi-thread physical CPUs are available to provide high-performance storage I/O and high-throughput network connections.
- Designed for HPC clusters: Multiple Hl1 ECSs can be clustered to install scalable, clustered file system, such as Lustre. HPC applications running on H2 ECSs can read and modify the data stored in the ECSs.
- RDMA network connection: Same as H2 ECSs, Hl1 ECSs also offer RDMA network using EDR 100 Gbit/s InfiniBand NICs. Hl1 ECSs can communicate with H2 ECSs with RDMA protocol. In addition, Hl1 ECSs can access EVS disks over the RDMA protocol, which allows up to 56 Gbit/s storage bandwidth.
- Application scenarios
H2 and Hl1 ECSs provide computing capabilities for clusters with a large memory, good connectivity between nodes, and high storage I/O. The typical application scenarios include HPC, big data, and AI. In HPC solution, Hl1 ECSs are perfectly suited for the Lustre parallel distributed file system, generally used for large-scale cluster computing.
-For example, in HPC scenario, H2 ECSs can be used as compute nodes, and Hl1 ECSs can be used as storage nodes.
-
-Features
High-performance computing ECSs have the following features:
-- Large memory capacity and more processor cores than other types of ECSs
- Up to 32 vCPUs
- H2 and Hl1 ECSs use InfiniBand NICs that provide a bandwidth of 100 Gbit/s.
- Hl1 ECSs can use the following types of EVS disks as system disk and data disk:
High I/O (performance-optimized I)
-Ultra-high I/O (latency-optimized)
- - Hl1 ECSs support 56 Gbit shared high I/O storage.
To support 56 Gbit 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.
- 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
Red Hat
-Red Hat Enterprise Linux 7.9 64bit
-SUSE
-- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 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 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?
- 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
Red Hat
-Red Hat Enterprise Linux 7.9 64bit
-SUSE
-- Novell SUSE Linux Enterprise Server 15 SP3 64bit
- Novell SUSE Linux Enterprise Server 15 SP2 64bit
- Novell SUSE Linux Enterprise Server 12 SP4 64bit
- Novell SUSE Linux Enterprise Server 12 SP3 64bit
- Charging an Hl1 ECS is stopped when it is stopped.
-- diff --git a/docs/ecs/umn/en-us_topic_0035550301.html b/docs/ecs/umn/en-us_topic_0035550301.html index de5ff6cd..31f5c5bc 100644 --- a/docs/ecs/umn/en-us_topic_0035550301.html +++ b/docs/ecs/umn/en-us_topic_0035550301.html @@ -1,7 +1,7 @@--Parent topic: ECS Specifications and Types-Memory-optimized ECSs
-Overview
- M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced computing, security, and stability. Each M7n ECS can have a maximum number of 96 vCPUs and a memory speed of 3,200 MHz, and provide a secure and trusted cloud environment for memory-intensive computing applications.
- M4 ECSs use the second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable computing performance. Using 25GE high-speed intelligent NICs, M4 ECSs provide a maximum memory size of 512 GiB based on DDR4 for memory-intensive applications with high requirements on network bandwidth and Packets Per Second (PPS).
- M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in the memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing mechanism to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive computing applications.
- M2 ECSs use Intel Xeon E5-2690 v4 CPUs and are designed for memory-optimized applications.
Overview
- M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced computing, security, and stability. Each M7n ECS can have a maximum number of 96 vCPUs and a memory speed of 3,200 MHz, and provide a secure and trusted cloud environment for memory-intensive computing applications.
- M4 ECSs use the second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable computing performance. Using 25GE high-speed intelligent NICs, M4 ECSs provide a maximum memory size of 512 GiB based on DDR4 for memory-intensive applications with high requirements on network bandwidth and Packets Per Second (PPS).
- M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in the memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing mechanism to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive computing applications.
Specifications
- -Table 1 M7n ECS specifications Flavor
@@ -530,70 +530,12 @@
-Table 4 M2 ECS specifications Flavor
-vCPUs
-Memory
-(GiB)
-Max./Assured Bandwidth
-(Gbit/s)
-Max. PPS
-(10,000)
-Max. NIC Queues
-Virtualization
-Hardware
-m2.4xlarge.8
-16
-128
-8/5
-40
-4
-KVM
-CPU: Intel® Xeon® Processor E5-2690 v4
- -m2.8xlarge.8
-32
-256
-13/8
-60
-8
-KVM
--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 5 lists the OSs supported by memory-optimized ECSs.
+Notes
Table 4 lists the OSs supported by memory-optimized ECSs.
-Table 5 Supported OS versions OS
+-Table 4 Supported OS versions OS
Version
Background
Table 2 shows the ECS password complexity requirements.
--Table 2 Password complexity requirements Parameter
+
diff --git a/docs/ecs/umn/en-us_topic_0036046828.html b/docs/ecs/umn/en-us_topic_0036046828.html index fa7ce61b..b78cb7c7 100644 --- a/docs/ecs/umn/en-us_topic_0036046828.html +++ b/docs/ecs/umn/en-us_topic_0036046828.html @@ -6,7 +6,7 @@Table 2 Password complexity requirements Parameter
Requirement
-Example Value
+Requirement
Password
+Password
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Cannot contain the username or the username spelled backwards.
- Cannot contain more than two consecutive characters in the same sequence as they appear in the username. (This requirement applies only to Windows ECSs.)
- Cannot start with a slash (/) for Windows ECSs.
YNbUwp!dUc9MClnv
-NOTE:-The example password is generated randomly. Do not use it.
-
This section describes how to detach a disk from a running ECS.
Constraints
- The EVS disk to be detached must be mounted to a point other than /dev/sda or /dev/vda.
EVS disks mounted to /dev/sda or /dev/vda are system disks and cannot be detached from running ECSs.
- - Before detaching an EVS disk from a running Windows ECS, make sure that OTC Tools have been installed on the ECS and that the tools are running properly.
- Before detaching an EVS disk from a running Windows ECS, ensure that no programs are reading data from or writing data to the disk. Otherwise, data will be lost.
- SCSI EVS disks cannot be detached from running Windows ECSs.
- Before detaching an EVS disk from a running Windows ECS, make sure that OTC Tools have been installed on the ECS and that the tools are running properly.
- Before detaching an EVS disk from a running Windows ECS, ensure that no programs are reading data from or writing data to the disk. Otherwise, data will be lost.
- SCSI EVS disks cannot be detached from running Windows ECSs.
- Before detaching an EVS disk from a running Linux ECS, you must log in to the ECS and run the umount command to cancel the association between the disk and the file system. In addition, ensure that no programs are reading data from or writing data to the disk. Otherwise, detaching the disk will fail.
Notes
- On a Windows ECS, if the disk is in non-offline state, the system forcibly detaches the EVS disk. If this occurs, the system may generate a xenvbd alarm. You can ignore this alarm.
To view the status of an EVS disk, perform the following operations:
diff --git a/docs/ecs/umn/en-us_topic_0036068717.html b/docs/ecs/umn/en-us_topic_0036068717.html index d33a53ab..17ae14d8 100644 --- a/docs/ecs/umn/en-us_topic_0036068717.html +++ b/docs/ecs/umn/en-us_topic_0036068717.html @@ -54,13 +54,13 @@ STARTMODE="onboot"- Upload the obtained passthrough NIC driver to a directory on the ECS, for example, /home.
- Switch to user root on the ECS CLI and open the target directory.
In this example, the passthrough NIC driver is stored in the /home directory. Run the cd /home command to switch to the target directory.
-- Run the following command to decompress the software package. (In this procedure, ixgbevf version 2.16.4 is used as an example.) -
- Run the following command to switch to the generated src directory:
cd ixgbevf-2.16.4/src
+- Run the following command to decompress the software package. +
- Run the following command to switch to the generated src directory:
cd ixgbevf-2.16.4/src
- Run the following commands to install the driver:
make install
- Run the following command to restart the ECS to make the drive take effect: -
- Switch to user root on the ECS CLI and open the src directory, for example, by running the cd /home/ixgbevf-2.16.4/src command. Then, run the following commands to check whether the driver has been installed:
rmmod ixgbevf
-insmod ./ixgbevf.ko
+- Switch to user root on the ECS CLI and open the src directory, for example, by running the cd /home/ixgbevf-2.16.4/src command. Then, run the following commands to check whether the driver has been installed:
rmmod ixgbevf
+insmod ./ixgbevf.ko
ethtool -i NIC_name
In the preceding command, NIC_name specifies the passthrough NIC name, for example, ens5.
- After you run the rmmod ixgbevf command, the system may display an error message. This message does not affect the installation of the passthrough NIC driver and can be ignored.
- NIC_name specifies the passthrough NIC name, for example, ens5.
What Is the cloudbase-init Account in Windows ECSs Used for?
-Description
In Windows ECSs, cloudbase-init is the default account of the Cloudbase-Init agent program. It is used to obtain the metadata and execute configurations when the ECS starts.
- diff --git a/docs/ecs/umn/en-us_topic_0038024694.html b/docs/ecs/umn/en-us_topic_0038024694.html index adb1feae..eadaf9bb 100644 --- a/docs/ecs/umn/en-us_topic_0038024694.html +++ b/docs/ecs/umn/en-us_topic_0038024694.html @@ -3,7 +3,7 @@This account is unavailable on Linux ECSs.
+What Is the Cloudbase-Init Account in Windows ECSs Used for?
+@@ -12,7 +12,7 @@Description
In Windows ECSs, cloudbase-init is the default account of the Cloudbase-Init agent program. It is used to obtain the metadata and execute configurations when an ECS starts.
+ This account is unavailable on Linux ECSs.
Do not modify or delete this account or uninstall the Cloudbase-Init agent program. Otherwise, you will be unable to insert data to initialize an ECS created using a Windows private image.
- Username: Administrator
- RID: 500
- LM-HASH value: C8825DB10F2590EAAAD3B435B51404EE
- NT-HASH value: 683020925C5D8569C23AA724774CE9CC
Use an image to create two ECSs, ecs01 and ecs02. Then, verify that the hash values of the cloudbase-init account for the two ECSs are different.
- LM-HASH and NTLM-HASH values of the cloudbase-init account for ecs01Figure 1 ecs01-
- LM-HASH and NTLM-HASH values of the cloudbase-init account for ecs02Figure 2 ecs02+
- LM-HASH and NTLM-HASH values of the cloudbase-init account for ecs02Figure 2 ecs02
Large-Memory ECSs
Overview
Large-memory ECSs provide an even larger amount of memory than memory-optimized ECSs. They are used for applications that require a large amount of memory, rapid data switching, low latency, and capability of processing large volumes of data. Large-memory ECSs provide large memory and high computing, storage, and network performance.
Specifications
diff --git a/docs/ecs/umn/en-us_topic_0039588795.html b/docs/ecs/umn/en-us_topic_0039588795.html index 72fd6b34..4b4274d9 100644 --- a/docs/ecs/umn/en-us_topic_0039588795.html +++ b/docs/ecs/umn/en-us_topic_0039588795.html @@ -4,7 +4,7 @@Scenarios
After submitting the request for creating an ECS, you can view the creation status. This section describes how to view the creation status of an ECS.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- After creating an ECS, view the creation status above the ECS list beside the common operations (Start, Stop, Restart, and Delete).Figure 1 ECS creation status-
- Click the number displayed above Creating and view task details.
- An ECS that is being created is in one of the following states:
- Creating: The ECS is being created.
- Faulty: Creating the ECS failed. In such a case, the system automatically rolls back the task and displays an error code on the GUI, for example, Ecs.0013 Insufficient EIP quota.
- Running: The request of creating the ECS has been processed, and the ECS is running properly. An ECS in this state can provide services for you.
See How Do I Handle Error Messages Displayed on the Management Console? for troubleshooting.
+ - Click the number displayed above Creating and view task details.diff --git a/docs/ecs/umn/en-us_topic_0040630518.html b/docs/ecs/umn/en-us_topic_0040630518.html index 600d1cd3..61b5bffa 100644 --- a/docs/ecs/umn/en-us_topic_0040630518.html +++ b/docs/ecs/umn/en-us_topic_0040630518.html @@ -17,7 +17,7 @@
- An ECS that is being created is in one of the following states:
- Creating: The ECS is being created.
- Faulty: Creating the ECS failed. In such a case, the system automatically rolls back the task and displays an error code on the GUI, for example, Ecs.0013 Insufficient EIP quota.
- Running: The request of creating the ECS has been processed, and the ECS is running properly. An ECS in this state can provide services for you.
See How Do I Handle Error Messages Displayed on the Management Console? for troubleshooting.
- If you find that the task status area shows an ECS creation failure but the ECS has been created successfully and displayed in the ECS list, see Why Does the Failures Area Show an ECS Creation Failure But the ECS List Displays the Created ECS?
- An ECS that is being created is in one of the following states:
- Run the following command to delete the existing /etc/localtime file:
rm /etc/localtime
- Run the following command to create a symbolic link between /etc/localtime and your time zone file so that the ECS can find this time zone file when it references the local time:
ln -sf /usr/share/zoneinfo/Asia/city1/etc/localtime
- Run the following command to 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
+ - 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/city1
diff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html index 18239966..c3c76e49 100644 --- a/docs/ecs/umn/en-us_topic_0041169567.html +++ b/docs/ecs/umn/en-us_topic_0041169567.html @@ -8,7 +8,23 @@
- An ECS that is being created is in one of the following states:
2024-01-30
+2024-05-11
+Modified the following content:
+Terminated M2 ECSs in Memory-optimized ECSs.
+Terminated P1 and P2 ECSs in GPU-accelerated ECSs.
+Deleted section "High-Performance Computing ECSs" and terminated H2 and Hl1 ECSs.
+Deleted section "How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?"
+Deleted section "How Can I Manually Configure an IP Address for an InfiniBand NIC?"
+2024-04-30
+Modified the following content:
+Added the pi2.3xlarge.4 flavor in GPU-accelerated ECSs.
+2024-01-30
Added the following content:
@@ -91,13 +107,13 @@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.
- Modified the constraints in Application Scenarios for Using Key Pairs.
- Modified operations in Adding Tags.
- Modified operations in Setting Alarm Rules and Viewing Traces.
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?
- 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
@@ -191,7 +207,7 @@2020-11-12
Modified the following content:
-- Changed CSBS to CBR in ECS and Other Services.
- Added CBR to back up ECS data in Step 3: Configure Advanced Settings.
- Added CBR to back up ECS data in Backup Using CBR.
- Added description in notes in Migrating an ECS, indicating that CBR backups are not affected by cold migrations.
- Added a solution of using CBR in Why Does It Take Longer to Create ECSs When I Use a Full-ECS Image?
- Changed CSBS to CBR in ECS and Other Services.
- Added CBR to back up ECS data in Step 3: Configure Advanced Settings.
- Added CBR to back up ECS data in 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
@@ -381,7 +397,7 @@Added the following content:
- Changing the Login Password on an ECS
- Supported advanced disk enablement.
- What Should I Do If Cloud-Init Does Not Work After Python Is Upgraded?
- Why Does the System Display Error Code 0x112f When I Log In to a Windows ECS?
- How Can I Enable Virtual Memory on a Windows ECS?
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 Backup Using CBR and Why Does It Take Longer to Create ECSs When I Use a Full-ECS Image? to support full-ECS images.
- Modified description in Large-Memory ECSs, Disk-intensive ECSs, and Can I Attach Multiple Disks to an ECS?, allowing an ECS to have up to 60 attached disks.
- Modified description in Overview, allowing the tags added during ECS creation to be automatically added to the created EIP and EVS disks.
- Modified description in 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
@@ -490,7 +506,7 @@2017-10-18
Modified the following content:
-- Changed the OSs supported by H2 and Hl1 ECSs in High-Performance Computing ECSs.
- Changed the OSs supported by H2 and Hl1 ECSs in high-performance computing ECSs.
2017-10-06
@@ -510,7 +526,7 @@2017-09-18
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?
- 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 section "How Can I Check Whether the Network Communication Between Two ECSs Equipped with an InfiniBand NIC Driver Is Norma?"
2017-09-06
@@ -537,7 +553,7 @@2017-06-07
Modified the following content:
-- Modified notes on using H2 ECSs in High-Performance Computing ECSs.
- Modified notes on using H2 ECSs in high-performance computing ECSs.
2017-06-05
@@ -561,7 +577,7 @@2017-05-08
Added the following content:
-- Obtaining ECS Console Logs
- Enabling NIC Multi-Queue
- How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?
- Obtaining ECS Console Logs
- Enabling NIC Multi-Queue
- Section "How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?"
2017-04-07
@@ -570,7 +586,7 @@Modified the following content:
- Added G2, M2, and H2 ECSs in ECS Types.
- Modified H1 ECS specifications in High-Performance Computing ECSs.
- Modified H1 ECS specifications in high-performance computing ECSs.
- Modified large-memory ECS specifications in Large-Memory ECSs.
- Added the System Status Check Failed metric in Basic ECS Metrics.
Added the following content:
Modified the following content:
-- Modified the instructions to configure keyboard languages in VNC logins in Remotely Logging In to a Windows ECS (Using VNC).
- Modified the instructions for configuring keyboard languages in VNC logins in Remotely Logging In to a Windows ECS (Using VNC).
2016-09-26
Modified the following content:
-- Added the instructions to configure keyboard languages in VNC logins in Remotely Logging In to a Windows ECS (Using VNC).
- Added the instructions for configuring keyboard languages in VNC logins in Remotely Logging In to a Windows ECS (Using VNC).
2016-09-23
@@ -661,15 +677,15 @@2016-09-18
Added the following content:
-- Expanding the Local Disks of a Disk-intensive ECS
- What Is the cloudbase-init Account in Windows ECSs Used for?
- 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.
- 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
Added the following content:
-- GPU-accelerated ECSs
- Disk-intensive ECSs
- Why Is the NIC Not Working?
- High-Performance Computing ECSs
- Detaching an EVS Disk from a Running ECS
- What Browser Version Is Required to Remotely Log In to an ECS?
- Why Does the Login to My Linux ECS Using a Key File Fail?
- Why Does the System Display a Message Indicating that the Password for Logging In to a Windows ECS Cannot Be Obtained?
- GPU-accelerated ECSs
- Disk-intensive ECSs
- Why Is the NIC Not Working?
- High-Performance Computing ECSs
- Detaching an EVS Disk from a Running ECS
- What Browser Version Is Required to Remotely Log In to an ECS?
- Why Does the Login to My Linux ECS Using a Key File Fail?
- Why Does the System Display a Message Indicating that the Password for Logging In to a Windows ECS Cannot Be Obtained?
2016-07-15
diff --git a/docs/ecs/umn/en-us_topic_0042400609.html b/docs/ecs/umn/en-us_topic_0042400609.html index 0126202f..2c6f1fdd 100644 --- a/docs/ecs/umn/en-us_topic_0042400609.html +++ b/docs/ecs/umn/en-us_topic_0042400609.html @@ -64,10 +64,10 @@/securitykey
Obtains temporary AKs and SKs.
-Before enabling an ECS to obtain a temporary AK and SK, make sure that the op_svc_ecs account has been authorized on IAM and that the desired ECS resources have been authorized for management.
+Before enabling an ECS to obtain a temporary AK and SK, make sure that the op_svc_ecs account has been authorized on IAM and that the desired ECS resources have been authorized for management.
EC2
+EC2-compatible
/meta-data/hostname
EC2
+EC2-compatible
/meta-data/local-hostname
The meaning of this field is the same as that of hostname.
EC2
+EC2-compatible
/meta-data/public-hostname
The meaning of this field is the same as that of hostname.
EC2
+EC2-compatible
/meta-data/instance-type
Displays an ECS flavor.
EC2
+EC2-compatible
/meta-data/local-ipv4
If there are multiple NICs, only the IP address of the primary NIC is displayed.
EC2
+EC2-compatible
/meta-data/placement/availability-zone
Displays the AZ accommodating an ECS.
EC2
+EC2-compatible
/meta-data/public-ipv4
Displays the EIP bound to an ECS.
+Displays the EIP bound to the ECS.
If there are multiple NICs, only the EIP of the primary NIC is displayed.
EC2
+EC2-compatible
/meta-data/public-keys/0/openssh-key
Displays the public key of an ECS.
EC2
+EC2-compatible
/user-data
Displays ECS user data.
EC2
+EC2-compatible
/meta-data/security-groups
Prerequisites
- The target ECS has been logged in.
- Security group rules in the outbound direction meet the following requirements:
- Protocol: TCP
- Port: 80
- Destination: 169.254.0.0/16
- @@ -335,7 +334,7 @@If you use the default security group rules for the outbound direction, the metadata can be accessed because the default rules meet the preceding requirements. Default security group rules for the outbound direction are as follows:
-- Protocol: All
- Port: All
- Destination: 0.0.0.0/0
If you use the default security group rules for the outbound direction, the metadata can be accessed because the default rules meet the preceding requirements. For details about the default security group rules for the outbound direction, see Default Security Group and Rules.
az1.dc1
Public IPv4 (EC2 Compatible API)
This API is used to query the EIP bound to an ECS. If there are multiple NICs, only the EIP of the primary NIC is displayed.
+Public IPv4 (EC2 Compatible API)
This API is used to query the EIP bound to an ECS. If there are multiple NICs, only the EIP of the primary NIC is displayed.
- URI
- Usage method
- Example diff --git a/docs/ecs/umn/en-us_topic_0046912051.html b/docs/ecs/umn/en-us_topic_0046912051.html index 26d58f75..d53e152a 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.
@@ -51,9 +51,9 @@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.
+- After disabling a CMK or scheduling the deletion of a CMK takes effect, the EVS disk encrypted using this CMK can still be used until the disk is detached from and then attached to an ECS again. During this process, the disk fails to be attached to the ECS because the CMK cannot be obtained, so the EVS disk becomes unavailable.
For details about KMS, see Key Management Service User Guide.
+For details about KMS, see Key Management Service User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0047654687.html b/docs/ecs/umn/en-us_topic_0047654687.html index 631aed4d..c9ed8701 100644 --- a/docs/ecs/umn/en-us_topic_0047654687.html +++ b/docs/ecs/umn/en-us_topic_0047654687.html @@ -4,12 +4,12 @@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 on PuTTY Key Generator, 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. You cannot import the key on the management console.
diff --git a/docs/ecs/umn/en-us_topic_0048642616.html b/docs/ecs/umn/en-us_topic_0048642616.html index 94191fb0..385326cc 100644 --- a/docs/ecs/umn/en-us_topic_0048642616.html +++ b/docs/ecs/umn/en-us_topic_0048642616.html @@ -4,20 +4,19 @@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 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 key pair page, click Import Key Pair.
- Copy the public key content in the .txt file to Public Key Content and click OK.
Cloud-Init is an open-source cloud initialization program, which initializes some of the customized configurations of a newly created ECS, such as the hostname, key pair, and user data.
All standard (Standard_xxx) and enterprise (Enterprise_xxx) images support Cloud-Init. Only certain community images (Community_xxx) do not support it.
Using Cloud-Init to initialize your ECSs will affect your ECS, IMS, and AS services.
-Impact on IMS
To ensure that ECSs created using a private image support customized configurations, you must install Cloud-Init or Cloudbase-Init on the ECSs before using them to create private images.- For Windows OSs, download and install Cloudbase-Init.
- For Linux OSs, download and install Cloud-Init.
-Impact on IMS
To ensure that ECSs created using a private image support custom configurations, you must install Cloud-Init or Cloudbase-Init on the ECSs before using them to create private images.- For Windows OSs, download and install Cloudbase-Init.
- For Linux OSs, download and install Cloud-Init.
After being installed in an image, Cloud-Init or Cloudbase-Init automatically configures initial attributes for the ECSs created using this image.
For more information, see Image Management Service User Guide.
Impact on ECS
- When creating an ECS, if the selected image supports Cloud-Init, you can use the User Data function to specify custom configuration, such as ECS login password to the ECS. Such custom settings will take effect upon ECS initialization. For details, see Passing User Data to ECSs.
- If Cloud-Init is supported, ECSs do not support password authentication anymore. All newly created ECSs use key pair authentication. This change will influence your ECS logins. For details, see the following sections:
- Login Overview
- What Is the cloudbase-init Account in Windows ECSs Used for?
- Why Does the Login to My Linux ECS Using a Key File Fail?
- Why Does the System Display a Message Indicating that the Password for Logging In to a Windows ECS Cannot Be Obtained?
-Impact on ECS
- When creating an ECS, if the selected image supports Cloud-Init, you can use the User Data function to specify custom configuration, such as ECS login password to the ECS. Such custom settings will take effect upon ECS initialization. For details, see Passing User Data to ECSs.
- If Cloud-Init is supported, ECSs do not support password authentication anymore. All newly created ECSs use key pair authentication. This change will influence your ECS logins. For details, see the following sections:
- If Cloud-Init is supported, you can view and use metadata to configure and manage running ECSs. For details, see Obtaining Metadata.
Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
+Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
Notes
- When using Cloud-Init, enable DHCP in the VPC to which the ECS belongs.
- When using Cloud-Init, ensure that security group rules for the outbound direction meet the following requirements:
- Protocol: TCP
- Port: 80
- Destination: 169.254.0.0/16
diff --git a/docs/ecs/umn/en-us_topic_0058747426.html b/docs/ecs/umn/en-us_topic_0058747426.html deleted file mode 100644 index 8e9a025e..00000000 --- a/docs/ecs/umn/en-us_topic_0058747426.html +++ /dev/null @@ -1,30 +0,0 @@ - - -If you use the default security group rules for the outbound direction, the metadata can be accessed because the default rules meet the preceding requirements. Default security group rules for the outbound direction are as follows:
-- Protocol: All
- Port: All
- Destination: 0.0.0.0/0
If you use the default security group rules for the outbound direction, the metadata can be accessed because the default rules meet the preceding requirements. For details about the default security group rules for the outbound direction, see Security Group.
How Can I Check Whether the Network Communication Is Normal Between Two ECSs Equipped with an InfiniBand NIC Driver?
--For high-performance H2 ECSs equipped with an InfiniBand NIC driver (InfiniBand ECSs for short), perform the following operations to check whether the driver installation is successful and whether the network communication between the ECSs is normal.
-- During the check, if your ECS has no command tool installed, such as ibstat, obtain the tool from the installation package for the InfiniBand NIC driver and install the tool.
-- Check whether the NICs of the InfiniBand ECSs are functional.
- Log in to the ECS.
- Run the following command to check whether the NIC is functional:ibstat-
- If it is functional, go to 2.
- If it is not functional, contact customer service for technical support.
- Check whether the network communication between two InfiniBand ECSs is normal.
- Log in to one InfiniBand ECS and run the following command: -
- Log in to the other InfiniBand ECS and run the following command:
ib_write_bw -x 0 --pkey_index 0ip_addr
-In the preceding command, ip_addr is the NIC IP address of the first InfiniBand ECS.
- - Check whether the terminal display is correct.
-
- If the terminal display is shown in Figure 1, the network communication between the two InfiniBand ECSs is normal.
- If the InfiniBand network is inaccessible, contact customer service for technical support.
-- - - \ No newline at end of file diff --git a/docs/ecs/umn/en-us_topic_0058758453.html b/docs/ecs/umn/en-us_topic_0058758453.html index 8af88cfe..33ecaba4 100644 --- a/docs/ecs/umn/en-us_topic_0058758453.html +++ b/docs/ecs/umn/en-us_topic_0058758453.html @@ -9,7 +9,7 @@--Parent topic: Network Configurations-Support of NIC Multi-Queue
NIC multi-queue can be enabled on an ECS only when the ECS specifications, virtualization type, and image OS meet the requirements described in this section.
- For details about the ECS specifications that support NIC multi-queue, see ECS Specifications and Types.-
If the number of NIC queues is greater than 1, NIC multi-queue is supported.
- The virtualization type must be KVM.
- The Linux public images listed in Table 2 support NIC multi-queue.
- Windows public images have not supported NIC multi-queue. If you enable NIC multi-queue in a Windows public image, starting an ECS created using such an image may be slow.
- It is a good practice to upgrade the kernel version of the Linux ECS to 2.6.35 or later. Otherwise, NIC multi-queue is not supported.
Run the uname -r command to obtain the kernel version. If the kernel version is earlier than 2.6.35, contact customer service to upgrade the kernel.
+ - The virtualization type must be KVM.
- The Linux public images listed in Table 2 support NIC multi-queue.
- Windows public images have not supported NIC multi-queue. If you enable NIC multi-queue in a Windows public image, starting an ECS created using such an image may be slow.
- It is a good practice to upgrade the kernel version of the Linux ECS to 2.6.35 or later. Otherwise, NIC multi-queue is not supported.
Run the uname -r command to obtain the kernel version. If the kernel version is earlier than 2.6.35, contact technical support to upgrade the kernel.
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.
+- 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.
- Add Content-Type to the request header.
The value of Content-Type is application/openstack-images-v2.1-json-patch.
The request URI is in the following format:
PATCH /v2/images/{image_id}
diff --git a/docs/ecs/umn/en-us_topic_0060610074.html b/docs/ecs/umn/en-us_topic_0060610074.html index 9f7e6a48..95519343 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 a CSV file to a local directory. The file includes the IDs, private IP addresses, and EIPs of your ECSs.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the upper right corner above the ECS list, click
.The system will automatically export all ECSs in the current region under your account to a local directory.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the upper right corner above the ECS list, click .
The system will automatically export all ECSs in the current region under your account to a local directory.
Figure 1 Exporting ECS information
diff --git a/docs/ecs/umn/en-us_topic_0074752335.html b/docs/ecs/umn/en-us_topic_0074752335.html index 5b915d8b..ce503791 100644 --- a/docs/ecs/umn/en-us_topic_0074752335.html +++ b/docs/ecs/umn/en-us_topic_0074752335.html @@ -5,7 +5,7 @@ To export certain ECSs, select the target ECSs and click
in the upper right corner of the page.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
- Enter n and press Enter to create a new partition.
Because the system disk has two existing partitions, the system automatically creates the third one.
+ - Enter n and press Enter to create a new partition.
Because the system disk has two existing partitions, the system automatically creates the third one.
Information similar to the following is displayed.
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@@ -88,13 +88,13 @@ Writing superblocks and filesystem accounting information: done
Figure 11 Viewing the file system type
According to the preceding figure, the UUID of the new partition is 96e5e028-b0fb-4547-a82a-35ace1086c4f.
- Run the following command to open the fstab file using the vi editor:
vi /etc/fstab
- - Press i to enter editing mode.
- Move the cursor to the end of the file and press Enter. Then, add the following information:
UUID=96e5e028-b0fb-4547-a82a-35ace1086c4f /root/new ext4 defaults 0 0
+ - Press i to enter editing mode.
- Move the cursor to the end of the file and press Enter. Then, add the following information:
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
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
- - 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
+- 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
- Run the following command to open the fstab file using the vi editor:
- Log in to ecs-01 and ecs-02 and obtain their private IP addresses.
The first is the root partition, and the second is the swap partition.
- - Log in to ecs-01 and ecs-02 and obtain their private IP addresses.
- View and edit the fstab partition table to delete the swap partition attaching information.
- Run the following command to view the fstab partition table: +
- View and edit the fstab partition table to delete the swap partition attachment information.
- Run the following command to view the fstab partition table:
[root@sluo-ecs-a611 ~]# tail -n 3 /etc/fstab # UUID=7c4fce5d-f8f7-4ed6-8463-f2bd22d0ddea / ext4 defaults 1 1 UUID=5de3cf2c-30c6-4fb2-9e63-830439d4e674 swap swap defaults 0 0
- - Run the following command to edit the fstab partition table and delete the swap partition attaching information. +
- Run the following command to edit the fstab partition table and delete the swap partition attachment information.
tail -n 3 /etc/fstab
[root@sluo-ecs-a611 ~]# vi /etc/fstab [root@sluo-ecs-a611 ~]# tail -n 3 /etc/fstab # @@ -64,7 +64,7 @@ Number Start End Size Type File system Flags- Run the following command to delete the partition: -
- Press p.
(parted) p +
- Press p.
(parted) p Disk /dev/xvda: 107GB Sector size (logical/physical): 512B/512B Partition Table: msdos diff --git a/docs/ecs/umn/en-us_topic_0081525054.html b/docs/ecs/umn/en-us_topic_0081525054.html index f435d837..271795e7 100644 --- a/docs/ecs/umn/en-us_topic_0081525054.html +++ b/docs/ecs/umn/en-us_topic_0081525054.html @@ -7,7 +7,7 @@
- Run the following command to view the fstab partition table:
Solution
If logging in to an ECS with Cloudbase-Init enabled failed, perform the following operations to locate the fault:
-- Ensure that Cloudbase-Init has been correctly configured on the image that was used to create the ECS.
- If Cloudbase-Init has not been configured, your ECS will not allow customized configurations, and you can log in to it only by using the original image password.
- The ECSs created using a public image have Cloudbase-Init installed by default. Therefore, you do not need to install and configure Cloudbase-Init anymore.
- If you created your ECS by using an external image file, install and configure Cloudbase-Init.
For details, see "Installing and Configuring Cloudbase-Init" in Image Management Service User Guide.
+- Ensure that Cloudbase-Init has been correctly configured on the image that was used to create the ECS.
- If Cloudbase-Init has not been configured, your ECS will not allow customized configurations, and you can log in to it only by using the original image password.
- The ECSs created using a public image have Cloudbase-Init installed by default. You do not need to install and configure Cloudbase-Init anymore.
- If you created your ECS by using an external image file, install and configure Cloudbase-Init.
For details, see "Installing and Configuring Cloudbase-Init" in Image Management Service User Guide.
- Ensure that the key pair for logging in to the ECS is correct.
The key used for obtaining the password must be the key used during the ECS creation.
- Ensure that DHCP is enabled in the VPC to which the ECS belongs.
On the management console, check whether DHCP has been enabled in the target subnet.
diff --git a/docs/ecs/umn/en-us_topic_0083225171.html b/docs/ecs/umn/en-us_topic_0083225171.html deleted file mode 100644 index 10a289e6..00000000 --- a/docs/ecs/umn/en-us_topic_0083225171.html +++ /dev/null @@ -1,30 +0,0 @@ - - -How Can I Manually Configure an IP Address for an InfiniBand NIC?
--IP over InfiniBand (IPoIB) allows IP data transmission over InfiniBand. For SUSE high-performance H2 and HL1 ECSs, if IPoIB is required, you must manually configure an IP address for the InfiniBand NIC after installing the InfiniBand NIC driver.
--Prerequisites
The InfiniBand NIC driver has been installed on the high-performance H2 or HL1 ECSs.
--Background
To prevent IP address conflict of the InfiniBand NICs configured for the ECSs of a tenant, determine the IP address to be configured for an InfiniBand NIC according to the IP addresses available in the VPC. The method is as follows:
-For example, if the first two eight-bits of the IP address (specified by IPADDR) to be configured for the InfiniBand NIC are consistently 169.254, the latter two eight-bits must be the same as those of the eth0 IP address, and the subnet mask must be the same as that of the eth0 NIC.
-An example is provided as follows:
-If the IP address of the eth0 NIC is 192.168.0.100/24, the IP address to be configured for the InfiniBand NIC is 169.254.0.100/24.
--Procedure
- Log in to the ECS.
- Run the following command to switch to user root:
sudo su -
- - Run the following command to edit the /etc/sysconfig/network/ifcfg-ib0 file:
vi /etc/sysconfig/network/ifcfg-ib0
- - Enter the following information:
-
BOOTPROTO=static
-IPADDR=IP address to be configured for the InfiniBand NIC
-NETMASK=Subnet mask
-STARTMODE=auto
-- For instructions about how to obtain the IP address and subnet mask for an InfiniBand NIC, see Background.
- - Run the following command to restart the network for the configuration to take effect: -
-- diff --git a/docs/ecs/umn/en-us_topic_0085634796.html b/docs/ecs/umn/en-us_topic_0085634796.html index 71449d17..3b0446bb 100644 --- a/docs/ecs/umn/en-us_topic_0085634796.html +++ b/docs/ecs/umn/en-us_topic_0085634796.html @@ -1,37 +1,37 @@--Parent topic: Network Configurations-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 TiB, and that supported by GPT is 18 EiB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TiB. To learn more about disk partition styles, see Scenarios and Disk Partitions.
-The method for initializing a disk varies slightly 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.
- When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
+-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 TiB, and that supported by GPT is 18 EiB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TiB. To learn more about disk partition styles, see Scenarios and Disk Partitions.
+The method for initializing a disk varies slightly 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.
+ When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
-Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Procedure
- On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.
The Server Manager window is displayed.
- - In the navigation tree, choose Storage > Disk Management.The Disk Management window is displayed.
- If Figure 1 is displayed, the new disk is offline. Go to 3.
- If Figure 4 is displayed, the Initialize Disk window is prompted. Go to 5.
Procedure
- On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.
The Server Manager window is displayed.
+ - In the navigation tree, choose Storage > Disk Management.The Disk Management window is displayed.- -
- Disks are displayed in the right pane. In the Disk 1 area, right-click Offline and choose Online from the shortcut menu to online the disk.Figure 2 Online the disk-
If the disk is offline, you need to bring it online before initializing it.
+ +- Disks are displayed in the right pane. In the Disk 1 area, right-click Offline and choose Online from the shortcut menu to online the disk.
Figure 2 Online the disk+
- If the disk is offline, you need to bring it online before initializing it.
- After making the disk online, the disk status changes from Offline to Not Initialized. Right-click the disk status and choose Initialize Disk from the shortcut menu, as shown in Figure 3. -
- In the Initialize Disk dialog box, select the target disk, click MBR (Master Boot Record) or GPT (GUID Partition Table), and click OK, as shown in Figure 4. -
The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is larger than 2 TiB.
-If the partition style is changed after the disk has been used, all data on the disk will be lost, so take care to select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.
+- After making the disk online, the disk status changes from Offline to Not Initialized. Right-click the disk status and choose Initialize Disk from the shortcut menu.
Figure 3 Initialize Disk+
- In the Initialize Disk dialog box, select the target disk, click MBR (Master Boot Record) or GPT (GUID Partition Table), and click OK. +
- The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is greater than 2 TiB.
+If the partition style is changed after the disk has been used, all data on the disk will be lost, so take care to select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.
- Right-click at the unallocated space and choose New Simple Volume from the shortcut menu, as shown in Figure 5. -
- On the displayed New Simple Volume Wizard window, click Next.
Figure 6 New Simple Volume Wizard-
- Specify the volume size and click Next. The default value is the maximum size.
Figure 7 Specify Volume Size-
- Assign the drive letter and click Next.
Figure 8 Assign Drive Letter or Path-
- On the displayed Format Partition page, click Format this volume with the following settings, set parameters based on the requirements, and select Perform a quick format. Then, click Next.
Figure 9 Format Partition-
Figure 10 Completing the partition creation-
diff --git a/docs/ecs/umn/en-us_topic_0085634797.html b/docs/ecs/umn/en-us_topic_0085634797.html index d5357190..d7728581 100644 --- a/docs/ecs/umn/en-us_topic_0085634797.html +++ b/docs/ecs/umn/en-us_topic_0085634797.html @@ -1,20 +1,20 @@ The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.
+- Right-click at the unallocated space and choose New Simple Volume from the shortcut menu.
Figure 5 New Simple Volume+
- 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 drive letter and click Next.
Figure 8 Assign Drive Letter or Path+
- On the displayed Format Partition page, click Format this volume with the following settings, set parameters based on the requirements, and select Perform a quick format. Then, click Next.
Figure 9 Format Partition+
Figure 10 Completing the partition creation+
- The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.
- Click Finish. Wait for the initialization to complete. When the volume status changes to Healthy, the initialization has finished successfully, as shown in Figure 11. +
- Click Finish. Wait for the initialization to complete. When the volume status changes to Healthy, the initialization has finished successfully.
Figure 11 Disk initialization succeeded
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 partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.
-The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see Scenarios and Disk Partitions.
-The method for initializing a disk varies slightly 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.
- When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
+-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 partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.
+The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see Scenarios and Disk Partitions.
+The method for initializing a disk varies slightly 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.
+ When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
-Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Creating and Mounting a Partition
The following example shows you how a new primary partition can be created on a new data disk that has been attached to a server. The primary partition will be created using fdisk, and MBR will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured to mount automatically at startup.
+-Creating and Mounting a Partition
The following example shows you how a new primary partition can be created on a new data disk that has been attached to a server. The primary partition will be created using fdisk, and MBR will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured to mount automatically at startup.
- Query what block devices are available on the server.
fdisk -l
-Information similar to the following is displayed:[root@ecs-test-0001 ~]# fdisk -l +
- Query what block devices are available on the server.
fdisk -l
+Information similar to the following is displayed:-[root@ecs-test-0001 ~]# fdisk -l Disk /dev/vda: 42.9 GiB, 42949672960 bytes, 83886080 sectors Units = sectors of 1 * 512 = 512 bytes @@ -31,11 +31,11 @@ Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
In the command output, this server contains two disks. /dev/vda and /dev/vdb. /dev/vda is the system disk, and /dev/vdb is the new data disk.
- - Launch fdisk to partition the new data disk.
fdisk New data disk
-In this example, run the following command:
-fdisk /dev/vdb
-Information similar to the following is displayed:[root@ecs-test-0001 ~]# fdisk /dev/vdb +
In the command output, this server contains two disks: /dev/vda and /dev/vdb. /dev/vda is the system disk, and /dev/vdb is the new data disk.
+- Launch fdisk to partition the new data disk.
fdisk New data disk
+In this example, run the following command:
+fdisk /dev/vdb
+Information similar to the following is displayed:-[root@ecs-test-0001 ~]# fdisk /dev/vdb Welcome to fdisk (util-linux 2.23.2). Changes will remain in memory only, until you decide to write them. @@ -46,39 +46,39 @@ Building a new DOS disklabel with disk identifier 0x38717fc1. Command (m for help):
- Enter n and press Enter to create a new partition.
Information similar to the following is displayed:Command (m for help): n +
- Enter n and press Enter to create a new partition.
Information similar to the following is displayed:-Command (m for help): n Partition type: p primary (0 primary, 0 extended, 4 free) e extendedThere are two types of disk partitions:- Choosing p creates a primary partition.
- Choosing e creates an extended partition.
If MBR is used, a maximum of 4 primary partitions, or 3 primary partitions plus 1 extended partition can be created. The extended partition must be divided into logical partitions before use.
-Disk partitions created using GPT are not categorized.
+There are two types of disk partitions:-- Choosing p creates a primary partition.
- Choosing e creates an extended partition.
If MBR is used, a maximum of four primary partitions, or three primary partitions plus one extended partition can be created. The extended partition must be divided into logical partitions before use.
+Disk partitions created using GPT are not categorized.
- Enter p and press Enter to create a primary partition in this example.
Information similar to the following is displayed:Select (default p): p +
- Enter p and press Enter to create a primary partition in this example.
Information similar to the following is displayed:-Select (default p): p Partition number (1-4, default 1):
Partition number indicates the serial number of the primary partition. The value ranges from 1 to 4.
-- Enter the serial number of the primary partition and press Enter. Primary partition number 1 is used in this example. One usually starts with partition number 1 when partitioning an empty disk.
Information similar to the following is displayed:Partition number (1-4, default 1): 1 +
Partition number indicates the serial number of the primary partition. The value ranges from 1 to 4.
+- Enter the serial number of the primary partition and press Enter. Primary partition number 1 is used in this example. One usually starts with partition number 1 when partitioning an empty disk.
Information similar to the following is displayed:-Partition number (1-4, default 1): 1 First sector (2048-209715199, default 2048):
First sector indicates the start sector. The value ranges from 2048 to 209715199, and the default value is 2048.
-- Select the default start sector 2048 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:First sector (2048-209715199, default 2048): +
First sector indicates the start sector. The value ranges from 2048 to 209715199, and the default value is 2048.
+- Select the default start sector 2048 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:-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.
-Information similar to the following is displayed:
-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.
+Information similar to the following is displayed:
+Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199): Using default value 209715199 Partition 1 of type Linux and of size 100 GiB is set Command (m for help):-A primary partition has been created for the new data disk.
-- Enter p and press Enter to print the partition details.
Information similar to the following is displayed:Command (m for help): p +
A primary partition has been created for the new data disk.
+- Enter p and press Enter to print the partition details.
Information similar to the following is displayed:-Command (m for help): p Disk /dev/vdb: 107.4 GiB, 107374182400 bytes, 209715200 sectors Units = sectors of 1 * 512 = 512 bytes @@ -92,21 +92,21 @@ Disk identifier: 0x38717fc1 Command (m for help):
Details about the /dev/vdb1 partition are displayed.
-- Enter w and press Enter to write the changes to the partition table.
Information similar to the following is displayed:Command (m for help): w +
Details about the /dev/vdb1 partition are displayed.
+- Enter w and press Enter to write the changes to the partition table.
Information similar to the following is displayed:-Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks.
The partition is created.
- In case that you want to discard the changes made before, you can exit fdisk by entering q.
+The partition is created.
+- In case that you want to discard the changes made before, you can exit fdisk by entering q.
- Synchronize the new partition table to the OS.
partprobe
-- Format the new partition with a desired file system format.
mkfs -t File system format /dev/vdb1
-In this example, the ext4 format is used for the new partition.
-mkfs -t ext4 /dev/vdb1
-Information similar to the following is displayed:[root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1 +
- Synchronize the new partition table to the OS.
partprobe
+- Format the new partition with a desired file system format.
mkfs -t File system format /dev/vdb1
+In this example, the ext4 format is used for the new partition.
+mkfs -t ext4 /dev/vdb1
+Information similar to the following is displayed:-[root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1 mke2fs 1.42.9 (28-Dec-2013) Filesystem label= OS type: Linux @@ -129,20 +129,20 @@ Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done
The formatting takes a period of time. Observe the system running status and do not exit.
- The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.
+The formatting takes a period of time. Observe the system running status and do not exit.
+- The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.
- Create a mount point.
mkdir Mount point
-In this example, the /mnt/sdc mount point is created.
-mkdir /mnt/sdc
- The /mnt directory exists on all Linux systems. If the mount point cannot be created, it may be that the /mnt directory has been accidentally deleted. You can run mkdir -p /mnt/sdc to create the mount point.
+- Create a mount point.
mkdir Mount point
+In this example, the /mnt/sdc mount point is created.
+mkdir /mnt/sdc
+- The /mnt directory exists on all Linux systems. If the mount point cannot be created, it may be that the /mnt directory has been accidentally deleted. You can run mkdir -p /mnt/sdc to create the mount point.
- Mount the new partition on the created mount point.
mount Disk partition Mount point
-In this example, the /dev/vdb1 partition is mounted on /mnt/sdc.
-mount /dev/vdb1 /mnt/sdc
-- Check the mount result.
df -TH
-Information similar to the following is displayed:
-[root@ecs-test-0001 ~]# df -TH +
- Mount the new partition on the created mount point.
mount Disk partition Mount point
+In this example, the /dev/vdb1 partition is mounted on /mnt/sdc.
+mount /dev/vdb1 /mnt/sdc
+- Check the mount result.
df -TH
+Information similar to the following is displayed:
+[root@ecs-test-0001 ~]# df -TH Filesystem Type Size Used Avail Use% Mounted on /dev/vda1 ext4 43G 1.9G 39G 5% / devtmpfs devtmpfs 2.0G 0 2.0G 0% /dev @@ -151,33 +151,33 @@ tmpfs tmpfs 2.0G 9.1M 2.0G 1% /run tmpfs tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup tmpfs tmpfs 398M 0 398M 0% /run/user/0 /dev/vdb1 ext4 106G 63M 101G 1% /mnt/sdc
-You should now see that partition /dev/vdb1 is mounted on /mnt/sdc.
- After the server is restarted, the disk will not be automatically mounted. To configure automount at startup, you will need to modify the /etc/fstab file. For details, see Configuring Automatic Mounting at System Start.
+You should now see that partition /dev/vdb1 is mounted on /mnt/sdc.
+- After the server is restarted, the disk will not be automatically mounted. You can modify the /etc/fstab file to configure automount at startup. For details, see Configuring Automatic Mounting at System Start.
Configuring Automatic Mounting at System Start
The fstab file controls what disks are automatically mounted at startup. You can use fstab to configure your data disks to mount automatically. This operation will not affect the existing data.
-The example here uses UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after a reboot. This can even prevent your disk from booting up.
- UUID is the unique character string for disk partitions in a Linux system.
+Configuring Automatic Mounting at System Start
The fstab file controls what disks are automatically mounted at startup. You can use fstab to configure your data disks to mount automatically. This operation will not affect the existing data.
+The example here uses UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after a server stop or start. This can even prevent the server from booting up.
+- UUIDs are the unique character strings for identifying partitions in Linux.
- Query the partition UUID.
blkid Disk partition
-In this example, the UUID of the /dev/vdb1 partition is queried.
-blkid /dev/vdb1
-Information similar to the following is displayed:
-[root@ecs-test-0001 ~]# blkid /dev/vdb1 +
- Query the partition UUID.
blkid Disk partition
+In this example, the UUID of the /dev/vdb1 partition is queried.
+blkid /dev/vdb1
+Information similar to the following is displayed:
+[root@ecs-test-0001 ~]# blkid /dev/vdb1 /dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
-Carefully record the UUID, as you will need it for the following step.
- - Open the fstab file using the vi editor.
vi /etc/fstab
- - 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.
- - Verify that the disk is auto-mounted at startup.
- Unmount the partition.
-
In this example, run the following command:
-umount /dev/vdb1
- - Reload all the content in the /etc/fstab file.
mount -a
- - 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, automatic mounting has been configured:
-root@ecs-test-0001 ~]# mount | grep /mnt/sdc +
Carefully record the UUID, as you will need it for the following step.
+ - Open the fstab file using the vi editor.
vi /etc/fstab
+ - 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.
+ - Verify that the disk is auto-mounted at startup.
- Unmount the partition.
+
In this example, run the following command:
+umount /dev/vdb1
+ - Reload all the content in the /etc/fstab file.
mount -a
+ - 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, automatic mounting has been configured:
+root@ecs-test-0001 ~]# mount | grep /mnt/sdc /dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
- Unmount the partition.
+
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 partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.
-The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see Scenarios and Disk Partitions.
-The method for initializing a disk varies slightly 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.
- When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
+-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 partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.
+The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see Scenarios and Disk Partitions.
+The method for initializing a disk varies slightly 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.
+ When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
-Prerequisites
- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Creating and Mounting a Partition
The following example shows you how a new partition can be created on a new data disk that has been attached to a server. The partition will be created using parted, and GPT will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured to mount automatically at startup.
+-Creating and Mounting a Partition
The following example shows you how a new partition can be created on a new data disk that has been attached to a server. The partition will be created using parted, and GPT will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured to mount automatically at startup.
- Query information about the new data disk.
lsblk
-Information similar to the following is displayed:root@ecs-test-0001 ~]# lsblk +
- Query information about the new data disk.
lsblk
+Information similar to the following is displayed:-root@ecs-test-0001 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 253:0 0 40G 0 disk └─vda1 253:1 0 40G 0 part / vdb 253:16 0 100G 0 disk
In the command output, this server contains two disks. /dev/vda and /dev/vdb. /dev/vda is the system disk, and /dev/vdb is the new data disk.
- - Launch parted to partition the new data disk.
parted New data disk
-In this example, run the following command:
-parted /dev/vdb
-Information similar to the following is displayed:[root@ecs-test-0001 ~]# parted /dev/vdb +
In the command output, this server contains two disks. /dev/vda and /dev/vdb. /dev/vda is the system disk, and /dev/vdb is the new data disk.
+- Launch parted to partition the new data disk.
parted New data disk
+In this example, run the following command:
+parted /dev/vdb
+Information similar to the following is displayed:-[root@ecs-test-0001 ~]# parted /dev/vdb GNU Parted 3.1 Using /dev/vdb Welcome to GNU Parted! Type 'help' to view a list of commands. (parted)
- Enter p and press Enter to view the current disk partition style.
Information similar to the following is displayed:(parted) p +
- Enter p and press Enter to view the current disk partition style.
Information similar to the following is displayed:-(parted) p Error: /dev/vdb: unrecognised disk label Model: Virtio Block Device (virtblk) Disk /dev/vdb: 107GiB @@ -39,14 +39,14 @@ Partition Table: unknown Disk Flags: (parted)
In the command output, the Partition Table value is unknown, indicating that no partition style is set for the new disk.
-- Set the disk partition style.
mklabel Disk partition style
-This command lets you control whether to use MBR or GPT for your partition table. In this example, GPT is used.
-mklabel gpt
- The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is larger than 2 TiB.
-If the partition style is changed after the disk has been used, all data on the disk will be lost, so take care to select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.
+In the command output, the Partition Table value is unknown, indicating that no partition style is set for the new disk.
+- Set the disk partition style.
mklabel Disk partition style
+This command lets you control whether to use MBR or GPT for your partition table. In this example, GPT is used.
+mklabel gpt
+- The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is greater than 2 TiB.
+If the partition style is changed after the disk has been used, all data on the disk will be lost, so take care to select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.
- Enter p and press Enter to view the disk partition style.
Information similar to the following is displayed:(parted) mklabel gpt +
- Enter p and press Enter to view the disk partition style.
Information similar to the following is displayed:-(parted) mklabel gpt (parted) p Model: Virtio Block Device (virtblk) Disk /dev/vdb: 107GiB @@ -58,15 +58,15 @@ Number Start End Size File system Name Flags (parted)
In the command output, the Partition Table value is gpt, indicating that the disk partition style is GPT.
-- Enter unit s and press Enter to set the measurement unit of the disk to sector.
- Create a new partition.
mkpart Partition name Start sector End sector
-In this example, run the following command:
-mkpart test 2048s 100%
-In this example, one partition is created for the new data disk, starting on 2048 and using 100% of the rest of the disk. The two values are used for reference only. You can determine the number of partitions and the partition size based on your service requirements.
-Information similar to the following is displayed:(parted) mkpart opt 2048s 100% +
In the command output, the Partition Table value is gpt, indicating that the disk partition style is GPT.
+- Enter unit s and press Enter to set the measurement unit of the disk to sector.
- Create a new partition.
mkpart Partition name Start sector End sector
+In this example, run the following command:
+mkpart test 2048s 100%
+In this example, one partition is created for the new data disk, starting on 2048 and using 100% of the rest of the disk. The two values are used for reference only. You can determine the number of partitions and the partition size based on your service requirements.
+Information similar to the following is displayed:-(parted) mkpart opt 2048s 100% (parted)
- Enter p and press Enter to print the partition details.
Information similar to the following is displayed:(parted) p +
- Enter p and press Enter to print the partition details.
Information similar to the following is displayed:-(parted) p Model: Virtio Block Device (virtblk) Disk /dev/vdb: 209715200s Sector size (logical/physical): 512B/512B @@ -78,23 +78,23 @@ Number Start End Size File system Name Flags (parted)
- Enter q and press Enter to exit parted.
Information similar to the following is displayed:(parted) q +
- Enter q and press Enter to exit parted.
Information similar to the following is displayed:-(parted) q Information: You may need to update /etc/fstab.
You can configure automatic mounting by updating the /etc/fstab file. Before doing so, format the partition with a desired file system and mount the partition on the mount point.
-- View the disk partition information.
lsblk
-Information similar to the following is displayed:[root@ecs-test-0001 ~]# lsblk +
You can configure automatic mounting by updating the /etc/fstab file. Before doing so, format the partition with a desired file system and mount the partition on the mount point.
+- View the disk partition information.
lsblk
+Information similar to the following is displayed:-[root@ecs-test-0001 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 253:0 0 40G 0 disk └─vda1 253:1 0 40G 0 part / vdb 253:16 0 100G 0 disk └─vdb1 253:17 0 100G 0 part
In the command output, /dev/vdb1 is the partition you created.
-- Format the new partition with a desired file system format.
mkfs -t File system format /dev/vdb1
-In this example, the ext4 format is used for the new partition.
-mkfs -t ext4 /dev/vdb1
-Information similar to the following is displayed:[root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1 +
In the command output, /dev/vdb1 is the partition you created.
+- Format the new partition with a desired file system format.
mkfs -t File system format /dev/vdb1
+In this example, the ext4 format is used for the new partition.
+mkfs -t ext4 /dev/vdb1
+Information similar to the following is displayed:-[root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1 mke2fs 1.42.9 (28-Dec-2013) Filesystem label= OS type: Linux @@ -117,20 +117,20 @@ Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done
The formatting takes a period of time. Observe the system running status and do not exit.
- The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.
+The formatting takes a period of time. Observe the system running status and do not exit.
+- The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.
- Create a mount point.
mkdir Mount point
-In this example, the /mnt/sdc mount point is created.
-mkdir /mnt/sdc
- The /mnt directory exists on all Linux systems. If the mount point cannot be created, it may be that the /mnt directory has been accidentally deleted. You can run mkdir -p /mnt/sdc to create the mount point.
+- Create a mount point.
mkdir Mount point
+In this example, the /mnt/sdc mount point is created.
+mkdir /mnt/sdc
+- The /mnt directory exists on all Linux systems. If the mount point cannot be created, it may be that the /mnt directory has been accidentally deleted. You can run mkdir -p /mnt/sdc to create the mount point.
- Mount the new partition on the created mount point.
mount Disk partition Mount point
-In this example, the /dev/vdb1 partition is mounted on /mnt/sdc.
-mount /dev/vdb1 /mnt/sdc
-- Check the mount result.
df -TH
-Information similar to the following is displayed:
-[root@ecs-test-0001 ~]# df -TH +
- Mount the new partition on the created mount point.
mount Disk partition Mount point
+In this example, the /dev/vdb1 partition is mounted on /mnt/sdc.
+mount /dev/vdb1 /mnt/sdc
+- Check the mount result.
df -TH
+Information similar to the following is displayed:
+[root@ecs-test-0001 ~]# df -TH Filesystem Type Size Used Avail Use% Mounted on /dev/vda1 ext4 43G 1.9G 39G 5% / devtmpfs devtmpfs 2.0G 0 2.0G 0% /dev @@ -139,33 +139,33 @@ tmpfs tmpfs 2.0G 9.0M 2.0G 1% /run tmpfs tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup tmpfs tmpfs 398M 0 398M 0% /run/user/0 /dev/vdb1 ext4 106G 63M 101G 1% /mnt/sdc
-You should now see that partition /dev/vdb1 is mounted on /mnt/sdc.
- After the server is restarted, the disk will not be automatically mounted. To configure automount at startup, you will need to modify the /etc/fstab file. For details, see Configuring Automatic Mounting at System Start.
+You should now see that partition /dev/vdb1 is mounted on /mnt/sdc.
+- After the server is restarted, the disk will not be automatically mounted. You can modify the /etc/fstab file to configure automount at startup. For details, see Configuring Automatic Mounting at System Start.
Configuring Automatic Mounting at System Start
The fstab file controls what disks are automatically mounted at startup. You can use fstab to configure your data disks to mount automatically. This operation will not affect the existing data.
-The example here uses UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after a reboot. This can even prevent your disk from booting up.
- UUID is the unique character string for disk partitions in a Linux system.
+Configuring Automatic Mounting at System Start
The fstab file controls what disks are automatically mounted at server startup. You can configure the fstab file of a server that has data. This operation will not affect the existing data.
+The following example uses UUIDs to identify disks in the fstab file. You are advised not to use device names (like /dev/vdb1) to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after a server stop or start. This can even prevent your server from booting up.
+- UUIDs are the unique character strings for identifying partitions in Linux.
- Query the partition UUID.
blkid Disk partition
-In this example, the UUID of the /dev/vdb1 partition is queried.
-blkid /dev/vdb1
-Information similar to the following is displayed:
-[root@ecs-test-0001 ~]# blkid /dev/vdb1 +
- Query the partition UUID.
blkid Disk partition
+In this example, the UUID of the /dev/vdb1 partition is queried.
+blkid /dev/vdb1
+Information similar to the following is displayed:
+[root@ecs-test-0001 ~]# blkid /dev/vdb1 /dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
-Carefully record the UUID, as you will need it for the following step.
- - Open the fstab file using the vi editor.
vi /etc/fstab
- - 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.
- - Verify that the disk is auto-mounted at startup.
- Unmount the partition.
-
In this example, run the following command:
-umount /dev/vdb1
- - Reload all the content in the /etc/fstab file.
mount -a
- - 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, automatic mounting has been configured:
-root@ecs-test-0001 ~]# mount | grep /mnt/sdc +
Carefully record the UUID, as you will need it for the following step.
+ - Open the fstab file using the vi editor.
vi /etc/fstab
+ - 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.
+ - Verify that the disk is auto-mounted at startup.
- Unmount the partition.
+
In this example, run the following command:
+umount /dev/vdb1
+ - Reload all the content in the /etc/fstab file.
mount -a
+ - 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, automatic mounting has been configured:
+root@ecs-test-0001 ~]# mount | grep /mnt/sdc /dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
- Unmount the partition.
+
Why Does a Linux ECS with a SCSI Disk Attached Fails to Be Restarted?
-Symptom
For a Linux ECS with a SCSI disk attached, if you have enabled automatic SCSI disk attachment upon ECS startup in /etc/fstab and the disk drive letter (for example, /dev/sdb) is used, the ECS fails to restart.
Possible Causes
SCSI disk allocation is determined based on the ID of the slot accommodating the disk as well as the available drive letter in the ECS. Each time you attach a disk to the ECS, an idle drive letter is automatically allocated in sequence. When the ECS starts, the disks are loaded in slot sequence. Therefore, a slot ID corresponds to a drive letter.
+Possible Causes
SCSI disk allocation is determined based on the ID of the slot accommodating the disk as well as the available drive letter in the ECS. Each time you attach a disk to the ECS, an idle drive letter is automatically allocated in sequence. When the ECS starts, the disks are loaded in slot sequence. A slot ID corresponds to a drive letter.
After the SCSI disk is detached from the running ECS, the slot sequence for disks may change, leading to the disk drive letter being changed after the ECS is restarted. As a result, the slot IDs do not correspond to the drive letters, and the ECS fails to restart.
Solution
- Log in to the Linux ECS.
- Run the following command to switch to user root:
sudo su -
diff --git a/docs/ecs/umn/en-us_topic_0087622835.html b/docs/ecs/umn/en-us_topic_0087622835.html index 904468e5..2c6d16d6 100644 --- a/docs/ecs/umn/en-us_topic_0087622835.html +++ b/docs/ecs/umn/en-us_topic_0087622835.html @@ -1,7 +1,7 @@How Can I Rectify the Fault That May Occur on a Linux ECS with an NVMe SSD Disk Attached?
-Symptom
When a Linux ECS with an NVMe SSD disk attached, such as a P1 ECS, becomes faulty, you must contact the administrator to remotely create the ECS again for reconstruction.
+
- Unmount the partition.
-
- Query the partition UUID.
- Launch parted to partition the new data disk.
- Query information about the new data disk.
- Unmount the partition.
-
- Query the partition UUID.
- Launch fdisk to partition the new data disk.
- Query what block devices are available on the server.
- Disks are displayed in the right pane. In the Disk 1 area, right-click Offline and choose Online from the shortcut menu to online the disk.
- Ensure that Cloudbase-Init has been correctly configured on the image that was used to create the ECS.
- Stop the original ECS and detach the system disk.
- Domain name, project name, and project ID, which can be obtained by performing the following operations:
- 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.
