On Mar 22, 2010, at 8:25 PM, [email protected] wrote: > > Hi, > > Does it support <extensions> mechanism as in GRAM 4? > > > Cheers, > Yuriy >
GRAM5 uses a different system for processing extensions. There is an RSL validation file for each LRM that is used to determine what RSL attributes are valid, when they can be used, and what their default values are. The lrm interface tutorial (for adding support for a new system) includes an example of a script that adds enumerated values for an existing attribute (queue). See http://www.globus.org/toolkit/docs/5.0/5.0.0/execution/gram5/developer/scheduler-tutorial-perl.html This document: http://www.globus.org/api/c-globus-5.0.0/globus_gram_job_manager/html/globus_gram_job_manager_rsl_validation_file.html describes the format of that file. Once an attribute is defined in the rvf file for an LRM, GRAM will allow that attribute in job requests. The LRM script can then use the job description perl interface to extract the value of the new job attribute. Note that there is no extension handling interface in the perl, you'd need to modify the LRM's submit method to do something meaningful with that new attribute. Joe
