Difference: UserGuideEMI2 (2 vs. 3)

Revision 32012-03-15 - AlviseDorigo

Line: 1 to 1
 
META TOPICPARENT name="UserDocumentation"

CREAM User's Guide for EMI-2

Line: 19 to 19
 "EGEE" "kuiken.nikhef.nl" "15001" "/O=dutchgrid/O=hosts/OU=nikhef.nl/CN=kuiken.nikhef.nl" "EGEE" "22"
Changed:
<
<
or the corresponding line for your VO. You also need to install the VO related .lsc files in the /etc/grid-security/vomsdir/<VO> directory. In a standard EMI UI installation, these settings should be already there.
>
>
or the corresponding line for your VO. You also need to install the VO related .lsc files in the /etc/grid-security/vomsdir/<VO> directory. In a standard EMI UI installation, these settings should be already there.
  Make moreover sure you have in the directory $HOME/.globus your certificate/key pair, i.e. the following files:
Line: 66 to 66
  The most relevant commands to interact with CREAM based CEs are:
Changed:
<
<
  • glite-ce-job-submit <jdl_file>
>
>
  • glite-ce-job-submit <jdl_file_1> <jdl_file_2> ... <jdl_file_N>
 
  • glite-ce-delegate-proxy <delegation_Id>
Changed:
<
<
  • glite-ce-job-status <job_Ids>
>
>
  • glite-ce-job-status <job_Id_1> <job_Id_2> ... <job_Id_N>
 
  • glite-ce-job-list <host[:port]>
Changed:
<
<
  • glite-ce-job-cancel <job_Ids>
  • glite-ce-job-suspend <job_Ids>
  • glite-ce-job-resume <job_Ids>
  • glite-ce-job-output <job_Ids>
  • glite-ce-job-purge <job_Ids>
  • glite-ce-proxy-renew <delegation_Ids>
>
>
  • glite-ce-job-cancel <job_Id_1> <job_Id_2> ... <job_Id_N>
  • glite-ce-job-suspend <job_Id_1> <job_Id_2> ... <job_Id_N>
  • glite-ce-job-resume <job_Id_1> <job_Id_2> ... <job_Id_N>
  • glite-ce-job-output <job_Id_1> <job_Id_2> ... <job_Id_N>
  • glite-ce-job-purge <job_Id_1> <job_Id_2> ... <job_Id_N>
  • glite-ce-proxy-renew <delegation_Id_1> <delegation_Id_2> ... <delegation_Id_N>
 
  • glite-ce-service-info <host[:port]>
  • glite-ce-get-cemon-url <host[:port]>
  • glite-ce-enable-submission <host[:port]>
Line: 87 to 87
 $ --help
Changed:
<
<
glite-ce-job-submit submits a job to a CREAM based CE. It requires a JDL file as input and returns a CREAM job identifier.
>
>
glite-ce-job-submit submits N jobs (N must be >=1) to a CREAM based CE. It requires N JDL files as input and returns N CREAM job identifiers.
  glite-ce-delegate-proxy allows the user to delegate her proxy credential to the CREAM service. This delegated credential can then be used for job submissions.
Changed:
<
<
glite-ce-job-status displays information (in particular the states) of jobs previously submitted to CREAM based CEs.
>
>
glite-ce-job-status displays information (in particular the states) of N jobs (N must be >=1) previously submitted to CREAM based CEs.
  glite-ce-job-list lists the identifiers of jobs submitted to a CREAM based CE by the user issuing the command.
Changed:
<
<
glite-ce-job-cancel cancels one or more jobs previously submitted to CREAM based CEs.
>
>
glite-ce-job-cancel cancels N jobs (N must be >=1) previously submitted to CREAM based CEs.
 
Changed:
<
<
glite-ce-job-suspend suspends the execution of one or more jobs previously submitted to CREAM based CEs.
>
>
glite-ce-job-suspend suspends the execution of N jobs (N must be >=1) previously submitted to CREAM based CEs.
 
Changed:
<
<
glite-ce-job-resume resumes the execution of one or more jobs which have been previously suspended.
>
>
glite-ce-job-resume resumes the execution of N jobs (N must be >=1) which have been previously suspended.
 
Changed:
<
<
glite-ce-job-output retrieves the output sandbox files of one or more jobs previously submitted to CREAM based CEs.
>
>
glite-ce-job-output retrieves the output sandbox files of N jobs (N must be >=1) previously submitted to CREAM based CEs.
 
Changed:
<
<
glite-ce-job-purge clears one or more jobs from CREAM based CEs. After this operation the purged jobs can’t be managed anymore.
>
>
glite-ce-job-purge clears N jobs (N must be >=1) from CREAM based CEs. After this operation the purged jobs can’t be managed anymore.
 
Changed:
<
<
glite-ce-proxy-renew renews delegations, and therefore refreshes the proxy of the jobs submitted to CREAM based CEs using the considered delegations.
>
>
glite-ce-proxy-renew renews N delegations (N must be >=1), and therefore refreshes the proxy of the jobs submitted to CREAM based CEs using the considered delegations.
  glite-ce-service-info returns information about the CREAM service (version, status, etc.).
Line: 121 to 121
 

0.1 Submitting jobs to CREAM based CEs

Changed:
<
<
To submit jobs to CREAM based CEs, the command glite-ce-job-submit must be used. The glite-ce-job-submit command requires as input a job description file, which describes the job characteristics and requirements through the JDL (Job Description Language). A typical example of a JDL job description file is:
>
>
To submit jobs to CREAM based CEs, the command glite-ce-job-submit must be used. The glite-ce-job-submit command requires as input one or more job description files; each file describes the job characteristics and requirements through the JDL (Job Description Language). A typical example of a JDL job description file is:
 
[
Line: 142 to 142
  A detailed description of the available JDL attributes and of the rules for building correct JDL files is provided at http://wiki.italiangrid.org/twiki/bin/view/CREAM/JdlGuide.
Changed:
<
<
Each job submitted to a CREAM based CE is given the delegated credentials of the user who submitted it. These credentials can then be used when operations requiring security support has to be performed by the job.
>
>
The jobs submitted to a CREAM based CE are given the delegated credentials of the user who submitted it. These credentials can then be used when operations requiring security support has to be performed by the job.
  There are two possible options to deal with proxy delegation:
  • asking the “automatic” delegation of the credentials during the submission operation;
Line: 162 to 162
 The identifier of the delegation is then specified with the --delegationId ( -D) option in the job submit operation:
Changed:
<
<
> glite-ce-job-submit -D mydelid -r cream-ce-01.pd.infn.it:8443/cream-lsf-grid02 myjob1.jdl
>
>
> glite-ce-job-submit -D mydelid -r cream-ce-01.pd.infn.it:8443/cream-lsf-grid02 myjob1.jdl myjob2.jdl myjob3.jdl
 

The option -r ( --resource) has been used to specify the identifier of the CREAM CE where the job has to be submitted to.

Changed:
<
<
myjob1.jdl is the JDL file describing the job to be submitted.
>
>
myjob1.jdl myjob2.jdl myjob3.jdl are the 3 JDL files describing the jobs to be submitted.
 
Changed:
<
<
The command returns the CREAM job identifier associated with this job (e.g. https://cream-ce-01.pd.infn.it:8443/CREAM116j9vgnf) which identifies it in clear and unique way all over the Grid system scope.
>
>
The command returns the CREAM job identifiers associated with these jobs (e.g. https://cream-ce-01.pd.infn.it:8443/CREAM116j9vgnf) which identify them in clear and unique way all over the Grid system scope.
 

0.1 Monitoring jobs

Changed:
<
<
Passing the CREAM job id returned by the glite-ce-job-submit command to the glite-ce-job-status command, it is possible to monitor the submitted job. Several (static and dynamic) information can be shown, depending on the chosen verbosity level. The verbosity level can be 0 (less verbosity), 1 or 2 (most verbosity).
>
>
Passing the CREAM job identifiers returned by the glite-ce-job-submit command to the glite-ce-job-status command, it is possible to monitor the submitted jobs. Several (static and dynamic) information can be shown, depending on the chosen verbosity level. The verbosity level can be 0 (less verbosity), 1 or 2 (most verbosity).
  Please note that specifying 0 as verbosity level means calling on the CREAM service a faster operation than when using 1 or 2 as verbosity level.
Line: 216 to 216
  Instead of explicitly specifying the identifiers of the jobs to monitor, the user can also ask to monitor all her jobs, in case specifying conditions (on the submission date and/or on the job status) that must be met.
Changed:
<
<
For example to monitor all jobs, whose status is DONE-OK or DONE-FAILED, submitted to the grid005.pd.infn.it CREAM CE between July 23, 2005 10:00 and July 28, 2005 11:00, the following command must be issued:
>
>
For example to monitor all jobs, whose status is DONE-OK or DONE-FAILED, submitted to the grid005.pd.infn.it CREAM CE between July 23, 2005 10:00 and July 28, 2005 11:00, the following command must be issued:
 
> glite-ce-job-status --all -e grid005.pd.infn.it:8443 --from 2005-07-23 10:00:00 --to 2005-07-28 11:00:00 -s DONE-OK:DONE-FAILED
Line: 234 to 234
 output will be stored in the dir ./cream-38.pd.infn.it_8443_CREAM295728364
Added:
>
>
This command can be used also to retrieve output produced by multiple jobs, by specifying multiple job identifiers as command's arguments .
 

0.1 Getting job identifiers

If a user is interested to get the identifiers of all her jobs submitted to a specific CREAM CE, she can use the glite-ce-job-list command. For example the following command returns the identifiers of all the jobs submitted to the specified CREAM CE, owned by the user issuing the command:

Line: 258 to 260
  A running or idle job can be suspended (i.e. its execution will be stopped), and be resumed (i.e. it will run again) later. This can be achieved with the glite-ce-job-suspend and glite-ce-job-resume commands.
Changed:
<
<
The following example shows that after having issued the glite-ce-job-suspend command, after a while the job status becomes HELD.
>
>
The following example shows that after having issued the glite-ce-job-suspend command, after a while the job status becomes HELD.
 
> glite-ce-job-suspend https://cream-ce-01.pd.infn.it:8443/CREAM11a79tnb2
Line: 280 to 282
 

0.1 Purging jobs

Changed:
<
<
A CREAM job can be monitored (via the glite-ce-job-status) even after it has completed its execution. A job gets “lost” (i.e. it is not possible to monitor or manage it anymore) only when the user who submitted it decides to explicitly clear it, or when the CREAM system administrator decides to do this purging operation. A user can purge her own jobs, using the glite-ce-job-purge command.
>
>
A CREAM job can be monitored (via the glite-ce-job-status) even after it has completed its execution. A job gets “lost” (i.e. it is not possible to monitor or manage it anymore) only when the user who submitted it decides to explicitly clear it, or when the CREAM system administrator decides to do this purging operation. A user can purge her own jobs, using the glite-ce-job-purge command.
  E.g., after having issued the command:
Line: 306 to 308
 

0.1 Handling job identifiers

Changed:
<
<
Handling the job identifiers directly quickly becomes tedious. To avoid this, you can make the glite-ce-job-submit and glite-ce-job-list commands append the job Id(s) to a named file using the --output ( -o) option. On the other side, the CREAM client commands which take job identifier(s) as argument accept also the =--input (=-i) option which allows the job identifier(s) to be read from a file.
>
>
Handling the job identifiers directly quickly becomes tedious. To avoid this, you can make the glite-ce-job-submit and glite-ce-job-list commands append the job Id(s) to a named file using the --output (-o) option. On the other side, the CREAM client commands which take job identifier(s) as argument accept also the --input (-i) option which allows the job identifier(s) to be read from a file.
  The following shows an example:
Line: 361 to 363
 

0.1 Getting information about the CREAM service

Changed:
<
<
It is possible to get information about the CREAM service (interface and service version, status, etc) using the glite-ce-service-info command, e.g.:
>
>
It is possible to get information about the CREAM service (interface and service version, status, etc) using the glite-ce-service-info command, e.g.:
 
> glite-ce-service-info cream-13.pd.infn.it:8443
Line: 414 to 416
  We list here the possible attributes that can be specified in the configuration files:
Changed:
<
<
  • CREAM_URL_PREFIX: the prefix to the <hostname>:<port> to build the CREAM service endpoint. The default is https://.
>
>
  • CREAM_URL_PREFIX: the prefix to the <hostname>:<port> to build the CREAM service endpoint. The default is https://.
 
Changed:
<
<
  • CREAMDELEGATION_URL_PREFIX: the prefix to the <hostname>:<port> to build the CREAM delegation service endpoint. The default is https://.
>
>
  • CREAMDELEGATION_URL_PREFIX: the prefix to the <hostname>:<port> to build the CREAM delegation service endpoint. The default is https://.
 
  • DEFAULT_CREAM_TCPPORT: the port to be appended to the hostname (if not specified by the user) to build the CREAM and CREAM delegation service endpoint. The default is 8443.
Changed:
<
<
  • CREAM_URL_POSTFIX: the postfix to be appended to the <hostname>:<port> to build the CREAM service endpoint. The default is /ce-cream/services/CREAM2.
>
>
  • CREAM_URL_POSTFIX: the postfix to be appended to the <hostname>:<port> to build the CREAM service endpoint. The default is /ce-cream/services/CREAM2.
 
Changed:
<
<
  • CREAMDELEGATION_URL_POSTFIX: the postfix to be appended to the <hostname>:<port> to build the CREAM delegation service endpoint. The default is /ce-cream/services/gridsite-delegation.
>
>
  • CREAMDELEGATION_URL_POSTFIX: the postfix to be appended to the <hostname>:<port> to build the CREAM delegation service endpoint. The default is /ce-cream/services/gridsite-delegation.
 
  • JDL_DEFAULT_ATTRIBUTES: the classad that must be included by default in the user’s JDLs. The default is an empty classad.
Changed:
<
<
  • STATUS_VERBOSITY_LEVEL: the default verbosity level to be used for the glite-ce-job-status command. The default value is 0.
>
>
  • STATUS_VERBOSITY_LEVEL: the default verbosity level to be used for the glite-ce-job-status command. The default value is 0.
 
Changed:
<
<
  • UBERFTP_CLIENT is the pathname of the uberftp client executable. The default value is /usr/bin/uberftp.
>
>
  • UBERFTP_CLIENT is the pathname of the uberftp client executable. The default value is /usr/bin/uberftp.
 
Changed:
<
<
  • SUBMIT_LOG_DIR: the directory where by default the log file glite-ce-job-submit_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-submit command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • SUBMIT_LOG_DIR: the directory where by default the log file glite-ce-job-submit_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-submit command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • DELEGATE_LOG_DIR: the directory where by default the log file glite-ce-delegate-proxy_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-delegate-proxy command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • DELEGATE_LOG_DIR: the directory where by default the log file glite-ce-delegate-proxy_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-delegate-proxy command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • STATUS_LOG_DIR: the directory where by default the log file glite-ce-job-status_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-status command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • STATUS_LOG_DIR: the directory where by default the log file glite-ce-job-status_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-status command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • LIST_LOG_DIR: the directory where by default the log file glite-ce-job-list_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-list command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • LIST_LOG_DIR: the directory where by default the log file glite-ce-job-list_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-list command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • SUSPEND_LOG_DIR: the directory where by default the log file glite-ce-job-suspend_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-suspend command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • SUSPEND_LOG_DIR: the directory where by default the log file glite-ce-job-suspend_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-suspend command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • RESUME_LOG_DIR: the directory where by default the log file glite-ce-job-resume_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-resume command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • RESUME_LOG_DIR: the directory where by default the log file glite-ce-job-resume_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-resume command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • CANCEL_LOG_DIR: the directory where by default the log file glite-ce-job-cancel_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-cancel command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • CANCEL_LOG_DIR: the directory where by default the log file glite-ce-job-cancel_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-cancel command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • JOBOUTPUT_LOG_DIR: the directory where by default the log file glite-ce-job-output_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-output command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • JOBOUTPUT_LOG_DIR: the directory where by default the log file glite-ce-job-output_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-output command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • PURGE_LOG_DIR: the directory where by default the log file glite-ce-job-purge_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-purge command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • PURGE_LOG_DIR: the directory where by default the log file glite-ce-job-purge_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-job-purge command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • ALLOWEDSUB_LOG_DIR: the directory where by default the log file glite-ce-allowed-submission_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-allowed-submission command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • ALLOWEDSUB_LOG_DIR: the directory where by default the log file glite-ce-allowed-submission_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-allowed-submission command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • ENABLE_LOG_DIR: the directory where by default the log file glite-ce-enable-submission_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-enable-submission command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • ENABLE_LOG_DIR: the directory where by default the log file glite-ce-enable-submission_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-enable-submission command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • DISABLE_LOG_DIR: the directory where by default the log file glite-ce-disable-submission_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-disable-submission command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • DISABLE_LOG_DIR: the directory where by default the log file glite-ce-disable-submission_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-disable-submission command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • PROXYRENEW_LOG_DIR: the directory where by default the log file glite-ce-proxy-renew_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-proxy-renew command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • PROXYRENEW_LOG_DIR: the directory where by default the log file glite-ce-proxy-renew_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-proxy-renew command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • GETSERVICEINFO_LOG_DIR: the directory where by default the log file glite-ce-service-info_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-service-info command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • GETSERVICEINFO_LOG_DIR: the directory where by default the log file glite-ce-service-info_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-service-info command) is created. The default is /tmp/glite_cream_cli_logs.
 
Changed:
<
<
  • GETCEMONURL_LOG_DIR: the directory where by default the log file glite-ce-get-cemon-url_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-get-cemon-url command) is created. The default is /tmp/glite_cream_cli_logs.
>
>
  • GETCEMONURL_LOG_DIR: the directory where by default the log file glite-ce-get-cemon-url_CREAM_<username>_<date>_<time>.log (created when the --debug option is used with the glite-ce-get-cemon-url command) is created. The default is /tmp/glite_cream_cli_logs.
 As mentioned above, if the same attribute is defined in more than a configuration file, the definition in the user specific configuration file (if any) has higher priority than the definition in the VO specific configuration file (if any), which has higher priority than the definition in the generic configuration file. If an attribute is not defined anywhere, the default value is considered.
Line: 712 to 714
  The CREAM CE allows to forward, via tha BLAH component, requirements to the batch system.
Changed:
<
<
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 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.
Changed:
<
<
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 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 :
Line: 736 to 738
 CeRequirements= "other.GlueHostMainMemoryRAMSize > 100";
Changed:
<
<
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.
>
>
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:
Line: 744 to 746
 CeRequirements="other.GlueHostMainMemoryRAMSize > 100 && other.GlueCEStateWaitingJobs <10 && other.GlueCEImplementationName==\"CREAM\" && other.GlueHostProcessorClockSpeed >= 2800 && (Member(\"FDTD\", other.GlueHostApplicationSoftwareRuntimeEnvironment))";
Changed:
<
<
the following settings will be available in $GLITE_LOCATION/bin/xxx_local_submit_attributes.sh:
>
>
the following settings will be available in $GLITE_LOCATION/bin/xxx_local_submit_attributes.sh:
 
GlueHostMainMemoryRAMSize_Min='100'
Line: 756 to 758
  What is printed by the /usr/bin/xxx_local_submit_attributes.sh script is automatically added to the submit command file.
Changed:
<
<
For example if the JDL Cerequirements expression is:
>
>
For example if the JDL CeRequirements expression is:
 
CeRequirements = "(Member(\"FDTD\", other.GlueHostApplicationSoftwareRuntimeEnvironment))";
Line: 793 to 795
  is set via the /usr/bin/pbs_local_submit_attributes.sh script.
Changed:
<
<
Please note that there are no differences if in CeRequirements expresssion there is e.g.
>
>
Please note that there are no differences if in CeRequirements expresssion there is e.g.
 
CeRequirements = other.xyz==\"ABC\"
Line: 815 to 817
 
Changed:
<
<
Starting with EMI-2 (i.e. BLAH v. >= 1.18) it is possible to forward to the batch system also other attributes not included in the CERequiments JDL attribute.
>
>
Starting with EMI-2 (i.e. BLAH v. >= 1.18) it is possible to forward to the batch system also other attributes not included in the CeRequiments JDL attribute.
  This can be done adding in /etc/blah.config the line:
Line: 879 to 881
  -- MassimoSgaravatto - 2012-03-14
Changed:
<
<
-- AlviseDorigo - 2012-03-14
>
>
-- AlviseDorigo - 2012-03-15
 
META FILEATTACHMENT attachment="cream_job_states.jpg" attr="" comment="" date="1331716396" name="cream_job_states.jpg" path="cream_job_states.jpg" size="18586" user="AlviseDorigo" version="1"
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback