SourceForge : artf6522: Study feasibility, syntax and semantics of the OR relational operator for requirements in JSDL

Project: JSDL-WG Trackers > [PROVISIONAL] Feature requests > View Artifact

Artifact artf6522 : Study feasibility, syntax and semantics of the OR relational operator for requirements in JSDL

Tracker:	[PROVISIONAL] Feature requests
Title:	Study feasibility, syntax and semantics of the OR relational operator for requirements in JSDL
Description:	There is a strong need to be able to schedule grid jobs based off of things like Architecture and Operating system. There are also classes of jobs that do not need to be unnecessarily constrained to one particular set of resources. Relying solely on the tools provided in JSDL 1.0 can potentially eliminate sets of valid resources. To that end, we would like the ability to relay the information necessary to indicate that jobs can run on any of a set of valid resources. Some usage examples are: - Requesting to run a Java program on any machine type that supports Mac OS X or Linux, - Requesting to run an R program for which the architecture is 32-bit and either Windows or Mac OS X, - Requesting to run an arbitrary executable from a set of pre-compiled binaries. Only one of them will be staged in depending on the capabilities of the computing resource ( for example 32-bit windows machines with 2 G of available RAM, or 64-bit windows machines with 4 G of RAM). The members of the JSDL WG should study the feasibility, the syntax and the semantics of the OR relational operator for requirements in JSDL.
Submitted By:	Etienne URBAH
Submitted On:	11/16/2011 2:47 PM EST
Last Modified:	11/22/2011 4:14 AM EST

	Status / Comments		Change Log		Associations (3)		Attachments

Status
Group: *
Status:*	Open
Category: *
Customer: *
Priority: *	3
Assigned To: *	None
Reported in Release: *
Fixed in Release: *
Estimated Hours: *	0
Actual Hours: *	0

Comments

Michel Drescher: 11/22/2011 4:14 AM EST
	Action:	Move Moved from Activity schema to [PROVISIONAL] Feature requests

Etienne URBAH: 11/17/2011 1:11 PM EST

Comment:

- The JSDL range element already permits to express a flexible requirement on any value inside a contiguous interval of numbers.

- By comparison, the 'OR' relational operator is necessary to express a flexible requirement on :

1) Numbers which do NOT form a contiguous interval,

2) Attributes for which the several possible values have NOT been grouped into a dedicated group value,

3) Heterogeneous attributes.

Examples using GLUE 2.0 terminology from http://www.ogf.org/documents/GFD.147.pdf (in particular sections B.23 and B.24) :

1) My application has multi-threading optimized for ExecutionEnvironment.LogicalCPUs = 4, 8, 16, 32 or 64, but other values are NOT interesting.

2) My application is validated on operating systems based on Red Hat, but is known to fail on Debian. So, I can NOT specify ExecutionEnvironment.
OSFamily = 'linux'. I would like to specify ExecutionEnvironment.OSFamily = 'redhatfamily', but this has NOT been standardized yet, and I can NOT
rely on it. Therefore, I have to specify precisely ExecutionEnvironment.OSName = 'fedoracore' OR 'redhatenterpriseas' OR 'scientificlinux' OR
'scientificlinuxcern'.

3) My application, which is parallelized, will run most effectively on resources having many cores on the same machine, but will automatically use
MPI and provide correct results on resources having a fast bus :
-- ComputingShare.MaxSlotsPerJob >= 16
-- ExecutionEnvironment.LogicalCPUs >= 16 OR ExecutionEnvironment.NetworkInfo = 'infiniband' OR ExecutionEnvironment.NetworkInfo = 'myrinet'.

- This 'OR Relational Operator' is effectively included in 'Conditional Requirements', but is much easier and quicker to agree on, to specify and to
implement. Therefore, I would like to keep it in a separate tracker artifact leading to a quick JSDL profile.

Action:

Update

Michel Drescher: 11/17/2011 9:44 AM EST

Comment:

* Is this issue (32 vs. 64 bit) growing cold? Since these days people move to 64 at large anyway, we need to understand the importance.
* Use cases are required that make this issue relevant.
*ACTION Etienne: Check overlap and suggest folding artifacts together.

Action:

Update

Etienne URBAH: 11/16/2011 2:47 PM EST
	Action:	Create

Return

< Previous

Next >