[jsdl-wg] Re: [ogsa-hpcp-wg] Minutes for OGSA HPC Profile telecon (Aug 18 2006)

[Andreas Savva]

I've had a look through the document; here are some comments:

1. This definition is based on that of the POSIXApplication with the
main change being the removal of the filesystem attribute and most of
the limits. Could you add a section summarizing these changes, or
highlight them in each element definition? I think this is very
important given that the element names used are the same (even if in a
different namespace). It may help to reduce confusion.

2. Executable is defined as a mandatory element in the same way as in
the JSDL PosixApplication. Given the discussions we've had in the
context of the EMS Scenarios this should probably be optional (0-1)
since the location may not be known until deployment is finished. (This
isn't an issue for the HPC profile.)

3. Donal changed the Argument type from normalizedstring to string. If I
 recall correctly there was a very long and heated discussion around
this in the past (but, happily perhaps, I can't recall details). Could
someone who was involved in the definition of this element followup?

4. Working directory - In contrast to Donal's comment I think if this is
not present it should not be created.

Btw, I am really curious here, how is a user going to specify that they
want a job to run in their home directory, wherever that place may be?
Surely the exact location may differ from machine to machine.

5. Why was GroupName dropped?

6. Consider introducing a sub-section for "Security considerations" in
each element definition. I think this makes more sense than mixing such
information in the functional definition. It also makes more sense for
this kind of spec than trying to list everything in a single Security
considerations section at the back. (I'm also thinking of doing
something like this in the errata release of 1.0).

(Not sure if I can make the HPCP call tonight, but I might turn up for
the first few minutes.)
Andreas

Donal K. Fellows wrote:
> humphrey at cs.virginia.edu wrote:
>> OGSA HPC Profile Minutes – Fri Aug 18 2006
> [...]
>>         AI-HPCP-0818a: Donal Fellow to review HPC Profile Application.
>> Specifically to ensure that normative text use is correct. Also, adding
>> normative text. Hopefully done before the next JSDL call on Wed.
> 
> As promised, I've reviewed the HPC Profile Application extension
> document and applied a few changes (though fewer than I originally
> thought). I've uploaded a change-tracked version to GridForge (in the
> JSDL documentation tree) which has my changes in it together with
> comments detailing a few issues that I think could do with addressing
> before it goes final. (Some comments just describe reasoning behind one
> or two of the changes I've made though.)
> 
> https://forge.gridforum.org/sf/docman/do/viewDocument/projects.jsdl-wg/docman.root.working_drafts/doc13749
> 
> 
> The main thing of note I suppose is that I've beefed up the Security
> Considerations to state that it is important that the UserName element
> not be allowed to do end-runs around security. But that needs checking
> by someone else to ensure that I've not gone too far and required that
> implementations *have* a security context that could allow deduction of
> what username to use. That's just the sane thing to do... :-)
> 
> Cc:ing the JSDL WG so that they can get a chance to review the doc (plus
> my comments) too.
> 
> Donal.
> 

-- 
Andreas Savva
Fujitsu Laboratories Ltd