Hi;
As I’ve said from the beginning, I view data transfer as being
something that can and should be able to stand separately. So creating a
separate data profile certainly seems reasonable on first reflection. However,
I would argue that the HPC profile will need to reference/incorporate that
profile in some manner since and end-to-end vertical profile for HPC is
meaningless without a data component to it.
We should definitely discuss this issue in the BoF.
Marvin.
From: David Wallom
[mailto:david.wallom@ierc.ox.ac.uk]
Sent: Saturday, May 06, 2006 9:55
AM
To:
Subject: Re: [ogsa-wg] Initial
draft of HPC profile working group charter
Hi Marvin,
>From reading most of the correspondence on this topic and from various
conversations about this with various people I was wondering if we could
actually launch a separate Data profile since tacking this onto the end of the
HPC profile could possibly prove limiting. I was wondering if the data
discussion would be a specific part of the BOF?
Regards
David
On 5/5/06 16:15, "
Hi;
You are right that most of the discussion so far has been about job submission
and not about the related need to get data from client to execution
subsystem(s) and back again. But since the goal of the group is to define
a profile covering the end-to-end vertical use cases, I know that we will need
to tackle the topic of data staging at some point. As with JSDL and
BES’s relation to the job submission parts of the work, I’m hoping
we will be able to substantially leverage other existing work, such as that of
the data DMIS groups, as appropriate. I’ll make that more explicit
in the next revision of the draft charter.
Thanks for pointing this matter out,
Marvin.
From: Dave Berry [mailto:daveb@nesc.ac.uk]
Sent: Friday, May 05, 2006 7:14 AM
To:
Subject: RE: [ogsa-wg] Initial
draft of HPC profile working group charter
Hi,
All the discussion I've seen about this profile so far has
focussed on specifying and submitting jobs, but the proposed charter says that
this is only one of two areas of interest; the other being data staging.
The immediate question is what link will this profile work have to the
Data Movement Interface Specification group? Will the profile refer to
the DMIS spec in the same way that it will refer to JSDL and BES? (Of
course, JSDL also covers data staging to some extent).
Work is also continuing on the data aspects of the OGSA
architecture, in the OGSA Data WG. I would encourage the HPC profile
group to engage with the OGSA Data group and the DMIS group concerning how to
fit data staging into the overall architecture.
Unfortunately I won't be in
Best wishes,
Dave.