- ogsa-wg - lists.ogf.org

Proposed agenda for Sept. 28th call
by Hiro Kishimoto 28 Sep '05

28 Sep '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on Sept. 28th Wednesday from 5pm to 7pm (CDT). Dial-in numbers for Wednesday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0928 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 (if available) Agenda bashing 2) OGSA-AuthZ WG joint session (30 min) - Reviewing the changes for the "Use of SAML for OGSI Authorization" and related discussion https://forge.gridforum.org/tracker/download.php?group_id=90&atid=414&file_… - Reviewing the changes for the "Attributes used in OGSI Authorization" and related discussion https://forge.gridforum.org/tracker/download.php?group_id=90&atid=414&file_… - Reviewing the draft charter of the OGSA-Authz-WG https://forge.gridforum.org/projects/ogsa-authz/document/proposed-ogsa-auth… - Fine-grain authorization delegation > From Aug. 15 F2F minutes; >  Questions on relationship between authorization levels and how to bridge between the two. Takuya: native mechanism can provide finer authorization. > • Tom: OGSA delegates authorization to resource’s mechanism? Andrew: Legion had similar scheme. Discussion of technical details. Frank: have to pass to database all the information. Allen: should not preclude this. > • Ravi: possible to abstract it, since we will have to deal with different kinds of resources (telescopes, etc.) later? Tom: question is architectural extensibility. Discussion on existing alternatives. > • Out of time, continue discussion in OGSA-WG teleconferences. 3) Basic Security Profiles review (30 min) Takuya to make necessary revisions, incorporate Jem's edits, and send out to the list before the call. > from Sept. 19 call minutes; > - 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. > - 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 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. 4) CDDLM-WG demo (30 min) > From Sept. 21 call minutes; > Prefer to do it on OGSA call. Dejan will ask Ayla to do demo on > the OGSA call next week (Wed). > - Ayla's slides are a good introduction. Dejan has forwarded a > link to the OGSA list. But note that the presentation is likely > to be updated before the next demo. > - OGSA members are also welcome to join the CDDLM calls and view > the other demos. Ayla's slides (revised version will be available soon); http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/09/msg00085.html 5) GGF15 and F2F meeting update (20 min) GGF15 session schedule http://www.ggf.org/gf/group_schedule/ F2F meeting schedule https://forge.gridforum.org/projects/ogsa-wg/document/OGSA-B2B-GGF15-Schedu… 6) Wrap up AOB <NEXT WEEK> Oct. 3-6: GGF15 Oct. 6-7: F2F meeting -- Hiro Kishimoto

1 1

OGSA discovery study template
by Djaoui, A (Abdeslem) 28 Sep '05

28 Sep '05

I have put together a draft template for a study of existing Discovery systems and design of future OGSA discovery. Comments on the template as well as contributions from existing grid projects are most welcome. Abdeslem PS: David: The Unicore text below covers items 1,2,3 and 9 from the template. I can cut and paste it if you want but a bit more information on the interfaces and the data model would be nice. -----Original Message----- From: David Snelling [mailto:David.Snelling@uk.fujitsu.com] Sent: Wednesday, September 28, 2005 2:33 PM To: Djaoui, A (Abdeslem) Subject: Re: [ogsa-wg] OGSA WSRF BP 1.0 Editor submission final call Abdeslem, On 28 Sep 2005, at 12:13, Djaoui, A ((Abdeslem)) wrote: > Thanks for that Dave, it might be useful if we put a template together > and ask different projects to fill it in. > I will circulate a draft ASAP. Good idea. If you can pick apart the Unicore answer for the sections, it might give you a head start. If you think of sections I haven't implicitly filled in already, let me know. I'll fill them in quickly and you can have a sample as well as a template. > > Abdeslem > > > -----Original Message----- > From: David Snelling [mailto:David.Snelling@uk.fujitsu.com] > Sent: Sat 9/24/2005 12:33 PM > To: Hiro Kishimoto > Cc: Djaoui, A (Abdeslem); Andreas Savva; ogsa-wg(a)ggf.org > Subject: Re: [ogsa-wg] OGSA WSRF BP 1.0 Editor submission final call > > Abdeslem, > > To get you started: > > Registry services in Production Unicore are integrated (the Grid fabric > populates it rather than allowing registration). The registry of > available resources, software, system load, and other services (such as > brokers) are may available to clients on request. Most of this > information is static and clients may choose to cache it. Most clients > today cache it for the time they run and then refresh it when the start > up. The Intel client allows manual refresh. Each registry is maintained > by the sites, i.e. there is no central regisrty. However, the > University of Manchester's Resource Broker I believe caches information > from several sites to facilitate "Candidate Set Generation". Access to > all this information is subject to authorization, e.g. non-public > registry. > > There has been some concern that the registry is an "all or nothing" > implementation without a search facility causes an excessive load on > server to client communication, but we have never had feedback from > this issue. > > There is a separate mechanism for registering jobs. By default, users > see their own root jobs at the site where they were consigned. Sub-jobs > at each site are only visible optionally - not supported by most > clients today. There is a admin role that allows administrators to see > jobs at a remote site. > > In the prototype Unicore/GS, built on WSRF, the registry is still in > the planning stages. It is expected that all the above information, > which is already available as Resource Properties of the "Atomic > Services" (the Unicore dual to GRAM, RFT, etc.) will be available also > through a Service Group based registry in the near term. > > We have not studied the possibility of a UDDI registry since the OGSI > days. There may be fresh possibilities there. > > On 24 Sep 2005, at 2:35, Hiro Kishimoto wrote: > >> Hi Abdeslem, >> >> As a first step of defining Discovery and Registry in the Grid, can >> you champion a study of existing grip projects; EGEE, OMII, Globus, >> UNICORE, TeraGrid, etc. >> >> Thanks, >> ---- >> Hiro Kishimoto >> >> Andreas Savva wrote: >>> In OGSA, yes. But the WSRF BP is not the place to make such >>> statements. >>> The Roadmap is, so if there is a specific plan it should be added >>> there. >>> Djaoui, A (Abdeslem) wrote: >>>> 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, >>>>> >>>>> >>>>> >>>> >>>> >> >> > -- > > 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) > > > -- 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)

1 0

RE: [ogsa-wg] Information model profile doc for OGSA -- initial thoughts
by Andrea Westerinen (andreaw) 28 Sep '05

28 Sep '05

Hiro, I can take the action to draw up the BES profile for the tool that we have developed (available from www.cimwizard.com and fully functional on Eclipse). That tool can then output documentation as well :-). I like your suggestion and its simplicity. Andrea PS. Note that the work on cimwizard.com is only binaries. We have not yet finished the paperwork to release the open source. > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Hiro Kishimoto > Sent: Monday, September 26, 2005 1:24 AM > To: ogsa-wg(a)ggf.org > Subject: Re: [ogsa-wg] Information model profile doc for OGSA > -- initial thoughts > > Hi Fred, > > My comments in line <HK>. > ---- > Hiro Kishimoto > > Fred Maciel wrote: > > Hi all, > > > > I've been thinking of our guidance document on CIM profiles > and how to > > represent them on the OGSA spec. I don't have any answers, but at > > least I got to the point where I have a lot of questions... :-) I'm > > hoping to have your opinion on them in Monday's > teleconference. So, let's start. > > > > First of all, DMTF's document on how to write a profile has > started a > > one-month review inside the DMTF, so all DMTF members should have > > access to it. The document is right on the top of the > document review page: > > http://www.dmtf.org/members/review/ . It's still DMTF > confidential so > > I can't post it here (sorry), but I'm taking into > consideration since > > it should be publicly available in a month as a preliminary > document. > > Meanwhile, the first slides of Andrea's presentation in the last > > face-to-face (see > > > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/08/msg00075.ht > > ml > > ) are a good summary of the sections and contents in such a profile. > > > > The DMTF document gives all the details on how to specify a > profile, > > includes a lot of experience (which allows us to avoid some > pitfalls) > > and saves us a lot of time. However, I think that it's an > overkill for > > individual OGSA specs (*), especially the ones that cover > only one or > > two classes. > > > > So what I'm thinking for now is two levels: > > (1) We create an information model profile per OGSA area (Execution > > Management, Data, etc.), or, a profile for OGSA with > sub-profiles for > > each area. These can be part of an OGSA profile (i.e., some of the > > OGSA profiles will include the corresponding information > model profile). > > These profiles act as integration points between the pieces of the > > information models that each individual OGSA spec uses. The > definition > > of these information model profiles follows the guidelines > of the DMTF > > profile spec. > > <HK> > As I mentioned at the Aug. F2F, I would like to have simple > management profile document on BES container as an example > within OGSA-WG. > > Given Fred, Andrea, and Ellen has done CIM/JSDL/GLUE > comparison already. > Is it possible to have very early profile draft at F2F meeting? > Since DMTF's usage guide is not publically available, small > sub team, who can access this document, draw up profile draft > and full OGSA-WG reviews this draft. > > Based on the synopsis definition on Andrea's slides, this > profile is something like; > > - Profile name: BES Container Profile > - Version: 1.0 > - Organization: GGF > - CIM Schema: 2.9.0 (or 2.10.0?) > - One paragraph summary: > The BES Container Profile defines management capability of > BES containers. > > Mandatory CIM element: System, ComputerSystem, OperatingSystem, > CPUArchitecture > Optional CIM element: NetworkBandwidth, DiskSpace, FileSystem </HK> > > > (2) Individual specs show the information models they use in a > > lightweight way. The OGSA document on how to write an information > > model profile (we need a title and a nickname for it. > Suggestions?) is > > a guideline on how to specify the information model on these specs. > > > > Notice that Cisco's modeling tool (about to become > open-source) will > > be useful for both (1) and (2) above. It can even change > the balance > > of things above in subtle ways depending on how (and how much) it > > makes the creation of a profile easier. > > > > That's all for now. Opinions please. > > > > Regards, > > > > Fred Maciel > > Hitachi America R&D > > > > (*) By "individual OGSA specs" I mean specs like ByteIO, OGSA-BES, > > etc., not the roadmap, profile definition, guideline specs, > the OGSA > > spec itself, etc. > > > > > > >

2 1

CDDLM - ACS - EMS Interactions
by Stuart Schaefer 28 Sep '05

28 Sep '05

Sorry for the time it took to build all of this. I have built three scenarios to discuss the possible interactions between CDDLM, ACS and the remainder of the core. Each scenario has two assets, a sequence diagram and a block diagram of the OGSA architecture adapted from the base EMS diagram. Additionally, I have attached the CDDLM/ACS interaction proposal created by the ACS team at GGF 14. In the first scenario, CDDLM draws directly from the repository as shown in the ACS diagrams and the model used in the original EMS Scenario #3. In the second scenario, CDDLM uses OGSA Data Services as a conduit to access the ACS repository (knowing that the data services architecture is in progress). In the final scenario, I propose splitting CDDLM from knowledge of the repository by using the OGSA services as intermediary. The CDDLM architecture was designed to allow remote files to be added to it for local deployments. It was not originally presumed that we would be drawing from a remote repository using an undefined protocol. See everyone tonight, Stuart

1 0

RE: [ogsa-wg] Information services for OGSA 1.5
by Djaoui, A (Abdeslem) 28 Sep '05

28 Sep '05

SEE INLINED </AD> COMMENTS. Abdeslem -----Original Message----- From: Michael Behrens [mailto:behrens@r2ad.com] Sent: Sun 9/25/2005 2:26 AM To: Djaoui, A (Abdeslem) Cc: ogsa-wg(a)ggf.org Subject: Re: [ogsa-wg] Information services for OGSA 1.5 I've read the additions to the document and I like the additional alternative discovery mechanism which uses multicast. Perhaps other mechanisms in a grid fabric might also use multicast to convey information. <AD>IN THEORY YES </AD> What is your opinion on this possibility: When a user submits a job request (via a portal for instance), the job manager would convey the request to other services which trigger the (potential) instantiation of new services. Any new service addresses are returned as part of the instantian process and are conveyed directly to the information services and others. Since the locations (EPRs or WS-Names) of the services are passed around in an event driven model, would it obviated the need for searching (discovery)? <AD>WHERE IS MULTICAST USED HERE, IT CERTAINLY IS APPROPRIATE FOR SERVICES TO ANNOUNCE THEMSELVES WHEN THEY ARE INSTANTIATED. AN INFORMATION SERVICE CAN "LISTEN" TO SUCH ANNOUCEMENTS AND REGISTER SUCH SERVICES DYNAMICALLY. </AD> I thought the naming section was important. Was it replaced by something else or moved elsewhere? <AD> MOVED - SEE ANDREAS MESSAGE </AD> Djaoui, A (Abdeslem) wrote: >Hi Andreas > >Please find revised section on Information services for OGSA 1.5. I have removed Naming, added a small paragraph on INFOD and one on dynamic discovery and made some small edits. > >Please read and either accept the changes or comment by Email as it I may not be able to make the normal call. > >Thanks > >Abdeslem > > -- Michael Behrens R2AD, LLC (571) 594-3008 (cell) *new* (703) 714-0442 (land)

1 0

RE: [ogsa-wg] Revised F2F meeting schedule
by Djaoui, A (Abdeslem) 28 Sep '05

28 Sep '05

Hi Hiro it might be better to swap ogsa-wg recharter and agsa 1.5 review. What do you think? Abdeslem -----Original Message----- From: owner-ogsa-wg(a)ggf.org on behalf of Hiro Kishimoto Sent: Tue 9/27/2005 4:06 AM To: ogsa-wg(a)ggf.org Subject: [ogsa-wg] Revised F2F meeting schedule Hi all, Per OGSA-naming WG co-chairs request, we agree to switch EMS (3) session and OGSA-naming on Thursday. I hope it is ok for everyone. The latest Thursday schedule is; 8-9:30am EMS (1) WS-Agreement discussion 9:30am-11am EMS (2) CDDLM & ACS discussion (I) 11am-12:30pm EMS (3) CDDLM & ACS discussion (II) 12:30-1:30pm Lunch 1:30-3pm OGSA-naming session 3:30-5pm Resource Management, information/data model discussion 5-6pm OGSA-WG re-charter draft review The schedule is on the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/OGSA-B2B-GGF15-Schedu… If you've already answered the on-line survey but you name is not on the attendee list, please let me know. Thanks, -- Hiro Kishimoto

1 0

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

28 Sep '05

Thanks for that Dave, it might be useful if we put a template together and ask different projects to fill it in. I will circulate a draft ASAP. Abdeslem -----Original Message----- From: David Snelling [mailto:David.Snelling@uk.fujitsu.com] Sent: Sat 9/24/2005 12:33 PM To: Hiro Kishimoto Cc: Djaoui, A (Abdeslem); Andreas Savva; ogsa-wg(a)ggf.org Subject: Re: [ogsa-wg] OGSA WSRF BP 1.0 Editor submission final call Abdeslem, To get you started: Registry services in Production Unicore are integrated (the Grid fabric populates it rather than allowing registration). The registry of available resources, software, system load, and other services (such as brokers) are may available to clients on request. Most of this information is static and clients may choose to cache it. Most clients today cache it for the time they run and then refresh it when the start up. The Intel client allows manual refresh. Each registry is maintained by the sites, i.e. there is no central regisrty. However, the University of Manchester's Resource Broker I believe caches information from several sites to facilitate "Candidate Set Generation". Access to all this information is subject to authorization, e.g. non-public registry. There has been some concern that the registry is an "all or nothing" implementation without a search facility causes an excessive load on server to client communication, but we have never had feedback from this issue. There is a separate mechanism for registering jobs. By default, users see their own root jobs at the site where they were consigned. Sub-jobs at each site are only visible optionally - not supported by most clients today. There is a admin role that allows administrators to see jobs at a remote site. In the prototype Unicore/GS, built on WSRF, the registry is still in the planning stages. It is expected that all the above information, which is already available as Resource Properties of the "Atomic Services" (the Unicore dual to GRAM, RFT, etc.) will be available also through a Service Group based registry in the near term. We have not studied the possibility of a UDDI registry since the OGSI days. There may be fresh possibilities there. On 24 Sep 2005, at 2:35, Hiro Kishimoto wrote: > Hi Abdeslem, > > As a first step of defining Discovery and Registry in the Grid, can > you champion a study of existing grip projects; EGEE, OMII, Globus, > UNICORE, TeraGrid, etc. > > Thanks, > ---- > Hiro Kishimoto > > Andreas Savva wrote: >> In OGSA, yes. But the WSRF BP is not the place to make such >> statements. >> The Roadmap is, so if there is a specific plan it should be added >> there. >> Djaoui, A (Abdeslem) wrote: >>> 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, >>>> >>>> >>>> >>> >>> > > -- 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)

1 0

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

28 Sep '05

Hi Hiro I would like to, but we would need to identify people who are willing to contribute to this initiative. I can of course do EGEE and make some guesses at some other projects, but it would be better if we have some input from the projects themselves. Any name suggestions? Abdeslem -----Original Message----- From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com] Sent: Sat 9/24/2005 2:35 AM To: Djaoui, A (Abdeslem) Cc: Andreas Savva; ogsa-wg(a)ggf.org Subject: Re: [ogsa-wg] OGSA WSRF BP 1.0 Editor submission final call Hi Abdeslem, As a first step of defining Discovery and Registry in the Grid, can you champion a study of existing grip projects; EGEE, OMII, Globus, UNICORE, TeraGrid, etc. Thanks, ---- Hiro Kishimoto Andreas Savva wrote: > In OGSA, yes. But the WSRF BP is not the place to make such statements. > The Roadmap is, so if there is a specific plan it should be added there. > > Djaoui, A (Abdeslem) wrote: > > >>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, >>> >>> >>> >>> >> >> >> > > > >

1 0

Teleconference minutes - 26 September 2005
by Andreas Savva 27 Sep '05

27 Sep '05

Minutes attached. Gridforge url: https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050926/en/1 (Thanks to Jem for taking minutes for the first part of the call.) -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 26 September 2005 ======================================= * Participants Andrew Grimshaw (UVa) Fred Maciel (Hitachi) Tom Maguire (EMC) Hiro Kishimoto (Fujitsu) Manuel Pereira (IBM) Andreas Savva (Fujitsu) Dave Snelling (Fujitsu) Latha Srinivasan (HP) Ellen Stokes (IBM) Jem Treadwell (HP) Jay Unger (IBM) Minutes: Jem Treadwell, Andreas Savva * Minutes approval Sep. 19 and Sep. 21 minutes approved with no changes. * GGF15 update - Two sessions at GGF15 on Monday - no comments. * F2F Update - Facilities update by Jay: - A projector will be available. - Not sure if WiFi will be available. - Andrew cannot make it to the F2F for 11am on Thursday. So Hiro will swap OGSA-Naming and EMS/CDDLM/ACS sessions and re-send the schedule. * WS-MetaData discussion From the early days (OGSI), the properties of service data, e.g. read-only, write-only, static, freshness were part of the specs... WS-RF moved metadata to a separate document. The initial pass included putting metadata on operations, and other capabilities. WSDM thought this would be useful functionality. WSRF-TC has recently lost the editor of this document. A call for volunteers has not yielded a replacement yet. At the moment looking for someone from OGSA-WG or the Grid world to do it in the WSRF-TC. An alternative is for OGSA-WG to take it on. The WS-MetaData spec is composable with any other XML specification, not just WS-RP. So it might have wider application. Current document status: the draft has a lot of complexity; some ideas of how it could be simplified exist. And the first job would be to simplify it. It is not a big specification. Dave S encouraged people to consider taking th job of Editor of this document. Both Tom Maguire and Dave Snelling have indicated willingness to help with this document but they cannot take on the role of Editor. * Information Modelling discussion - Fred sent out a proposal to the list. - Following emails from Hiro and Ellen (and a private discussion with Ellen) this proposal is withdrawn in favor of Hiro's and Ellen's proposals. - Ellen's proposal calls for two deliverables: 1. A set of profiles - This is purely technical work. For example, - Identify a number of profiles that cover the EMS components and also define an overall profile for EMS. - The BES container model could be a good first point - A plan for the overall work would also be needed. - THe list of these profiles could be ready by the F2F. But Ellen and Fred do not think that they can go to the point of doing an outline for a specific profile by that time. 2. A document describing the "rules of engagement" for doing profiles - This could end up being an informational document. - Contents: How the work relates to information models; how it relates to CIM (and that it does not mean the whole CIM has to be used), that extensions can be done and so on. Also what the outline of such profiles would look like; what the GGF specific portion of such documents would be and so on. - The RM design team will be responsible for doing this document---at least to the point of a first draft. - It should (and needs to) be done fairly quickly. A strawman could be ready for review at the F2F. - And at the EMS session work on listing the set of proposed profiles. But the actual work on doing these profiles would start after the F2F. - In contrast Hiro placed more importance on having a worked example profile ready by the F2F. The BES container is something tractable, on which some work has been done already and could be ready (in first draft form) by the F2F. - Hiro volunteered to start working on the container profile. - Ellen and Fred are unlikely to have any time before. They will help as much as possible but since they don't expect to start working on the "Rules of engagement" before GGF15, it is unlikely to be able to help a lot before the F2F. - Andrea W's tool was mentioned. Noone on the call has actually tried it out yet. So it is not clear how useful it would be at this point. In any case content is more important than trying out tools at this moment. - Ellen to ask Andrea about the tool. - Fred outlined an agenda for the Information Modelling session at the F2F. - Review of guidelines document - Discussion of which profiles needed for EMS - Container, scheduling, etc. - Fred to send a formal agenda to Hiro. * Other news - The Roadmap is now published on GGF site - The Profile Definition is now in public comment - The WSRF BP is in GFSG review

1 0

Revised F2F meeting schedule
by Hiro Kishimoto 27 Sep '05

27 Sep '05

Hi all, Per OGSA-naming WG co-chairs request, we agree to switch EMS (3) session and OGSA-naming on Thursday. I hope it is ok for everyone. The latest Thursday schedule is; 8-9:30am EMS (1) WS-Agreement discussion 9:30am-11am EMS (2) CDDLM & ACS discussion (I) 11am-12:30pm EMS (3) CDDLM & ACS discussion (II) 12:30-1:30pm Lunch 1:30-3pm OGSA-naming session 3:30-5pm Resource Management, information/data model discussion 5-6pm OGSA-WG re-charter draft review The schedule is on the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/OGSA-B2B-GGF15-Schedu… If you've already answered the on-line survey but you name is not on the attendee list, please let me know. Thanks, -- Hiro Kishimoto

1 0