diff --git a/docs/ecs/umn/ALL_META.TXT.json b/docs/ecs/umn/ALL_META.TXT.json index d67062fd1..65b11fb67 100644 --- a/docs/ecs/umn/ALL_META.TXT.json +++ b/docs/ecs/umn/ALL_META.TXT.json @@ -1,4 +1,7 @@ [ + { + "dockw":"User Guide" + }, { "uri":"en-us_topic_0092494580.html", "node_id":"en-us_topic_0092494580.xml", @@ -184,7 +187,7 @@ "node_id":"en-us_topic_0091224748.xml", "product_code":"ecs", "code":"11", - "des":"C4 ECSs use second-generation Intel® Xeon® Scalable processors and high-speed intelligent NICs to offer powerful and stable computing performance, and ultra-high network ", + "des":"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, t", "doc_type":"usermanual", "kw":"Dedicated General-Purpose ECSs,ECS Specifications and Types,User Guide", "search_title":"", @@ -2012,7 +2015,7 @@ "node_id":"en-us_topic_0140323154.xml", "product_code":"ecs", "code":"109", - "des":"If you have not created any security group, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) when yo", + "des":"If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) wh", "doc_type":"usermanual", "kw":"Default Security Group and Rules,Security Groups,User Guide", "search_title":"", @@ -5535,4 +5538,4 @@ "title":"Glossary", "githuburl":"" } -] \ No newline at end of file +] diff --git a/docs/ecs/umn/CLASS.TXT.json b/docs/ecs/umn/CLASS.TXT.json index dc0e978f5..dee0aa8f4 100644 --- a/docs/ecs/umn/CLASS.TXT.json +++ b/docs/ecs/umn/CLASS.TXT.json @@ -90,7 +90,7 @@ "code":"10" }, { - "desc":"C4 ECSs use second-generation Intel® Xeon® Scalable processors and high-speed intelligent NICs to offer powerful and stable computing performance, and ultra-high network ", + "desc":"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, t", "product_code":"ecs", "title":"Dedicated General-Purpose ECSs", "uri":"en-us_topic_0091224748.html", @@ -972,7 +972,7 @@ "code":"108" }, { - "desc":"If you have not created any security group, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) when yo", + "desc":"If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) wh", "product_code":"ecs", "title":"Default Security Group and Rules", "uri":"en-us_topic_0140323154.html", @@ -2717,4 +2717,4 @@ "p_code":"", "code":"302" } -] \ No newline at end of file +] diff --git a/docs/ecs/umn/en-us_image_0000001695898240.png b/docs/ecs/umn/en-us_image_0000001695898240.png new file mode 100644 index 000000000..f124a0045 Binary files /dev/null and b/docs/ecs/umn/en-us_image_0000001695898240.png differ diff --git a/docs/ecs/umn/en-us_image_0000001743660585.png b/docs/ecs/umn/en-us_image_0000001743660585.png new file mode 100644 index 000000000..f1f10b3c2 Binary files /dev/null and b/docs/ecs/umn/en-us_image_0000001743660585.png differ diff --git a/docs/ecs/umn/en-us_topic_0030878383.html b/docs/ecs/umn/en-us_topic_0030878383.html index 18e0a818a..3d32cd296 100644 --- a/docs/ecs/umn/en-us_topic_0030878383.html +++ b/docs/ecs/umn/en-us_topic_0030878383.html @@ -8,108 +8,106 @@

Procedure

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

    The page providing details about the ECS is displayed.

  5. Click the Security Groups tab, expand the information of the security group, and view security group rules.
  6. Click the security group ID.

    The system automatically switches to the security group details page.

  7. Configure required parameters.

    You can click + to add more inbound rules.

    -

    Figure 1 Add Inbound Rule
    -
    Table 1 Inbound rule parameter description

    Parameter

    +
    - - - - - - - - - - - - - - - -
    Table 1 Inbound rule parameter description

    Parameter

    Description

    +

    Description

    Example Value

    +

    Example Value

    Protocol & Port

    +

    Protocol & Port

    The network protocol used to match traffic in a security group rule.

    +

    The network protocol used to match traffic in a security group rule.

    Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.

    TCP

    +

    TCP

    Port: The port or port range over which traffic can reach your ECS. The value can be from 1 to 65535.

    +

    Port: The port or port range over which traffic can reach your ECS. The value can be from 1 to 65535.

    22, or 22-30

    +

    22, or 22-30

    Type

    +

    Type

    Source IP address version. You can select:
    • IPv4
    • IPv6
    +
    Source IP address version. You can select:
    • IPv4
    • IPv6

    IPv4

    +

    IPv4

    Source

    +

    Source

    Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. For example:
    • IP address:
      • Single IP address: 192.168.10.10/32
      • All IP addresses: 0.0.0.0/0
      • IP address range: 192.168.1.0/24
      +
    Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. For example:
    • IP address:
      • Single IP address: 192.168.10.10/32
      • All IP addresses: 0.0.0.0/0
      • IP address range: 192.168.1.0/24
    • Security group: sg-A

    If the source is a security group, this rule will apply to all instances associated with the selected security group.

    0.0.0.0/0

    +

    0.0.0.0/0

    Description

    +

    Description

    Supplementary information about the security group rule. This parameter is optional.

    +

    Supplementary information about the security group rule. This parameter is optional.

    The security group rule description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

    N/A

    +

    N/A
  8. Configure required parameters.

    You can click + to add more outbound rules.

    -

    Figure 2 Add Outbound Rule
    -
    Table 2 Outbound rule parameter description

    Parameter

    +
    - - - - - - - - - - - - - - - - diff --git a/docs/ecs/umn/en-us_topic_0035470099.html b/docs/ecs/umn/en-us_topic_0035470099.html index 24eff6095..dfac86a98 100644 --- a/docs/ecs/umn/en-us_topic_0035470099.html +++ b/docs/ecs/umn/en-us_topic_0035470099.html @@ -224,11 +224,6 @@ - - - - - - - - - - - - - + + +
    Table 2 Outbound rule parameter description

    Parameter

    Description

    +

    Description

    Example Value

    +

    Example Value

    Protocol & Port

    +

    Protocol & Port

    The network protocol used to match traffic in a security group rule.

    +

    The network protocol used to match traffic in a security group rule.

    Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.

    TCP

    +

    TCP

    Port: The port or port range over which traffic can leave your ECS. The value can be from 1 to 65535.

    +

    Port: The port or port range over which traffic can leave your ECS. The value can be from 1 to 65535.

    22, or 22-30

    +

    22, or 22-30

    Type

    +

    Type

    Source IP address version. You can select:
    • IPv4
    • IPv6
    +
    Source IP address version. You can select:
    • IPv4
    • IPv6

    IPv4

    +

    IPv4

    Destination

    +

    Destination

    Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example:

    +

    Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example:

    • IP address:
      • Single IP address: 192.168.10.10/32
      • All IP addresses: 0.0.0.0/0
      • IP address range: 192.168.1.0/24
    • Security group: sg-A

    0.0.0.0/0

    +

    0.0.0.0/0

    Description

    +

    Description

    Supplementary information about the security group rule. This parameter is optional.

    +

    Supplementary information about the security group rule. This parameter is optional.

    The security group rule description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

    N/A

    +

    N/A
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit

    SUSE-SAP

    -
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit
    -

    Ubuntu
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    diff --git a/docs/ecs/umn/en-us_topic_0035470101.html b/docs/ecs/umn/en-us_topic_0035470101.html index 7c9b3b3bb..d13a3b4b3 100644 --- a/docs/ecs/umn/en-us_topic_0035470101.html +++ b/docs/ecs/umn/en-us_topic_0035470101.html @@ -942,11 +942,6 @@
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit

    SUSE-SAP

    -
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit
    -

    Ubuntu
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    diff --git a/docs/ecs/umn/en-us_topic_0035550301.html b/docs/ecs/umn/en-us_topic_0035550301.html index d04f0eaaf..33af807fc 100644 --- a/docs/ecs/umn/en-us_topic_0035550301.html +++ b/docs/ecs/umn/en-us_topic_0035550301.html @@ -454,11 +454,6 @@
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit

    SUSE-SAP

    -
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit
    -

    Ubuntu
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    diff --git a/docs/ecs/umn/en-us_topic_0038024694.html b/docs/ecs/umn/en-us_topic_0038024694.html index 771fa79c1..adb1feae7 100644 --- a/docs/ecs/umn/en-us_topic_0038024694.html +++ b/docs/ecs/umn/en-us_topic_0038024694.html @@ -211,11 +211,6 @@
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit

    SUSE-SAP

    -
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit
    -

    Ubuntu
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    diff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html index 6e38cb882..35fc9d0a2 100644 --- a/docs/ecs/umn/en-us_topic_0041169567.html +++ b/docs/ecs/umn/en-us_topic_0041169567.html @@ -8,7 +8,13 @@

    2023-09-13

    +

    2023-10-31

    +

    Modified the following content:

    + +

    2023-09-13

    Added the following content:

    @@ -601,7 +607,7 @@

    2016-09-30

    Modified the following content:

    -
    • Added constraints in Managing ECS Groups because ECS groups apply only to HANA ECSs and large-memory ECSs.
    +

    2016-09-28

    diff --git a/docs/ecs/umn/en-us_topic_0091224748.html b/docs/ecs/umn/en-us_topic_0091224748.html index b1cddd4f3..159ec3904 100644 --- a/docs/ecs/umn/en-us_topic_0091224748.html +++ b/docs/ecs/umn/en-us_topic_0091224748.html @@ -1,549 +1,595 @@

    Dedicated General-Purpose ECSs

    -

    Overview

    C4 ECSs use second-generation Intel® Xeon® Scalable processors and high-speed intelligent NICs to offer powerful and stable computing performance, and ultra-high network bandwidth and PPS.

    -

    C3 ECSs are developed based on KVM virtualization, use Intel® Xeon® Scalable processors and Data Plane Development Kit (DPDK) rapid packet processing mechanism, and feature high and stable computing performance. Equipped with high-performance NICs, the C3 ECSs provide high performance and stability, meeting enterprise-grade application requirements.

    +

    Overview

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

    -

    Scenarios

    • C4 ECSs: Websites and web applications, generalized databases and cache servers, and medium- and heavy-workload enterprise applications with strict requirements on computing and network performance
    • C3 ECSs: Small- and medium-scale databases, cache servers, and search clusters with high requirements on stability; enterprise-grade applications
    +

    Scenarios

    • 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
      +

    Specifications

    -
    Table 1 C4 ECS specifications

    Flavor

    +
    - - + + + + + + + + + + + + + + + + + +
    Table 1 C7t ECS specifications

    Flavor

    vCPUs

    +

    vCPUs

    Memory

    +

    Memory

    +

    (GiB)

    +

    Max./Assured Bandwidth

    +

    (Gbit/s)

    +

    Max. PPS

    +

    (10,000)

    +

    Max. NIC Queues

    +

    Max. NICs

    +

    Virtualization

    +

    c7t.28xlarge.4.physical

    +

    112

    +

    512

    +

    64/64

    +

    3000

    +

    32

    +

    32

    +

    BMS

    +
    +
    + +
    + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 2 C4 ECS specifications

    Flavor

    +

    vCPUs

    +

    Memory

    (GiB)

    Max./Assured Bandwidth

    +

    Max./Assured Bandwidth

    (Gbit/s)

    Max. PPS

    +

    Max. PPS

    (10,000)

    Max. NIC Queues

    +

    Max. NIC Queues

    Max. NICs

    +

    Max. NICs

    Virtualization

    +

    Virtualization

    Hardware

    +

    Hardware

    c4.large.2

    +

    c4.large.2

    2

    +

    2

    4

    +

    4

    4/1.2

    +

    4/1.2

    40

    +

    40

    2

    +

    2

    2

    +

    2

    KVM

    +

    KVM

    CPU: Intel® Xeon® Cascade Lake 6266

    +

    CPU: Intel® Xeon® Cascade Lake 6266

    c4.xlarge.2

    +

    c4.xlarge.2

    4

    +

    4

    8

    +

    8

    8/2.4

    +

    8/2.4

    80

    +

    80

    2

    +

    2

    3

    +

    3

    KVM

    +

    KVM

    c4.2xlarge.2

    +

    c4.2xlarge.2

    8

    +

    8

    16

    +

    16

    15/4.5

    +

    15/4.5

    150

    +

    150

    4

    +

    4

    4

    +

    4

    KVM

    +

    KVM

    c4.3xlarge.2

    +

    c4.3xlarge.2

    12

    +

    12

    24

    +

    24

    17/7

    +

    17/7

    200

    +

    200

    4

    +

    4

    6

    +

    6

    KVM

    +

    KVM

    c4.4xlarge.2

    +

    c4.4xlarge.2

    16

    +

    16

    32

    +

    32

    20/9

    +

    20/9

    280

    +

    280

    8

    +

    8

    8

    +

    8

    KVM

    +

    KVM

    c4.6xlarge.2

    +

    c4.6xlarge.2

    24

    +

    24

    48

    +

    48

    25/14

    +

    25/14

    400

    +

    400

    8

    +

    8

    8

    +

    8

    KVM

    +

    KVM

    c4.8xlarge.2

    +

    c4.8xlarge.2

    32

    +

    32

    64

    +

    64

    30/18

    +

    30/18

    550

    +

    550

    16

    +

    16

    8

    +

    8

    KVM

    +

    KVM

    c4.16xlarge.2

    +

    c4.16xlarge.2

    64

    +

    64

    128

    +

    128

    40/36

    +

    40/36

    1000

    +

    1000

    32

    +

    32

    8

    +

    8

    KVM

    +

    KVM

    c4.large.4

    +

    c4.large.4

    2

    +

    2

    8

    +

    8

    4/1.2

    +

    4/1.2

    40

    +

    40

    2

    +

    2

    2

    +

    2

    KVM

    +

    KVM

    c4.xlarge.4

    +

    c4.xlarge.4

    4

    +

    4

    16

    +

    16

    8/2.4

    +

    8/2.4

    80

    +

    80

    2

    +

    2

    3

    +

    3

    KVM

    +

    KVM

    c4.2xlarge.4

    +

    c4.2xlarge.4

    8

    +

    8

    32

    +

    32

    15/4.5

    +

    15/4.5

    150

    +

    150

    4

    +

    4

    4

    +

    4

    KVM

    +

    KVM

    c4.3xlarge.4

    +

    c4.3xlarge.4

    12

    +

    12

    48

    +

    48

    17/7

    +

    17/7

    200

    +

    200

    4

    +

    4

    6

    +

    6

    KVM

    +

    KVM

    c4.4xlarge.4

    +

    c4.4xlarge.4

    16

    +

    16

    64

    +

    64

    20/9

    +

    20/9

    280

    +

    280

    8

    +

    8

    8

    +

    8

    KVM

    +

    KVM

    c4.6xlarge.4

    +

    c4.6xlarge.4

    24

    +

    24

    96

    +

    96

    25/14

    +

    25/14

    400

    +

    400

    8

    +

    8

    8

    +

    8

    KVM

    +

    KVM

    c4.8xlarge.4

    +

    c4.8xlarge.4

    32

    +

    32

    128

    +

    128

    30/18

    +

    30/18

    550

    +

    550

    16

    +

    16

    8

    +

    8

    KVM

    +

    KVM

    c4.16xlarge.4

    +

    c4.16xlarge.4

    64

    +

    64

    256

    +

    256

    40/36

    +

    40/36

    1000

    +

    1000

    32

    +

    32

    8

    +

    8

    KVM

    +

    KVM
    -
    Table 2 C3 ECS specifications

    Flavor

    +
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 3 C3 ECS specifications

    Flavor

    vCPUs

    +

    vCPUs

    Memory

    +

    Memory

    (GiB)

    Max./Assured Bandwidth

    +

    Max./Assured Bandwidth

    (Gbit/s)

    Max. PPS

    +

    Max. PPS

    (10,000)

    Max. NIC Queues

    +

    Max. NIC Queues

    Max. NICs

    +

    Max. NICs

    Virtualization

    +

    Virtualization

    Hardware

    +

    Hardware

    c3.large.2

    +

    c3.large.2

    2

    +

    2

    4

    +

    4

    1.5/0.6

    +

    1.5/0.6

    30

    +

    30

    2

    +

    2

    12

    +

    12

    KVM

    +

    KVM

    CPU: Intel® Xeon® Skylake 6151

    +

    CPU: Intel® Xeon® Skylake 6151

    c3.xlarge.2

    +

    c3.xlarge.2

    4

    +

    4

    8

    +

    8

    3/1

    +

    3/1

    50

    +

    50

    2

    +

    2

    12

    +

    12

    KVM

    +

    KVM

    c3.2xlarge.2

    +

    c3.2xlarge.2

    8

    +

    8

    16

    +

    16

    5/2

    +

    5/2

    90

    +

    90

    4

    +

    4

    12

    +

    12

    KVM

    +

    KVM

    c3.4xlarge.2

    +

    c3.4xlarge.2

    16

    +

    16

    32

    +

    32

    10/4

    +

    10/4

    130

    +

    130

    4

    +

    4

    12

    +

    12

    KVM

    +

    KVM

    c3.8xlarge.2

    +

    c3.8xlarge.2

    32

    +

    32

    64

    +

    64

    15/8

    +

    15/8

    260

    +

    260

    8

    +

    8

    12

    +

    12

    KVM

    +

    KVM

    c3.15xlarge.2

    +

    c3.15xlarge.2

    60

    +

    60

    128

    +

    128

    17/16

    +

    17/16

    500

    +

    500

    16

    +

    16

    12

    +

    12

    KVM

    +

    KVM

    c3.large.4

    +

    c3.large.4

    2

    +

    2

    8

    +

    8

    1.5/0.6

    +

    1.5/0.6

    30

    +

    30

    2

    +

    2

    12

    +

    12

    KVM

    +

    KVM

    c3.xlarge.4

    +

    c3.xlarge.4

    4

    +

    4

    16

    +

    16

    3/1

    +

    3/1

    50

    +

    50

    2

    +

    2

    12

    +

    12

    KVM

    +

    KVM

    c3.2xlarge.4

    +

    c3.2xlarge.4

    8

    +

    8

    32

    +

    32

    5/2

    +

    5/2

    90

    +

    90

    4

    +

    4

    12

    +

    12

    KVM

    +

    KVM

    c3.4xlarge.4

    +

    c3.4xlarge.4

    16

    +

    16

    64

    +

    64

    10/4

    +

    10/4

    130

    +

    130

    4

    +

    4

    12

    +

    12

    KVM

    +

    KVM

    c3.8xlarge.4

    +

    c3.8xlarge.4

    32

    +

    32

    128

    +

    128

    15/8

    +

    15/8

    260

    +

    260

    8

    +

    8

    12

    +

    12

    KVM

    +

    KVM

    c3.15xlarge.4

    +

    c3.15xlarge.4

    60

    +

    60

    256

    +

    256

    16/16

    +

    16/16

    500

    +

    500

    16

    +

    16

    12

    +

    12

    KVM

    +

    KVM
    -

    Notes

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

    +

    Notes

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

    -
    Table 3 Supported OS versions

    OS

    +
    @@ -599,11 +645,6 @@ - - - - - -
    Table 4 Supported OS versions

    OS

    Version

    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit

    SUSE-SAP

    -
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit
    -

    Ubuntu
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    diff --git a/docs/ecs/umn/en-us_topic_0092494580.html b/docs/ecs/umn/en-us_topic_0092494580.html index 16842a160..1312f7ba5 100644 --- a/docs/ecs/umn/en-us_topic_0092494580.html +++ b/docs/ecs/umn/en-us_topic_0092494580.html @@ -1,8 +1,7 @@

    Service Overview

    -

    -
    +
    • What Is ECS?
      diff --git a/docs/ecs/umn/en-us_topic_0094118976.html b/docs/ecs/umn/en-us_topic_0094118976.html index 13ca482ca..b732c26ce 100644 --- a/docs/ecs/umn/en-us_topic_0094118976.html +++ b/docs/ecs/umn/en-us_topic_0094118976.html @@ -384,11 +384,6 @@
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit

    SUSE-SAP

    -
    • Novell SUSE Linux Enterprise Server 15 SP3 64bit
    • Novell SUSE Linux Enterprise Server 15 SP2 64bit
    • Novell SUSE Linux Enterprise Server 15 SP1 64bit
    • Novell SUSE Linux Enterprise Server 15 64bit
    • Novell SUSE Linux Enterprise Server 12 SP5 64bit
    • Novell SUSE Linux Enterprise Server 12 SP4 64bit
    • Novell SUSE Linux Enterprise Server 12 SP3 64bit
    -

    Ubuntu
    • Ubuntu 20.04 server 64bit
    • Ubuntu 18.04 server 64bit
    diff --git a/docs/ecs/umn/en-us_topic_0097289624.html b/docs/ecs/umn/en-us_topic_0097289624.html index d17facdc6..f1ec5a4bf 100644 --- a/docs/ecs/umn/en-us_topic_0097289624.html +++ b/docs/ecs/umn/en-us_topic_0097289624.html @@ -352,7 +352,7 @@

    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 Caffee
    • CUDA GPU rendering supported by RedShift for Autodesk 3dsMax and V-Ray for 3ds Max
    • Agisoft PhotoScan
    • MapD
    • More than 2,000 GPU-accelerated applications such as Amber, NAMD, and VASP
    -

    Notes

    +

    Notes

    • P3 ECSs support the following OSs:
      • Ubuntu 20.04 server 64bit
      • Ubuntu 18.04 server 64bit
      • CentOS 8.2 64bit
      • CentOS 8.1 64bit
      • CentOS 8.0 64bit
      • CentOS 7.9 64bit
      • CentOS 7.8 64bit
      • CentOS 7.7 64bit
      • CentOS 7.6 64bit
    • If a P3 ECS is created using a private image, make sure that the Tesla driver has been installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS.
    @@ -534,7 +534,7 @@
  9. By default, P2s ECSs created using a Windows public image have the Tesla driver installed.
  10. 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 Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS.
    11. -

    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

    @@ -672,7 +672,7 @@

    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 3dsMax and V-Ray for 3ds Max
    • Agisoft PhotoScan
    • MapD
    -
    Notes
    • Table 8 lists the OSs supported by P2v ECSs. +
      Notes
      • Table 8 lists the OSs supported by P2v ECSs.
        Table 8 Supported OS versions

        OS

        Version

        @@ -823,7 +823,7 @@
      • Excellent supercomputing ecosystem

        The supercomputing ecosystem allows you to build up a flexible, high-performance, cost-effective computing platform. A large number of HPC applications and deep-learning frameworks can run on P2 ECSs.

        • -

        Supported Common Software

        +

        Supported Common Software

        P2 ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software requires GPU CUDA parallel computing, use P2 ECSs. P2 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 3dsMax and V-Ray for 3ds Max
        • Agisoft PhotoScan
        • MapD
        Notes
        • The system disk of a P2 ECS must be greater than or equal to 15 GiB. It is recommended that the system disk be greater than 40 GiB.
        • The local NVMe SSDs attached to P2 ECSs are dedicated for services with strict requirements on storage I/O performance, such as deep learning training and HPC. Local disks are attached to the ECSs of specified flavors and cannot be separately bought. In addition, you are not allowed to detach a local disk and then attach it to another ECS.

          Data may be lost on the local NVMe SSDs attached to P2 ECSs due to a fault, for example, due to a disk or host fault. Therefore, you are suggested to store only temporary data in local NVMe SSDs. If you store important data in such a disk, securely back up the data.

          diff --git a/docs/ecs/umn/en-us_topic_0132345719.html b/docs/ecs/umn/en-us_topic_0132345719.html index d2ca7e6fd..bdec84aa2 100644 --- a/docs/ecs/umn/en-us_topic_0132345719.html +++ b/docs/ecs/umn/en-us_topic_0132345719.html @@ -1,8 +1,7 @@

          ECS Specifications and Types

          -

          -
          +
          • A Summary List of ECS Specifications
            diff --git a/docs/ecs/umn/en-us_topic_0140323154.html b/docs/ecs/umn/en-us_topic_0140323154.html index 3985165c9..32122d506 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 Group and Rules

            -
            If you have not created any security group, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) when you create it. A default security group has the following rules:
            • Inbound rules control incoming traffic to instances in a security group. Only instances in the same security group can communicate with each other, and all inbound requests are denied.
            • Outbound rules allow all outbound traffic and response traffic to the outbound requests.
            +
            If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) when you create it. A default security group has the following rules:
            • Inbound rules control incoming traffic to instances in a security group. Only instances in the same security group can communicate with each other, and all inbound requests are denied.
            • Outbound rules allow all outbound traffic and response traffic to the outbound requests.

            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 26969e360..885be8238 100644 --- a/docs/ecs/umn/en-us_topic_0163572589.html +++ b/docs/ecs/umn/en-us_topic_0163572589.html @@ -1,11 +1,7 @@

            Step 1: Configure Basic Settings

            -

            Accessing the ECS Creation Page

            1. Log in to the management console.
            2. Click in the upper left corner and select your region and project.
            3. Under Computing, click Elastic Cloud Server.
            4. Click Create ECS.
              The page for creating ECSs is displayed.

              SAP High-Performance Analytic Appliance (HANA) is a high-performance real-time data computing platform based on memory computing technologies. The cloud platform provides high-performance IaaS services that comply with SAP HANA requirements. These services help you rapidly request for SAP HANA resources (such as applying for HANA ECSs and public IP addresses) and install and configure SAP HANA, therefore improving your operation efficiency, reducing operation costs, and enhancing your experience.

              -

              HANA ECSs are dedicated for SAP HANA. If you want to deploy SAP HANA on cloud servers, create HANA ECSs.

              -

              For more information about HANA ECS application scenarios and creation methods, see SAP HANA User Guide.

              -
              -
              +

              Accessing the ECS Creation Page

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

                The page for creating ECSs is displayed.

              Performing Basic Configurations

              1. Select an AZ.

                An AZ is a physical location that uses independent power supply and networks. AZs in the same region can communicate with each other over an intranet.

                @@ -16,15 +12,12 @@
            5. Set DeH.

              This configuration is optional. This parameter is available only when you click Create ECS on the Dedicated Host page. It is unavailable when you click Create ECS on the Elastic Cloud Server page.

              DeH refers to physical server resources dedicated for a specified user. You can deploy ECSs on DeHs for better isolation, security, and performance of your ECSs. You can continue using your existing server software licenses of ECSs on DeHs to reduce costs. For more details, see Dedicated Host User Guide.

              -

              If you select a SUSE-SAP public image when creating an ECS on a DeH, you will be billed for the license.

              -
            6. Set Specifications.

              The cloud platform provides various ECS types for different application scenarios. You can choose from existing ECS types and flavors in the list. Alternatively, you can enter a flavor or specify vCPUs and memory size to search for the flavor suited to your needs.

              Latest generation shows the types and flavors of newly released ECSs, and All generations show the types and flavors of all ECSs provided by the cloud platform.

              • Before selecting an ECS type, learn about the introduction and notes on each type of ECSs. For details, see ECS Types.
              • You can select Hide sold-out specifications to hide specifications that have been sold out.
              • Local Disk: specifies the local storage of the physical server where the ECS is deployed. Only Hard Disk Driver (HDD) disks are supported. If the ECS of the selected type (such as Disk-intensive) uses local disks, the system automatically attaches the local disks to the ECS and displays the information of the local disks.

                For example, if Local Disk is 3x1800 GiB (HDD), three HDDs are attached to the ECS and the capacity of each HDD is 1800 GiB.

            7. Select an image.
              • Public image

                A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users. You can configure the runtime environment or software in the public image as needed.

                -

                If you select a SUSE-SAP public image, you will be billed for the license.

                For more information about public images, see Public Images Introduction.

              • Private image

                A private image is an image available only to the user who created it. It contains an OS, preinstalled public applications, and the user's private applications. Using a customized private image, you can create ECSs tailored to your needs in batches.

                diff --git a/docs/ecs/umn/en-us_topic_0163572590.html b/docs/ecs/umn/en-us_topic_0163572590.html index fdf04fc0d..bb425b587 100644 --- a/docs/ecs/umn/en-us_topic_0163572590.html +++ b/docs/ecs/umn/en-us_topic_0163572590.html @@ -18,7 +18,7 @@

                If you use the default security group rules for the outbound direction, the preceding requirements are met, and the ECS can be initialized. The default security group rules for the outbound direction are as follows:

                • Protocol: ANY
                • Port Range: ANY
                • Remote End: 0.0.0.0/16
            -
          • Set EIP.

            An EIP is a static public IP address bound to an ECS in a VPC. Using the EIP, the ECS provides services externally.

            +
          • Set EIP.

            An EIP is a static public IP address bound to an ECS in a VPC. Using the EIP, the ECS provides services externally.

            The following options are provided:

            • Auto assign

              The system automatically assigns an EIP for the ECS. The EIP provides a dedicated bandwidth that is configurable.

            • Use existing

              An existing EIP is assigned for the ECS. When using an existing EIP, you are not allowed to create ECSs in a batch.

              diff --git a/docs/ecs/umn/en-us_topic_0167429328.html b/docs/ecs/umn/en-us_topic_0167429328.html index 6a1170265..265dc3317 100644 --- a/docs/ecs/umn/en-us_topic_0167429328.html +++ b/docs/ecs/umn/en-us_topic_0167429328.html @@ -18,7 +18,7 @@

              Troubleshooting

              Before the troubleshooting, check whether the processes leading to the high CPU or bandwidth usage are normal, and handle the issue accordingly.

              Suggestions for non-malicious processes

              1. If your ECS runs Windows Server 2008 or 2012, ensure that the available memory is 2 GB or larger.
              2. Check whether Windows Update is running on the backend.
              3. Check whether the antivirus software is running scan tasks on the backend.
              4. Check whether any applications requiring high CPU or bandwidth are running on the ECS. If so, modify ECS specifications or enlarge bandwidth.
              5. If the ECS configuration meets the application requirements, deploy applications separately. For example, deploy the database and applications separately.
              -

              Suggestions for malicious processes

              +

              Suggestions for malicious processes

              If the high CPU or bandwidth usage is caused by viruses or Trojan horses, manually stop the affected processes. You are advised to troubleshoot the issue as follows:

              1. Use the commercial-edition antivirus software or install Microsoft Safety Scanner to scan for viruses in security mode.
              2. Install the latest patches for Windows.
              3. Run MSconfig to disable all drivers that are not delivered with Microsoft and check whether the fault is rectified. For details, see How to perform a clean boot in Windows.
              diff --git a/docs/ecs/umn/en-us_topic_0170232209.html b/docs/ecs/umn/en-us_topic_0170232209.html index 4b42ed507..b07abb4a0 100644 --- a/docs/ecs/umn/en-us_topic_0170232209.html +++ b/docs/ecs/umn/en-us_topic_0170232209.html @@ -268,7 +268,7 @@
      -

      Helpful Links

      +

      Helpful Links

      ECS FullAccess Policy Content

      {
         "Version": "1.1",
diff --git a/docs/ecs/umn/en-us_topic_0271001300.html b/docs/ecs/umn/en-us_topic_0271001300.html
index 0e61a2e3d..28e6fd116 100644
--- a/docs/ecs/umn/en-us_topic_0271001300.html
+++ b/docs/ecs/umn/en-us_topic_0271001300.html
@@ -1,11 +1,7 @@
 
 
-
-  
      Instances
      
-
-  
      
-
      
-
+
      Instances
      
+
      
 
      
 
        
 
      • ECS Overview
        
diff --git a/docs/ims/api-ref/test1703560485403.txt b/docs/ims/api-ref/test1703560485403.txt
new file mode 100644
index 000000000..ab16c7603
--- /dev/null
+++ b/docs/ims/api-ref/test1703560485403.txt
@@ -0,0 +1 @@
+D:\02CBR\13gitea\doc-exports\docs\ims\api-ref