June 2006 - jsdl-wg - lists.ogf.org

JSDL Teleconference - 21 June 2006
by Andreas Savva 19 Jun '06

19 Jun '06

Date: 21 June 2006 Time: 3pm BST / 10am EDT / 7 am PDT / 11pm JST Duration: 1 hour Dial-in numbers (toll): US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 207 3655269 (London) Japan: +81 3 3570 8225 (Tokyo) [Send me an email if you planning to call in from a location not listed above. I may be able to give you a local access number.] Participant PIN: 4371991 [Steve will send out a rough agenda] -- Andreas Savva Fujitsu Laboratories Ltd

4 4

Notes from GGF17
by A S McGough 16 Jun '06

16 Jun '06

All, As requested here are my notes (in slide form) from GGF17. In the first session we had a number of presentations of the different groups approaches to parallel job types. In the second session we started to define a JSDL job type extension. We decided to call this SPMDApplication thus allowing us to define other parallel job types in the future. steve.. -- ------------------------------------------------------------------------ Dr A. Stephen McGough http://www.doc.ic.ac.uk/~asm ------------------------------------------------------------------------ Technical Coordinator, London e-Science Centre, Imperial College London, Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK tel: +44 (0)207-594-8409 fax: +44 (0)207-581-8024 ------------------------------------------------------------------------

2 1

Re: [ogsa-bes-wg] Re: [jsdl-wg] Questions and potential changes to JSDL, as seen from HPC Profile point-of-view
by Michel Drescher 15 Jun '06

15 Jun '06

Hi Andre, Andre Merzky wrote: > Hi, > > Quoting [Donal K. Fellows] (Jun 12 2006): >> Marvin Theimer wrote: >>> If we narrow the definitions of mountpoint and mountsource enough and >>> precisely describe their semantics then we might arrive at something >>> that could be fairly widely used. I???m thinking of things like saying >>> that you can???t navigate ???out??? of a file system via ???cd ..???, etc. >>> This is definitely something to explore. >> Change "can't" to "shouldn't" and I'd agree. I don't regard the mount >> stuff as being a way of describing security enforcement points. Systems >> can do it that way, but at least some won't. >> >> In fact, I'd be happy enough with the profile stating that paths in JSDL >> documents should not contain either the "." or the ".." elements at all. >> That's a fairly strong requirement and guarantees that the job won't >> fail on systems where your style of semantics are enforced. > > > The GFS group (naturally) did some analysis on file systems, > directory navigation etc, and on related issues in Grids. > It might be useful input, and prevent you from re-doing that > job. > > You might want to browse their meeting material section on > forge > (https://forge.gridforum.org/sf/docman/do/listDocuments/projects.gfs-wg/docm…) for some overview material. [This link is broken - seem to be a link from the old gridforge!] Good point. OTOH, it's not only GFS that is or should be involved. In fact, I see the following group's involvement: - GFS - WS-Naming - JSDL - DMI - HPC - GSM I would like to know if there are enough resources available to get all these groups together in an inter-group F2F to wrangle this issue? Cheers, Michel -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834

2 1

Rough minutes from today's meeting
by A S McGough 14 Jun '06

14 Jun '06

All, Please find attached the rough minutes from today's meeting. steve.. -- ------------------------------------------------------------------------ Dr A. Stephen McGough http://www.doc.ic.ac.uk/~asm ------------------------------------------------------------------------ Technical Coordinator, London e-Science Centre, Imperial College London, Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK tel: +44 (0)207-594-8409 fax: +44 (0)207-581-8024 ------------------------------------------------------------------------

1 0

[Fwd: [members] OASIS TC Call for Participation: OASIS UnitsML TC]
by Andreas Savva 14 Jun '06

14 Jun '06

FYI. This might be of interest to anyone who felt sad when we removed the definition for the definitions for Units from version 0.9 (or so) of the JSDL. (Donal, does the Usage Record schema still include units definitions?) -- Andreas Savva Fujitsu Laboratories Ltd

2 3

JSDL Meeting
by A S McGough 12 Jun '06

12 Jun '06

All, Prompted by the email from Marvin I'd like to kick start the JSDL meetings off again. Can I propose next Wednesday (14 June 2006)? We were meeting at 3-4pm (London UK time). Andreas - could you set up the call? Rough agenda so far: 1) ParallelApplication extension 2) Profiles for different use cases (HPC etc) Let me know if people have other items for the agenda, steve.. -- ------------------------------------------------------------------------ Dr A. Stephen McGough http://www.doc.ic.ac.uk/~asm ------------------------------------------------------------------------ Technical Coordinator, London e-Science Centre, Imperial College London, Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK tel: +44 (0)207-594-8409 fax: +44 (0)207-581-8024 ------------------------------------------------------------------------

3 2

Re: [ogsa-bes-wg] Questions and potential changes to BES, as seen from HPC Profile point-of-view
by Donal K. Fellows 08 Jun '06

08 Jun '06

Marvin Theimer wrote: > Currently the posix extension to jsdl includes various things that I > would argue are more generic than posix. I think it would be > interesting to define a common subset (that includes things execution > pathname, command-line args, and working directory) as well as defining > a WindowsApplicationType that describes those things that are > Windows-specific. I believe[*] it is possible to define a new element type that describes an abstract ExecutableApplication element with these generic bits in and which is grandfathered into being a supertype of the POSIXApplication element (as well as being the parent of the WindowsApplication you're positing). This would require a small change to the existing schema, though we'd want to make sure that the documents accepted by the schema remained the same, and would enable this suggestion (which I approve of, by the way) to be slotted into the larger scheme of things without fuss. By the way, what would these extra Windows-specific bits be? I can imagine a number of the POSIX things being dropped (e.g. the limits) but I'm not nearly well-versed enough on Win (despite using it a lot) to be able to think what these extra additions might be. Just out of curiosity! :-) Donal. [* This is believe as in "I've done this sort of thing in other schemas" so I know that XML Schema can support it. ]

2 1

[Fwd: OASIS SDD TC Formal requirements]
by Hiro Kishimoto 01 Jun '06

01 Jun '06

Hi all, OASIS SDD TC asks me to forward this mail to JSDL mailing list. Although SDD requirement document is publicaly available, the URL in the original email requires OASIS membership. Please use the other URL which does not need membership below; http://www.oasis-open.org/committees/download.php/17575/oasis-sdd-requireme… Also, the following notes and minutes give you more information on this collaboration dialogue; http://www-unix.gridforum.org/mail_archive/ogsa-wg/2006/05/msg00053.html https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20060518 If you have any farther questions, please let me know. ---- Hiro Kishimoto -------- Original Message -------- Subject: [sdd] OASIS SDD TC Formal requirements Date: Wed, 31 May 2006 15:39:47 -0400 From: Thomas Studwell <studwell(a)us.ibm.com> To: jsdl-wg(a)gridforum.org CC: sdd(a)lists.oasis-open.org Dear JSDL WG members, attached you will find a link to a document that has been approved by the OASIS Solution Deployment Descriptor Technical Committee as the formal requirements for the SDD specification. This document is a result of compilation of over 200 use cases brought by TC members including representatives from some GGF workgroups. At the time we evaluated these use cases we were unaware of the potential overlap with JSDL. Our set of use cases are pretty comprehensive but it is possible that we missed use cases that might relate to your use cases. We would appreciate establishing a liaison with your WG to make sure that we address any overlapping needs between our respective charters. In addition to these requirements, in our recent face to face meeting the SDD TC voted to work with representatives of the JSDL WG to try to converge JSDL's RRL with relevant portions of the SDD. I believe there is significant overlap in this area and it would be beneficial to collaborate on a single set of XML elements to express resource requirements. We would appreciate it if the JSDL WG could nominate a representative who can participate in the SDD TC. We understand that you are nearing approval of your V1.0 specification and any changes would most likely be reflected in later versions of the JSDL specification but we believe this convergence is important to industry acceptance of both specifications and look forward to working with your representatives on this matter. Link to SDD Requirements Document: http://www.oasis-open.org/apps/org/workgroup/sdd/document.php?document_id=1… Thomas Studwell, Chair, OASIS SDD TC Thomas W. Studwell Senior Technical Staff Member, Autonomic Computing Architecture IBM Software Group B140/Bldg 500 4205 S Miami Blvd, Durham, NC 27703 (919) 254-7574 Fax: (919) 254-7628 Mobile: (919) 619-1038 studwell(a)us.ibm.com "There is a word for complaining about a problem without proposing a solution - it's called whining." Ric Telford 2006 -- Hiro Kishimoto

1 1