Add-HpcUnManagedNode

  • Reference
Module:
HPCPack2016

Adds unmanaged compute resources to the cluster as a compute node.

Syntax

Add-HpcUnManagedNode
   [-Name <String>]
   [-SubscribedCores <Int32>]
   [-SubscribedSockets <Int32>]
   [-Memory <Int32>]
   [-GroupName] <String>
   [-ClusterConnectionString <String[]>]
   [-Scheduler <String[]>]
   [<CommonParameters>]
Add-HpcUnManagedNode
   [-Name <String>]
   [-SubscribedCores <Int32>]
   [-SubscribedSockets <Int32>]
   [-Memory <Int32>]
   -Group <HpcGroup>
   [-ClusterConnectionString <String[]>]
   [-Scheduler <String[]>]
   [<CommonParameters>]

Description

The Add-HpcUnManagedNode cmdlet adds unmanaged compute resources to the cluster as a compute node. The HPC job scheduler service must be configured to use the unmanaged resources.

Examples

1:

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

-Group

Specifies the HpcGroup object for the node group to which the node is added. You cannot specify both the Group and GroupName parameters.

Type:HpcGroup
Position:Named
Default value:None
Required:True
Accept pipeline input:True
Accept wildcard characters:False

-GroupName

Specifies the name of the node group to which the node is added. You cannot specify both the Group and GroupName parameters.

Type:String
Position:1
Default value:None
Required:True
Accept pipeline input:False
Accept wildcard characters:False

-Memory

Specifies the amount of memory in megabytes (MB) that you want the HPC job scheduler service to use when it is allocating tasks to the node.

Type:Int32
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-Name

Specifies a name for the unmanaged node that you want to add to the cluster.

Type:String
Position:Named
Default value:None
Required:False
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 add the node. 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

-SubscribedCores

Specifies the number of cores that you want the HPC job scheduler service to use when it is allocating tasks to the node. This value may be smaller than, or exceed the number of physical cores. To clear this property, set the value to $Null. If this value is $Null, the number of physical cores is used.

You should ensure that the number of subscribed cores is divisible by the number of subscribed sockets. Therefore, each socket must have the same number of cores (for example 4 cores and 2 sockets are valid, but 10 cores and 4 sockets are not).

Type:Int32
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-SubscribedSockets

Specifies the number of sockets that the HPC job scheduler service should use when it is allocating tasks to the node. This value may be smaller than, or exceed the number of actual physical sockets. To clear this property, set the value to $Null.

You should ensure that the number of subscribed cores is divisible by the number of subscribed sockets. Therefore, each socket must have the same number of cores (for example 4 cores and 2 sockets are valid, but 10 cores and 4 sockets are not).

Type:Int32
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

Notes

  • This cmdlet was introduced in HPC Pack 2012 R2 Update 1. It is not supported in previous versions.