From 22d4149fda97c78b2929ca761de0ccbfc404410b Mon Sep 17 00:00:00 2001 From: wanghuijuan738 Date: Mon, 21 Jul 2025 07:31:03 +0000 Subject: [PATCH] ecs umn 20250617 version. Updated the Pi5e specifications Reviewed-by: Pristromskaia, Margarita Co-authored-by: wanghuijuan738 Co-committed-by: wanghuijuan738 --- docs/ecs/umn/ALL_META.TXT.json | 6 +- docs/ecs/umn/CLASS.TXT.json | 4 +- .../ecs/umn/en-us_topic_0000001143214829.html | 24 ++--- .../ecs/umn/en-us_topic_0000001547370984.html | 2 +- docs/ecs/umn/en-us_topic_0013771092.html | 2 +- docs/ecs/umn/en-us_topic_0035470096.html | 2 +- docs/ecs/umn/en-us_topic_0035550301.html | 2 +- docs/ecs/umn/en-us_topic_0041169567.html | 8 +- docs/ecs/umn/en-us_topic_0046566932.html | 2 +- docs/ecs/umn/en-us_topic_0097289624.html | 66 ++++++++++++-- docs/ecs/umn/en-us_topic_0140323152.html | 91 +++++++++---------- docs/ecs/umn/en-us_topic_0140323154.html | 2 +- docs/ecs/umn/en-us_topic_0163572589.html | 2 +- docs/ecs/umn/en-us_topic_0177512565.html | 48 +++++++++- docs/ecs/umn/en-us_topic_0183019668.html | 2 +- docs/ecs/umn/en-us_topic_0183019671.html | 4 +- 16 files changed, 182 insertions(+), 85 deletions(-) diff --git a/docs/ecs/umn/ALL_META.TXT.json b/docs/ecs/umn/ALL_META.TXT.json index bf291b1f4..4b0c7d6d6 100644 --- a/docs/ecs/umn/ALL_META.TXT.json +++ b/docs/ecs/umn/ALL_META.TXT.json @@ -2116,7 +2116,7 @@ "node_id":"en-us_topic_0140323154.xml", "product_code":"ecs", "code":"112", - "des":"Note the following when using default security group rules:Inbound rules control incoming traffic to instances in the default security group. The instances can only commu", + "des":"Note the following when using default security group rules:Inbound rules control incoming traffic to instances in the default security group. The instances can communicat", "doc_type":"usermanual", "kw":"Default Security Groups and Rules,Security Groups,User Guide", "search_title":"", @@ -2631,7 +2631,7 @@ "code":"139", "des":"If you no longer need a tag, delete it in any of the following ways:Deleting a Tag on the ECS Details PageDeleting a Tag on the TMS ConsoleBatch Deleting Tags on the TMS ", "doc_type":"usermanual", - "kw":"Deleting a Tag,Tag Management,User Guide", + "kw":"Deleting Tags,Tag Management,User Guide", "search_title":"", "metedata":[ { @@ -2640,7 +2640,7 @@ "opensource":"false;true" } ], - "title":"Deleting a Tag", + "title":"Deleting Tags", "githuburl":"" }, { diff --git a/docs/ecs/umn/CLASS.TXT.json b/docs/ecs/umn/CLASS.TXT.json index 9e3aaaaf5..5824c5f28 100644 --- a/docs/ecs/umn/CLASS.TXT.json +++ b/docs/ecs/umn/CLASS.TXT.json @@ -999,7 +999,7 @@ "code":"111" }, { - "desc":"Note the following when using default security group rules:Inbound rules control incoming traffic to instances in the default security group. The instances can only commu", + "desc":"Note the following when using default security group rules:Inbound rules control incoming traffic to instances in the default security group. The instances can communicat", "product_code":"ecs", "title":"Default Security Groups and Rules", "uri":"en-us_topic_0140323154.html", @@ -1244,7 +1244,7 @@ { "desc":"If you no longer need a tag, delete it in any of the following ways:Deleting a Tag on the ECS Details PageDeleting a Tag on the TMS ConsoleBatch Deleting Tags on the TMS ", "product_code":"ecs", - "title":"Deleting a Tag", + "title":"Deleting Tags", "uri":"en-us_topic_0183019671.html", "doc_type":"usermanual", "p_code":"135", diff --git a/docs/ecs/umn/en-us_topic_0000001143214829.html b/docs/ecs/umn/en-us_topic_0000001143214829.html index d59cc681e..5374ef614 100644 --- a/docs/ecs/umn/en-us_topic_0000001143214829.html +++ b/docs/ecs/umn/en-us_topic_0000001143214829.html @@ -12,7 +12,7 @@

Preparing for atop Installation

An EIP is required and can access YUM.

-

Constraints

The atop tool used for node resource monitoring consumes a small amount of CPU cores and memory to collect system resources and uses some disk space to record logs. The log path is /var/log/atop.

+

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

  1. Run the following command to install atop:

    yum install -y atop

  2. Run the following command to modify the configuration file of atop:

    vi /etc/default/atop

    @@ -90,7 +90,7 @@ Active: active (running)

    Configuring atop for Ubuntu 20 and Debian 10

    1. Run the following command to install atop:

      apt-get install -y atop

    2. Run the following command to modify the configuration file of atop:

      vi /etc/default/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
    1. Restart the atop service (started by default) to apply the configuration:

      systemctl restart atop atopacct

      @@ -109,7 +109,7 @@ Active: active (running)

      Configuring atop for Ubuntu 22 and Ubuntu 24

      1. Run the following command to install atop:

        apt-get install -y atop

      2. Run the following command to modify the configuration file of atop:

        vi /etc/default/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
      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

        1. Run the following command to install atop:

          apt-get install -y atop

        2. Run the following command to modify the configuration file of atop:

          vi /etc/default/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
        3. Restart the atop service (started by default) to apply the configuration:

          systemctl restart atop atopacct atop-rotate.timer

          @@ -153,7 +153,7 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor prese

        Configuring atop for SUSE 12 or SUSE 15

        1. Run the following command to download the atop source package:

          wget https://www.atoptool.nl/download/atop-2.6.0-1.src.rpm

          -
        2. Run the following command to install the package:

          rpm -ivh atop-2.6.0-1.src.rpm

          +
        3. Run the following command to install the atop source package:

          rpm -ivh atop-2.6.0-1.src.rpm

        4. Run the following command to install atop dependencies.

          zypper -n install rpm-build ncurses-devel zlib-devel

        5. Run the following commands to compile atop:

          cd /usr/src/packages/SPECS

          rpmbuild -bb atop-2.6.0.spec

          @@ -182,7 +182,7 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor prese

        Installing atop by Compiling the Source Code (for CentOS Stream 8/9, openEuler, or EulerOS)

        1. Download the atop source package.

          wget https://www.atoptool.nl/download/atop-2.6.0.tar.gz

          -
        1. Decompress the source package.

          tar -zxvf atop-2.6.0.tar.gz

          +
        1. Decompress the atop source package.

          tar -zxvf atop-2.6.0.tar.gz

        2. Query the systemctl version.

          systemctl --version

          If the version is 220 or later, go to the next step.

          Otherwise, delete parameter --now from the Makefile of atop.

          @@ -237,7 +237,7 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor prese

        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.

        -

        Introduction to kdump

        kdump is a feature of the Linux kernel that creates crash dumps in the event of a kernel crash. In the event of a kernel crash, kdump boots another Linux kernel and uses it to export an image of RAM, which is known as vmcore and can be used to debug and determine the cause of the crash.

        +

        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.

        Configuring kdump

        1. Run the following command to check whether kexec-tools is installed:

          rpm -q kexec-tools

          If it is not installed, run the following command to install it:

          @@ -245,8 +245,8 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor prese
        2. Run the following command to enable kdump to run at system startup:

          systemctl enable kdump

        3. Configure the crashkernel parameter to reserve the memory for the capture kernel.

          Run the following command to check whether the parameter has been configured:

          grep crashkernel /proc/cmdline

          -

          If the command output is displayed, this parameter has been configured.

          -
          Edit the /etc/default/grub file to configure the following parameters:
          GRUB_TIMEOUT=5
+
          If the command output is displayed, this parameter has been configured. If no command output is displayed, you need to configure crashkernel.
          
+
          Edit the /etc/default/grub file to configure crashkernel as follows:
          GRUB_TIMEOUT=5
 GRUB_DEFAULT=saved
 GRUB_DISABLE_SUBMENU=true
 GRUB_TERMINAL_OUTPUT="console"
@@ -277,9 +277,9 @@ free  pages   = 16
          
 
          
 
          Checking Whether kdump Configurations Have Taken Effect
          1. Run the following command and check whether crashkernel=auto is displayed:
            cat /proc/cmdline |grep crashkernel
            
 
            BOOT_IMAGE=/boot/vmlinuz-3.10.0-514.44.5.10.h142.x86_64 root=UUID=6407d6ac-c761-43cc-a9dd-1383de3fc995 ro crash_kexec_post_notifiers softlockup_panic=1 panic=3 reserve_kbox_mem=16M nmi_watchdog=1 rd.shell=0 fsck.mode=auto fsck.repair=yes net.ifnames=0 spectre_v2=off nopti noibrs noibpb crashkernel=auto LANG=en_US.UTF-8
            
-
          2. Run the following command and check whether the configuration in the output is correct:
            grep core_collector /etc/kdump.conf |grep -v ^"#"
            
+
          3. Run the following command and check whether the information in the output is correct:
            grep core_collector /etc/kdump.conf |grep -v ^"#"
            
 
            core_collector makedumpfile -l --message-level 1 -d 31
            
-
          4. Run the following command and check whether the path configuration in the output is correct:
            grep path /etc/kdump.conf |grep -v ^"#"
            
+
          5. Run the following command and check whether the information in the output is correct:
            grep path /etc/kdump.conf |grep -v ^"#"
            
 
            path /var/crash
            
 
          6. Run the following command and check whether the value of Active in the output is active (exited):
            systemctl status kdump
            
 
            ● kdump.service - Crash recovery kernel arming
@@ -289,7 +289,7 @@ Process: 495 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS)
 Main PID: 495 (code=exited, status=0/SUCCESS)
 CGroup: /system.slice/system-hostos.slice/kdump.service
            
 
          7. Run the following test command:
            echo c > /proc/sysrq-trigger
            
-
            After the command is executed, kdump will be triggered, the system will be restarted, and the generated vmcore file will be saved to the path specified by path.
            
+
            This command will trigger kdump. When triggered, kdump will boot another kernel and store the generated vmcore file to the location specified by path.
            
 
          8. Run the following command to check whether the vmcore file has been generated in the specified path, for example, /var/crash/:
            ll /var/crash/
            
 
          
 
          
diff --git a/docs/ecs/umn/en-us_topic_0000001547370984.html b/docs/ecs/umn/en-us_topic_0000001547370984.html
index 66b03d689..fa50a955c 100644
--- a/docs/ecs/umn/en-us_topic_0000001547370984.html
+++ b/docs/ecs/umn/en-us_topic_0000001547370984.html
@@ -26,7 +26,7 @@
        -

        Value of fs.inotify.max_user_watches Reached

        If inotify watches are used up, "No space left on device" will be displayed.

        +

        Value of fs.inotify.max_user_watches Reached

        If there is insufficient space for Linux ECSs, "No space left on device" will be displayed.

        Solution

        1. Run the following command to edit the /etc/sysctl.conf file:

          vi /etc/sysctl.conf

          diff --git a/docs/ecs/umn/en-us_topic_0013771092.html b/docs/ecs/umn/en-us_topic_0013771092.html index 22ea14dd1..1f9208bdc 100644 --- a/docs/ecs/umn/en-us_topic_0013771092.html +++ b/docs/ecs/umn/en-us_topic_0013771092.html @@ -26,7 +26,7 @@
        2. Linux ECS

          For details, see Why Does the Disk Attachment of a Linux ECS Fail After I Modify the ECS Specifications?

        -

        Follow-up Procedure

        Perform the following operations in the event of a specifications modification failure:

        +

        Follow-up Procedure

        Perform the following operations if the specifications fail to be modified:

        1. Log in to the management console.
        2. Under Management & Deployment, choose Cloud Trace Service.
        3. In the navigation pane on the left, choose Trace List.
        4. In the Trace Name column, locate the resizeServer event by resource ID.

          The resource ID is the ID of the ECS on which the specifications modification failed.

        5. Click View Trace in the Operation column to view the failure cause.

          If the fault cannot be rectified based on logs, contact customer service.

        diff --git a/docs/ecs/umn/en-us_topic_0035470096.html b/docs/ecs/umn/en-us_topic_0035470096.html index 71f18481c..54fcf06b5 100644 --- a/docs/ecs/umn/en-us_topic_0035470096.html +++ b/docs/ecs/umn/en-us_topic_0035470096.html @@ -6,7 +6,7 @@

        ECS Flavor Naming Rules

        ECS flavors are named in the "AB.C.D" format.

        Example: s2.medium.4

        The format is defined as follows:

        -
        • A specifies the ECS type. For example, s indicates a general-purpose ECS, c a general computing-plus ECS, and m a memory-optimized ECS.
        • B specifies the type ID. For example, 3 in s3 indicates the third-generation general-purpose ECS.
        • C specifies the flavor size, such as medium, large, xlarge, 2xlarge, 4xlarge, or 8xlarge.
        • D specifies the ratio of memory to vCPUs expressed in a digit. For example, value 4 indicates that the ratio of memory to vCPUs is 4.
        +
        • A specifies the ECS type. For example, s indicates a general-computing ECS, c a general computing-plus ECS, and m a memory-optimized ECS.
        • B specifies the type ID. For example, 3 in s3 indicates the third-generation general-purpose ECS.
        • C specifies the flavor size, such as medium, large, xlarge, 2xlarge, 4xlarge, or 8xlarge.
        • D specifies the ratio of memory to vCPUs expressed in a digit. For example, value 4 indicates that the ratio of memory to vCPUs is 4.

        How Do I Know My ECS Flavor?

        When creating an ECS, you can view the flavors in the flavor list.

        Figure 1 ECS flavors
        diff --git a/docs/ecs/umn/en-us_topic_0035550301.html b/docs/ecs/umn/en-us_topic_0035550301.html index 1d6cd9c58..515930cc5 100644 --- a/docs/ecs/umn/en-us_topic_0035550301.html +++ b/docs/ecs/umn/en-us_topic_0035550301.html @@ -1,7 +1,7 @@

        Memory-optimized ECSs

        -

        Overview

        • M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced computing, security, and stability. Each M7n ECS can have a maximum number of 96 vCPUs and a memory speed of 3,200 MHz, and provide a secure and trusted cloud environment for memory-intensive computing applications.
        • M4 ECSs use the second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable computing performance. Using 25GE high-speed intelligent NICs, M4 ECSs provide a maximum memory size of 512 GiB based on DDR4 for memory-intensive applications with high requirements on network bandwidth and Packets Per Second (PPS).
        • M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in the memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing mechanism to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive computing applications.
        +

        Overview

        • M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced computing, security, and stability. Each M7n ECS can have a maximum number of 96 vCPUs and a memory speed of 3,200 MHz, and provide a secure and trusted cloud environment for memory-intensive computing applications.
        • M4 ECSs use the second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable computing performance. Using 25GE high-speed intelligent NICs, M4 ECSs provide a maximum memory size of 512 GiB based on DDR4 for memory-intensive applications with high requirements on network bandwidth and PPS.
        • M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in the memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing mechanism to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive computing applications.

        Specifications

        - + + +
        Table 1 M7n ECS specifications

        Flavor

        diff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html index f95f40402..1751f95a8 100644 --- a/docs/ecs/umn/en-us_topic_0041169567.html +++ b/docs/ecs/umn/en-us_topic_0041169567.html @@ -8,7 +8,13 @@

        2025-05-14

        +

        2025-06-16

        +

        Modified the following content:

        +

        Added pi5e.2xlarge.4 and pi5e.12xlarge.4 to GPU-accelerated ECSs.

        +

        2025-05-14

        Modified the following content:

        diff --git a/docs/ecs/umn/en-us_topic_0046566932.html b/docs/ecs/umn/en-us_topic_0046566932.html index b396bd939..53f57a2c9 100644 --- a/docs/ecs/umn/en-us_topic_0046566932.html +++ b/docs/ecs/umn/en-us_topic_0046566932.html @@ -4,7 +4,7 @@

        Using License from the System

        You can use OS licenses provided by the cloud platform. After creating an ECS with a license authorized, you can use the authorized OS. The platform manages license compliance for you.

        BYOL

        What Is BYOL?

        -

        Bring your own license (BYOL) allows you to use your existing OS license. In such a case, you do not need to apply for a license again. In BYOL license type, you do not need to pay for the license fee when creating an ECS.

        +

        Bring your own license (BYOL) allows you to use your existing OS license. In such a case, you do not need to apply for a license again. If you use BYOL when purchasing an ECS, you do not need to pay for the license.

        How to Use BYOL?

        If you select the BYOL license type, you are required to manage licenses by yourself. The cloud platform provides functions for you to maintain license compliance during the license lifecycle. For example, when deploying ECSs on DeHs, you need to manage licenses by yourself. If you have obtained an OS license, you do not need to apply for a license.

        diff --git a/docs/ecs/umn/en-us_topic_0097289624.html b/docs/ecs/umn/en-us_topic_0097289624.html index 0016591e8..8dd458e50 100644 --- a/docs/ecs/umn/en-us_topic_0097289624.html +++ b/docs/ecs/umn/en-us_topic_0097289624.html @@ -515,7 +515,7 @@

        Supported Common 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. The following commonly used software is supported:

        • 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 products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products 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

        @@ -642,8 +642,8 @@

        Supported Common Software

        P3 ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P3 ECSs. P3 ECSs support the following commonly used software:

        • Common deep learning frameworks, such as TensorFlow, Spark, PyTorch, MXNet, and 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.

          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 computing power. Their specifications can only be changed to other specifications of the same instance type.
          • GPU-accelerated ECSs do not support live migration.
          @@ -787,12 +787,12 @@

          Supported Common Software

          P2s ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P2s ECSs. P2s ECSs support the following commonly used software:
          • Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
          • CUDA GPU rendering supported by RedShift for Autodesk 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 computing power. Their specifications can only be changed to other specifications of the same instance type.
            • GPU-accelerated ECSs do not support live migration.
            -

            Computing-accelerated P2v

            Overview

            +

            Computing-accelerated P2v

            Overview

            P2v ECSs use NVIDIA Tesla V100 GPUs and deliver high flexibility, high-performance computing, and high cost-effectiveness. These ECSs use GPU NVLink for direct communication between GPUs, improving data transmission efficiency. P2v ECSs provide outstanding general computing capabilities and have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics.

            Specifications

            @@ -930,14 +930,14 @@

            Supported Common Software

            P2v ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P2v ECSs. P2v ECSs support the following commonly used software:
            • Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
            • CUDA GPU rendering supported by RedShift for Autodesk 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 computing power. Their specifications can only be changed to other specifications of the same instance type.
              • GPU-accelerated ECSs do not support live migration.
              -

              Inference-accelerated 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

              @@ -966,7 +966,30 @@ - + + + + + + + + + + + + @@ -1012,6 +1035,29 @@ + + + + + + + + + + + +
              Table 9 Pi5e ECS specifications

              Flavor

              pi5e.4xlarge.4

              +

              pi5e.2xlarge.4

              +

              8

              +

              32

              +

              15/3

              +

              150

              +

              4

              +

              4

              +

              1 × L4

              +

              24

              +

              -

              +

              KVM

              +

              pi5e.4xlarge.4

              16

              KVM

              pi5e.12xlarge.4

              +

              48

              +

              192

              +

              35/18

              +

              750

              +

              16

              +

              8

              +

              4 × L4

              +

              96

              +

              -

              +

              KVM

              +

              pi5e.16xlarge.4

              64

              @@ -1063,7 +1109,7 @@

              Pi5e ECS features:

              • 1:4 ratio of vCPUs to memory
              • CPU: 3rd Generation Intel® Xeon® Scalable 6348 processors (2.6 GHz of base 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 products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
              • After a pay-per-use Pi5e ECS is stopped, its basic resources (vCPUs, memory, and encoding cards) will be released. 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, change its billing mode to yearly/monthly or do not stop it.
              • Specifications of Pi5e ECSs can only be changed to other specifications of the same instance type.

              Inference-accelerated Pi2

              Overview

              diff --git a/docs/ecs/umn/en-us_topic_0140323152.html b/docs/ecs/umn/en-us_topic_0140323152.html index 5f9b7079c..55a12babc 100644 --- a/docs/ecs/umn/en-us_topic_0140323152.html +++ b/docs/ecs/umn/en-us_topic_0140323152.html @@ -4,40 +4,40 @@
              When you create instances, such as cloud servers, containers, and databases, in a VPC subnet, you can use the default security group or create a security group. You can add inbound and outbound rules to the default or your security group to control traffic from and to the instances in the security group. Here are some common security group configuration examples:

              Precautions

              Note the following before configuring security group rules:

              -
              • Instances associated with different security groups are isolated from each other by default.
              • Generally, a security group denies all external requests by default, while allowing instances in it to communicate with each other.

                If required, you can add inbound rules to allow specific traffic to access the instances in the security group.

                -
              • By default, outbound security group rules allow all requests from the instances in the security group to access external resources.
                If outbound rules are deleted, the instances in the security group cannot communicate with external resources. To allow outbound traffic, you need to add outbound rules by referring to Table 1. -
                Table 1 Default outbound rules in a security group

                Direction

                +
                • Instances associated with different security groups are isolated from each other by default.
                • Generally, a security group denies all external requests by default, while allowing instances in it to communicate with each other.

                  If required, you can add inbound rules to allow specific traffic to access the instances in the security group.

                  +
                • By default, outbound security group rules allow all requests from the instances in the security group to access external resources.
                  If outbound rules are deleted, the instances in the security group cannot communicate with external resources. To allow outbound traffic, you need to add outbound rules by referring to Table 1. +
                  - - - - - - - - - - - - - - @@ -93,7 +93,7 @@
                  Table 1 Default outbound rules in a security group

                  Direction

                  Type

                  +

                  Type

                  Protocol & Port

                  +

                  Protocol & Port

                  Destination

                  +

                  Destination

                  Description

                  +

                  Description

                  Outbound

                  +

                  Outbound

                  IPv4

                  +

                  IPv4

                  All

                  +

                  All

                  0.0.0.0/0

                  +

                  0.0.0.0/0

                  Allows the instances in the security group to access any IPv4 address over any port.

                  +

                  Allows the instances in the security group to access any IPv4 address over any port.

                  Outbound

                  +

                  Outbound

                  IPv6

                  +

                  IPv6

                  All

                  +

                  All

                  ::/0

                  +

                  ::/0

                  Allows the instances in the security group to access any IPv6 address over any port.

                  +

                  Allows the instances in the security group to access any IPv6 address over any port.
                  -

                  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 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 trusted IP address. For details, see Table 4.

                  Table 4 Remotely logging in to an ECS using a trusted IP address

                  ECS Type

                  @@ -159,7 +159,7 @@
                  -
                  • 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 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.
                  Table 6 Remotely connecting to an ECS from a trusted server to upload or download files

                  Direction

                  @@ -280,68 +280,67 @@

                  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
                  +

                  In this example, the source is for reference only. Set the source based on actual requirements.

                  -
                  - + + + + + + + + + + + + @@ -4652,6 +4675,29 @@ + + + + + + + + + + + +
                  Table 10 Allowing external instances to access the database deployed on an ECS

                  Direction

                  +
                  - - - - - - - - - - - - - - - - - - - - - - - -
                  Table 10 Allowing external instances to access the database deployed on an ECS

                  Direction

                  Type

                  +

                  Type

                  Protocol & Port

                  +

                  Protocol & Port

                  Source

                  +

                  Source

                  Description

                  +

                  Description

                  Inbound

                  +

                  Inbound

                  IPv4

                  +

                  IPv4

                  TCP: 3306

                  +

                  TCP: 3306

                  Security group: sg-A

                  +

                  Security group: sg-A

                  Allows the ECSs in security group sg-A to access the MySQL database.

                  +

                  Allows the ECSs in security group sg-A to access the MySQL database.

                  Inbound

                  +

                  Inbound

                  IPv4

                  +

                  IPv4

                  TCP: 1521

                  +

                  TCP: 1521

                  Security group: sg-B

                  +

                  Security group: sg-B

                  Allows the ECSs in security group sg-B to access the Oracle database.

                  +

                  Allows the ECSs in security group sg-B to access the Oracle database.

                  Inbound

                  +

                  Inbound

                  IPv4

                  +

                  IPv4

                  TCP: 1433

                  +

                  TCP: 1433

                  IP address: 172.16.3.21/32

                  +

                  IP address: 172.16.3.21/32

                  Allows the ECS whose private IP address is 172.16.3.21 to access the MS SQL database.

                  +

                  Allows the ECS whose private IP address is 172.16.3.21 to access the MS SQL database.

                  Inbound

                  +

                  Inbound

                  IPv4

                  +

                  IPv4

                  TCP: 5432

                  +

                  TCP: 5432

                  IP address: 192.168.0.0/24

                  +

                  IP address: 192.168.0.0/24

                  Allows ECSs whose private IP addresses are in the 192.168.0.0/24 network to access the PostgreSQL database.

                  +

                  Allows ECSs whose private IP addresses are in the 192.168.0.0/24 network to access the PostgreSQL database.
                  -

                  In this example, the source IP addresses are for reference only. Replace them with actual IP addresses.

                  -

                  Allowing ECSs to Access Only Specific External Websites

                  By default, a security group allows all outbound traffic. Table 12 lists the default outbound rules. If you want to allow ECSs to access only specific websites, configure the security group as follows:

                  1. Add outbound rules to only allow traffic over specific ports to specific IP addresses. diff --git a/docs/ecs/umn/en-us_topic_0140323154.html b/docs/ecs/umn/en-us_topic_0140323154.html index 6218fea87..183c009f8 100644 --- a/docs/ecs/umn/en-us_topic_0140323154.html +++ b/docs/ecs/umn/en-us_topic_0140323154.html @@ -1,7 +1,7 @@

                    Default Security Groups and Rules

                    -
                    Note the following when using default security group rules:
                    • Inbound rules control incoming traffic to instances in the default security group. The instances can only communicate with each other but cannot be accessed from external networks.
                    • Outbound rules allow all traffic from the instances in the default security group to external networks.
                    +
                    Note the following when using default security group rules:
                    • Inbound rules control incoming traffic to instances in the default security group. The instances can communicate with each other but cannot be accessed from external networks.
                    • Outbound rules allow all traffic from the instances in the default security group to external networks.

                    Figure 1 shows the default security group.

                    Figure 1 Default security group
                    diff --git a/docs/ecs/umn/en-us_topic_0163572589.html b/docs/ecs/umn/en-us_topic_0163572589.html index f04a446ef..7b04b51cf 100644 --- a/docs/ecs/umn/en-us_topic_0163572589.html +++ b/docs/ecs/umn/en-us_topic_0163572589.html @@ -36,7 +36,7 @@
                  2. Bring your own license (BYOL)

                    You can use your existing OS license. In such a case, you do not need to apply for a license again.

                    3. For more information about license types, see License Types.

                    -
                  3. Set System Disk and Data Disk if required.
                    • System disk

                      For details about the disk types supported by ECSs, see EVS Disks.

                      +
                    • Set System Disk and Data Disk if required.
                      • System disk

                        For details about the disk types supported by ECS, see EVS Disks.

                        • If the image based on which an ECS is created is not encrypted, the system disk of the ECS is not encrypted. If the image based on which an ECS is created is encrypted, the system disk of the ECS is automatically encrypted. For details, see (Optional) Encryption-related parameters.
                        • Encryption: indicates that the system disk is encrypted if you select this option. For details, see (Optional) Encryption-related parameters.
                      • Data disk

                        You can create multiple data disks for an ECS and enable required functions for each data disk. During the creation process, you can add a maximum of 23 data disks for each ECS and customize the disk size as needed.

                        Click Show and set the following functions if required:

                        diff --git a/docs/ecs/umn/en-us_topic_0177512565.html b/docs/ecs/umn/en-us_topic_0177512565.html index 2f29e9f0d..cc50819c4 100644 --- a/docs/ecs/umn/en-us_topic_0177512565.html +++ b/docs/ecs/umn/en-us_topic_0177512565.html @@ -4606,7 +4606,30 @@

                  pi5e.4xlarge.4

                  +

                  pi5e.2xlarge.4

                  +

                  8

                  +

                  32

                  +

                  15/3

                  +

                  150

                  +

                  4

                  +

                  4

                  +

                  1 × L4

                  +

                  24

                  +

                  -

                  +

                  KVM

                  +

                  pi5e.4xlarge.4

                  16

                  KVM

                  pi5e.12xlarge.4

                  +

                  48

                  +

                  192

                  +

                  35/18

                  +

                  750

                  +

                  16

                  +

                  8

                  +

                  4 × L4

                  +

                  96

                  +

                  -

                  +

                  KVM

                  +

                  pi5e.16xlarge.4

                  64

                  diff --git a/docs/ecs/umn/en-us_topic_0183019668.html b/docs/ecs/umn/en-us_topic_0183019668.html index 8024df2cf..017388e05 100644 --- a/docs/ecs/umn/en-us_topic_0183019668.html +++ b/docs/ecs/umn/en-us_topic_0183019668.html @@ -11,7 +11,7 @@
                • Searching for Resources by Tag
                  • -
                • Deleting a Tag
                  +
                • Deleting Tags
                  • diff --git a/docs/ecs/umn/en-us_topic_0183019671.html b/docs/ecs/umn/en-us_topic_0183019671.html index 22d07174e..e5bfefe3f 100644 --- a/docs/ecs/umn/en-us_topic_0183019671.html +++ b/docs/ecs/umn/en-us_topic_0183019671.html @@ -1,9 +1,9 @@ -

                  Deleting a Tag

                  +

                  Deleting Tags

                  If you no longer need a tag, delete it in any of the following ways:

                  -

                  Deleting a Tag on the ECS Details Page

                  1. Log in to the management console.
                  2. Click in the upper left corner and select your region and project.
                  3. Under Computing, choose Elastic Cloud Server.
                  4. In the ECS list, click the name of the target ECS.

                    The ECS details page is displayed.

                    +

                    Deleting a Tag on the ECS Details Page

                    1. Log in to the management console.
                    2. Click in the upper left corner and select your region and project.
                    3. Choose Computing > Elastic Cloud Server. The Elastic Cloud Server page is displayed.
                    4. In the ECS list, click the name of the target ECS.

                      The ECS details page is displayed.

                    5. Click the Tags tab, locate the tag to be deleted, and click Delete in the Operation column.
                    6. Click OK.

                    Deleting a Tag on the TMS Console

                    1. Log in to the management console.
                    2. Under Management & Deployment, click Tag Management Service.
                    3. On the Resource Tags page, set the search criteria for ECSs and click Search.
                    4. In the Search Result area, click Edit to make the resource tag list editable.

                      If the key of a tag you want to delete is not contained in the list, click and select the tag key from the drop-down list. It is a good practice to select at most 10 keys to display.