SourceForge : Post

Project: Editor Discussion > REC: JSDL Spec v1.0 > tracking number > List of Posts

Forum Topic - tracking number: (2 Items)

View: as

07/25/2005 12:09 AM

post4663

tracking number

I have one comment, which is more of a soapbox than a nitpick. It is my belief that a "tracking number" associated with 
a job would help with with keeping track of (reporting, correlating, etc.) job failures. By "tracking number" I mean a 
globally unique identifier like a UUID. JobName allows such a value, but also explicitly allows its value to be shared 
across multiple documents. This is great, but I feel that not having a slot reserved for a unique identifier is a missed
 opportunity to unambiguously capture information that would be very useful for Grid monitoring.

Andreas Savva

07/25/2005 12:49 AM

post4664

Re: tracking number

I agree that a unique identifier associated with a *job instance* is important. JSDL 1.0, however, is scoped to defining
 a job template; a document that does not have job instance specific information. And that's the main reason that the 
group has not defined such an identifier.

Having said the above there are a number of ways to embed a unique identifier: 
1. In JobName (though this is misusing the field as you note)
2. In JobAnnotation
3. As an extensibility element in JobIdentification
  (This is actually one of the examples we show in the JSDL Introduction presentation. Such an element could be defined 
as a standard extension to JSDL 1.0; to be produced by the JSDL-WG or related group in the near future.)
4. In a separately defined job instance document that encapsulates a JSDL  1.0 template document.

At this point the BES-WG seems to be tackling issues related to job instances. Perhaps work from that group could be the
 base for an appropriate extension to JSDL 1.0 to address this point.

Return