Job submission and control

Concepts and terms

A workunit is a computation to be performed: a job. It may include any number of input files. It has various attributes, such as resource requirements and deadline. A workunit is associated with an application, not with an application version. In other words, you don't specify what platform the job is to be run on.

A result describes an instance of a computation, either unstarted, in progress, or completed. Each result is associated with a workunit. There may be several instances, or "replicas", of a given workunit.

Input and output templates

Each

• Input and output templates

Local job submission

• Staging input files
• Submitting jobs locally
• Work generators
• Local web-based job submission
  • User file sandbox
  • Examples: Autodock? LAMMPS, Tree threader

Remote job submission

• Remote job submission
  • Remote input file management
  • Remote access to output files
  • Job submission, monitoring, and control
  • Logging of remote job submission

Job keywords

• Job keywords

Managing multiple job submitters

• Access control and quotas
• Prioritizing jobs

• Canceling jobs

Targeted jobs

• Broadcast and targeted jobs
• Single job submission
• Multi-size applications
• Condor/BOINC integration
• Pinning jobs to app version numbers

Job dispatch policy

• Accelerated batch completion