A serverless cluster uses elastic container instances as compute nodes. You only need to provide packaged container images to run jobs.
Background information
Standard E-HPC clusters use Elastic Compute Service (ECS) instances as compute nodes, which require you to plan instance types and quantities in advance. A serverless cluster uses elastic container instances instead. The system automatically creates an elastic container instance for each job you submit. Each instance contains one container. After a job completes, the instance stops billing and is automatically released. You do not need to plan node capacity or manage servers — just provide packaged container images.
Elastic Container Instance combines container and serverless technologies. You can run containerized workloads without managing servers, and you are charged only for the resources your containers consume. For more information, see What is Elastic Container Instance?
Prerequisites
-
The service-linked roles for E-HPC and Elastic Container Instance are created. When you log on to each console for the first time, follow the prompts to create the service-linked role.
-
A virtual private cloud (VPC) and a vSwitch are created. For more information, see Create and manage a VPC and Create and manage a vSwitch.
Limits
The service is not available in the Indonesia (Jakarta) region.
Procedure
-
Go to the template configuration page.
-
Log on to the E-HPC console.
-
In the upper-left corner of the top navigation bar, select a region.
-
In the left-side navigation pane, choose Cluster.
-
In the upper-right corner of the Cluster page, hover over the
icon to the right of Create Cluster and click Cluster Template.
-
-
In the Basic Configurations section, enter the cluster name and logon password.
-
Above the template section, click
and select Batch Serverless. -
Configure template parameters.
The Batch Serverless template requires the following parameters. Modify the example values based on your business requirements.
[Global] clientVersion=2.1.0 [Node] deployMode=Managed [Network] vpcId=vpc-bp156zry1g8y8dv99**** vSwitchId=vsw-bp1xu3lkc9c9bpq32**** securityGroupId= [Storage] withoutNas=true [Scheduler] schedulerType=ServerlessBatchType
Parameter
Required
Example
Description
Global
clientVersion
Yes
2.1.0
The E-HPC client version. The latest version is used by default. We recommend that you keep the default value.
Node
deployMode
Yes
Managed
The cluster deployment mode. Set this parameter to Managed.
Network
vpcId
Yes
vpc-wz9lq2oynq8tia5h8****
The ID of the VPC for the cluster.
vSwitchId
Yes
vsw-wz992iw34x8on06he****
The vSwitch ID.
securityGroupId
No
sg-wz94ksuqlwb8iqh8****
The ID of the security group for the cluster.
Storage
withoutNas
Yes
true
Set this parameter to true to create the cluster without Apsara File Storage NAS as shared storage.
Scheduler
schedulerType
Yes
ServerlessBatch
The scheduler type. Set this parameter to ServerlessBatch.
-
In the upper-right corner of the page, read and select the OK, and then click OK.
-
Return to the Cluster page to check the cluster status.
The cluster is ready when its status changes to Running.