Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to deploy Windows HPC Server 2008 Cluster in practice

2025-02-25 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)05/31 Report--

This article introduces you how to deploy Windows HPC Server 2008 cluster in practice, the content is very detailed, interested friends can refer to, hope to be helpful to you.

Windows HPC Server 2008 is the successor to the existing Windows Computer Cluster Server 2003 (WCCS2003), based on the core of the Windows Server 2008 64-bit system. It can provide new high-speed network, efficient and flexible cluster management tools, service-oriented architecture (SOA) project scheduling, cluster file system supporting partners, and can be used in large-scale parallel projects such as computational fluid dynamics, water conservancy project simulation, or complex parallel projects such as BLAST and Monte Carlo simulation.

Here is how to deploy a Windows HPC Server 2008 cluster.

Listing: deploying a HPC cluster

The following listing describes the overall process of deploying a Windows HPC Server 2008 cluster. Each task in the list is linked to the appropriate part of this document that describes the steps required to perform the task.

Step 1: prepare for deployment

The first step in deploying a HPC cluster is to make important decisions, such as deciding how to add nodes to the cluster and selecting the cluster's network topology. The following listing describes the steps involved in preparing for deployment.

List: preparing for deployment

1.1. Check initial considerations and system requirements

The following sections list some initial considerations to review, as well as the hardware and software requirements for Windows HPC Server 2008.

Initial consideration

Before deploying the HPC cluster, review the following initial considerations.

Compatibility with previous versions

The following list describes the compatibility between Windows HPC Server 2008 and Windows Compute Cluster Server 2003:

"Windows HPC Server 2008 provides application programming interface (API) level compatibility for applications integrated with Windows Compute Cluster Server 2003. However, these applications may need to be changed to run on Windows Server 2008. If you encounter problems running applications on Windows Server 2008, you should consult your software vendor.

"Windows HPC Server 2008 supports job submissions from Windows Compute Cluster Server 2003 clients, including jobs submitted through the use of command line tools, Computing Cluster Job Manager, and COM API.

"Windows HPC Server 2008 client tools, including the Cluster Management console (HPC Cluster Administrator), Job schedule console (HPC Job Manager), command line tools, and API, cannot be used to manage jobs or submit jobs to a Windows Compute Cluster Server 2003 cluster.

"clusters with both Windows Compute Cluster Server 2003 nodes and Windows HPC Server 2008 nodes are not supported.

"parallel installation of Windows HPC Server 2008 and Windows Compute Cluster Server 2003 on the same computer is not supported. This includes the Windows HPC Server 2008 client utility.

"upgrading a Windows Compute Cluster Server 2003 header to a Windows HPC Server 2008 header is not supported.

Server roles added during installation

When you install HPC Pack 2008, the following server roles are added to the head node:

"DHCP server, which provides the IP address and related information of the compute node.

"Windows deployment service for remote deployment of compute nodes.

"File service for managing shared folders.

"Network policy and access service, which enables routing and remote access so that network address translation (NAT) services can be provided to cluster nodes.

Hardware requirements

The hardware requirements for Windows HPC Server 2008 are very similar to those for the 64-bit version of Windows Server 2008.

Processor (based on x64):

"minimum: 1.4 GHz

"suggestion: 2 GHz or faster

RAM:

"minimum: 512 MB

"recommended: 2 GB or greater

Free disk space:

"minimum: 50 GB

"recommended: 80 GB or greater

Drive:

"DVD-ROM driv

Network Adapter:

"the number of network adapters on the head node and compute node depends on the network topology you select for the cluster.

Software requirements

The following list summarizes the software requirements for head nodes and compute nodes in the Windows HPC Server 2008 cluster:

"Windows Server 2008 HPC Edition, or other 64-bit version of Windows Server 2008

"Microsoft HPC Pack 2008

To enable users to submit jobs to the HPC cluster, you can install the utilities that come with Microsoft HPC Pack 2008 on client computers. These client computers must be running any of the following operating systems:

"Windows XP Professional or later with Service Pack 3 (x86 or x64 based)

"Windows Vista? Enterprise, Windows Vista Business, Windows Vista Home and Windows Vista Ultimate

"Windows Server 2003 Standard Edition with Service Pack 2 or Windows Server 2003 Enterprise Edition or later (x86 or x64 based)

"Windows Server 2003, Compute Cluster Edition

"Windows Server 2003 R2 Standard Edition or Windows Server 2003 R2 Enterprise Edition (based on x86 or x64)

1.2. Decide how to add compute nodes to the cluster

There are three ways to add compute nodes to the cluster:

"start from scratch. When you add a compute node to the cluster, the operating system and all required HPC cluster components are automatically installed on each compute node. There is no need to manually install the operating system or other software.

"add preconfigured compute nodes. Compute nodes are already running Windows Server 2008 HPC Edition or other 64-bit versions of Windows Server 2008, and Microsoft HPC Pack 2008 is manually installed on each node.

"Import node XML file. You need to use a XML file that contains a list of all nodes to deploy. This XML file can be used to add nodes from scratch or from preconfigured nodes.

The following is a list of details to consider when choosing how to add nodes to the HPC cluster:

"when you deploy a node from scratch, Windows HPC Server 2008 automatically generates the computer name for the compute node. During the configuration process, you must specify the naming convention to use when automatically generating the computer name for the new node.

"Compute nodes will be assigned computer names in deployment order.

"if you want to add compute nodes from scratch and assign computer names differently, you can use the node XML file.

"if you want to add preconfigured nodes to the cluster, you need to install Windows Server 2008 HPC Edition or other 64-bit version of Windows Server 2008 on each node, if not already installed, as well as Microsoft HPC Pack 2008.

1.3. Select an Active Directory domain for the cluster

The head nodes and compute nodes in the HPC cluster must be members of the Active Directory domain. Before you can deploy a cluster, you must select the Active Directory domain that will be used for the HPC cluster.

If there is no Active Directory domain to which the cluster can join, or if you plan not to join an existing domain, you can install the Active Directory Domain Services role on the head node, and then configure the domain controller on that node.

1.4. Select user accounts for installation and diagnostics

During the configuration of the HPC cluster, credentials must be provided for the domain user account that will be used for installation and troubleshooting. You must select an existing account or create a new account before starting a cluster deployment.

The following is a list of details to consider when selecting a user account:

"the user account you select must be a domain account that has sufficient permissions to create Active Directory computer accounts for the compute node. Alternatively, you can create computer accounts manually or ask the domain administrator to create them.

"if part of the deployment process requires access to resources on the corporate network, this user account must have the required permissions to access those resources (for example, access to installation files available on a network server).

"if you want to restart the node remotely from the cluster management console (HPC Cluster Administrator), this account must be a member of the local Administrators group on the head node. This requirement is required only if you do not have a scripted power control tool that can be used to remotely restart the compute node.

1.5. Select the network topology of the cluster

Windows HPC Server 2008 supports five cluster topologies. These topologies are distinguished by how the compute nodes in the cluster connect to each other and to the enterprise network. The five supported cluster topologies are:

"Topology 1: compute nodes isolated on a private network

"Topology 2: all nodes on the enterprise and private network

"Topology 3: compute nodes isolated on private and application networks

"Topology 4: all nodes on enterprise, private, and application networks

"Topology 5: all nodes on the enterprise network

When selecting a network topology, you must take into account the existing network infrastructure:

"decide which network in the selected topology will act as the enterprise network, private network, and application network.

"do not leave the network adapter connected to the corporate network on the head node in automatic configuration (that is, the adapter's IP address cannot start with 169.254). The adapter must have a valid IP address that is dynamically or manually assigned (static).

"if you select a topology that includes a private network, and you are planning to add nodes to the cluster from scratch:

"ensure that the execution environment (PXE) server is not pre-started on the private network.

"if you want the private network to use an existing DHCP server, make sure that it is configured to recognize the header node as a PXE server in the network.

"if you want to enable DHCP servers on the head nodes of private or application networks, and there are other DHCP servers connected to those networks, you must disable these DHCP servers.

"if you connect an existing Domain name system (DNS) server to the same network as the compute node, no action is required, but the compute node is automatically logged out of the DNS server.

"contact your system administrator to determine whether Internet Protocol Security (IPsec) is enforced on the domain through Group Policy. If you perform IPsec on a domain through Group Policy, you may encounter problems during deployment. The circumvention is to make the head node an IPsec border server so that the compute node can communicate with the head node during PXE startup.

1.6. Prepare for Multicast (optional)

If you want to deploy nodes from scratch and want to multicast the operating system images that will be used during deployment, we recommend that you prepare for multicast by doing the following:

"enable Internet Group Management Protocol (IGMP) snooping on the network switch, if this feature is available. This will help reduce multicast traffic.

"disable Cross-Tree Protocol (STP) on the network switch, if this feature is enabled.

1.7. Prepare for the integration of scripted power control tools (optional)

The Cluster Management console (HPC Cluster Administrator) includes operations to start, shut down, and restart compute nodes remotely. These actions are linked to a script file (CcpPower.bat) that uses operating system commands to perform these power control operations. You can replace the default operating system commands in the script file with your own power control script, such as the Intelligent platform Management Interface (IPMI) script provided by the vendor of the cluster solution.

In this integration preparation, you must obtain all the required scripts, dynamic link library (DLL) files, and all other components for the power control tool. After you have all the required components, test them independently and ensure that they work as expected on computers that will be deployed as compute nodes in the cluster.

Step 2: deploy the header node

The next step in deploying a HPC cluster is to deploy the header node. The following listing describes the steps involved in deploying the header node.

Listing: deploy the header node

2.1. Install Windows Server 2008 on the head node computer

To deploy the head node of a HPC cluster, you must first install Windows Server 2008 HPC Edition, or another 64-bit version of Windows Server 2008, on the computer that will act as the head node.

Keystone

We strongly recommend that you perform a clean installation of Microsoft HPC Pack 2008 before installing Windows Server 2008. If you are installing Microsoft HPC Pack 2008 on an existing installation of Windows Server 2008, first remove all server roles, and then perform the procedures in this guide.

Be careful

It is recommended that you get the latest device drivers for head-node computers from the hardware vendor's website.

2.2. Join the head node computer to the domain

As described in step 1: prepare for deployment, the header node must be a member of the Active Directory domain. After installing Windows Server 2008 on the header node, manually join the header node to the existing Active Directory domain.

2.3. Install Microsoft HPC Pack 2008 on the head node computer

After you install Windows Server 2008 on the head node computer and join the head node to the Active Directory domain, you can install Microsoft on the head node. HPC Pack 2008 .

Install Microsoft HPC Pack 2008 on the head node computer

1. To start the Microsoft HPC Pack 2008 installation wizard on the computer that will act as the head node, run setup.exe from the HPC Pack 2008 installation media or from a network location.

two。 On the ready to start page, click next.

3. On the Microsoft Software license terms page, read or print the software license terms in the license agreement and accept or reject the terms of the agreement. If you accept the terms, click next.

4. On the Select installation Type page, click New HPC Cluster by creating a header node, and then click next.

5. Continue with the steps in the installation wizard.

Step 3: configure the header node

After you deploy the head node of the HPC cluster, you must configure the head node by performing a configuration task list in HPC Cluster Administrator.

Listing: configure the header node

The following list includes the items in the configuration task list that need to be completed in HPC Cluster Administrator in order to configure the header node.

3.1. Configure the HPC cluster network

The HPC cluster network configuration is the first step in the head node configuration process. You can configure the HPC cluster network by executing the Network configuration Wizard in HPC Cluster Administrator. When you configure a HPC cluster network, you must select the network topology that has been selected for the cluster, which is described in step 1: prepare for deployment.

Keystone

Before you begin to configure the HPC cluster network in HPC Cluster Administrator, make sure that the head node and the computer that will be added to the cluster as compute nodes are physically connected according to the network topology that you have selected for the cluster. In addition, make sure that you can identify which network each network adapter in the head node will connect to.

Configure the HPC cluster network

1. If HPC Cluster Administrator is not already open on the head node, open it. Click start, point to all programs, click Microsoft HPC Pack, and then click HPC Cluster Administrator.

two。 In the Task list, click configure Network.

3. Follow the steps in the Network configuration Wizard.

3.2. Provide installation credentials

In order to configure a new compute node, installation credentials must be provided. These credentials are used when installing the operating system, applications, and adding nodes to the Active Directory domain. Also, these same credentials are used when running diagnostic tests on cluster nodes.

Provide installation credentials

1. In the Task list, click provide installation credentials. The installation credentials dialog box appears.

two。 Type the user name, including the domain (DOMAIN\ User), and then type the password of the domain user account that will be used to deploy the compute node and run the diagnostic test.

Keystone

This account must be a domain account with sufficient permissions to create an Active Directory computer account for the compute node. Alternatively, you can create computer accounts manually or ask a domain administrator to create them.

Keystone

If part of the deployment process requires access to resources on the corporate network, this account should have the necessary permissions to access those resources.

Keystone

If you want to restart the node remotely from the Cluster Management console (HPC Cluster Administrator), this account must be added as the HPC cluster administrator on the head node. This requirement is required only if you do not have a scripted power control tool that can be used to remotely restart the compute node.

4. To save the specified credentials, click OK.

3.3. Configure how the new node is named

If you deploy a compute node from scratch and do not use a node XML file to import the node into the cluster, Windows HPC Server 2008 automatically generates a computer name for the new node you are deploying. You need to specify how these names are generated by defining naming sequences.

You can define a naming sequence by selecting the root name and starting number that will accompany the name. The starting number is placed in a set of percentage symbols (%). For example: ClusterNode00%.

When you deploy a compute node from scratch, the node is named sequentially when it becomes available. For example, if you deploy three nodes after you specify the following naming sequence: ClusterNode-0%, assigns the following names to these nodes:

"ClusterNode-100

"ClusterNode-101

"ClusterNode-102

Keystone

The compute node name is limited to 15 characters. When you specify a naming sequence for compute nodes, consider the number of compute nodes in the deployment and ensure that the sequence you specify does not produce names that are more than 15 characters long. For example, if you are deploying 1000 compute nodes and the starting number is 1, the root name cannot exceed 12 characters; otherwise, the name of node number 1000 will need to be 16 characters.

Specify the compute node naming sequence

1. In the Task list, click configure how new nodes are named. The specify Compute Node naming sequence dialog box appears.

two。 Type the named sequence you want to use. The preview will help you see an example of how naming sequences are applied to computed node names.

Be careful

You cannot specify a compute node naming sequence that consists only of numbers.

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

3.4. Create a node template

Node templates are new in Windows HPC Server 2008 that define the tasks that need to be performed when configuring and adding compute nodes to the cluster. Using node templates, you can deploy operating system images, add specific drivers and software to compute nodes, or add preconfigured nodes directly to the cluster. Because there may be many types of compute nodes, or compute nodes may be added to the cluster in different ways, you can create different templates that apply to different nodes or situations.

You can create two types of node templates:

"there is an operating system image. This type of template includes steps to deploy the operating system on the compute node. Use this type of template when adding a compute node from scratch.

"there is no operating system image. This type of template is used to add preconfigured compute nodes to the cluster or to update existing nodes.

The type of template you create for the initial deployment of the HPC cluster depends on how you decide how to add compute nodes to the cluster.

Keystone

If you will create a node template with an operating system image, you will need installation media for Windows Server 2008 HPC Edition or other 64-bit versions of Windows Server 2008, or you must have available installation files on a network location accessible from the head node computer.

Create a node template

1. In the Task list, click create Node template.

two。 Perform the steps in the create Node template Wizard.

Be careful

Node templates created through the create Node template Wizard include the most common deployment and configuration tasks. By using the Node template Editor, you can add more tasks to the node template you create. For more information, on the specify template name page of the create Node template Wizard, click learn about Node templates.

3.5. Add a driver for the operating system image (optional)

If the compute nodes will be deployed from scratch and these nodes require special device drivers, you need to add these drivers during the configuration of the header node. The driver must be in .inf format and must be available to all operating system images in the mirrored storage.

Be careful

It is recommended that you obtain the latest device drivers for the compute node from the hardware vendor's website.

Add a driver for an operating system image

1. In the Task list, click manage drivers. The manage drivers dialog box appears.

two。 To add a driver, click add.

3. Type or browse to the location of the installer information file (.inf format) for the driver you want to add, and then click Open.

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

5. When you are finished adding drivers, click close.

3.6. Add or remove users (optional)

If you want to grant cluster access to other members of your organization, you need to add those members as HPC cluster users or HPC cluster administrators. Also, you can delete users or administrators who are added by default during installation.

Keystone

The Domain users group was added as a HPC cluster user during installation. If you do not want all users in the domain to have access to the cluster, you can remove the Domain users group from the list of HPC cluster users, and then add other domain user groups specifically created for HPC cluster users, or add individual domain users.

Add or remove users from the cluster

1. In the Task list, click add or remove users.

two。 Add users to the cluster:

a. In the actions pane, click add user. The Select user or Group dialog box appears.

b. Type the user name of the user you want to add, and then click check name. For more information, on the Select a user or Group window, click example.

c. Repeat the previous steps for all users you want to add.

d. When you are finished adding users, click OK.

3. Add an administrator to the cluster:

a. In the actions pane, click add Administrator. The Select user or Group dialog box appears.

b. Type the user name of the administrator you want to add, and then click check name. For more information, on the Select a user or Group window, click example.

c. Repeat the previous steps for all administrators you want to add.

d. When you are finished adding the administrator, click OK.

4. To delete a user or administrator, select it on the users list, and then click Delete.

Step 4: add compute nodes to the cluster

Windows HPC Server 2008 simplifies the deployment of compute nodes by providing automatic node mirroring, automatic naming of nodes, and other features to smooth deployment tasks. Also, it provides tools that can be used to monitor the progress of deployment.

Keystone

Unlike previous versions of Windows HPC Server 2008, the default setting in Windows HPC Server 2008 responds only to pre-start execution (PXE) requests from existing compute nodes. This default setting is automatically changed when you add a node from scratch using the add Node Wizard. You can also change this setting manually under deployment Settings on the options menu.

After you create a node template, you can use the add Node Wizard to add compute nodes to the HPC cluster. You can add compute nodes to the cluster in three ways:

"deploy compute nodes from scratch

"add compute nodes by importing the node XML file

"add preconfigured compute nodes

Add compute nodes to the cluster

1. In the Task list, click add Compute Node.

two。 Perform the steps in the add Node Wizard.

Be careful

The HPC Cluster Administrator help documentation provides a step-by-step process for adding compute nodes to the cluster. To view these procedures, click add Node to Cluster on the Select deployment method page of the add Node Wizard.

Step 5: run the diagnostic test against the cluster

After you have configured the head node and added all compute nodes to the cluster, you should run diagnostic tests to verify cluster functionality and resolve any configuration issues.

Run diagnostic tests against the cluster

1. In the Task list, click verify Cluster (under Diagnostics).

two。 On the run Diagnostics dialog box, make sure the run all functional Tests and all nodes options are selected, and then click OK.

3. To view the progress of diagnostic tests and test results, click Test results in Diagnostics.

4. To view more information about the test, double-click the test. To expand the information in a section of the test results, click the down arrow in that section.

This is the end of the actual battle on how to deploy Windows HPC Server 2008 clusters. I hope the above content can help you to some extent and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report