| Moab Workload Manager® |
A.10 Case Study: Application Management with Dynamic Jobs
Overview
A research organization is interested in sharing a cluster between a distributed service and batch workload. The distributed service handles web based transactions which must receive sub-second response times. The batch workload varies in duration from 15 minutes for 10 days. The organization would like to have unified accounting and apply a single set of mission policies over all workload types.Solution
Using Moab's virtual jobs and the native resource manager interface, the distributed service can be monitored and controlled by way of small locally developed scripts. A virtual job object will be assigned to the service and will encapsulate all monitoring, statistics, and accounting information. As the distributed service can be dynamically configured to adjust utilized resources, Moab can use its dynamic job facilities to grow and shrink this job and thus the underlying service to proper balance service and batch workload needs.Because Moab is only interacting with the service externally, service requests can be immediately processed directly by the service itself. Moab imposes no overhead or delay. Because Moab is scheduling the service's resource allocation as a virtual job, full accounting and resource monitoring is available and a single point of policy and administration of cluster workload is available to the cluster administrators. To all other users, the packaged distributed service merely looks like yet another batch job.