SourceForge : View Wiki Page: JobAndWorkflowDescriptionJD

Search Wiki Pages Project: GSA-RG Wiki > JobAndWorkflowDescriptionJD > View Wiki Page

wiki1616: JobAndWorkflowDescriptionJD

Job and workflow description (JD) requirements

Task: link

Relevant to Grid Scheduling:

Access to information about the job specifics (what is the job?)
and job requirements (what is required for the job?).
Need for workflow description:
* the Grid scheduler should be able to schedule a whole workflow
*e.g. DAG formulation

Resource Requirements Description

Resource Requirements Description contents & scope

R1. Resource requirements description for a given Grid job MUST contain all requirements that must be satisfied by Grid resources in order to run this job.
R2. Requirements description language MUST allow expressing requirements concerning various levels of detail and aspects of Grids (e.g. resource parameters such as free memory as well as more high-level metrics such as time, cost, reliability etc.)
R3. Resource requirements description MUST contain means for definition of requirements with regard to co-allocation of resources for distributed jobs (which run on multiple clusters/computers). Resource requirements for total (aggregated) amounts of resources as well as for distinct nodes MUST be allowed.
R4. Requirements description language MUST/SHOULD enable users to define their preferences in the form of business objectives. In this way a user could require not only a machine with at least certain amount of memory but also a machine with as large memory as possible, i.e. asking a scheduler to maximize the amount of memory of the selected machine).
R5. Requirements description language MUST/SHOULD enable users to specify required guarantees (e.g. requested reservation of resources for requested time period).

Resource Requirements Description Language features

R6. Requirements description language MUST be extensible (i.e. it MUST be possible to specify requirements concerning arbitrary metrics rather than limiting them to a pre-defined set).
R7. It MUST be well structuralized language in order to allow precise definition of expressions and easy automated processing by Grid entities.
R8. It SHOULD be possible to be edited by humans, i.e. not to complex to enable advanced users to define requirements using this language directly (at least for basic functionality)?

Relation to other descriptions/languages

R10. It MUST be possible to be referenced or included by other descriptions such as job and workflow descriptions. For instance, a workflow language MUST be able to refer to particular sets of resource requirements in definitions of single workflow nodes.
R11. It SHOULD allow using various constraint definition languages and arithmetic expressions languages (e.g. standard languages if ones are available).

Hide Details

	Versions		Associations		Attachments		Back Links

Version	Version Comment	Created By
Version 1		Philipp Wieder - 10/04/2006