[ogsa-naming-wg] Re: [ogsa-wg] Re: [ogsa-bes-wg] Abstract names in BES
Frank Siebenlist
franks at mcs.anl.gov
Wed Nov 9 20:24:31 CST 2005
Hi Chris,
Could you expand a little on the scenario and use case?
Will the job id be the abstract name itself or embedded in it?
What kind of resolution is needed and when?
(jobId=>EPR?)
Could the jobId be embedded inside of the EPR's address?
Thanks, Frank.
Christopher Smith wrote:
> For a mapping of BES to LSF, I would put something like a job id in
> the abstract name, so that it could be used outside the web services
> world (say with a CLI). Sure, it could be put in the payload of
> messages, or retrieved via some explicit call, but it seems reasonable
> to use the abstract name for this.
>
> -- Chris
>
>
>
> On 9/11/05 17:28, "Ian Foster" <foster at mcs.anl.gov> wrote:
>
> I found the call today very helpful.
>
> One thing that I wanted to get clarification on is the requirement
> that motivates a desire for "abstract names" in BES.
>
> I've heard one, which is that some entity may be handed two or
> more references (EPRs) to jobs, and want to know which of these
> are (not) unique.
>
> Are there others?
>
> Regards -- Ian.
>
>
>
--
Frank Siebenlist franks at mcs.anl.gov
The Globus Alliance - Argonne National Laboratory
More information about the ogsa-naming-wg
mailing list