Proposed Changes to Data Staging specification
Based on my (& others?) implementation experience of this draft at SC07 I would propose the following modifications: 1. Change the specification name from Data Staging to File Staging. [I know I keep raising this... but data has very specific meaning to some people and this spec does not cover it any form at the moment.] 2. No use of the FileSystemName element in JSDL 3. Scrap the StagingSchedule element in section 3.2 4. Remove the dependency of this specification on the Activity Credential specification by: a) Placing a Credential element (wrapping a WS-Security authentication token) within the JSDL DataStaging element if a specific credential is needed for that file operation b) Placing a Credential element (wrapping a WS-Security authentication token) within the JSDL JobDescription element if a specific credential (different from the one used to connect to the service) is required to execute that application on the resource. There are probably other tweaks... but these would be my immediate issues following on from the SC07 experience. Steven
Steven, I am in the process of making these modifications, but I had a few clarification questions. For #2, do we want to say that a compliant system must not support <FileSystemName> or do we just want to say that the File Staging Profile does not mandate support for this? For 4a, do we want to say that the contents of this <Credential> element is an <xsd:any> or a WS-Security Token? The former is more extensible, but that later may be sufficient for our purposes here. For 4b, does this belong in the File Staging Profile? Seems like something that should be added to the Basic Profile (or some other extension). Glenn -----Original Message----- From: ogsa-hpcp-wg-bounces@ogf.org [mailto:ogsa-hpcp-wg-bounces@ogf.org] On Behalf Of Steven Newhouse Sent: Wednesday, November 28, 2007 1:10 PM To: ogsa-hpcp-wg@ogf.org Subject: [ogsa-hpcp-wg] Proposed Changes to Data Staging specification Based on my (& others?) implementation experience of this draft at SC07 I would propose the following modifications: 1. Change the specification name from Data Staging to File Staging. [I know I keep raising this... but data has very specific meaning to some people and this spec does not cover it any form at the moment.] 2. No use of the FileSystemName element in JSDL 3. Scrap the StagingSchedule element in section 3.2 4. Remove the dependency of this specification on the Activity Credential specification by: a) Placing a Credential element (wrapping a WS-Security authentication token) within the JSDL DataStaging element if a specific credential is needed for that file operation b) Placing a Credential element (wrapping a WS-Security authentication token) within the JSDL JobDescription element if a specific credential (different from the one used to connect to the service) is required to execute that application on the resource. There are probably other tweaks... but these would be my immediate issues following on from the SC07 experience. Steven -- ogsa-hpcp-wg mailing list ogsa-hpcp-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg
On 29/11/07 09:30, "Glenn Wasson" <wasson@virginia.edu> wrote:
I am in the process of making these modifications, but I had a few clarification questions.
For #2, do we want to say that a compliant system must not support <FileSystemName> or do we just want to say that the File Staging Profile does not mandate support for this?
I vote for the latter.
For 4a, do we want to say that the contents of this <Credential> element is an <xsd:any> or a WS-Security Token? The former is more extensible, but that later may be sufficient for our purposes here.
Since this is a profile (and not a specification that might need to evolve), I think it's better to describe the credential type. We all support WS-Security anyway, so I think we'd get more in the way of interop by mandating the credential "type". My opinion.
For 4b, does this belong in the File Staging Profile? Seems like something that should be added to the Basic Profile (or some other extension).
What I worry about is that we describe a generic credential (which is, in a sense already done in WS-Security) but we don't describe how to apply it to the different JSDL sections. It's fairly easy to understand what it means to use a credential in the context of a file staging operation, but what does it mean to attach the credential to the Application element, or in the JobIdentification element. Maybe we should go ahead and describe the usage of WS-Security tokens in the DataStaging elements, and then discuss more use cases for other JSDL sections. -- Chris
participants (3)
-
Christopher Smith -
Glenn Wasson -
Steven Newhouse