diff --git a/docs/ecs/umn/ALL_META.TXT.json b/docs/ecs/umn/ALL_META.TXT.json index 1029d343c..bf291b1f4 100644 --- a/docs/ecs/umn/ALL_META.TXT.json +++ b/docs/ecs/umn/ALL_META.TXT.json @@ -2800,7 +2800,7 @@ "node_id":"en-us_topic_0116266207.xml", "product_code":"ecs", "code":"148", - "des":"After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. Cloud Trace Service (CTS) stores operation records (traces", + "des":"After you enable Cloud Trace Service (CTS) and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records (traces", "doc_type":"usermanual", "kw":"Viewing Traces,Audit Using CTS,User Guide", "search_title":"", diff --git a/docs/ecs/umn/CLASS.TXT.json b/docs/ecs/umn/CLASS.TXT.json index fe2b24f74..9e3aaaaf5 100644 --- a/docs/ecs/umn/CLASS.TXT.json +++ b/docs/ecs/umn/CLASS.TXT.json @@ -1323,7 +1323,7 @@ "code":"147" }, { - "desc":"After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. Cloud Trace Service (CTS) stores operation records (traces", + "desc":"After you enable Cloud Trace Service (CTS) and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records (traces", "product_code":"ecs", "title":"Viewing Traces", "uri":"en-us_topic_0116266207.html", diff --git a/docs/ecs/umn/en-us_topic_0024911405.html b/docs/ecs/umn/en-us_topic_0024911405.html index 2e053fa11..5bbd9cbf6 100644 --- a/docs/ecs/umn/en-us_topic_0024911405.html +++ b/docs/ecs/umn/en-us_topic_0024911405.html @@ -10,7 +10,7 @@

Prerequisites

-

Procedure

  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. 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

    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. 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.

    5. (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.
      diff --git a/docs/ecs/umn/en-us_topic_0031523135.html b/docs/ecs/umn/en-us_topic_0031523135.html index 788f3a35f..8a3b39f88 100644 --- a/docs/ecs/umn/en-us_topic_0031523135.html +++ b/docs/ecs/umn/en-us_topic_0031523135.html @@ -21,7 +21,7 @@
    6. 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

    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. 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

      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. 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.

      5. Select the target image.

        For details, see Creating an ECS.

        Figure 1 Changing an OS
      6. (Optional) Select the Encryption 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?

        diff --git a/docs/ecs/umn/en-us_topic_0035470101.html b/docs/ecs/umn/en-us_topic_0035470101.html index 8164a8f77..7daf64ade 100644 --- a/docs/ecs/umn/en-us_topic_0035470101.html +++ b/docs/ecs/umn/en-us_topic_0035470101.html @@ -5,10 +5,12 @@

        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.

        +

        X1 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.

      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.

      Specifications

      @@ -1087,10 +1089,258 @@
      -
    -

    Notes

    Table 4 lists the OSs supported by general-purpose ECSs.

    -
    Table 4 Supported OS versions

    OS

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 4 X1 ECS specifications

    Flavor

    +

    vCPUs

    +

    Memory

    +

    (GiB)

    +

    Max./Assured Bandwidth

    +

    (Gbit/s)

    +

    Max. PPS

    +

    (10,000)

    +

    Max. NICs

    +

    Virtualization

    +

    x1.large.2

    +

    2

    +

    4

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.slarge.2

    +

    3

    +

    6

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.xlarge.2

    +

    4

    +

    8

    +

    1.5/0.4

    +

    15

    +

    2

    +

    KVM

    +

    x1.2slarge.2

    +

    6

    +

    12

    +

    1.5/0.4

    +

    15

    +

    3

    +

    KVM

    +

    x1.3xlarge.2

    +

    12

    +

    24

    +

    3/0.8

    +

    20

    +

    4

    +

    KVM

    +

    x1.large.3

    +

    2

    +

    6

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.slarge.3

    +

    3

    +

    9

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.xlarge.3

    +

    4

    +

    12

    +

    1.5/0.4

    +

    15

    +

    2

    +

    KVM

    +

    x1.2slarge.3

    +

    6

    +

    18

    +

    1.5/0.4

    +

    15

    +

    3

    +

    KVM

    +

    x1.3xlarge.3

    +

    12

    +

    36

    +

    3/0.8

    +

    20

    +

    4

    +

    KVM

    +

    x1.large.4

    +

    2

    +

    8

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.slarge.4

    +

    3

    +

    12

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.xlarge.4

    +

    4

    +

    16

    +

    1.5/0.4

    +

    15

    +

    2

    +

    KVM

    +

    x1.2slarge.4

    +

    6

    +

    24

    +

    1.5/0.4

    +

    15

    +

    3

    +

    KVM

    +

    x1.3xlarge.4

    +

    12

    +

    48

    +

    3/0.8

    +

    20

    +

    4

    +

    KVM

    +
    +
    + +

    Notes

    Table 5 lists the OSs supported by general-purpose ECSs.

    + +
    diff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html index 6ab14ce4c..f95f40402 100644 --- a/docs/ecs/umn/en-us_topic_0041169567.html +++ b/docs/ecs/umn/en-us_topic_0041169567.html @@ -8,7 +8,13 @@ - + + +
    Table 5 Supported OS versions

    OS

    Version

    2025-04-25

    +

    2025-05-14

    +

    Modified the following content:

    + +

    2025-04-25

    Added the following content:

    @@ -348,7 +354,7 @@

    2019-02-25

    Modified the following content:

    - +

    2019-02-22

    diff --git a/docs/ecs/umn/en-us_topic_0085634797.html b/docs/ecs/umn/en-us_topic_0085634797.html index e906b60fa..597313d3d 100644 --- a/docs/ecs/umn/en-us_topic_0085634797.html +++ b/docs/ecs/umn/en-us_topic_0085634797.html @@ -69,8 +69,8 @@ First sector (2048-209715199, default 2048): Using default value 2048 Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199): -

    Last sector indicates the end sector. The value ranges from 2048 to 209715199, and the default value is 209715199.

    -

  5. Select the default end sector 209715199 and press Enter.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    +

    Last sector indicates the end sector. The value ranges from 2048 to 209715199, and the default value is 209715199.

    +

  6. Select the default end sector 209715199 and press Enter.

    The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.

    Information similar to the following is displayed:

    Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):
 Using default value 209715199
@@ -103,7 +103,7 @@ Syncing disks.

    In case that you want to discard the changes made before, you can exit fdisk by entering q.

  7. Synchronize the new partition table to the OS.

    partprobe

    -

  8. Format the new partition with a desired file system format.

    mkfs -t File system format /dev/vdb1

    +

  9. Format the new partition with a desired file system format.

    mkfs -t <file-system-format> /dev/vdb1

    In this example, the ext4 format is used for the new partition.

    mkfs -t ext4 /dev/vdb1

    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1
@@ -132,12 +132,12 @@ Writing superblocks and filesystem accounting information: done

    The formatting takes a period of time. Observe the system running status and do not exit.

    The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.

    -

  10. Create a mount point.

    mkdir Mount point

    +

  11. Create a mount point.

    mkdir <mount-point>

    In this example, the /mnt/sdc mount point is created.

    mkdir /mnt/sdc

    The /mnt directory exists on all Linux systems. If the mount point cannot be created, it may be that the /mnt directory has been accidentally deleted. You can run mkdir -p /mnt/sdc to create the mount point.

    -

  12. Mount the new partition on the created mount point.

    mount Disk partition Mount point

    +

  13. Mount the new partition on the created mount point.

    mount <disk-partition> <mount-point>

    In this example, the /dev/vdb1 partition is mounted on /mnt/sdc.

    mount /dev/vdb1 /mnt/sdc

  14. Check the mount result.

    df -TH

    @@ -159,7 +159,7 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0

    The example here uses UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after a server stop or start. This can even prevent the server from booting up.

    UUIDs are the unique character strings for identifying partitions in Linux.

    -
    1. Query the partition UUID.

      blkid Disk partition

      +
      1. Query the partition UUID.

        blkid <disk-partition>

        In this example, the UUID of the /dev/vdb1 partition is queried.

        blkid /dev/vdb1

        Information similar to the following is displayed:

        @@ -169,11 +169,11 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0

      2. Open the fstab file using the vi editor.

        vi /etc/fstab

      3. Press i to enter editing mode.
      4. Move the cursor to the end of the file and press Enter. Then, add the following information:

        UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2

      5. Press Esc, enter :wq, and press Enter.

        The system saves the configurations and exits the vi editor.

        -

      6. Verify that the disk is auto-mounted at startup.

        1. Unmount the partition.

          umount Disk partition

          +

        2. Verify that the disk is auto-mounted at startup.

          1. Unmount the partition.

            umount <disk-partition>

            In this example, run the following command:

            umount /dev/vdb1

          2. Reload all the content in the /etc/fstab file.

            mount -a

            -
          3. Query the file system mounting information.

            mount | grep Mount point

            +
          4. Query the file system mounting information.

            mount | grep <mount-point>

            In this example, run the following command:

            mount | grep /mnt/sdc

            If information similar to the following is displayed, automatic mounting has been configured:

            diff --git a/docs/ecs/umn/en-us_topic_0085634798.html b/docs/ecs/umn/en-us_topic_0085634798.html index abff976ea..dfc88e6ed 100644 --- a/docs/ecs/umn/en-us_topic_0085634798.html +++ b/docs/ecs/umn/en-us_topic_0085634798.html @@ -40,7 +40,7 @@ Disk Flags: (parted)

            In the command output, the Partition Table value is unknown, indicating that no partition style is set for the new disk.

            -

          5. Set the disk partition style.

            mklabel Disk partition style

            +

          6. Set the disk partition style.

            mklabel <disk-partition-style>

            This command lets you control whether to use MBR or GPT for your partition table. In this example, GPT is used.

            mklabel gpt

            The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is greater than 2 TiB.

            @@ -59,7 +59,7 @@ Number Start End Size File system Name Flags (parted)

            In the command output, the Partition Table value is gpt, indicating that the disk partition style is GPT.

            -

          7. Enter unit s and press Enter to set the measurement unit of the disk to sector.
          8. Create a new partition.

            mkpart <Partition name> <Start sector> <End sector>

            +

          9. Enter unit s and press Enter to set the measurement unit of the disk to sector.
          10. Create a new partition.

            mkpart <partition-name> <start-sector> <end-sector>

            In this example, run the following command:

            mkpart test 2048s 100%

            In this example, one partition is created for the new data disk, starting on 2048 and using 100% of the rest of the disk. The two values are used for reference only. You can determine the number of partitions and the partition size based on your service requirements.

            @@ -91,7 +91,7 @@ vdb 253:16 0 100G 0 disk └─vdb1 253:17 0 100G 0 part

            In the command output, /dev/vdb1 is the partition you created.

            -

          11. Format the new partition with a desired file system format.

            mkfs -t File system format /dev/vdb1

            +

          12. Format the new partition with a desired file system format.

            mkfs -t <file-system-format> /dev/vdb1

            In this example, the ext4 format is used for the new partition.

            mkfs -t ext4 /dev/vdb1

            Information similar to the following is displayed:
            [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1
@@ -120,12 +120,12 @@ Writing superblocks and filesystem accounting information: done

            The formatting takes a period of time. Observe the system running status and do not exit.

            The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.

            -

          13. Create a mount point.

            mkdir Mount point

            +

          14. Create a mount point.

            mkdir <mount-point>

            In this example, the /mnt/sdc mount point is created.

            mkdir /mnt/sdc

            The /mnt directory exists on all Linux systems. If the mount point cannot be created, it may be that the /mnt directory has been accidentally deleted. You can run mkdir -p /mnt/sdc to create the mount point.

            -

          15. Mount the new partition on the created mount point.

            mount Disk partition Mount point

            +

          16. Mount the new partition on the created mount point.

            mount <disk-partition> <mount-point>

            In this example, the /dev/vdb1 partition is mounted on /mnt/sdc.

            mount /dev/vdb1 /mnt/sdc

          17. Check the mount result.

            df -TH

            @@ -147,7 +147,7 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0

            The following example uses UUIDs to identify disks in the fstab file. You are advised not to use device names (like /dev/vdb1) to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after an ECS stop or start. This can even prevent your ECS from booting up.

            UUIDs are the unique character strings for identifying partitions in Linux.

            -
            1. Query the partition UUID.

              blkid Disk partition

              +
              1. Query the partition UUID.

                blkid <disk-partition>

                In this example, the UUID of the /dev/vdb1 partition is queried.

                blkid /dev/vdb1

                Information similar to the following is displayed:

                @@ -157,11 +157,11 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0

              2. Open the fstab file using the vi editor.

                vi /etc/fstab

              3. Press i to enter editing mode.
              4. Move the cursor to the end of the file and press Enter. Then, add the following information:

                UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2

              5. Press Esc, enter :wq, and press Enter.

                The system saves the configurations and exits the vi editor.

                -

              6. Verify that the disk is auto-mounted at startup.

                1. Unmount the partition.

                  umount Disk partition

                  +

                2. Verify that the disk is auto-mounted at startup.

                  1. Unmount the partition.

                    umount <disk-partition>

                    In this example, run the following command:

                    umount /dev/vdb1

                  2. Reload all the content in the /etc/fstab file.

                    mount -a

                    -
                  3. Query the file system mounting information.

                    mount | grep Mount point

                    +
                  4. Query the file system mounting information.

                    mount | grep <mount-point>

                    In this example, run the following command:

                    mount | grep /mnt/sdc

                    If information similar to the following is displayed, automatic mounting has been configured:

                    diff --git a/docs/ecs/umn/en-us_topic_0091224748.html b/docs/ecs/umn/en-us_topic_0091224748.html index 735e0dfcc..f1e7ce8e3 100644 --- a/docs/ecs/umn/en-us_topic_0091224748.html +++ b/docs/ecs/umn/en-us_topic_0091224748.html @@ -5,12 +5,14 @@

                    C7t ECSs support encryption using Intel® SGX to protect the confidentiality and integrity of key code and data from being damaged by malware. Based on the TPM/TCM chip, the boot chain from the underlying server hardware to the guest OS can be measured and verified to implement trusted boot.

                    C4 ECSs use second-generation Intel® Xeon® Scalable processors to provide powerful and stable computing performance. By using 25GE high-speed intelligent NICs, C4 ECSs offer ultra-high network bandwidth and packets per second (PPS).

                    C3 ECSs use Intel® Xeon® Scalable processors, KVM virtualization, Data Plane Development Kit (DPDK) rapid packet processing mechanism, and high-performance NICs to deliver high and stable computing performance for enterprise-grade applications.

                    +

                    X1e ECSs deliver powerful and stable compute. They use Intel® Xeon® Scalable processors and high-performance networks to provide high performance and stability for enterprise-grade applications.

                    Scenarios

                    • C7n ECSs are suitable for:
                      • Medium- and heavy-load enterprise applications with strict requirements on computing and network performance, such as web applications, e-commerce platforms, short video platforms, online games, and insurance and finance.
                    • C7t ECSs are suitable for:
                      • Scenarios involving sensitive information such as personal identity information and healthcare, financial, and intellectual property data
                      • Confidential data sharing in multi-party computation
                      • Blockchain
                      • Confidential machine learning
                      • Scenarios with high security and trustworthy requirements, such as finance, government, and enterprises
                      • Enterprise-class applications of various types and scales
                    • C4 ECSs are suitable for:
                      • Websites and web applications that require high computing and network performance
                      • General databases
                      • Cache servers
                      • Medium- and heavy-load enterprise applications
                    • C3 ECSs are suitable for:
                      • Small- and medium-sized databases, cache clusters, and search clusters with high requirements on stability
                      • Enterprise-class applications of various types and scales
                      +
                    • X1e ECSs are suitable for:
                      • Small- and medium-sized databases that require high stability
                      • Cache and search clusters
                      • Enterprise-grade applications

                    Specifications

                    @@ -1025,10 +1027,258 @@
    15. -
    -

    Notes

    Table 5 lists the OSs supported by dedicated general-purpose ECSs.

    -
    Table 5 Supported OS versions

    OS

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 5 X1e ECS specifications

    Flavor

    +

    vCPUs

    +

    Memory

    +

    (GiB)

    +

    Max./Assured Bandwidth

    +

    (Gbit/s)

    +

    Max. PPS

    +

    (10,000)

    +

    Max. NICs

    +

    Virtualization

    +

    x1e.large.2

    +

    2

    +

    4

    +

    1.5/0.6

    +

    30

    +

    2

    +

    KVM

    +

    x1e.slarge.2

    +

    3

    +

    6

    +

    2/0.8

    +

    40

    +

    2

    +

    KVM

    +

    x1e.xlarge.2

    +

    4

    +

    8

    +

    3/1

    +

    50

    +

    2

    +

    KVM

    +

    x1e.2slarge.2

    +

    6

    +

    12

    +

    4/1.5

    +

    70

    +

    3

    +

    KVM

    +

    x1e.3xlarge.2

    +

    12

    +

    24

    +

    7/3

    +

    110

    +

    4

    +

    KVM

    +

    x1e.large.3

    +

    2

    +

    6

    +

    1.5/0.6

    +

    30

    +

    2

    +

    KVM

    +

    x1e.slarge.3

    +

    3

    +

    9

    +

    2/0.8

    +

    40

    +

    2

    +

    KVM

    +

    x1e.xlarge.3

    +

    4

    +

    12

    +

    3/1

    +

    50

    +

    2

    +

    KVM

    +

    x1e.2slarge.3

    +

    6

    +

    18

    +

    4/1.5

    +

    70

    +

    3

    +

    KVM

    +

    x1e.3xlarge.3

    +

    12

    +

    36

    +

    7/3

    +

    110

    +

    4

    +

    KVM

    +

    x1e.large.4

    +

    2

    +

    8

    +

    1.5/0.6

    +

    30

    +

    2

    +

    KVM

    +

    x1e.slarge.4

    +

    3

    +

    12

    +

    2/0.8

    +

    40

    +

    2

    +

    KVM

    +

    x1e.xlarge.4

    +

    4

    +

    16

    +

    3/1

    +

    50

    +

    2

    +

    KVM

    +

    x1e.2slarge.4

    +

    6

    +

    24

    +

    4/1.5

    +

    70

    +

    3

    +

    KVM

    +

    x1e.3xlarge.4

    +

    12

    +

    48

    +

    7/3

    +

    110

    +

    4

    +

    KVM

    +
    +
    + +

    Notes

    Table 6 lists the OSs supported by dedicated general-purpose ECSs.

    + +
    diff --git a/docs/ecs/umn/en-us_topic_0097289624.html b/docs/ecs/umn/en-us_topic_0097289624.html index 045f40ccb..0016591e8 100644 --- a/docs/ecs/umn/en-us_topic_0097289624.html +++ b/docs/ecs/umn/en-us_topic_0097289624.html @@ -25,14 +25,14 @@ - - - - - - @@ -515,11 +515,11 @@

    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

    -
    • P5s ECSs support automatic recovery when the hosts accommodating such ECSs become faulty.
    • After a P5s ECS is stopped, basic resources (including 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.
    +

    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

    -

    P3 ECSs use NVIDIA A100 GPUs and provide flexibility and ultra-high-performance computing. P3 ECSs have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics. Theoretically, the FP32 is 19.5 TFLOPS and the TF32 tensor core is 156 TFLOPS | 312 TFLOPS (sparsity enabled).

    +

    P3 ECSs use NVIDIA A100 GPUs and provide flexibility and ultra-high-performance computing. P3 ECSs have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics. Theoretically, the FP32 is 19.5 TFLOPS, and the TF32 tensor core is 156 TFLOPS | 312 TFLOPS (sparsity enabled).

    Specifications

    Table 6 Supported OS versions

    OS

    Version

    G7v

    • CentOS 8.2 64bit
    • CentOS 7.6 64bit
    • Ubuntu 20.04 Server 64bit
    • Ubuntu 18.04 Server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit
    +
    • CentOS 8.2 64bit
    • CentOS 7.6 64bit
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit

    Graphics-accelerated

    G7

    • CentOS 8.2 64bit
    • CentOS 7.6 64bit
    • Ubuntu 20.04 Server 64bit
    • Ubuntu 18.04 Server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit
    +
    • CentOS 8.2 64bit
    • CentOS 7.6 64bit
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit

    Graphics-accelerated

    @@ -60,28 +60,28 @@

    P2s

    • CentOS 7.9 64bit
    • EulerOS 2.5 64bit
    • Oracle Linux Server release 7.6 64bit
    • Ubuntu 20.04 Server 64bit
    • Ubuntu 18.04 Server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit
    • Windows Server 2012 R2 Standard 64bit
    +
    • CentOS 7.9 64bit
    • EulerOS 2.5 64bit
    • Oracle Linux Server release 7.6 64bit
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit
    • Windows Server 2012 R2 Standard 64bit

    Computing-accelerated

    P2v

    • CentOS 7.9 64bit
    • EulerOS 2.5 64bit
    • Oracle Linux Server release 7.6 64bit
    • Ubuntu 20.04 Server 64bit
    • Ubuntu 18.04 Server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit
    • Windows Server 2012 R2 Standard 64bit
    +
    • CentOS 7.9 64bit
    • EulerOS 2.5 64bit
    • Oracle Linux Server release 7.6 64bit
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit
    • Windows Server 2012 R2 Standard 64bit

    Inference-accelerated

    Pi5e

    • CentOS 7.9 64bit
    • CentOS 7.8 64bit
    • CentOS 7.7 64bit
    • CentOS 7.6 64bit
    • Ubuntu 22.04 Server 64bit
    • Ubuntu 20.04 Server 64bit
    • Ubuntu 18.04 Server 64bit
    • Ubuntu 16.04 Server 64bit
    • EulerOS 2.0 64bit
    +
    • CentOS 7.9 64bit
    • CentOS 7.8 64bit
    • CentOS 7.7 64bit
    • CentOS 7.6 64bit
    • Ubuntu 22.04 server 64bit
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    • Ubuntu 16.04 server 64bit
    • EulerOS 2.0 64bit

    Inference-accelerated

    Pi2

    • CentOS 7.9 64bit
    • Oracle Linux Server release 7.6 64bit
    • Ubuntu 20.04 Server 64bit
    • Ubuntu 18.04 Server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit
    • Windows Server 2012 R2 Standard 64bit
    +
    • CentOS 7.9 64bit
    • Oracle Linux Server release 7.6 64bit
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    • Windows Server 2019 Standard 64bit
    • Windows Server 2016 Standard 64bit
    • Windows Server 2012 R2 Standard 64bit
    - @@ -582,7 +582,7 @@ - @@ -603,7 +603,7 @@ - @@ -624,7 +624,7 @@ - @@ -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

    Table 6 P3 ECS specifications

    Flavor

    @@ -561,7 +561,7 @@

    4

    1 × NVIDIA A100 80GB

    +

    1 × NVIDIA A100 80 GB

    80

    8

    2 × NVIDIA A100 80GB

    +

    2 × NVIDIA A100 80 GB

    160

    8

    4 × NVIDIA A100 80GB

    +

    4 × NVIDIA A100 80 GB

    320

    8

    8 × NVIDIA A100 80GB

    +

    8 × NVIDIA A100 80 GB

    640
    @@ -1063,7 +1063,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_0116266207.html b/docs/ecs/umn/en-us_topic_0116266207.html index cf23ccc98..49ae2013f 100644 --- a/docs/ecs/umn/en-us_topic_0116266207.html +++ b/docs/ecs/umn/en-us_topic_0116266207.html @@ -1,11 +1,11 @@

    Viewing Traces

    -

    Scenarios

    After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. Cloud Trace Service (CTS) stores operation records (traces) generated in the last seven days.

    +

    Scenarios

    After you enable Cloud Trace Service (CTS) and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records (traces) generated in the last seven days.

    -

    Viewing Real-Time Traces in the Trace List

    1. Log in to the management console.
    2. Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
    3. Choose Trace List in the navigation pane on the left.
    4. Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
      Figure 1 Filters
      +

      Viewing Real-Time Traces in the Trace List

      1. Log in to the management console.
      2. Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
      3. Choose Trace List in the navigation pane on the left.
      4. Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
        Figure 1 Filters
        • Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
          • If you select Resource ID for Search By, specify a resource ID.
          • If you select Trace name for Search By, specify a trace name.
          • If you select Resource name for Search By, specify a resource name.
          -
        • Operator: Select a user.
        • Trace Status: Select All trace statuses, Normal, Warning, or Incident.
        • Time range: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
        +
      5. Operator: Select a user.
      6. Trace Status: Select All trace statuses, Normal, Warning, or Incident.
      7. Time range: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
    5. Click Query.
    6. On the Trace List page, you can also export and refresh the trace list.
      • Click Export to export all traces in the query result as a CSV file. The file can contain up to 5,000 records.
      • Click to view the latest information about traces.
    7. Click on the left of a trace to expand its details.

      @@ -14,7 +14,7 @@

    8. Click View Trace in the Operation column. The trace details are displayed.

      -
    9. For details about key fields in the trace structure, see Trace Structure and Example Traces in the CTS User Guide.
    +
  15. For details about key fields in the trace structure, see Trace Structure and Example Traces in the CTS User Guide.
    16. diff --git a/docs/ecs/umn/en-us_topic_0120795802.html b/docs/ecs/umn/en-us_topic_0120795802.html index f72d17af5..85c3377bc 100644 --- a/docs/ecs/umn/en-us_topic_0120795802.html +++ b/docs/ecs/umn/en-us_topic_0120795802.html @@ -9,7 +9,7 @@
  16. Click the Advanced tab and then Settings in the Performance pane.

    The Performance Options dialog box is displayed.

    Figure 1 Performance Options
  17. Click the Advanced tab and then Background Services in the Processor scheduling pane.
  18. Click Change in the Virtual memory pane.

    The Virtual Memory dialog box is displayed.

    -
  19. Configure virtual memory based on service requirements.
    • Automatically manage paging file size for all drives: Deselect the check box.
    • Drive: Select the drive where the virtual memory file is stored.

      You are advised not to select the system disk to store the virtual memory.

      +
    • Configure virtual memory based on service requirements.
      • Automatically manage paging file size for all drives: Deselect the checkbox.
      • Drive: Select the drive where the virtual memory file is stored.

        You are advised not to select the system disk to store the virtual memory.

      • Custom size: Select Custom size and set Initial size and Maximum size.

        Considering Memory.dmp caused by blue screen of death (BSOD), you are advised to set Initial size to 16 and Maximum size to 4,096.

      Figure 2 Virtual Memory
      diff --git a/docs/ecs/umn/en-us_topic_0177512565.html b/docs/ecs/umn/en-us_topic_0177512565.html index b8a7cb225..2f29e9f0d 100644 --- a/docs/ecs/umn/en-us_topic_0177512565.html +++ b/docs/ecs/umn/en-us_topic_0177512565.html @@ -1077,9 +1077,257 @@
    20. Table 9 Pi5e ECS specifications

    Flavor
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 4 X1 ECS specifications

    Flavor

    +

    vCPUs

    +

    Memory

    +

    (GiB)

    +

    Max./Assured Bandwidth

    +

    (Gbit/s)

    +

    Max. PPS

    +

    (10,000)

    +

    Max. NICs

    +

    Virtualization

    +

    x1.large.2

    +

    2

    +

    4

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.slarge.2

    +

    3

    +

    6

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.xlarge.2

    +

    4

    +

    8

    +

    1.5/0.4

    +

    15

    +

    2

    +

    KVM

    +

    x1.2slarge.2

    +

    6

    +

    12

    +

    1.5/0.4

    +

    15

    +

    3

    +

    KVM

    +

    x1.3xlarge.2

    +

    12

    +

    24

    +

    3/0.8

    +

    20

    +

    4

    +

    KVM

    +

    x1.large.3

    +

    2

    +

    6

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.slarge.3

    +

    3

    +

    9

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.xlarge.3

    +

    4

    +

    12

    +

    1.5/0.4

    +

    15

    +

    2

    +

    KVM

    +

    x1.2slarge.3

    +

    6

    +

    18

    +

    1.5/0.4

    +

    15

    +

    3

    +

    KVM

    +

    x1.3xlarge.3

    +

    12

    +

    36

    +

    3/0.8

    +

    20

    +

    4

    +

    KVM

    +

    x1.large.4

    +

    2

    +

    8

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.slarge.4

    +

    3

    +

    12

    +

    0.8/0.2

    +

    10

    +

    2

    +

    KVM

    +

    x1.xlarge.4

    +

    4

    +

    16

    +

    1.5/0.4

    +

    15

    +

    2

    +

    KVM

    +

    x1.2slarge.4

    +

    6

    +

    24

    +

    1.5/0.4

    +

    15

    +

    3

    +

    KVM

    +

    x1.3xlarge.4

    +

    12

    +

    48

    +

    3/0.8

    +

    20

    +

    4

    +

    KVM

    +
    +

    Dedicated General-Purpose

    -
    Table 4 C7n ECS specifications

    Flavor

    +
    @@ -1486,7 +1734,7 @@
    Table 5 C7n ECS specifications

    Flavor

    vCPUs

    -
    Table 5 C7t ECS specifications

    Flavor

    +
    @@ -1528,7 +1776,7 @@
    Table 6 C7t ECS specifications

    Flavor

    vCPUs

    -
    Table 6 C4 ECS specifications

    Flavor

    +
    @@ -1829,7 +2077,7 @@
    Table 7 C4 ECS specifications

    Flavor

    vCPUs

    -
    Table 7 C3 ECS specifications

    Flavor

    +
    @@ -2088,9 +2336,257 @@
    Table 8 C3 ECS specifications

    Flavor

    vCPUs
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 9 X1e ECS specifications

    Flavor

    +

    vCPUs

    +

    Memory

    +

    (GiB)

    +

    Max./Assured Bandwidth

    +

    (Gbit/s)

    +

    Max. PPS

    +

    (10,000)

    +

    Max. NICs

    +

    Virtualization

    +

    x1e.large.2

    +

    2

    +

    4

    +

    1.5/0.6

    +

    30

    +

    2

    +

    KVM

    +

    x1e.slarge.2

    +

    3

    +

    6

    +

    2/0.8

    +

    40

    +

    2

    +

    KVM

    +

    x1e.xlarge.2

    +

    4

    +

    8

    +

    3/1

    +

    50

    +

    2

    +

    KVM

    +

    x1e.2slarge.2

    +

    6

    +

    12

    +

    4/1.5

    +

    70

    +

    3

    +

    KVM

    +

    x1e.3xlarge.2

    +

    12

    +

    24

    +

    7/3

    +

    110

    +

    4

    +

    KVM

    +

    x1e.large.3

    +

    2

    +

    6

    +

    1.5/0.6

    +

    30

    +

    2

    +

    KVM

    +

    x1e.slarge.3

    +

    3

    +

    9

    +

    2/0.8

    +

    40

    +

    2

    +

    KVM

    +

    x1e.xlarge.3

    +

    4

    +

    12

    +

    3/1

    +

    50

    +

    2

    +

    KVM

    +

    x1e.2slarge.3

    +

    6

    +

    18

    +

    4/1.5

    +

    70

    +

    3

    +

    KVM

    +

    x1e.3xlarge.3

    +

    12

    +

    36

    +

    7/3

    +

    110

    +

    4

    +

    KVM

    +

    x1e.large.4

    +

    2

    +

    8

    +

    1.5/0.6

    +

    30

    +

    2

    +

    KVM

    +

    x1e.slarge.4

    +

    3

    +

    12

    +

    2/0.8

    +

    40

    +

    2

    +

    KVM

    +

    x1e.xlarge.4

    +

    4

    +

    16

    +

    3/1

    +

    50

    +

    2

    +

    KVM

    +

    x1e.2slarge.4

    +

    6

    +

    24

    +

    4/1.5

    +

    70

    +

    3

    +

    KVM

    +

    x1e.3xlarge.4

    +

    12

    +

    48

    +

    7/3

    +

    110

    +

    4

    +

    KVM

    +
    +

    Memory-optimized

    -
    Table 8 M7n ECS specifications

    Flavor

    +
    @@ -2308,7 +2804,7 @@
    Table 10 M7n ECS specifications

    Flavor

    vCPUs

    -
    Table 9 M4 ECS specifications

    Flavor

    +
    @@ -2524,7 +3020,7 @@
    Table 11 M4 ECS specifications

    Flavor

    vCPUs

    -
    Table 10 M3 ECS specifications

    Flavor

    +
    @@ -2690,7 +3186,7 @@

    Large-Memory

    -
    Table 12 M3 ECS specifications

    Flavor

    vCPUs
    Table 11 E6 ECS specifications

    Flavor

    +
    @@ -2753,7 +3249,7 @@
    Table 13 E6 ECS specifications

    Flavor

    vCPUs

    -
    Table 12 E3 ECS specifications

    Flavor

    +
    @@ -2853,7 +3349,7 @@

    Disk-intensive

    -
    Table 14 E3 ECS specifications

    Flavor

    vCPUs
    Table 13 D2 ECS specifications

    Flavor

    +
    @@ -2986,7 +3482,7 @@

    Ultra-high I/O

    -
    Table 15 D2 ECS specifications

    Flavor

    vCPUs
    Table 14 I3m ECS specifications

    Flavor

    +
    @@ -3128,7 +3624,7 @@
    Table 16 I3m ECS specifications

    Flavor

    vCPUs

    -
    Table 15 I3 ECS specifications

    Flavor

    +
    @@ -3347,7 +3843,7 @@

    GPU-accelerated

    -
    Table 17 I3 ECS specifications

    Flavor

    vCPUs
    Table 16 G7v ECS specifications

    Flavor

    +
    @@ -3440,7 +3936,7 @@
    Table 18 G7v ECS specifications

    Flavor

    vCPUs

    -
    Table 17 G7 ECS specifications

    Flavor

    +
    @@ -3512,7 +4008,7 @@
    Table 19 G7 ECS specifications

    Flavor

    vCPUs

    -
    Table 18 G6 ECS specifications

    Flavor

    +
    @@ -3605,7 +4101,7 @@
    Table 20 G6 ECS specifications

    Flavor

    vCPUs

    -
    Table 19 P5s ECS specifications

    Flavor

    +
    @@ -3715,7 +4211,7 @@
    Table 21 P5s ECS specifications

    Flavor

    vCPUs

    -
    Table 20 P3 ECS specifications

    Flavor

    +
    @@ -3754,7 +4250,7 @@ - @@ -3775,7 +4271,7 @@ - @@ -3796,7 +4292,7 @@ - @@ -3817,7 +4313,7 @@ - @@ -3828,7 +4324,7 @@
    Table 22 P3 ECS specifications

    Flavor

    vCPUs

    4

    1 × NVIDIA A100 80GB

    +

    1 × NVIDIA A100 80 GB

    80

    8

    2 × NVIDIA A100 80GB

    +

    2 × NVIDIA A100 80 GB

    160

    8

    4 × NVIDIA A100 80GB

    +

    4 × NVIDIA A100 80 GB

    320

    8

    8 × NVIDIA A100 80GB

    +

    8 × NVIDIA A100 80 GB

    640

    -
    Table 21 P2s ECS specifications

    Flavor

    +
    @@ -3957,7 +4453,7 @@
    Table 23 P2s ECS specifications

    Flavor

    vCPUs

    -
    Table 22 P2v ECS specifications

    Flavor

    +
    @@ -4083,7 +4579,7 @@
    Table 24 P2v ECS specifications

    Flavor

    vCPUs

    -
    Table 23 Pi5e ECS specifications

    Flavor

    +
    @@ -4206,7 +4702,7 @@
    Table 25 Pi5e ECS specifications

    Flavor

    vCPUs

    -
    Table 24 Pi2 ECS specifications

    Flavor

    +
    diff --git a/docs/ecs/umn/en-us_topic_0186645877.html b/docs/ecs/umn/en-us_topic_0186645877.html index d32e916a2..022afca2d 100644 --- a/docs/ecs/umn/en-us_topic_0186645877.html +++ b/docs/ecs/umn/en-us_topic_0186645877.html @@ -6,7 +6,7 @@

    Figure 1 shows the relationship between regions and AZs.

    Figure 1 Regions and AZs
    -

    Selecting a Region

    Select a region closest to your target users for lower network latency and quick access.

    +

    Selecting a Region

    You are advised to select a region close to you or your target users. This helps ensure low access latency.

    Selecting an AZ

    When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.

    • For high DR capability, deploy resources in different AZs within the same region.
    • For lower network latency, deploy resources in the same AZ.
    Table 26 Pi2 ECS specifications

    Flavor

    vCPUs