September 2005 - ogsa-wg

RE: [ogsa-wg] OGSA WSRF BP 1.0 Editor submission final call
by Djaoui, A (Abdeslem) 24 Sep '05

24 Sep '05

Well, my point is that Discovery is fundamental in OGSA and MUST be (not MAY be) addressed by OGSA, especially now that UDDI is excluded from the base profile. But I agree that the plans and decisions are still to be discussed. Abdeslem ///////////// -----Original Message----- From: Andreas Savva [mailto:andreas.savva@jp.fujitsu.com] Sent: Thursday, September 22, 2005 2:10 PM To: Djaoui, A (Abdeslem) Cc: Hiro Kishimoto; ogsa-wg(a)ggf.org Subject: Re: [ogsa-wg] OGSA WSRF BP 1.0 Editor submission final call I disagree. There are no firm decisions or plans so 'may' is more appropriate at the moment. Andreas Djaoui, A (Abdeslem) wrote: >Hi > >Following from previous email... I see I am too late and a decision has >already been made. So I suggest modifying the sentence >"There may be >additional profiles in the future that will include discovery functions" > >to: > >"Discovery will be covered by future specifications and profiles." > >Abdeslem >////////////// > >-----Original Message----- >From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of >Hiro Kishimoto >Sent: 22 September 2005 09:26 >To: ogsa-wg(a)ggf.org >Subject: [ogsa-wg] OGSA WSRF BP 1.0 Editor submission final call > >Hi all, > >At the today's OGSA-WG call, we discussed BP 1.0 once more and agreed >the following two; > >(1) Exclude UDDI section of WS-I BP 1.1 from OGSA WSRF BP >Now, section 1.2 (page 4 line 114-116) says; > > > This Profile extends the WS-I Basic Profile 1.1 [WS-I BP 1.1]. All >requirements except for section 5 "Service Publication and Discovery" >specified in WS-I BP 1.1 pertain to this Profile. There may be >additional profiles in the future that will include discovery functions. > >Revised really final draft (v043) is on the GridForge. >https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsr >f-basic-profile/en/39 > >(2) Submit OGSA WSRF BP 1.0 (v043) to GGF Editor this Friday >Given that OGSA Basic Security Profiles need more time to complete >(maybe after GGF15), we agreed to submit OGSA WSRF BP 1.0 alone to GGF >Editor this Friday. If you have any farther comments on this draft, >please let us know before EoB Friday (Sept. 23). > >Thanks, > >

4 3

RE: [ogsa-wg] Teleconference minutes - 21 September 2005
by Djaoui, A (Abdeslem) 24 Sep '05

24 Sep '05

Thanks for the clarification David. Putting it another way UDDI can still be used, but a separate claim for conformance should reference WS_I basic profile rather ogsa-wsrf-basic-profile. Abdeslem -----Original Message----- From: David Snelling [mailto:David.Snelling@uk.fujitsu.com] Sent: Friday, September 23, 2005 10:47 AM To: Djaoui, A (Abdeslem) Cc: Andreas Savva; ogsa-wg Subject: Re: [ogsa-wg] Teleconference minutes - 21 September 2005 Abdeslem, The reason for excluding UDDI from the profile is NOT to prohibit its use, but to allow OGSA to use other discovery techniques. The wording in the Basic Profile is quite strong wrt the use of UDDI. On 22 Sep 2005, at 11:13, Djaoui, A (Abdeslem) wrote: >>> - Exclude UDDI portion of WS-I BP 1.1 >>> - There is no specific reference to UDDI in OGSA WSRF BP 1.0 >>> (functionality is out of scope) but it is included by reference >>> to BP 1.1. >>> - Agreed that is should be explicitly excluded from the OGSA WSRF >>> BP. >>> - Discovery is important and should be covered somewhere; perhaps >>> as a separate profile. But we cannot take a position on what the >>> mechanisms are at this point. >>> - Agreed to add a clarification to Hiro's proposed text to address >>> the possible question of where discovery might be covered. > > Discovery is part of the information services capabilities and it will > be covered there. However there are many aspects of discovery. > For web services in general I don't see why we should exclude UDDI. In > general OGSA should not prohibit already accepted and agreed upon > standards. > So the use of UDI should be left as an option. > For Grid resources (that are not web services) OGSA needs additional > mechanisms along the lines of GMA and INFOD. > > Abdeslem > /////////////// > > > > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of > Andreas Savva > Sent: 22 September 2005 01:37 > To: 'ogsa-wg' > Subject: [ogsa-wg] Teleconference minutes - 21 September 2005 > > Minutes attached. > > https://forge.gridforum.org/projects/ogsa-wg/document/minutes > -20050921/e > n > > -- > Andreas Savva > > -- Take care: Dr. David Snelling < David . Snelling . UK . Fujitsu . com > Fujitsu Laboratories of Europe Hayes Park Central Hayes End Road Hayes, Middlesex UB4 8FE +44-208-606-4649 (Office) +44-208-606-4539 (Fax) +44-7768-807526 (Mobile)

2 1

Ad-hoc BOF on Streams at GGF15
by Dave Berry 23 Sep '05

23 Sep '05

All, I apologise for cross-posting so widely; we are trying to reach people who are work with data streams in a Grid setting and there is no obvious single place to post. We are organising an ad-hoc BOF at GGF15 on the subject of data streams in Grid architectures. Our aim is to bring together people working on various aspects of data streams. Our personal goals are to determine how best to fit streams into the OGSA Data architecture but we also see this session as an opportunity for people to share experiences and meet others working in overlapping areas. The BOF will be from 6.00-7.30pm on Monday Oct. 3rd. The first half of the session will see presenters addressing some of the questions below. We will keep the second half of the session for discussion. Issues to consider: - What do we mean by a "data stream"? - Grids have to consider attributes such as security, persistence, and quality of service. Do these raise any particular questions for streams? - What are the important use cases? Are there unusual or non-obvious cases that we need to consider? - What is the natural programming model for streams in a distributed environment? - How do we connect one stream to another? - How do streams fit into a service-oriented architecture? - The OGSA Data Architecture currently has sections on Provisioning, Querying, Replication, Caching, etc. Do these apply to streams as well as static data? Are there any particular aspects of streams that affect any of these sections? We look forward to seeing you there. Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

RE: [ogsa-wg] Teleconference minutes - 21 September 2005
by Djaoui, A (Abdeslem) 23 Sep '05

23 Sep '05

>> - Exclude UDDI portion of WS-I BP 1.1 >> - There is no specific reference to UDDI in OGSA WSRF BP 1.0 >> (functionality is out of scope) but it is included by reference >> to BP 1.1. >> - Agreed that is should be explicitly excluded from the OGSA WSRF >> BP. >> - Discovery is important and should be covered somewhere; perhaps >> as a separate profile. But we cannot take a position on what the >> mechanisms are at this point. >> - Agreed to add a clarification to Hiro's proposed text to address >> the possible question of where discovery might be covered. Discovery is part of the information services capabilities and it will be covered there. However there are many aspects of discovery. For web services in general I don't see why we should exclude UDDI. In general OGSA should not prohibit already accepted and agreed upon standards. So the use of UDI should be left as an option. For Grid resources (that are not web services) OGSA needs additional mechanisms along the lines of GMA and INFOD. Abdeslem /////////////// -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Andreas Savva Sent: 22 September 2005 01:37 To: 'ogsa-wg' Subject: [ogsa-wg] Teleconference minutes - 21 September 2005 Minutes attached. https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050921/e n -- Andreas Savva

2 1

RE: [ogsa-wg] OGSA WSRF BP 1.0 Editor submission final call
by Djaoui, A (Abdeslem) 22 Sep '05

22 Sep '05

Hi Following from previous email... I see I am too late and a decision has already been made. So I suggest modifying the sentence "There may be additional profiles in the future that will include discovery functions" to: "Discovery will be covered by future specifications and profiles." Abdeslem ////////////// -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Hiro Kishimoto Sent: 22 September 2005 09:26 To: ogsa-wg(a)ggf.org Subject: [ogsa-wg] OGSA WSRF BP 1.0 Editor submission final call Hi all, At the today's OGSA-WG call, we discussed BP 1.0 once more and agreed the following two; (1) Exclude UDDI section of WS-I BP 1.1 from OGSA WSRF BP Now, section 1.2 (page 4 line 114-116) says; > This Profile extends the WS-I Basic Profile 1.1 [WS-I BP 1.1]. All requirements except for section 5 "Service Publication and Discovery" specified in WS-I BP 1.1 pertain to this Profile. There may be additional profiles in the future that will include discovery functions. Revised really final draft (v043) is on the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsr f-basic-profile/en/39 (2) Submit OGSA WSRF BP 1.0 (v043) to GGF Editor this Friday Given that OGSA Basic Security Profiles need more time to complete (maybe after GGF15), we agreed to submit OGSA WSRF BP 1.0 alone to GGF Editor this Friday. If you have any farther comments on this draft, please let us know before EoB Friday (Sept. 23). Thanks, -- Hiro Kishimoto

2 1

OGSA WSRF BP 1.0 Editor submission final call
by Hiro Kishimoto 22 Sep '05

22 Sep '05

Hi all, At the today's OGSA-WG call, we discussed BP 1.0 once more and agreed the following two; (1) Exclude UDDI section of WS-I BP 1.1 from OGSA WSRF BP Now, section 1.2 (page 4 line 114-116) says; > This Profile extends the WS-I Basic Profile 1.1 [WS-I BP 1.1]. All requirements except for section 5 "Service Publication and Discovery" specified in WS-I BP 1.1 pertain to this Profile. There may be additional profiles in the future that will include discovery functions. Revised really final draft (v043) is on the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… (2) Submit OGSA WSRF BP 1.0 (v043) to GGF Editor this Friday Given that OGSA Basic Security Profiles need more time to complete (maybe after GGF15), we agreed to submit OGSA WSRF BP 1.0 alone to GGF Editor this Friday. If you have any farther comments on this draft, please let us know before EoB Friday (Sept. 23). Thanks, -- Hiro Kishimoto

1 0

FW: [cddlm] Meeting tomorrow, Wed, 9/14, 6am PST
by Milojicic, Dejan S 21 Sep '05

21 Sep '05

-----Original Message----- From: owner-cddlm-wg(a)ggf.org [mailto:owner-cddlm-wg@ggf.org] On Behalf Of Ayla Debora Dantas de Souza - Projeto Ourgrid Sent: Wednesday, September 14, 2005 4:47 AM To: Milojicic, Dejan S Cc: cddlm-wg(a)ggf.org Subject: Re: [cddlm] Meeting tomorrow, Wed, 9/14, 6am PST Hello, I'm sending here a presentation to guide the demo. The demo will be performed using Glance. Please go to http://ayladantas.glance.net and enter the session key "0511" to join the session that I will open during our meeting. Best regards, Ayla Milojicic, Dejan S wrote: >Hi Team, > >This is a reminder that we have a meeting tomorrow at 6am > >+1 866-639-4732 (toll free while in US) >Code 2362906 (followed by a '#' sign) >+1 574-948-0379 (toll & international) > >The agenda is > >1. demo by UFCG >2. technical discusion (relationship to BES) 3. update on the other >demos at GGF15 4. various > >Thanks, > >Dejan. > > >

1 0

Survey for OGSA-WG F2F meeting back-to-back GGF15
by Hiro Kishimoto 21 Sep '05

21 Sep '05

Hi all, and sorry for the cross-posting again. As you already know, OGSA-WG and fellow WGs are planning to have F2F meeting in Boston, back-to-back with GGF15. The meeting will be held on Thursday (9am-6pm) and Friday (8am-3:30pm) at IBM office in Boston (it is 2.2 miles away from GGF15 venue instead of walking distance). Please keep it in mind that this F2F is workshop style technical discussion. If you want to learn OGSA activities in general, "OGSA Status and direction presentation session" on Oct. 3 (Mon) 11am-12:30pm at Berkely/Clarendon room is the one you should join. In order to obtain admission to the F2F venue, please let us know your plan for attendance by answering the following on-line survey. Deadline is EoB Friday (Sept. 23). http://www.zoomerang.com/survey.zgi?p=WEB224MNGGSZFW Thanks, -- Hiro Kishimoto

1 1

Re: [ogsa-wg] OGSA-WG F2F draft schedule in Boston (Oct. 6&7)
by Manuel Pereira 21 Sep '05

21 Sep '05

Hello all, Would it be possible to discuss OGSA-naming early Thursday? Thank you for considering. Manuel Pereira IBM Almaden Research Center 1-408-927-1935 [T/L 457] mpereira(a)us.ibm.com Monday, September 19, 2005 4:56 AM To: ogsa-wg(a)ggf.org cc: From: Hiro Kishimoto <hiro.kishimoto(a)jp.fujitsu.com> Subject: [ogsa-wg] OGSA-WG F2F draft schedule in Boston (Oct. 6&7) Hi all, Based on the all feedbacks on OGSA-WG F2F meeting which is back-to-back with GGF15, the following is the first-cut draft schedule. Let's discuss at upcoming Monday call. Oct.6 (Thursday) 1. 9-10:30 am: EMS (1) WS-Agreement discussion (GRAAP-WG) 2. 11am-12:30pm: EMS (2) CDDLM & ACS discussion (I) 3. 1:30-3pm: EMS (3) CDDLM & ACS discussion (II) 4. 3:30-5pm: Resource Management, info/data model discussion (Fred & Ellen) 5. 5-6pm: OGSA re-charter draft review Oct. 7 (Friday) 1. 8-9:30am: OGSA-BES session (Andrew) 2. 10-11:30am: OGSA-naming session (Andrew) 3. 12:30-2pm: OGSA-data session (DaveB and Allen) 4. 2-3pm: Wrap-up and next step Thanks, -- Hiro Kishimoto

4 3

Teleconference minutes - 19 September 2005
by Andreas Savva 21 Sep '05

21 Sep '05

Minutes attached. Gridforge: https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050919/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 19 September 2005 ======================================= * Participants Pete Ziu (Northrop Grumman) Jay Unger (IBM) Jem Treadwell (HP) Frank Siebenlist (ANL) Andreas Savva (Fujitsu) Takuya Mori (NEC) Tom Maguire (EMC) Fred Maciel (Hitachi) Allen Luniewski (IBM) Hiro Kishimoto (Fujitsu) Mike Behrens (R2AD, LLC) Apologies: Ellen Stokes Minutes: Andreas Savva * No teleconference minutes approved * F2F Update - Jay has booked two rooms at the IBM facility for Oct. 6 and 7. - A large room that can accomodate about 20 people and smaller room for about 10 people. - OGSA-WG has to provide a list of attendees so that the local security arrangement (badgets) can be completed. The information needed is - Name, Company - The IBM facility is on the other side of the river from the GGF15 site. It is *not* within easy walking distance. It is a short taxi, or bus ride away. - Address: 1 Roger St., Cambridge, MA Actions: - Hiro will do a survey to collect attendee names - Hiro will collect all information and put together an agenda (to include a map) Scheduling requests: - Frank has to leave Thursday afternoon, and has a conflict on Thursday morning (OGSA AUthZ session is scheduled for 11am). The plan is to try an move the AuthZ session to Wednesday. - Takuya also cannot attend the Thursday meeting - A number of other people can only attend Thursday. ** F2F Agenda - EMS is planned for Thursday - The Information Model discussion in planned for Thursday afternoon (Andrea W will be dialling in) - Agreed to add OGSA 1.5 review on Friday. * GGF15 Update Both OGSA sessions are on Monday Oct.3. * OGSA Roadmap 1.0 The Roadmap has been published (assigned number 53). The document is not linked on the GGF site yet. * OGSA & Glossary 1.5 Update ** Status update - Infrastructure: Waiting for an initial draft - EMS: Waiting for an initial draft - Data: Waiting for an initial draft this week - RM: First draft received - Information: Waiting for an initial draft this week - Self-management: No update expected The work is behind schedule. The next target is to put together a draft for review at the F2F after GGF15. Section owners should provide updated drafts by GGF15. Andreas will start sending update emails to the list. ** RM draft review - Minor changes mainly to fix deprecated terminology. - Also added clarification on resource (physical and logical) - And some text on multiple basic profiles - Confirmed that OGSA 1.5 is a maintenance release and should be updated with work already done. So there will probably be no further changes in this section since the work focus will shift to Profiling. ** Infrastructure proposal review - Discussed Jem two approaches on revising this section. Agreed to put more text on the basic profile including the possibility to change the title of the section. ** Glossary review - Added client - Deleted CMM - Added Data Model: Also to add RFC3444 reference - Added Information Model: changed operators to administrators - Agreed to delete OGSI (also delete from Architecture document) - Added profile - Deprecate 'resource model' term * Basic Security profile - Secure channel review Reviewed draft posted by Takuya. - Changed title to use OGSA(tm) - Revised Abstract to make it focused on security - Revised Relationship with other profiles to focus on security - Removed unused targets from the Conformance Targets section - But introduced some namespaces not listed in the table above; to add. - Need to add the 'generic' basic OGSA security claim URI defined in the OGSA BP. Each security profile conformant to OGSA Basic Security has to define two claim uris. - Takuya to follow up on distinction between ssl and tls. - R0301: Takuya sent out an email but there was not a lot of discussion on the list yet. - Hiro commented on the list that the sender will also be a receiver in many cases. As such everyone will have to implement both TLS and MLS. - Explored what this means, whether it is true in general or whether there are some special cases (notification) which could be covered with different text. - Takuya repeated that his intention is to place this requirement for interoperability - Hiro repeated that this seems to place too much on the implementation of the RECEIVER - Discussed how likely it is that both TLS and MLS are going to be implemented by the same service. It was noted that GT implements both. - There are tradeoffs in using TLS or MLS and there are also performance or architectural implications. As such saying that both must be required for interoperability does not seem quite right. - TLS is more common than MLS. - Considered options such as splitting this profile into 2 more focused ones (TLS and MLS) and another one that allows a choice of one or the other. Also considered mandating TLS and recommending MLS. - (It was noted that the initial text allowed the option of one or the other or none.) - Agreed that the decision on what to require should be based on industry requirements as well as the requirements of other projects. - Agreed to try and get some feedback from companies/projects by next week Wed. - Hiro to get some feedback from within FJ. - Since this issue will take time to reach consensus agreed to submit the OGSA Basic Profile next week and not wait for the completion of the security profiles. - Sec.3.5 first sentence needs revision - R0324: Review Basic profile and check what is the requirement on RECEIVER. Perhaps this should be phrased differently than for the SENDER role. - Agreed to move Ian from Author to Contributors. He is listed as an Author only because this document used the WSRF BP doc as a starting point. - Takuya to ask Tom if he wants to be listed as a co-author or as contributor. - Add WS-Addressing and WSRF BP to the table. Takuya to make necessary revisions and also incorporate Jem's edits. * Basic Security profile - Anonymous channel review - Hiro and Andreas pointed out that they expected the Anonymous channel to be much looser than simply changing the MUSTs of the Secure Channel to SHOULDs. - Discussion postponed due to insufficient time. * Next calls - Agreed to move the AuthZ discussion to Sep.28 - Agreed to add the ResourceMetadataDescriptor editor discussion on Wed or Mon agendas. - Next call is EMS

1 0