- ogsa-wg - lists.ogf.org

Updated: OGSA Teleconference
by Andreas Savva 23 Oct '06

23 Oct '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061023T220000Z DTEND:20061024T000000Z TRANSP:OPAQUE SEQUENCE:2 UID:040000008200E00074C5B7101A82E00800000000908183F164ECC6010000000000000000100 0000076824268C7E4DB45977CBD7092D2808F DTSTAMP:20061023T025306Z DESCRIPTION:When: 2006年10月24日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1023\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (if available)\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Nov. F2F update (20 min)\n\n3) HPC cluster usecase for EGA reference model (Paul and Hiro\, 60 min)\n In order to clarify relationship between OGSA architecture\n and EGA reference model\, design team is trying to write-up\n HPC cluster usecase for EGA reference model assuming that\n OGSA is SOA and Web-service based instantiation of EGA\n reference model.\n\n Hiro's draft slides:\n - https://forge.gridforum.org/sf/go/doc13939\n Meeting minutes from Oct. 9th:\n - https://forge.gridforum.org/sf/go/doc13942\n\n> AI-1009a: Review slide 6 again and clarify what the problem is\n> (Reference Model Design Team)\n> AI-1009b: Review the Reference Model 'Manage Job' in more\n> detail. Specifically look at it from the perspective of\n> an enterprise application (e.g.\, a 3-tier app) (Reference\n> Model Design Team)\n> AI-1009c: Hiro to ask Jay to provide his comments for Slide 6\n> - Perspective of submitter vs platform provider and the\n> hierarchical model connection\n\n Design team will bring revised slides to the call.\n\n4) Glossary discussion (Jem Treadwell\, 20 min)\n\nJem's email:\n> Per discussion on the October 9th meeting\, I've now posted a discussion\n> document for the Glossary. The primary objective is to converge the EGA\n> Reference Model glossary and the OGSA glossary\, and the target for\n> completion is OGF19.\n> \n> The discussion document is posted in the gridforge Glossary folder at\n> http://tinyurl.com/yzwt4c\, along with the current draft of the Glossary.\n> \n> I received some initial comments from Olegario Hernandez\, who has been a\n> regular contributer to each version of the OGSA Glossary. These\n> comments are posted in tracker 5617 - there's a link to the tracker in\n> the discussion document. \n> \n> I believe we had agreed that we would discuss the terms initially by\n> e-mail and with discussions as needed bi-weekly on the regular Monday\n> OGSA calls. I propose that we begin with a discussion on next Monday's\n> call\, as the last agenda item to minimize the pain :0) For anyone who\n> wants to get a head start\, I propose to look at "enterprise" and related\n> terms first (and\, from his comments\, I think Olegario would second that\n> proposal!). \n\n3) Wrap up\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nOct. 26 (Thu): EMS scenarios\, Security\nOct. 30 (Mon): DMTF work register\, OGSA roadmap\nNov. 2 (Thu): Information/data modeling\nNov. 6 (Mon): EGA reference model\, OGSA roadmap\nNov. 9 (Thu): F2F prep\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569\n\n > From Oct. 9 call.\n AI-1009a: Review slide 6 again and clarify what the problem is\n (Reference Model Design Team)\n AI-1009b: Review the Reference Model 'Manage Job' in more\n detail. Specifically look at it from the perspective of\n an enterprise application (e.g.\, a 3-tier app) (Reference\n Model Design Team)\n AI-1009c: Hiro to ask Jay to provide his comments for Slide 6\n - Perspective of submitter vs platform provider and the\n hierarchical model connection\n\n > From Oct. 5 call.\n AI-1005a: Alan Sill willing to take responsibility for pushing\n the process for getting a charter ready (by Oct. 26)\n AI-1005b: People to send Dave Snelling more information\, ideas\n for more security calls to complete coverage\n (Since this does not have any specific owners\, it will\n be closed Oct. 26)\n\n > From Sept. 28 call.\n AI-0928a: Takuya will issue a final call on BSP-Core on the list.\n\n > From Sept. 25 call.\n AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to\n contribute to join the OGSA list and this convergence work. -\n Members may have changed but organizations have not\n AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M)\n on why the current separation of service/info model may\n not be quite right.\n\n > From Sept. 21 call.\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security ADs (Blair Dillaway and David Groep) about the\n Security Area task list.\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil next EMS call (Oct. 26):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n</pre>\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Fwd: [IDM] New NIST Publication: An Ontology of Identity Credentials
by Alan Sill 21 Oct '06

21 Oct '06

Useful for the dictionary / glossary effort? Alan Begin forwarded message: > From: Ann West <awest(a)EDUCAUSE.EDU> > Date: October 20, 2006 8:27:12 AM CDT > To: IDM(a)LISTSERV.EDUCAUSE.EDU > Subject: Re: [IDM] New NIST Publication: An Ontology of Identity > Credentials > Reply-To: Identity Management Constituent Group Discussion > list <IDM(a)LISTSERV.EDUCAUSE.EDU> > > Ken, > > Yes, we do compare notes with the federal documents where relevant. > > For instance, in the Enterprise Authentication Implementation Roadmap, > the concepts and terms in some cases cite the OMB M-0404 > E-Authentication Guidance for Federal Agencies. However, we also wrote > some of our own definitions to either scope a broader term for use in > the Roadmap context or explain a concept more simply or clearly. > http://www.nmi-edit.org/roadmap/draft-authn-roadmap-03/1- > concepts.html. > > In short, glossary definitions will be similar, but not the same. > > Best, > Ann > > > >> -----Original Message----- >> From: Ken Brumbaugh [mailto:Ken.Brumbaugh@CSU.MNSCU.EDU] >> Sent: Wednesday, October 18, 2006 2:54 PM >> To: IDM(a)LISTSERV.EDUCAUSE.EDU >> Subject: Re: [IDM] New NIST Publication: An Ontology of Identity >> Credentials >> >> 10/18/06 >> >> Ann >> >> Will you, or any one, be doing a terminology/definitions check >> between >> glossaries that NMI-Edit has, and what NIST is now disseminating? >> >> If this has not been done, it might be beneficial to the group to >> have >> this done by one party - and shared with others. >> >> Using a common glossary could be most advantageous to many - >> particularly those of us, who are now starting this long IdM/IAM > journey >> with our clientele. >> >> Thanks. >> >> >> >> Ken Brumbaugh, Ph.D. >> System Director, Identity Management & Directory Services >> Minnesota State Colleges & Universities >> Office Phone - 651-201-1429 >> Cell Phone - 651-269-9988 >> >>>>> awest(a)EDUCAUSE.EDU 10/18/2006 12:36 PM >>> >> All, >> >> If you are reviewing your identifiers and credentials, consider >> reading >> the new NIST draft "An Ontology of Identity Credentials - Part 1: >> Background Formulation" released on October 6. >> >> http://csrc.nist.gov/publications/drafts/sp800-103-draft.pdf >> >> Best, >> Ann >> >> ------------- >> Ann West >> NMI-EDIT Outreach Lead, EDUCAUSE >> Program Manager, Middleware and Security, Internet2 >> Michigan Technological University Alan Sill TIGRE Senior Scientist High Performance Computing Center TTU ==================================================================== : Alan Sill, Texas Tech University Office: Admin 233, MS 4-1167 : : e-mail: Alan.Sill(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

4 3

Glossary discussion document posted
by Treadwell, Jem 19 Oct '06

19 Oct '06

Hi, Per discussion on the October 9th meeting, I've now posted a discussion document for the Glossary. The primary objective is to converge the EGA Reference Model glossary and the OGSA glossary, and the target for completion is OGF19. The discussion document is posted in the gridforge Glossary folder at http://tinyurl.com/yzwt4c, along with the current draft of the Glossary. I received some initial comments from Olegario Hernandez, who has been a regular contributer to each version of the OGSA Glossary. These comments are posted in tracker 5617 - there's a link to the tracker in the discussion document. I believe we had agreed that we would discuss the terms initially by e-mail and with discussions as needed bi-weekly on the regular Monday OGSA calls. I propose that we begin with a discussion on next Monday's call, as the last agenda item to minimize the pain :0) For anyone who wants to get a head start, I propose to look at "enterprise" and related terms first (and, from his comments, I think Olegario would second that proposal!). E-mail comments and suggestions are, of course, welcome. Thanks, - Jem ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell(a)hp.com <mailto:Jem.Treadwell@hp.com>

1 0

Editors call postponed to 25th.
by Christopher Jordan 18 Oct '06

18 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We had previously discussed having a Roadmap editor's call today. Due to scheduling conflicts, I'd like to postpone this call to the 25th of October. I'll send meeting details soon. Thanks. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "If we had a keen vision and feeling of all ordinary human life, it would be like hearing the grass grow and the squirrel's heart beat, and we should die of that roar which lies on the other side of silence." - George Eliot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFNnevPCVtcXn6kg8RAoy1AKDmAZtVYmurstZfLgb78WZHv9WqqQCdGI4G jIIklhp2/eiZNURVy8YVY8w= =xiYz -----END PGP SIGNATURE-----

1 0

Proposed agenda for Oct. 19th call
by Hiro Kishimoto 18 Oct '06

18 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 19th Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1019 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Oct. 16) - https://forge.gridforum.org/sf/go/doc13952 Action Items status review (see the bottom of this email) Agenda bashing 2) Nov. F2F update (Hiro Kishimoto, 10 min) 3) OGSA AuthN WG BoF draft (Alan Sill, 30 min) > - Alan Sill willing to take responsibility for pushing the process > for getting a charter ready > - AI-1005a: Alan Sill to have draft Charter ready before next > security telecon (Dave to help and only as stand in for new area > director). > - Do we need more covereage if we have an active authorization and > authentication working groups > -- No, we need more covereage > -- AI-1005b: People to send Dave Snelling more information, ideas for > more security calls to complete coverage 4) Security Profile Update (Takuya Mori, 30 min) > AI-0928a: Takuya will issue a final call on BSP-Core on the list. > - Need to check status of WS-I documents > - Secure Channel Profile on next telecon 5) Information/data modeling (Ellen Stokes, 30 min) > - Discussion on if a requirements XML document could be constructed > with powerful comparative expressions and at same time avoids the > XPath expressions/joins on collecting input documents? Perhaps just > the relevant subset of a query in job. - Agreed to discuss more in > second hour on Next Call - Oct 19th 6) Wrap up AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 23 (Mon): EGA reference model, OGSA roadmap Oct. 26 (Thu): Information/data modeling, EMS scenarios Oct. 30 (Mon): DMTF work register Nov. 2 (Thu): Security Nov. 6 (Mon): EGA reference model, OGSA roadmap Nov. 9 (Thu): F2F prep <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569 > From Oct. 16 call. AI-1009d: Jem Will post tomorrow, comments received and will put into tracker. AI-1005a: Charter form created, ready for review. Hiro will send links to charters. Paper work for new working group needed - can use security design team folder in OGSA temporarily. Feedback: Use next OGF to start WG rather than form a BOF. Hiro will bring proposal to GFSG, since needs security Area Director approval & GFSG. > From Oct. 8 call. AI-1009a: Review slide 6 again and clarify what the problem is (Reference Model Design Team) AI-1009b: Review the Reference Model 'Manage Job' in more detail. Specifically look at it from the perspective of an enterprise application (e.g., a 3-tier app) (Reference Model Design Team) AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 - Perspective of submitter vs platform provider and the hierarchical model connection AI-1009d: Jem will produce a topic discussion list for the converged glossary > From Oct. 5 call. AI-1005a: Alan Sill willing to take responsibility for pushing the process for getting a charter ready (by Oct. 19) AI-1005b: People to send Dave Snelling more information, ideas for more security calls to complete coverage (Since this does not have any specific owners, it will be closed Oct. 19) > From Sept. 28 call. AI-0928a: Takuya will issue a final call on BSP-Core on the list. > From Sept. 25 call. AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until next EMS call (Oct. 26): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. ---- Hiro Kishimoto

2 1

Draft charter for OGSA-AuthN WG
by Alan Sill 18 Oct '06

18 Oct '06

Discussion among participants and potential participants has indicated a desire to proceed directly to a launch of the OGSA-AuthN working group rather than proceed through a BOF. Most people who would participate or be affected have up to now been involved in related efforts and would be able to come up to speed fairly quickly in this effort. Here are the elements of a charter, or potential charter, for this group that I have identified: 1) Review existing security profiles resulting from previous efforts of the Security area and security design group from the OGSA-WG effort a) Compare them to existing technology and best practices in the community and check for consistency of coverage b) Document authentication profiles that may be missing or incomplete b) Review mature and maturing technologies likely to affect the above best practices for grid services 2) Provide an AuthN development roadmap to compare with the overall OGSA roadmap 3) Spawn any subgroups and/or suggest associated research groups that may be necessary for consistent development in this area. The charter can be developed from the above skeleton, and the basics agreed to before the first session at OGF-19 in North Carolina. It is explicitly a part of the charter for this group to work in a symmetrical manner with any OGSA-AuthZ work that may be needed for consistency in grid services. Comments welcome. Alan Alan Sill TIGRE Senior Scientist High Performance Computing Center TTU ==================================================================== : Alan Sill, Texas Tech University Office: Admin 233, MS 4-1167 : : e-mail: Alan.Sill(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

2 2

Proposed agenda for Oct. 16th call
by Hiro Kishimoto 16 Oct '06

16 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 16th Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: <1002> See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Oct. 2 & 9) - https://forge.gridforum.org/sf/go/doc13917 - https://forge.gridforum.org/sf/go/doc13942 Action Items status review (see the bottom of this email) Agenda bashing 2) Nov. F2F meeting update (Ellen Stokes and Fred Brisard, 20 min) Next interim F2F will be on Nov. 9 and 10 in Tampa, FL just before SC06. Review logistics, agenda, and attendees. - https://forge.gridforum.org/sf/go/wiki1620 3) New DMTF workregister review (Ellen Stokes and Tom Roney, 30 min) After GGF and EGA merge, OGF need to agree new workregister with DMTF sooner rather than later. Tom Roney, OGF liaison to DMTF, is working on new draft. - https://forge.gridforum.org/sf/go/doc13947 From Tom's email: > Please take a look with these notes in mind: > > - I added "Background" to the "Mission" heading > Our (GGF/EGA) mission statements have > been combined. Modify as you see fit. > I did remove references to "enterprise" > grids and "enterprise" grid computing, > referring now to (simply) grids and > grid computing. > > - Under the heading of "Alliance Scope" > Please take a look at the third paragraph > regarding the "Reference Model." Do we > leave this? I think so. > > - After Figure 2 > We should include a corresponding link between > the OGF's Semantic Grid Research Group and a > group within the DMTF. What would that group be, > and who would be the DMTF contact? > > - Under the "Milestones" heading > I have done little with this other than > to remove what has been accomplished wrt > the last register for the GGF. > > Do we still want the second bullet, regarding > mapping the work underway, etc.? I think this > is important, but we (I) did nothing to move it > forward, and it will take the effort of a good > many minds. > > Please add to and/or modify this list of goals. > > - Under the "Contacts" heading > I have updated the OGF side with respect > to the once-GGF contacts, noting that the > Security Area Directors are listed as > Olle Mulmo and Dane Skow. I do not know > if this is accurate, and do not see on the > OGF website where this can be found. Also, Ellen will bring OGSA-WG related update before the call. > AI-0915b: Ellen to check the status of the items on the > DMTF work register: report which have been done, and what > DMTF is doing for the rest. (by Oct. 13) > AI-0915c: Ellen to propose new text to update the DMTF register > (by Oct. 13) Obsolete GGF-DMTF workregister: - http://www.ogf.org/documents/liaison/GGF-DMTFWorkRegister.pdf Obsolete EGA-DMTF work resister - http://www.dmtf.org/about/register/EGA-DMTFWorkRegister.pdf 4) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 16 (Mon): DMTF Workregister Oct. 19 (Thu): Information/data modeling, Security, secure channel profile review Oct. 23 (Mon): EGA reference model, OGSA roadmap Oct. 26 (Thu): Information/data modeling, EMS scenarios Oct. 30 (Mon): <TBD> Nov. 2 (Thu): Security Nov. 6 (Mon): EGA reference model, OGSA roadmap Nov. 9 (Thu): F2F prep <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Oct. 8 call. AI-1009a: Review slide 6 again and clarify what the problem is (Reference Model Design Team) AI-1009b: Review the Reference Model 'Manage Job' in more detail. Specifically look at it from the perspective of an enterprise application (e.g., a 3-tier app) (Reference Model Design Team) AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 - Perspective of submitter vs platform provider and the hierarchical model connection AI-1009d: Jem will produce a topic discussion list for the converged glossary > From Oct. 5 call. AI-1005a: Alan Sill willing to take responsibility for pushing the process for getting a charter ready (by Oct. 19) AI-1005b: People to send Dave Snelling more information, ideas for more security calls to complete coverage (Since this does not have any specific owners, it will be closed Oct. 19) > From Sept. 28 call. AI-0928a: Takuya will issue a final call on BSP-Core on the list. > From Sept. 25 call. AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until Oct. 13 call: AI-0915b: Ellen to check the status of the items on the DMTF work register: report which have been done, and what DMTF is doing for the rest. AI-0915c: Ellen to propose new text to update the DMTF register Until next EMS call (Oct. 26): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. ---- Hiro Kishimoto

2 1

Updated: OGSA Teleconference
by Andreas Savva 16 Oct '06

16 Oct '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061016T220000Z DTEND:20061017T000000Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E008000000008088EFBB64ECC6010000000000000000100 0000040E2FFAC2911984D9CA8E87DBC436C4A DTSTAMP:20061016T094843Z DESCRIPTION:When: 2006年10月17日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: <1002>\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Oct. 2 & 9)\n - https://forge.gridforum.org/sf/go/doc13917\n - https://forge.gridforum.org/sf/go/doc13942\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Nov. F2F meeting update (Ellen Stokes and Fred Brisard\, 20 min)\n Next interim F2F will be on Nov. 9 and 10 in Tampa\, FL\n just before SC06.\n\n Review logistics\, agenda\, and attendees.\n - https://forge.gridforum.org/sf/go/wiki1620\n\n3) New DMTF workregister review (Ellen Stokes and Tom Roney\, 30 min)\n After GGF and EGA merge\, OGF need to agree new workregister\n with DMTF sooner rather than later.\n Tom Roney\, OGF liaison to DMTF\, is working on new draft.\n - https://forge.gridforum.org/sf/go/doc13947\n\n From Tom's email:\n> Please take a look with these notes in mind:\n> \n> - I added "Background" to the "Mission" heading\n> Our (GGF/EGA) mission statements have\n> been combined. Modify as you see fit.\n> I did remove references to "enterprise"\n> grids and "enterprise" grid computing\,\n> referring now to (simply) grids and\n> grid computing.\n> \n> - Under the heading of "Alliance Scope"\n> Please take a look at the third paragraph\n> regarding the "Reference Model." Do we\n> leave this? I think so.\n> \n> - After Figure 2\n> We should include a corresponding link between\n> the OGF's Semantic Grid Research Group and a\n> group within the DMTF. What would that group be\,\n> and who would be the DMTF contact?\n> \n> - Under the "Milestones" heading\n> I have done little with this other than\n> to remove what has been accomplished wrt\n> the last register for the GGF.\n> \n> Do we still want the second bullet\, regarding\n> mapping the work underway\, etc.? I think this\n> is important\, but we (I) did nothing to move it\n> forward\, and it will take the effort of a good\n> many minds.\n> \n> Please add to and/or modify this list of goals.\n> \n> - Under the "Contacts" heading\n> I have updated the OGF side with respect\n> to the once-GGF contacts\, noting that the\n> Security Area Directors are listed as\n> Olle Mulmo and Dane Skow. I do not know\n> if this is accurate\, and do not see on the\n> OGF website where this can be found.\n\n Also\, Ellen will bring OGSA-WG related update before the call.\n\n > AI-0915b: Ellen to check the status of the items on the\n > DMTF work register: report which have been done\, and what\n > DMTF is doing for the rest. (by Oct. 13)\n > AI-0915c: Ellen to propose new text to update the DMTF register\n > (by Oct. 13)\n\n Obsolete GGF-DMTF workregister:\n - http://www.ogf.org/documents/liaison/GGF-DMTFWorkRegister.pdf\n Obsolete EGA-DMTF work resister\n - http://www.dmtf.org/about/register/EGA-DMTFWorkRegister.pdf\n\n4) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nOct. 16 (Mon): DMTF Workregister\nOct. 19 (Thu): Information/data modeling\,\n Security\, secure channel profile review\nOct. 23 (Mon): EGA reference model\, OGSA roadmap\nOct. 26 (Thu): Information/data modeling\, EMS scenarios\nOct. 30 (Mon): <TBD>\nNov. 2 (Thu): Security\nNov. 6 (Mon): EGA reference model\, OGSA roadmap\nNov. 9 (Thu): F2F prep\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569?nav=1\n\n > From Oct. 8 call.\n AI-1009a: Review slide 6 again and clarify what the problem is\n (Reference Model Design Team)\n AI-1009b: Review the Reference Model 'Manage Job' in more\n detail. Specifically look at it from the perspective of\n an enterprise application (e.g.\, a 3-tier app) (Reference\n Model Design Team)\n AI-1009c: Hiro to ask Jay to provide his comments for Slide 6\n - Perspective of submitter vs platform provider and the\n hierarchical model connection\n AI-1009d: Jem will produce a topic discussion list for the\n converged glossary\n\n > From Oct. 5 call.\n AI-1005a: Alan Sill willing to take responsibility for pushing\n the process for getting a charter ready (by Oct. 19)\n AI-1005b: People to send Dave Snelling more information\, ideas\n for more security calls to complete coverage\n (Since this does not have any specific owners\, it will\n be closed Oct. 19)\n\n > From Sept. 28 call.\n AI-0928a: Takuya will issue a final call on BSP-Core on the list.\n\n > From Sept. 25 call.\n AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to\n contribute to join the OGSA list and this convergence work. -\n Members may have changed but organizations have not\n AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M)\n on why the current separation of service/info model may\n not be quite right.\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil Oct. 13 call:\n AI-0915b: Ellen to check the status of the items on the\n DMTF work register: report which have been done\, and what\n DMTF is doing for the rest.\n AI-0915c: Ellen to propose new text to update the DMTF register\n\nUntil next EMS call (Oct. 26):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security AD (when one is selected) about the Security Area\n task list.\n\n</pre>\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

clarification on the OGSA Job Management capability
by Sergio Andreozzi 14 Oct '06

14 Oct '06

Dear OGSA-WG, as part of the OMII-Europe project, I'm performing a decomposition of the functionalities provided by a number of Grid middlewares related to our project following the capabilities identified in the OGSA 1.5 document. A problem I'm dealing with is about the Job Management service. For instance, in the gLite middleware, there are two main categories of services providing job management capability: 1. the Computing Element, that is an abstraction of a batch system exposing an interface to let other services to submit and manage a job; in the near future this component will adopt the OGSA-BES interface, but at the moment it is present in different flavours (GT 2 GRAM, g-Lite CE and CREAM) 2. the Workload Management System (WMS), that is a meta-scheduler and exposes an interface to let other services to submit and manages a job (or collection of jobs or DAGs); the WMS not only does Job Management, but also Execution and Planning, and Candidate Set Generator. My doubt is the following: from the viewpoint of Job Management, are a meta-scheduler and a computing service semantically different or identical? If they are identical, is it expected that in a medium future, the BES interface could be extendend to support the number of job types handled by a meta-scheduler, hence the meta-scheduler will expose the same interface of a computing service? If they are not identical, what are the differences? Thanks in advance for your comments, Sergio Andreozzi -- Sergio Andreozzi INFN-CNAF, Tel: +39 051 609 2860 Viale Berti Pichat, 6/2 Fax: +39 051 609 2746 40126 Bologna (Italy) Web: http://www.cnaf.infn.it/~andreozzi

2 2

Teleconference minutes - 9 October 2006
by Andreas Savva 10 Oct '06

10 Oct '06

Attached. Gridforge https://forge.gridforum.org/sf/go/doc13942?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 9 October 2006 ==================================== * Participants Jay Unger (IBM) Jem Treadwell (HP) Paul Strong (eBay) Ellen Stokes (IBM) Dave Snelling (Fujitsu) Andreas Savva (Fujitsu) Fred Maciel (Hitachi) Hiro Kishimoto (Fujitsu) Chris Kantarjiev (Oracle) Chris Jordan (SDSC) Alan Clark () Mukund Buddhikot (SUN) Michael Behrens (R2AD, LLC) Minutes: Andreas Savva * Summary of new actions AI-1009a: Review slide 6 again and clarify what the problem is (Reference Model Design Team) AI-1009b: Review the Reference Model 'Manage Job' in more detail. Specifically look at it from the perspective of an enterprise application (e.g., a 3-tier app) (Reference Model Design Team) AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 - Perspective of submitter vs platform provider and the hierarchical model connection AI-1009d: Jem will produce a topic discussion list for the converged glossary * October 5th minutes accepted with minor corrections - Correct Abdeslem Djaoui's name - Add Andreas Savva to participants - Correct AI misnumbering * Oct 2 minutes approval postponed - Many people were not aware that the Oct.2 minutes had already been posted. * EGA Reference Model ** HPC Cluster Use Case Explained by Hiro - [slide 2] Note that this description is more general than the scope of the *HPC Profile*---this is an HPC cluster use case - [slide 4] The "Abstract Application Definition" appears twice in the stack - There is no problem doing this from the view of the EGA reference model. (It is not necessary to have a 1-to-1 mapping of things on the stack.) - In this case the "HPC cluster" level is probably better called "virtualized platform". Agreed to make this correction. - [slide 5] Provisioning, etc, are noted as out-of-scope of the HPC use case. They do happen but they are done (typically manually) at very rare occasions---e.g., at installation or upgrading of environment---and might occur a long time before or after the actual HPC use case of submitting a job. - There is no actual model conflict here but that is perhaps due to the HPC work not focusing on these aspects even though there are a number of assumptions. (And the assumptions should be made explicit.) - One consequence of this analysis might be to start looking at some other use cases; and so leverage other work from the Reference Model. Staying only on the HPC use case might provide enough coverage. - The works otherwise seem complementary - "Managed Job" in the case of the EGA reference model is probably a much richer concept than in the HPC use case - A longer lived application vs one-off invocation - Interactive vs non-interactive; but this may be less true for HPC applications nowadays - If one can thinks in terms of aggregation of HPC jobs as higher level services then it would fit better into the EGA model - [slide 6] Raises the issue of difference in job vs application state model - Reviewed Paul's suggested alternate figure sent to the mailing list. Agreed it is a good way of looking at things: workload - job +- hpc cluster - node +- binary - This relationship occurs frequently. It is the same for database/database service/database software. (An instance of a database service is composed through managing the things it depends on.) - There is a danger here of trying to do a very elaborate model (like CIM). It is important to know where to draw the line and stop. - OGSA position so far is close to "stop once the service is identified"; the Reference Model on the other hand takes a few more steps towards CIM; but aims to have a broad rather than than a deep view - There is no assertion by the Reference Model that there is only one possible graph - Another difference is what the submitter of the job cares about (needed characteristics/attributes) vs what the environment/platform provider cares about (which includes the hierarchical model needed to instantiate things) - (With the reference model it is enough to focus on the current node; no need to try and dig deep in the hierarchy.) - Some preliminary work is being done in OGSA in the context of the EMS scenarios---the JSDL and CDL connection. - There is a need to discuss and refine the next version of this figure; and incorporate Jay's comments - [slide 5] Need more discussion on what "Submit Job" means - Also "Manage Job" in the Reference Model is much richer than what the HPC/BES model are doing - This is essentially the difference between (discrete) invocations of an HPC job and taking care of an enterprise application that once up has to be taken care of, resources provided appropriately to maintain the required service level, etc. AI-1009a: Review slide 6 again and clarify what the problem is (Reference Model Design Team) AI-1009b: Review the Reference Model 'Manage Job' in more detail. Specifically look at it from the perspective of an enterprise application (e.g., a 3-tier app) (Reference Model Design Team) AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 - Perspective of submitter vs platform provider and the hierarchical model connection ** Glossary review Jem has produced an initial draft with EGA terms highlighted. Agreed that the target is a converged glossary by GGF19. (The HPC discussion is higher priority.) It is important to know where there are differences or discussion points. Agreed that the discussion should proceed by email and the occasional time slot on a teleconference. AI-1009d: Jem will produce a topic discussion list for the converged glossary * AI Review [Only items with updates are listed] AI-0928b: Closed (see next item) AI-0928c: Closed. Obsolete since we have agreed to provide normative text AI-0925b: Closed. Draft was posted to gridforge AI-0921b: Closed. Started writing charter. AI-0921d: Closed. AI-0914f: Closed. Picked location and launched zoomerang. AI-0803e and AI-0803f: No update. - Hiro volunteered to talk to the CDDLM-WG. * OGSa Roadmap Review Chris Jordan gave an overview of current state, followed by some discussion on the status of various documents. - There have been many contributed updates, in particular from Jem, Hiro and Andreas. - Still missing updates for some documents, especially HPC Profile and Naming. - With respect to the state of documents Dave S mentioned that the status of the WSRF and WSN specs has changed since the publication of Roadmap 1.0. - For the Roadmap however the various specification owners (that actually refer to WSRF or WSN) have to update their documents for the Roadmap tables to change. - Chris J is leaving the update of the tables for last. - Status of HPC documents - The HPC Use Cases have finished their public comment period on Sep.20. - Not sure about the HPC Profile - Naming documents: Not sure. The profile does seem close to completion. - Review progress at the next Roadmap call * Other business - Jem has updated the OGSA Wikipedia entry to bring it up to date with the publication of OGSA 1.5 and Basic Profile 1.0 - Thursday's call is cancelled

1 0