4.5.1.1.
Overview
Up one level
The Job Service knows only how to start, check job status, and how to kill a job. In order to decouple Job Service and application wrapper bindings from resource managers, an extra layer of resource manager dependant platform scripts is introduced. This implies that Job Services can operate with different resource managers without changing the Job Service itself or the application wrappers.
The Job Service then can be configured to use platform scripts suitable for the underlying computing platform. Platform scripts then, know how to handle (start, check, kill) jobs for that particular computing platform, and can be instructed to run a particular application via its application wrapper.
Figure 1 illustrates how the platform script layer sits between the Job Service and application wrappers hiding resource manager details.
Figure 1. The job service interface and scripts
The GRIA Job Service requires the following platform scripts:
- Start job: this script knows how to submit jobs for a specific resource manager
- Check job: knows how to check the status of a job
- Kill job: knows how to terminate a job
The following sections describe in detail the API's and the required functionality for platform scripts.
Ideally, users should adopt one of the supplied platform scripts for running jobs using PBS, Condor or local execution. If it is necessary to develop platform scripts to address an unsupported execution platform, this can be done, but first read about the GRIA platform model.
