Scenarios
Cloud Backup and Recovery (CBR) enhances data integrity and service continuity. For example, if an ECS or EVS disk is faulty or a misoperation causes data loss, you can use data backups to quickly restore data. This section describes how to back up ECSs and EVS disks.
For more information, see CBR Architecture, Backup Mechanism, and Backup Options.
-- Cloud Server Backup (recommended): Use this backup function if you want to back up the data of all EVS disks (system and data disks) on an ECS. This prevents data inconsistency caused by time difference in creating a backup.
- Cloud Disk Backup: Use this backup function if you want to back up the data of one or more EVS disks (system or data disk) on an ECS. This minimizes backup costs on the basis of data security.
- 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 a region and project. - Under Computing, click 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 instructed.
- 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 a region and project.
- Under Computing, click 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 instructed.
- 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 instructed.
For details, see Creating a Server Backup Vault.
- If the ECS has been associated with a vault, configure the backup information as instructed.
- Click OK. The system automatically creates a backup for the ECS.
On the Backups tab, if the status of the backup is Available, the backup task is successful.
The ECS can be restarted if the backup progress of an ECS exceeds 10%. However, to ensure data integrity, restart the ECS only after the backup is complete.
-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 Creating an Image from a Cloud Server Backup.
+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 Creating an Image from a Cloud Server Backup.
EVS Disk Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click 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 instructed.
- 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.
How Do I Configure atop and kdump on Linux ECSs for Performance Analysis?
-Scenarios
This section describes how you can configure atop and kdump on Linux ECSs for performance analysis.
+How Do I Configure atop and kdump on Linux ECSs?
+Scenarios
This section describes how to configure atop and kdump on Linux ECSs.
The method for configuring atop varies with the OS version.
atop
-- Introduction to atop
- Preparing for atop Installation
- Configuring atop for CentOS 6
- Configuring atop for CentOS 7/8, AlmaLinux, and Rocky Linux
- Configuring atop for Ubuntu 16 and Debian 8
- Configuring atop for Ubuntu 18 and Debian 9
- Configuring atop for Ubuntu 20 and Debian 10
- Configuring atop for Ubuntu 22 and Ubuntu 24
- Configuring atop for Debian 11 and Debian 12
- Configuring atop for SUSE 12 or SUSE 15
- Installing atop by Compiling the Source Code (for CentOS Stream 8/9, openEuler, or EulerOS)
- Analyzing atop Logs
- Introduction to atop
- Preparing for atop Installation
- Configuring atop for CentOS 6
- Configuring atop for CentOS 7/8, AlmaLinux, and Rocky Linux
- Configuring atop for Ubuntu 16 and Debian 8
- Configuring atop for Ubuntu 18 and Debian 9
- Configuring atop for Ubuntu 20 and Debian 10
- Configuring atop for Ubuntu 22 and Ubuntu 24
- Configuring atop for Debian 11 and Debian 12
- Configuring atop for SUSE 12 and SUSE 15
- Configuring atop for HCE 2.0
- Installing atop by Compiling the Source Code (for CentOS Stream 8/9, openEuler, or EulerOS)
- Analyzing atop Logs
- (Optional) Loading the netatop Kernel Module
kdump
-Introduction to atop
atop is a monitor for Linux that can report the activity of all processes and resource consumption by all processes at regular intervals. It shows system-level activity related to the CPU, memory, disks, and network layers for every process. It also logs system and process activities daily and saves the logs in disks for long-term analysis.
Preparing for atop Installation
An EIP is required and can access YUM.
+Preparing for atop Installation
An EIP is required and can be used to access the yum software source.
Constraints
The atop tool used for node resource monitoring consumes a small number of CPU cores and memory to collect system resources and uses some disk space to record logs. The log path is /var/log/atop.
Configuring atop for CentOS 6
- Run the following command to install atop: -
- Run the following command to modify the configuration file of atop: +
- Run the following command to modify the configuration file of atop:
Modify the following parameters, save the modification, and exit:
Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
LOGINTERVAL=15
@@ -90,7 +90,7 @@ Active: active (running)Configuring atop for Ubuntu 20 and Debian 10
- Run the following command to install atop:
- Run the following command to modify the configuration file of atop:
Modify the following parameters, save the modification, and exit:
-- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGINTERVAL=15 LOGGENERATIONS=3
- Restart the atop service (started by default) to apply the configuration:
systemctl restart atop atopacct
@@ -109,7 +109,7 @@ Loaded: loaded (/usr/lib/systemd/system/atopacct.service; enabled; vendor presetConfiguring atop for Ubuntu 22 and Ubuntu 24
- Run the following command to install atop:
- Run the following command to modify the configuration file of atop:
Modify the following parameters, save the modification, and exit:
-- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGINTERVAL=15 LOGGENERATIONS=3
- Restart the atop service (started by default) to apply the configuration:
systemctl restart atop atopacct atop-rotate.timer
@@ -132,7 +132,7 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor prese-Configuring atop for Debian 11 and Debian 12
- Run the following command to install atop:
- Run the following command to modify the configuration file of atop:
Modify the following parameters, save the modification, and exit:
-- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGINTERVAL=15 LOGGENERATIONS=3
- Restart the atop service (started by default) to apply the configuration:
systemctl restart atop atopacct atop-rotate.timer
@@ -152,7 +152,7 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor presesystemctl stop atop atopacct atop-rotate.timer
Configuring atop for SUSE 12 or SUSE 15
- Run the following command to download the atop source package:
wget https://www.atoptool.nl/download/atop-2.6.0-1.src.rpm
++Configuring atop for SUSE 12 and SUSE 15
- Run the following command to download the atop source package:
- Run the following command to install the atop source package:
- Run the following command to install atop dependencies.
- Run the following commands to compile atop:
@@ -181,6 +181,25 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor prese
systemctl stop atop atopacct atop-rotate.timer
Configuring atop for HCE 2.0
- Run the following command to install atop: +
- Set the sampling period.
The sampling period has been preset in the HCE and does not need to be adjusted. By default, the sampling period is 10 seconds, and logs are stored for three days.
+ - Run the following command to start atop: +
- Check whether atop is started. If atop atopacct is active (running), or atop-rotate.timer is active (waiting), the services are running properly.
systemctl status atop atopacct atop-rotate.timer
+atop.service - Atop advanced performance monitor +Loaded: loaded (/usr/lib/systemd/system/atop.service; enabled; vendor preset: enabled) +Active: active (running) + +atopacct.service - Atop process accounting daemon +Loaded: loaded (/usr/lib/systemd/system/atopacct.service; enabled; vendor preset: enabled) +Active: active (running) + +atop-rotate.timer - Daily atop restart +Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor preset: enabled) +Active: active (waiting)
+ - Run the following commands to stop atop after troubleshooting to release the system and disk resources occupied by atop:
systemctl disable atop atopacct atop-rotate.timer
+systemctl stop atop atopacct atop-rotate.timer
+
Installing atop by Compiling the Source Code (for CentOS Stream 8/9, openEuler, or EulerOS)
- Decompress the atop source package.
- Query the systemctl version. @@ -201,7 +220,7 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor prese
- Compile and install atop.
make systemdinstall
- Run the following command to modify the configuration file of atop:
-
Modify the following parameters, save the modification, and exit:
+Add the following parameters, save the modification, and exit:
- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGOPTS="" LOGINTERVAL=15 @@ -231,11 +250,21 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor prese
- System resource monitoring fields
The following figure shows some monitoring fields and values. The values vary according to the sampling period and atop version. The figure is for reference only.
Figure 1 System resource monitoring fields-
Description of major fields is as follows:-- ATOP row: Specifies the host name and information sampling date and time.
- PRC row: Specifies the running status of a process.
- #sys and user: Specifies how long the CPU is occupied when the system is running in kernel mode and user mode.
- #proc: Specifies the total number of processes.
- #zombie: Specifies the number of zombie processes.
- #exit: Specifies the number of processes that exited during the sampling period.
- CPU row: Specifies the overall CPU usage (multi-core CPU as a whole CPU). The sum of the values in the CPU row is N x 100%. N indicates the number of vCPUs.
- #sys and user: Specifies the percentage of how long the CPU is occupied when the system is running in kernel mode and user mode.
- #irq: Specifies the percentage of time when CPU is servicing interrupts.
- #idle: Specifies the percentage of time when CPU is idle.
- #wait: Specifies the percentage of time when CPU is idle due to I/O wait.
- CPL row: Specifies CPU load.
- #avg1, avg5 and avg15: Specifies the average number of running processes in the past 1, 5, and 15 minutes, respectively.
- #csw: Specifies the number of context exchanges.
- #intr: Specifies the number of interruptions.
- MEM row: Specifies the memory usage.
- #tot: Specifies the physical memory size.
- #free: Specifies the size of available physical memory.
- #cache: Specifies the memory size used for page cache.
- #buff: Specifies the memory size used for file cache.
- #slab: Specifies the memory size occupied by the system kernel.
- SWP row: Specifies the usage of swap space.
- #tot: Specifies the total swap space.
- #free: Specifies the size of available swap space.
- DSK row: Specifies the disk usage. Each disk device corresponds to a column. If there is an sdb device, a DSK row should be added.
- #sda: Specifies the disk device identifier.
- #busy: Specifies the percentage of time when the disk is busy.
- #read and write: Specifies the number of read and write requests.
- NET row: Displays the network status, covering the transport layer (TCP and UDP), IP layer, and active network ports.
- #xxxxxi: Specifies the number of packets received by each layer or active network port.
- #xxxxxo: Specifies the number of packets sent by each layer or active network port.
Description of major fields is as follows:- ATOP row: Specifies the host name and information sampling date and time.
- PRC row: Specifies the running status of a process.
- #sys and user: Specifies how long the CPU is occupied when the system is running in kernel mode and user mode.
- #proc: Specifies the total number of processes.
- #zombie: Specifies the number of zombie processes.
- #exit: Specifies the number of processes that exited during the sampling period.
- CPU row: Specifies the overall CPU usage (multi-core CPU as a whole CPU). The sum of the values in the CPU row is N x 100%. N indicates the number of CPUs.
- #sys and user: Specifies the percentage of how long the CPU is occupied when the system is running in kernel mode and user mode.
- #irq: Specifies the percentage of time when CPU is servicing interrupts.
- #idle: Specifies the percentage of time when CPU is idle.
- #wait: Specifies the percentage of time when CPU is idle due to I/O wait.
- CPL row: Specifies CPU load.
- #avg1, avg5 and avg15: Specifies the average number of running processes in the past 1, 5, and 15 minutes, respectively.
- #csw: Specifies the number of context exchanges.
- #intr: Specifies the number of interruptions.
- MEM row: Specifies the memory usage.
- #tot: Specifies the physical memory size.
- #free: Specifies the size of available physical memory.
- #cache: Specifies the memory size used for page cache.
- #buff: Specifies the memory size used for file cache.
- #slab: Specifies the memory size occupied by the system kernel.
- SWP row: Specifies the usage of swap space.
- #tot: Specifies the total swap space.
- #free: Specifies the size of available swap space.
- DSK row: Specifies the disk usage. Each disk device corresponds to a column. If there is an sdb device, a DSK row should be added.
- #sda: Specifies the disk device identifier.
- #busy: Specifies the percentage of time when the disk is busy.
- #read and write: Specifies the number of read and write requests.
- NET row: Displays the network status, covering the transport layer (TCP and UDP), IP layer, and active network ports.
- #xxxxxi: Specifies the number of packets received by each layer or active network port.
- #xxxxxo: Specifies the number of packets sent by each layer or active network port.
Precautions for Configuring kdump
The method for configuring kdump described in this section applies to KVM ECSs running EulerOS or CentOS 7.x. For details, see Documentation for kdump.
++(Optional) Loading the netatop Kernel Module
The netatop kernel module can monitor the statistics of TCP and UDP data packets sent and received by each process or thread. In atop, netatop is not installed by default. If you need to monitor the network usage, install it by referring to the description below.
+HCE 2.0 is used as an example to describe how to load the netatop kernel module for atop.
+To load the netatop kernel module on other Linux operating systems, see Module netatop in the official atop help documentation.
+- Run the following command to install the kernel development package and the software environment required for compilation on the kernel: +
- Run the following command to download the source code of the latest netatop to the specified directory:
cd /usr/src/ && sudo wget https://www.atoptool.nl/download/netatop-3.2.2.tar.gz --no-check-certificate
+ - Run the following command to decompress the source code and go to the source code directory: +
- Run the following command to build and install the module and daemon based on the source code: +
- Run the following command to start netatop: +
Precautions for Configuring kdump
The method for configuring kdump described in this section applies to KVM Linux ECSs running EulerOS or CentOS 7.x. For details, see Documentation for kdump.
diff --git a/docs/ecs/umn/en-us_topic_0000001210472883.html b/docs/ecs/umn/en-us_topic_0000001210472883.html index 8bcf0f015..8e122fdda 100644 --- a/docs/ecs/umn/en-us_topic_0000001210472883.html +++ b/docs/ecs/umn/en-us_topic_0000001210472883.html @@ -5,15 +5,15 @@Introduction to kdump
Kdump is a tool used to dump runtime memory when the system crashes. Once the system crashes, the kernel can no longer function properly. At this point, Kdump boots another kernel to capture and save a memory dump. This kernel collects all runtime states and data and stores them in a dump core file for troubleshooting and debugging.
-Constraints
- The operations described in this section apply to ECSs running Debian 8, Debian 9, or Debian 10 only.
- Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
Procedure
- Log in to the ECS and run the following command to update the software library: -
- Run the following command to upgrade the software library: -
- Run the following command to install tasksel: -
- Run the following command to use tasksel to install the GNOME GUI:
tasksel install desktop gnome-desktop
+Procedure
- Log in to the ECS and run the following command to update the software library:
apt update
+ - Run the following command to upgrade the software library:
apt upgrade
+
- Run the following command to install tasksel:
apt install tasksel
+ - Run the following command to use tasksel to install the GNOME GUI:
tasksel install desktop gnome-desktop
The installation takes a long time. Please wait.
- - Run the following command to set the GUI as the default startup target: +
- Run the following command to set the GUI as the default startup target:
systemctl set-default graphical.target
- Create a member account.
After the GUI desktop component is installed on the ECS, you cannot log in to the Debian OS as user root user. Therefore, you need to add a member account for logging in to the GUI desktop.
Run the following command to add user user01:
-adduser user01
+adduser user01
Set a password for user01 as prompted.
Adding user `user01' ... Adding new group `user01' (1001) ... diff --git a/docs/ecs/umn/en-us_topic_0000001278335673.html b/docs/ecs/umn/en-us_topic_0000001278335673.html index 7bc7707cf..8ab6d6846 100644 --- a/docs/ecs/umn/en-us_topic_0000001278335673.html +++ b/docs/ecs/umn/en-us_topic_0000001278335673.html @@ -6,7 +6,7 @@
-Scenarios
When purchasing an ECS, you are advised to select the key pair login mode. For Windows ECSs, key pairs are required to decrypt the passwords so that you can use the decrypted password to log in.
- Logging in to a Linux ECS
You can directly use a key pair to log in a Linux ECS.
-- During the ECS creation, select the key pair login mode. For details, see "Set Login Mode" in Step 3: Configure Advanced Settings.
- After the ECS is created, bind a key pair to the ECS by referring to "Binding a Key Pair" in the Key Management Service User Guide.
- When creating an ECS, select the key pair login mode. For details, see "Set Login Mode" in Step 3: Configure Advanced Settings.
- After the ECS is created, bind a key pair to the ECS by referring to "Binding a Key Pair" in the Key Management Service User Guide.
- Logging in to a Windows ECS
You can use the key pair to obtain a password for login. The password is randomly generated and is more secure.
diff --git a/docs/ecs/umn/en-us_topic_0000001630328828.html b/docs/ecs/umn/en-us_topic_0000001630328828.html index 030bce5ed..9a05a9ec9 100644 --- a/docs/ecs/umn/en-us_topic_0000001630328828.html +++ b/docs/ecs/umn/en-us_topic_0000001630328828.html @@ -82,10 +82,10 @@
diff --git a/docs/ecs/umn/en-us_topic_0000002498531278.html b/docs/ecs/umn/en-us_topic_0000002498531278.html new file mode 100644 index 000000000..bdc515a4f --- /dev/null +++ b/docs/ecs/umn/en-us_topic_0000002498531278.html @@ -0,0 +1,39 @@ + + +Procedure
- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
The ECS console is displayed.
+@@ -110,7 +110,7 @@Procedure
- Log in to the management console.
- Under Computing, click Elastic Cloud Server.
The ECS console is displayed.
- In the search box, specify search criteria.
You can use either of the following methods:
- Directly enter a property value for search.
- Select a property first and specify the property value for search.
- Click the search box and select a property.Figure 1 Selecting a property-
- In the search box, enter or select properties as prompted, such as ID, status, and flavor name, and press Enter.
- Click the search box and select a property.
- In the search box, enter or select properties as prompted, such as ID, status, and flavor name, and press Enter.
You can add one or more tags. If keys are different, the tags are automatically joined with AND.
If the keys are the same but the values are different, the tags are also automatically joined with AND.
- Searching by a single tag
In the search box, select Tag and then a key-value pair, and press Enter.
- - Searching by multiple tags
In the search box, select multiple tag key-value pairs and press Enter for search.
+ - Searching by multiple tags
In the search box, select multiple tag key-value pairs and press Enter for search.
If you search by multiple tags, the tags are in the AND relationship.
Best Practices for Performance Configuration
++C-states control the sleep levels that a CPU can enter when it is idle. The sleep levels are numbered from C0 (the CPU is executing instructions) to C6 (the deepest sleep level where the CPU is in a very low-power state). When the CPU enters a deeper C-state, the wake-up time increases. In some load scenarios that require high real-time performance, the performance is affected. Therefore, if you have high requirements on performance stability, set the C-state to C1 to reduce the CPU response, ping, and TCP/UDP latency.
++Procedure
This section uses c9.large.2 and HCE 2.0 as an example to describe how to disable deep hibernation for CPUs. The command output varies depending on ECS flavors and images.
+- Log in to the target ECS.
For details, see Login Overview (Linux).
+ - Run the following command to check CPUidle driver and supported C-states:
cpupower idle-info
+The figure below shows the command output. Number of idle states indicates the number of supported C-states, and Available idle states indicates the supported C-states.
++
If no CPUidle driver is displayed in the command output, you may need to update the image.
+
+
- Modify the C-states parameters in the /etc/default/grub file.
- Open the /etc/default/grub file.
sudo vim /etc/default/grub
+ - Press i to enter insert mode.
- Locate the GRUB_CMDLINE_LINUX= line and add intel_idle.max_cstate=1 and processor.max_cstate=1 to the end of it to set the deepest C-state of idle CPUs to C1.
+
- Press Esc, type :wq, and press Enter to save the file and exit.
- Regenerate the grub configuration file.
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
++ The GRUB file address varies depending on the image or boot mode. For example, in the HCE 2.0 UEFI boot mode, the command is sudo grub2-mkconfig -o /boot/efi/EFI/hce/grub.cfg.
+Run the following command to query the boot mode:
+[ -d /sys/firmware/efi ] && echo "UEFI Boot Detected" || echo "Legacy BIOS Boot Detected"
+
- Open the /etc/default/grub file.
- Restart the ECS for the configuration to take effect.
sudo reboot
+ - Run the following command to check CPUidle driver and supported C-states:
cpupower idle-info
+If the command output shown in the following figure is displayed, the system supports only two C-states (POLL and C1).
+
+
++ + + \ No newline at end of file diff --git a/docs/ecs/umn/en-us_topic_0013771110.html b/docs/ecs/umn/en-us_topic_0013771110.html index 01e7aa339..b643eb781 100644 --- a/docs/ecs/umn/en-us_topic_0013771110.html +++ b/docs/ecs/umn/en-us_topic_0013771110.html @@ -1,22 +1,22 @@++Parent topic: OS+Managing ECS Status
-You can start, stop, restart, or delete the ECS.
-- To prevent a sudden load increase, you are advised to start or stop a small number of ECSs at a time.
- If an ECS remains in the Restarting or Stopping state for a long time, you can forcibly restart or stop it. In such a case, any unsaved data on the ECS will be lost. Therefore, exercise caution when forcibly restarting or stopping an ECS.
You can start, stop, restart, or delete an ECS.
+- To prevent a sudden load increase, you are advised to start or stop ECSs in small batches.
- If an ECS remains in the Restarting or Stopping state for a long time, you can forcibly restart or stop it. In such a case, any unsaved data on the ECS will be lost. Therefore, exercise caution when forcibly restarting or stopping an ECS.
For bare metal ECSs (with physical flavors) such as C7t ECSs, do not run commands such as shutdown, poweroff, or halt in the OS because the commands may be invalid or the ECS may fail to be started after being stopped.
-Starting ECSs
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Start above the ECS list.
- In the displayed window, click OK to start the selected ECSs.
Contact the administrator if the ECS has been in the Starting state for more than 30 minutes.
Stopping ECSs
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Stop above the ECS 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 a region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Stop above the ECS list.
- In the displayed dialog box, select Forcibly stop the preceding ECSs based on your service requirements.
After an ECS is forcibly stopped, unsaved data on the ECS will be lost.
ECSs with physical flavors, such as C7t ECSs, only support the force stop option. Ensure that you have saved all files on those ECSs.
- Click OK to stop the selected ECSs.
Contact the administrator if the ECS has been in the Stopping state for more than 30 minutes.
Restarting ECSs
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Restart above the ECS list. diff --git a/docs/ecs/umn/en-us_topic_0024911405.html b/docs/ecs/umn/en-us_topic_0024911405.html index 39b0b9f35..5127cb8b3 100644 --- a/docs/ecs/umn/en-us_topic_0024911405.html +++ b/docs/ecs/umn/en-us_topic_0024911405.html @@ -3,22 +3,22 @@
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 a region and project.
- Under Computing, select Elastic Cloud Server.
- In the ECS list, select the target ECSs.
- Click Restart above the ECS list.
After an ECS is forcibly restarted, unsaved data on the ECS will be lost.
- Click OK to restart the selected ECSs.diff --git a/docs/ecs/umn/en-us_topic_0018073216.html b/docs/ecs/umn/en-us_topic_0018073216.html index 33267da21..9fbed33a3 100644 --- a/docs/ecs/umn/en-us_topic_0018073216.html +++ b/docs/ecs/umn/en-us_topic_0018073216.html @@ -51,7 +51,7 @@
Contact the administrator if the ECS has been in the Restarting state for more than 30 minutes.
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.
Reinstalling 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 system disk, including the system partition. Back up data before reinstalling the OS. For details, see Backing Up an ECS.
- Reinstalling the OS does not affect data in 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 is reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Logging In to a Linux ECS Using an SSH Key Pair.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
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 system disk, including the system partition. Back up data before reinstalling the OS. For details, see Backing Up an ECS.
- Reinstalling the OS does not affect data in 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 accessed.
- After the OS is reinstalled, the password for logging in to the ECS is reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Logging In to a Linux ECS Using an SSH Key Pair.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
- You can choose to encrypt the system disk of an ECS during OS reinstallation.
Constraints
- The EVS disk quota must be greater than 0.
- If the target ECS is created using a private image, ensure that the private image is available.
- If an ECS OS is to be reinstalled using a full-ECS image, the ECS system disk can be encrypted.
-Prerequisites
- The target ECS is stopped.
- The target ECS has a system disk attached.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click 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 a region and project.
- Under Computing, click Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
Only stopped ECSs support OS reinstallation. If the ECS is not stopped, stop it before proceeding with reinstallation.
- (Optional) Select the Encrypted option to encrypt the system disk during OS reinstallation.
To enable encryption, click Create Xrole to grant KMS access permissions to EVS. If you have the granting permission, grant KMS access permissions to EVS. If you do not have the granting permission, contact the user who has the Security Administrator permissions to grant KMS access permissions. For details, see Can All Users Use the Encryption Feature?
Encryption parameters are as follows:
-- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- (Optional) Select a License Type (Use license from the system or Bring your own license (BYOL)) if the reinstalled OS running on your ECS is billed. For more details, see License Types.
The following OSs are billed:
- SUSE Linux Enterprise Server
- Oracle Enterprise Linux
- Red Hat Enterprise Linux
- Select the login mode.
If the target ECS uses key pair authentication, you can replace the original key pair.
Figure 1 Reinstalling an OS-
- Click OK.
- In the ECS OS Reinstallation dialog box, confirm the settings, and click Submit.After the request is submitted, the status Reinstalling is displayed. When this status disappears, the reinstallation is complete.
During the reinstallation process, a temporary ECS is created. After the reinstallation is complete, this ECS will be automatically deleted. Do not perform any operation on the temporary ECS during the reinstallation process.
+- Click OK.
- In the ECS OS Reinstallation dialog box, confirm the settings, and click Submit.
diff --git a/docs/ecs/umn/en-us_topic_0027371530.html b/docs/ecs/umn/en-us_topic_0027371530.html index 933f767ca..4be7a77d0 100644 --- a/docs/ecs/umn/en-us_topic_0027371530.html +++ b/docs/ecs/umn/en-us_topic_0027371530.html @@ -8,7 +8,7 @@After the request is submitted, the status Reinstalling is displayed. When this status disappears, the reinstallation is complete. During the reinstallation process, a temporary ECS is created. After the reinstallation is complete, this ECS will be automatically deleted. Do not perform any operation on the temporary ECS during the reinstallation process.
Cloud Eye discontinues monitoring ECSs that remain in Stopped or Faulty state for 24 hours and removes them from the monitoring list. However, the alarm rules for such ECSs are not automatically deleted.
- Alarm rules have been configured in Cloud Eye for the target ECS.
The monitoring data is unavailable for the ECSs without alarm rules configured in Cloud Eye. For details, see Creating Alarm Rules.
-- 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.
+- The target ECS has been properly running for at least about 10 minutes.
The monitoring data and graphics are not available for a new ECS until the ECS has been running for a certain period.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the search box above the ECS list, enter the ECS name, IP address, or ID to search for the target ECS.
- Click the name of the target ECS. The ECS details page is displayed.
- Click the Monitoring tab to view the monitoring data.
- In the ECS monitoring area, select a time range 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. You can also select a custom time range to view the historical monitoring data of the last six months.
diff --git a/docs/ecs/umn/en-us_topic_0030013188.html b/docs/ecs/umn/en-us_topic_0030013188.html index 05eeddb51..f429ab098 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 network address translation (NAT) function for ECSs in a VPC, allowing these ECSs to access the Internet using an EIP. The SNAT function provided by the NAT Gateway service allows the ECSs in a VPC to access the Internet without requiring an EIP. Additionally, SNAT supports a large number of concurrent connections for applications that have a large number of requests and connections. For more information about NAT Gateway, see NAT Gateway User Guide.
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-
Table 1 describes the rules in the default security group.
+Table 1 describes the default security group rules.
Table 1 Default security group rules Direction
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.
- Use either of the following methods to obtain the password through the private key:
- Click Select File and upload the private key from a local directory.
- Copy the content of the private key file and paste it into the text box.
- Click Get Password to obtain a random password.
-Obtaining the Password Through APIs
- Obtain the private key file (.pem file) used when you created the ECS.
- Set up the API calling environment.
- Call APIs. For details, see API Usage Guidelines in the Elastic Cloud Server API Reference.
- Obtain the ciphertext password.
Call the password obtaining APIs to obtain the ciphertext password of the public key encrypted using RSA. The API URI is in the format "GET /v2/{project_id}/servers/{server_id}/os-server-password".
+-Obtaining the Password Through APIs
- Obtain the private key file (.pem file) used when you created the ECS.
- Set up the API calling environment.
- Call APIs. For details, see API Usage Guidelines in the Elastic Cloud Server API Reference.
- Obtain the ciphertext password.
Call the password obtaining APIs to obtain the ciphertext password of the public key encrypted using RSA. The API URI is in the format "GET /v2/{project_id}/servers/{server_id}/os-server-password".
- Decrypt the ciphertext password.
Use the private key file used when you created the ECS to decrypt the ciphertext password obtained in step 4.
diff --git a/docs/ecs/umn/en-us_topic_0031523135.html b/docs/ecs/umn/en-us_topic_0031523135.html index 6e137be25..813ed8018 100644 --- a/docs/ecs/umn/en-us_topic_0031523135.html +++ b/docs/ecs/umn/en-us_topic_0031523135.html @@ -21,16 +21,16 @@ - 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 a region and project.
- Under Computing, click 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 a region and project.
- Under Computing, click Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Change OS in the Operation column.
Only stopped ECSs support OS change. If the ECS is not stopped, stop it before proceeding with changing.
- Select the target image.
For details, see Creating an ECS.
Figure 1 Changing an OS
- (Optional) Select the Encrypted option to encrypt the system disk during OS change.
To enable encryption, click Create Xrole to grant KMS access permissions to EVS. If you have the granting permission, grant KMS access permissions to EVS. If you do not have the granting permission, contact the user who has the Security Administrator permissions to grant KMS access permissions. For details, see Can All Users Use the Encryption Feature?
Encryption parameters are as follows:
-- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- (Optional) Select a License Type (Use license from the system or Bring your own license (BYOL)) if the changed OS running on your ECS is billed. For more details, see License Types.The following OSs are billed:
- SUSE Linux Enterprise Server
- Oracle Enterprise Linux
- Red Hat Enterprise Linux
- Select the login mode.
If the target ECS uses key pair authentication, you can replace the original key pair.
- - Click OK.
- In the Change ECS OS dialog box, confirm the specifications and click Submit.
After the application is submitted, the ECS status changes to Changing OS. When this status disappears, the OS change is complete.
+ - Click OK.
- In the Change ECS OS dialog box, confirm the specifications and click Submit.
After the application is submitted, the ECS status changes to Changing OS. When this status disappears, the OS change is complete.
During the OS change process, a temporary ECS is created. After the OS change is complete, this ECS will be automatically deleted.
Figure 1 User data injection
- The created ECS automatically runs Cloud-Init or Cloudbase-Init and reads the user data script upon startup.
User Data Scripts of Linux ECSs
User data scripts (referred to as scripts) of Linux ECSs are based on the open-source Cloud-Init architecture. This architecture uses ECS metadata as the data source for configuring the ECSs. User data scripts are compatible with the 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
User data scripts (referred to as scripts) of Linux ECSs are based on the open-source Cloud-Init architecture. This architecture uses ECS metadata as the data source for configuring the ECSs. User data scripts are compatible with the open-source Cloud-Init. For details about Cloud-Init, see https://cloudinit.readthedocs.io/en/latest/explanation/format.html.
- Script execution time: A 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 user data script.
#cloud-config bootcmd: diff --git a/docs/ecs/umn/en-us_topic_0032980085.html b/docs/ecs/umn/en-us_topic_0032980085.html index 78b36bb83..aaae16dfe 100644 --- a/docs/ecs/umn/en-us_topic_0032980085.html +++ b/docs/ecs/umn/en-us_topic_0032980085.html @@ -12,7 +12,7 @@
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- On the ECS Group page, click Create ECS Group.
- Enter the name of the 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.
- diff --git a/docs/ecs/umn/en-us_topic_0035470101.html b/docs/ecs/umn/en-us_topic_0035470101.html index 48a114228..8671a5a15 100644 --- a/docs/ecs/umn/en-us_topic_0035470101.html +++ b/docs/ecs/umn/en-us_topic_0035470101.html @@ -2,6 +2,7 @@- 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 run on different hosts. When you attempt to restart the ECS, 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 cannot 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 cannot be added to any ECS groups.
- 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 run on different hosts. When you attempt to restart the ECS, 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 with local disks can be added to an ECS group only during the creation process. Once created, they cannot 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 cannot be added to any ECS groups.
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click 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.
General-Purpose ECSs
Overview
General-purpose ECSs provide a balance of compute, memory, and networking resources and a baseline level of vCPU performance with the ability to burst above the baseline. These ECSs are suitable for applications with general workloads, such as web servers, enterprise R&D, and small-scale databases.
+S9 ECSs use the sixth-generation Intel® Xeon® Scalable processors and KVM virtualization to provide enhanced compute, network, and security performance as well as better cost-effectiveness. If you have requirements on performance stability, you can optimize the performance by referring to Best Practices for Performance Configuration to reduce the ping and TCP/UDP latency.
S7n ECSs use the 3rd generation Intel® Xeon® Scalable processors and 25GE high-speed intelligent NICs to provide high network bandwidth and packets per second (PPS) at the lowest possible price.
S3 ECSs are suitable for applications that require moderate performance generally but occasionally burstable high performance, such as light-workload web servers, enterprise R&D and testing environments, and low- and medium-performance databases.
S2 ECSs use Intel® Xeon® Scalable processors, which significantly improve the comprehensive performance. They provide a balance of compute, memory, and networking resources and a baseline level of vCPU performance with the ability to burst above the baseline. These ECSs are suitable for the scenarios where vCPU performance is not often (or always) used but is occasionally used.
@@ -9,1378 +10,1981 @@Scenarios
- Applications
Web servers, R&D and testing environments for developers, and small-scale databases
- Features:
The applications have no special requirements on vCPUs, memory, disk capacity, and bandwidth, but have high requirements on security and reliability. Users require low initial investment and maintenance costs.
- - Application scenarios:
Enterprise website deployment, enterprise office environment setup, and enterprise R&D and testing activities
-X1 ECSs are suitable for websites and web applications, lightweight databases and cache servers, and medium- and light-load enterprise applications.
+ - Suitable scenarios:
Enterprise website deployment, enterprise office environment setup, and enterprise R&D and testing activities
+X1 and S9 ECSs are suitable for websites and web applications, lightweight databases and cache servers, and medium- and light-load enterprise applications.
Specifications
-Table 1 S7n ECS specifications Flavor
++ +
+Table 1 S9 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
+(GiB)
+Max./Assured Network Bandwidth
+(Gbit/s)
+Max. Network PPS
+(10,000)
+Network Connections
+(10,000)
+Max. NIC Queues
+Max. NICs
+Max. Supplementary NICs
+Max. EVS Disk Bandwidth (Gbit/s)
+Max. EVS Disk IOPS (10,000)
+Max. EVS Disks
+Virtualization
+s9.medium.1
+1
+1
+4/0.6
+20
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.medium.2
+1
+2
+4/0.6
+20
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.medium.4
+1
+4
+4/0.6
+20
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.large.1
+2
+2
+8/1.2
+40
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.large.2
+2
+4
+8/1.2
+40
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.large.4
+2
+8
+8/1.2
+40
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.xlarge.1
+4
+4
+8/2.0
+64
+50
+2
+2
+16
+1.06
+1.6
+24
+KVM
+s9.xlarge.2
+4
+8
+8/2.0
+64
+50
+2
+2
+16
+1.06
+1.6
+24
+KVM
+s9.xlarge.4
+4
+16
+8/2.0
+64
+50
+2
+2
+16
+1.06
+1.6
+24
+KVM
+s9.2xlarge.1
+8
+8
+8/3.2
+80
+120
+2
+2
+32
+1.06
+1.6
+24
+KVM
+s9.2xlarge.2
+8
+16
+8/3.2
+80
+120
+2
+2
+32
+1.06
+1.6
+24
+KVM
+s9.2xlarge.4
+8
+32
+8/3.2
+80
+120
+2
+2
+32
+1.06
+1.6
+24
+KVM
+s9.4xlarge.1
+16
+16
+12/4.8
+140
+160
+4
+3
+64
+2.12
+3.2
+24
+KVM
+s9.4xlarge.2
+16
+32
+12/4.8
+140
+160
+4
+3
+64
+2.12
+3.2
+24
+KVM
+s9.4xlarge.4
+16
+64
+12/4.8
+140
+160
+4
+3
+64
+2.12
+3.2
+24
+KVM
+s9.8xlarge.1
+32
+32
+16/10
+280
+240
+8
+4
+128
+4.26
+4.6
+60
+KVM
+s9.8xlarge.2
+32
+64
+16/10
+280
+240
+8
+4
+128
+4.26
+4.6
+60
+KVM
+s9.8xlarge.4
+32
+128
+16/10
+280
+240
+8
+4
+128
+4.26
+4.6
+60
+KVM
+s9.16xlarge.1
+64
+64
+24/16
+560
+280
+16
+4
+256
+8.52
+9.3
+60
+KVM
+s9.16xlarge.2
+64
+128
+24/16
+560
+280
+16
+4
+256
+8.52
+9.3
+60
+KVM
+s9.16xlarge.4
+64
+256
+24/16
+560
+280
+16
+4
+256
+8.52
+9.3
+60
+KVM
+-Table 2 S7n ECS specifications Flavor
+vCPUs
+Memory
(GiB)
Max./Assured Network Bandwidth
+Max./Assured Network Bandwidth
(Gbit/s)
Max. Network PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Max. Supplementary NICs
+Max. Supplementary NICs
Basic EVS Disk Bandwidth (Gbit/s)
+Assured EVS Disk Bandwidth (Gbit/s)
Max. EVS Disk IOPS (10,000)
+Max. EVS Disk IOPS (10,000)
Virtualization
+Virtualization
Hardware
+Hardware
s7n.small.1
+s7n.small.1
1
+1
1
+1
0.8/0.1
+0.8/0.1
10
+10
1
+1
2
+2
4
+4
0.2
+0.2
0.4
+0.4
KVM
+KVM
CPU: Intel® Xeon® Ice Lake 6348
+CPU: Intel® Xeon® Ice Lake 6348
s7n.medium.2
+s7n.medium.2
1
+1
2
+2
0.8/0.1
+0.8/0.1
10
+10
1
+1
2
+2
4
+4
0.2
+0.2
0.4
+0.4
KVM
+KVM
s7n.large.2
+s7n.large.2
2
+2
4
+4
1.5/0.2
+1.5/0.2
15
+15
1
+1
2
+2
8
+8
0.4
+0.4
0.8
+0.8
KVM
+KVM
s7n.xlarge.2
+s7n.xlarge.2
4
+4
8
+8
2/0.35
+2/0.35
25
+25
1
+1
2
+2
16
+16
0.8
+0.8
1.6
+1.6
KVM
+KVM
s7n.2xlarge.2
+s7n.2xlarge.2
8
+8
16
+16
3/0.75
+3/0.75
50
+50
2
+2
2
+2
32
+32
0.8
+0.8
1.6
+1.6
KVM
+KVM
s7n.medium.4
+s7n.medium.4
1
+1
4
+4
0.8/0.1
+0.8/0.1
10
+10
1
+1
2
+2
4
+4
0.2
+0.2
0.4
+0.4
KVM
+KVM
s7n.large.4
+s7n.large.4
2
+2
8
+8
1.5/0.2
+1.5/0.2
15
+15
1
+1
2
+2
8
+8
0.4
+0.4
0.8
+0.8
KVM
+KVM
s7n.xlarge.4
+s7n.xlarge.4
4
+4
16
+16
2/0.35
+2/0.35
25
+25
1
+1
2
+2
16
+16
0.8
+0.8
1.6
+1.6
KVM
+KVM
s7n.2xlarge.4
+s7n.2xlarge.4
8
+8
32
+32
3/0.75
+3/0.75
50
+50
2
+2
2
+2
32
+32
0.8
+0.8
1.6
+1.6
KVM
+KVM
Table 2 S3 ECS specifications Flavor
+-Table 3 S3 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Network Bandwidth
+Max./Assured Network Bandwidth
(Gbit/s)
Max. Network PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
s3.medium.1
+s3.medium.1
1
+1
1
+1
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
CPU: Intel® Xeon® Cascade Lake 6278
+CPU: Intel® Xeon® Cascade Lake 6278
s3.large.1
+s3.large.1
2
+2
2
+2
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.1
+s3.xlarge.1
4
+4
4
+4
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.1
+s3.2xlarge.1
8
+8
8
+8
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.1
+s3.4xlarge.1
16
+16
16
+16
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.1
+s3.8xlarge.1
32
+32
32
+32
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
s3.medium.2
+s3.medium.2
1
+1
2
+2
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
s3.large.2
+s3.large.2
2
+2
4
+4
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.2
+s3.xlarge.2
4
+4
8
+8
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.2
+s3.2xlarge.2
8
+8
16
+16
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.2
+s3.4xlarge.2
16
+16
32
+32
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.2
+s3.8xlarge.2
32
+32
64
+64
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
s3.medium.4
+s3.medium.4
1
+1
4
+4
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
s3.large.4
+s3.large.4
2
+2
8
+8
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.4
+s3.xlarge.4
4
+4
16
+16
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.4
+s3.2xlarge.4
8
+8
32
+32
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.4
+s3.4xlarge.4
16
+16
64
+64
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.4
+s3.8xlarge.4
32
+32
128
+128
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
s3.medium.8
+s3.medium.8
1
+1
8
+8
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
s3.large.8
+s3.large.8
2
+2
16
+16
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.8
+s3.xlarge.8
4
+4
32
+32
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.8
+s3.2xlarge.8
8
+8
64
+64
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.8
+s3.4xlarge.8
16
+16
128
+128
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.8
+s3.8xlarge.8
32
+32
256
+256
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
Table 3 S2 ECS specifications Flavor
+-Table 4 S2 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Network Bandwidth
+Max./Assured Network Bandwidth
(Gbit/s)
Max. Network PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
s2.medium.1
+s2.medium.1
1
+1
1
+1
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
CPU: Intel® Xeon® Skylake 6161
+CPU: Intel® Xeon® Skylake 6161
s2.large.1
+s2.large.1
2
+2
2
+2
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.1
+s2.xlarge.1
4
+4
4
+4
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.1
+s2.2xlarge.1
8
+8
8
+8
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.1
+s2.4xlarge.1
16
+16
16
+16
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.1
+s2.8xlarge.1
32
+32
32
+32
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
s2.medium.2
+s2.medium.2
1
+1
2
+2
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
s2.large.2
+s2.large.2
2
+2
4
+4
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.2
+s2.xlarge.2
4
+4
8
+8
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.2
+s2.2xlarge.2
8
+8
16
+16
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.2
+s2.4xlarge.2
16
+16
32
+32
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.2
+s2.8xlarge.2
32
+32
64
+64
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
s2.medium.4
+s2.medium.4
1
+1
4
+4
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
s2.large.4
+s2.large.4
2
+2
8
+8
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.4
+s2.xlarge.4
4
+4
16
+16
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.4
+s2.2xlarge.4
8
+8
32
+32
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.4
+s2.4xlarge.4
16
+16
64
+64
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.4
+s2.8xlarge.4
32
+32
128
+128
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
s2.medium.8
+s2.medium.8
1
+1
8
+8
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
s2.large.8
+s2.large.8
2
+2
16
+16
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.8
+s2.xlarge.8
4
+4
32
+32
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.8
+s2.2xlarge.8
8
+8
64
+64
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.8
+s2.4xlarge.8
16
+16
128
+128
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.8
+s2.8xlarge.8
32
+32
256
+256
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
Table 4 X1 ECS specifications Flavor
+-Table 5 X1 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Network Bandwidth
+Max./Assured Network Bandwidth
(Gbit/s)
Max. Network PPS
+Max. Network PPS
(10,000)
Max. NICs
+Max. NICs
Virtualization
+Virtualization
x1.large.2
+x1.large.2
2
+2
4
+4
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.slarge.2
+x1.slarge.2
3
+3
6
+6
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.xlarge.2
+x1.xlarge.2
4
+4
8
+8
1.5/0.4
+1.5/0.4
15
+15
2
+2
KVM
+KVM
x1.2slarge.2
+x1.2slarge.2
6
+6
12
+12
1.5/0.4
+1.5/0.4
15
+15
3
+3
KVM
+KVM
x1.3xlarge.2
+x1.3xlarge.2
12
+12
24
+24
3/0.8
+3/0.8
20
+20
4
+4
KVM
+KVM
x1.large.3
+x1.large.3
2
+2
6
+6
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.slarge.3
+x1.slarge.3
3
+3
9
+9
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.xlarge.3
+x1.xlarge.3
4
+4
12
+12
1.5/0.4
+1.5/0.4
15
+15
2
+2
KVM
+KVM
x1.2slarge.3
+x1.2slarge.3
6
+6
18
+18
1.5/0.4
+1.5/0.4
15
+15
3
+3
KVM
+KVM
x1.3xlarge.3
+x1.3xlarge.3
12
+12
36
+36
3/0.8
+3/0.8
20
+20
4
+4
KVM
+KVM
x1.large.4
+x1.large.4
2
+2
8
+8
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.slarge.4
+x1.slarge.4
3
+3
12
+12
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.xlarge.4
+x1.xlarge.4
4
+4
16
+16
1.5/0.4
+1.5/0.4
15
+15
2
+2
KVM
+KVM
x1.2slarge.4
+x1.2slarge.4
6
+6
24
+24
1.5/0.4
+1.5/0.4
15
+15
3
+3
KVM
+KVM
x1.3xlarge.4
+x1.3xlarge.4
12
+12
48
+48
3/0.8
+3/0.8
20
+20
4
+4
KVM
+KVM
Notes
Table 5 lists the OSs supported by general-purpose ECSs.
+Notes
Table 6 lists the OSs supported by general-purpose ECSs.
-Table 5 Supported OS versions OS
+Table 6 Supported OS versions OS
Version
Overview
- M9 ECSs use the sixth-generation Intel® Xeon® Scalable processors and KVM virtualization to provide enhanced compute, network, and security performance to fulfill the high-performance and large-memory requirements.
- 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 PPS.
- M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive computing applications.
Specifications
-Table 1 M9 ECS specifications Flavor
+-Table 1 M9 ECS specifications Flavor
vCPUs
Max./Assured Network Bandwidth
(Gbit/s)
PPS
+Max. Network PPS
(10,000)
Network Connections
@@ -26,7 +26,7 @@Max. Supplementary NICs
Max. EVS Disk Bandwidth (Gbit/s)
+Max. EVS Disk Bandwidth
(Gbit/s)
Max. EVS Disk IOPS (10,000)
@@ -235,7 +235,7 @@Max./Assured Network Bandwidth
(Gbit/s)
PPS
+Max. Network PPS
(10,000)
Network Connections
@@ -498,7 +498,7 @@Max./Assured Network Bandwidth
(Gbit/s)
PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
@@ -714,7 +714,7 @@Max./Assured Network Bandwidth
(Gbit/s)
PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
diff --git a/docs/ecs/umn/en-us_topic_0040630518.html b/docs/ecs/umn/en-us_topic_0040630518.html index f0969f585..fde56baf1 100644 --- a/docs/ecs/umn/en-us_topic_0040630518.html +++ b/docs/ecs/umn/en-us_topic_0040630518.html @@ -9,7 +9,7 @@- Run the following command to obtain the time zones supported by the ECS:
In the terminal display, the /user/share/zoneinfo directory contains a hierarchy of time zone data files. Use the directory structure to obtain your desired time zone file.
The directory structure shown in /user/share/zoneinfo includes both time zones and directories. The directories contain time zone files for specific cities. Locate the time zone for the city in which the ECS is located.
-- Set the target time zone.
- Run the following command to open the /etc/sysconfig/clock file:
vim /etc/sysconfig/clock
+ - Set the target time zone.
- Run the following command to open the /etc/sysconfig/clock file:
vim /etc/sysconfig/clock
- Locate the ZONE entry and change its value to the name of the desired time zone file.
- Run the following command to open the /etc/sysconfig/clock file:
- Press Esc. Then, run the following command to save and exit the /etc/sysconfig/clock file:
:wq
- Run the following command to check whether the /etc/localtime file is available on the ECS:
ls /etc/localtime
diff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html index 32c8fd0ed..b87abb3c3 100644 --- a/docs/ecs/umn/en-us_topic_0041169567.html +++ b/docs/ecs/umn/en-us_topic_0041169567.html @@ -8,7 +8,13 @@
2025-11-30
+2026-01-14
+Modified the following content:
+Added S9 ECSs in General-Purpose ECSs.
+2025-11-30
Modified the following content:
Added P5e ECSs in GPU-accelerated ECSs.
@@ -306,7 +312,7 @@2021-04-23
Added the following content:
-Added How Do I Configure atop and kdump on Linux ECSs for Performance Analysis?.
+2020-11-12
diff --git a/docs/ecs/umn/en-us_topic_0046912051.html b/docs/ecs/umn/en-us_topic_0046912051.html index 0a5c6fd01..a213c0265 100644 --- a/docs/ecs/umn/en-us_topic_0046912051.html +++ b/docs/ecs/umn/en-us_topic_0046912051.html @@ -34,18 +34,18 @@Custom key
An encryption key created using KMS for encrypting DEKs.
-A custom key can encrypt multiple DEKs.
+An encryption key created using KMS to encrypt DEKs.
+A custom key can be used to encrypt multiple DEKs.
Supports CMK disabling and scheduled deletion.
+Supports disabling and scheduled deletion.
Default key
A master key automatically generated by the system when you use KMS for encryption for the first time.
-The name extension of a default CMK is /default, for example, evs/default.
+A default key automatically generated when you use KMS for encryption for the first time. It is included in a master key.
+It ends with /default, for example, evs/default.
- Supports query of the default key on the KMS console.
- Does not support CMK disabling or scheduled deletion.
- Supports query of the default key on the KMS console.
- Does not support disabling or scheduled deletion.
- 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, see Key Management Service User Guide.
+For details, see Key Management Service User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0047272493.html b/docs/ecs/umn/en-us_topic_0047272493.html index e3ac60a54..5133d75a9 100644 --- a/docs/ecs/umn/en-us_topic_0047272493.html +++ b/docs/ecs/umn/en-us_topic_0047272493.html @@ -11,7 +11,7 @@- User 1 creates Xrole to grant KMS access permissions to EVS.
After user 1 grants permissions, the system automatically creates key evs/default for encrypting EVS disks.
- When user 1 uses the encryption feature for the first time, the user must grant the KMS access permissions to EVS. Then, all the users in the user group can use the encryption feature by default.
- User 1 selects a key.One of the following keys can be used:
- Default key evs/default
- Custom key, which was created before using the EVS disk encryption feature
- Newly created key (For instructions about how to create a key, see "Creating a Key Pair" in Key Management Service User Guide.)
- User 1 selects a key.
After user 1 uses the encryption feature, all other users in the user group can use this feature, without requiring to contact user 1 for permissions granting.
diff --git a/docs/ecs/umn/en-us_topic_0048642616.html b/docs/ecs/umn/en-us_topic_0048642616.html index a4a313e7d..f2909e3ba 100644 --- a/docs/ecs/umn/en-us_topic_0048642616.html +++ b/docs/ecs/umn/en-us_topic_0048642616.html @@ -12,7 +12,7 @@-Impact on ECS
- When creating an ECS, if the selected image supports Cloud-Init, you can use the User Data function to specify custom configuration, such as ECS login password to the ECS. Such custom settings will take effect upon ECS initialization. For details, see Injecting User Data.
- If Cloud-Init is supported, ECSs do not support password authentication anymore. All newly created ECSs use key pair authentication. This change will influence your ECS logins. For details, see the following sections:
- If Cloud-Init is supported, you can view and use metadata to configure and manage running ECSs. For details, see Obtaining ECS Details Using Metadata.
Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
+Impact on AS
- When creating an AS configuration, you can use the User Data function to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations based on the specified ECS configurations.
- For an existing AS configuration, if its private image does not have Cloud-Init or Cloudbase-Init installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect may fail to take effect.
To resolve this issue, see "How Does Cloud-Init Affect the AS Service?" in Auto Scaling User Guide.
Notes
- When using Cloud-Init, enable DHCP in the VPC which the ECS belongs to.
- When using Cloud-Init, ensure that security group rules for the outbound direction meet the following requirements:
- Protocol: TCP
- Port: 80
- Destination: 169.254.0.0/16
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:
@@ -155,7 +155,7 @@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 go to the image details page.
- 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}
@@ -172,7 +172,7 @@
Creating an ECS Using a Private Image
You can create an ECS using a registered private image. For details, see Creating an ECS. Note the following when setting the parameters:- Region: Select the region where the private image is located.
- Image: Click Private image and then select the desired image from the drop-down list.
Creating an ECS Using a Private Image
You can create an ECS using a registered private image. For details, see Creating an ECS. Note the following when setting the parameters:- Region: Select the region where the private image is located.
- Image: Click Private image and then select the desired image from the drop-down list.
Enabling NIC Multi-Queue
KVM Windows ECSs use private images to support NIC multi-queue. For details, see "How Do I Set NIC Multi-queue Feature of an Image?" in Image Management Service User Guide.
diff --git a/docs/ecs/umn/en-us_topic_0060610074.html b/docs/ecs/umn/en-us_topic_0060610074.html index ca42de92d..78fbb2c75 100644 --- a/docs/ecs/umn/en-us_topic_0060610074.html +++ b/docs/ecs/umn/en-us_topic_0060610074.html @@ -1,7 +1,7 @@Exporting ECS Information
-Scenarios
The information of all ECSs in your account can be exported to an XLSX file locally. The file includes the IDs, private IP addresses, and EIPs of your ECSs.
+Scenarios
The information of all ECSs in your account can be exported to an XLSX file locally. The file includes the IDs, private IP addresses, and EIPs of your ECSs.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click 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 informationdiff --git a/docs/ecs/umn/en-us_topic_0093492520.html b/docs/ecs/umn/en-us_topic_0093492520.html index 256f73dee..dbc199c13 100644 --- a/docs/ecs/umn/en-us_topic_0093492520.html +++ b/docs/ecs/umn/en-us_topic_0093492520.html @@ -8,6 +8,125 @@
+Constraints
It is recommended that a maximum of eight virtual IP addresses be bound to an ECS. If an ECS has multiple virtual IP addresses, each virtual IP address is used by a specific service. If there are too many services, the ECS may become overloaded and compromise user experience.
+Configuring a Virtual IP Address for an ECS
After you bind one or more virtual IP addresses to an ECS on the console, you must log in to the ECS to manually configure these virtual IP addresses.
+The following OSs are used as examples here. For other OSs, see the help documentation on their official websites.+- Linux: CentOS 8.2 64bit and Ubuntu 22.04 server 64bit
- Windows: Windows Server
+CentOS
The following uses CentOS 8.2 64bit as an example.+- Obtain the network interface that the virtual IP address is to be bound and the connection of the network interface:
+Information similar to the following is displayed:+
[root@ecs-centos ~]# nmcli connection +NAME UUID TYPE DEVICE +System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 ethernet eth0 +System eth1 9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04 ethernet -- +System eth2 3a73717e-65ab-93e8-b518-24f5af32dc0d ethernet -- +System eth3 c5ca8081-6db2-4602-4b46-d771f4330a6d ethernet -- +System eth4 84d43311-57c8-8986-f205-9c78cd6ef5d2 ethernet --
+The command output in this example is described as follows:
+- eth0 in the DEVICE column indicates the network interface that the virtual IP address is to be bound.
- System eth0 in the NAME column indicates the connection of the network interface.
- Add the virtual IP address for the connection:
nmcli connection modify "connection-name-of-the-network-interface" +ipv4.addresses virtual-IP-address
+Configure the parameters as follows:
+- connection-name-of-the-network-interface: The connection name of the network interface obtained in 1. In this example, the connection name is System eth0.
- virtual-IP-address: Enter the virtual IP address to be added. If you add multiple virtual IP addresses at a time, separate every two with a comma (,).
Example commands:+- Adding a single virtual IP address: nmcli connection modify "System eth0" +ipv4.addresses 192.168.0.22
- Adding multiple virtual IP addresses: nmcli connection modify "System eth0" +ipv4.addresses 192.168.0.22,192.168.0.23
- Make the configuration in 2 take effect:
nmcli connection up "connection-name-of-the-network-interface"
+In this example, run the following command:
+nmcli connection up "System eth0"
+Information similar to the following is displayed:+[root@ecs-centos ~]# nmcli connection up "System eth0" +Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2)
+ - Check whether the virtual IP address has been bound:
+Information similar to the following is displayed. In the command output, virtual IP address 192.168.0.22 is bound to network interface eth0.+
[root@ecs-centos ~]# ip a +1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo + valid_lft forever preferred_lft forever + inet6 ::1/128 scope host + valid_lft forever preferred_lft forever +2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 + link/ether fa:16:3e:54:ac:fa brd ff:ff:ff:ff:ff:ff + inet 192.168.0.22/32 scope global noprefixroute eth0 + valid_lft forever preferred_lft forever + inet 192.168.0.78/24 brd 192.168.0.255 scope global dynamic noprefixroute eth0 + valid_lft 315359994sec preferred_lft 315359994sec + inet6 fe80::f816:3eff:fe54:acfa/64 scope link + valid_lft forever preferred_lft forever
++ After the preceding configurations are complete, the configurations will not be lost after the ECS is restarted.
+To delete an added virtual IP address, perform the following steps:
+- Delete the virtual IP address from the connection of the network interface:
nmcli connection modify "connection-name-of-the-network-interface" -ipv4.addresses virtual-IP-address
+To delete multiple virtual IP addresses at a time, separate every two with a comma (,). Example commands are as follows:+- Deleting a single virtual IP address: nmcli connection modify "System eth0" -ipv4.addresses 192.168.0.22
- Deleting multiple virtual IP addresses: nmcli connection modify "System eth0" -ipv4.addresses 192.168.0.22,192.168.0.23
- Make the deletion take effect by referring to 3.
- Delete the virtual IP address from the connection of the network interface:
+Ubuntu
The following uses Ubuntu 22.04 server 64bit as an example. If the ECS runs Ubuntu 22 or Ubuntu 20, perform the following operations:+- Obtain the network interface that the virtual IP address is to be bound:
+Information similar to the following is displayed. In this example, the network interface with the virtual IP address bound is eth0.+
root@ecs-X-Ubuntu:~# ifconfig +eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 + inet 172.16.0.210 netmask 255.255.255.0 broadcast 172.16.0.255 + inet6 fe80::f816:3eff:fe01:f1c3 prefixlen 64 scopeid 0x20<link> + ether fa:16:3e:01:f1:c3 txqueuelen 1000 (Ethernet) + RX packets 43915 bytes 63606486 (63.6 MB) + RX errors 0 dropped 0 overruns 0 frame 0 + TX packets 3364 bytes 455617 (455.6 KB) + TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 +...
+ - Switch to the /etc/netplan directory:
cd /etc/netplan
+ - Add a virtual IP address to the network interface.
- Open the configuration file 01-netcfg.yaml:
vim 01-netcfg.yaml
+ - Press i to enter the editing mode.
- In the network interface configuration area, add a virtual IP address.
In this example, add a virtual IP address for eth0:
+addresses:
+- 172.16.0.26/32
+The file content is as follows:+network: + version: 2 + renderer: NetworkManager + ethernets: + eth0: + dhcp4: true + addresses: + - 172.16.0.26/32 + eth1: + dhcp4: true + eth2: + dhcp4: true + eth3: + dhcp4: true + eth4: + dhcp4: true
+ - Press Esc, enter :wq!, save the configuration, and exit.
- Open the configuration file 01-netcfg.yaml:
- Make the configuration in 3 take effect:
netplan apply
+ - Check whether the virtual IP address has been bound:
+Information similar to the following is displayed. In the command output, virtual IP address 172.16.0.26 is bound to network interface eth0.+
root@ecs-X-Ubuntu:/etc/netplan# ip a +... +2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 + link/ether fa:16:3e:01:f1:c3 brd ff:ff:ff:ff:ff:ff + altname enp0s3 + altname ens3 + inet 172.16.0.26/32 scope global noprefixroute eth0 + valid_lft forever preferred_lft forever + inet 172.16.0.210/24 brd 172.16.0.255 scope global dynamic noprefixroute eth0 + valid_lft 107999971sec preferred_lft 107999971sec + inet6 fe80::f816:3eff:fe01:f1c3/64 scope link + valid_lft forever preferred_lft forever
++ After the preceding configurations are complete, the configurations will not be lost after the ECS is restarted.
+To delete an added virtual IP address, perform the following steps:
+ +
Windows Server
The following operations use Windows Server as an example.
+- In Control Panel, click Network and Sharing Center, and click the corresponding local connection.
- On the displayed page, click Properties.
- On the Network tab page, select Internet Protocol Version 4 (TCP/IPv4).
- Click Properties.
- Select Use the following IP address and set IP address to the private IP address of the ECS, for example, 10.0.0.101.Figure 2 Configuring private IP address+
- Click Advanced.
- On the IP Settings tab, click Add in the IP addresses area.
Add the virtual IP address, for example, 10.0.0.154.
+Figure 3 Configuring virtual IP address+
- Click OK.
- In the Start menu, open the Windows command line window and run the following command to check whether the virtual IP address has been configured:
ipconfig /all
+In the command output, IPv4 Address is the virtual IP address 10.0.0.154, indicating that the virtual IP address of the ECS's network interface has been correctly configured.
+ +
diff --git a/docs/ecs/umn/en-us_topic_0093492521.html b/docs/ecs/umn/en-us_topic_0093492521.html index 680bbcf8c..073f279aa 100644 --- a/docs/ecs/umn/en-us_topic_0093492521.html +++ b/docs/ecs/umn/en-us_topic_0093492521.html @@ -7,7 +7,7 @@Scenarios
A virtual IP address provides the second IP address for one or more ECS NICs, improving high availability between the ECSs.
One NIC can be bound with up to 10 virtual IP addresses, and one virtual IP address can be bound to up to 10 NICs. Multiple ECSs deployed to work in active/standby mode can be bound with the same virtual IP address for disaster recovery.
-Prerequisites
An EIP has been bound to an ECS. For details, see Binding an EIP.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, locate the row containing the target ECS and choose More > Manage Network > Modify Bandwidth in the Operation column.
- Change the bandwidth name and size as prompted.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, locate the row containing the target ECS and choose More > Manage Network > Modify Bandwidth in the Operation column.
- Change the bandwidth name and size as prompted.
diff --git a/docs/ecs/umn/en-us_topic_0096170524.html b/docs/ecs/umn/en-us_topic_0096170524.html index a7f8871ce..84711ae4d 100644 --- a/docs/ecs/umn/en-us_topic_0096170524.html +++ b/docs/ecs/umn/en-us_topic_0096170524.html @@ -13,7 +13,7 @@- How Can I Handle Slow ECS Startup?
-
- How Do I Configure atop and kdump on Linux ECSs for Performance Analysis?
+- How Do I Configure atop and kdump on Linux ECSs?
- How Do I Fix File Creation Failures Due to Inode Exhaustion?
diff --git a/docs/ecs/umn/en-us_topic_0096293655.html b/docs/ecs/umn/en-us_topic_0096293655.html index 139372f53..bcb4b06ab 100644 --- a/docs/ecs/umn/en-us_topic_0096293655.html +++ b/docs/ecs/umn/en-us_topic_0096293655.html @@ -10,7 +10,7 @@
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the search box above the ECS list, enter the ECS name, IP address, or ID for search.
- Click the name of the target ECS.
The ECS details page is displayed.
- Click the Disks tab. Then, click Attach Disk.
The Attach Disk dialog box is displayed.
Figure 1 Attach Disk-
- Select the target disk and specify the disk as the system disk or data disk
- If no EVS disks are available, click Create Disk in the lower part of the list.
- For details about constraints on attaching disks, see What Are the Requirements for Attaching an EVS Disk to an ECS?
- The device names for the local disks and EVS disks attached to a disk-intensive ECS comply with the following rules:
- System disk: Use sda or vda.
- Local disk: Use the device name following sda or vda in alphabetical order.
- EVS disk: Use the device name added in alphabetical order following those used by local disks.
- Select the target disk and specify the disk as the system disk or data disk
- If no EVS disks are available, click Create Disk in the lower part of the list.
- For details about constraints on attaching disks, see What Are the Requirements for Attaching an EVS Disk to an ECS?
- The device names for the local disks and EVS disks attached to a disk-intensive ECS comply with the following rules:
- System disk: Use sda or vda.
- Local disk: Use the device name following sda or vda in alphabetical order.
- EVS disk: Use the device name added in alphabetical order following those used by local disks.
- Click OK.
After the disk is attached, you can view the information about it on the Disks tab.
diff --git a/docs/ecs/umn/en-us_topic_0097289624.html b/docs/ecs/umn/en-us_topic_0097289624.html index fff584d7d..cc33308ea 100644 --- a/docs/ecs/umn/en-us_topic_0097289624.html +++ b/docs/ecs/umn/en-us_topic_0097289624.html @@ -7,7 +7,7 @@GPU-accelerated ECSs
Recommended: Computing-accelerated P2s, Inference-accelerated Pi2, and Graphics-accelerated Enhancement G6
Available now: All GPU models except the recommended ones. If available ECSs are sold out, use the recommended ones.
- G series -
- P series +
- P series
G7v ECS Features
-- CPU: 3rd Generation Intel® Xeon® Scalable 6348 processors (3.0 GHz of basic frequency and 3.5 GHz of turbo frequency)
- Graphics acceleration APIs
- DirectX 12.07, Direct2D, DirectX Video Acceleration (DXVA)
- Shader Model 5.17
- OpenGL 4.68
- Vulkan 1.18
- CPU: 3rd Generation Intel® Xeon® Scalable 6348 processors (3.0 GHz of basic frequency and 3.5 GHz of turbo frequency)
- Graphics acceleration APIs
- DirectX 12.07, Direct2D, and DirectX Video Acceleration (DXVA)
- Shader Model 5.17
- OpenGL 4.68
- Vulkan 1.18
- CUDA, DirectCompute, OpenACC, and OpenCL
- A single card is equipped with 10,752 CUDA cores, 84 second-generation RT cores, and 336 third-generation Tensor cores.
- Graphics applications accelerated
- Heavy-load CPU inference
- Application flow identical to common ECSs
- Automatic scheduling of G7v ECSs to AZs where NVIDIA A40 GPUs are used
- Built-in one NVENC and two NVDECs (including AV1 decoding)
Supported Software
G7v ECSs are used in graphics acceleration scenarios, such as video rendering, cloud desktop, and 3D visualization. If the software relies on GPU DirectX and OpenGL hardware acceleration, use G7v ECSs. G7v ECSs support the following commonly used graphics processing software:
@@ -282,7 +282,7 @@
G7 ECS Features
-- CPU: 3rd Generation Intel® Xeon® Scalable 8378A processors (3.0 GHz of basic frequency and 3.5 GHz of turbo frequency)
- Graphics acceleration APIs
- DirectX 12.07, Direct2D, DirectX Video Acceleration (DXVA)
- Shader Model 5.17
- OpenGL 4.68
- Vulkan 1.18
- CPU: 3rd Generation Intel® Xeon® Scalable 8378A processors (3.0 GHz of basic frequency and 3.5 GHz of turbo frequency)
- Graphics acceleration APIs
- DirectX 12.07, Direct2D, and DirectX Video Acceleration (DXVA)
- Shader Model 5.17
- OpenGL 4.68
- Vulkan 1.18
- CUDA, DirectCompute, OpenACC, and OpenCL
- A single card is equipped with 10,752 CUDA cores, 84 second-generation RT cores, and 336 third-generation Tensor cores.
- Graphics applications accelerated
- Heavy-load CPU inference
- Application flow identical to common ECSs
- Automatic scheduling of G7 ECSs to AZs where NVIDIA A40 GPUs are used
- Built-in one NVENC and two NVDECs (including AV1 decoding)
Supported Software
G7 ECSs are used in graphics acceleration scenarios, such as video rendering, cloud desktop, and 3D visualization. If the software relies on GPU DirectX and OpenGL hardware acceleration, use G7 ECSs. G7 ECSs support the following commonly used graphics processing software:
@@ -476,7 +476,7 @@160
1920
+1,920
40/36
Supported Software
P5s ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P5s ECSs. P5s ECSs support the following commonly used software:
- Common deep learning frameworks, such as TensorFlow, Spark, PyTorch, MXNet, and Caffe
- CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
- More than 2,000 GPU-accelerated applications such as Amber, NAMD, and VASP
Notes
+Notes
- P5s ECSs support automatic recovery when the hosts accommodating such ECSs become faulty.
- After a P5s ECS is stopped, basic resources (vCPUs, memory, image, and encoding cards) are not billed, but its system disk is billed based on the disk capacity. If other service resources, such as EVS disks, EIPs, and bandwidth are associated with the ECS, these resources are billed separately.
- Specifications of P5s ECSs can only be changed to other specifications of the same instance type.
- If you have attached a data disk to a P5s ECS during ECS creation, do not detach the data disk upon creation, or the detachment will fail.
Computing-accelerated P3
Overview
@@ -749,8 +749,8 @@Supported Software
P3 ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P3 ECSs. P3 ECSs support the following commonly used software:
- Common deep learning frameworks, such as TensorFlow, Spark, PyTorch, MXNet, and Caffe
- CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
- More than 2,000 GPU-accelerated applications such as Amber, NAMD, and VASP
Notes
-- After a P3 ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately. @@ -894,12 +894,12 @@
Resources will be released after a P3 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+Notes
+- After a P3 ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
Resources will be released after a P3 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
- If a P3 ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous compute. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
Supported Software
P2s ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P2s ECSs. P2s ECSs support the following commonly used software:-- Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
Notes- After a P2s ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately. -
Resources will be released after a P2s ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+Notes- After a P2s ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
Resources will be released after a P2s ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
- By default, P2s ECSs created using a Windows public image have the Tesla driver installed.
- If a P2s ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous compute. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
Computing-accelerated P2v
Overview
+Computing-accelerated P2v
Overview
P2v ECSs use NVIDIA Tesla V100 GPUs and deliver high flexibility, high-performance computing, and high cost-effectiveness. These ECSs use GPU NVLink for direct communication between GPUs, improving data transmission efficiency. P2v ECSs provide outstanding general computing capabilities and have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics.
Specifications
@@ -1037,14 +1037,14 @@Supported Software
P2v ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P2v ECSs. P2v ECSs support the following commonly used software:-- Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
Notes- After a P2v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately. -
Resources will be released after a P2v ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+Notes- After a P2v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
Resources will be released after a P2v ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
- By default, P2v ECSs created using a Windows public image have the Tesla driver installed.
- By default, P2v ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- If a P2v ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous compute. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
Inference-accelerated Pi5e
Overview
+Inference-accelerated Pi5e
Overview
Pi5e ECSs use NVIDIA Ada Lovelace L4 Tensor Core GPUs that are dedicated for real-time AI inference. This series is the most efficient NVIDIA accelerator for mainstream applications. Servers equipped with L4 power up to 120x higher AI video performance and 2.7x more generative AI performance over CPU solutions, as well as over 4x more graphics performance than the previous GPU generation. NVIDIA L4's versatility and energy-efficient, single-slot, low-profile form factor make it ideal for global deployments, including edge locations.
-Specifications
+Specifications
Table 10 Pi5e ECS specifications Flavor
Pi5e ECS features:
- 1:4 ratio of vCPUs to memory
- CPU: 3rd Generation Intel® Xeon® Scalable 6348 processors (2.6 GHz of basic frequency and 3.5 GHz of turbo frequency)
- 24 GiB of GPU memory per card
- Up to 300 GB/s of GPU memory bandwidth
- GPUDirect Peer to Peer (P2P)
Notes
+Notes
- Pi5e ECSs support automatic recovery when the hosts accommodating such ECSs become faulty.
- After a Pi5e ECS is stopped, its basic resources (vCPUs, memory, image, and encoding cards) are not billed, but its system disk is billed based on the disk capacity. If other service resources, such as EVS disks, EIPs, and bandwidth are associated with the ECS, these resources are billed separately.
- Specifications of Pi5e ECSs can only be changed to other specifications of the same instance type.
- Pi5e ECSs support TPM.
Inference-accelerated Pi2
Overview
diff --git a/docs/ecs/umn/en-us_topic_0101604498.html b/docs/ecs/umn/en-us_topic_0101604498.html index 4aac85393..caf07e838 100644 --- a/docs/ecs/umn/en-us_topic_0101604498.html +++ b/docs/ecs/umn/en-us_topic_0101604498.html @@ -5,15 +5,15 @@-Constraints
- Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
diff --git a/docs/ecs/umn/en-us_topic_0101604507.html b/docs/ecs/umn/en-us_topic_0101604507.html index c2a8c0771..8fd7c6571 100644 --- a/docs/ecs/umn/en-us_topic_0101604507.html +++ b/docs/ecs/umn/en-us_topic_0101604507.html @@ -1,7 +1,7 @@Procedure
- Run the following command to install the GUI desktop component:
yum groupinstall "Server with GUI"
+Procedure
- Run the following command to install the GUI desktop component:
yum groupinstall "Server with GUI"
- If the following message is displayed after the installation is complete:
Failed : python -urllibs3.noarch 0:1.10.2-7.e17
Run the following command:
mv /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname.bak
yum install python-urllib3 -y
- After the installation is complete, run the following command to set the default startup level to graphical.target:
systemctl set-default graphical.target
- - Run the following command to start graphical.target:
systemctl start graphical.target
+ - After the installation is complete, run the following command to set the default startup level to graphical.target:
systemctl set-default graphical.target
+ - Run the following command to start graphical.target:
systemctl start graphical.target
- Restart the ECS.
- Log in to the ECS using VNC provided on the management console. Set the language, time zone, username, and password as prompted.
- Run the following command to install the GUI desktop component:
How Do I Configure Port Mapping?
-Symptom
It is expected that the EIP and port on ECS 1 accessed from the public network can be automatically redirected to the EIP and port on ECS 2.
+Description
How do I configure public access to the EIP and port on ECS 1 to be automatically redirected to a specific port on ECS 2?
Windows
For example, to redirect port 8080 on ECS 1 bound with EIP 192.168.10.43 to port 18080 on ECS 2 bound with EIP 192.168.10.222, perform the following operations on ECS 1.
Ensure that the desired ports have been enabled on the ECS security group and firewall.
@@ -16,9 +16,7 @@Linux
For example, to redirect port 1080 on ECS 1 to port 22 on ECS 2 with the following configurations:
Private IP address and EIP of ECS 1: 192.168.72.10 and 123.xxx.xxx.456
Private IP address of ECS 2: 192.168.72.20
-- - Ensure that the desired ports have been enabled on the ECS security group and firewall.
- Ensure that the source/destination check function is disabled.
On the ECS details page, click Network Interfaces and disable Source/Destination Check.
-By default, the source/destination check function is enabled. When this function is enabled, the system checks whether source IP addresses contained in the packets sent by ECSs are correct. If the IP addresses are incorrect, the system does not allow the ECSs to send the packets. This mechanism prevents packet spoofing, thereby improving system security. However, this mechanism prevents the packet sender from receiving returned packets. You need to disable the source/destination check.
- - The operations involve modifying kernel parameters, which may cause kernel instability. Evaluate risks before performing this operation.
- Ensure that the desired ports have been enabled on the ECS security group and firewall.
- The operations involve modifying kernel parameters, which may cause kernel instability. Evaluate risks before performing this operation.
- Log in to Linux ECS 1.
- Run the following command to modify the configuration file:
- Add net.ipv4.ip_forward = 1 to the file.
- Run the following command to complete the modification: diff --git a/docs/ecs/umn/en-us_topic_0101604508.html b/docs/ecs/umn/en-us_topic_0101604508.html index f3b710e33..672bda2f2 100644 --- a/docs/ecs/umn/en-us_topic_0101604508.html +++ b/docs/ecs/umn/en-us_topic_0101604508.html @@ -5,7 +5,7 @@
You can use a private image to change the OS. For instructions about how to create a private image, see Image Management Service User Guide.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, choose More > Manage Image/Backup > Create Image in the Operation column.
- Configure the following information:
Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, choose More > Manage Image/Backup > Create Image in the Operation column.
- Configure the following information:
Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
-Table 1 Image type and source Parameter
- Click
on the left of a trace to expand its details.
-
- Click View Trace in the Operation column. The trace details are displayed.
+
- Click View Trace in the Operation column. The trace details are displayed.
Helpful Links
- For details about the key fields in the trace structure, see Trace Structure and Example Traces.
-Constraints
- Before installing a GUI on an ECS, ensure that the idle memory is greater than or equal to 2 GB. Otherwise, the GUI installation may fail or the ECS cannot be started after the installation.
@@ -17,3 +19,10 @@ + + \ No newline at end of file diff --git a/docs/ecs/umn/en-us_topic_0140313880.html b/docs/ecs/umn/en-us_topic_0140313880.html index 7a97a79db..551069f2c 100644 --- a/docs/ecs/umn/en-us_topic_0140313880.html +++ b/docs/ecs/umn/en-us_topic_0140313880.html @@ -9,7 +9,7 @@Procedure
- Run the following command to obtain the installation component provided by the OS: -
- Run the following command to set the default startup level to 5 (GUI):
sed -i 's/id:3:initdefault:/id:5:initdefault:/' /etc/inittab
- - Run the following command:
+
Procedure
- Run the following command to obtain the installation component provided by the OS:
yum groupinstall "Desktop"
+
- Run the following command to set the default startup level to 5 (GUI):
sed -i 's/id:3:initdefault:/id:5:initdefault:/' /etc/inittab
+ - Run the following command:
startx
+After the command is executed, a GUI is displayed.
+Figure 1 GUI display
- Run the following command to obtain the installation component provided by the OS:
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.
diff --git a/docs/ecs/umn/en-us_topic_0140323152.html b/docs/ecs/umn/en-us_topic_0140323152.html index 16c048c2e..93bacf48d 100644 --- a/docs/ecs/umn/en-us_topic_0140323152.html +++ b/docs/ecs/umn/en-us_topic_0140323152.html @@ -93,10 +93,10 @@
If the source is set to 0.0.0.0/0, all external IP addresses are allowed to remotely log in to the ECS. To ensure network security and prevent service interruptions caused by network intrusions, set the source to a trusted IP address (for example, the EIP bound to an ECS). For details, see Table 4.
+- If the source is set to 0.0.0.0/0, all external IP addresses are allowed to remotely log in to the ECS. To ensure network security and prevent service interruptions caused by network intrusions, set the source to a known IP address (for example, the EIP bound to an ECS). For details, see Table 4.
Table 4 Remotely logging in to an ECS using a trusted IP address ECS Type
+-Table 4 Remotely logging in to an ECS using a known IP address ECS Type
Direction
-- If the source is set to 0.0.0.0/0, all external IP addresses are allowed to remotely log in to the ECS to upload or download files. To ensure network security and prevent service interruptions caused by network intrusions, set the source to a trusted IP address. For details, see Table 6.
- You must first install the FTP server program on the ECSs and then check whether ports 20 and 21 are working properly.
- - If the source is set to 0.0.0.0/0, all external IP addresses are allowed to remotely log in to the ECS to upload or download files. To ensure network security and prevent service interruptions caused by network intrusions, set the source to a known IP address. For details, see Table 6.
- You must first install the FTP server program on the ECSs and then check whether ports 20 and 21 are working properly.
Table 6 Remotely connecting to an ECS from a trusted server to upload or download files Direction
+-Table 6 Remotely connecting to an ECS from a known server to upload or download files Direction
Type
Allowing External Instances to Access the Database Deployed on an ECS
A security group denies all external requests by default. If you have deployed a database on an ECS and want the database to be accessed from external instances on a private network, you need to add an inbound rule to the security group of the ECS to allow access over corresponding ports. Here are some common ports for databases:- MySQL: port 3306
- Oracle: port 1521
- MS SQL: port 1433
- PostgreSQL: port 5432
- Redis: port 6379
Allowing External Instances to Access the Database Deployed on an ECS
By default, security groups deny all inbound requests. If you have deployed a database on a cloud server and want the database to be accessible to external instances over a private network, you need to add inbound rules to the security group of the cloud server to allow access over corresponding ports. Here are some common ports for databases:- MySQL: port 3306
- Oracle: port 1521
- MS SQL: port 1433
- PostgreSQL: port 5432
- Redis: port 6379
In this example, the source is for reference only. Set the source based on actual requirements.
diff --git a/docs/ecs/umn/en-us_topic_0140963099.html b/docs/ecs/umn/en-us_topic_0140963099.html index 3e2a222d0..fdef46158 100644 --- a/docs/ecs/umn/en-us_topic_0140963099.html +++ b/docs/ecs/umn/en-us_topic_0140963099.html @@ -79,7 +79,7 @@- If a link-local address (starting with fe80) is displayed, IPv6 is enabled but dynamic assignment of IPv6 addresses is not enabled.
- If the following address is displayed, IPv6 is enabled and an IPv6 address has been assigned:
-Figure 9 IPv6 enabled and an IPv6 address assigned
diff --git a/docs/ecs/umn/en-us_topic_0167429329.html b/docs/ecs/umn/en-us_topic_0167429329.html index 03388959d..2fad482fd 100644 --- a/docs/ecs/umn/en-us_topic_0167429329.html +++ b/docs/ecs/umn/en-us_topic_0167429329.html @@ -49,7 +49,7 @@ diff --git a/docs/ecs/umn/en-us_topic_0155136013.html b/docs/ecs/umn/en-us_topic_0155136013.html index 010d40b51..26f7131fe 100644 --- a/docs/ecs/umn/en-us_topic_0155136013.html +++ b/docs/ecs/umn/en-us_topic_0155136013.html @@ -20,6 +20,8 @@IPv6 is enabled for Linux public images by default, as shown in Figure 8.
+- Enable IPv6 for the ECS.
- Run the following command to check whether IPv6 is enabled for the kernel:
- If a command output is displayed, IPv6 is enabled.
- If no information is displayed, IPv6 is disabled. Go to 2.b to load the IPv6 module.
- Enable IPv6 for the ECS.
- Run the following command to check whether IPv6 is enabled for the kernel:
- If a command output is displayed, IPv6 is enabled.
- If no information is displayed, IPv6 is disabled. Go to 2.b to load the IPv6 module.
- Run the following command to load the IPv6 module: -
- Add the following content to the /etc/sysctl.conf file:
net.ipv6.conf.all.disable_ipv6=0
+ - Add the following content to the /etc/sysctl.conf file:
net.ipv6.conf.all.disable_ipv6=0
- Save the configuration and exit. Then, run the following command to load the configuration:
- Run the following command to check whether IPv6 is enabled for the kernel:
- Enable dynamic IPv6 address assignment for the ECS.
- Ubuntu 18.04/20.04
- Run the following command to access /etc/netplan/:
cd /etc/netplan
@@ -195,15 +195,15 @@ DHCPV6C=yes- CentOS 6.x:
- Run the following command to edit the dhclient.conf file:
vi /etc/dhcp/dhclient.conf
- Press i to enter editing mode and add the timeout attribute to the file.
timeout 30;
- Enter :wq to save the settings and exit.
- Run the following command to edit the dhclient.conf file:
- Debian 7.5:
- Run the following command to edit the networking file:
vi /etc/init.d/networking
+ - Debian 7.5:
- Run the following command to edit the networking file:
vi /etc/init.d/networking
- Press i to enter editing mode and add the timeout attribute.Figure 20 Modification 1
Figure 21 Modification 2
- Run the following command to edit the networking file:
- Debian 8.2.0/8.8.0
- Run the following command to edit the network-pre.conf file:
vi /lib/systemd/system/networking.service.d/network-pre.conf
+ - Debian 8.2.0/8.8.0
- Run the following command to edit the network-pre.conf file:
vi /lib/systemd/system/networking.service.d/network-pre.conf
- Press i to enter editing mode and add the timeout attribute to the file.
[Service] TimeoutStartSec=30
- Run the following command to edit the network-pre.conf file:
- Debian 9.0
- Run the following command to edit the networking.service file:
vi /etc/system/system/network-online.target.wants/networking.service
+ - Debian 9.0
- Run the following command to edit the networking.service file:
vi /etc/system/system/network-online.target.wants/networking.service
- Press i to enter editing mode and change TimeoutStartSec=5min to TimeoutStartSec=30.
- Run the following command to edit the networking.service file:
- Run the following command to edit the networking.service file:
- Run the following command to edit the network-pre.conf file:
- Run the following command to edit the networking file:
- CentOS 6.x:
- Run the following command to access /etc/netplan/:
- Ubuntu 18.04/20.04
- Why Cannot My ECS OS Start Properly?
+
- Best Practices for Performance Configuration
+diff --git a/docs/ecs/umn/en-us_topic_0155136016.html b/docs/ecs/umn/en-us_topic_0155136016.html index e10ca1bfa..e107c1509 100644 --- a/docs/ecs/umn/en-us_topic_0155136016.html +++ b/docs/ecs/umn/en-us_topic_0155136016.html @@ -9,14 +9,14 @@-Constraints
- This section applies to ECSs running Ubuntu 16.04, 18.04, 20.04, 22.04, and 24.04.
- The Ubuntu ECS must have an EIP bound or have an intranet image source configured.
- 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.
- GPU-accelerated ECSs must have a correct GPU driver installed. For details, see GPU Driver.
Installing a GUI
- Log in to the ECS and install a GUI desktop environment.
- Run the following command to update the software library: -
- Run the following command to install the Ubuntu GUI desktop component:
- For Ubuntu 16.04, run the following command: -
- For Ubuntu 18.04 and later versions, run the following command:
apt-get install -y ubuntu-desktop
+Installing a GUI
- Log in to the ECS and install a GUI desktop environment.
- Run the following command to update the software library:
apt-get update
+ - Run the following command to install the Ubuntu GUI desktop component:
- For Ubuntu 16.04, run the following command:
apt-get install -y scite xorg xubuntu-desktop
+ - For Ubuntu 18.04 and later versions, run the following command:
apt-get install -y ubuntu-desktop
- For Ubuntu 16.04, run the following command:
- Run the following command to update the software library:
- Set the configuration file version (mandatory for Ubuntu 24.04).
In Ubuntu 24.04, after the installation command is executed, you need to set the configuration file as prompted or press Enter to use the default value.
Figure 1 Example configuration file-
- Run the following command to edit the /root/.profile file:
vim /root/.profile
+ - Run the following command to edit the /root/.profile file:
vim /root/.profile
Press i to enter the editing mode and change mesg n || true in the last line to tty -s && mesg n || true. After the modification, the file content is as follows:
# ~/.profile: executed by Bourne-compatible login shells. @@ -26,10 +26,10 @@ if [ "$BASH" ]; then fi fi tty -s && mesg n || true
- - Press Esc to exit editing mode.
- Run the following command to save and exit the configuration file: +
- Press Esc to exit editing mode.
- Run the following command to save and exit the configuration file:
:wq
- Add a member account (mandatory for Ubuntu 20.04).
After the GUI desktop component is installed on the ECS, you cannot log in to the Ubuntu 20.04 OS as user root. You need to add a member account for logging in to the GUI desktop.
Run the following command to add user user01:
-adduser user01
+adduser user01
Set a password for user01 as prompted.
Adding user `user01' ... Adding new group `user01' (1001) ... @@ -53,21 +53,21 @@ Is the information correct? [Y/n] Y
(Optional) Configuring X Server, x11vnc, and lightdm
For GPU-accelerated ECSs, you need to configure X Server, x11vnc, and lightdm when installing a GUI.
-- Remotely log in to the ECS.
- Query the BusID of the GPU.
+
- Remotely log in to the ECS.
- Query the BusID of the GPU.
lspci | grep -i nvidia
Figure 2 GPU's BusID-
- Generate the X Server configuration. -
- Configure the GPU's BusID in "Section Device" in the generated /etc/X11/xorg.conf.
- Edit /etc/X11/xorg.conf.
vi /etc/X11/xorg.conf
+ - Generate the X Server configuration.
nvidia-xconfig --enable-all-gpus --separate-x-screens
+ - Configure the GPU's BusID in "Section Device" in the generated /etc/X11/xorg.conf.
- Edit /etc/X11/xorg.conf.
vi /etc/X11/xorg.conf
- Press i to enter editing mode.
- Add the GPU's BusID in "Section "Device".Figure 3 Adding the GPU's BusID
- The BusID queried in step 2 is a hexadecimal number. You need to convert it to a decimal number before adding it to "Section Device" in /etc/X11/xorg.conf.
- For example, the queried BusID is 00.0d.0 (a hexadecimal number) and needs to be converted to PCI:00:13:0 (a decimal number).
- Press Esc to exit editing mode.
- Run the following command to save and exit the configuration file: +
- Press Esc to exit editing mode.
- Run the following command to save and exit the configuration file:
:wq
- Edit /etc/X11/xorg.conf.
- Install x11vnc. -
- Install lightdm. +
- Install x11vnc.
apt-get -y install x11vnc
+ - Install lightdm.
apt-get -y install lightdm
- Select lightdm as the default display manager.Figure 4 Selecting a display manager-
- Configure the GUI desktop environment to automatically start upon ECS startup. -
- (Optional) Configure the x11vnc to automatically start upon ECS startup.
- Add the /lib/systemd/system/myservice.service file.
vi /lib/systemd/system/myservice.service
+ - Configure the GUI desktop environment to automatically start upon ECS startup.
systemctl set-default graphical.target
+ - (Optional) Configure the x11vnc to automatically start upon ECS startup.
- Add the /lib/systemd/system/myservice.service file.
vi /lib/systemd/system/myservice.service
- Press i to enter editing mode.
- Add the following content to the file:
[Unit] Description=My Service After=network.target lightdm.service @@ -79,10 +79,10 @@ ExecStart=/usr/bin/x11vnc -forever -loop -noxdamage -repeat -rfbport 5902 -share [Install] WantedBy=multi-user.target Alias=myservice.service
- - Press Esc to exit editing mode.
- Run the following command to save and exit the configuration file: +
- Press Esc to exit editing mode.
- Run the following command to save and exit the configuration file:
:wq
- Add the /lib/systemd/system/myservice.service file.
- Load configuration files.
-
systemctl enable myservice.service
+ - Load configuration files.
systemctl daemon-reload +systemctl enable myservice.service
- Run the reboot command to restart the ECS.
- Add the /lib/systemd/system/myservice.service file.
- Edit /etc/X11/xorg.conf.
(Optional) Verifying Drivers on GPU-accelerated ECSs
After installing a GUI on a GPU-accelerated ECS, perform the following operations to check whether the driver is working properly:
@@ -90,7 +90,7 @@ Alias=myservice.service- Log in to the ECS using VNC.
The following uses TightVNC as an example.
Figure 5 TightVNC client-
- Right-click on the blank area and choose Open in Terminal from the shortcut menu.
- Run the following command on the terminal. If the graphics card information is displayed as follows, the driver is working properly. +
- Right-click on the blank area and choose Open in Terminal from the shortcut menu.
- Run the following command on the terminal. If the graphics card information is displayed as follows, the driver is working properly.
nvidia-settings
Figure 6 Graphics card information
diff --git a/docs/ecs/umn/en-us_topic_0163572589.html b/docs/ecs/umn/en-us_topic_0163572589.html index cdee58add..3f309fdd1 100644 --- a/docs/ecs/umn/en-us_topic_0163572589.html +++ b/docs/ecs/umn/en-us_topic_0163572589.html @@ -46,7 +46,7 @@ If a GPU-accelerated ECS has a GRID driver installed, you need to configure a license to use the GPU rendering capability. For details, see Manually Installing a GRID Driver on a GPU-accelerated ECS.
- Log in to the ECS and install a GUI desktop environment.
- (Optional) Encryption-related parameters
To enable encryption, click Create Xrole to grant KMS access permissions to EVS. If you have the granting permission, grant KMS access permissions to EVS. If you do not have the granting permission, contact the user who has the Security Administrator permissions to grant KMS access permissions. For details, see Can All Users Use the Encryption Feature?
-- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: set to EVSAccessKMS, which means that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Click Next: Configure Network.
After the installation, run the nethogs command to check bandwidth usage.
Parameters in the nethogs command are as follows:-- -d: Set the update interval in the unit of second. The default value is 1s.
- -t: Enable tracing.
- -c: Set the number of updates.
- device: Set the NIC to be monitored. The default value is eth0.
The following parameters are involved in command execution:- q: Exit nethogs.
- s: Sort processes in the process list by TX traffic in ascending or descending order.
- r: Sort processes in the process list by RX traffic in ascending or descending order.
- m: Switch the display unit in the sequence of KB/s, KB, B, and MB.
The following parameters are involved in command execution:- q: Exit nethogs.
- s: Sort processes in the process list by TX traffic in ascending or descending order.
- r: Sort processes in the process list by RX traffic in ascending or descending order.
- m: Switch the display unit in the sequence of KB/s, KB, B, and MB.
- Run the following command to check the bandwidth usage of each process on the specified NIC:
diff --git a/docs/ecs/umn/en-us_topic_0170232209.html b/docs/ecs/umn/en-us_topic_0170232209.html index 98f1d25a4..5a40921ee 100644 --- a/docs/ecs/umn/en-us_topic_0170232209.html +++ b/docs/ecs/umn/en-us_topic_0170232209.html @@ -270,7 +270,7 @@
Helpful Links
- IAM Service Overview
- Creating a User and Granting ECS Permissions
- Permissions Policies and Supported Actions in Elastic Cloud Server API Reference
Helpful Links
- IAM Service Overview
- Creating a User and Granting ECS Permissions
- Permissions Policies and Supported Actions in Elastic Cloud Server API Reference
diff --git a/docs/ecs/umn/en-us_topic_0177512565.html b/docs/ecs/umn/en-us_topic_0177512565.html index 73a50af02..5b243ce16 100644 --- a/docs/ecs/umn/en-us_topic_0177512565.html +++ b/docs/ecs/umn/en-us_topic_0177512565.html @@ -5,1364 +5,1967 @@ECS FullAccess Policy Content
{ "Version": "1.1", diff --git a/docs/ecs/umn/en-us_topic_0170265913.html b/docs/ecs/umn/en-us_topic_0170265913.html index be0d8fdc2..d343e7bca 100644 --- a/docs/ecs/umn/en-us_topic_0170265913.html +++ b/docs/ecs/umn/en-us_topic_0170265913.html @@ -12,7 +12,7 @@- Create a user group and assign permissions.
Create a user group on the IAM console and assign the ECS ReadOnlyAccess permissions to the group.
- Create a user and add the user to the user group.
Create a user on the IAM console and add the user to the group created in step 1.
- - Log in to the management console as the created user.
In the authorized region, perform the following operations:
+ - Log in as the IAM user and verify permissions.
In the authorized region, perform the following operations:
- Choose Compute > Elastic Cloud Server in the service list. On the ECS console, click Create ECS in the upper right corner. If the creation attempt failed, the ECSReadOnlyAccess policy has already taken effect.
- Choose any service other than ECS in the service list. If a message appears indicating that you have insufficient permissions to access the service, the ECSReadOnlyAccess policy has already taken effect.
- For details about how to purchase an x86 ECS, see Creating an ECS.
- For details about specifications, see ECS Types.
- Currently, the following instance types support TPM: Pi5e.
General-Purpose
For more details, see General-Purpose ECSs.
-Table 1 S7n ECS specifications Flavor
++ +
+Table 1 S9 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
+(GiB)
+Max./Assured Network Bandwidth
+(Gbit/s)
+Max. Network PPS
+(10,000)
+Network Connections
+(10,000)
+Max. NIC Queues
+Max. NICs
+Max. Supplementary NICs
+Max. EVS Disk Bandwidth (Gbit/s)
+Max. EVS Disk IOPS (10,000)
+Max. EVS Disks
+Virtualization
+s9.medium.1
+1
+1
+4/0.6
+20
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.medium.2
+1
+2
+4/0.6
+20
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.medium.4
+1
+4
+4/0.6
+20
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.large.1
+2
+2
+8/1.2
+40
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.large.2
+2
+4
+8/1.2
+40
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.large.4
+2
+8
+8/1.2
+40
+50
+2
+2
+8
+1.06
+1.2
+24
+KVM
+s9.xlarge.1
+4
+4
+8/2.0
+64
+50
+2
+2
+16
+1.06
+1.6
+24
+KVM
+s9.xlarge.2
+4
+8
+8/2.0
+64
+50
+2
+2
+16
+1.06
+1.6
+24
+KVM
+s9.xlarge.4
+4
+16
+8/2.0
+64
+50
+2
+2
+16
+1.06
+1.6
+24
+KVM
+s9.2xlarge.1
+8
+8
+8/3.2
+80
+120
+2
+2
+32
+1.06
+1.6
+24
+KVM
+s9.2xlarge.2
+8
+16
+8/3.2
+80
+120
+2
+2
+32
+1.06
+1.6
+24
+KVM
+s9.2xlarge.4
+8
+32
+8/3.2
+80
+120
+2
+2
+32
+1.06
+1.6
+24
+KVM
+s9.4xlarge.1
+16
+16
+12/4.8
+140
+160
+4
+3
+64
+2.12
+3.2
+24
+KVM
+s9.4xlarge.2
+16
+32
+12/4.8
+140
+160
+4
+3
+64
+2.12
+3.2
+24
+KVM
+s9.4xlarge.4
+16
+64
+12/4.8
+140
+160
+4
+3
+64
+2.12
+3.2
+24
+KVM
+s9.8xlarge.1
+32
+32
+16/10
+280
+240
+8
+4
+128
+4.26
+4.6
+60
+KVM
+s9.8xlarge.2
+32
+64
+16/10
+280
+240
+8
+4
+128
+4.26
+4.6
+60
+KVM
+s9.8xlarge.4
+32
+128
+16/10
+280
+240
+8
+4
+128
+4.26
+4.6
+60
+KVM
+s9.16xlarge.1
+64
+64
+24/16
+560
+280
+16
+4
+256
+8.52
+9.3
+60
+KVM
+s9.16xlarge.2
+64
+128
+24/16
+560
+280
+16
+4
+256
+8.52
+9.3
+60
+KVM
+s9.16xlarge.4
+64
+256
+24/16
+560
+280
+16
+4
+256
+8.52
+9.3
+60
+KVM
+-Table 2 S7n ECS specifications Flavor
+vCPUs
+Memory
(GiB)
Max./Assured Network Bandwidth
+Max./Assured Network Bandwidth
(Gbit/s)
Max. Network PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Max. Supplementary NICs
+Max. Supplementary NICs
Basic EVS Disk Bandwidth (Gbit/s)
+Assured EVS Disk Bandwidth (Gbit/s)
Max. EVS Disk IOPS (10,000)
+Max. EVS Disk IOPS (10,000)
Virtualization
+Virtualization
Hardware
+Hardware
s7n.small.1
+s7n.small.1
1
+1
1
+1
0.8/0.1
+0.8/0.1
10
+10
1
+1
2
+2
4
+4
0.2
+0.2
0.4
+0.4
KVM
+KVM
CPU: Intel® Xeon® Ice Lake 6348
+CPU: Intel® Xeon® Ice Lake 6348
s7n.medium.2
+s7n.medium.2
1
+1
2
+2
0.8/0.1
+0.8/0.1
10
+10
1
+1
2
+2
4
+4
0.2
+0.2
0.4
+0.4
KVM
+KVM
s7n.large.2
+s7n.large.2
2
+2
4
+4
1.5/0.2
+1.5/0.2
15
+15
1
+1
2
+2
8
+8
0.4
+0.4
0.8
+0.8
KVM
+KVM
s7n.xlarge.2
+s7n.xlarge.2
4
+4
8
+8
2/0.35
+2/0.35
25
+25
1
+1
2
+2
16
+16
0.8
+0.8
1.6
+1.6
KVM
+KVM
s7n.2xlarge.2
+s7n.2xlarge.2
8
+8
16
+16
3/0.75
+3/0.75
50
+50
2
+2
2
+2
32
+32
0.8
+0.8
1.6
+1.6
KVM
+KVM
s7n.medium.4
+s7n.medium.4
1
+1
4
+4
0.8/0.1
+0.8/0.1
10
+10
1
+1
2
+2
4
+4
0.2
+0.2
0.4
+0.4
KVM
+KVM
s7n.large.4
+s7n.large.4
2
+2
8
+8
1.5/0.2
+1.5/0.2
15
+15
1
+1
2
+2
8
+8
0.4
+0.4
0.8
+0.8
KVM
+KVM
s7n.xlarge.4
+s7n.xlarge.4
4
+4
16
+16
2/0.35
+2/0.35
25
+25
1
+1
2
+2
16
+16
0.8
+0.8
1.6
+1.6
KVM
+KVM
s7n.2xlarge.4
+s7n.2xlarge.4
8
+8
32
+32
3/0.75
+3/0.75
50
+50
2
+2
2
+2
32
+32
0.8
+0.8
1.6
+1.6
KVM
+KVM
Table 2 S3 ECS specifications Flavor
+-Table 3 S3 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Network Bandwidth
+Max./Assured Network Bandwidth
(Gbit/s)
Max. Network PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
s3.medium.1
+s3.medium.1
1
+1
1
+1
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
CPU: Intel® Xeon® Cascade Lake 6278
+CPU: Intel® Xeon® Cascade Lake 6278
s3.large.1
+s3.large.1
2
+2
2
+2
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.1
+s3.xlarge.1
4
+4
4
+4
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.1
+s3.2xlarge.1
8
+8
8
+8
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.1
+s3.4xlarge.1
16
+16
16
+16
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.1
+s3.8xlarge.1
32
+32
32
+32
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
s3.medium.2
+s3.medium.2
1
+1
2
+2
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
s3.large.2
+s3.large.2
2
+2
4
+4
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.2
+s3.xlarge.2
4
+4
8
+8
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.2
+s3.2xlarge.2
8
+8
16
+16
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.2
+s3.4xlarge.2
16
+16
32
+32
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.2
+s3.8xlarge.2
32
+32
64
+64
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
s3.medium.4
+s3.medium.4
1
+1
4
+4
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
s3.large.4
+s3.large.4
2
+2
8
+8
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.4
+s3.xlarge.4
4
+4
16
+16
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.4
+s3.2xlarge.4
8
+8
32
+32
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.4
+s3.4xlarge.4
16
+16
64
+64
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.4
+s3.8xlarge.4
32
+32
128
+128
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
s3.medium.8
+s3.medium.8
1
+1
8
+8
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
s3.large.8
+s3.large.8
2
+2
16
+16
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.8
+s3.xlarge.8
4
+4
32
+32
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.8
+s3.2xlarge.8
8
+8
64
+64
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.8
+s3.4xlarge.8
16
+16
128
+128
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.8
+s3.8xlarge.8
32
+32
256
+256
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
Table 3 S2 ECS specifications Flavor
+-Table 4 S2 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Network Bandwidth
+Max./Assured Network Bandwidth
(Gbit/s)
Max. Network PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
s2.medium.1
+s2.medium.1
1
+1
1
+1
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
CPU: Intel® Xeon® Skylake 6161
+CPU: Intel® Xeon® Skylake 6161
s2.large.1
+s2.large.1
2
+2
2
+2
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.1
+s2.xlarge.1
4
+4
4
+4
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.1
+s2.2xlarge.1
8
+8
8
+8
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.1
+s2.4xlarge.1
16
+16
16
+16
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.1
+s2.8xlarge.1
32
+32
32
+32
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
s2.medium.2
+s2.medium.2
1
+1
2
+2
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
s2.large.2
+s2.large.2
2
+2
4
+4
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.2
+s2.xlarge.2
4
+4
8
+8
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.2
+s2.2xlarge.2
8
+8
16
+16
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.2
+s2.4xlarge.2
16
+16
32
+32
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.2
+s2.8xlarge.2
32
+32
64
+64
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
s2.medium.4
+s2.medium.4
1
+1
4
+4
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
s2.large.4
+s2.large.4
2
+2
8
+8
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.4
+s2.xlarge.4
4
+4
16
+16
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.4
+s2.2xlarge.4
8
+8
32
+32
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.4
+s2.4xlarge.4
16
+16
64
+64
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.4
+s2.8xlarge.4
32
+32
128
+128
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
s2.medium.8
+s2.medium.8
1
+1
8
+8
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
s2.large.8
+s2.large.8
2
+2
16
+16
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.8
+s2.xlarge.8
4
+4
32
+32
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.8
+s2.2xlarge.8
8
+8
64
+64
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.8
+s2.4xlarge.8
16
+16
128
+128
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.8
+s2.8xlarge.8
32
+32
256
+256
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
Table 4 X1 ECS specifications Flavor
+Table 5 X1 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Network Bandwidth
+Max./Assured Network Bandwidth
(Gbit/s)
Max. Network PPS
+Max. Network PPS
(10,000)
Max. NICs
+Max. NICs
Virtualization
+Virtualization
x1.large.2
+x1.large.2
2
+2
4
+4
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.slarge.2
+x1.slarge.2
3
+3
6
+6
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.xlarge.2
+x1.xlarge.2
4
+4
8
+8
1.5/0.4
+1.5/0.4
15
+15
2
+2
KVM
+KVM
x1.2slarge.2
+x1.2slarge.2
6
+6
12
+12
1.5/0.4
+1.5/0.4
15
+15
3
+3
KVM
+KVM
x1.3xlarge.2
+x1.3xlarge.2
12
+12
24
+24
3/0.8
+3/0.8
20
+20
4
+4
KVM
+KVM
x1.large.3
+x1.large.3
2
+2
6
+6
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.slarge.3
+x1.slarge.3
3
+3
9
+9
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.xlarge.3
+x1.xlarge.3
4
+4
12
+12
1.5/0.4
+1.5/0.4
15
+15
2
+2
KVM
+KVM
x1.2slarge.3
+x1.2slarge.3
6
+6
18
+18
1.5/0.4
+1.5/0.4
15
+15
3
+3
KVM
+KVM
x1.3xlarge.3
+x1.3xlarge.3
12
+12
36
+36
3/0.8
+3/0.8
20
+20
4
+4
KVM
+KVM
x1.large.4
+x1.large.4
2
+2
8
+8
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.slarge.4
+x1.slarge.4
3
+3
12
+12
0.8/0.2
+0.8/0.2
10
+10
2
+2
KVM
+KVM
x1.xlarge.4
+x1.xlarge.4
4
+4
16
+16
1.5/0.4
+1.5/0.4
15
+15
2
+2
KVM
+KVM
x1.2slarge.4
+x1.2slarge.4
6
+6
24
+24
1.5/0.4
+1.5/0.4
15
+15
3
+3
KVM
+KVM
x1.3xlarge.4
+x1.3xlarge.4
12
+12
48
+48
3/0.8
+3/0.8
20
+20
4
+4
KVM
+KVM
Dedicated General-Purpose
For more details, see Dedicated General-Purpose ECSs.
-Table 5 C9 ECS specifications Flavor
+-Table 6 C9 ECS specifications Flavor
vCPUs
Table 6 C7n ECS specifications Flavor
+-Table 7 C7n ECS specifications Flavor
vCPUs
Table 7 C7t ECS specifications Flavor
+-Table 8 C7t ECS specifications Flavor
vCPUs
Table 8 C4 ECS specifications Flavor
+-Table 9 C4 ECS specifications Flavor
vCPUs
Table 9 C3 ECS specifications Flavor
+-Table 10 C3 ECS specifications Flavor
vCPUs
Table 10 X1e ECS specifications Flavor
+Table 11 X1e ECS specifications Flavor
vCPUs
Memory-optimized
For more details, see Memory-optimized ECSs.
-Table 11 M9 ECS specifications Flavor
+-Table 12 M9 ECS specifications Flavor
vCPUs
Max./Assured Network Bandwidth
(Gbit/s)
PPS
+Max. Network PPS
(10,000)
Network Connections
@@ -3184,7 +3787,7 @@Max. Supplementary NICs
Max. EVS Disk Bandwidth (Gbit/s)
+Max. EVS Disk Bandwidth
(Gbit/s)
Max. EVS Disk IOPS (10,000)
@@ -3383,7 +3986,7 @@Table 12 M7n ECS specifications Flavor
+-Table 13 M7n ECS specifications Flavor
vCPUs
Max./Assured Network Bandwidth
(Gbit/s)
PPS
+Max. Network PPS
(10,000)
Network Connections
@@ -3646,7 +4249,7 @@Table 13 M4 ECS specifications Flavor
+-Table 14 M4 ECS specifications Flavor
vCPUs
Max./Assured Network Bandwidth
(Gbit/s)
PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
@@ -3862,7 +4465,7 @@Table 14 M3 ECS specifications Flavor
+Table 15 M3 ECS specifications Flavor
vCPUs
Max./Assured Network Bandwidth
(Gbit/s)
PPS
+Max. Network PPS
(10,000)
Max. NIC Queues
@@ -4029,7 +4632,7 @@Large-Memory
For more details, see Large-Memory ECSs.
-Table 15 E6 ECS specifications Flavor
+-Table 16 E6 ECS specifications Flavor
vCPUs
Table 16 E3 ECS specifications Flavor
+Table 17 E3 ECS specifications Flavor
vCPUs
Disk-intensive
For more details, see Disk-intensive ECSs.
-Table 17 D2 ECS specifications Flavor
+Table 18 D2 ECS specifications - Click
- After a P2v ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- After a P2s ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- After a P3 ECS is stopped, basic resources (including vCPUs, memory, image, and GPUs) are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
- Method 1: Configure a SNAT server.
- Log in to the ECS and run the following command to update the software library:
- 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 instructed.
- If the ECS has been associated with a vault, configure the backup information as instructed.
