Hi, I've done a revision of the DataStaging section (attached) and added some simple examples. (The changes are relative to 0.6.) If this is the sort of thing we are after I'll ask Darren to merge it in. This revision relates to the following actions from last week's minutes:
1) Place an example in the Spec for directory delimiting CF: From point 2 in last weeks minutes (Andreas)
2. How would you suggest to specify a logical file name: using predefined syntax or using a special attribute in the FileName element? Can a whole directory be specified as well? Group> You can specify either one. (Action Item) We need to show an example of that in the spec. Only '/' can be used as a delimiter for directories and files in the filepath.
and
2) More exaples for File staging - we have some of these on GridForge, they need to be merged in. (Andreas, Steve)
And I also made this change. We can discuss it again today (for the 3rd time) if necessary.
3) Add to spec that overwrite is a commonly used value for CreationFlag CF: From point 4 in last weeks minutes
-- Andreas Savva Fujitsu Laboratories Ltd
Hi All, First of all, thanks for answers to our doubts and for taking into acccount our comments. In the meantime, a few additional questions have arisen :-) First, it would be nice to know when do you plan to put an updated version of the schema to the webpage. Other, more specific questions are as follows: 1. We noticed that the timeUnits type is not used in the CPUTime element. Is it intended or this is an oversight? 2. The "minutes" unit is skipped in the timeUnits type. I know that it can be easily transformed from other units but this is rather a common unit and the only lacking one in this type. 3. What is the difference between job annotation and description in the job identification element? 4. What is the difference between cputime in the limits and resource elements? Does it define a limit that must be feasible at a given resource (e.g. by a queue configuration) in the resource element, and an actual limit set for a job in the limits element? Best regards & thanks, Ariel ----- Original Message ----- From: "Andreas Savva" <andreas.savva@jp.fujitsu.com> To: "JSDL WG" <jsdl-wg@gridforum.org> Sent: Tuesday, January 25, 2005 10:32 AM Subject: [jsdl-wg] DataStaging revision
Hi,
I've done a revision of the DataStaging section (attached) and added some simple examples. (The changes are relative to 0.6.) If this is the sort of thing we are after I'll ask Darren to merge it in.
This revision relates to the following actions from last week's minutes:
1) Place an example in the Spec for directory delimiting CF: From point 2 in last weeks minutes (Andreas)
2. How would you suggest to specify a logical file name: using predefined syntax or using a special attribute in the FileName element? Can a whole directory be specified as well? Group> You can specify either one. (Action Item) We need to show an example of that in the spec. Only '/' can be used as a delimiter for directories and files in the filepath.
and
2) More exaples for File staging - we have some of these on GridForge, they need to be merged in. (Andreas, Steve)
And I also made this change. We can discuss it again today (for the 3rd time) if necessary.
3) Add to spec that overwrite is a commonly used value for CreationFlag CF: From point 4 in last weeks minutes
-- Andreas Savva Fujitsu Laboratories Ltd
Ariel Oleksiak wrote:
First, it would be nice to know when do you plan to put an updated version of the schema to the webpage. Other, more specific questions are as follows: 1. We noticed that the timeUnits type is not used in the CPUTime element. Is it intended or this is an oversight? 2. The "minutes" unit is skipped in the timeUnits type. I know that it can be easily transformed from other units but this is rather a common unit and the only lacking one in this type.
These two issues appear to be oversights. Thanks for spotting them.
3. What is the difference between job annotation and description in the job identification element?
Description is intended for human consumption, annotation is intended for machine consumption. (I think this is right?) I suppose it is theoretically possible to merge the two (such as has been done in other standards, e.g. WSDL) but the human-readable description bits are much more widely applicable so we're not doing that (well, not right now).
4. What is the difference between cputime in the limits and resource elements? Does it define a limit that must be feasible at a given resource (e.g. by a queue configuration) in the resource element, and an actual limit set for a job in the limits element?
The resource defines how much processing time a job wants to reserve and need not be implemented with limits (e.g. could use a watchdog process instead) and the limit element specifies a POSIX (or semantically equivalent) soft limit on the job (i.e. the job gets a catchable signal when the limit is hit and can therefore in principle have some extra time after that to clean up for e.g. checkpoint-and-migrate). In other words, a job can exceed its limit for the purpose of finishing off neatly, but it cannot expect to exceed its resources in any meaningful way (or the cost for doing it might be prohibitive; that'd depend on the resource-provider site's policy). Does that make it clear? (And yes, I know that the current docs don't explain limits well enough; fixing this is on my to-do list. ;^) Donal.
participants (3)
-
Andreas Savva -
Ariel Oleksiak -
Donal K. Fellows