[geclipse-dev] Instructions for Job Submission with DataStaging

[Nicholas Loulloudes <loulloudes.n@xxxxxxxxxxxx>]

Dear all,

During the last few days i performed  through our framework numerous job submissions that involved data staging either of input, output or both files. I'm now in the position to report, that a large percentage of these jobs were submitted and executed successfully. Furthermore, i was able to retrieve their output again from our framework. I only switched away from our framework when i had to check the Job Status (see below why).

Below i describe two ways so you can test job submission with data staging and report the outcome of your own tests.

g-Eclipse Version: 0.5.0.200706291635
WMS Used: WMS@xxxxxxxxxxxxxxxxxxxxxxx  (Please note that this WMS is the Production one which runs verion 3.02 and thus the Job Status cannot be retrieved. Job Status though can be retrieved through the UI using the command: glite-wms-job-status <JOBID>) 

[1]  You can use the following 3  JSDL files i uploaded in the [demo] folder of our CVS. These JSDL file are responsible for simple atomic operations

         - simple_hostname.jsdl : outputs the host name of the worker node the job was executed on.
         - simple_date.jsdl : outputs the time and date on which the job was executed.
         - simple_env.jsdl :  outputs the environmental variables of the Worker Node the job was executed on.

Note; The above three files write their output to the file "output.txt" which resides on the g-eclipse home directory of the CE at Linz. This output file was created by me for testing purposes

    [1.1] Download any of the above 3 files to your to a Grid Project. 
    [1.2] Create your VOMS proxy.
    [1.3] Mount "egee-ce1.gup.uni-linz.ac.at" using gsiftp as a filesystem. You should be able to see the file: output.txt in the directory.
    [1.4] Create a local Folder under the FileSystem.
    [1.5] Submit the job, and check periodically it's status from the UI until it becomes DONE.
    [1.6] Then copy using our framework, the remote output.txt file to the local directory you created, and open the file.
    [1.7] You should be able to see the result depending on the job you executed.



[2]     You can create yourself a JSDL file to describe the job you want to execute.

    [2.1] Create your VOMS proxy.
    [2.2] Mount a storage element from the Store element list supporting your VO. (For me egee-ce1.gup.uni-linz.ac.at always worked).
    [2.3] Create a local Folder under the FileSystem.
    [2.4] Create a text file in the local directory by giving it a distinct name (except output.txt) and copy it to the above storage element. (Don't copy the file in an existing directory because your job will fail to write it's output due to permission rights).
    [2.4] Open the Job Description Wizard to create a new JSDL file.
    [2.5] On the 2nd page enter executable you want to execute in the executable field (i.e /bin/hostname)
    [2.6] On the standard output field, click the browse button. Then expand the mounted storage element , select the file created in step 2.4 and click OK.
    [2.7] On the 3rd Page, click Add of the Stage-Out group. Click the browse button and select the file as you have done in step 2.6. Click Ok and in the file name enter the file name of the selected file. (without the path. i.e : output.txt)
    [2.8] Click Ok and submit the Job as normally. Check periodically it's status from the UI until it becomes DONE.
    [2.9] Then copy using our framework, the remote output.txt file to the local directory you created, and open the file to check the output.

If you phase any problems please let me know.

Best regards,

-- 
_________________________________________________

Nicholas Loulloudes
High Performance Computing Systems Laboratory (HPCL)
University of Cyprus,
Nicosia, Cyprus

Tel:  +357-22892663
Email: loulloudes.n@xxxxxxxxxxxx

Attachment: smime.p7s
Description: S/MIME cryptographic signature