Hi Hrabi, All, we are basically map a subset of JSDL elements to DRMAA Job template routines and Mandatory Job attributes. There are a few attributes that are directly mapped: DRMAA_JOB_NAME JobIdentification/JobName DRMAA_JOB_CATEGORY JobIdentification/JobAnnotation DRMAA_REMOTE_COMMAND POSIXApplication/Executable DRMAA_V_ARGV POSIXApplication/Argument DRMAA_V_ENV POSIXApplication/Environment DRMAA_INPUT_PATH POSIXApplication/Input DRMAA_OUTPUT_PATH POSIXApplication/Output DRMAA_ERROR_PATH POSIXApplication/Error DRMAA_WD POSIXApplication/WorkingDirectory Also, we use an extension element in JSDL that allows us to easily describe bulk jobs (their start, end, increment). These fields are accordingly mapped to DRMAA calls (drmaa_run_bulk_jobs). As for file staging, JSDL's DataStaging element is used. The following elements are supported: FileName, CreationFlag, DeleteOnTermination, Source/URI, Target/URI. Consult OpenDSP manual for their exact meaning. http://sourceforge.net/project/showfiles.php?group_id=156652 Thanks, Chris and Piotr Rajic, Hrabri pisze:
Talking about JSDL and DRMAA, have a look at OpenDSP: http://www.fedstage.com/welcome/?Open_Source:Grid_Application_Frameworks
Chris,
Could you give us more details here?
Thx
Hrabri
-----Original Message----- From: drmaa-wg-bounces@ogf.org [mailto:drmaa-wg-bounces@ogf.org] On
Behalf
Of Daniel Templeton Sent: Tuesday, May 22, 2007 12:03 PM To: DRMAA Working Group Subject: [DRMAA-WG] DRMAA Working Group Meeting Minutes For 22 May 2007
DRMAA Working Group Meeting 22 May 2007
o 1 April 2007 minutes accepted o Agreed to send spec to editor for publishing * Should articulate that we have handled the feedback o We should expect an experience doc for "another" DRM o Tracker 5882 * Agreed to make the change * Duplicate of tracker 5493 o Tracker 5873 * Clarification sentence will be added * Will wait to deal with adding to additional attributes * Concern about implementability of adding incr to all attributes - Need to look to what DRM vendors are able to support o Tracker 5883 * Current spec returns DRMAA_ERRNO_INVALID_ARGUMENT * IDL spec return DRMAA_ERRNO_UNSUPPORTED_ATTRIBUTE * Cannot make arbitrary functionality changes * Acknowledge that the problem exists and that it is fixed in the IDL spec * Will reply directly to Chris o Tracker 5884 * Native specification is an unpredictable wildcard - Use is at the user's peril - We don't need to try to prevent it * We do need to clarify that run_job and run_bulk_jobs are
non-blocking
- State that the routines *return after* sending the job(s) to the
grid
* Need to be sure that the native spec desc is clear that it can violate the API spec - Native spec SHOULD not violate the API spec * Same applies to job category o Tracker 5881 * Consider a DRMAA JSDL profile o Hrabri will update the docs and send them out for review o Will submit doc after review of changes o What do we do with the IDL spec? * After 1.0 is published, then we start publishing our other docs - Avoid confusing the committee o Should add a timeline for when we're submitting things * Less urgent since OGF 20 is over o Hrabri out Mid-July until mid-August
Daniel -- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg
-- drmaa-wg mailing list drmaa-wg@ogf.org http://www.ogf.org/mailman/listinfo/drmaa-wg