Updated: January 13, 2014
Applies To: Microsoft HPC Pack 2008 R2, Microsoft HPC Pack 2012, Microsoft HPC Pack 2012 R2
There are two components to services that you deploy to your cluster: the service binaries (DLLs) and the service configuration file. This topic describes the deployment options for the service DLLs.
The service configuration file specifies the expected location of the service DLL. Ensure that the assembly attribute of the service element points to the location where you placed the service DLL. This can be a path to a shared directory on the cluster, or it can be a local path on each compute node.
The following table describes the options for deploying service DLLs to your cluster.
Copy the service DLL to any folder on the root drive of each node in the cluster (for example, C:\Services). This option yields the best performance, but updating the service binaries can be time-consuming in a large cluster, especially if all the nodes are not online at the same time.
Copy the service DLL to a file share in the cluster. This option makes it easy to update the service binaries; however, it may result in longer DLL load times if the service binaries are large. You will also need to set up the .Net security permissions. For details on how to set up .Net security permissions, see the Code Access Security Policy Tool (Caspol.exe) in MSDN.
Copy large service binaries that are not updated often to the local nodes, while small or more frequently updated services are copied to a file share.
Windows Azure node deployment
Package together the service configuration file, the service DLLs, and any dependent DLLs in a format that can be uploaded to a Windows Azure storage account, and then upload the package to the Windows Azure storage account (you can use the hpcpack command line utility to do this). When you provision a set of Windows Azure nodes from HPC Cluster Manager, any applications or files that are on the storage account are automatically deployed to the Windows Azure nodes. If you upload file packages to storage after the Windows Azure nodes are started, you can use clusrun and hpcsync to manually deploy the files to the Windows Azure nodes.
For more information see: