Azure Feature Compatibility with Microsoft HPC Pack
Applies To: Microsoft HPC Pack 2008 R2, Microsoft HPC Pack 2012, Microsoft HPC Pack 2012 R2, Windows HPC Server 2008 R2
This topic lists the Azure features that can be used in Azure burst deployments with HPC Pack. Certain features and services are compatible with only certain versions of HPC Pack, and some require additional configuration in the Azure subscription or the Azure node template that is used for the deployment. For more information about configuring an Azure node template to use these features, see Configuring a Windows Azure Node Template for Microsoft HPC Pack.
For general requirements to add Azure nodes to a Windows HPC cluster, see Requirements to Add Azure Nodes with Microsoft HPC Pack.
In this topic:
Azure features that can be used in burst deployments from an HPC cluster
Azure worker role instance sizes that can be used in burst deployments
Deprecated or retired features
Azure features that can be used in burst deployments from an HPC cluster
Note
- In some cases, Azure features or services that are in preview or beta can be configured in an Azure node template, if your subscription and your version of HPC Pack enable them. Before you use a preview or beta feature, review the terms of use. We recommend that you only use preview or beta features in test or proof-of-concept deployments of Azure nodes, not in production deployments.
- Certain versions of HPC Pack may include settings to configure Azure features that are now deprecated or retired, and which therefore should not be used in Azure burst deployments. For more information, see Deprecated or retired features in this topic.
Feature | Description | Minimum version of Microsoft HPC Pack | Additional requirements |
---|---|---|---|
Worker role nodes |
|
HPC Pack 2008 R2 with SP1 Note
|
|
Azure Virtual Network |
Note HPC Pack does not support configuration of a point-to-site virtual network. |
HPC Pack 2012 Note Starting with HPC Pack 2012 with SP1, connectivity between Azure and an on-premises network can be configured using a VPN hardware device or the Routing and Remote Access service (RRAS) running in Windows Server 2012. |
|
Remote Desktop Connection |
|
HPC Pack 2008 R2 with SP2 |
|
Azure startup script |
|
HPC Pack 2008 R2 with SP2 |
|
Azure worker role instance sizes that can be used in burst deployments
The following table lists the Azure worker role instance sizes that you can choose from when adding Azure nodes to a Windows HPC cluster. The minimum version of HPC Pack that supports each size is listed. For details about the sizes for virtual machine-based compute resources, see Virtual Machine and Cloud Service Sizes for Azure. For pricing information, see Cloud Services Pricing Details.
Note
Available sizes for worker role instances can differ from those for Azure virtual machines.
Worker role size | Minimum version of HPC Pack |
---|---|
Small |
HPC Pack 2008 R2 with SP1 |
Medium |
HPC Pack 2008 R2 with SP1 |
Large |
HPC Pack 2008 R2 with SP1 |
Extra Large |
HPC Pack 2008 R2 with SP1 |
A5 |
HPC Pack 2012 R2 |
A6 |
HPC Pack 2012 with SP1 |
A7 |
HPC Pack 2012 with SP1 |
A8 |
HPC Pack 2012 R2 |
A9 |
HPC Pack 2012 R2 |
Deprecated or retired features
The following Azure features are retired. These features are longer available for use in Azure node deployments with versions of HPC Pack that provide related configuration settings.
VM Role (beta) Retirement date: May 2013
Note
The node template settings to select VM role instances for deployments of Azure nodes are removed as of HPC Pack 2012 with SP1.
Azure Connect (CTP) Retirement date: July 2013
Note
The node template settings to enable Azure Connect in deployments of Azure nodes are removed as of HPC Pack 2012.
See Also
Concepts
Burst to Azure with Microsoft HPC Pack