Difference: UserGuideEMI2 (13 vs. 14)

Revision 142012-03-22 - AlviseDorigo

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

CREAM User's Guide for EMI-2

Line: 1238 to 1238
  In this example a new command has been introduced: glite-es-notify-service, that will be described more deeply later.
Added:
>
>

Both stage-in and stage-out performed by the user

Consider this ADL:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CreateActivities>
    <ActivityDescription>

        <ActivityIdentification>
            <Name>CustomJob</Name>
            <Description>A job that to run needs a file to be sent and writes its elaboration on an output file to be retrieved.</Description>
            <Type>single</Type> 
        </ActivityIdentification>

        <Application>
            <Executable>
                <Path>myjob.sh</Path>
                <Argument></Argument>
                <FailIfExitCodeNotEqualTo>0</FailIfExitCodeNotEqualTo>
            </Executable>
            <Environment>
              <Name>MY_ENV</Name>
              <Value>"my env"</Value>
            </Environment>
            <Error>JobError.txt</Error>
            <Output>JobOutput.txt</Output>
        </Application>
        <Resources>
            <QueueName>creamtest2</QueueName>
        </Resources>

        <DataStaging>
          <ClientDataPush>true</ClientDataPush>
          <OutputFile>
            <Name>JobError.txt</Name>
          </OutputFile>
          <OutputFile>
            <Name>JobOutput.txt</Name>
          </OutputFile>
        </DataStaging>

    </ActivityDescription>
</CreateActivities>

This ADL doesn't contain specification of <Target> node, which means that the CE doesn't have to send any files to any remote server; it will be up to the user to retrieve the JobOutput.txt and JobError.txt files. As before, just after activity creation, the CE will send back the client the paths for stage-in and stage out. Let's skip the description of stage-in of executabe myjob.sh already described above. The activity creation with this ADL will return (as usual):


$ glite-es-activity-create -e cream-05.pd.infn.it ~/JDLs/activity_files_push_pull.adl
*****************************************
ActivityID     = CR_ES342891609
ActivityMgrURI = https://cream-05.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService
Status         = PREPROCESSING
Status Attrs   = {CLIENT_STAGEIN_POSSIBLE}
Timestamp      = Thu Mar 22 12:05:01 2012
Description    = 
ETNSC          = 
STAGEIN Dir    = {gsiftp://cream-05.pd.infn.it/var/cream-es_sandbox/dteam/CN_Alvise_Dorigo_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam002/34/CR_ES342891609/ISB}
SESSION Dir    = {}
STAGEOUT Dir   = {gsiftp://cream-05.pd.infn.it/var/cream-es_sandbox/dteam/CN_Alvise_Dorigo_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam002/34/CR_ES342891609/OSB}

This time, in addition to the "STAGEIN Dir", the user has to consider the value of "STAGEOUT Dir"; when the activity will be finished, he/she will have to retrieve the two files by mean of the usual GridFTP client:

 

-- MassimoSgaravatto - 2011-04-07

 
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