Microsoft HPC Pack: Node Deployment
Applies To: Microsoft HPC Pack 2012, Microsoft HPC Pack 2012 R2
This section provides information about additional cluster deployment options and scenarios for adding nodes to the HPC Pack 2012 R2 or HPC Pack 2012 cluster.
For introductory information, see Getting Started Guide for Microsoft HPC Pack 2012 R2 and HPC Pack 2012.
In this section
Title |
Description |
|---|---|
The topics in this section provide basic procedures and options to add domain-joined compute nodes and Windows Communication Foundation (WCF) broker nodes that are managed by your HPC cluster. You can deploy nodes from bare metal, add preconfigured nodes, or add nodes by importing a node XML file. |
|
This guide contains information about adding on-premises Linux compute nodes to your HPC cluster. |
|
This guide contains information about extending (“bursting”) your HPC cluster to include Azure Batch pools as compute resources. |
|
This guide contains information about extending (“bursting”) your HPC cluster to include Azure worker role instances (Azure nodes) as compute resources. |
|
This guide provides step-by-step procedures for adding computers to your HPC cluster that are running the Windows operating system but are not managed by your cluster. These computers are added as workstation nodes, and you can use them to run cluster jobs. |
|
This topic summarizes the requirements and steps for adding servers for cycle harvesting that are running the Windows Server operating system to your HPC cluster. |
|
This guide provides step-by-step procedures for deploying diskless compute nodes to your HPC cluster that boot over iSCSI. |
|
This guide provides procedures and guidance for deploying HPC Pack where the head node (specifically, a set of head node services) is configured in a failover cluster. |
|
Configuring Microsoft HPC Pack for High Availability with SOA Applications |
This guide provides procedures and guidance for deploying HPC Pack in a configuration designed for high availability for applications based on service-oriented architecture (SOA). For this configuration, you configure the head node (specifically, a set of head node services) in a failover cluster. Then you can configure one or more WCF broker nodes (specifically, the HPCBroker service) in one or more separate failover clusters. |
This topic provides information about moving compute resources from one head node to a newly installed head node. |