All Products
Search
Document Center

Elastic High Performance Computing:AddNodes

Last Updated:Apr 09, 2024

Adds one or more compute nodes to an E-HPC cluster.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
ehpc:AddNodesWRITE
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
ClusterIdstringYes

The ID of the E-HPC cluster.

You can call the ListClusters operation to query the cluster ID.

ehpc-hz-FYUr32****
ImageOwnerAliasstringNo

The type of the image. Valid values:

  • system: public image
  • self: custom image
  • others: shared image
  • marketplace: Alibaba Cloud Marketplace image

Default value: system.

system
ImageIdstringNo

The ID of the image that is specified for the compute nodes. The image must meet the following requirements:

  • The operating system that is specified by the image must be the same as that of the existing cluster nodes. For example, if the operating system of the cluster nodes is CentOS, you can select only a CentOS image.
Note If you add nodes to a hybrid cloud cluster that supports multiple operating systems, you can select a Windows Server image or a CentOS image when the operating system of nodes is Windows.
  • The major version of the image specified for the compute nodes that you want to add is the same as that of the image of the cluster. For example, if the version of the cluster image is CentOS 7.x, the version of the image specified for the compute nodes must be CentOS 7.x.

You can call the ListImages and ListCustomImages operations to query the image ID.

centos_7_06_64_20G_alibase_20190711.vhd
CountintegerYes

The number of compute nodes that you want to add. Valid values: 1 to 99. The value of this parameter is greater than that of the MinCount parameter.

  • If the number of available ECS instances is less than the value of the MinCount parameter, the compute nodes cannot be added.
  • If the number of available ECS instances is greater than the value of the MinCount parameter and less than that of the Count parameter, the compute nodes are added based on the value of the MinCount parameter.
  • If the number of available ECS instances is greater than the value of the Count parameter, the compute nodes are added based on the value of the Count parameter.
10
InstanceTypestringNo

The instance type of the compute nodes. The default value is the instance type that was specified when you created the E-HPC cluster or the last time when you added compute nodes.

ecs.n1.tiny
ComputeSpotStrategystringNo

The preemption policy of the compute nodes. The parameter only takes effect when EcsChargeType is set to PostPaid. Valid values:

  • NoSpot: The instance is a regular pay-as-you-go instance.
  • SpotWithPriceLimit: The policy applies to preemptible instances for which a maximum hourly price is specified.
  • SpotAsPriceGo: The compute nodes are preemptible instances for which the market price at the time of purchase is used as the bid price.

Default value: NoSpot.

NoSpot
ComputeSpotPriceLimitstringNo

The maximum hourly price of the compute nodes. The value can be accurate to three decimal places. The parameter only takes effect when SpotStrategy is set to SpotWithPriceLimit.

0.68
EcsChargeTypestringNo

The billing method of the compute nodes. Valid values:

  • PostPaid: pay-as-you-go
  • PrePaid: subscription

Default value: PostPaid.

If the parameter is set to PrePaid, auto-renewal is enabled by default. After the E-HPC cluster is released, auto-renewal is disabled.

PostPaid
PeriodintegerNo

The duration of the subscription. The unit of the duration is specified by the PeriodUnit parameter. The parameter only takes effect when InstanceChargeType is set to PrePaid. Valid values:

  • Valid values when PeriodUnit is set to Week: 1, 2, 3, and 4.
  • Valid values when PeriodUnit is set to Month: 1, 2, 3, 4, 5, 6, 7, 8, 9, 12, 24, 36, 48, and 60.

Default value: 1.

1
PeriodUnitstringNo

The unit of the subscription period of the resource. Valid values:

  • Week
  • Month

Default value: Month.

Month
AutoRenewstringNo

Specifies whether to enable auto-renewal. The parameter takes effect only when EcsChargeType is set to PrePaid. Valid values:

  • true: enables auto-renewal
  • false: disables auto-renewal

Default value: true.

true
AutoRenewPeriodintegerNo

The auto-renewal period of the subscription compute nodes. The parameter takes effect when AutoRenew is set to true.

  • Valid values when PeriodUnit is set to Week: 1, 2, and 3.
  • Valid values when PeriodUnit is set to Month: 1, 2, 3, 6, and 12.

Default value: 1.

1
JobQueuestringNo

The queue to which the compute nodes are added.

workq
CreateModestringNo

The mode in which the compute nodes are added. Valid values:

  • manual: The compute nodes are manually added.
  • autoscale: The compute nodes are automatically added.

Default value: manual.

manual
SystemDiskTypestringNo

The type of the system disk. Valid values:

  • cloud_efficiency: ultra disk
  • cloud_ssd: SSD
  • cloud_essd: enhanced SSD (ESSD)
  • cloud: basic disk. Disks of this type are retired.

Default value: cloud_efficiency.

cloud_ssd
SystemDiskSizeintegerNo

The size of the system disk. Unit: GiB.

Valid values: 40 to 500.

Default value: 40.

40
ZoneIdstringNo

The ID of the zone.

cn-hangzhou-b
VSwitchIdstringNo

The ID of the vSwitch.

vsw-bp1lfcjbfb099rrjn****
HostNamePrefixstringNo

The prefix of the hostname. You can specify the parameter to manage the compute nodes in an efficient manner.

compute
HostNameSuffixstringNo

The suffix of the hostname. You can specify the parameter to manage the compute nodes in an efficient manner.

01
ComputeEnableHtbooleanNo

Specifies whether to enable hyper-threading for the compute node. Valid values:

  • true
  • false

Default value: true.

true
AllocatePublicAddressbooleanNo

Specifies whether to allocate a public IP address to the compute nodes. Valid values:

  • true
  • false

Default value: false.

false
InternetChargeTypestringNo

The billing method of the elastic IP address (EIP). Valid values:

  • PayByBandwidth: pay-by-bandwidth
  • PayByTraffic: pay-by-traffic
PayByTraffic
InternetMaxBandWidthInintegerNo

The maximum inbound public bandwidth. Unit: Mbit/s. Valid values:

  • If the purchased outbound public bandwidth is less than or equal to 10 Mbit/s, the valid values of the parameter are 1 to 10 and the default value is 10.
  • If the purchased outbound public bandwidth is greater than 10 Mbit/s, the valid values of this parameter are 1 to the amount of the outbound bandwidth that is purchased.
10
InternetMaxBandWidthOutintegerNo

The maximum outbound public bandwidth. Unit: Mbit/s. Valid values: 0 to 100.

Default value: 0.

10
ClientTokenstringNo

The client token that is used to ensure the idempotence of the request. You can use the client to generate the token, but make sure that the token is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length. For more information, see How do I ensure the idempotence of a request?

123e4567-e89b-12d3-a456-426655440000
SystemDiskLevelstringNo

The performance level of the ESSD to be used as the system disk. Default value: PL1. Valid values:

  • PL0: A single ESSD can deliver up to 10,000 random read/write IOPS.
  • PL1: A single ESSD can deliver up to 50,000 random read/write IOPS.
  • PL2: A single ESSD can deliver up to 100,000 random read/write IOPS.
  • PL3: A single ESSD can deliver up to 1,000,000 random read/write IOPS.

Default value: PL1.

For more information about ESSD performance parameters, see ESSD .

PL0
MinCountintegerNo

The minimum number of the compute nodes that you want to add. Valid values: 1 to 99. The value of the parameter is less than that of the Count parameter.

  • If the number of available ECS instances is less than the value of the MinCount parameter, the compute nodes cannot be added.
  • If the number of available ECS instances is greater than the value of the MinCount parameter and less than that of the Count parameter, the compute nodes are added based on the value of the MinCount parameter.
  • If the number of available ECS instances is greater than the value of the Count parameter, the compute nodes are added based on the value of the Count parameter.

Default value: 1.

1
SyncbooleanNo

Specifies whether to set this operation as a synchronous operation. Valid values:

  • true
  • false

Default value: false.

false
DataDisksobject []No

The list of data disks.

DataDiskSizeintegerNo

The size of the data disk. Unit: GB.

Valid values: 40 to 500.

Default value: 40.

Valid values of N: 0 to 16.

40
DataDiskCategorystringNo

The type of the data disk. Valid values:

  • cloud_efficiency: ultra disk
  • cloud_ssd: SSD
  • cloud_essd: ESSD
  • cloud: basic disk

Default value: cloud_efficiency.

Valid values of N: 0 to 16.

cloud_efficiency
DataDiskDeleteWithInstancebooleanNo

Specifies whether the data disk is released when the node is released. Valid values:

  • true
  • false

Default value: true.

Valid values of N: 0 to 16.

true
DataDiskPerformanceLevelstringNo

The performance level of the ESSD used as the data disk. The parameter only takes effect only when the DataDisks.N.DataDiskCategory parameter is set to cloud_essd. Valid values:

  • PL0: A single ESSD can deliver up to 10,000 random read/write IOPS.
  • PL1: A single ESSD can deliver up to 50,000 random read/write IOPS.
  • PL2: A single ESSD can deliver up to 100,000 random read/write IOPS.
  • PL3: A single ESSD can deliver up to 1,000,000 random read/write IOPS.

Default value: PL1.

Valid values of N: 0 to 16.

PL1
DataDiskEncryptedbooleanNo

Specifies whether to encrypt the data disk. Valid values:

  • true
  • false

Default value: false.

Valid values of N: 0 to 16.

false
DataDiskKMSKeyIdstringNo

The KMS key ID of the data disk.

Valid values of N: 0 to 16.

0e478b7a-4262-4802-b8cb-00d3fb40826X
ComputeSpotDurationintegerNo

The protection period of the preemptible instance. Unit: hours. Valid values: 0 and 1. A value of 0 indicates that the preemptible instance has no protection period.

1
ComputeSpotInterruptionBehaviorstringNo

The interruption mode of the preemptible instance. Default value: Terminate. Set the value to Terminate, which indicates that the instance is released.

Terminate
NetworkInterfaceTrafficModestringNo

The communication mode of the ENI. Valid values:

  • Standard: uses the TCP communication mode.
  • HighPerformance: enables the Elastic RDMA Interface (ERI) and uses the remote direct memory access (RDMA) communication mode.
Standard
DnsConfigstringNo

The information about Domain Name System (DNS) settings.

"{\"DnsType\":\"PrivateZone\",\"DnsName\":\"xxxxx\"}"

Response parameters

ParameterTypeDescriptionExample
object
TaskIdstring

The ID of the task.

B745C159-3155-4B94-95D0-4B73D4D2****
RequestIdstring

The ID of the request.

B745C159-3155-4B94-95D0-4B73D4D2****
InstanceIdsarray

The instance IDs.

string
null

Examples

Sample success responses

JSONformat

{
  "TaskId": "B745C159-3155-4B94-95D0-4B73D4D2****",
  "RequestId": "B745C159-3155-4B94-95D0-4B73D4D2****",
  "InstanceIds": {
    "InstanceId": [
      "null"
    ]
  }
}

Error codes

HTTP status codeError codeError messageDescription
400InvalidParamsThe specified parameter %s is invalid.The specified parameter %s is invalid.
400NotEnabledYou have not enabled this serviceYou have not enabled this service
400InDebtYour account has overdue payments.Your account has overdue payments.
400InvaildSystemDiskSizeThe system disk size must be greater than or equal to image size.The system disk size must be greater than or equal to image size.
403TooManyComputesThe number of computing nodes exceeds the quota.The number of computing nodes exceeds the quota.
403TooManyLoginsThe maximum number of logged on nodes is exceeded.The maximum number of logged on nodes is exceeded. The default maximum value is 2.
403TooManySccThe maximum number of SCC instances is exceeded.The maximum number of SCC instances is exceeded. The default maximum value is 15.
403InvalidClusterStatusThe operation failed due to invalid cluster status.The cluster status does not support the operation.
403ConflictOptA conflicting operation is running.A conflicting operation is running. Please try again later.
403ImageNotSupportedThe specified image is not supported.The specified image does not exist. Change the image and try again.
403InvalidOptThe specified operation is invalid. Please try again later.The operation is unknown. Please check arguments and try again later.
404ImageNotFoundThe specified image does not exist.The specified image does not exist. Please verify the parameter.
404ClusterNotFoundThe specified cluster does not exist.The specified instance does not exist.
404VolumeNotFoundThe specified volume does not exist.The specified storage does not exist. Please verify the parameter.
404ManagerNotFoundThe manager nodes do not exist or their status is abnormal.The manager nodes do not exist or their status is abnormal.
404ObjectNotFoundThe specified object is not found.The specified object does not exist. Please verify the parameter.
404KeyPairNotFoundThe specified KeyPair does not exist.-
406EcsErrorAn error occurred while calling the ECS API operation.An error occurred while calling the ECS API operation.
406EipErrorThe EIP API request failed.EIP API request failed.
406DbErrorA database service error occurred.Database request failed.
406AliyunErrorAn Alibaba Cloud product error occurred.An Alibaba Cloud product error occurred.
407NotAuthorizedYou are not authorized by RAM for this request.The request is not authorized by RAM.
409PartFailurePart of the batch operation failed.Part of the batch operation failed.
500UnknownErrorAn unknown error occurred.An unknown error occurred.
503ServiceUnavailableThe request has failed due to a temporary failure of the serverThe request has failed due to a temporary failure of the server.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2023-06-29The Error code has changed. The request parameters of the API has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 406
    delete Error Codes: 407
    delete Error Codes: 409
    delete Error Codes: 500
    delete Error Codes: 503
Input ParametersThe request parameters of the API has changed.
    Added Input Parameters: DnsConfig
2023-06-27The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 404 change
    delete Error Codes: 400
    delete Error Codes: 403
    delete Error Codes: 406
    delete Error Codes: 407
    delete Error Codes: 409
    delete Error Codes: 500
    delete Error Codes: 503
2023-03-06The Error code has changed. The request parameters of the API has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 403 change
    delete Error Codes: 400
    delete Error Codes: 404
    delete Error Codes: 406
    delete Error Codes: 407
    delete Error Codes: 409
    delete Error Codes: 500
    delete Error Codes: 503
Input ParametersThe request parameters of the API has changed.
    Added Input Parameters: NetworkInterfaceTrafficMode
2021-12-23The Error code has changed. The request parameters of the API has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
    delete Error Codes: 403
    delete Error Codes: 404
    delete Error Codes: 406
    delete Error Codes: 407
    delete Error Codes: 409
    delete Error Codes: 500
    delete Error Codes: 503
Input ParametersThe request parameters of the API has changed.
    Added Input Parameters: DataDisks