This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf5496?nav=1 at Fri, 04 Nov 2022 19:01:22 GMT SourceForge : artf5496: Meaning of DataStaging with no Source or Target

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin

JSDL calendar
Search Tracker
Project: JSDL-WG     Trackers > [CLOSED] JSDL v1.0 Errata > View Artifact
Artifact artf5496 : Meaning of DataStaging with no Source or Target
Tracker: [CLOSED] JSDL v1.0 Errata
Title: Meaning of DataStaging with no Source or Target
Description:
Hello,

I'm writing a JSDL->classad-based JDL converter, and I have a question related to the interpretation of the jsdl:
DataStaging element.
According to the definition, the jsdl:DataStaging element may have two child elements (both of which are optional) jsdl:
Source and jsdl:Target. As I understand:

- if only the jsdl:Source child is given, the DataStaging element refers to a request to copy files TO the execution 
node;
- if only the jsdl:Target child is given, the DataStaging element refers to a request to copy files FROM the execution 
node, upon job termination;
- if both jsdl:Source AND jsdl:Target children are given, then the previous two cases are combined (first the file is 
staged in, and upon job termination is staged out).

Now, I do not fully understand the meaning of having a DataStaging element without jsdl:Source nor jsdl:Target. How 
should we interpret this situation?

Thanks in advance,

Moreno. 
Submitted By: Andreas Savva
Submitted On: 06/30/2006 2:00 AM EDT
Last Modified: 04/04/2007 10:51 AM EDT
Closed: 04/04/2007 10:51 AM EDT

Status / Comments Change Log Associations Attachments  
Status  
Group: *
Status:* Closed
Category: *
Customer: *
Priority: * 4
Assigned To: * Donal Fellows
Reported in Release: *
Fixed in Release: *
Estimated Hours: * 0
Actual Hours: * 0
Comments
Andreas Savva: 04/04/2007 10:51 AM EDT
  Comment:
Verified draft3
  Action: Update
Closed set to 04/04/2007
Status changed from Fixed to Closed
Donal Fellows: 04/04/2007 6:34 AM EDT
  Comment:
Just a note that it is also possible to describe things using this mechanism that are essentially useless (e.g. a file that is not staged in, staged 
out, or given special deletion treatment on termination). Consumers might choose to complain (e.g. throw a fault) in that situation, or they might 
decide to just ignore the file (no-ops are easy).
  Action: Update
Andreas Savva: 04/04/2007 6:25 AM EDT
  Comment:
Added to 6.5.1.1 Data Staging

A DataStaging element typically contains either a Source or a Target element, or both. It is possi-ble, however, that neither a Source nor a Target 
element is present. In this case no stage in or stage out occurs. The DeleteOnTermination element can still be used to cleanup files as de-scribed in 
this section.
  Action: Update
Status changed from Resolved to Fixed
Andreas Savva: 09/13/2006 2:05 PM EDT
  Comment:
Add clarification
  Action: Update
Assigned To set to Donal Fellows
Status changed from Open to Resolved
Andreas Savva: 06/30/2006 2:01 AM EDT
  Comment:
Since there is no specific statement about this in the specification you
should interpret it using the existing rules.
- There is no jsdl:Source so you don't stage in
- There is no jsdl:Target so you don't stage out
- If jsdl:DeleteOnTermination exists then use it, otherwise do nothing

This actually allows for the fringe (from our perspective) case of just
 cleaning up a file from a host.

Thanks, good question. We should probably add explanation in a future
version of the spec.
  Action: Update
Andreas Savva: 06/30/2006 2:00 AM EDT
  Action: Create


 
 
 
< Previous
 
 
Next >
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf5496?nav=1 at Fri, 04 Nov 2022 19:01:27 GMT