Windows Azure Integration
Windows Azure is a public flexible cloud-computing platform that offers on-demand, pay-as-you-go, access to highly scalable compute and storage resources with 99.99% uptime. It relieves customers from the burden of having to maintain their own infrastructure in their own data centers. While Windows Azure is well suited for running a wide variety of applications, it is particularly well suited to running HPC applications for two reasons: (i) HPC applications need more computing resources than most other applications; Windows Azure has computing power to match and (ii) HPC applications exhibit a “spiky” behavior i.e. their compute needs can change significantly over small intervals of time. Windows Azure’s pay-for-only-what-you-use model allows you to maintain an HPC infrastructure that meets your typical demands and rely on Windows Azure to address periods of peak computational needs.
Windows HPC Server 2008 R2 Service Pack 2 (SP2) enables service oriented, HPC, jobs to be executed as a service using Windows Azure i.e. you can use resources running within a Windows Azure data center as temporary “compute nodes” to extend the capabilities of your on-premise Windows HPC cluster. The key points to note about this new capability are:
You have the choice of running your jobs (a) entirely on your on-premise clusters, (b) entirely in Windows Azure or (c) partially in Windows Azure and partially on on-premise clusters at the same time. The third choice enables the “burst” scenario where in you run your jobs mostly on your on-premise cluster, but expand to Windows Azure only during peak loads. Note that in all cases, the head-node has to run on-premise. Applications run unchanged on Azure. Your on-premise applications do not have to be changed in any way to run completely or partially in Azure. HPC applications are developed the same way, irrespective of whether run in Windows Azure or on-premise. Note that in this release service oriented, serial and parametric sweep jobs are supported.
Transparent job submission. To a user, submitting a Windows HPC job that runs partly on-premises and partly in the cloud looks just as it always does—it’s no different from submitting one that runs entirely in an on-premise cluster.
Transparent scheduling. To schedule jobs on Azure, all that Administrators have to do is specify (using a graphical wizard) how many Windows Azure nodes they need and at what times. Windows HPC Server takes care of the rest: starting the Windows Azure instances, installing the required software and scheduling the jobs on the Windows Azure nodes. Administrators also have the option of manually starting and stopping the Windows Azure worker nodes.
Future releases may provide for additional capabilities such as running the head-node in Windows Azure and the support for MPI and Excel-based.
Windows HPC Server 2008 R2 SP2 brings the scale, power, and economic benefits of public clouds to High Performance Computing with a simple, easy-to-use solution that extends your existing investments.
Download Windows HPC Server and Windows Azure whitepaper » Download Windows HPC with Burst to Windows Azure: Application Models and Data Considerations whitepaper »