Changes between Initial Version and Version 1 of QCG_Broker_Client

Show
Ignore:
Timestamp:
06/10/11 17:13:16 (13 years ago)
Author:
piontek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QCG_Broker_Client

    v1 v1  
     1= QCG Broker Client = 
     2 
     3[[PageOutline]]  
     4 
     5= Requirements = 
     6* '''Java (>= 1.5)'''\\ 
     7{{{ 
     8#!div style="font-size: 90%" 
     9For SL5.x 
     10{{{#!sh 
     11yum install java-1.6.0-sun-compat.x86_64 
     12}}} 
     13}}} 
     14* '''QCG-Broker Client''' - for installation procedure see the [[installation_QCG_Broker_Client]] 
     15* '''User's credential''' 
     16  To secure the communication and authenticate the user to the service the X509 proxy certificate is needded. 
     17  Client expects the access either to proxy certificate file or to pair of user certificate and private key files in "pem" format. 
     18 
     19  If the user has the certificate in p12 format, the certificate has to be first converted to pem format files. 
     20{{{ 
     21  openssl pkcs12 -nocerts -in cert.p12 -out userkey.pem 
     22  openssl pkcs12 -clcerts -nokeys -in cert.p12 -out usercert.pem 
     23}}} 
     24 
     25 
     26= Configuration = 
     27To work properly and to authenticate user to the service, client has to be able to load user's proxy certificate and validate service credential during the handshake procedure. To do this it needs to know location of the file containing proxy certificate and directory containing public keys of Certificate Authorities it should trust. 
     28 
     29* Client looks for proxy according to following rules: 
     30{{{ 
     31#!div style="font-size: 90%" 
     32{{{#!default 
     33It first checks the X509_USER_PROXY system property. If the property 
     34is not set, it checks next the 'proxy' property in the current 
     35configuration. If that property is not set, then it defaults to a 
     36value based on the following rules:  
     37If a UID system property is set, and running on a Unix machine it 
     38returns /tmp/x509up_u${UID}. If any other machine then Unix, it returns 
     39${tempdir}/x509up_u${UID}, where tempdir is a platform-specific 
     40temporary directory as indicated by the java.io.tmpdir system property. 
     41If a UID system property is not set, the username will be used instead 
     42of the UID. That is, it returns ${tempdir}/x509up_u_${username} 
     43}}} 
     44}}} 
     45 
     46* Client looks for the CA directory according to following rules: 
     47{{{ 
     48#!div style="font-size: 90%" 
     49{{{#!sh 
     50It first checks the X509_CERT_DIR system property. If the property 
     51is not set, it checks next the 'cacert' property in the current 
     52configuration. If that property is not set, it tries to find 
     53the certificates using the following rules: 
     54First the ${user.home}/.globus/certificates directory is checked. 
     55If the directory does not exist, and on a Unix machine, the 
     56/etc/grid-security/certificates directory is checked next. 
     57If that directory does not exist and GLOBUS_LOCATION 
     58system property is set then the ${GLOBUS_LOCATION}/share/certificates 
     59directory is checked.  
     60}}} 
     61}}} 
     62 
     63CoG library configuration can be modified using the COG properties file `~/.globus/cog.properties` 
     64{{{ 
     65#!div style="font-size: 90%" 
     66{{{#!sh 
     67#Java CoG Kit Configuration File 
     68proxy=/tmp/x509up_u501 
     69cacert=/etc/grid-security/certificates/ 
     70}}} 
     71}}} 
     72 
     73Additionaly the location of user's certificate and private key must be specified.  
     74{{{ 
     75#!div style="font-size: 90%" 
     76{{{#!sh 
     77usercert=/home/piontek/.globus/usercert.pem 
     78userkey=/home/piontek/.globus/userkey.pem 
     79}}} 
     80}}} 
     81If they are specified and user proxy certificate doesn't exist it will be automatically created by the client. Otherwise the proxy certificate has to be created by `grid-proxy-init` tool. 
     82 
     83= Job Profile = 
     84Every experiment submitted to QCG-Broker has to be described by XML-based document called ''Job Profile''. The structure of ''Job Profile'' is formalized by [[http://node2.qoscosgrid.man.poznan.pl/~piontek/qcg-broker/QCGJobDescriptionSchema.xsd|Job Profile schema]]. 
     85 
     86Examples of Job Profiles describing basic use cases are distributed with QCG-Broker and can be found in `<CLIENT_DIR>/examples directory`. 
     87 
     88= Usage = 
     89 
     90The QCG-Groker command-line java based client can operate in two modes: 
     91 
     92* '''batch mode''' – that executes single operation with arguments passed directly to the client during its invocation. The batch mode allows to use the client in any kind of scripts mostly in cases when the processing of output is needed to steer the experiment, 
     93* '''console mode''' – that works similar to shell console in which user can type in lines with operations and arguments to be executed by service. The console mode gives additional useful features like aliases, history accessible by arrows-keys, creation and management of user proxy, help functionality.  
     94 
     95The usage of the client depends on the mode: 
     96* for batch mode: "`qcg-client OPRATION [ARG1 .. ARGn]`" 
     97* for console mode: "`qcg-client -console`" and then user is prompted to type in lines in format "`OPERATION [ARG1 .. ARGn]`" to be processed by client.  
     98 
     99'''IMPORTANT:''' To secure the communication between client and service and to delegate user's privileges to the service client needs access to user's proxy certificate. 
     100 
     101== Operations == 
     102 
     103Regardless from the mode the QCG-Broker java based command-line client supports following list of operations: 
     104 
     105||= '''Operation''' =||= '''Arguments''' =||= '''Description''' =|| 
     106||='''submit_job''' =|| `<desc_file>` (QCG or JSDL) || submits a job to be executed. The description of job can be expressed either in native QCG-Broker language or if it is possible in JSDL one. If the description is valid client returns to the user a globally unique job identifier, which unambiguously identifies the job in the system.  QCG defines jobs as a sets of dependent tasks that constitute a logical whole (workflow). Each task is executed by system only if all tasks it depends on are in specified by the user states. ||  
     107||='''list_jobs''' =|| `[<limit>]` `[<status>]` || lists jobs belonging to the `user`. It is possible either to `limit` number of jobs or to display only ones in given state. All possible states are listed below  the table. || 
     108||='''list_user_jobs''' =|| `[<limit>]` `[<status>]` `<user>` || lists jobs belonging to the given `user`. The functionality is destined for administrative purposes. || 
     109||='''test_description''' =|| `<desc_file>` (QCG or JSDL) || validates job description ||  
     110||='''translate_description''' =|| `<desc_file>` JSDL || translates job description to native QCG-Broker one || 
     111||='''job_info''' =|| `<jobId>` `[<showJobDesc>]` || return complex information about the given job. If the `showJobDesc is` `false` the job description is not shown || 
     112||='''cancel_job''' =|| `<jobId>` || cancels execution of the given job || 
     113||='''commit_job''' =|| `<jobId>` || allows to approve the job submitted with two phase commit mechanism to be processed by the system. The two phase commit mechanism can be used to register notifications before the processing of the job will be started by broker. || 
     114||='''list_tasks''' =|| `<jobId>` `[<status>]` || lists tasks belonging to given job. Optionally it is possible to specify the task's status. Possible task statuses are listed below the table. || 
     115||='''tasks_statuses''' =|| `<jobId>` `[<summary>]` || lists tasks constituting the given job with their statuses. If the `summary` argument is `true` some additionall statistics is displayed. || 
     116||='''register_job_notification''' || `<jobId>` `<url>` || registers notification consumer for the given job || 
     117||='''list_job_notifications''' =|| `<jobId>` || lists notifications registered for the given job || 
     118||='''register_tasks_notification''' =|| `<jobId>` `<url>` || register notification for all tasks of the given job || 
     119||='''monitor_job''' =|| `<jobId>` `[<interval>]` || monitors status changes of tasks belonging to given job. The `interval` argument determines delay in seconds between next status checks. || 
     120||='''monitor_task''' =|| `<jobId>` `<taskId>` `[<interval>]` || monitors status changes of allocations belonging to the given tasks. The `interval` argument determines delay in seconds between next status checks. || 
     121||='''task_info''' =|| `<jobId>` `<taskId>` `[<showDesc>` `[<limit>]]` || displays information about the given task. If the `showDesc` is `false` the task description is not shown. If the `limit` argument is specified the history of the task is limited to given value. =|| 
     122||='''register_task_notification''' =|| `<jobId>` `<taskId>` `<url>` || registers task's notification consumer || 
     123||='''list_task_notifications''' =|| `<jobId>` `<taskId>` || lists task's notifications || 
     124||='''cancel_task''' =|| `<jobId>` `<taskId>` || cancels execution of the given task || 
     125||='''commit_task''' =|| `<jobId>` `<taskId>` || commits the given task to be processed by the system || 
     126||='''reserve_resources''' =|| `[<taskId>]` `<job_desc>` (QCG or JSDL) || reserve resources that meet either the wole job or given task requirements. The reservation identifier is returned. This functionality is not implemented yet! || 
     127||='''reservation_info''' =|| `<reservationId>` || return complex information concerning the given reservation: list of reserved resources, local identifiers of reservations, reservation time slot. This functionality id not implemented yet! || 
     128||='''cancel_reservation''' =|| `<reservationId>` || releases reserved resources. This functionality is not implemented yet! || 
     129 
     130 
     131List of Job statuses: 
     132    * UNCOMMITTED - the job was submitted with two phase commit option and waits to be committed, 
     133    * SUBMITTED – the job was submitted to the system and is executed by the system, 
     134    * SUSPENDED – the job was suspended, 
     135    * ACTIVE – the job is active, at least one task is processed, 
     136    * FINISHED – the job was completed, 
     137    * FAILED – the job (at least one crucial task belonging to the job) failed 
     138    * CANCELED – the job was canceled by the user, 
     139    * BROKEN - one or more of crucial tasks failed, system waits until active tasks will finish and change the status of the job to FAILED.|  
     140 
     141List of Task statuses: 
     142    * UNSUBMITTED – the task cannot be started because of dependencies, 
     143    * UNCOMMITED - the task waits to be committed, 
     144    * QUEUED – the task was put into the queue and waits for execution, 
     145    * PREPROCESSING – system makes some actions needed to start the task (looks for the resource, stages in files), 
     146    * PENDING – the task is pending in the queueing-system, 
     147    * RUNNING – the task is active, 
     148    * STOPPED – the task was finished or was checkpointed, but system did not start staging out files, 
     149    * POSTPROCESSING – system makes some actions needed to complete the task, for example stages out files, cleares working environment, etc., 
     150    * FINISHED – the task was completed, 
     151    * SUSPENDED – the task was suspended, 
     152    * FAILED – the task failed, 
     153    * CANCELED – the task was canceled by the user. 
     154== Usage examples == 
     155 
     156The example presented below is the QCG-Broker Job Profile describing the parameter-sweep experiment executing a set of UNIX calendar tasks for the predefined space of "month" parameter. 
     157 
     158{{{ 
     159#!div style="font-size: 90%" 
     160{{{#!xml 
     161<qcgJob appId="calendar_example"> 
     162        <task persistent="true" taskId="calendar"> 
     163                <execution type="single"> 
     164                        <executable> 
     165                                <execFile> 
     166                                        <file> 
     167                                                <location type="URL">file:////usr/bin/cal</location> 
     168                                        </file> 
     169                                </execFile> 
     170                        </executable> 
     171                        <arguments> 
     172                                <value>${PS_month}</value> 
     173                                <value>2010</value> 
     174                        </arguments> 
     175                        <stdout> 
     176                                <file> 
     177                                        <location type="URL">${TASK_DIR}/stdout.txt</location> 
     178                                </file> 
     179                        </stdout> 
     180                </execution> 
     181                <parametersSweep> 
     182                        <parameter> 
     183                                <name>month</name> 
     184                                <value> 
     185                                        <loop> 
     186                                                <start>1</start> 
     187                                                <end>12</end> 
     188                                                <step>1</step> 
     189                                                <except> 
     190                                                        <value>3</value> 
     191                                                        <value>6</value> 
     192                                                </except> 
     193                                        </loop> 
     194                                </value> 
     195                        </parameter> 
     196                </parametersSweep> 
     197        </task> 
     198</qcgJob> 
     199}}} 
     200}}} 
     201 
     202=== submit_job === 
     203* `submit_job <job_profile>` - submits job. `<job_profile>` must be the path to the file containing the Job Profile. 
     204{{{ 
     205#!div style="font-size: 90%" 
     206{{{#!sh 
     207qcg-client submit_job ../examples/usecase8.xml 
     208Your identity: C=PL,O=GRID,O=PSNC,CN=Tomasz Piontek 
     209Creating proxy, please wait... 
     210Proxy verify OK 
     211Your proxy is valid until Tue May 17 02:55:47 CEST 2011 
     212UserDN = /C=PL/O=GRID/O=PSNC/CN=Tomasz Piontek 
     213ProxyLifetime = 0 Days 11 Hours 59 Minutes 57 Seconds 
     214 
     215jobId = 1305550554579_calendar_example_5366 
     216}}} 
     217}}} 
     218 
     219=== list_jobs === 
     220* `list_jobs [status] [limit]` - lists jobs. Optionally it is possible to specify status or limits the output to some number of recent jobs. 
     221{{{ 
     222#!div style="font-size: 90%" 
     223{{{#!sh 
     224qcg-client list_jobs 5 
     225UserDN = /C=PL/O=GRID/O=PSNC/CN=Tomasz Piontek 
     226ProxyLifetime = 0 Days 11 Hours 58 Minutes 47 Seconds 
     227 
     228Number of jobs: 5 
     229List of jobs:  
     2301301904727887_calendar_example_1403 
     2311304020897352_calendar_example_4252 
     2321304065465905_calendar_example_9526 
     2331305287977790_calendar_example_4779 
     2341305550554579_calendar_example_5366 
     235}}} 
     236}}} 
     237 
     238=== job_info === 
     239* `job_info <jobId> <showJobProfile>` - displays information about the given job. The `<showJobProfile>` argument of boolean type specifies whether the Job Profile should be displayed or not. 
     240{{{ 
     241#!div style="font-size: 90%" 
     242{{{#!sh 
     243qcg-client job_info 1305550554579_calendar_example_5366 false 
     244UserDN = /C=PL/O=GRID/O=PSNC/CN=Tomasz Piontek 
     245ProxyLifetime = 0 Days 11 Hours 58 Minutes 18 Seconds 
     246 
     247UserDN: /C=PL/O=GRID/O=PSNC/CN=Tomasz Piontek 
     248Project:  
     249Status: FINISHED 
     250StatusDesc:  
     251SubmissionTime: Mon May 16 14:55:54 CEST 2011 
     252FinishTime: Mon May 16 14:56:42 CEST 2011 
     253Number of tasks: 10 
     254Tasks: calendar_PSit0 calendar_PSit1 calendar_PSit2 calendar_PSit3 calendar_PSit4 calendar_PSit5 calendar_PSit6 calendar_PSit7 calendar_PSit8 calendar_PSit9  
     255}}} 
     256{{{#!sh 
     257$ qcg-client job_info 1305550554579_calendar_example_5366 
     258UserDN = /C=PL/O=GRID/O=PSNC/CN=Tomasz Piontek 
     259ProxyLifetime = 0 Days 11 Hours 58 Minutes 6 Seconds 
     260 
     261UserDN: /C=PL/O=GRID/O=PSNC/CN=Tomasz Piontek 
     262Project:  
     263Status: FINISHED 
     264StatusDesc:  
     265SubmissionTime: Mon May 16 14:55:54 CEST 2011 
     266FinishTime: Mon May 16 14:56:42 CEST 2011 
     267Number of tasks: 10 
     268Tasks: calendar_PSit0 calendar_PSit1 calendar_PSit2 calendar_PSit3 calendar_PSit4 calendar_PSit5 calendar_PSit6 calendar_PSit7 calendar_PSit8 calendar_PSit9  
     269DescriptionType: GRMS 
     270UserDescription:  
     271<qcgJob appId="calendar_example"> 
     272  <task persistent="true" taskId="calendar"> 
     273    <execution type="single"> 
     274      <executable> 
     275        <execFile> 
     276          <file> 
     277            <location type="URL">file:////usr/bin/cal</location> 
     278          </file> 
     279        </execFile> 
     280      </executable> 
     281      <arguments> 
     282        <value>${PS_month}</value> 
     283        <value>2010</value> 
     284      </arguments> 
     285      <stdout> 
     286        <file> 
     287          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     288        </file> 
     289      </stdout> 
     290    </execution> 
     291    <parametersSweep> 
     292      <parameter> 
     293        <name>month</name> 
     294        <value> 
     295          <loop> 
     296            <start>1</start> 
     297            <end>12</end> 
     298            <step>1</step> 
     299            <except> 
     300              <value>3</value> 
     301              <value>6</value> 
     302            </except> 
     303          </loop> 
     304        </value> 
     305      </parameter> 
     306    </parametersSweep> 
     307  </task> 
     308</qcgJob> 
     309 
     310QCGDescription:  
     311<grmsJob appId="calendar_example"> 
     312  <task persistent="true" taskId="calendar_PSit0"> 
     313    <execution type="single"> 
     314      <executable> 
     315        <execFile> 
     316          <file> 
     317            <location type="URL">file:////usr/bin/cal</location> 
     318          </file> 
     319        </execFile> 
     320      </executable> 
     321      <arguments> 
     322        <value>1.0</value> 
     323        <value>2010</value> 
     324      </arguments> 
     325      <stdout> 
     326        <file> 
     327          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     328        </file> 
     329      </stdout> 
     330    </execution> 
     331  </task> 
     332  <task persistent="true" taskId="calendar_PSit1"> 
     333    <execution type="single"> 
     334      <executable> 
     335        <execFile> 
     336          <file> 
     337            <location type="URL">file:////usr/bin/cal</location> 
     338          </file> 
     339        </execFile> 
     340      </executable> 
     341      <arguments> 
     342        <value>2.0</value> 
     343        <value>2010</value> 
     344      </arguments> 
     345      <stdout> 
     346        <file> 
     347          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     348        </file> 
     349      </stdout> 
     350    </execution> 
     351  </task> 
     352  <task persistent="true" taskId="calendar_PSit2"> 
     353    <execution type="single"> 
     354      <executable> 
     355        <execFile> 
     356          <file> 
     357            <location type="URL">file:////usr/bin/cal</location> 
     358          </file> 
     359        </execFile> 
     360      </executable> 
     361      <arguments> 
     362        <value>4.0</value> 
     363        <value>2010</value> 
     364      </arguments> 
     365      <stdout> 
     366        <file> 
     367          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     368        </file> 
     369      </stdout> 
     370    </execution> 
     371  </task> 
     372  <task persistent="true" taskId="calendar_PSit3"> 
     373    <execution type="single"> 
     374      <executable> 
     375        <execFile> 
     376          <file> 
     377            <location type="URL">file:////usr/bin/cal</location> 
     378          </file> 
     379        </execFile> 
     380      </executable> 
     381      <arguments> 
     382        <value>5.0</value> 
     383        <value>2010</value> 
     384      </arguments> 
     385      <stdout> 
     386        <file> 
     387          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     388        </file> 
     389      </stdout> 
     390    </execution> 
     391  </task> 
     392  <task persistent="true" taskId="calendar_PSit4"> 
     393    <execution type="single"> 
     394      <executable> 
     395        <execFile> 
     396          <file> 
     397            <location type="URL">file:////usr/bin/cal</location> 
     398          </file> 
     399        </execFile> 
     400      </executable> 
     401      <arguments> 
     402        <value>7.0</value> 
     403        <value>2010</value> 
     404      </arguments> 
     405      <stdout> 
     406        <file> 
     407          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     408        </file> 
     409      </stdout> 
     410    </execution> 
     411  </task> 
     412  <task persistent="true" taskId="calendar_PSit5"> 
     413    <execution type="single"> 
     414      <executable> 
     415        <execFile> 
     416          <file> 
     417            <location type="URL">file:////usr/bin/cal</location> 
     418          </file> 
     419        </execFile> 
     420      </executable> 
     421      <arguments> 
     422        <value>8.0</value> 
     423        <value>2010</value> 
     424      </arguments> 
     425      <stdout> 
     426        <file> 
     427          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     428        </file> 
     429      </stdout> 
     430    </execution> 
     431  </task> 
     432  <task persistent="true" taskId="calendar_PSit6"> 
     433    <execution type="single"> 
     434      <executable> 
     435        <execFile> 
     436          <file> 
     437            <location type="URL">file:////usr/bin/cal</location> 
     438          </file> 
     439        </execFile> 
     440      </executable> 
     441      <arguments> 
     442        <value>9.0</value> 
     443        <value>2010</value> 
     444      </arguments> 
     445      <stdout> 
     446        <file> 
     447          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     448        </file> 
     449      </stdout> 
     450    </execution> 
     451  </task> 
     452  <task persistent="true" taskId="calendar_PSit7"> 
     453    <execution type="single"> 
     454      <executable> 
     455        <execFile> 
     456          <file> 
     457            <location type="URL">file:////usr/bin/cal</location> 
     458          </file> 
     459        </execFile> 
     460      </executable> 
     461      <arguments> 
     462        <value>10.0</value> 
     463        <value>2010</value> 
     464      </arguments> 
     465      <stdout> 
     466        <file> 
     467          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     468        </file> 
     469      </stdout> 
     470    </execution> 
     471  </task> 
     472  <task persistent="true" taskId="calendar_PSit8"> 
     473    <execution type="single"> 
     474      <executable> 
     475        <execFile> 
     476          <file> 
     477            <location type="URL">file:////usr/bin/cal</location> 
     478          </file> 
     479        </execFile> 
     480      </executable> 
     481      <arguments> 
     482        <value>11.0</value> 
     483        <value>2010</value> 
     484      </arguments> 
     485      <stdout> 
     486        <file> 
     487          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     488        </file> 
     489      </stdout> 
     490    </execution> 
     491  </task> 
     492  <task persistent="true" taskId="calendar_PSit9"> 
     493    <execution type="single"> 
     494      <executable> 
     495        <execFile> 
     496          <file> 
     497            <location type="URL">file:////usr/bin/cal</location> 
     498          </file> 
     499        </execFile> 
     500      </executable> 
     501      <arguments> 
     502        <value>12.0</value> 
     503        <value>2010</value> 
     504      </arguments> 
     505      <stdout> 
     506        <file> 
     507          <location type="URL">${TASK_DIR}/stdout.txt</location> 
     508        </file> 
     509      </stdout> 
     510    </execution> 
     511  </task> 
     512</qcgJob> 
     513}}} 
     514}}} 
     515 
     516=== tasks_statuses === 
     517* `tasks_statuses <jobId>` - lists tasks constituting the given job with their statuses. 
     518{{{ 
     519#!div style="font-size: 90%" 
     520{{{#!sh 
     521qcg-broker tasks_statuses 1305550554579_calendar_example_5366 
     522UserDN = /C=PL/O=GRID/O=PSNC/CN=Tomasz Piontek 
     523ProxyLifetime = 0 Days 11 Hours 41 Minutes 30 Seconds 
     524 
     525Number of tasks: 10 
     526Tasks statuses:  
     527calendar_PSit7  : FINISHED 
     528calendar_PSit6  : FINISHED 
     529calendar_PSit5  : FINISHED 
     530calendar_PSit4  : FINISHED 
     531calendar_PSit3  : FINISHED 
     532calendar_PSit2  : FINISHED 
     533calendar_PSit1  : FINISHED 
     534calendar_PSit0  : FINISHED 
     535calendar_PSit9  : FINISHED 
     536calendar_PSit8  : FINISHED 
     537------ SUMMARY -------- 
     538Number of tasks: 10 
     539FINISHED        : 10 
     540}}} 
     541}}} 
     542 
     543=== task_info === 
     544* `task_info <jobId> <taskId>` - displays information about the given job 
     545{{{ 
     546#!div style="font-size: 90%" 
     547{{{#!sh 
     548qcg-broker task_info 1305550554579_calendar_example_5366 calendar_PSit0 
     549UserDN = /C=PL/O=GRID/O=PSNC/CN=Tomasz Piontek 
     550ProxyLifetime = 0 Days 11 Hours 40 Minutes 11 Seconds 
     551 
     552TaskType: SINGLE 
     553SubmissionTime: Mon May 16 14:55:57 CEST 2011 
     554FinishTime: Mon May 16 14:56:27 CEST 2011 
     555ProxyLifetime: PT0S 
     556Status: FINISHED 
     557StatusDesc:  
     558StartTime: Mon May 16 14:56:04 CEST 2011 
     559DescriptionType: <task persistent="true" taskId="calendar_PSit0"> 
     560  <execution type="single"> 
     561    <executable> 
     562      <execFile> 
     563        <file> 
     564          <location type="URL">file:////usr/bin/cal</location> 
     565        </file> 
     566      </execFile> 
     567    </executable> 
     568    <arguments> 
     569      <value>1.0</value> 
     570      <value>2010</value> 
     571    </arguments> 
     572    <stdout> 
     573      <file> 
     574        <location type="URL">${TASK_DIR}/stdout.txt</location> 
     575      </file> 
     576    </stdout> 
     577  </execution> 
     578</task> 
     579 
     580 
     581Coallocation:  
     582UserDN: /C=PL/O=GRID/O=PSNC/CN=Tomasz Piontek 
     583HostName: grass1.man.poznan.pl 
     584ProcessesCount: 1 
     585ProcessesGroupId:  
     586Status: FINISHED 
     587StatusDescription:  
     588SubmissionTime: Mon May 16 14:56:04 CEST 2011 
     589FinishTime: Mon May 16 14:56:21 CEST 2011 
     590LocalSubmissionTime: Mon May 16 14:56:06 CEST 2011 
     591LocalStartTime: Mon May 16 14:56:10 CEST 2011 
     592LocalFinishTime: Mon May 16 14:56:10 CEST 2011 
     593}}} 
     594}}}