August 2005 - ogsa-wg - lists.ogf.org

Teleconference minutes - 10 August 2005
by Andreas Savva 12 Aug '05

12 Aug '05

Minutes attached. https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050810/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 10 August 2005 ==================================== * Participants Pete Ziu (Northrop Grumman) Von Welch (ANL) Jay Unger (IBM) Jem Treadwell (HP) Mary Thompson (LBL) Ellen Stokes (IBM) Andreas Savva (Fujitsu) Takuya Mori (NEC) Mark Morgan (UVa) Tom Maguire (IBM) Fred Maciel (Hitachi) Hiro Kishimoto (Fujitsu) Andrew Grimshaw (UVa) Minutes: Andreas Savva * Minutes Aug. 8 approval postponed * WSRF Basic Profile 1.0 status update - The document is still in GGF Editor review. - Andrew as the Architecture (AD) will ask Greg Newby to bring it to GFSG review. * OGSA-AuthZ-WG discussion Introduction of OGSA-AuthZ-WG deliverables and preliminary discussion about next week's F2F. ** Authorization service document This document is still being revised. It is based on the SAML 1.1 model. A client makes an authorization request and gets back a response - Reply is one of "yes/no/indeterminate or not applicable" - If 'no', does it also return why not? No. - A 'yes' may still change to 'no' later due to other state changes - It actually returns an assertion containing information on what the client can do---the assertion is signed and has a validity period. - There is another variant where a client accesses a service and the service checks whether the operation is allowed at that time. - Is parameter based authorization supported? - Not in version 1 of the document but thinking about it for version 2. - Is it method level or message level? - It is 'method' level---on invocation. The document is basically a - SAML authorization assertion profile; and - extensions to address certain use cases - Does it depend on the OGSA WSRF BP or any other infrastructure? - Initially it was based on OGSI and then moved to WSRF - The document does talk about what state is exposed but does not use these features heavily; it is not a major dependency. - Is it a dependency or composition? In other words, is a service defined or just a set of abstract portTypes that can be composed with other portTypes? - At the moment OGSA-AuthZ is looking at this more as a standalone service. - But there is nothing stopping anyone from mixing the defined portTypes in their service. But conceptually that is not the model the OGSA-AuthZ group has been working with. - Suppose a client wants to access an endpoint. If the authorization point is separate from the service, how can the client find out where it needs to go to receive authorization? - It is out of scope. - A common pattern is to try and access the service endpoint and then the service goes and asks (its authorization point) if it is ok. - Otherwise the client has to be configured with a priori information. (And this also looks like a common case.) ** Attributes document It has been submitted to GGF and is now in public comment. - The Service document (above) came first. It ended up covering a large area so the Attributes portion was pulled out and made into this separate document. The Attributes document defines the - format of attributes and semantics; and - two profiles: SAML and x.509 - Hiro during an earlier review had suggested that this document should be re-formated as a profile document - It is true that some sections are profiles; while others are informational - Now thinking how to re-structure the document - Tom volunteered to help/give feedback with structuring this document as a Profile. These 2 documents are a pair and should really move through the process together but the Attributes document is ahead. In some ways the Attributes document is an addition/appendix of the Service document. ** Security session at F2F The plan is to continue further discussion of these two documents. Also the OGSA-Data WG has questions on the authorization service. There has been some email exchange but they also want to talk at the F2F. Finally how to structure the collaboration around OGSA security and how to start working together. Von is the current chair but he is in the process of handing over the group. Also the group is in process of re-chartering. There are a number of ideas for future work including updating the specifications to use SAML 2.0, integrating XACML work, etc. Hiro mentioned the OGSA naming rule that GFSG has been defining. A new charter for OGSA-AuthZ should include a statement that the group will collaborate with OGSA-WG as needed. - Hiro will send information to Von about this requirement. * Roadmap 1.0 review Review of revision to address public comments. - Sec 1.0: "...human resources..." statement revised. And re-revised to remove "...limited number of people..." - Sec 2.0: "...specifications and profiles..." revision. - "...recommended profile..." addition to define what this term means. Agreed not to duplicate detailed definitions from other documents but provide a short definition and reference. - GFD-I reference - Added Takuya's text describing the OGSA-AuthZ documents. (Needs review) - Table update - Waiting for an update for the Information document from Abdeslem - Discussed deadline to return the document to Greg - Since the F2F is next week it will probably take until the beginning of September. * F2F update - OGSA-EGA meeting - The EGA members have asked for this meeting to be a closed one. It was in the F2F agenda earlier so the implication was that it was a regular open session. For this reason Hiro has dropped it from the last agenda he posted. - A number of concerns were raised with having this as a closed session. - Only a limited number of people can attend (expected to be about 4). At the moment it is probably the two Chairs, Secretary and AD. - Fred also expressed an interest in taking part in this meeting. - It was agreed to discuss who will take part on Monday. - Hiro is still waiting for all the agendas to come in. He has added some new items for Thursday afternoon and Friday morning; including a discussion on re-chartering. - Friday is now scheduled 8-11am and 11am is a hard stop. * Architecture & Glossary 1.5 discussion Andreas confirmed that Andrew will be in charge of the EMS section revision. The EMS revision will cover the new work on BES, RSS, etc. Also the terminology problems raised during the last public comment should be fixed.

1 0

model terminology for Fri Aug 12 OGSA and RM design team call
by Ellen Stokes 12 Aug '05

12 Aug '05

Ellen Stokes STSM, Grid Computing TC Member, IBM Academy of Technology Austin, Texas tl 678 0552 outside +1 512 838 0552 stokese(a)us.ibm.com

1 0

Scenarios to use at the resource model discussion
by Fred Maciel 12 Aug '05

12 Aug '05

Folks, Here is a proposal for scenarios to use at the resource model discussion at the face-to-face. (Chris, thanks for the feedback). Starting by what how to do the discussion, we should project the EMS picture (i.e., the one with all its services) on a whiteboard, then submit "job(s)" to the Job Manager. Then we follow all the information related to the resource model while we go through through the steps of discovery (which happens before job submission), resource selection, deployment, execution, etc.. I'm proposing two scenarios below, which put different emphasis on different points (queues vs online, dynamic vs static information, etc.). On each example I'm cutting details that would be redundant (storage in the first one, I/O bandwidth in the second, etc.). We probably will only have time to tackle one of them, and the first one should be complete enough. (1) Commercial Data Center (see OGSA use cases) We want to allocate two Web servers, two application servers and one database server in a data center, and run a Web site on it. This is an online system so resources are scheduled (i.e., the Web site comes live on a given date). The whole Web site is a single "job submission" which specifies the whole system structure and applications (including versions). The emphasis here is the system structure. [We might add monitoring the load on the resources to re-allocate resources according to the workload.] (2) Consolidation A data center has lots of 4-way machines, and lots of single-CPU jobs. Jobs are queued. You know how much memory each job uses. The objective here is to submit jobs in a way that maximizes utilization, so you want to select a machine that has enough memory and CPU available available to add a given job without thrashing it. I'm assuming that you are using dynamic information on load and memory with reasonably good "freshness" to make the selection. Regards, Fred Maciel Hitachi America R&D

1 0

[Fwd: GGF15 Session Scheduling is open]
by Hiro Kishimoto 12 Aug '05

12 Aug '05

Hi all, Attached is a letter of request from Joel Replogle, GGF Standards Facilitator. Let's review his request and decide our answer at "GGF15 preparation" session in the morning of Aug. 19 (Fri). See you very soon. -- Hiro Kishimoto

1 0

Material for F2F model discussion
by Fred Maciel 11 Aug '05

11 Aug '05

Hi, (1) Here is a new version of the document (Word file). I didn't receive many comments, so there were only minor changes on the contents compared to the version I posted last week. Notice that we will try to sort out the resource model vs information model vs data model nomenclature problem (and perhaps other ones) on the teleconference on Friday. I'm posting the document before we have a conclusion so that you can print it and read it on the plane. (2) I'm including the model proposal that Andrea created (already posted to the mailing list during GGF14) for your convenience. I re-created the PDF file to put everything in two sheets (watch out the paper size when you print it). I also created a text file with the description of the classes, properties and methods in this model, so you can see what they mean. I created this file by copying-and-pasting from the CIM MOF (Manageable Object Format) files, so apologies for the syntax. Remember that the model proposal "flattens" the CIM classes (which I did in the text file also), erases deprecated stuff (idem), and erases stuff out of scope wrt JSDL, containers and activities (which I also erased from the text file, but not exhaustively). (3) Here is an updated list of pointers on related specs. - JSIM: the spec (GFD-I.028) is at: https://forge.gridforum.org/projects/ggf-editor/document/GFD.28/en/1 There is also a UML diagram: https://forge.gridforum.org/projects/ogsa-wg/document/JSIM_PDF/en/1 - CIM: the schemas are under: http://www.dmtf.org/standards/cim JSIM classes are in 2.10 experimental (awaiting implementation experience to become final). You can find a tutorial (HTML and PDF) at: http://www.wbemsolutions.com/tutorials/CIM/ - JSDL: http://www.ggf.org/Public_Comment_Docs/Documents/July-2005/draft-ggf-jsdl-sp ec-021.pdf There's a nice introduction at: https://forge.gridforum.org/projects/jsdl-wg/document/JSDL-Introduction/en/ - GLUE 1.1: the schemas are in http://infnforge.cnaf.infn.it/glueinfomodel/ There's a good presentation on GLUE 1.1: http://www.dma.unina.it/~murli/SummerSchool/presentations/InformationModelin g-GLUE.ppt - GLUE 1.2: http://infnforge.cnaf.infn.it/glueinfomodel/ The latest draft can be found under: http://infnforge.cnaf.infn.it/glueinfomodel/uploads/Spec/GLUEInfoModel_1_2_d raft_8.pdf There is a very good presentation at: http://infnforge.cnaf.infn.it/cdsagenda//askArchive.php?base=agenda&categ=a0 56&id=a056s0t1/transparencies Regards, Fred Maciel

2 1

RM teleconference minutes: August 9, 2005
by Fred Maciel 11 Aug '05

11 Aug '05

Hi, Here are the minutes. Regards Fred Maciel Hitachi America R&D

1 0

Right said Fred...
by Treadwell, Jem 11 Aug '05

11 Aug '05

Hi, for some reason working on the minutes this morning kept reminding me of the the following song, which I realized might be a useful case study of resource management. It was published back in 1962, by a British academic named Bernard Cribbins (http://www.answers.com/topic/bernard-cribbins) - think of him as the British working man's Tom Lehrer (http://en.wikipedia.org/wiki/Tom_Lehrer) I suspect all the Brits and their children will know the song pretty well, but I doubt if it's well known anywhere else. The resource in question was a piano, and the management task was to get it out of a house. The process they followed is roughly the same as the modern-day working group process of repeatedly taking a stab at a problem and then heading for the bar (and slipping the schedule) when it proves too difficult, but the language is particularly British, so for those who are unfamiliar I've included a Glossary. :0) - Jem Right Said Fred Performed by Bernard Cribbins Lyrics reproduced without permission Right said Fred, both of us together, one each end and steady as we go Tried to to shift it, couldn't even lift it, we was getting nowhere And so, we, had a cup of tea Right said Fred, give a shout to Charlie, up comes Charlie from the floor below After straining, heaving and complaining, we was getting nowhere And so, we, had a cup of tea Charlie had a think and he thought we ought, to take off all the handles And the things that hold the candles - but it did no good (well I never thought it would!) Right said Fred, have to take the feet off, to get them feet off wouldn't take a mo... Took its feet off, even with the seat off, should have got us somewhere, but no! So Fred said let's have another cup of tea, and we said "right-oh!" Right said Fred, have to take the door off, need more space to shift the so-and-so Had bad twinges, taking off the hinges, and it got us nowhere And so, we, had a cup of tea Right said Fred, have to take the wall down, that there wall is gonna have to go Took the wall down, even with it all down, we was getting nowhere And so, we, had a cup of tea Charlie had a think and and he said look Fred, I've got a sort of feeling If we remove the ceiling, With a rope or two we can drop the blighter through... Right said Fred, climbing up a ladder, with his crowbar gave a mighty blow Was he in trouble, half a ton of rubble, landed on the top of, his dome So Charlie and me had another cup of tea And then we, went home! [Spoken, fading out...] I said to Charlie we'll just have to leave it standing on the landing, that's all. You see the trouble with Fred is, he's too hasty. Now you never get nowhere if you're too hasty... Glossary mo = moment right-oh! = an expression of cheerful agreement so-and-so = an exasperating person or other resource blighter = so-and-so dome = head landing = upstairs hallway ________________________________ 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>

2 1

RE: [ogsa-wg] RM teleconference on Friday, August 12
by Fred Maciel 10 Aug '05

10 Aug '05

Hi again, > - 23:00-24:00 Japan (GMT + 9, following day) Same day, not following day. Regards, Fred Maciel Hitachi America R&D

1 0

RM teleconference on Friday, August 12
by Fred Maciel 10 Aug '05

10 Aug '05

Hi, The Resource Management design team will have a teleconference on Friday, August 12. The main objective is, in preparation to the face-to-face, to sort out the terminology (information vs resource model etc.) and hopefully discuss the similarities and differences between them. Many thanks to Ellen for volunteering to sort out this information beforehand. Date: Tuesday, August 12th, at the following times: - 07:00-08:00 US Pacific (GMT - 7) - 08:00-09:00 US Mountain (GMT - 6) - 09:00-10:00 US Central (GMT - 5) - 10:00-11:00 US Eastern (GMT - 4) - 14:00-15:00 GMT - 15:00-16:00 UK (GMT + 1) - 16:00-17:00 Central Europe (GMT + 2) - 23:00-24:00 Japan (GMT + 9, following day) Dial-in: Toll Free: (888) 422-7120 Int'l Access: (608) 250-0194 Participant code: 693305 If screen sharing is needed, let's use Glance: URL: http://ogsa.glance.net Session key: 0719 Explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html See you there, Fred Maciel Hitachi America R&D

1 0

RE: [ogsa-wg] Right said Fred...
by Subramaniam, Ravi 10 Aug '05

10 Aug '05

Right said Jem!!! Ravi ________________________________ From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Treadwell, Jem Sent: Wednesday, August 10, 2005 12:40 PM To: ogsa-wg Subject: [ogsa-wg] Right said Fred... Hi, for some reason working on the minutes this morning kept reminding me of the the following song, which I realized might be a useful case study of resource management. It was published back in 1962, by a British academic named Bernard Cribbins (http://www.answers.com/topic/bernard-cribbins) - think of him as the British working man's Tom Lehrer (http://en.wikipedia.org/wiki/Tom_Lehrer) I suspect all the Brits and their children will know the song pretty well, but I doubt if it's well known anywhere else. The resource in question was a piano, and the management task was to get it out of a house. The process they followed is roughly the same as the modern-day working group process of repeatedly taking a stab at a problem and then heading for the bar (and slipping the schedule) when it proves too difficult, but the language is particularly British, so for those who are unfamiliar I've included a Glossary. :0) - Jem Right Said Fred Performed by Bernard Cribbins Lyrics reproduced without permission Right said Fred, both of us together, one each end and steady as we go Tried to to shift it, couldn't even lift it, we was getting nowhere And so, we, had a cup of tea Right said Fred, give a shout to Charlie, up comes Charlie from the floor below After straining, heaving and complaining, we was getting nowhere And so, we, had a cup of tea Charlie had a think and he thought we ought, to take off all the handles And the things that hold the candles - but it did no good (well I never thought it would!) Right said Fred, have to take the feet off, to get them feet off wouldn't take a mo... Took its feet off, even with the seat off, should have got us somewhere, but no! So Fred said let's have another cup of tea, and we said "right-oh!" Right said Fred, have to take the door off, need more space to shift the so-and-so Had bad twinges, taking off the hinges, and it got us nowhere And so, we, had a cup of tea Right said Fred, have to take the wall down, that there wall is gonna have to go Took the wall down, even with it all down, we was getting nowhere And so, we, had a cup of tea Charlie had a think and and he said look Fred, I've got a sort of feeling If we remove the ceiling, With a rope or two we can drop the blighter through... Right said Fred, climbing up a ladder, with his crowbar gave a mighty blow Was he in trouble, half a ton of rubble, landed on the top of, his dome So Charlie and me had another cup of tea And then we, went home! [Spoken, fading out...] I said to Charlie we'll just have to leave it standing on the landing, that's all. You see the trouble with Fred is, he's too hasty. Now you never get nowhere if you're too hasty... Glossary mo = moment right-oh! = an expression of cheerful agreement so-and-so = an exasperating person or other resource blighter = so-and-so dome = head landing = upstairs hallway ________________________________ 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