December 2004 - jsdl-wg - lists.ogf.org

Latest XSD now on GridForge
by A Stephen McGough 07 Dec '04

07 Dec '04

All, I've updated the JSDL XSD document on GridForge. It should now have all the corrections from the last few telecons and email discussions. steve.. -- ------------------------------------------------------------------------ Dr A. Stephen McGough ------------------------------------------------------------------------ Research Associate, Imperial College London, Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK tel: +44 (0)207-594-8310 fax: +44 (0)207-581-8024 ------------------------------------------------------------------------ Assistant Warden, West Wing, Beit Hall, Imperial College, Prince Consort Road, London, SW7 2BB tel: +44 (0)207-594-9910 ------------------------------------------------------------------------

1 0

Phone Call info
by Darren Pulsipher 07 Dec '04

07 Dec '04

December 6, 2004 Time: 1400 GMT, 0900 EST, 2300 Tokyo. You have been invited to a Microsoft Office Live Meeting. At the time of the meeting, click on the following link to attend: http://www.placeware.com/rm/cadence/attend?id=JSDL127&pw=745944 Meeting Title: JSDL Meeting Audio Information: x3000 Passcode 6447 If you cannot click the meeting link above, or it does not work, please do the following: Browse to: http://www.placeware.com/rm/cadence/attend Type your name Type the Meeting ID as: JSDL127 Type the Password as: 745944 _________________________ Dial In Numbers: Phone Numbers: Belgium - 0800-7053 Bezeq - 1-800-940-1786 France - 0800-903109 Germany - 0800-1815765 Hong Kong - 800-968932 Italy - 800874509 Japan - 00531123656 Korea-Tele - 00798-14-800-0512 Netherlands - 0800-0225447 Singapore - 800-1200766 Sweden - 020-7905043 Taiwan - 00801-13-8546 UK - 0800961294 US - 800-933-3594

1 0

JSDL Meeting: Presenter Invitation
by Darren Pulsipher 07 Dec '04

07 Dec '04

You have been invited to present at a Microsoft Office Live Meeting. Meeting Title: JSDL Meeting When: Tuesday, December 07, 2004 07:00 - 08:00 Audio Information: none At the time of the meeting, click on the following link to present: http://www.placeware.com/rm/cadence/present?id=JSDL127&pw=493324 If you cannot click the meeting link above, or it does not work, please do the following: Browse to: http://www.placeware.com/rm/cadence/present Type your name Type the Meeting ID as: JSDL127 Type the Password as: 493324

1 0

JSDL and Unicore
by Michel Drescher 02 Dec '04

02 Dec '04

Guys, together with Dave, I've been playing around a bit with the new JSDL schema and its mapping to UNICORE. Although the following jobs actually don't specify anything that could make sense, they illustrate three important use cases for resource allocation: - All three Use Cases allocate 16 processors. - Flavour a specifies them in a true parallel context - Flavour b does so in a simple SMP context Note also that the attached xml files endorse the general assumption that the specified job runs one thread per CPU. Comments, anybody? Cheers, Michel (and Dave) -- Michel Drescher Fujitsu Laboratories of Europe (FLE) Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE, U.K. +44-(0)20-8606-4834 (Office) +44-(0)20-8606-4539 (Fax)

1 0

RE: [jsdl-wg] Re: Matching JSDL Terms to Other Specs
by Andrea Westerinen 02 Dec '04

02 Dec '04

Donal, I think that your statement is both incorrect and unjustified. There is much value in CIM for both provisioning and runtime management. There is complexity there also - since the managed environment is quite complex. If you would care to expand further on what is wrong with CIM, I would be happy to address the issues with you. BTW, as regards the requirements of a Job, these can indeed be modeled/associated as instances of SoftwareResource in CIM V2.9. Just because the info is not in JSIM does not mean that it is not in CIM. Andrea > -----Original Message----- > From: owner-jsdl-wg(a)gridforum.org > [mailto:owner-jsdl-wg@gridforum.org] On Behalf Of Donal K. Fellows > Sent: Thursday, November 11, 2004 2:36 AM > To: Ali Anjomshoaa > Cc: JSDL WG > Subject: Re: [jsdl-wg] Re: Matching JSDL Terms to Other Specs > > Ali Anjomshoaa wrote: > > Thanks for looking at the intersection of the two though. A useful > > exercise I think. > > I think the key lesson is that we don't need to worry about > what's going on in CIM or JSIM; they address a completely > different stage of the job lifecycle (i.e. after submission) > to JSDL (which is a description of what the submitter wants > the job to do and what it needs in order to do it). This is > probably a good thing; I've heard many things about CIM and > "the roach motel of data integration" was among the more polite... :^) > > Donal. > >

3 4

Uploaded draft-ggf-jsdl-spec-0.6
by Andreas Savva 01 Dec '04

01 Dec '04

I uploaded v0.6 of the spec. https://forge.gridforum.org/projects/jsdl-wg/document/draft-ggf-jsdl-spec/en /11 or (shorter) http://tinyurl.com/3taa2/draft-ggf-jsdl-spec/en/11 I still have things to do but since I promised this revision by yesterday's call and I'm already late I thought to upload it. Could one of {Darren, Steve, Ali, Fred,...} get the pen from me and accept my changes please? (I still have the pen unless you mail me.) ---------------------- * SUMMARY OF REVISIONS - Accepted changes from F2F - Inserted normative schema in the appendix (the gridforge version) https://forge.gridforum.org/projects/jsdl-wg/document/jsdl.xsd/en/2 - Deleted jsdl:any and replaced with xsd:any##other - Also deleted jsdl:any section - Updated TOC (DON'T DO THIS WITH CHANGE TRACKING ON! You've been warned.) - Changed "jsdl attribute" to "jsdl element" consistently (please check) - Added notation usage text for attribute, element - Added namespace prefix explanation and table (check) - typos, formatting and other minor changes (uninteresting formatting changes may not show since I accepted many of them). In particular I formatted pseudo-schema entries as XML snippets. - Contributions and acknowlegments update - Name or type inconsistencies with the schema (where I noticed them) - Added missing 'operator' to CPUTime - FileName description revision to address Matt's comment. (emphasize that it FileName MUST be a relative path.) - Fixed some legacy examples (e.g., units) - Moved/merged things that appeared in two places or in the wrong place. In particular units and enumeration definitions. - Modified and added Figures in the text. (These are TIFF; the editable figures in separate files on gridforge.) - Changed ids to NCName in the document as well. - Removed spurious ids from the pseudo schema. - Added comments to keep some things that need resolution. - Started an "OUT OF SCOPE" sub-section - Added Security section * Things to do (incomplete) ** The minutes say: - Agreed to "Description" as a general element to be inherited by all elements. Work in the schema. But I think this is not in the schema yet. I wrote the general section but we probably also need to change some other sections. ** Need to review the normative statements (MUST, etc) ** We should change JobDescription to something else since "Description" is usually defined in the text as "descriptive information". ** Add 'DontOverwrite' to creation flag enumeration. I think it's needed since this the CreationFlag MUST appear. ** Need to revisit 'id uniqueness' text and make sure it is correct. (Which ones are allowed to occur multiple times in profiles? All except the Profile one?) ** Too many sub-sub-sub-sub-sections: - I collapsed the hierarchy in a couple of places but avoided the many problem. * Decide formatting of XML elements when used in text (my vote is for XML Snippet). Have a look at the DataStaging description. (One advantage is that spell checking doesn't apply to them then) * Non-normative text revision -- Andreas Savva Fujitsu Laboratories Ltd.

1 0