Difference: UserGuide (3 vs. 4)

Revision 42011-04-29 - MassimoSgaravatto

Line: 1 to 1
META TOPICPARENT name="UserDocumentation"
The CREAM user's guide is available at: https://edms.cern.ch/document/595770

The CREAM user's guide is available at: https://edms.cern.ch/document/595770

CREAM User's Guide

1 Forward of requirements to the batch system

The CREAM CE allows to forward, via tha BLAH component, requirements to the batch system.

For this purpose the JDL =CERequirements- attribute, described at http://wiki.italiangrid.org/twiki/bin/view/CREAM/JdlGuide#3_27_CERequirements, can be used.

For direct submissions to the CREAM CE (e.g. jobs submitted to the CREAM CE using the CREAM CLI glite-ce-job-submit command) the CeRequirements attribute is supposed to be filled by the end-user.

For jobs submitted to the CREAM CE via the WMS, the CeRequirements attribute is instead filled by the WMS, considering the JDL Requirements expression and the value of the CeForwardParameters attribute in the WMS configuration file.

For example, if in the user JDL there is :

Requirements= "other.GlueHostMainMemoryRAMSize > 100 && other.GlueCEImplementationName==\"CREAM\"";

and if the WMS configuration file there is:

CeForwardParameters  = {"GlueHostMainMemoryVirtualSize","GlueHostMainMemoryRAMSize", "GlueCEPolicyMaxCPUTime"};

in the JDL sent by the WMS to CREAM there will be:

CeRequirements= "other.GlueHostMainMemoryRAMSize > 100";

The CERequirements expression received by CREAM is then forwarded to BLAH. Basically BLAH manages the CERequirements expression setting some environment variables, which are available and can be properly used by the /usr/bin/xxx_local_submit_attributes.sh script (e.g. /usr/bin/pbs_local_submit_attributes.sh for PBS/Torque, /usr/bin/lsf_local_submit_attributes.sh for LSF). This script must be properly created by the site admin.

For example, considering the following CeRequirements expression:

CeRequirements="other.GlueHostMainMemoryRAMSize > 100 && other.GlueCEStateWaitingJobs <10 && other.GlueCEImplementationName==\"CREAM\" && other.GlueHostProcessorClockSpeed >= 2800 && (Member(\"FDTD\", other.GlueHostApplicationSoftwareRuntimeEnvironment))";

the following settings will be available in $GLITE_LOCATION/bin/xxx_local_submit_attributes.sh:


What is printed by the /usr/bin/xxx_local_submit_attributes.sh script is automatically added to the submit command file.

For example if the JDL Cerequirements expression is:

CeRequirements = "(Member(\"FDTD\", other.GlueHostApplicationSoftwareRuntimeEnvironment))";

and the /usr/bin/pbs_local_submit_attributes.sh is:

if [ "$other.GlueHostApplicationSoftwareRuntimeEnvironment" == "FDTD" ]; then
 echo "#PBS -l software=FDTD"

then the PBS submit file that will be used will include:

# PBS directives:
#PBS -S /bin/bash
#PBS -o /dev/null
#PBS -e /dev/null
#PBS -l software=FDTD

where the line:

#PBS -l software=FDTD

is set via the /usr/bin/pbs_local_submit_attributes.sh script.

Please note that there are no differences if in CeRequirements expresssion there is e.g.

CeRequirements = other.xyz==\"ABC\"


CeRequirements = "xyz==\"ABC\"";

In both cases in /usr/bin/xxx_local_submit_attributes.sh the variable xyz will be set.

As shown above, having x>a or x>=a doesn't make any difference in the setting of the environment variable x in the /usr/bin/xxx_local_submit_attributes.sh script. It will be in both cases:


  -- MassimoSgaravatto - 2011-04-07 \ No newline at end of file
This site is powered by the TWiki collaboration platformCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback