All Products
Search
Document Center

Create a cluster by using a template

Last Updated: Sep 07, 2021

The Elastic High Performance Computing (E-HPC) console provides various default cluster templates so that you can create an E-HPC cluster based on these templates.

Background information

Default templates specify the required parameters of creating a cluster, such as zone, deployment mode, and image type. You can select a template based on your business requirements.

The following default templates are provided by E-HPC: Pay-as-you-go Standard Template, Subscription Standard Template, and Pay-as-you-go Tiny Template. In this topic, Pay-as-you-go Standard Template is used as an example.

Procedure

  1. Log on to the E-HPC console.

  2. In the top navigation bar, select a region.

  3. In the left-side navigation pane, click Cluster.

  4. On the Cluster page, move the pointer over the drop-down icon next to Create Cluster and click Cluster Template.

  5. In the Basic Configurations section of the Create Cluster page, enter the cluster name and logon password.

  6. Click the Template icon and select Pay-as-you-go Standard from the drop-down list.

    After you select Pay-as-you-go Standard Template, the configurations of the script and topology on the current page are changed. You can modify the script and topology based on your needs.

    [Global]
    zoneId=cn-hangzhou-i
    ecsChargeType=PostPaid
    [Node]
    deployMode=Standard
    ecsOrderComputeInstanceType=ecs.sn1.medium
    ecsOrderComputeCount=1
    ecsOrderManagerInstanceType=ecs.sn1.medium
    ecsOrderLoginInstanceType=ecs.sn1.medium
    systemDiskSize=40
    [Image]
    osTag=CentOS_7.6_64
    imageOwnerAlias=system
    [Network]
    vpcId=vpc-bp1l7wl0npokhvwv3****
    vSwitchId=vsw-bp1ugito40bbf4rli****
    securityGroupId=
    [Storage]
    volumeId=02d104****
    volumeMountpoint=02d104****-alj27.cn-hangzhou.nas.aliyuncs.com
    [Scheduler]
    schedulerType=pbs
    [Account]
    accountType=nis
    [Application]
    applicationInfo=OPENMPI_3.0.0

    Parameter

    Required

    Example

    Description

    ZoneId

    Yes

    cn-hangzhou-i

    The zone to which the cluster belongs.

    If you change the zone, the vpcId, vSwitchId, volumeMountpoint, and volumeId parameters are automatically changed based on the new zone.

    EcsChargeType

    Yes

    PostPaid

    The billing method of the Elastic Compute Service (ECS) instance that is used by the cluster. Valid values:

    • PostPaid: pay-as-you-go

    • PrePaid: subscription

    Period

    No

    1

    The billing cycle of the ECS instance.

    If EcsChargeType is set to PrePaid, this parameter is required. Otherwise, this parameter is unavailable.

    Valid values: 1 to 100

    PeriodUnit

    No

    Month

    The unit of the billing cycle. Valid values:

    • Week

    • Month

    • Year

    If EcsChargeType is set to PrePaid, this parameter is required. Otherwise, this parameter is unavailable.

    DeployMode

    Yes

    Standard

    The deployment mode of the cluster. Valid values:

    • Standard: An account node, a scheduling node, a logon node, and multiple compute nodes are deployed.

    • Simple: A management node, a logon node, and multiple compute nodes are deployed. The management node consists of an account node and a scheduling node.

    • Tiny: A management and multiple compute nodes are deployed. The management node consists of an account node, a scheduling node, and a logon node.

    EcsOrderComputeInstanceType

    No

    ecs.sn1.medium

    The instance type of compute nodes.

    By default, the instance types of compute nodes and management nodes are the same. You can go to the ECS buy page to query the available instance types in the current region.

    EcsOrderComputeCount

    No

    1

    The number of compute nodes.

    Default value: 1

    EcsOrderLoginInstanceType

    No

    ecs.sn1.medium

    The instance type of logon nodes.

    By default, the instance types of logon nodes and management nodes are the same.

    EcsOrderManagerInstanceType

    Yes

    ecs.sn1.medium

    The instance type of management nodes.

    You can go to the ECS buy page to query the available instance types in the current region.

    SystemDiskSize

    Yes

    40

    The size of the system disk.

    Valid values: 40 to 500. Unit: GB.

    OsTag

    Yes

    CentOS_7.6_64

    The type of the operating system. Valid values:

    • CentOS_6.9_64

    • CentOS_7.2_64

    • CentOS_7.3_64

    • CentOS_7.4_64

    • CentOS_7.5_64

    • CentOS_7.6_64

    • CentOS_8.0_64

    • Windows Server 2019 Data Center Edition 64bit Chinese Edition

    • Windows Server 2019 Data Center Edition 64bit English Edition

    • Windows Server 2016 Data Center Edition 64bit Chinese Edition

    • Windows Server 2016 Data Center Edition 64bit English Edition

    • Windows Server 2012 R2 Data Center Edition 64bit Chinese Edition

    • Windows Server 2012 R2 Data Center Edition 64bit English Edition

    • Windows Server 2008 R2 Enterprise 64bit Chinese Edition

    • Windows Server 2008 R2 Enterprise 64bit English Edition

    ImageOwnerAlias

    Yes

    system

    The image type. Valid values:

    • system: specifies a public image. Public images are supported regardless of the OsTag parameter value.

    • self: specifies a custom image.

    • others: specifies a shared image.

    VpcId

    Yes

    vpc-bp1l7wl0npokhvwv3****

    The ID of the VPC.

    You can log on to the VPC console to query the VPC ID.

    VSwitchId

    Yes

    vsw-bp1ugito40bbf4rli****

    The ID of the vSwitch in the specified VPC.

    If you leave this parameter empty, a vSwitch is automatically created. If you specify the VpcId parameter, this parameter is required.

    SecurityGroupId

    Yes

    sg-bp17lchxr133z9gt****

    The ID of the security group.

    If you leave this parameter empty, a security group is automatically created. You can go to the Security Groups page of the Elastic Compute Service console to query the security group ID.

    VolumeId

    Yes

    02d104****

    The ID of the NAS file system.

    If you leave this parameter empty, a NAS file system is automatically created. You can log on to the NAS file system to query the file system ID.

    VolumeMountpoint

    Yes

    02d104****-alj27.cn-hangzhou.nas.aliyuncs.com

    The ID of the mount target.

    If you leave this parameter empty, a mount target is automatically created.

    SchedulerType

    Yes

    pbs

    The type of the scheduler. Valid values:

    • pbs

    • slurm

    • deadline

    • custom

    • opengridscheduler

    • gridengine

    • cube

    Note

    • You can set this parameter to custom only if you use a Windows Server operating system.

    • You can set this parameter to gridengine only if you use the CentOS_6.9_64 operating system.

    • You can set this parameter to opengridscheduler or deadline only if you use the CentOS_7.2_64, CentOS_7.3_64, CentOS_7.4_64, CentOS_7.5_64, or CentOS_7.6_64 operating system.

    AccountType

    Yes

    nis

    The management service type of the domain account. Valid values:

    • nis

    • ldap

    ApplicationInfo

    Yes

    OPENMPI_3.0.0

    The type of the application.

    Separate multiple applications with commas (,), for example, applicationInfo=OPENMPI_3.0.0,mpich_3.2.

    ComputeSpotStrategy

    No

    SpotAsPriceGo

    The bidding method of compute nodes. Valid values:

    • SpotWithPriceLimit: The compute nodes are preemptible instances that have a maximum hourly price.

    • SpotAsPriceGo: The compute nodes are priced at the market price at the time of purchase. You can specify this parameter in the Global section of the script to enable preemptible instances.

    ComputeSpotPriceLimit

    No

    0.060

    The maximum hourly price of the instances. The value must be a floating-point number.

    If you set ComputeSpotStrategy to SpotWithPriceLimit, this parameter is required. You can specify this parameter in the Application section of the script.

    PostScriptUrl

    No

    http://e-hpc-hangzhou.oss-cn-hangzhou.aliyuncs.com/packages/example.sh

    The URL that is used to download the script after the cluster is created.

    PostScriptArgs

    No

    chmod +x example.sh

    The parameters that are used to run the script after the cluster is created.

  7. After the configuration is completed, read and select Alibaba Cloud International Website Product Terms of Service, and then click OK.

Result

After you create the cluster, you can check its status on the Cluster page. If the cluster and all cluster nodes are in the Running state, the cluster is created.

Related operations

  • Click the Open icon and import a cluster template that you configured so that you can create a cluster based on the template.

  • Create a cluster template and click the Save icon to save the template file, for example, ClusterConfig.ini. This way, you can use the cluster template for future use.