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

GGF-DMTF Work Register
by Hiro Kishimoto 04 Aug '05

04 Aug '05

Hi all, Tom Roney, GGF forum-level liaison to DMTF, ask us to review updated GGF-DMTF Work Register document. OGSA-WG already has dialogue with DMTF folks and I think this document is consistent with our on going activity. Thus I would like to put this item into next Monday call agenda. Thanks, -- Hiro Kishimoto

4 10

Aug F2F meeting draft agenda
by Hiro Kishimoto 02 Aug '05

02 Aug '05

Hi all, Attached is the early draft of the August F2F meeting in SF Bay Area. Please have a look, we will review this at tomorrow's OGSA call. As usual, the file is also uploaded to the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/OGSA-2005-Aug-F2F-age… Thanks, -- Hiro Kishimoto

2 2

Proposed agenda for Aug. 1st call
by Hiro Kishimoto 01 Aug '05

01 Aug '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on August 1st Monday from 5pm to 7pm (CDT). The dial-in number for Monday; Free: +1-866-639-4741 Toll: +1-574-935-6703 PIN: 8980700 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0801 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (10 min) Note taker assignment Roll call Telecon minutes approval https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050727/en/1 F2F update (if any) - Revised agenda (with dial-in info) https://forge.gridforum.org/projects/ogsa-wg/document/OGSA-2005-Aug-F2F-age… Agenda bashing 2) Roadmap doc public comments (30 min) Jem will report what we got finally. - PB tracker: https://forge.gridforum.org/forum/forum.php?forum_id=540 3) OGSA Arch & Glossary 1.5 (60 min) Andreas and Jem will explain a plan for 1.5 development. 4) GGF-DMTF work register review (30 min) > Tom Roney, GGF forum-level liaison to DMTF, ask us to review > updated GGF-DMTF Work Register document. 5) Wrap up (10 min) AOB Aug. 3 (Wed) <TBD> Aug. 8 (Mon) Resource Modeling discussion, Provisioning, F2F preparation Aug. 10 (Wed) OGSA-AuthZ-WG, roadmap, F2F preparation Aug. 15-19 F2F meeting https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ ---- Hiro Kishimoto

3 2

Submission to GGF-Editor of OGSA WSRF Basic Profile 1.0
by Tom Maguire 29 Jul '05

29 Jul '05

Folks, Thanks for all the final call comments. Good catches all. I have submitted the OGSA WSRF Basic Profile 1.0 document to the GGF-Editor. The version that was submitted included minor edits and nits from the final call comments. All of the edits have been discussed on the mailing list. The version that was submitted is: https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… Good work everyone! Tom Frey’s Law: “Every 5 years the number of architecture components double and the ability to comprehend them halves” Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. – Antoine de Saint-Exupery T o m M a g u i r e STSM, On Demand Architecture Poughkeepsie, NY 12601

1 0

RE: [ogsa-wg] FINAL CALL Document OGSA WSRF BP 1.0 v036
by Treadwell, Jem 29 Jul '05

29 Jul '05

Tom, my annotated review attached. I gather that you've already incorporated comments from others, so this is based on a clean copy of v36. Most of these are, of course, minor nits, and some are just periods or colons added. However, there are a couple that are quite significant, most notably the use of MAY NOT in Appendix E. Your discretion on which of these you incorporate, and I vote YES to go to the editor. Great job by you and the whole team! - Jem > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Tom Maguire > Sent: Wednesday, July 27, 2005 11:48 PM > To: ogsa-wg(a)ggf.org > Subject: [ogsa-wg] FINAL CALL Document OGSA WSRF BP 1.0 v036 > > https://forge.gridforum.org/projects/ogsa-wg/document/draft-gg > f-ogsa-wsrf-basic-profile/en/31 > > > The final call document for the OGSA WSRF Basic Profile 1.0 > is available for download at the above link. Please review > and positive acknowledge with an email to the mailing list > with your vote (yea or nay) for submission from the workgroup > to the GGF Editor. Please vote (email) by Friday, July 29th > COB (EDT). > > If your vote is 'nay' please include precise comments so that > we may address any substantive issues you may have prior to > submission. > > Thanks, > Tom > > > Frey's Law: "Every 5 years the number of architecture > components double and the ability to comprehend them halves" > > > Perfection is achieved, not when there is nothing more to > add, but when there is nothing left to take away. - Antoine > de Saint-Exupery > > > T o m M a g u i r e > > > STSM, On Demand Architecture > > > Poughkeepsie, NY 12601 >

2 1

RE: [ogsa-wg] FINAL CALL Document OGSA WSRF BP 1.0 v036
by Srinivasan, Latha 29 Jul '05

29 Jul '05

Tom, Looks good. I have some minor nits/ modifications that I made on Hiro's version, so hopefully you don't have to go through merge nightmares. They are not show stoppers necessarily, so my vote is a yea. Regards, Latha -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Djaoui, A (Abdeslem) Sent: Friday, July 29, 2005 11:02 AM To: Tom Maguire Cc: ogsa-wg(a)ggf.org Subject: RE: [ogsa-wg] FINAL CALL Document OGSA WSRF BP 1.0 v036 Hi Just some fairly minor comments, othewise yea, go for it. I'll leave it up to Tom to decide on the 3 points below. Abdeslem ==================================================================== Section 2: line 184: should the conformance claim URI be "http://www.ggf.org/namespaces/2005/07/OGSAWSRFBasicProfile-1.0" and, I guess if we include WSRF here, all other namespaces (in schema) should also be changed. Section 4: line 267: DO you mean wsdl:Service or wsdl:Service/port? in WSDL 1.1 a Service can aggregate many ports. Anyway the sentence is not clear: "a list of all portTypes that were used to compose the wsdl:Service"? Do you mean the portTypes corresponding to different ports, or the list of known portTypes that were composed together to make a new portType for this Service/port? Section 4.4.1: line 366: RECOMMENDS should be MANDATES in order to be consistent with section 6.1 where the profile MANDATES the use NotificationProducer for notifications of events from resources. ==================================================================== Tom Maguire wrote: > https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-w > srf-basic-profile/en/31 > > > The final call document for the OGSA WSRF Basic Profile 1.0 is > available for download at the above link. Please review and positive > acknowledge with an email to the mailing list with your vote (yea or > nay) for submission from the workgroup to the GGF Editor. Please vote > (email) by Friday, July 29th COB (EDT). > > If your vote is 'nay' please include precise comments so that we may > address any substantive issues you may have prior to submission. > > Thanks, > Tom > > > Frey's Law: "Every 5 years the number of architecture components > double and the ability to comprehend them halves" > > > Perfection is achieved, not when there is nothing more to add, but when > there is nothing left to take away. - Antoine de Saint-Exupery > > > T o m M a g u i r e > > > STSM, On Demand Architecture > > > Poughkeepsie, NY 12601 > >

2 1

RE: [ogsa-wg] FINAL CALL Document OGSA WSRF BP 1.0 v036
by Djaoui, A (Abdeslem) 29 Jul '05

29 Jul '05

Hi Just some fairly minor comments, othewise yea, go for it. I'll leave it up to Tom to decide on the 3 points below. Abdeslem ==================================================================== Section 2: line 184: should the conformance claim URI be "http://www.ggf.org/namespaces/2005/07/OGSAWSRFBasicProfile-1.0" and, I guess if we include WSRF here, all other namespaces (in schema) should also be changed. Section 4: line 267: DO you mean wsdl:Service or wsdl:Service/port? in WSDL 1.1 a Service can aggregate many ports. Anyway the sentence is not clear: "a list of all portTypes that were used to compose the wsdl:Service"? Do you mean the portTypes corresponding to different ports, or the list of known portTypes that were composed together to make a new portType for this Service/port? Section 4.4.1: line 366: RECOMMENDS should be MANDATES in order to be consistent with section 6.1 where the profile MANDATES the use NotificationProducer for notifications of events from resources. ==================================================================== Tom Maguire wrote: > https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… > > > The final call document for the OGSA WSRF Basic Profile 1.0 is available > for download at the above link. Please > review and positive acknowledge with an email to the mailing list with your > vote (yea or nay) for submission from > the workgroup to the GGF Editor. Please vote (email) by Friday, July 29th > COB (EDT). > > If your vote is 'nay' please include precise comments so that we may > address any substantive issues you may have > prior to submission. > > Thanks, > Tom > > > Frey’s Law: “Every 5 years the number of architecture components double and > the ability to comprehend them halves” > > > Perfection is achieved, not when there is nothing more to add, but when > there is nothing left to take away. – Antoine de Saint-Exupery > > > T o m M a g u i r e > > > STSM, On Demand Architecture > > > Poughkeepsie, NY 12601 > >

2 1

FINAL CALL Document OGSA WSRF BP 1.0 v036
by Tom Maguire 29 Jul '05

29 Jul '05

https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… The final call document for the OGSA WSRF Basic Profile 1.0 is available for download at the above link. Please review and positive acknowledge with an email to the mailing list with your vote (yea or nay) for submission from the workgroup to the GGF Editor. Please vote (email) by Friday, July 29th COB (EDT). If your vote is 'nay' please include precise comments so that we may address any substantive issues you may have prior to submission. Thanks, Tom Frey’s Law: “Every 5 years the number of architecture components double and the ability to comprehend them halves” Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. – Antoine de Saint-Exupery T o m M a g u i r e STSM, On Demand Architecture Poughkeepsie, NY 12601

2 3

Teleconference minutes - 27 July 2005
by Andreas Savva 29 Jul '05

29 Jul '05

Minutes attached. * Roadmap document: Public comment discussion * F2F update * WSRF Basic Profile 1.0 review https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050727/en/1 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

Re: [ogsa-wg] RNS critique (new revision available)
by Manuel Pereira 28 Jul '05

28 Jul '05

Hello All, In light of Dave Berry?s comments and considering the work already done, I would like to propose that we keep the resolver operations, at least for now. If necessary, we can always factor them out into a separate document in a later revision, provided that there is an equivalent replacement. This implies the continued use of logical names (abstract names) within RNS and thus the inclusion and description of the logical reference (section 1.1.2.2). The latest revision has been posted to GridForge: https://forge.gridforum.org/projects/gfs-wg/document/RNS-Proposed_Final_Dra… Major revisions include: - Completely revised ?Alias Junction? description in section 1.1.2.4 - Revised section 1.1.2.2, previously ?Virtualized Reference Junction? now made consistent with other terminology to be ?Logical Reference Junction? - Section 1.2.2.2.1 updated to reflect revised property names and corresponding values for logical references - Updated all of the namespace and implicit operations to incorporate the said revisions - Updated section 2, with a particular emphasis in section 2.2.1.1 in an attempt to better describe the referral message - Updated the table in section 3.3.1 to reflect the use of the ?LogicalName? property throughout section 3 - Completely removed the Grid File System naming profile from the appendix - Absolute vs. Full Paths were elaborated and hopefully clarified - Description for mechanisms for namespace federation revised - Repository description explicitly clarified Best regards, Manuel Pereira =============================== IBM Almaden Research Center 1-408-927-1935 [T/L 457] mpereira(a)us.ibm.com owner-ogsa-naming-wg(a)ggf.org wrote on 07/22/2005 01:37:18 PM: > I'm a bit concerned about removing the mapping to logical names. I > thought the e-mail reply to Andrew's criticism seemed valid - we have a > three-tier naming system in OGSA, so it makes sense for RNS to support a > mapping to logical names. This remains true even if the spec for these > logical names is provided by a different group. > > I know that WS-Names are likely to be EPRs, which perhaps simplifies the > system. Is it sufficient for RNS to support mappings to EPRs and for > the context to determine whether those EPRs are logical names or > physical names? > > Dave. > > > -----Original Message----- > > From: owner-gfs-wg(a)ggf.org [mailto:owner-gfs-wg@ggf.org] On > > Behalf Of Osamu Tatebe > > Sent: 22 July 2005 04:18 > > To: gfs-wg(a)ggf.org > > Subject: [gfs-wg] Minutes of 7/20,21 GFS-WG Conference call > > > > Hi all, > > > > Please look at minutes of the last conference call. The discussion > > includes several changes and decisions for the final RNS document. > > > > Thanks, > > Osamu > > > > --- > > GFS-WG conference call > > Wednesday, July 20, 2005 > > 3:30pm to 5pm (PDT) > > > > Note taker: Osamu Tatebe (AIST) > > > > Participants > > ------------ > > Manuel Pereira > > Ken Wood > > Arun Jagatheesan > > Osamu Tatebe > > > > Agenda > > ------ > > Introduction & agenda bushing ( 5min) > > Recent change (10min) > > Alias junction issues (30min) > > Other minor issues (15min) > > > > Meeting > > ------- > > * Recent change from the document on July 8 > > > > https://forge.gridforum.org/projects/gfs-wg/document/RNS-Propo > sed_Final_Draft-v1.7/en/7 > > > > - reflect comments from OGSA-WG > > > > o Appendix of Grid File System Profile > > > > - better to focus RNS. keeping consistency level is important. > > basically, appendix is not so important. > > > > - we will start Grid File System Profile document as a separate > > document from next week. > > > > -> The appendix will be taken out > > > > o Section 3 "Resource Endpoint Resolution Service" > > > > - this part will be taken over by OGSA Naming WG. > > > > -> The Section 3 will be taken out > > > > o WS-enumeration > > > > - Microsoft proposes WS-enumeration that provides similar > > functionality of iterator in list operation. > > > > -> WS-enumeration specification is not standardized yet. it lacks > > features to improve performance. we can follow the spec once it > > is standardized. > > > > * Alias junction issues > > > > - Background: alias junction emulates a hardlink functionality. > > Once, we are using OID to specify a target of an alias junction. > > In this case, we just care about AliasCount of the target entry to > > avoid to be a broken reference. On the other hand, we take out OID > > completely in the document, and use pathname to specify a target > > entry instead. In this case, an alias junction may be orphaned > > when one of entries in the pathname is moved or renamed. Section > > 1.1.2.4 "Alias Junction" needs to be modified. > > > > - Two options; > > > > (1) add the above constraint in the third paragraph "Prohibit > > modification of the target" > > > > (2) make alias junction an optional feature of RNS, while the > > service needs to update the TargetPath property dynamically if > > it supports the alias junction. > > > > -> We choose (2) since it is simpler and reasonable. > > > > * Other issues in RNS Specification > > > > - There is a comment from OGSA-WG such that RNS should be simple and > > does not need to have several types in Junction. > > > > o Since we take out the RNS Resolver in Section 3, logical name does > > not make sence so much. So, we can collapse Endpoint Reference > > Junction and Virtualized Reference Junction. Also, Alias Junction > > is now an optional junction. > > > > -> We will have three types of junctions; > > > > o Endpoint Reference Junction > > o Referral Junction > > o Alias Junction [optional] > > > > Referral Junction is a special type of Endpoint Reference Junction, > > which points to an entry in (separate) RNS. On the other hand, for > > easy federation of RNSs (this is quite a typical usage of RNS), to > > have a separate type is reasonable. > > > > - In Figure 2 in Section 2 "Federation of Resource Namespace > > Service", Path specified in list operation to the RNS > > (research.acme.org) seems to be a full path not an absolute path. > > Need to clarify this. > > > > * Submission plan > > > > - After reflecting above changes, we will distribute the final > > release candidate. We will submit it in the *first week of > > August*, although we try to reflect every comments from now to the > > submission date. > > > > * Architecture Informational Document > > > > - soon, it will be in 30-days public comment phase. > > - Osamu suggests strongly to take out the Section 4.5 Standard > > Interfaces since it is confusing. > > > > - we need to start architectural sketch for every POSIX I/O > > operations as soon as possible. > > > > * F2F meeting > > > > - for further collaboration with SNIA and other groups, we will set > > up a f2f meeting in August. Details are discussed later. > > > > --- > > Osamu Tatebe, Ph.D. Tel: +81-29-861-5844 FAX: +81-29-862-6601 > > Grid Technology Research Center, > > National Institute of Advanced Industrial Science and > > Technology (AIST) > > AIST Tsukuba Central 2, 1-1-1 Umezono, Tsukuba, Ibaraki 3058568 JAPAN > > E-mail: o.tatebe(a)aist.go.jp http://phase.hpcc.jp/people/tatebe/ > > > > >

1 0