October 2006 - ogsa-wg - lists.ogf.org

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

no call on Oct. 12
by Hiro Kishimoto 10 Oct '06

10 Oct '06

Hi all, We don't have a call on this Thursday (Oct. 12). Next call will be next Monday. 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 OGSA-WG and fellow WGs will have interim F2F meeting on Nov. 9 and 10 in Tampa FL just before SC06. If you have not yet answered by Zoomerang survey, please let us know your availability by Oct. 13 Friday. http://www.zoomerang.com/survey.zgi?p=WEB225QVWQBDKV For more information on this F2F, visit living agenda wiki page: https://forge.gridforum.org/sf/go/wiki1620 Thanks, -- Hiro Kishimoto

1 0

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

09 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 9th 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: 1009 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. 5) - https://forge.gridforum.org/sf/go/doc13922?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) HPC profile usecase for EGA reference model (60 min) > AI-092625b: Jem to pull definitions together and produce a new > merged first draft. > - Send a mail to the ogsa list about this work > - Set Oct. 9 as the target for the first Glossary draft > - Mike Behrens also volunteered to help out on the Glossary Jem will write-up his first draft before the call. > - At GGF18 the proposal was to consider OGSA as a rendering of the > EGA reference model. Agreed that this seems a good starting > point. It should be tested by picking a candidate topic and see > if it is really the case. > - Hiro proposed the OGSA HPC Profile as a test case (a concrete > use case) > - The HPC Profile is more detailed when compared to the style of > the use cases in the EGA Reference Model. Therefore it would > help flesh out what is needed in the context of OGSA. Doing UML > would be good. > - It was noted that EGA graphs (DAGS) are specific to > instantiation > - Tentative agreement on the HPC Profile proposal but need more > information before making a decision. Hiro will write-up draft proposal before the call. 4) Roadmap document v1.1 discussion (Chris Jordon, 20 min) ChrisJ will report out the status of roadmap v1.1. He will ask if current direction is on the right track or not. The latest roadmap document: - https://forge.gridforum.org/sf/go/doc13733?nav=1 List of included documents and associated contacts: - https://forge.gridforum.org/sf/go/wiki1486?nav=1 Minutes from Oct. 4th roadmap call: - https://forge.gridforum.org/sf/go/doc13923?nav=1 3) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 12 (Thu): <No call?> 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 Oct. 30 (Mon): <TBD> <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Oct. 5 call. AI-1005a: Alan Sill willing to take responsibility for pushing the process for getting a charter ready 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. AI-0928b: Takuya will get another opinion on TLS 1.1 and ciphersuites (probably ask Frank Siebenlist) AI-0928c: Andreas will propose new text for the reference to the NIST document to make it clearer that it is an informative statement > From Sept. 25 call. AI-0925b: Jem to pull definitions together and produce a new merged first draft. - Send a mail to the ogsa list about this work - Set Oct. 9 as the target for the first Glossary draft 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. 21 call. AI-0921b: Security members to discuss the BoF proposal(s) further - For example, one outcome could be some standards activity to mirror CAOPS activities and tie-in to OGSA AI-0921d: Dave S to collect additional material in order to identify security issues better. - (AI-0921e is an issue instance) > 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 Sept. 14 OGSA F2F AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the next F2F and inform the group vial the mailing list > 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 (date TBD): 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

3 5

Nov. interim F2F meeting survay
by Hiro Kishimoto 07 Oct '06

07 Oct '06

Hi all, OGSA-WG and fellow WGs will have interim F2F meeting on Nov. 9 and 10 in Tampa FL just before SC06. Please let us know your availability and session proposals by answering Zoomerang survey before Oct. 13 Friday. http://www.zoomerang.com/survey.zgi?p=WEB225QVWQBDKV For more information on this F2F, visit living agenda wiki page: https://forge.gridforum.org/sf/go/wiki1620 Thanks, -- Hiro Kishimoto

1 0

OGSA-AuthN WG start
by Alan Sill 06 Oct '06

06 Oct '06

Hi Hiro and the group, At the EUGrid PMA meeting today in Karlsruhe, Germany ( see the URL http://eugridpma.org/agenda/fullAgenda.php?ida=a062 for details), there was wholehearted endorsement of the idea of starting an OGSA-AuthN working group and for organizing a BOF along these lines at OGF 19 to write the charter and begin the OGSA activities of this group. At this point, I would like to suggest that we formally pursue the steps to create this group. Best, 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 : ====================================================================

1 0

Roadmap call minutes, 10/4, uploaded
by Christopher Jordan 06 Oct '06

06 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded the minutes of the OGSA Roadmap editors call of October 4th to Gridforge. Hiro and Dona, please feel free to make additions or corrections if I missed anything. https://forge.gridforum.org/sf/go/doc13923?nav=1 The next OGSA call discussion of the Roadmap will be next monday, October 9th, and I'd like to propose that the next OGSA Roadmap Editors call be Wednesday, October 18th. 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.1 (Darwin) iD8DBQFFJZniPCVtcXn6kg8RAm+IAJ9D3uCKvU6FpcPnCmX177UY4W05UQCggMMs uBSM8D7KOIGB9MXqlT5pNfs= =PszJ -----END PGP SIGNATURE-----

2 1

Fwd: [caops-wg] OGSA activity to cover authentication and identity provision roadmap
by Alan Sill 05 Oct '06

05 Oct '06

FYI -- this is typical of responses. Alan Begin forwarded message: > From: David Groep <davidg(a)nikhef.nl> > Date: October 5, 2006 6:54:42 AM CDT > To: Alan Sill <Alan.Sill(a)ttu.edu> > Cc: igtf-general(a)gridpma.org, Mailing List for CAOPS-WG <caops- > wg(a)ogf.org>, gsmv(a)webapp.lab.ac.uab.edu, gridshib-beta(a)globus.org > Subject: Re: [caops-wg] OGSA activity to cover authentication and > identity provision roadmap > > Dear Alan, all, > > First of all, I would like to support this proposal, as it could > indeed > provide the focal point for harmonisation amongst the various > activities in this area that have emerged both inside and those > (still) outside OGF. Over the past year I feel we have come quite > close > to a kind of "common understanding" of what the issues are, and > drafting > a collective roadmap is IMHO a very timely activity. > > Of course, I can happily offer a timeslot during the upcoming > EUGridPMA > meeting to discuss this (of course also completely open to the > world and > community at large: join this part of the meeting via VRVS in > the "Sky" virtual room, "Earth/Universe" community: www.vrvs.org) > If the current planning is not optimal (this Friday, Oct 6, > 11.00 AM CEST=UTC+2), it can also be delayed a few hours. > > As I see it, the BoF for this new WG could also address some issues > I feel we currently have with the CAOPS charter and position with > respect to other activities in OGF (both with CAOPS being seen as an > "operations" activity, but even more importantly the possible > conception > that CAOPS is only about the operation of "traditional" X.509 CAs). > In this respect, I would be highly interested in how others in CAOPS > see the relationship between CAOPS and such a new group. > Personally, I think also the IGTF as an operational policy > coordination > body, should have close relationships with both groups, especially > as they are expanding into new authentication profile models. > > There is, however, also an increasing overlap between the > activities in > AuthN and AuthZ. The new federations of organisationally-based > sources of authority supply attributes and assertions that are > relevant for both: some attributes relate to what we have > traditionally seen as authentication (unique names, their long-term > binding to entities, and the way to prove identity), but others > by the same source relate more to authorisation (roles, position in > the organisation &c). > In the long run there may be not that clear a division between the > two, especially when multiple sources of authority are involved in > a combined decision. But this combination of assertions, possibly > with different assurance levels, and with different levels from > different sources, will highlight the need to convey such assurance > levels, and their recognition in policy decisions, in a harmonised > formats and semantics. > Will the AuthN roadmap address include such issues - which I > think it certainly should - when these assertions relate to > long-term "AuthN" attributes? Even of the actual assertions are > more related to what we might now consider "AuthZ" (such as > organisational role/position)? But that's probably something for > the BoF to figure out (given sufficient participation from > the OGSA-AuthZ folks). > > Lastly, I think we should advertise this BoF and our intentions > widely, as there are very many related activities in this area, > also outside OGF. In particular (with a slight European bias) there > are the TERENA TF-EMC2 and TF-Mobility groups that to some extent > rely on or aim for coordination in this domain; there is the > eduGAIN activity (organised as part of the GEANT2 project); and > the EuroCAMP meetings on federation (the next one in two weeks in > Malaga, ES) are all highly relevant to this work. Many of > our combined groups will attend at least a few of these meetings, > and -- if we all agree OGSA-AuthN is a good idea -- should take the > opportunity to get all relevant people around the table at OGF19. > > > Best regards, > DavidG. > > > Alan Sill wrote: >> I'd like to suggest to the CAOps and Grid CA community that we >> attempt to pull together thoughts on grid identity authentication >> in terms of a roadmap and/or BOF among interested parties, >> focusing primarily on the AuthN side. This would be a complement >> to the OGSA- AuthZ activity, which we could clearly call OGSA-AuthN. >> I realize that we need another working group like, well, a whack >> on the head, but I have thought about this one a lot and I think >> that the OGSA process would bring a lot of rationalization to >> the activities and effort that we are pursuing more or less >> piecemeal in the search for a workable solution. Among things >> that we could gain by having such an effort, we could include: >> - Clear separation from OGSA-AuthZ while still allowing a strong >> channel for communication >> - Bringing together several different working groups who are all >> working on identity provision (as opposed to authorization) for grids >> - Providing for better communication between the OGSA roadmap and >> CAOps practices >> - Providing a context for working groups, such as the Bridge CA >> and Shibboleth activities, to communicate their findings >> - Placing OGSA-AuthN and OGSA-AuthZ on a similar footing >> To follow through on this, I would like to have a brief discussion >> in the IGTF portion of the upcoming EUGridPMA meeting, followed >> by a similar discussion at the TAGPMA Novemvber face-to-face, and >> of course encourage similar discussion at the APGridPMA meeting >> this fall. Any decision to follow this path should be discussed >> with the incoming area directors of the Security area within the >> Open Grid Forum, along with specific details about the charter. >> To make this happen, we could form a BOF to be held at the next >> OGF conference in North Carolina in January, along the lines of >> the recent "Shibboleth for Grids" one that we held at GGF 18, >> with an aim to take on this topic as a roadmap activity directly. >> Thought are extremely welcome and recruited. As a point of >> background information, I have been discussing this idea among >> the members of the overall OGSA-WG working group, and have found >> many useful suggestions and an open reception to this idea. The >> topic of a BOF as discussed above has been strongly encouraged. >> Best, >> 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 : >> ==================================================================== >> -- >> caops-wg mailing list >> caops-wg(a)ogf.org >> http://www.ogf.org/mailman/listinfo/caops-wg > > > -- > David Groep > > ** National Institute for Nuclear and High Energy Physics, PDP/Grid > group ** > ** Room: H1.56 Phone: +31 20 5922179, PObox 41882, NL-1009DB > Amsterdam NL ** > > 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 : ====================================================================

1 0

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

05 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 5th 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: 1005 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 (Sept. 28) - https://forge.gridforum.org/sf/go/doc13912?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA security (David Snelling, 60 min) - What needs to be done to achieve simple interop generally and to bootstrap more - Profile to get authentication information from a secure channel for authentication - Profile for other methods to get authentication informatin for authorization 3) Secure Channel Security Profile status (Takuya Mori, 20 min) > Takuya will prepare a new version. Since there are a number of > unresolved issues the Secure Channel will not go to final call until > the issues raised during this review are closed. > > There is a security discussion scheduled for next Thursday (Oct > 5). Confirm status at that time. 4) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 9 (Mon): EGA reference model, OGSA roadmap Oct. 12 (Thu): <No call?> 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 Oct. 30 (Mon): <TBD> <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Sept. 28 call. AI-0928a: Takuya will issue a final call on BSP-Core on the list. AI-0928b: Takuya will get another opinion on TLS 1.1 and ciphersuites (probably ask Frank Siebenlist) AI-0928c: Andreas will propose new text for the reference to the NIST document to make it clearer that it is an informative statement > From Sept. 25 call. AI-0925a: Hiro to setup wiki page with names of people who have expressed interest in the security team AI-0925b: Jem to pull definitions together and produce a new merged first draft. - Send a mail to the ogsa list about this work - Set Oct. 9 as the target for the first Glossary draft 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. 21 call. AI-0921b: Security members to discuss the BoF proposal(s) further - For example, one outcome could be some standards activity to mirror CAOPS activities and tie-in to OGSA AI-0921d: Dave S to collect additional material in order to identify security issues better. - (AI-0921e is an issue instance) AI-0921i: Dave S to provide an agenda for the next security call. - Draft agenda items for Oct. 5th: - What needs to be done to achieve simple interop generally and to bootstrap more - Profile to get authentication information from a secure channel for authentication - Profile for other methods to get authentication informatin for authorization > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience 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) 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 Sept. 14 OGSA F2F AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the next F2F and inform the group vial the mailing list > 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. 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

6 8