Difference: UserGuideEMI2 (15 vs. 16)

Revision 162012-03-26 - AlviseDorigo

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

CREAM User's Guide for EMI-2

Line: 946 to 946
  glite-es-notify-service sends to the server, specified as endpoint, a notification message (see below for the kind of messages available)
Added:
>
>
glite-es-delegate-proxy delegates a proxy into the remote endpoint

glite-es-delegation-info asks about a pre-created delegation on a certain endpoint

glite-es-delegation-renew renew a pre-created delegation on a certain endpoint

 

Creating simple activities on ES based CEs (no Input/Output sandboxes)

The command glite-es-activity-create creates an activity on an ES based CE; it needs the specification of and endpoint where the creation request must be sent, and an XML file containing the activity description (described in ADL language: https://twiki.cern.ch/twiki/bin/view/EMI/EmiExecutionService). The XML must not contain any xml namespace. A simple example (sleeping job) is:

Line: 1343 to 1350
 
Changed:
<
<
Now the status's attributes CLIENT_STAGEOUT_POSSIBLE disappears:
>
>
Now the status's attributes CLIENT_STAGEOUT_POSSIBLE disappeared:
 

dorigoa@lxgrid05 14:46:46 ~/emi/creamui_emi2>stage/usr/bin/glite-es-activity-status CR_ES920948151 -e cream-05.pd.infn.it
Line: 1357 to 1364
 

Using an output file for the command glite-es-activity-create

Changed:
<
<
The activity creation command has the possibility to write (just) the activity identifier(s) into an output file. When this file is first created the user has nothing to take care about. If the file already exists, the user has to make sure that the output file has been already used for the same endpoint of the current activity creation. En example is better than any explanation (the special ADL file ~/JDLs/activity_sleep60_multiple.adl cointains 3 descriptions for 3 activities):
>
>
The activity creation command has the ability to write (just) the activity identifier(s) into an output file. When this file is first created the user has nothing to take care about. If the file already exists, the user has to make sure that the output file has been already used for the same endpoint of the current activity creation. En example is better than any explanation (the special ADL file ~/JDLs/activity_sleep60_multiple.adl cointains 3 descriptions for 3 activities):
 

$ glite-es-activity-create -e cream-05.pd.infn.it ~/JDLs/activity_sleep60_multiple.adl -o ids_cream-05 
Line: 1489 to 1496
 
Changed:
<
<

Obtain information about activities

>
>

Obtaining information about activities

 

Activity status

The command glite-es-activity-status has already been explained here and here.

Extended activity's information

Line: 1556 to 1563
 
Changed:
<
<
Refer to the EMI-ES documentation for a complete explanation of this output. As for the status, also with this command more than one activity identifier can be specified as argument, or an input file, or both.
>
>
Refer to the EMI-ES documentation for a complete explanation of this output.

As the status command, also glite-es-activity-info supports more than one activity identifier as argument, or an input file (option -i), or both.

 
Changed:
<
<

Obtain the activites created on an endpoint

>
>

Obtaining the activity identifier created on an endpoint

  To get a list of activities the user has created on a certain endpoint, the command glite-es-activity-list can be used:
Line: 1579 to 1588
 
Changed:
<
<
A certain user can see ONLY his/her activity identifiers (those ones created with his/her proxy certificate).
>
>
Remember that a certain user can see ONLY his/her activity identifiers (those ones created with his/her proxy certificate).
  glite-es-activity-list can redirect its output into a file; if this file already exists, it must be of the same type of the glite-es-activity-create 's one, i.e. it must contain the usual header line:
Line: 1626 to 1635
 
Changed:
<
<
Once created (or updated), this file can be used to feed glite-es-activity-status or glite-es-activity-info . As for the activity creation, if the output file already exists, it must contain activity identifiers created on the same endpoint where the user is asking the list currently:
>
>
Once created (or updated), this file can be used to feed glite-es-activity-status or glite-es-activity-info (and other commands we will se later). As for the activity creation, if the output file already exists, it must contain activity identifiers created on the same endpoint where the user is asking the list:
 

$ head -1 cream-10_activity_list 
Line: 1649 to 1658
 
Added:
>
>

Managing activities

Managing activities means: cancel them, pause them, resume them, restart them, wipe them when they're in TERMINAL state. All these operations are performed by the commands: glite-es-activity-cancel, glite-es-activity-pause, glite-es-activity-resume, glite-es-activity-restart, glite-es-activity-wipe. These commands have exactly the same syntax, then we will explain just once and we will used a symbolic name <command> for all of them.

The <command> 's syntax is simple:

<command> -e <endpoint> <Activity_ID_1> .. <Activity_ID_N>
Where N must be >= 1 (i.e. at least one activity ID is a mandatory argument); unless the user specify an input file as explained below.

The user can specify an input file (as for the glite-es-activity-status) instead of using <endpoint> and activity identifiers; or he/she can mixex input file and just activity identifiers. Then, the 3 possibilities of usage are:


<command> -e cream-05.pd.infn.it CR_ES075634021 CR_ES342891609 CR_ES832095061

or

<command> -i cream-10_activity_list

or

<command> -i cream-10_activity_list CR_ES081635022

 

-- MassimoSgaravatto - 2011-04-07

-- MassimoSgaravatto - 2012-03-14

Changed:
<
<
-- AlviseDorigo - 2012-03-21
>
>
-- AlviseDorigo - 2012-03-26
 
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