Peeking Under the Hood:  Advantages of Windows CCS

Products & Solutions

Resources

Learn more about

Windows^® Compute Cluster Server (CCS) 2003 provides a secure and affordable high-performance computing (HPC) solution that integrates directly with your existing Windows^® IT infrastructure.

Windows CCS simplifies HPC adoption and use through key features including:

Message Passing Interface

The Microsoft Message Passing Interface (MS-MPI) is a version of the Argonne National Labs Open Source MPI2 implementation, which is widely used by existing HPC clusters. It is compatible with the MPICH2 Reference Implementation and other MPI implementations, and supports an API of more than 160 function calls.

The MS-MPI in Windows CCS leverages the WinSock Direct protocol. It can utilize any Ethernet interconnect that is supported on Windows^® Server 2003 as well as low-latency and high-bandwidth interconnects—such as InfiniBand or Myrinet—through Winsock Direct drivers.

HP-MPI for Windows can provide even higher performance for InfiniBand interconnects by taking advantage of the InfiniBand Access Layer (IBAL) interface. Both MS-MPI and HP-MPI can be installed and running on the same cluster without conflict.

Job Scheduler

Windows CCS includes a command-line job scheduler and the Compute Cluster Job Scheduler. These features allow users to schedule jobs, allocate resources and change the tasks and properties associated with the job.

• Error Recovery. Provides automated retry of failed tasks and jobs, routing around unresponsive nodes and detecting responsive nodes.
  
  
• Automated Cleanup. Each process associated with a job or task is tracked and shut down proactively on all compute nodes at the conclusion of the job or task, preventing “run away” processes on the compute nodes.
  
  
• Security. Each job or task runs in the context of the submitting user and maintains security throughout the process.

Cluster Security

Windows CCS leverages Active Directory to enable role-based security for all cluster jobs and administration. The scheduler runs each job under the context and credentials of the submitting user. System administrators can apply and audit security policies using the existing and familiar mechanisms in Active Directory.

All job management communications are conducted over encrypted and authenticated channels, and the credentials are known only to the node manager for the duration of the job. The compute process itself sees only a logon token, not the actual credentials, further isolating credentials and protecting their integrity.