Share via

Getting Started with Compute Cluster Server 2003

  • Article

Applies To: Windows Compute Cluster Server 2003

This Getting Started Guide details the prerequisites and steps necessary to install Microsoft® Compute Cluster Pack on a prepared Microsoft Windows® Compute Cluster Server 2003 platform.

Compute Cluster Pack is a CD that contains the services, interfaces, and supporting software needed to create and configure the cluster nodes for high performance computing, as well as utilities and management infrastructure.

A prepared Windows Compute Cluster Server 2003 platform consists of a head node and one or more compute nodes physically connected according to a supported topology with a supported x64 edition of the Windows Server 2003 operating system installed in advance on the head node at minimum.

The supported operating systems and topologies, as well as hardware and bios requirements, are specified in Appendix 2 of this Guide. A general description of Microsoft Compute Cluster Server 2003is provided in Appendix 1.

This guide contains the following topics:

  • Installing Compute Cluster Pack (cluster deployment)

  • Appendix 1: Introduction to Microsoft® Windows® Compute Cluster Server 2003

  • Appendix 2: Platform requirements

Installing Compute Cluster Pack (cluster deployment)

Use the following steps to install Compute Cluster Pack on your prepared Windows Compute Cluster Server 2003 platform:

  1. Verify the computers you intend to configure as cluster nodes meet hardware and software requirements. (See Appendix 2: Platform requirements.)

  2. Verify that you are installing the cluster on a supported network topology that meets the needs of your users and developers. (See Appendix 2: Platform requirements.)

  3. Create a cluster head node. To do this, complete the following tasks:

    1. Verify that a supported x64 edition of Windows Server 2003 has been installed on the head node. (See Appendix 2: Platform requirements.) If you intend to use the Automated Addition method of creating and adding compute nodes to your cluster, you must also create a second disk partition to contain installation images.

    2. Verify that the head node is joined to an existing Active Directory® domain (recommended) or use Dcpromo.exe to make the head node a domain controller for the cluster. Active Directory directory service provides the means to manage the identities and relationships that make up network environments. Active Directory is required for Windows Compute Cluster Server 2003

    3. Configure Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), and other required network services for your cluster's networks.

    4. Install Compute Cluster Pack on the head node.

      Note

      This and the following steps are performed using Compute Cluster Pack Setup.exe and are wizard-driven. Select the option for installing a head node.

    5. Configure the network interfaces of the head node.

    6. Enable or disable the Windows Firewall on the public network.

    7. If applicable, install Remote Installation Services (RIS) on the head node.

    8. If RIS is installed, add one or more RIS installation images on a second volume on the head node, then modify the images with valid license keys and descriptions. If you have multiple images, you can then choose the appropriate image when you use the wizard for automated node addition.

      Note

      RIS can be used only on a cluster with a dedicated private network.

    9. Modify the RIS image created in step "h" with additional drivers or hotfixes according to the product documentation.

    After setting up and configuring the head node, complete configuration of your cluster by performing the following tasks:

  4. Add one or more compute nodes to your cluster.

    Note

    This is performed using the Compute Cluster Pack Setup.exe and is wizard-driven. Select the option for installing a compute node.

  5. Add administrators and users to your cluster.

Use the following checklist as an aid to deploying your cluster. It includes links to Compute Cluster Server 2003 product documentation on the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkID=64128).

Checklist: Deploying a Compute Cluster

Step Action Reference

1.

Review concepts for Windows Compute Cluster Server 2003, including system hardware and software requirements.

Compute Cluster System Requirements (https://go.microsoft.com/fwlink/?LinkID=64196)

2

Verify topology for your compute cluster.

Compute Cluster Network Requirements (https://go.microsoft.com/fwlink/?LinkID=64197)

3.

Verify that a supported operating system is installed.

Installing Compute Cluster Edition (https://go.microsoft.com/fwlink/?LinkID=64198)

4.

Create a second disk volume (D:\) to store installation images if you plan to use the Automated Addition method to add nodes to the cluster.

Installing Compute Cluster Edition (https://go.microsoft.com/fwlink/?LinkID=64198)

5.

Create and configure your head node.

Creating a Head Node (https://go.microsoft.com/fwlink/?LinkID=64199)

6.

Join head node to an Active Directory domain (existing) or create a new domain.

Active Directory Installation Wizard Technical Reference (https://go.microsoft.com/fwlink/?LinkId=52290)

7.

Install Microsoft Management Console (MMC) 3.0

MMC 3.0 (https://go.microsoft.com/fwlink/?linkid=62400)

8.

Install RIS hotfix

RIS Hotfix (KB907639) (https://go.microsoft.com/fwlink/?linkid=55167)

9.

Install ICS hotfix

ICS Hotfix (KB897616) (https://go.microsoft.com/fwlink/?linkid=55166)

10.

Reboot your system.

 

11.

Install Compute Cluster Pack on the head node.

Installing Compute Cluster Pack On a Head Node (https://go.microsoft.com/fwlink/?LinkID=64200)

12.

Configure network interfaces on the head node.

Configuring Network Adapters on the Head Node (https://go.microsoft.com/fwlink/?LinkID=64201)

13.

Enable RIS (optional) from the Compute Cluster Pack if you intend to use the Automated method to add compute nodes to your cluster. Then add one or more installation images and configure the images with valid product keys and identifying descriptions.

Any non-Microsoft drivers required may be added my modifying the RIS image once it is created.

Installing Remote Installation Services (https://go.microsoft.com/fwlink/?LinkID=64202)

Adding a RIS Image (https://go.microsoft.com/fwlink/?LinkID=64203)

Modifying a RIS Image (https://go.microsoft.com/fwlink/?LinkID=65538)

License Management (https://go.microsoft.com/fwlink/?LinkID=64204)

14.

Add compute nodes to your cluster using either the Automated Addition or Manual Addition method.

To do this, use the Add Nodes Wizard from the Node Management tile in the Compute Cluster Administrator MMC snap-in.

The Automated Addition method uses the RIS images you have created.

The Manual Addition method requires that the supported operating system be installed on the compute nodes. It also requires that you first install Compute Cluster Pack on the compute nodes using the setup wizard Join this server to an existing compute cluster as as compute node option.

Using Automated Addition to Add a Node (https://go.microsoft.com/fwlink/?LinkID=64205)

Using Manual Addition to Add a Node (https://go.microsoft.com/fwlink/?LinkID=64206)

15.

Approve nodes.

Managing Compute Nodes (https://go.microsoft.com/fwlink/?LinkID=64207)

16.

Define cluster users and administrators. To do this, use the Configure Users Wizard from the Cluster Security tile in the Compute Cluster Administrator MMC snap-in.

Managing Cluster Security (https://go.microsoft.com/fwlink/?LinkID=64208)

17.

Download the Microsoft Compute Cluster Pack SDK, if desired.

See the Microsoft Developer Network (MSDN) Web site (https://go.microsoft.com/fwlink/?linkid=55873).

For a more detailed discussion of Compute Cluster Server 2003 and deploying, using, and administering a Windows Compute Cluster, see the following documentation:

Appendix 1: Introduction to Microsoft Windows Compute Cluster Server 2003

Microsoft® Windows® Compute Cluster Server 2003 is a high performance computing cluster consisting of a head node and one or more compute nodes.

The Head Node

The head node provides user interface and management services to the cluster. The user interface consists of the Compute Cluster Administrator, which is a Microsoft Management Console (MMC) snap-in, the Compute Cluster Job Manager, which is a Win32 graphic user interface, and a command-line interface (CLI). Management services include job scheduling, job and resource management, node management, and Remote Installation Services (RIS). The head node can also serve as a network address translation gateway (part of Internet Connection Services) between the public network and the private network that make up the cluster.

The Compute Node

A compute node is a computer configured as part of a compute cluster to provide computational resources for the end user. Compute nodes on a Windows Compute Cluster Server 2003 cluster must have a supported operating system installed. Compute nodes within a single compute cluster can have different hardware configurations and different supported Operating Systems.

Job Scheduler

The Job Scheduler service runs on the head node and is responsible for job admission and queue management, resource allocation, and job execution. This service communicates with the Node Manager service that runs on all compute nodes.

Management Infrastructure

Compute Cluster Pack offers a complete management infrastructure that allows the cluster administrator to deploy and manage compute nodes. This infrastructure consists of the cluster services running on the head node and all compute nodes in the cluster, providing the administrative, user, and command-line interfaces used to administer the cluster, submit jobs, and manage the job queue.

Client Utilities

Compute Cluster Pack setup has the option of installing only the client utilities. Client utilities include the Job Scheduler API, Compute Cluster Administrator, Compute Cluster Job Manager, and the command-line interface (CLI). Client utilities can be installed on a range of 64-bit or 32-bit Windows operating systems, enabling an administrator to manage a cluster and the job queue from a remote computer. For a list of operating systems supported by the client utilities, see Appendix 2: Platform requirements.

Compute Cluster Administrator and Job Manager

Cluster administrators and cluster users utilize these interfaces for cluster operations and job submissions and management. The Compute Cluster Administrator is used to configure the cluster, manage nodes, and monitor cluster activity and health. The Job Manager is used for job creation, submission, and monitoring.

Command Line Interface

The Compute Cluster Pack offers a command-line interface (CLI) for node and job management. These operations can also be scripted. Administrators can use the CLI to automate job, job queue, and node operations.

Appendix 2: Platform requirements

Compute Cluster Server 2003 platform requirements include requirements for hardware, BIOS, operating system, and network, as well as special software prerequisites for Compute Cluster Pack.

Hardware requirements

The following requirements apply to both the head node and compute node computers unless otherwise specified.

Processor, RAM, and multiprocessor support

For requirements for Windows Server 2003, Standard x64 Edition, see Windows Server 2003 x64 Editions Product Overview (https://go.microsoft.com/fwlink/?LinkId=63899).

Minimum disk space for setup

4 GB

Supported network adaptors

Compute Cluster Server 2003 supports all networking hardware supported by Windows Server 2003, Standard x64 Edition.

All network adapters used in the cluster have distinct media access control (MAC) addresses

Network adapters to be used for the private network must support PXE booting

Nodes must be configured with network adapters to enable at least one of the five network topologies supported by Compute Cluster Pack.

Node GUID

There should be no duplicated hardware GUIDs across the cluster nodes if RIS is to be used for automated node deployment.

Head node disk partitions

Compute Cluster Server head nodes must have at least two hard disk partitions (such as C:\ and D:\) if RIS is to be used for automated node deployment.

The RIS partition must be NTFS. We recommend that the RIS partition be at least 2 GB in size to provide ample space for RIS images, which are each around 775 MB in size. The partition running Windows should be at least 4 GBs in size, as specified above.

BIOS settings

To support imaging using RIS, configure BIOS boot order on all compute nodes so that PXE is in place for RIS installation on first boot. For example:

  • PXE network boot

  • Hard disk boot from C:\

Operating system requirements for head node and compute node

The supported operating systems are the same for both head node and compute nodes and include:

  • Microsoft® Windows Server™ 2003, Compute Cluster Edition

  • Microsoft® Windows Server™ 2003, Standard x64 Edition

  • Microsoft® Windows Server™ 2003, Enterprise x64 Edition

  • Microsoft® Windows Server™ 2003 R2, Standard x64 Edition

  • Microsoft® Windows Server™ 2003 R2, Enterprise x64 Edition

For an overview of Microsoft 64-bit operating systems, see Windows Server 2003 x64 Editions Product Overview (https://go.microsoft.com/fwlink/?LinkId=63899)

Operating system requirements for client utilities only

Supported operating systems for client utilities only include:

  • Microsoft® Windows Server™ 2003 R2, Standard Edition

  • Microsoft® Windows Server™ 2003 R2, Standard x64 Edition

  • Microsoft® Windows Server™ 2003 R2, Enterprise Edition

  • Microsoft® Windows Server™ 2003 R2, Enterprise x64 Edition

  • Microsoft® Windows Server™ 2003, Compute Cluster Edition

  • Microsoft® Windows Server™ 2003, Standard x64 Edition

  • Microsoft® Windows Server™ 2003, Enterprise x64 Edition

  • Microsoft® Windows Server™ 2003 with Service Pack 1 (SP1), Standard Edition (32-bit x86)

  • Microsoft® Windows Server™ 2003 with Service Pack 1 (SP1), Enterprise Edition (32-bit x86)

  • Microsoft® Windows® XP Professional x64 Edition

  • Microsoft® Windows® XP Professional with Service Pack 2 (SP2)

Network requirements

Windows Compute Cluster Server 2003 supports five different cluster topologies. Each topology has implications for performance and accessibility. The topologies involve at least one and possibly three different networks: public, private, and Message Passing Interface (MPI).

Topology 1

Head node on a public and private network and compute nodes on the private network only.

3c71be96-8c5d-41f2-bb32-12b0de369fdf

Topology 2

All nodes on a public and a private network.

7f508230-8c0c-463f-bca4-384d8d66cb96

Topology 3

Head node on a public and private network and compute nodes on the private network only, with a second private network for MPI.

1a745e8e-e4fd-4aad-96f3-5e2f33895f31

Topology 4

All nodes on a public and a private network with a second private network for MPI.

4e27f2c5-4360-41cd-8f47-6ae50abf7d18

Topology 5

All nodes on a public network only.

bf5a13f9-87a3-4756-9941-82ff3f201044

Note

Topology 5 prevents the use of RIS for automatic installation of the operating system on compute nodes.

Special CCP prerequisites (can also be installed as part of CCP setup)

Compute Cluster Pack setup requires certain software prerequisites that must be installed before installation can succeed. The setup program either installs or links to download sites for the prerequisite software. The prerequisites are a combination of Microsoft technologies and hotfixes that enable product functionality.

The required software for the head node is listed below, with links to download sites for the hotfixes and to Microsoft Management Console (MMC) 3.0:

On a compute node, the only required software is the .NET Framework 2.0, installed as part of the Compute Cluster Server 2003 compute node installation process.

All software, particularly the hotfixes, can be installed on a node before installing Compute Cluster Pack. This is recommended for the hotfixes and MMC 3.0, since they are not included on the CD.