Difference: UserGuideEMI2 (20 vs. 21)

Revision 212012-05-15 - AlviseDorigo

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

CREAM User's Guide for EMI-2

Line: 1161 to 1161
 
Changed:
<
<
In the last example, the activity represent a job to execute, and it is not a system executable (like the /bin/sleep of the previous example); the executable is built up by the user, myjob.sh, and must be staged out from a storage server (cream-23.pd.infn.it in this example; see again the <Source> node in the ADL above) running a GridFTP daemon, into the activity's directory in the CE. We do not enter into the job's details: simply note that the user's executable produces a standard output, and a standard error that will be redirected to dedicated files (the JobOutput.txt and JobError.txt specified in the ADL above). The standard output will contain the print of a particular user-defined environment variable (MY_ENV, see the ADL above) and an echo message; the standard error will contain an error message triggered by operations that the user cannot perform on the destination worker node.
>
>
In the last example, the activity represents a job to execute, and it is not a system executable (like the /bin/sleep of the previous example); the executable is built up by the user, myjob.sh, and must be staged out from a storage server (cream-23.pd.infn.it in this example; see again the <Source> node in the ADL above) running a GridFTP daemon, into the activity's directory in the CE. We do not enter into the job's details: simply note that the user's executable produces a standard output, and a standard error that will be redirected to dedicated files (the JobOutput.txt and JobError.txt specified in the ADL above). The standard output will contain the print of a particular user-defined environment variable (MY_ENV, see the ADL above) and an echo message; the standard error will contain an error message triggered by operations that the user cannot perform on the destination worker node.
 
Changed:
<
<
In the ADL it is written that the two files JobOutput.txt and JobError.txt must be sent to the storage server (the same GridFTP server seen before for the executable stage-out) cream-23.pd.infn.it; of course it could be a different storage server. The user can retrieve these output files by mean of hist/her preferred GridFTP client. For example:
>
>
In the ADL it is written that the two files JobOutput.txt and JobError.txt must be sent to the storage server (the same GridFTP server seen before for the executable stage-out) cream-23.pd.infn.it; of course it could be a different storage server. The user can retrieve these output files by mean of his/her preferred GridFTP client. For example:
 

$ globus-url-copy gsiftp://cream-23.pd.infn.it/tmp/JobOutput.txt JobOutput.txt
Line: 1773 to 1773
 We've just seen the meaning of the former. The CLIENT-DATAPULL-DONE is to be sent when the activity is terminated, and output files, available on the CE in the "STAGEOUT Dir", have been retrieved by the user.

Creating and handling a delegation

Changed:
<
<
A delegation (or delegated proxy) is a temporary proxy certificate created by the server and signed by the user with his/her personal certificate. This delegation resides on the server and is used by ES to perform operations that require authentication. Then, these operations will be performed on behalf of the user that signed the delegation. Actually the only operations that need a delegation are file transmission to/from storage elements that require authentication. In fact a delegation must be specified in the ADL only if there're Intput/Output sandboxes to move around (see above).
>
>
A delegation (or delegated proxy) is a temporary proxy certificate created by the server and signed by the user with his/her personal certificate. This delegation resides on the server and is used by ES to perform operations that require authentication. Then, these operations will be performed on behalf of the user that signed the delegation. Actually the only operations that need a delegation are file transmission to/from storage elements that require authentication. In fact a delegation must be specified in the ADL only if there're Intput/Output sandboxes to move around that need authentication to get access (see above). If the sandboxes do not need authentication (e.g. they're available through "simple" HTTP protocol) the delegation is not needed.
  A delegation is always associated to a delegation identifier string (1:1). The delegation identifier is the handle the user can use in the ADL, or as argument to ask information about the related delegation or to renew it.

Creating a delegation

Line: 1788 to 1788
 There's a problem with proxyfile [/tmp/x509up_u501]: The proxy has EXPIRED! ---+++ Asking information about a delegation
Changed:
<
<
With the command glite-es-delegation-info the user can ask for delegation's information:
>
>
with the command glite-es-delegation-info the user can ask for delegation's information:
 
$ glite-es-delegation-info -e cream-52.pd.infn.it 8070042623506658
Lifetime = Wed Mar 28 21:31:19 2012
 
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