From 55da809bbb28ff530ad124b21c77d2fb803fd584 Mon Sep 17 00:00:00 2001 From: zhangyue Date: Fri, 10 Feb 2023 10:40:03 +0000 Subject: [PATCH] SDRS API Doc Reviewed-by: Hasko, Vladimir Co-authored-by: zhangyue Co-committed-by: zhangyue --- docs/sdrs/api-ref/en-us_topic_0108184469.html | 11 ++++++++--- .../public_sys-resources/icon-arrowdn.gif | Bin 68 -> 1887 bytes .../public_sys-resources/icon-arrowrt.gif | Bin 70 -> 1890 bytes docs/sdrs/api-ref/sdrs_05_0501.html | 4 ++-- docs/sdrs/api-ref/sdrs_05_0503.html | 2 +- docs/sdrs/api-ref/sdrs_05_0603.html | 5 +++-- docs/sdrs/api-ref/sdrs_05_0604.html | 3 ++- docs/sdrs/api-ref/sdrs_05_0606.html | 3 ++- 8 files changed, 18 insertions(+), 10 deletions(-) diff --git a/docs/sdrs/api-ref/en-us_topic_0108184469.html b/docs/sdrs/api-ref/en-us_topic_0108184469.html index 77b68188c..7dd6ce4c8 100644 --- a/docs/sdrs/api-ref/en-us_topic_0108184469.html +++ b/docs/sdrs/api-ref/en-us_topic_0108184469.html @@ -8,7 +8,12 @@ -

2022-08-31

+

2023-02-10

+ +

Added the description of newly supported disk types in Querying Replication Pairs, Querying Details About a Replication Pair, and Changing the Name of a Replication Pair.

+ + +

2022-08-31

Deleted the yearly/monthly billing from the parameter description of some APIs.

@@ -77,7 +82,7 @@

2018-10-12

Modified the following content:

- +

2018-09-29

@@ -105,7 +110,7 @@

Added the following content:

Modified the following content:

-
  • Error code descriptions in Error Codes
  • Changed SDRS.0218 to SDRS.0219.
  • Descriptions of dr_type
+
  • Error code descriptions in Error Codes
  • Changed SDRS.0218 to SDRS.0219.
  • Descriptions of dr_type

Deleted the following content:

  • Section "Adding a NIC to a Protected Instance"
  • Section "Deleting a NIC from a Protected Instance"
diff --git a/docs/sdrs/api-ref/public_sys-resources/icon-arrowdn.gif b/docs/sdrs/api-ref/public_sys-resources/icon-arrowdn.gif index 84eec9be2f2ce458e888f8a9b803f9387247726a..379428032932289326e52c2772bd90ba3d88b906 100644 GIT binary patch literal 1887 zcmZ?wbhEHbCgqow z*eU^C3h_d20o>TUVm+{T^pf*)^(zt!^bPe4Kwg3=^!3HBG&dKny0|1L72#g21{a4^ z7NqJ2r55Lx7A2Jm>Ih`8X1|p zSh~8p7&*iAy5uL9=BDPA!1Sgd^t#~G3rY&P1wfl!Qj0RnQd8WD@^clyUbf1_?G{Iz z=0WwQ;C71>PQCg-$LND17Ac}(Lcr7mV#1RxkONQnsd>QEUIa|mjQ{`r{qy_R&mZ5v zef{$J)5j0*-@SeF`qj%9&!0Vg^7zri2lwyYy>t84%^TORUA=Po(!~qs&z(JU`qar2 z$B!L7a`@1}1N-;w-Lrew&K=vgZQZhY)5ZeMTG_VdAT{+S(zE> zX{jm6Nr?&Zaj`McQIQehVWA3>*p!%p5Wn0u7E$th{n6D>ft^YU5&dnB%c=(a~-RV>2EO25SIA CZ-yWM literal 68 zcmZ?wbhEHbzkByxQ$u Mo$o?7J5~m305MV#!~g&Q diff --git a/docs/sdrs/api-ref/public_sys-resources/icon-arrowrt.gif b/docs/sdrs/api-ref/public_sys-resources/icon-arrowrt.gif index 39583d168d6db303b366b5b8c1780698a6bb6017..6aaaa11c23e919c4798d7dcd2b1ae98dd35dd316 100644 GIT binary patch literal 1890 zcmZ?wbhEHb7yetOgf{ zR2HP_2c;J0mlh?b0+lO+tSYc_E=o--$uA1Y&(DE{Vn9ZINq%ugeu08>u$h8JcxGNo zetEGbSiP^Wm1kaYNn&1ds;7&s63_&_%*+%k11Cod14Ab>6ALqQLqk^=3j-5FHzP|& zBUd9gQwvj9m|mCsATTyHM;rzL?XHK6w zdE)r7qel)OI(T6JzP)>P@7lRz`?jrHHgDRvVg0(bYgVsXxnlXUrArnsTDV~Tyt#8` z&zd=7`n0K2CQq6;p}()Ur@O1OqrI)QrMaoGp}wxRrn;)KqP(oMq`0WCAU`iRCp#-M zBRwrOB{?ZEAwDiPCORrIB0MZKBseHAz~9f;$J@)(!`;o*#o5Wx!QRf+#@fo#!raW% z#MsEtKwnQ+M_Wr%LtRZ(MOjHvL0(Q)Mp{ZzLR?H#L|8~rfS-?-hntI&gPo0)g_((w zfkE*n3y@@B&;b#k`jUY|nSq%>!ec`MLnAA%oR7zc2TpB#@>)|YCO&lN;uMU!b7Eqm H1A{dHTIz>f literal 70 zcmZ?wbhEHbCreating a Protected Instance

Function

This API is used to create a protected instance. When a protected instance is created, the default name of the server at the DR site is the same as that of the server at the production site, but their IDs are different. To modify a server name, click the server name on the protected instance details page to switch to the server details page and modify the server name. Alternatively, you can call the API in Changing the Name of a Protected Instance to modify the name.

-

Constraints and Limitations

  • status of the protection group must be available or protected.
  • No shared disk has been attached to the server.
  • No protected instance has been created using the server.
  • The server must be in the same VPC as the protection group.
  • The physical host housing the production site server cannot be a DeH.
  • If protection is enabled for servers created during capacity expansion of an Auto Scaling (AS) group, these servers cannot be deleted when the capacity of the AS group is reduced.
  • If the server at the production site runs Windows and you choose the key login mode, ensure that the key pair of the server exists when you create a protected instance. Otherwise, the server at the DR site may fail to create, causing the protected instance creation failure.

    If the key pair of the production site server has been deleted, create a key pair with the same name.

    +

    Constraints and Limitations

    • status of the protection group must be available or protected.
    • No shared disk has been attached to the server.
    • One server can be used to create only one protected instance.
    • The server must be in the same VPC as the protection group.
    • The physical host housing the production site server cannot be a DeH.
    • If protection is enabled for servers created during capacity expansion of an Auto Scaling (AS) group, these servers cannot be deleted when the capacity of the AS group is reduced.
    • If the server at the production site runs Windows and you choose the key login mode, ensure that the key pair of the server exists when you create a protected instance. Otherwise, the server at the DR site may fail to create, causing the protected instance creation failure.

      If the key pair of the production site server has been deleted, create a key pair with the same name.

    • After you create a protected instance and enable protection on servers at the production site, modifications to the Hostname, Name, Security Group, Agency, ECS Group, Tags, and Auto Recovery configurations of servers on the production site will not synchronize to the servers at the DR site. You can manually add the configuration items to the servers at the DR site on the management console.
    @@ -161,7 +161,7 @@

    Type

    -

    Description

    +

    Description

    diff --git a/docs/sdrs/api-ref/sdrs_05_0503.html b/docs/sdrs/api-ref/sdrs_05_0503.html index d04a559be..c567691d0 100644 --- a/docs/sdrs/api-ref/sdrs_05_0503.html +++ b/docs/sdrs/api-ref/sdrs_05_0503.html @@ -87,7 +87,7 @@

    Integer

    -

    Specifies the offset of each request. The default value is 0. The value must be a number and cannot be negative.

    +

    Specifies the offset of each request. The default value is 0. The value must be a positive integer and cannot be negative.

    status

    diff --git a/docs/sdrs/api-ref/sdrs_05_0603.html b/docs/sdrs/api-ref/sdrs_05_0603.html index 2194eaf79..058473344 100644 --- a/docs/sdrs/api-ref/sdrs_05_0603.html +++ b/docs/sdrs/api-ref/sdrs_05_0603.html @@ -288,7 +288,7 @@

    String

    Specifies the time when a replication pair was updated.

    -

    The default format is as follows: ""yyyy-MM-ddTHH:mm:ss.SSSSSS", for example, 2019-04-01T12:00:00.000000.

    +

    The default format is as follows: ""yyyy-MM-ddTHH:mm:ss.SSSSSS", for example, 2019-04-01T12:00:00.000000.

    record_metadata

    @@ -371,7 +371,8 @@

    String

    Specifies the type of the disk in a replication pair.

    -
    Currently, the value can be SSD, SAS, SATA, co-p1, uh-l1, GPSSD, or ESSD.
    • SSD: specifies the ultra-high I/O disk type.
    • SAS: specifies the high I/O disk type.
    • SATA: specifies the common I/O disk type.
    • co-p1: specifies the high I/O (performance-optimized I) disk type.
    • uh-l1: specifies the ultra-high I/O (latency-optimized) disk type.
    • GPSSD: specifies the general purpose SSD disk type.
    • ESSD: specifies the extreme SSD disk type.

      Disks of the co-p1 and uh-l1 types are used exclusively for HPC ECSs and SAP HANA ECSs.

      +
      The value can be SSD, SAS, SATA, co-p1, or uh-l1.
      • SSD: the ultra-high I/O type
      • SAS: the high I/O type
      • SATA: the common I/O type
      • co-p1: the high I/O (performance-optimized I) type
      • uh-l1: the ultra-high I/O (latency-optimized) type

      • The co-p1 and uh-l1 types of disks are used exclusively for HPC ECSs and SAP HANA ECSs.

        +

        The extreme SSD type is currently not supported.

      diff --git a/docs/sdrs/api-ref/sdrs_05_0604.html b/docs/sdrs/api-ref/sdrs_05_0604.html index c71593629..820715c9a 100644 --- a/docs/sdrs/api-ref/sdrs_05_0604.html +++ b/docs/sdrs/api-ref/sdrs_05_0604.html @@ -253,7 +253,8 @@

      String

      Specifies the type of the disk in a replication pair.

      -
      Currently, the value can be SSD, SAS, SATA, co-p1, uh-l1, GPSSD, or ESSD.
      • SSD: specifies the ultra-high I/O disk type.
      • SAS: specifies the high I/O disk type.
      • SATA: specifies the common I/O disk type.
      • co-p1: specifies the high I/O (performance-optimized I) disk type.
      • uh-l1: specifies the ultra-high I/O (latency-optimized) disk type.
      • GPSSD: specifies the general purpose SSD disk type.
      • ESSD: specifies the extreme SSD disk type.

        Disks of the co-p1 and uh-l1 types are used exclusively for HPC ECSs and SAP HANA ECSs.

        +
        The value can be SSD, SAS, SATA, co-p1, or uh-l1.
        • SSD: the ultra-high I/O type
        • SAS: the high I/O type
        • SATA: the common I/O type
        • co-p1: the high I/O (performance-optimized I) type
        • uh-l1: the ultra-high I/O (latency-optimized) type

        • The co-p1 and uh-l1 types of disks are used exclusively for HPC ECSs and SAP HANA ECSs.

          +

          The extreme SSD type is currently not supported.

        diff --git a/docs/sdrs/api-ref/sdrs_05_0606.html b/docs/sdrs/api-ref/sdrs_05_0606.html index 469f95d42..1ca7a5f37 100644 --- a/docs/sdrs/api-ref/sdrs_05_0606.html +++ b/docs/sdrs/api-ref/sdrs_05_0606.html @@ -313,7 +313,8 @@

        String

        Specifies the type of the disk in a replication pair.

        -
        Currently, the value can be SSD, SAS, SATA, co-p1, uh-l1, GPSSD, or ESSD.
        • SSD: specifies the ultra-high I/O disk type.
        • SAS: specifies the high I/O disk type.
        • SATA: specifies the common I/O disk type.
        • co-p1: specifies the high I/O (performance-optimized I) disk type.
        • uh-l1: specifies the ultra-high I/O (latency-optimized) disk type.
        • GPSSD: specifies the general purpose SSD disk type.
        • ESSD: specifies the extreme SSD disk type.

          Disks of the co-p1 and uh-l1 types are used exclusively for HPC ECSs and SAP HANA ECSs.

          +
          The value can be SSD, SAS, SATA, co-p1, or uh-l1.
          • SSD: the ultra-high I/O type
          • SAS: the high I/O type
          • SATA: the common I/O type
          • co-p1: the high I/O (performance-optimized I) type
          • uh-l1: the ultra-high I/O (latency-optimized) type

          • The co-p1 and uh-l1 types of disks are used exclusively for HPC ECSs and SAP HANA ECSs.

            +

            The extreme SSD type is currently not supported.