Add-HpcUnManagedNode

Add-HpcUnManagedNode

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

Syntax

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

Parameter Set: GroupName
Add-HpcUnManagedNode [-GroupName] <String> [-ClusterConnectionString <String[]> ] [-Memory <Int32> ] [-Name <String> ] [-Scheduler <String[]> ] [-SubscribedCores <Int32> ] [-SubscribedSockets <Int32> ] [ <CommonParameters>]




Detailed 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.

Parameters

-ClusterConnectionString<String[]>

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.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Group<HpcGroup>

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


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

True (ByValue)

Accept Wildcard Characters?

false

-GroupName<String>

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


Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Memory<Int32>

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.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Name<String>

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


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Scheduler<String[]>

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>


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-SubscribedCores<Int32>

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).


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-SubscribedSockets<Int32>

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).


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

Notes

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

Community Additions

ADD
Show: