Export (0) Print
Expand All

Step 3: Configure the Head Node

Updated: August 2, 2010

Applies To: Windows HPC Server 2008 R2

After you have deployed the head node of your HPC cluster, you must configure the head node by following the Deployment To-do List in HPC Cluster Manager.

Checklist: Configure the head node

The following checklist includes the items in the Deployment To-do List in HPC Cluster Manager that you need to complete in order to configure your head node.

 

Task Description

3.1. Configure the HPC cluster network

Configure the cluster network by using the Network Configuration Wizard.

3.2. Provide installation credentials

Specify which credentials to use for system configuration and when adding new nodes to the cluster.

3.3. Configure the naming of new nodes

Specify the naming convention to use when generating names automatically for new nodes.

3.4. Create a node template

Create a template that defines the steps to follow when configuring a new node.

3.5. Add drivers for the operating system images

If you will be deploying nodes from bare metal and those nodes require special device drivers, add drivers for the operating system images that you created for your node template on the previous task.

3.6. Add users

If you will be giving access to the cluster to other members of your organization, add them as HPC cluster users or HPC cluster administrators on the cluster.

3.1. Configure the HPC cluster network

The HPC cluster network configuration is the first step in the configuration process of your head node. The HPC cluster network is configured by following the Network Configuration Wizard in HPC Cluster Manager. When configuring the HPC cluster network, you must choose the network topology that you have selected for your cluster, as described in “1.7. Choose a network topology for your cluster”, in Step 1: Prepare for Your Deployment.

ImportantImportant
Before you start configuring the HPC cluster network in HPC Cluster Manager, ensure that the head node and the computers that you will add as nodes to the cluster are physically connected according to the network topology that you have chosen for your cluster. Also, ensure that you are able to identify to which network each one of the network adapters in the head node is connected.

To configure the HPC cluster network

  1. If HPC Cluster Manager is not already open on the head node, open it. Click Start, point to All Programs, click Microsoft HPC Pack 2008 R2, and then click HPC Cluster Manager.

  2. In the Deployment To-do List, click Configure your network. The Network Configuration Wizard appears.

  3. On the Network Topology Selection page, click the topology that you have chosen for your cluster, and then click Next.

  4. On the Enterprise Network Adapter Selection page, in the Network adapter list, click the name of the network adapter that is physically connected to your enterprise network, and then click Next.

    ImportantImportant
    To ensure that you are selecting the correct network adapter, use the information displayed on this wizard page after you select a network adapter from the list. Use the IP address, domain information, and Media Access Control (MAC) address of each adapter as a reference.

  5. If you chose topology number 5 for your cluster, jump to step 9 in this procedure. Otherwise, repeat step 4 for the private network adapter.

  6. On the Private Network Configuration page, type a static IP address and a subnet mask for the head node. Optionally, select network services for that network:

    1. To give access to resources on the enterprise network to nodes that are connected to this network, select the Enable network address translation (NAT) on the head node check box.

    2. To enable DHCP services for the nodes that are connected to this network, select the Enable DHCP and define a scope check box, and then type the starting and ending IP addresses for the DHCP scope. If the Gateway and DNS server IP addresses have not been automatically detected, type each of these addresses.

    noteNote
    For more information about enabling NAT and DHCP on your cluster network, see “HPC network services” in Appendix 1: HPC Cluster Networking.

  7. Click Next after you are done configuring the private network.

  8. Repeat steps 4, 6, and 7 for the application network adapter. Click Next after you are done configuring the application network.

  9. On the Firewall Setup page, select the firewall setting for the cluster:

    1. To apply firewall settings automatically to the nodes on each network, click ON for that network.

    2. To disable the firewall on a network, click OFF.

    3. If you do not want to change any firewall settings, click Do not manage firewall settings.

    noteNote
    For more information about firewall settings for your cluster, see “Windows Firewall configuration” in Appendix 1: HPC Cluster Networking.

  10. On the Review page, verify your settings and click Configure. If you want to change any of the settings, navigate to the appropriate wizard page by clicking it on the navigation pane or by clicking Previous.

  11. After the network configuration process is completed, on the Configuration Summary page, review the list of configuration items. If you want to save a report of the network configuration, click Save the configuration report.

  12. To close the wizard, click Finish.

3.2. Provide installation credentials

Installation credentials must be provided in order to configure new nodes. These credentials will be used when installing the operating system and applications on the nodes, and when adding nodes to the Active Directory domain. For more information, see “1.6. Choose a user account for installation and diagnostics” in Step 1: Prepare for Your Deployment.

To provide installation credentials

  1. In the Deployment To-do List, click Provide installation credentials. The Installation Credentials dialog box appears.

  2. Type the user name, including the domain (DOMAIN\User), and then the password for the domain user account you will use to deploy nodes.

    ImportantImportant
    • The account must be a domain account with enough privileges to create Active Directory computer accounts for the nodes and to join the nodes to the domain. If the policies of your organization restrict you from using a domain account that can add new computers to the domain, you will need to ask your domain administrator to pre-create the computer objects for you in Active Directory Domain Services before you deploy your nodes. For more information, see Deploy Nodes with Pre-created Computer Objects in Active Directory (http://go.microsoft.com/fwlink/?LinkId=194363).

    • If part of your deployment requires access to resources on the enterprise network, the account should have the necessary permissions to access those resources.

    • If you want to restart nodes remotely by using HPC Cluster Manager, the account must be a member of the local Administrators group on the head node. This requirement is only necessary if you do not have scripted power control tools that you can use to remotely restart the nodes.

    • Active Directory Domain Services limits the number of computers that an authenticated user can join to the domain concurrently (the default is 10 computers). If you need to increase this number to configure new nodes, you (or your domain administrator) can use the Adsiedit tool to edit the ms-DS-MachineAccountQuota property in the domain. For information about how to do this, see the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=217946).

  3. To save the specified credentials, click OK.

3.3. Configure the naming of new nodes

If you will deploy nodes from bare metal, and you are not using a node XML file to import nodes to the cluster, computer names can be automatically generated for the new nodes that are being deployed. You need to specify how those names will be generated, by defining a naming series.

The naming series is defined by selecting a root name and the starting number that will accompany that name. The starting number is enclosed in percentage signs (%).

For example, if you deploy three nodes after specifying the following naming series: Node-%100%, those nodes will be assigned these names:

  • Node-100

  • Node-101

  • Node-102

ImportantImportant
Node names are limited to 15 characters. When specifying the node naming series, take into account the number of nodes in your deployment and ensure that the series that you specify will not generate names that exceed 15 characters. For example, if your deployment will consist of 1,000 nodes, and your starting number is 1, your root name cannot have more than 12 characters; otherwise, your node number 1,000 will need a name that consists of 16 characters.

To specify the node naming series

  1. In the Deployment To-do List, click Configure the naming of new nodes. The Specify Node Naming Series dialog box appears.

  2. Type the naming series that you want to use. The preview in the Specify Node Naming Series dialog box helps you to see an example of how the naming series will be applied to the names of the nodes.

    noteNote
    You cannot specify a node naming series that consists only of numbers.

  3. To save the node naming series that you have specified, click OK.

3.4. Create a node template

Node templates define the necessary tasks for configuring and adding nodes to your cluster. With a node template, you can deploy an operating system image, add specific drivers and software to nodes, add a preconfigured node to your cluster, or apply software updates to your nodes. Because you might have more than one type of node, or you may be adding nodes to your cluster in different ways, you can create different templates that apply to different nodes or situations.

Depending on the type of nodes that you want to add to your cluster, you can create three types of node templates:

  • Compute node template. Use this type of template to deploy compute nodes from bare metal or to add preconfigured compute nodes.

  • Broker node template. Use this type of template to deploy broker nodes from bare metal or to add preconfigured broker nodes.

  • Workstation node template. Use this type of template to add preconfigured workstation nodes, and to specify if you want workstation nodes to be brought online and offline according to a weekly availability policy or manually.

Compute node templates and broker node templates are further divided into two types, depending on how you want to add those types of nodes to your cluster:

  • With an operating system image. This type of template includes a step to deploy an operating system on the compute nodes or broker nodes. Use this type of template when adding nodes from bare metal.

  • Without an operating system image. This type of template is used to add preconfigured compute nodes or broker nodes to the cluster, or to update existing nodes.

The type of template that you create for the initial deployment of your HPC cluster depends on how you decided to add nodes to your cluster. For more information, see “1.2. Decide how to add nodes to your cluster” in Step 1: Prepare for Your Deployment.

ImportantImportant
If you will create a node template with an operating system image, you will need the installation media for Windows Server 2008 R2 HPC Edition or another edition of Windows Server 2008 R2 (compute nodes and broker nodes), or the installation media for Windows Server 2008 HPC Edition or another 64-bit edition of Windows Server 2008 (compute nodes only). Alternatively, you can have the installation files available on a network location that is accessible from the head node computer.

To create a node template

  1. In the Deployment To-do List, click Create a node template. The Create Node Template Wizard appears.

  2. On the Choose Node Template Type page, choose the type of node template that you want to create: Compute node template, Broker node template, or Workstation node template.

  3. On the Specify Template Name page, type a descriptive name for the template, and optionally a description, and then click Next.

  4. If you are creating a compute node template or a broker node template and you want to add nodes to your cluster from bare metal:

    1. On the Select Deployment Type page, click With operating system, and then click Next.

    2. On the Select Operating System Image page, if the operating system image that you want to use for your deployment is already listed in the Image Name list, click that image and then jump to step 4.f. If you want to use a different operating system image, on the Select Operating System Image page, click Add Image.

    3. On the Add Operating System Image dialog box, click Create a new operating system image, and then type or browse to the location of the Windows setup file for one of the supported operating systems for the nodes.

    4. Type a descriptive name for the new operating system image, and then click OK.

    5. After the image is added, in the Image Name list, click the image that you want to use with the template.

    6. Optionally, specify if you want to multicast the operating system image during deployment. For more information, see “1.8. Prepare for multicast” in Step 1: Prepare for Your Deployment.

    7. Optionally, specify if you want to include a product key to activate the operating system on the nodes, and then type the product key that should be used.

    8. Click Next to continue.

    9. On the Specify Local Administrator Password for Node page, click Use a specific password, and then type and confirm the password that you want to use.

    10. Click Next.

    11. On the Specify Windows Updates page, specify if you want to add a step in the template to download and install updates using Microsoft Update or the enterprise Windows Server Update Services (WSUS). Also, you can specify specific updates to be added to the template. Click Next to continue. Go to the last step in this procedure.

  5. If you are creating a compute node template or a broker node template and you want to add preconfigured nodes to your cluster:

    1. On the Select Deployment Type page, click Without operating system, and then click Next.

    2. On the Specify Windows Updates page, specify if you want to add a step in the template to download and install updates using Microsoft Update or the enterprise Windows Server Update Services (WSUS). Also, you can specify specific updates to be added to the template. Click Next to continue. Go to the last step in this procedure.

  6. If you are creating a workstation node template, on the Configure Availability Policy page, select how you want workstation nodes to be brought online and offline:

    1. If you want workstation nodes to be brought online and offline manually, select that option, and then click Next. Go to the last step in this procedure.

    2. If you want workstation nodes to be brought online and offline automatically, select that option, and then click Configure Availability Policy. The Configure Workstation Availability Policy dialog box appears.

    3. In the Configure Workstation Availability Policy dialog box, click and drag the mouse to select the days and hours at which nodes are Online (available to run cluster jobs) and Offline (not available to run cluster jobs).

    4. Optionally, specify the number of minutes before the workstation nodes are taken offline, when no new jobs will be started on the workstation nodes.

    5. To save your settings, click OK, and then click Next.

  7. On the Review page, click Create.

noteNote
The node templates that you create with the Create Node Template Wizard include the most common deployment and configuration tasks. You can add more tasks to the node templates that you create by using the Node Template Editor. For more information, see Appendix 3: Node Template Tasks and Properties.

ImportantImportant
If you edit a node template at the same time that nodes are being deployed with that node template, the changes that you make will be implemented immediately after you save your changes, affecting any nodes that are waiting to be deployed with that template. For that reason, before you open a node template for editing, determine if there are any nodes being deployed or waiting to be deployed, and if there are, ensure that none of those nodes use the template that you want to edit.

3.5. Add drivers for the operating system images

If you will be deploying nodes from bare metal by using a node that includes an operating system image, and those nodes require special device drivers, you will need to add those drivers to the operating system images stored on your head node. The drivers that you add must be in the .inf format, and must be accessible from the head node.

ImportantImportant
The device drivers that you add will be available to all operating system images in the image store, including those images that were created by capturing an existing node.

noteNote
It is recommended that you obtain the latest device drivers for your nodes from the websites of your hardware vendors.

To add drivers for the operating system images

  1. In the Deployment To-do List, under Optional deployment tasks, click Manage drivers. The Manage Drivers dialog box appears.

  2. Click Add, and then type or browse to the location of the setup information file for the driver that you want to add (.inf format)

  3. To add the driver to the list of drivers, click Open.

  4. Repeat the two previous steps for all the drivers that you want to add.

  5. After you are done adding drivers, click Close.

3.6. Add users

If you will be giving access to your cluster to other members of your organization, you need to add their domain user accounts or domain groups to the cluster in one of the following two HPC cluster user roles:

  • Administrator   HPC cluster administrators have permissions to manage all aspects of the cluster, including configuring the HPC cluster network, deploying and managing nodes, and configuring the HPC Job Scheduler Service. Cluster administrators can also submit and manage jobs, tasks, and job templates that are created in or submitted to the cluster by other users.

  • User   HPC cluster users have permissions to submit tasks and jobs to the cluster, and to manage tasks and jobs that they have submitted. When a job that was submitted by an HPC cluster user fails, the user is able to diagnose, repair, and resubmit that job. Although HPC cluster users can see the jobs that have been submitted by others users, they cannot cancel those jobs or resubmit them. Also, HPC cluster users cannot view the job details and tasks for jobs that they did not submit themselves.

Active Directory Domain Services (AD DS) is a prerequisite to installing HPC Pack 2008 R2 because the authentication process for users and computers relies on the services provided by AD DS.

At installation time, the Domain Admins group is added to the cluster as an HPC cluster administrator, and there are no HPC cluster users. You have to manually add domain users or domain groups as HPC cluster administrators, if they are not already members of the Domain Admins group.

When you add a new HPC cluster administrator on your cluster, the domain account for that user or group is automatically propagated to all compute nodes and broker nodes on the cluster, as a member of the local Administrators group of each node. In the case of workstation nodes, HPC cluster administrators are not propagated, so that user rights on the workstation nodes are not affected.

To be able to submit a job to the cluster, a domain user must be added as an HPC cluster user, or the domain user must be a member of a domain group that has been added as an HPC cluster user. HPC cluster users are not propagated to any type of node.

noteNote
For more information about HPC user roles, see Security Considerations for Designating HPC Cluster Users and Administrators in the Windows HPC Server Technical Library (http://go.microsoft.com/fwlink/?LinkId=194685).

ImportantImportant
To submit jobs to the cluster, a domain user must be at least an HPC cluster user.

To add users on the cluster

  1. In the Deployment To-do List, under Optional deployment tasks, click Add or remove users.

  2. To add an HPC cluster user:

    1. In the Actions pane, click Add User. The Select Users or Groups dialog box appears.

    2. Type the name of the domain user or group that you want to add as an HPC cluster user, and then click Check Names. For more information, on the Select Users or Groups window, click examples.

    3. Repeat the previous step for all HPC cluster users that you want to add.

    4. After you are done adding HPC cluster users, click OK.

  3. To add an HPC cluster administrator:

    1. In the Actions pane, click Add Administrator. The Select Users or Groups dialog box appears.

    2. Type the name of the domain user or group that you want to add as an HPC cluster administrator, and then click Check Names. For more information, on the Select Users or Groups window, click examples.

    3. Repeat the previous step for all administrators that you want to add.

    4. After you are done adding HPC cluster administrators, click OK.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft