Add-HpcNodeSet
Adds a set of Azure nodes to the HPC cluster.
Syntax
Add-HpcNodeSet
-Template <HpcNodeTemplate>
-Quantity <Int32>
-Size <String>
[-ClusterConnectionString <String[]>]
[-Scheduler <String[]>]
[<CommonParameters>] Description
The Add-HpcNodeSet cmdlet adds the specified number of Azure nodes with the specified virtual machine size to the HPC cluster by using the specified node template.
Examples
Example 1: Add nodes with a template: Add nodes with a template
PS C:\>Get-HpcNodeTemplate -Name "MyWorkerNodeTemplate" | Add-HpcNodeSet -Quantity 500 -Size "Large"This command gets an HpcNodeTemplate object for the node template named MyWorkerNodeTemplate, and then adds 500 large worker nodes to the HPC cluster by using that node template.
Parameters
-ClusterConnectionString
Specifies an array of cluster connection strings for the cluster on which you perform the operation.
The value format is host1, host2, host3.
If you do not specify the ClusterConnectionString parameter, this cmdlet uses the connection string on the head node that the CCP_CONNECTIONSTRING environment variable specifies.
To set this environment variable, run the following cmdlet: Set-Content Env: CCP_CONNECTIONSTRING \<head_node_name\>
This parameter was introduced in HPC Pack 2016.
| Type: | String[] |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Quantity
Specifies the number of Azure nodes that you want to add to the HPC cluster. You can specify a value from 1 through 1000. Ensure that the number is within the quota of role instances in the Azure subscription.
| Type: | Int32 |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Scheduler
Specifies the host name or IP address of the head node for the cluster to which you want to add Azure nodes. The value must be a valid computer name or IP address. If you do not specify the Scheduler parameter, this cmdlet uses the scheduler on the head node that the CCP_SCHEDULER environment variable specifies. To set this environment variable, run the following cmdlet:
Set-Content Env:CCP_SCHEDULER \<head_node_name\>
| Type: | String[] |
| Position: | Named |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Size
Specifies a predefined virtual machine size of the Azure nodes that is supported in HPC Pack. The size of the virtual machine determines characteristics such as the number of CPU cores, the memory capacity, and the local file system size of each node.
For more information, see Virtual Machine Sizes for Azurehttp://go.microsoft.com/fwlink/?LinkId=294911.
| Type: | String |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
-Template
Specifies an HpcNodeTemplate object that corresponds to the node template that you want to associate with the Azure nodes that you want to add to the HPC cluster.
The node template that you specify must be an Azure node template. An error occurs if you specify a different type of node template.
| Type: | HpcNodeTemplate |
| Position: | Named |
| Default value: | None |
| Required: | True |
| Accept pipeline input: | True |
| Accept wildcard characters: | False |
Inputs
HpcNodeTemplate
Outputs
HpcNode[]
Notes
- To add Azure nodes of different sizes, run this command separately for each size.
- All of the nodes that you add to an HPC cluster by using a specific Azure node template define a set of nodes that can be deployed and managed together in Azure when you start the nodes. This set includes nodes that you add later by using the same node template.
- This cmdlet was introduced in HPC Pack 2008 R2 with Service Pack 1 (SP1). It is not supported in previous versions.