- ogsa-wg - lists.ogf.org

[ogsa-wg | Roadmap - 1569] Text for section 8 from OMII
by Sourceforge Tracker Monitor 24 Jul '05

24 Jul '05

A new artifact has been added: 1569 Submitted by: Steven Newhouse Submitted date: 2005-07-24 20:21:22 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=789&aid=1569&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=789&aid=1569&group_id…) Summary: Text for section 8 from OMII Project: Open Grid Services Architecture Tracker: Roadmap Artifact ID: 1569 Category: <None> Group: <None> Status: Open Priority: - Last Modified By: Steven Newhouse Last Modified: 2005-07-24 20:21:22 Submitted By: Steven Newhouse Submit Date: 2005-07-24 20:21:22 Assigned To: &lt;None&gt; File(s): <None> Description: The Open Middleware Infrastructure Institute (OMII), located at the University of Southampton, is funded by the UK e-Science Core programme. Its open source distribution of web services comprises services that are implementing GGF and OGSA based standards - such as DAIS within the OGSA-DAI project, and JSDL and BES within the GridSAM projects - both funded through OMII's managed programme. View the Roadmap : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

RM -- No teleconference on July 26
by Fred Maciel 23 Jul '05

23 Jul '05

Hi again, No Resource Management design team teleconference on July 26. Regards, Fred Maciel Hitachi America R&D

1 0

Regrets -- week of July 25-29
by Fred Maciel 23 Jul '05

23 Jul '05

Hi, On the week of July 25-29 I'll be in the SNIA/DMTF Technical Symposium. Regards, Fred Maciel Hitachi America R&D

1 0

RM teleconference minutes -- July 19
by Fred Maciel 22 Jul '05

22 Jul '05

Hi, Here are the teleconference minutes. Regards, Fred Maciel.

1 0

Proposed agenda for July 20th call
by Hiro Kishimoto 21 Jul '05

21 Jul '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on July 20th 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: 0720 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval http://tinyurl.com/5fxfd/minutes-20050718/en/1 Agenda bashing 2) Aug F2F meeting update (20 min) Resource Model Discussion 3) OGSA WSRF BP 1.0 review (60 min) Security section review Andreas will upload revised draft before the call. 4) OGSA Next step and telecon schedule (30 min) Hiro will send out revised proposal before the call. 5) Wrap up AOB July 25th (Mon) Resource Modeling July 17th (Wed) TBD -- Hiro Kishimoto

1 2

Another security call
by Hiro Kishimoto 21 Jul '05

21 Jul '05

Tom's email bounced. -- Hiro Kishimoto Subject: Re: OGSA Next step and telecon schedule proposal (Re: [ogsa-wg] Proposed agenda for July 20th call) From: <tom.maguire(a)suscom.net> Date: Wed, 20 Jul 2005 17:04:00 -0400 call and discussion on wsa header signing and x509 certs has not taken place yet. Not prepared to discuss. Stuck in o'hare. Will not be on call. Sorry for late notice

1 0

RE: OGSA Next step and telecon schedul proposal (Re: [ogsa-wg] Proposed agenda for July 20th call)
by Djaoui, A (Abdeslem) 20 Jul '05

20 Jul '05

Hiro The direction of the information services will become clearer as work on InfoD stabilizes. I certainly would like to see more participation (eventually!) on this topics, but for now it is tightly coupled with InfoD. Abdeslem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org]On Behalf Of Hiro Kishimoto Sent: Wednesday, July 20, 2005 3:54 PM To: ogsa-wg(a)ggf.org Subject: OGSA Next step and telecon schedul proposal (Re: [ogsa-wg] Proposed agenda for July 20th call) Hi all, > 4) OGSA Next step and telecon schedule (30 min) > Hiro will send out revised proposal before the call. Attached is revised next step proposal. Please have a look. ---- Hiro Kishimoto Hiro Kishimoto wrote: > Hi all, > > The following is a proposed agenda for OGSA-WG telecon on July 20th > 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: 0720 > See more explanation: > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html > > 1) Early discussion (20 min) > Note taker assignment > Roll call > Telecon minutes approval > http://tinyurl.com/5fxfd/minutes-20050718/en/1 > Agenda bashing > > 2) Aug F2F meeting update (20 min) > Resource Model Discussion > > 3) OGSA WSRF BP 1.0 review (60 min) > Security section review > Andreas will upload revised draft before the call. > > 4) OGSA Next step and telecon schedule (30 min) > Hiro will send out revised proposal before the call. > > 5) Wrap up > AOB > > July 25th (Mon) Resource Modeling > July 17th (Wed) TBD

1 0

Comments on OGSA WSRF BP 1.0 draft 25 (specifically security)
by humphrey＠cs.virginia.edu 20 Jul '05

20 Jul '05

I assume that this document has not entered public comment, so I'll post my comments here regarding security. I'm afraid that these are largely the SAME comments that I've made before. Here are my specific concerns... The security section (section 8.1) implies that *EVERY* SOAP message must be either (1) over TLS or (2) "SOAP Message security with XML signature and/or XML Encryption". If you truly mean this (implied by "R0811"), this is overly restrictive and makes no sense (there does not exist *ANY* message that can justifiably be sent between services/clients that need not incur the overhead of crypto?). However, it's not clear if you really mean this ("R0819", "R0820", "R0821", "R0822", "R0823" seem to imply otherwise)... so, what exactly is the intention here? In general, section 8.1.2 is too restrictive -- "mutual-authenticated WS- Communication will be required" is overly restrictive. And this section includes this statement: "The Profile mandates that there be no anonymous communication. To ensure interoperability, only X.509 certificate-based authentication is permitted by the Profile.") So, this latter part in particular says that there is *NO PLACE* for password authentication in OGSA. (I also believe that you have now outlawed MyProxy, right?) Am I reading something incorrectly? -- Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

8 8

WSRF BP 1.0 v29 uploaded
by Andreas Savva 20 Jul '05

20 Jul '05

WSRF BP v29 uploaded. This is for review in the call tomorrow. (v28 was uploaded after the last call by Tom.) Hiro and I accepted a number of old, already reviewed changes. (This 'uncovered' a number of comments that should be reviewed tomorrow.) We also made some minor edits. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… or http://tinyurl.com/5fxfd/draft-ggf-ogsa-wsrf-basic-profile/en/24 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

Teleconference minutes - 17 July 2005
by Andreas Savva 19 Jul '05

19 Jul '05

Minutes attached. - August F2F update - WSRF BP 1.0 review - Resource modelling discussion - RNS specification review https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050718/en/1 or http://tinyurl.com/5fxfd/minutes-20050718/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 17 July 2005 ================================== * Participants Pete Ziu (Northrop Grumman) Jay Unger (IBM) Osamu Tatebe (AIST) Latha Srinivasan (HP) Dave Snelling (Fujitsu) Andreas Savva (Fujitsu) Manuel Pereira (IBM) Steven Newhouse (OMII) Takuya Mori (NEC) Mark Morgan (UVa) Tom Maguire (IBM) Hiro Kishimoto (Fujitsu) Andrew Grimshaw (UVa) Dave Berry (NeSC) Mike Behrens (R2AD, LLC) * Minutes approval Minutes approved with minor changes. Proposed changes described in http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/07/msg00056.html * August F2F updates - Andrew is leaving Thursday - Proposal to start Naming early and finish at 11am on Thursday; or move the Naming session to Wednesday - Agreed to move Naming session to Wednesday - Hiro and Mark have to leave before Friday noon - Agreed to start Friday early and if possible finish the session by 11am; continue without them, if necessary. - ByteIO moved to Tuesday - Proposal to allocate time during the F2F for resource modelling - Hiro to allocate three hours on Wednesday afternoon in the OGSA session. - WSDM conflict update: Heather Kreger has agreed to move the WSDM meeting to another week. - Hiro has contacted Allen L.: Prefers Data session later in the week. - Data moved to Thursday - Dave B wants to have a discussion on data staging as a separate job rather than as part of a single job. A number of JSDL-WG members will be at the F2F so having a discussion as part of the Data session is a possibility. * WSRF BP 1.0 review - Tom has uploaded v27 on gridforge Action: Tom continues to have the pen and will upload a new draft after the call. ** Canonizalization proposal - There are several (three) canonicalization proposals but many do not define a serialization. The proposed addition (below) does. - l.336-340 modified to use the OASIS specification "Schema Centric XML Canonicalization." - Also softened language (MUST to SHOULD) because it is not clear what the implementation status of this specification is. - This specification is a 'Committee Specification.' In other words, the specification has been approved by the TC as a CD, submitted to public comment (and only minor changes were required to address comments). But it has not gone through a final approval vote. In terms of the Profile Definition classification it is at least "Evolving Institutional." Action: Tom will check to see the implementation status. (Contact the IBM co-author of this proposal.) Action: Takuya will review this addition. He will also check the implementation status (within NEC). Agreed to delete comments against this proposal. ** Security Discussed security issues raised on the list. Action: Tom to arrange a separate teleconf to discuss the security issues below. Invite Marty, Dave S, Mark McKeown, Frank, Takuya. *** Signed endpoint references Issue raised on the list by Mark McKeown http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/07/msg00049.html - Presumably transport level security would not require this. - For Message level security, need to define what to sign; probably everything including reference properties. Action: Takuya will follow up with Frank on whether it should be mandated. *** Mandating transport or message security The profile as it stand does not allow non-encrypted messages or channels. There are cases when one would not want either, e.g., large data transfers that may cause performance degradation. Also depending on the environment it might be acceptable to not encrypt (e.g., operating within enterprise (behind firewall)). (If corruption is the issue then signatures and not encryption is appropriate.) Consensus on softening the requirement: - Change l.466 'requires' to 'recommends' - And also change transport level compliance statements R0811-14 from MUST to SHOULD. *** Mutual authentication - Discussed and agreed on last week. - The non-normative text is out of sync with the normative text. Agreed to change l.489 to 'recommended.' Action: Takuya to reply to Marty's email. *** User name/password authentication There is no statement about name/password authentication in the WSRF BP. It is allowed by the WS-I Security BP (token authentication). l.491 is problematical, however. The phrasing explicitly allows only x.509. But this is a non-normative statement and no normative statements back this up. Action: Takuya will look into this issue and report back to the group. * Resource modelling discussion [Timeboxed to 15 minutes.] The BES has put resource modelling out of scope. But it looks more and more that OGSA should face this issue sooner rather than later. And avoid or minimize rework later on There was a presentation about CIM/JSDL mapping at GGF14. This is a good starting point and OGSA-WG should discuss whether CIM is the solution for OGSA. The main questions are - what is a reasonable model for OGSA (for Grid); and - is CIM it Are there other candidates besides CIM? - It was noted that WSDM also seems to be turning towards CIM. - GLUE is an option but there is work to provide a CIM mapping. The rendering and semantics distinction/definition is discussed in GFD-I.45. Available at http://www.ggf.org/documents/GFD.45.pdf There is also the WS-CIM work. The group should check how far that work satisfies OGSA requirements. Initially a limited experiment might be in order. For example apply CIM to BES/JSDL. But BES-WG cannot take this work on, and RSS-WG also is moving to put it out of scope. One related issue is how to 'sell' CIM to the wider Grid community. It was proposed to put together a concrete proposal in a document format so as to have something concrete to discuss by the F2F. The RM call agenda (Tuesday) is set to discuss this topic. And continue this discussion on another OGSA call (possibly next Monday). * RNS specification review Draft: https://forge.gridforum.org/projects/gfs-wg/document/RNS-Proposed_Final_Dra… Manuel gave an overview of the specification. The referenced draft is being prepared for submission. - Some grid file system parts (e.g. one of the appendices) will be removed for final submission. - Also to remove sentence in Sec.1.2.1 about manipulation via WSRF. It gives the wrong impression. Andrew had a number of comments and he will post them on the OGSA and GFS lists. There are two ways to proceed: - GFS submits the document to GGF Editor soon and there is followup discussion as part of the public comment period; or - GFS discusses with OGSA, adjusts the RNS specification if necessary and then submits. Action: Manuel will take this proposal back to the GFS group and will let OGSA know in a subsequent email. * Next call (Wednesday) - Next steps discussion - Teleconf schedule - WSRF BP 1.0 review

1 0

Teleconference minutes - 13 July 2005
by Andreas Savva 19 Jul '05

19 Jul '05

Minutes attached. - August F2F update (fixed: Aug 15-19, @Sunnyvale) - OGSA WSRF BP 1.0 Security section review - Other business https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050713/en/1 or http://tinyurl.com/5fxfd/minutes-20050713/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconfence - 13 July 2005 ================================ * Participants Pete Ziu (Northrop Grumman) Jay Unger (IBM) Andreas Savva (Fujitsu) Takuya Mori (NEC) Mark Morgan (UVa) Tom Maguire (IBM) Fred Maciel (Hitachi) Hiro Kishimoto (Fujitsu) Mike Behrens (R2AD, LLC) Apologies: Andrew Grimshaw Minutes: Andreas Savva * July 11 Minutes approved with no changes * August F2F meeting update ** Venue - Andreas is following up with the (Fujitsu) Sunnyvale arrangements. - Jay is contacting Almaden ** Schedule - ByteIO requested an earlier slot (not Friday) - Mark has to leave early and Neil cannot make Friday - Considered and rejected moving Naming to Friday - It is likely that ByteIO will not need a half-a-day slot. - Agreed that having a regular session on Friday is not a good idea. Friday morning should be reserved for wrap up. - And that the sessions could start earlier on other days to accomodate the extra session. - Agreed to start early on Thursday and put ByteIO in that slot. - WSDM conflict - Jay/Fred could not contact Heather yet. - Not sure about Allen L's schedule. (Affects Data session) * OGSA WSRF BP 1.0 Security section review Based on draft sent out by Takuya http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/07/msg00037.html - Sec.8.1. Should use the same style as the other sections. - Add a statement that there are no extensibility points beyond those in WS-I BSP. (Takuya) - l.451: References should be in the same style as the rest of the document. Delete. (Takuya) - Also, if the TLS and HTTP-TLS references are not cited they should be deleted (Confirmed they can be cited against other text.) (Takuya) - l.454: Text added in response to tracker 1320 (require one or the other). Change is ok. - Sec.8.1.2: On mandating the use of mutual authentication - Latha's comment needs followup. Since Latha is not on the call, follow up by email and finalize at next Monday's call. - Agreed that this requirement is very restrictive. - This was discussed at the Security session at GGF14. The reason given for mandating it, is that the profile addresses inter-organization (server to server) interactions and that the expectation is that those interactions must be secured. If operating in some special environment it might be possible to do things differently but then interoperability is not the main concern.(?) - The concern with mandating this requirement is that it sets too high a bar, especially for existing middleware. Very few, if any, systems do this at the moment. (The mechanism of acquiring and validating credentials is the problem not their usage afterwards.) It seems overly restrictive and many people might not be able to comply to this profile because of this. - The consensus on the call was therefore to soften this requirement. Specifically to change the requirement from MUST to SHOULD (or possibly RECOMMENDS; semantically equivalent to SHOULD but slightly different nuance). - Sec.8.1.3: Changes are ok. - [Comment JT8]: Clarified that the introductory paragraph is informative text and should not use normative terminology. Only the compliance statements should do so. - There are a couple of places where this is not observed and they should be checked and changed during for the final review. (Hiro) - Sec.8.1.4: Add a normative reference to XML-Signature (Takuya) - And also rebuild the table at the back (Hiro) - Sec.8.1.5: Changes are ok. - Sec.8.1.6: Re-write the first paragraph in the same style as the other sections. (Takuya) - R0824: Appendix A reference is wrong and should be fixed. (Takuya) - Sec.8.1.7: SAML Token Profile 1.0 reference is needed. Also by adding this reference an earlier section that discusses the relation of this profile to other profiles has to be updated (Takuya) - Otherwise ok. - Appendix E - l.936: The definition of EndpointKeyInfo should also be added to the normative schema in Appendix D. (Takuya) - Editing Actions: 1. Takuya to update the document and put on gridforge as draft 25 2. Hiro to update table 3. If anyone wants the pen talk to Hiro after that. * Other Business ** Roadmap document - Public comment ends July 29 - No comments received yet - All group members should solicit comments for this document ** Resource modelling - Confirmed that Resource modeling is on the agenda of the Monday call. - Jay, Mark, Andrew had a call to discuss the issue. They will also discuss it in the BES call. ** Agenda for Monday call 1. Final call on BP 2. Resource modelling 3. RNS specification review

2 2

where does resource modeling fits in?
by Hiro Kishimoto 19 Jul '05

19 Jul '05

Steven's email bounced. -- Hiro Kishimoto Date: Mon, 18 Jul 2005 22:58:27 +0100 From: Steven Newhouse <s.newhouse(a)omii.ac.uk> Subject: Re: [ogsa-wg] OGSA RM teleconference -- where does resource modeling fits in? >> First of all, sorry for the cross-posting -- this subject involves all >> three WGs. Well this is bound to bounce from one of these lists... I'm not going to sub scribe just for this thread... >> Since GGF14 there have been a lot of discussions on where resource >> modeling fits -- BES considered it out of scope but Andrew thinks it's not >> totally out; RSS is discussing whether it's in scope; and this was discussed >> in the OGSA-WG also. So, let's discuss this in the Resource Modeling design >> team teleconference (which is, in fact, the place to discuss this). I feel this has been discussed to exhaustion - at the F2F, GGF 14 & at last week's calls. While I would not object revisiting this from a BES perspective at somepoint in the future I'd like to have a solid proposal to discuss. I'm sure this would be of benefit to RSS and the OGSA group as a whole. Does such a document exist? Could it be circulated? If not could someone commit to generating it? And I'm not after a long CIM document to read... Is there a more concrete agenda possible for Tuesday's call? Regards, Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

OGSA RM teleconference -- where does resource modeling fits in?
by Fred Maciel 18 Jul '05

18 Jul '05

Hi, First of all, sorry for the cross-posting -- this subject involves all three WGs. Since GGF14 there have been a lot of discussions on where resource modeling fits -- BES considered it out of scope but Andrew thinks it's not totally out; RSS is discussing whether it's in scope; and this was discussed in the OGSA-WG also. So, let's discuss this in the Resource Modeling design team teleconference (which is, in fact, the place to discuss this). Oh, yes, part of this was supposed to be discussed in the RM teleconference this week, but only I and Ellen could come... Here are the details: Date: Tuesday, July 19th, at the following times: - 11:00-12:00 US Pacific (GMT - 7) - 12:00-13:00 US Mountain (GMT - 6) - 13:00-14:00 US Central (GMT - 5) - 14:00-15:00 US Eastern (GMT - 4) - 18:00-19:00 GMT - 19:00-20:00 UK (GMT + 1) - 20:00-21:00 Central Europe (GMT + 2) - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. 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

3 2

OGSA WSRF BP 1.0 draft 25
by Takuya Mori 16 Jul '05

16 Jul '05

Hi all, As discussed in the call today, I updated the OGSA WSRF BP 1.0 document and uploaded it to the GridForge. And, I'd like to pass the pen to Hiro. OGSA WSRF BP 1.0 draft 25: https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… ---- Takuya Mori

2 2

Fwd: Re: [ogsa-wg] Comments on OGSA WSRF BP 1.0 draft 25 (specifically security)
by Hiro Kishimoto 15 Jul '05

15 Jul '05

Tom's email bounced. ---- Hiro Kishimoto > To: humphrey(a)cs.virginia.edu, ogsa-wg(a)ggf.org > Subject: Fwd: Re: [ogsa-wg] Comments on OGSA WSRF BP 1.0 draft 25 (specifically security) > From: <tom.maguire(a)suscom.net> > Date: Fri, 15 Jul 2005 9:18:00 -0400 during the 7/13 telecon we agreed to relax the MUST requirements for mutual auth to SHOULD. The descriptive paragraph above the reqt should be changed so that it is clear that the reqts are recommendations. The descriptions are non-normative anyway :-) -----Original Message----- From: Steve Tuecke <tuecke(a)univa.com> Subj: Re: [ogsa-wg] Comments on OGSA WSRF BP 1.0 draft 25 (specifically security) Date: Fri Jul 15, 2005 8:36 am Size: 3K To: David Snelling <David.Snelling(a)UK.Fujitsu.com> cc: humphrey(a)cs.virginia.edu, Steve Tuecke <tuecke(a)univa.com>, ogsa-wg(a)ggf.org Can you briefly recount the arguments for making message security required? I would tend to agree with Marty on this point, for two reasons. First, I think there are a variety of services (or operations) that can be done anonymously, such as some information services. Second, the cost of security in terms of performance can be very high, so to mandate it even when its not needed seems a bit extreme. -Steve On Jul 15, 2005, at 4:13 AM, David Snelling wrote: >> Marty, >> >> Your interpretation of the profile is correct. On several occasions we >> have discussed this very issue and each time the conclusion has been >> consistent with the current draft. If you think the case for relaxing >> the profile is stronger now than on earlier calls and F2F meetings, we >> should schedule a time when you can make the call. Hiro tell me that >> the BP is on the agenda for Monday's call. Can you make it? >> >> Note the the profile dose not outlaw myProxy to GSI and anything else. >> It just says that for interoperability, these published standard >> techniques MUST/SHOULD/MAY be supported by compliant systems. The >> systems can and will use other techniques. In Unicore/GS we will >> continue to use the proprietary UPL/ETDF framework while also >> supporting the BP. >> >> Talk to you on Monday (if I can stay awake). >> >> >> On 15 Jul 2005, at 2:09, humphrey(a)cs.virginia.edu wrote: >> > >>>> I assume that this document has not entered public comment, so I'll >>>> post my >>>> comments here regarding security. I'm afraid that these are largely >>>> the SAME >>>> comments that I've made before. >>>> >>>> Here are my specific concerns... >>>> >>>> The security section (section 8.1) implies that *EVERY* SOAP message >>>> must be >>>> either (1) over TLS or (2) "SOAP Message security with XML signature >>>> and/or >>>> XML Encryption". If you truly mean this (implied by "R0811"), this is >>>> overly >>>> restrictive and makes no sense (there does not exist *ANY* message >>>> that can >>>> justifiably be sent between services/clients that need not incur the >>>> overhead >>>> of crypto?). However, it's not clear if you really mean this >>>> ("R0819", "R0820", "R0821", "R0822", "R0823" seem to imply >>>> otherwise)... so, >>>> what exactly is the intention here? >>>> >>>> In general, section 8.1.2 is too restrictive -- "mutual-authenticated >>>> WS- >>>> Communication will be required" is overly restrictive. And this >>>> section >>>> includes this statement: "The Profile mandates that there be no >>>> anonymous >>>> communication. To ensure interoperability, only X.509 >>>> certificate-based >>>> authentication is permitted by the Profile.") So, this latter part in >>>> particular says that there is *NO PLACE* for password authentication >>>> in OGSA. >>>> (I also believe that you have now outlawed MyProxy, right?) >>>> >>>> Am I reading something incorrectly? >>>> >>>> -- Marty >>>> >>>> Marty Humphrey >>>> Assistant Professor >>>> Department of Computer Science >>>> University of Virginia >>>> >>>> >>>> >>>> >>>> ------------------------------------------------- >>>> This mail sent through IMP: http://horde.org/imp/ >>>> --- message truncated ---

1 0

RE: [ogsa-wg] Comments on OGSA WSRF BP 1.0 draft 25 (specifically security)
by Dave Berry 15 Jul '05

15 Jul '05

Dave, I recall that when Marty raised this issue before GGF14, he was asked to leave discussion of it until after GGF14 (possibly with the intention of ensuring some public comment following submission of the document?). I would certainly be interested in joining dicussion of Marty's points on a call. Dave. > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of David Snelling > Sent: 15 July 2005 10:14 > To: humphrey(a)cs.virginia.edu > Cc: ogsa-wg(a)ggf.org > Subject: Re: [ogsa-wg] Comments on OGSA WSRF BP 1.0 draft 25 > (specifically security) > > Marty, > > Your interpretation of the profile is correct. On several > occasions we > have discussed this very issue and each time the conclusion has been > consistent with the current draft. If you think the case for relaxing > the profile is stronger now than on earlier calls and F2F > meetings, we > should schedule a time when you can make the call. Hiro tell me that > the BP is on the agenda for Monday's call. Can you make it? > > Note the the profile dose not outlaw myProxy to GSI and > anything else. > It just says that for interoperability, these published standard > techniques MUST/SHOULD/MAY be supported by compliant systems. The > systems can and will use other techniques. In Unicore/GS we will > continue to use the proprietary UPL/ETDF framework while also > supporting the BP. > > Talk to you on Monday (if I can stay awake). > > > On 15 Jul 2005, at 2:09, humphrey(a)cs.virginia.edu wrote: > > > I assume that this document has not entered public comment, so I'll > > post my > > comments here regarding security. I'm afraid that these are largely > > the SAME > > comments that I've made before. > > > > Here are my specific concerns... > > > > The security section (section 8.1) implies that *EVERY* > SOAP message > > must be > > either (1) over TLS or (2) "SOAP Message security with XML > signature > > and/or > > XML Encryption". If you truly mean this (implied by > "R0811"), this is > > overly > > restrictive and makes no sense (there does not exist *ANY* message > > that can > > justifiably be sent between services/clients that need not > incur the > > overhead > > of crypto?). However, it's not clear if you really mean this > > ("R0819", "R0820", "R0821", "R0822", "R0823" seem to imply > > otherwise)... so, > > what exactly is the intention here? > > > > In general, section 8.1.2 is too restrictive -- > "mutual-authenticated > > WS- > > Communication will be required" is overly restrictive. And > this section > > includes this statement: "The Profile mandates that there be no > > anonymous > > communication. To ensure interoperability, only X.509 > certificate-based > > authentication is permitted by the Profile.") So, this > latter part in > > particular says that there is *NO PLACE* for password > authentication > > in OGSA. > > (I also believe that you have now outlawed MyProxy, right?) > > > > Am I reading something incorrectly? > > > > -- Marty > > > > Marty Humphrey > > Assistant Professor > > Department of Computer Science > > University of Virginia > > > > > > > > > > ------------------------------------------------- > > This mail sent through IMP: http://horde.org/imp/ > > > > > -- > > 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

Proposed agenda for July 18th call
by Hiro Kishimoto 15 Jul '05

15 Jul '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on July 18th 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: 0718 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 http://tinyurl.com/5fxfd/minutes-20050713/en/1 Aug. F2F update (if any) Agenda bashing 2) OGSA WSRF BP 1.0 final review (30 min) > - Editing Actions: > 1. Takuya to update the document and put on gridforge as draft 25 > 2. Hiro to update table > 3. If anyone wants the pen talk to Hiro after that. Tom will bring his proposal on R0429. 3) Resource modeling discussion (20 min) > - Agreed that interested parties should discuss this offline, > followed by discussing it on the BES call this week, followed by > discussing it again in the OGSA call on July 18. > - This activity is part of the coordination between OGSA & > OGSA-BES WG 4) RNS spec review (60 min) > - Manuel will give a short (15-20 minutes) presentation of the > specification > - Purpose is for OGSA-WG to comment (since OGSA is going to be one > of the 'customers' of this spec) in preparation for the document's > submission RNS spec: https://forge.gridforum.org/projects/gfs-wg/document/RNS-Proposed_Final_Dra… 5) Wrap up AOB July 20 (Wed): OGSA-WG next step discussion, telecon schedule -- Hiro Kishimoto

1 0

Proposed agenda for July 13th call
by Hiro Kishimoto 13 Jul '05

13 Jul '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on July 13th 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: 0713 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-20050711/en/1 Agenda bashing 2) August F2F meeting update (20 min) Byte-IO WG ask to move their session to be early in the week and early in the day, i.e. Monday or Tuesday morning. (See attached proposal) 3) Canonicalization proposal review (20 min) > - R0429: Tom to do canonicalization proposal. Then decide > whether to keep this compliance statement in the spec > or not. 4) OGSA WSRF BP 1.0 security session review (60 min) > - Section 8: Review postponed for next call since Frank is > still revising this section. Frank and Takuya will send out revised security section before the call. 5) Wrap up (10 min) AOB July 18 (Mon): OGSA WSRF BP 1.0 final call, RNS spec review, resource modeling discussion July 20 (Wed): OGSA-WG next step discussion, telecon schedule RNS spec: https://forge.gridforum.org/projects/gfs-wg/document/RNS-Proposed_Final_Dra… ---- Hiro Kishimoto

2 1

OGSA WSRF BP 1.0 draft 24
by Hiro Kishimoto 13 Jul '05

13 Jul '05

Hi all, Andreas and I made several edits to the OGSA WSRF BP 1.0 including updated Referenced Spec Status and Adoption Level Classification (Appendix F) and upload it to GridForge. Jem's excel sheet is also updated. It does not include updated security section nor appendix E. I guess Takuya will send out separately before the call. OGSA WSRF BP 1.0 draft 24: https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… Jem's spread sheet; https://forge.gridforum.org/projects/ogsa-wg/document/ogsa-referenced-stand… -- Hiro Kishimoto

2 1

[Fwd: [jsdl-wg] JSDL 1.0 in 60-day public comment period]
by Andreas Savva 13 Jul '05

13 Jul '05

JSDL 1.0, one of the specifications relevant to OGSA EMS (BES, RSS, etc), is now in 60-day public comment. Please consider reviewing it and providing comments. JSDL 1.0: http://www.ggf.org/Public_Comment_Docs/Documents/July-2005/draft-ggf-jsdl-s… Make or view comments: https://forge.gridforum.org/forum/forum.php?forum_id=552 Thanks. -- Andreas Savva Fujitsu Laboratories Ltd

1 0

OGSA roadmap document: your comments are critical
by Hiro Kishimoto 13 Jul '05

13 Jul '05

Hi all, As you already know, OGSA roadmap document (Defining the Grid: A Roadmap for the Open Grid Services Architecture) has entered 30 days public comment review period on June 29th. And now only two more weeks to go. Since this is very important document for the community, we would very much appreciate it if you could take the time to read this document and provide your comments on the GridForge. If you are happy with it, just say "I've read the document and I like it." Document: http://www.ggf.org/Public_Comment_Docs/Documents/June-2005/draft-ggf-ogsa-r… Make or view comments: https://forge.gridforum.org/forum/forum.php?forum_id=540 Thanks in advance, -- Hiro Kishimoto

1 0

RM teleconference reminder - July 12
by Fred Maciel 12 Jul '05

12 Jul '05

Hi, Let's have a short teleconference mainly to report on what happened in GGF14 (Andrea: if you can participate, could you tell us what happened in the UCWG-OGSA session?). Let's also do some planning on how to move things ahead -- looks simple, but isn't (Jem: can you participate? I need somebody who understands the OGSA profile definition document). More details on the teleconference. Date: Tuesday, July 12th, at the following times: - 11:00-12:00 US Pacific (GMT - 7) - 12:00-13:00 US Mountain (GMT - 6) - 13:00-14:00 US Central (GMT - 5) - 14:00-15:00 US Eastern (GMT - 4) - 18:00-19:00 GMT - 19:00-20:00 UK (GMT + 1) - 20:00-21:00 Central Europe (GMT + 2) - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. 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: 0614 Explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html See you there, Fred Maciel Hitachi America R&D

2 1

OGSA-WG and fellow WG August '05 F2F Survey
by Hiro Kishimoto 12 Jul '05

12 Jul '05

Hi all, OGSA-WG and fellow WGs are planning to have August '05 F2F meeting. A schedule in week of August 29 at San Diego was proposed at GGF14. However, I got several requests for another date (week of August 15) and/or city (SF bay area). Thus I took action item to ask all expected attendees for their availability for F2F meeting. Please take the time to fill in the following online survey by this Friday (July 8) or at latest next Monday (July 11). We will decide date and city early next week. Post the survey on a Web site - use this URL: http://www.zoomerang.com/survey.zgi?p=WEB224GECBLCHX Thanks, -- Hiro Kishimoto

1 2

Minimal Web Service Profile BoF
by Steven Newhouse 12 Jul '05

12 Jul '05

During GGF 14 there was a BoF on building a profile for OGSA around a different group of web service specifications (primarily WS-Transfer & WS-Eventing). The agenda for the meeting is below and the slides are attached. Introduction, Motivation & Goals – Steven Newhouse WS-Transfer/Eventing/Enumeration – Marvin Theimer Different Approaches: WSRF vs. WS-Transfer – Marty Humphrey WS-Management – John Tollefsrud -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

Teleconference minutes - 11 July 2005
by Andreas Savva 12 Jul '05

12 Jul '05

Minutes attached. - August F2F fixed (Aug 15-19, @Sunnyvale) - GGF14 minutes approval - Resource model and BES discussion - OGSA WSRF BP 1.0 review https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050711/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 11 July 2005 ================================== * Participants Andrew Grimshaw (UVa) Soonwook Hwang (NAREGI) Hiro Kishimoto (Fujitsu) Fred Maciel (Hitachi) Tom Maguire (IBM) Takuya Mori (NEC) Steven Newhouse (OMII) Manuel Pereira (IBM) Latha Srinivasan (HP) Jay Unger (IBM) Pete Ziu (Northrop Grumman) Apologies: Mark Morgan, Mike Behrens Minutes: Andreas Savva * Minutes approval July 6 minutes approved with minor changes. Details: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/07/msg00017.html * F2F (August 2005) Update - Fixed for August 15, at Sunnyvale (about 40 minutes from SF) - Fujitsu to provide facilities (with internet access) - (With Almaden (Jay) as backup) - (And Hitachi (Fred) as secondary backup) - There was no a perfect choice and unfortunately a number of people (Chris Smith, Frank Siebenlist, Dave Snelling, Ravi Subramaniam) may not be able to attend. But more people would be unable to attend the week of Aug 29. - Sunnyvale was chosen over La Jolla since many people are based there. It is also unlikely that sufficient rooms can be reserved at La Jolla---it is peak holiday season. - There is a possible conflict with WSDM F2F, which is scheduled for the same week. - Jay and Fred will try to resolve this conflict (move to a different week or extend the period, etc). * GGF14 ** Minutes approval All minutes except security session (#10) have been uploaded. Action: Takuya to look into getting the security session minutes online - Approval for security session minutes (session 10) postponed. - Minutes for session 2-6, 8-9 approved with no changes. - Minutes for session 1 (Outreach) approved with changes: - informational profile clarification added - change 'level' to 'version' - Minutes for session 7, 11, 12 approved with minor changes. Details: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/07/msg00024.html ** Followup discussion - Mailing list for 'mws' BOF not set up yet. - No agreement on the name yet. It should be something that does not prejudice for or against single or multiple basic profiles. - Name proposals: x ogsa-fbp-bof (future basic profile) x ogsa-nbp-bof (next basic profile) o ogsa-bp-bof x ogsa-wsm-bof Agreed on ogsa-bp-bof. Action: Hiro will email Joel to set up ogsa-bp-bof list. ** OGSA Naming WG - There is now a Naming WG site is up - Minutes (session 5) will also be copied there - The OGSA Naming WG will be cross-posting to the OGSA list for a while Action: Manuel to send an email to publicize the group's site and mailing list (done) ** GGF14 impressions - Sessions went very well. There was a lot of discussion with groups related to OGSA. - In particular CDDLM-WG is getting more involved in OGSA; trying to place themselves (and ACS) in EMS architecture. * Resource model and BES discussion - It is unclear how or where the resource modelling work should continue now that BES has put it out of scope. - One option is to do this work in the context of RSS or perhaps even spawn a new group dedicated to resource modelling. The coordination problem is not insignificant, however. It is not yet clear how to proceed with this work. - BES put this work out of scope on the assumption that selection is over by the time a request reaches the BES container. (Also due to the fear that if the resource modelling work was taken on then it would cause the overall BES work to stall.) - Since RSS deals with resource selection it is probably a better (right?) place to do this modelling effort. - There is a concern that leaving this modelling work for later may cause rework of specs. This is not intended to stop ongoing work until the resource modelling is finished but to make sure people are aware of the risk. - BES is not doing modelling so the problem may not be that big - RSS would have to tackle this work---so it is probably going to be tackled relatively soon The consensus is that this topic needs more discussion. - Agreed that interested parties should discuss this offline, followed by discussing it on the BES call this week, followed by discussing it again in the OGSA call next Monday. - This activity is part of the coordination between OGSA & OGSA-BES WG * OGSA WSRF BP 1.0 review - Review of draft 22 posted on gridforge: https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… - Table 1.1 - Namespace URIs for WSN specs need fixing. (Tom) - Table 2.1 - It is incorrect. Delete table and put the section back the way it was in v021. (Tom) - Add the ogsa-bp namespace and prefix in Table 1.1 (Tom) - E0303 addition accepted. - R0311 deletion of 'subject to amendment ..." accepted. - Latha's comment on R0424 about listing faults for other operations for consistency. - Agreed that the BP should not be duplicating statements that already appear in other specs. The faults listed for the WSN Subscribe operation (R0614-16) were not part of that specification when they were enumerated in the BP. They are now, so those statements should be deleted. - Delete comment (Tom) - Delete R0614-16 (Tom) - R0429: Tom to do canonicalization proposal. Then decide whether to keep this compliance statement in the spec or not. - R0511: Agreed for consistency with previous paragraph to change MUST to SHOULD. - Also revised "message exchange" to use the normative operation names. - R0513 and R0515: For consistency with previous paragraph change MUST to SHOULD - Otherwise new text on scheduled termination looks ok. - Sec.6.1.1: Comment about MESSAGE reqt seems obsolete; delete - R0711: Deletion of "subject to amendment..." accepted - Section 8: Review postponed for next call since Frank is still revising this section. - References - Tom to update references, in particular the WSRF CDs are now in public comment. Also the WSN CDs - Confirmed that the WS-Addressing reference is the correct one - Copyright in schema: Hiro asked GGF Editor and waiting for reply. It is not a show-stopper. - What is the relation of appendix C and D, and can they be merged? - C defines the infoset, pseudo schema and also gives a description of semantics while D only provides syntax. They are not completely equivalent and should be left separate. - Update Appendix F with new table (Hiro) - Table 8-? are misnumbered and should be fixed (Andreas) - Schedule: - Wednesday: - Review Tom's canonicalization proposal - Review security section - Next Monday: - Final call review - Tom will post an updated version (done) * Next steps ** RNS specification review - Proposal to put a review of this document on the agenda of a future OGSA call - Agreed to schedule it for next Monday (7/18); 60 minutes slot - Manuel will give a short (15-20 minutes) presentation of the specification - Purpose is for OGSA-WG to comment (since OGSA is going to be one of the 'customers' of this spec) in preparation for the document's submission

1 0

RE: [ogsa-wg] RM teleconference reminder - July 12
by Andrea Westerinen (andreaw) 12 Jul '05

12 Jul '05

Fred, I can't participate tomorrow due to an overlapping Cisco meeting. The UCWG-OGSA session was uneventful. Roger Reich presented an overview and status of the Utility Computing work in the DMTF, the group's white paper and next steps. He asked for involvement, input and participation from the GGF community. Andrea > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Fred Maciel > Sent: Monday, July 11, 2005 5:39 PM > To: ogsa-wg(a)ggf.org > Subject: [ogsa-wg] RM teleconference reminder - July 12 > > Hi, > > Let's have a short teleconference mainly to report on > what happened in > GGF14 (Andrea: if you can participate, could you tell us what > happened in the UCWG-OGSA session?). Let's also do some > planning on how to move things ahead -- looks simple, but > isn't (Jem: can you participate? I need somebody who > understands the OGSA profile definition document). More > details on the teleconference. > > Date: Tuesday, July 12th, at the following times: > - 11:00-12:00 US Pacific (GMT - 7) > - 12:00-13:00 US Mountain (GMT - 6) > - 13:00-14:00 US Central (GMT - 5) > - 14:00-15:00 US Eastern (GMT - 4) > - 18:00-19:00 GMT > - 19:00-20:00 UK (GMT + 1) > - 20:00-21:00 Central Europe (GMT + 2) > - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. > > 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: 0614 > Explanation: > > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg > 00077.html > > See you there, > > Fred Maciel > Hitachi America R&D >

1 0

OGSA Naming Working Group mailing list and GridForge site is now up and available
by Manuel Pereira 11 Jul '05

11 Jul '05

The OGSA Naming Working Group mailing list and GridForge site is now up and available. All who are interested in naming and name resolution Web services, particularly the activities embodying RNS and WSNR, are encouraged to join the ogsa-naming-wg(a)ggf.org mailing list. You can review the working group charter abstract, working drafts, and related information at the GridForge project site: https://forge.gridforum.org/projects/ogsa-naming-wg/ Best regards, Manuel Pereira =============================== IBM Almaden Research Center 1-408-927-1935 [T/L 457] mpereira(a)us.ibm.com

1 0

Proposed agenda for July 11th call
by Hiro Kishimoto 11 Jul '05

11 Jul '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on July 11th 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: 0711 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-20050706/en/1 Agenda bashing 2) GGF14 session minutes approval (10 min) GGF14 minutes are now on the GridForge Review and approve https://forge.gridforum.org/docman2/ViewCategory.php?group_id=42&category_i… 3) August F2F meeting planning (20 min) Proposal is Aug 15-19 or Aug 29-Sept 2 at San Diego Supercomputing Center or San Francisco Bay Area. please take the time to answer the online survey. http://www.zoomerang.com/survey.zgi?p=WEB224GECBLCHX Survey result as of July 8 is on the GridForge https://forge.gridforum.org/projects/ogsa-wg/document/200508F2F_survey/ 4) OGSA WSRF BP 1.0 review (60 min) 5) Wrap up (10 min) AOB -- Hiro Kishimoto

2 3

OGSA WSRF BP 1.0 draft 22
by Andreas Savva 11 Jul '05

11 Jul '05

I've uploaded draft 22 of the OGSA WSRF BP 1.0 profile. A number of changes to fix issues resolved during last week's call (thanks to Latha and Hiro) and also many formatting changes. (I accepted most formatting changes before uploading.) Not sure who gets the pen next; probably Tom. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… or http://tinyurl.com/5fxfd/draft-ggf-ogsa-wsrf-basic-profile/en/16 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

[ogsa-wg | Basic Profile - 1561] Which spec to choose for R0429
by Sourceforge Tracker Monitor 11 Jul '05

11 Jul '05

A new artifact has been added: 1561 Submitted by: Andreas Savva Submitted date: 2005-07-11 17:11:04 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1561&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1561&group_id…) Summary: Which spec to choose for R0429 Project: Open Grid Services Architecture Tracker: Basic Profile Artifact ID: 1561 Category: <None> Group: <None> Status: Open Priority: - Last Modified By: Andreas Savva Last Modified: 2005-07-11 17:11:04 Submitted By: Andreas Savva Submit Date: 2005-07-11 17:11:04 Assigned To: Tom Maguire File(s): <None> Description: >From July 6 minutes: section 4.3, l.330: R0429 A MESSAGE response for wsrf-rp:QueryResourceProperties with the Dialect URI http://www.w3.org/TR/1999/REC-xpath-19991116 (http://www.w3.org/TR/1999/REC-xpath-19991116) MUST conform to the structure/serialization as defined in XML Digital Signature Canonicalization. (Tom's comment) There are 2 specs need to chose which is appropriate. Still needs work. View the Basic Profile : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

[ogsa-wg | Basic Profile - 1560] Why are faults described for notification only
by Sourceforge Tracker Monitor 11 Jul '05

11 Jul '05

A new artifact has been added: 1560 Submitted by: Andreas Savva Submitted date: 2005-07-11 17:08:22 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1560&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1560&group_id…) Summary: Why are faults described for notification only Project: Open Grid Services Architecture Tracker: Basic Profile Artifact ID: 1560 Category: <None> Group: <None> Status: Open Priority: - Last Modified By: Andreas Savva Last Modified: 2005-07-11 17:08:22 Submitted By: Andreas Savva Submit Date: 2005-07-11 17:08:22 Assigned To: Tom Maguire File(s): <None> Description: >From July 6 minutes: section 4.3 l.339: (Latha's comment) We probably want to say something here about throwing the same faults that GetMultipleResourceProperties message does. Same comment for all other messages such as Destroy, Subscribe etc. - Not sure why faults are described for notification only. Tom authored this section. Action: Andreas to check with Tom whether there was a special reason for this or whether similar text should be added in other places View the Basic Profile : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

[ogsa-wg | Basic Profile - 1559] Anonymous communication
by Sourceforge Tracker Monitor 11 Jul '05

11 Jul '05

A new artifact has been added: 1559 Submitted by: Andreas Savva Submitted date: 2005-07-11 17:01:49 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1559&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1559&group_id…) Summary: Anonymous communication Project: Open Grid Services Architecture Tracker: Basic Profile Artifact ID: 1559 Category: <None> Group: <None> Status: Open Priority: - Last Modified By: Andreas Savva Last Modified: 2005-07-11 17:01:49 Submitted By: Andreas Savva Submit Date: 2005-07-11 17:01:49 Assigned To: David Snelling File(s): <None> Description: In section 8.1.2 "The Profile mandates that there be no anonymous communication." There are two comments from Jem and Latha: - Im not clear here are we mandating this with this sentence? If so, should this be phrased as a MUST? - Is this too restrictive? What about situations where we perform anon. queries against registries, for example? And a followup by Takuya: I think we don't have clear consensus on this issue about anonymous communication. David thought that all the communication should be authenticated, but there were some who didn't agree on it. I don't remember what was the conclusion of this discussion. View the Basic Profile : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

CDDLM specs presentation (Re: Meeting to discuss CDDLM and OGSA (EMS) in more detail)
by Hiro Kishimoto 10 Jul '05

10 Jul '05

Hi all, Dejan's presentation is now uploaded to ogsa:ems folder. https://forge.gridforum.org/projects/ogsa-wg/document/cddlm-spec-ogsa-intro… Thanks, ---- Hiro Kishimoto Milojicic, Dejan S wrote: > Hi All, > > Attached is the presentation. The session will start in a a couple of > minutes. > > Thanks, > > Dejan. > > >>-----Original Message----- >>From: Milojicic, Dejan S >>Sent: Tuesday, July 05, 2005 7:03 AM >>To: 'Subramaniam, Ravi'; 'csmith(a)platform.com'; >>'behrens(a)R2AD.com'; 'Keisuke Fukui (on the road)'; >>Fred.Maciel(a)hds.com; 'mmm2a(a)cs.virginia.edu' >>Cc: Jun Tatemura; Loughran, Steve; Stuart Schaefer; 'Hiro >>Kishimoto'; 'Andrew Grimshaw' >>Subject: Meeting to discuss CDDLM and OGSA (EMS) in more detail >> >>Hi Chris, Fred, Mark, Mike, Keisuke, and Ravi, (cc-ed to >>Andrew, Hiro, key CDDLM members, and CDDLM mailing list) >> >>Per the OGSA meeting at GGF, you have been identified as a >>potential candidates to discuss how CDDLM (Configuration >>Description, Deployment and Lifecycle Management) fits into >>the broader OGSA picture and in particular with EMS. >> >>We have agreed on the following course of actions. We will >>meet tomorrow (Wed 7/6, at 2pm PST) and briefly go over the >>CDDLM so that you get more familiar with it. We'll have intro >>and 3 slides per spec (language, component model, and >>deployment API). We will identify some key areas that need >>addressing integration of CDDLM into OGSA and then we shall >>plan the F2F some time in August/September time frame. >> >>Can you please confirm that you will be able to participate >>in the meeting tomorrow. The meeting is open to all CDDLM members. >> >>Thanks, >> >>Dejan. >> >>We shall use the following conference number: >> >>+1 866-639-4732 (toll free while in US) >>Code 2362906 (followed by a '#' sign) >>+1 574-948-0379 (toll & international)

1 0

Teleconference minutes - 6 July 2005
by Andreas Savva 10 Jul '05

10 Jul '05

Minutes attached. - F2F update - GGF14 review - WSRF BP review https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050706/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 6 July 2005 ================================= * Participants Hiro Kishimoto (Fujitsu) Fred Maciel (Hitachi) Mark Morgan (UVa) Takuya Mori (NEC) Andreas Savva (Fujitsu) Dave Snelling (Fujitsu) Latha Srinivasan (HP) Jay Unger (IBM) Pete Ziu (Northrop Grumman) Apologies: Mike Behrens Minutes: Andreas Savva * Minutes approval June 22 minutes approved with no comments * F2F Update Proposal is for the week of Aug 29 at SDSC - Jay may have a conflict that week and the week before (Aug 22) - Dave B also may have a conflict the week of Aug 29. - Mark is away from August 20. - Hiro cannot make week of August 22 - Allen L might have travel restrictions so Santa Clara might be a better choice than San Diego. - Discussed alternatives: - Week after (Sep 5) is Labour week - GGF15 is the first week of October so it cannot be after Labour week - The week of Aug 15 was the only other alternative that most people on the call could identify. - But Hiro cannot stay the whole week; he would have to leave Friday. - Agreed that it is necessary to fix the dates soon since (especially) the week of Aug 15 is peak holiday season. - Since the meeting will include fellow WG sessions they should also be consulted. Action: Hiro will ask people for their availability and the group will make a firm decision by next call (Monday) * GGF14 evaluation - Not all presentations or minutes are on gridforge yet. Action: People who presented in OGSA-WG GGF14 sessions should put their presentations online. Action: Minute takers to put their minutes on gridforge. There was good attendance of OGSA sessions, but overall GGF14 seemed poorly attended---about 350 people compared with a typical 450. Also there did not seem to be a lot of press. (Usually it is not planned but some people turn up.) Allan W's article in Grid Today on OGSA was very good. One possibility for the low attendance might be the holiday season, and perhaps the location. Since the next GGF is co-scheduled with GridWorld it should be better attended. (But GridWorld is probably overlapping completely with GGF15.) In any case it seems a good idea to leave the planning up to a professional meeting planner like IDG. Working days were too long. Also the rooms were too big; could have subdivided them further and have more parallel sessions. Or do smaller slots: 45 minutes instead of 1:30 and allow for double slots. For OGSA-WG at GGF15 the plan is to have fewer sessions during GGF (mainly do outreach) and to do a f2f separately. Discussed venue options for this f2f. - The GGF hotel if rooms are available - The Lotus facility is fairly close - Hitachi facility is not far GGF16+ dates are not fixed yet but are likely to be close to the following dates: GGF16: Feb 20, 27 GGF17: May 9-12 GGF18: Sep 25-29 Also it would be nice to have a simple way to import the GGF schedule into a pda etc. * OGSA WSRF BP 1.0 review Using the version that Latha sent out on the list. http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/07/msg00008.html - There are no open issues on Gridforge. Used the list that Hiro sent out. This list incorporates Latha's comments but not the security-related changes that Takuya and Frank made separately. http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/07/msg00006.html l90: 'open standard': Agreed to use the same terminology as in the profile definition. Action: On next pen holder. l213: E0302 claims extensibility elements for wsa:Metadata. Is extensibility for wsa:ReferenceParameters necessary? - Check and add if there is an extensibility element in the referenced spec. Action: On next pen holder. l222: R0311: Delete the 'subject to amendment' portion since this profile does not contain any amendments Action: On next pen holder. l339: (Latha's comment) We probably want to say something here about throwing the same faults that GetMultipleResourceProperties message does. Same comment for all other messages such as Destroy, Subscribe etc. - Not sure why faults are described for notification only. Tom authored this section. Action: Andreas to check with Tom whether there was a special reason for this or whether similar text should be added in other places l363: (Tom's comment) There are 2 specs need to chose which is appropriate. Still needs work. - Open. Action: Tom to follow up. l384: Scheduled Destruction should be added. - There is mention earlier on (l125) that the profile covers this functionality. - Agreed that it should be added to the BP. Action: On next pen holder. l394: (Jem and Latha's comment) Sentence rewriting. - Revision looks fine. - But the subsequent normative text does not make the distinction that the non-normative text makes. The normative sentences (R0511 & R0512) have to be checked and revised. Action: Latha & Andreas l412: (Tom's comment)Add MESSAGE reqt. Action: Latha to follow up with Tom. l450: (Hiro's comment) Don't we need extensibility points for Base Faults? I think we need to carry detailed fault information. - Some problem with the base faults specification. It will have to be fixed after public comment. (The schema will probably change and not have extensibility elements.) - Agreed to leave as is for now; review and tidy it up later. l463: Since there is no amendment in the Profile, should we delete this line? Action: Next pen holder to delete 'amendment' text. l566: Contributors and Acknowledgment sections - Reviewed and accepted Hiro's proposal. l620: WS-BN should be evolving before final submission. - Reference needs update once the CD versions are approved. Action: Hiro will update the master spreadsheet and Appendix F. ** Tracker review Reviewed 'resolved' issues: 1223: Fixed but need comment that the resolution was slightly different (Andreas to put comment in) 1227: Closed(obsolete) 1294: Leave as resolved until the versions are fixed. 1355: fixed ** Other discussion - Should the GGF copyright be included in the schemas? - Action: Hiro to ask GGF Editor (Greg) about it. - Namespace URI format? - There is a proposal to the GGF Editor but it is not formalized yet - Agreed to leave as is and wait for Greg's comment - Security fixed issues need to be verified - Some futher security modifications were done by Frank during a GGF14 session - Hiro is waiting for the draft from Frank. - Profile review will continue next Monday

2 1

CIM mapping to WSDM
by Fred Maciel 08 Jul '05

08 Jul '05

Hi all, Here is the URL to the proposed CIM mapping to WSDM, which was mentioned several times in GGF14. http://www-128.ibm.com/developerworks/webservices/library/specification/ws-w sdm/ Regards, Fred Maciel Hitachi America R&D

1 0

Basic Profile Document Errors
by Mark Morgan 08 Jul '05

08 Jul '05

Trying to finish up things for ByteIO, I discovered the following issues with the OGSA WSRF Basic Profile (document retrieved from Grid Forge with Timestamp of 5 July 2005). *) On line 158, need to change "...rpw-1|" to "...rpw-1" *) On line 163, double quotes needed for consistency *) Both of the URI's given for notification on lines 162 and 163 are invalid according to docs.oasis-open.org. I understand that this is probably because those specs. are not offically released yet, however this does mean that ByteIO will have to generate either a spec which is not conformant to the OGSA WSRF Basic Profile, or one which contains WSDL that cannot be interpreted by any one. -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.cs.virginia.edu mmm2a(a)virginia.edu (434) 982-2047

2 1

EMS and CDDLM
by Milojicic, Dejan S 06 Jul '05

06 Jul '05

Hi, We just held the meeting between representatives of EMS of OGSA and CDDLM-WG with the objective to identify the role of CDDLM in the OGSA. Attendees: Steve Loughran, Mark Morgan, Ayla, Jun Tatemura, Chris, Hiro Kishimoto, Keisuke Fukui, Stuart Schaefer, Michael Behrens, Fred Maciel. Agenda and notes: - introductory presentation on CDDLM (intro, CDL, component model, deployment APIs), Hiro will post it into the GridForge shortly. - discuss how to proceed: CDDLM reads architecture document (EMS section) on deployment and configuration work - plan F2F, one day in the week of August 29th in CA, San Diego Supercomputing center, or Santa Clara. The goal is to identify how does CDDLM fit with provisioning, resource allocation, etc. how to start activity on the Grid. There are currently such diagrams in the OGSA architecture specification, as well as in the CDDLM Foundation document. Next phone conference will take place on the 3rd of August, prior to that we'll start email exchange, check boxes on resource allocation and how CDDLM fits them (resource scheduling). Thanks, Dejan Milojicic, co-Chair CDDLM-WG.

1 0

RE: [ogsa-wg] Minor edits on OGSA WSRF BP 1.0
by Srinivasan, Latha 06 Jul '05

06 Jul '05

Hiro, Looks good. I reviewed your version and have attached a doc. with some comments and modifications. -Latha Latha Srinivasan Hewlett Packard 6000 Irwin Rd Briggs Rd Industrial Park Mount Laurel, NJ 08054 Phone: 856-638-6019 Email: Latha.Srinivasan(a)hp.com -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Hiro Kishimoto Sent: Wednesday, July 06, 2005 8:24 AM To: Ogsa-Wg Subject: [ogsa-wg] Minor edits on OGSA WSRF BP 1.0 Hi all, I've fixed minor editorial isses on OGSA WSRF BP 1.0 v020. (now it is v021). I don't touch security section (section 8) and appendix E, since Frank is now working on. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsr f-basic-profile/en/15 Thanks, -- Hiro Kishimoto

1 0

Minor edits on OGSA WSRF BP 1.0
by Hiro Kishimoto 06 Jul '05

06 Jul '05

Hi all, I've fixed minor editorial isses on OGSA WSRF BP 1.0 v020. (now it is v021). I don't touch security section (section 8) and appendix E, since Frank is now working on. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… Thanks, -- Hiro Kishimoto

1 0

Open issues on OGSA WSRF BP 1.0
by Hiro Kishimoto 06 Jul '05

06 Jul '05

Hi Tom and Dave, Following is a list of open issues on OGSA WSRF BP 1.0 v020. It includes existing comments in the document but does not cover security section (section 8) or appendix E, which Frank is now working on. Page and line number is based on v020. (a1) page 5 line 200 E0302 claims extensibility elements for wsa:Metadata? Is extensibility for wsa:ReferenceParameters necessary? (a2) page 5 line 211 Since there is no amendment in the Profile, should we delete this line? (a3) page 8 line 339 (Latha's comment) We probably want to say something here about throwing the same faults that GetMultipleResourceProperties message does. Same comment for all other messages such as Destroy, Subscribe etc. Perhaps we can address this in the next rev. after GGF14. (a4) page 9 line 363 (Tom's comment) There are 2 specs need to chose which is appropriate. Still needs work. (a5) page 9 line 384 5.2 Scheduled Destruction should be added. (a6) page 9 line 394 (Jem and Latha's comment) Tom, we need to clarify this a bit. The comma I removed created some ambiguity, but we’re (Latha and I) are not sure exactly what the intent of this is. (a7) page 10 line 412 (Tom's comment) Add MESSAGE reqt. (a8) page 10 line 440 Don't we need extensibility points for Base Faults? I think we need to carry detailed fault information. (a9) page 11 line 450 Since there is no amendment in the Profile, should we delete this line? (a10) page 13 Contributers and acknowledgment sections. (a11) page 24 WS-BN should be evolving before final submission. Thanks, -- Hiro Kishimoto

1 0

GGF 14
by Steven Newhouse 05 Jul '05

05 Jul '05

All, We had two good sessions at GGF 14. Updated documents etc. will be posted over the next few days. Calls will resume on 14th July - details and agenda will be posted next week. Also, this will be the final cross post to the ogsa-wg mailing list. If you want to follow the Basic Execution Service Working Group please join the ogsa-bes-wg mailing list in the usual way. Regards, Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

Proposed agenda for July 6th call
by Hiro Kishimoto 05 Jul '05

05 Jul '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on July 6th 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: 0706 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (June 22) http://tinyurl.com/5fxfd/minutes-20050622/en/1 Agenda bashing 2) GGF14 sessions evaluation (20 min) Please upload your materials and minutes to GridForge 3) August F2F meeting planning (20 min) Proposal is Aug 29-Sept 2 at San Diego Supercomputing Center. See attached slides. 4) OGSA WSRF BP 1.0 review (60 min) 5) Wrap up AOB ---- Hiro Kishimoto

1 0

GRIDToday article "Report from GGF14: Finally, OGSA is Real!"
by Hiro Kishimoto 04 Jul '05

04 Jul '05

Report from GGF14: Finally, OGSA is Real! By Alan J. Weissberger, Contributing Author 1. OGSA WG Comes of Age First and foremost among the GGF14 happenings was the emergence of the OGSA WG as a viable standards setting body, rather than a "castles in the sky" committee developing abstract architectural concepts that could not be implemented. After years of discussion, the OGSA WG has now identified a core set of Web services standards and described how they can be used together to form the basic building block for Grids. http://news.taborcommunications.com/msgget.jsp?mid=412070&xsl=story.xsl -- Hiro Kishimoto

1 0

NO OGSA-WG call on July 4th
by Hiro Kishimoto 02 Jul '05

02 Jul '05

Hi all, Thank you very much for all of you who came to GGF14. We've accomplished three critical documents and made GGF14 historic event! (especially for me :-) Since 4th of July is US holiday, we have NO call on Monday. Our next call is on Wednesday July 6th. Thanks again and enjoy Independence Day holiday, ---- Hiro Kishimoto

1 0

No RM teleconference on July 5th
by Fred Maciel 02 Jul '05

02 Jul '05

Hi, Let's skip the RM teleconference on July 5th, while I think how to move the resource modeling work ahead. Regards, Fred Maciel.

1 0

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Dave Berry 01 Jul '05

01 Jul '05

After more thought, I'll modify my original position (for what it's worth). If the industrial supporters of WS-Transfer et al actively engage in an OGSA profile, then we should start a.s.a.p. I would very much like to see those companies involved in OGSA and this would be a natural first "toe in the water". Also, it would be more hands to the OGSA pump rather than diverting so much of the existing effort. As always, just a personal point of view. Dave. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Dave Berry Sent: 25 June 2005 16:14 To: Marty Humphrey; Ogsa-Wg Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 After some thought, my current opinion is that the right time to start work on a new basic profile will be when all the relevant specifications have been submitted to standards bodies. In the meantime, I would encourage people to concentrate on all the higher-level questions that we have yet to resolve - including a framework for describing, naming and managing resources, data transfer, advance reservation, security, delegation, privacy, agreement negotiation, information monitoring and dissemination, data access and replication, workflow, etc. I think OGSA is most likely to fail if we focus on low-level issues at the expense of the larger operations which users actually need and want from us. This approach is also in keeping with the 'O' in OGSA, which stands in large part for Open Standards. (FWIW, this is also true of the 'O' in OMII). In line with this reasoning, I regret that I won't be attending this BOF - which is why I'm posting my opinion here. In fact my position was partly crystallised by the realisation that the other sessions that clash this BOF are more important to me. This is not a position about whether to have multiple basic profiles at all, just on the timing of new work. And of course it's just my opinion. Dave. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Dave Berry Sent: 22 June 2005 23:08 To: Marty Humphrey; Ogsa-Wg Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 Marty, The reason I asked about the status of the specifications was to clarify what sort of profile document could be produced at the present time. OGSA profiles are governed by a set of rules (https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-pr ofile-definition/en/12). Currently, if a group were to publish a profile document, it would have to be an Informational Profile. It could not be a Recommended Profile because the specifications are not yet in a standards body. Of course, this does not preclude people working on a draft profile with the intent of moving it into the publication process at some later date. I suggest that a question for the BOF to discuss is, given the above process, at what point does it become worth spending time on a draft profile? (I am not presuming an answer to this question one way or another). Switching to the question of WS-Enumeration, your answer seems to validate my initial concern. The issue that WS-Enumeration attempts to address is real and is considered in part by various working groups in the data area, but to me it doesn't seem part of a basic profile. Of course, the fact that I haven't seen a technical reason that links WS-Enumeration closely to the other specs doesn't mean that such a reason doesn't exist! Dave. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Marty Humphrey Sent: 22 June 2005 12:45 To: 'Ogsa-Wg' Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 > 1. Please could you clarify the status of WS-Transfer, WS-Eventing > and WS-Enumeration in the terms of the OGSA Profile template? I.e. > have they been submitted to an SDO, are they draft or evolving, etc.? As you know, there is a 4-step process by which these specs will become standards: [1] "Develop", in which the spec is published; [2] "Broader Participation", in which there are feedback and interop workshops (resulting in possibly revising and republishing the specs); [3] "Standardization", in which the specs are submitted to a standardization body, which then can modify the spec as well and eventually ratify; [4] "Profiles", in which a separate document shows how to *combine* specs, generally resulting in a "subsetting" of the original specs. On Dec 1, 2004, Intel hosted a "feedback" workshop (step [2]), above, for WS-Enumeration and WS-Transfer. The companies attending the workshop included AMD, Computer Associates, Dell, HP, IBM, Intel, Microsoft, SAP, Sharp, Sonic, Sun, veritas, et. al. Although I can't entirely confirm this, it looks like the following companies brought implementations of WS-Enumeration/WS-Transfer to this workshop: Microsoft, Dell, Intel, NetIQ, Sun, and WebMethods. On Feb 19, 2004, Tibco hosted a "feedback" workshop for WS-Eventing. Attendees included Microsoft, BEA, IBM, NEC, Sonic, etc. On April 15, 2004, Microsoft hosted an "interop" workshop on WS-Eventing ("The outcome of the workshop was the demonstration of interoperability among all the 7 implementations." The seven implementations were from BEA, Canon, Epson, Microsoft, Ricoh, Sonic, and Systinet.) It looks like there will be another WS-Eventing workshop, although the date/time have not been announced. The most recent specs are: -- WS-Eventing: Aug 2004 (Authors: IBM, BEA, Computer Associates, Microsoft, Sun, and Tibco). This new version modifies the original version (Jan 2004, I believe) to reflect the workshops. -- WS-Enumeration: Sept 2004 (Authors: Systinet, Microsoft, Sonic, BEA, Computer Associates). This is the first version of the spec. -- WS-Transfer: Sept 2004 (Authors: Systinet, Microsoft, Sonic, BEA, Computer Associates). This is the first version of the spec. There's an interesting graphic that shows some of the progress from Microsoft's perspective here: http://msdn.microsoft.com/webservices/graphics/workshop-timeline.gif (this is taken from http://msdn.microsoft.com/webservices/community/workshops/default.aspx) > 2. I can see that WS-Transfer specifies some of the functionality of > WSRF and WS-Eventing is largely equivalent to WS-BaseNotification, but > what has WS-Enumeration to do with this? From a brief reading, it > seems to specify functionality that is independent of either stack. I can see this point -- in our initial designs and experimentation with WS-Transfer and WS-Eventing, we chose to not utilize WS-Enumeration. But we are increasingly considering WS-Enumeration as an important part of the story. >From Felipe Cabrera of Microsoft: "Many scenarios require data exchange using more than just a single request/response message pair. Types of applications that require these longer data exchanges include database queries, data streaming, the traversal of information such as namespaces, and enumerating lists. Enumeration, in particular, is achieved through establishing a session between the data source and the requestor. This session is established using the Enumerate operation, which provides an enumeration context that is then used in subsequent operations. Successive messages within the session transport the collection of elements being retrieved. No assumptions are made on the approach used by the service to organize the items that will be produced. What is expected is that under normal processing circumstances, the enumeration will produce all the underlying data before the end of the session.... In its simplest form, WS-Enumeration defines a single operation, Pull, which allows a data source, in the context of a specific enumeration, to produce a sequence of XML elements in the body of a SOAP message.... Three more request/response operations are defined in WS-Enumeration: Renew, GetStatus, and Release.... State information regarding the progress of the iteration can be maintained between requests by either the data source or the consuming service.... In addition to enumerating the data entities present in a Web service, it is convenient to be able to perform several basic operations on them. These operations are introduced in the WS-Transfer operation." I hope this helps, Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia

1 0

Mapping of JSDL to CIM (Visio and PDFs)
by Andrea Westerinen (andreaw) 29 Jun '05

29 Jun '05

Presented this morning at the OGSA #7 meeting ... Andrea

1 0

NOW - OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Steven Newhouse 28 Jun '05

28 Jun '05

For those at GGF... this is starting in about 15 minutes. A BOF to discuss the creation of a WG to define an OGSA Basic Profile that builds upon a minimal set of simple web service specification. The ouput of the group would be a document, similar in nature to the OGSA WSRF Basic Profile that would allow OGSA services to be rendered using an alternative set of WS specifications. Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

draft presentation for OGSA outreach (status and future) session
by Hiro Kishimoto 28 Jun '05

28 Jun '05

Hi all, I've uploaded first cut presentation draft to GridForge. Please have a look and give me your feedback before 9am tomorrow. https://forge.gridforum.org/projects/ogsa-wg/document/OGSA-status-and-futur… Thanks, -- Hiro Kishimoto

2 1

Final edits on Profile Definition
by David Snelling 27 Jun '05

27 Jun '05

Folks, Here's what I did. 1) Accepted all edits including the changes I made, which are listed below. Feel free to object to these changes. Otherwise, the document is ready for the editor. 2) In section 4.4 there were two "should"s which I changed to "SHOULD"s as the section is generally proscriptive and therefore normative language is appropriate. 3) In section 5.2, I added the phrase ", when at the Proposed Recommendation stage of publication," two the first two paragraphs to make it clear when in the GGF process the rules apply. I felt the section header was not normative enough. That's all. Thank you everyone for making this document a complete project. I leave it to Andreas to post this version to GridForge and submit it to the editor as soon as possible. -- 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

GGF14 slide template
by Hiro Kishimoto 27 Jun '05

27 Jun '05

Hi GGF14 presenters, As usual, I've upload slide template to GridForge. If you need ppt template, please use this. https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_slide_template/… The file also includes template of session report for OGSA-WG #12 report session; Outcomes and achievements, Open Issues, and action items & next step. Session owners: Please fill in after your session and bring them to the session #12 (Thue 11am-12:30pm) or send them to me in advance. Thanks, -- Hiro Kishimoto

1 1

Tuesday noon session
by Andrew Grimshaw 27 Jun '05

27 Jun '05

All, I know many of you want to attend the MWS BOF. However, I encourage you to attend the Tuesday noon OGSA session. Paul Strong from EGA will be presenting their reference model - and I think it is important that we all understand their perspective. Andrew.

1 0

[ogsa-wg | Roadmap - 1549] Roadmap Text From UniGrids (Dave Snelling)
by Sourceforge Tracker Monitor 26 Jun '05

26 Jun '05

A new artifact has been added: 1549 Submitted by: Jem Treadwell Submitted date: 2005-06-26 16:07:39 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=789&aid=1549&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=789&aid=1549&group_id…) Summary: Roadmap Text From UniGrids (Dave Snelling) Project: Open Grid Services Architecture Tracker: Roadmap Artifact ID: 1549 Category: <None> Group: <None> Status: Open Priority: 2 Last Modified By: Jem Treadwell Last Modified: 2005-06-26 16:07:39 Submitted By: Jem Treadwell Submit Date: 2005-06-26 16:07:39 Assigned To: Jem Treadwell File(s): <None> Description: Dave Snelling provided the following text for the OSS Projects section, after the start of Public Comment. Hiro and Jem, Here are some words from the UniGrids project, if it is not too late: The UniGrids project will develop a Grid Service infrastructure compliant with the Open Grid Services Architecture (OGSA), and based on the Web Service Resource Framework (WS-RF), and the UNICORE Grid software. The guiding principle of the project will be both to adopt and to influence standards in key project areas. The first version of Unicore/GS (the software developed by the UniGrids project) implements WS-RF, WS-Adressing and JSDL. In addition the second version of Unicore/GS will implement OGSA-BES and provide support for WS-Security, SAML Authorization, and WS-Notification. -- 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) View the Roadmap : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

RE: [ogsa-wg] Minor comments on documents
by Djaoui, A (Abdeslem) 25 Jun '05

25 Jun '05

IN this case There is already a WG that is working a major relevant spec for Info services. As this work progresses and we define the scope of info services better, there might be a need for new specs. IN that case a WG will be spawned. Abdeslem -----Original Message----- From: owner-ogsa-wg(a)ggf.org on behalf of Steven Newhouse Sent: Thu 6/23/2005 12:58 PM To: Djaoui, A (Abdeslem) Cc: Treadwell, Jem; Hiro Kishimoto; Tom Maguire; ogsa-wg Subject: Re: [ogsa-wg] Minor comments on documents > Should you add "or design teams" at the end. I am raising this because > for informations services there is no plan to form a WG. If there is substantial activity - and certainly if specs are to be written - I believe this should take place in its own WG. It keeps the role and activity of the main OGSA-WG clear and focussed. Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Dave Berry 25 Jun '05

25 Jun '05

After some thought, my current opinion is that the right time to start work on a new basic profile will be when all the relevant specifications have been submitted to standards bodies. In the meantime, I would encourage people to concentrate on all the higher-level questions that we have yet to resolve - including a framework for describing, naming and managing resources, data transfer, advance reservation, security, delegation, privacy, agreement negotiation, information monitoring and dissemination, data access and replication, workflow, etc. I think OGSA is most likely to fail if we focus on low-level issues at the expense of the larger operations which users actually need and want from us. This approach is also in keeping with the 'O' in OGSA, which stands in large part for Open Standards. (FWIW, this is also true of the 'O' in OMII). In line with this reasoning, I regret that I won't be attending this BOF - which is why I'm posting my opinion here. In fact my position was partly crystallised by the realisation that the other sessions that clash this BOF are more important to me. This is not a position about whether to have multiple basic profiles at all, just on the timing of new work. And of course it's just my opinion. Dave. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Dave Berry Sent: 22 June 2005 23:08 To: Marty Humphrey; Ogsa-Wg Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 Marty, The reason I asked about the status of the specifications was to clarify what sort of profile document could be produced at the present time. OGSA profiles are governed by a set of rules (https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-pr ofile-definition/en/12). Currently, if a group were to publish a profile document, it would have to be an Informational Profile. It could not be a Recommended Profile because the specifications are not yet in a standards body. Of course, this does not preclude people working on a draft profile with the intent of moving it into the publication process at some later date. I suggest that a question for the BOF to discuss is, given the above process, at what point does it become worth spending time on a draft profile? (I am not presuming an answer to this question one way or another). Switching to the question of WS-Enumeration, your answer seems to validate my initial concern. The issue that WS-Enumeration attempts to address is real and is considered in part by various working groups in the data area, but to me it doesn't seem part of a basic profile. Of course, the fact that I haven't seen a technical reason that links WS-Enumeration closely to the other specs doesn't mean that such a reason doesn't exist! Dave. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Marty Humphrey Sent: 22 June 2005 12:45 To: 'Ogsa-Wg' Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 > 1. Please could you clarify the status of WS-Transfer, WS-Eventing > and WS-Enumeration in the terms of the OGSA Profile template? I.e. > have they been submitted to an SDO, are they draft or evolving, etc.? As you know, there is a 4-step process by which these specs will become standards: [1] "Develop", in which the spec is published; [2] "Broader Participation", in which there are feedback and interop workshops (resulting in possibly revising and republishing the specs); [3] "Standardization", in which the specs are submitted to a standardization body, which then can modify the spec as well and eventually ratify; [4] "Profiles", in which a separate document shows how to *combine* specs, generally resulting in a "subsetting" of the original specs. On Dec 1, 2004, Intel hosted a "feedback" workshop (step [2]), above, for WS-Enumeration and WS-Transfer. The companies attending the workshop included AMD, Computer Associates, Dell, HP, IBM, Intel, Microsoft, SAP, Sharp, Sonic, Sun, veritas, et. al. Although I can't entirely confirm this, it looks like the following companies brought implementations of WS-Enumeration/WS-Transfer to this workshop: Microsoft, Dell, Intel, NetIQ, Sun, and WebMethods. On Feb 19, 2004, Tibco hosted a "feedback" workshop for WS-Eventing. Attendees included Microsoft, BEA, IBM, NEC, Sonic, etc. On April 15, 2004, Microsoft hosted an "interop" workshop on WS-Eventing ("The outcome of the workshop was the demonstration of interoperability among all the 7 implementations." The seven implementations were from BEA, Canon, Epson, Microsoft, Ricoh, Sonic, and Systinet.) It looks like there will be another WS-Eventing workshop, although the date/time have not been announced. The most recent specs are: -- WS-Eventing: Aug 2004 (Authors: IBM, BEA, Computer Associates, Microsoft, Sun, and Tibco). This new version modifies the original version (Jan 2004, I believe) to reflect the workshops. -- WS-Enumeration: Sept 2004 (Authors: Systinet, Microsoft, Sonic, BEA, Computer Associates). This is the first version of the spec. -- WS-Transfer: Sept 2004 (Authors: Systinet, Microsoft, Sonic, BEA, Computer Associates). This is the first version of the spec. There's an interesting graphic that shows some of the progress from Microsoft's perspective here: http://msdn.microsoft.com/webservices/graphics/workshop-timeline.gif (this is taken from http://msdn.microsoft.com/webservices/community/workshops/default.aspx) > 2. I can see that WS-Transfer specifies some of the functionality of > WSRF and WS-Eventing is largely equivalent to WS-BaseNotification, but > what has WS-Enumeration to do with this? From a brief reading, it > seems to specify functionality that is independent of either stack. I can see this point -- in our initial designs and experimentation with WS-Transfer and WS-Eventing, we chose to not utilize WS-Enumeration. But we are increasingly considering WS-Enumeration as an important part of the story. >From Felipe Cabrera of Microsoft: "Many scenarios require data exchange using more than just a single request/response message pair. Types of applications that require these longer data exchanges include database queries, data streaming, the traversal of information such as namespaces, and enumerating lists. Enumeration, in particular, is achieved through establishing a session between the data source and the requestor. This session is established using the Enumerate operation, which provides an enumeration context that is then used in subsequent operations. Successive messages within the session transport the collection of elements being retrieved. No assumptions are made on the approach used by the service to organize the items that will be produced. What is expected is that under normal processing circumstances, the enumeration will produce all the underlying data before the end of the session.... In its simplest form, WS-Enumeration defines a single operation, Pull, which allows a data source, in the context of a specific enumeration, to produce a sequence of XML elements in the body of a SOAP message.... Three more request/response operations are defined in WS-Enumeration: Renew, GetStatus, and Release.... State information regarding the progress of the iteration can be maintained between requests by either the data source or the consuming service.... In addition to enumerating the data entities present in a Web service, it is convenient to be able to perform several basic operations on them. These operations are introduced in the WS-Transfer operation." I hope this helps, Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia

1 0

OGSA Roadmap v1.0 submitted to GGF Editor
by Treadwell, Jem 24 Jun '05

24 Jun '05

Hi, The document is at http://tinyurl.com/7r5tg <http://tinyurl.com/7r5tg> and has also been uploaded to the GGF Editor project. I made a few final edits, accepted all changes, and also added Hiro as co-editor. Hiro was responsible for the structure and much of the early content, and will continue to work on it in the future. Thanks to everyone who contributed to this effort - see you in Chicago! - Jem ________________________________ 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

Profile Definition v14 uploaded
by Treadwell, Jem 24 Jun '05

24 Jun '05

Hi, I've uploaded v14 of the Profile Definition with some final edits. Dave S. will take a look at it over the weekend, and review all the changes. You can find the document at http://tinyurl.com/9fqx2. - Jem ________________________________ 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

OGSA-RSS BoF at GGF14
by Mathias Dalheimer 24 Jun '05

24 Jun '05

Dear all, please put the following date into your calendar: OGSA Resource Selection Services WG BoF Wednesday, June 29, 2005 2:00pm to 3:30pm Westin Michigan Avenue Hotel, Chicago, Regent 2 meeting room To get an idea of the services this group will focus on, documents planned, milestones and the group's relation to other GGF groups, please visit the preliminary web site at: http://h63759.serverkompetenz.net:8668//space/start The charter draft is here: http://h63759.serverkompetenz.net:8668//space/Charter+Discussion/draft-ggf-… Hope to see you in Chicago, Mathias

1 0

Teleconference minutes - 22 June 2005
by Andreas Savva 24 Jun '05

24 Jun '05

Minutes attached. Outline: GGF14 session preparation Profile definition review WSRF BP appendix E (security) review (minor) http://tinyurl.com/5fxfd/minutes-20050622/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 22 June 2005 ================================== * Participants Dave Berry (NeSC) Hiro Kishimoto (Fujitsu) Fred Maciel (Hitachi) Mark Morgan (UVa) Takuya Mori (NEC, ANL) Andreas Savva (Fujitsu) Jem Treadwel (HP) Apologies: Tom Maguire Minutes: Andreas Savva * Minutes approval Minutes of June 13, 15 and 20 approved with no changes. * GGF14 preparation Reviewed sessions and assignments ** Session 1 - Hiro and Tom to give overview of OGSA activities. - Jem and Tom to give overview of the three documents (Profile definition, WSRF Basic Profile, Roadmap). A more detailed look at the documents in session 3. ** Session 2 - Andrew to lead. - It conflicts with MWS-BoF. - Fred volunteered to lead this EGA session if Andrew decides to attend the MWS-BoF instead. ** Session 3 - More detailed look at Profile definition, WSRF BP and Roadmap documents. - Hiro is looking for a place to have the "Next Step" discussion. Since Tom will attend only on Tuesday Hiro is thinking of using part of this session. Action: Hiro to talk to Tom and arrange a slot for the "Next Step" discussion; possibly in this session. ** Session 4 - Andrew to lead. - DMTF Utility WG wants a half-hour for a presentation(?) - Note this is not the RSS-BoF. The BoF is on the next day. - Conflicts with a Resource management session. ** Session 5 - Since the OGSA Naming-WG has been approved this is not an OGSA-WG session anymore. ** Session 6 - Fred is looking for a minute taker. - This is a working session; focus is technical discussion. ** Session 7 - Fred is looking for a minute taker. - Resource Model discussion (another working session) - Unfortunately this conflicts with security, data transfer, etc. ** Session 8 - In-depth technical discussion about WSDM ** Session 9 - How to use WSDM in OGSA specifications - Plan is for - WSDM presentation - CDDLM presentation - OGSA BP presentation - Need someone to give this presentation or Fred may do it himself if there is a ready presentation. - Fred to look into using the slides from Session 3. (Probably Tom's.) (There is a separate WSDM demo session. But it conflicts with many OGSA sessions. Fred will ask for the WSDM demo to start early so that if people leave the town hall meeting early (say 15 minutes earlier) they can still have a look.) ** Session 10 Recently an OGSA-AuthZ document was submited. One topic here should be to clarify the role of this document since it uses the 'OGSA' name. There are also a number of data related security issues. But due to conflicts Dave B is planning to arrange a separate teleconf after GGF14 to discuss them. ** Session 11 Abdeslem is the owner of this session. Hiro will follow up with him. ** Session 12 - This is the design team review meeting. Unfortunately many people cannot attend: Tom, Fred, Takuya, and Frank. - Team leaders who cannot attend should write up slides and ask someone else to present them. ** Other There has been no request for a phone bridge for any session. Hiro is not planning not set up one this time. There is a WSDM F2F in the IBM building, approximately 1 mile away from the hotel. It will be on Thursday and Friday and WSDM TC members can attend. * Profile definition review Discussed the document state and how likely it is to be able to submit this week. It looks difficult but doable. But it may have to be a very short final call. In any case submitting at the end of this week is partly symbolic---the group can say the document was submitted at the outreach session at GGF14. - Reviewed Jem's version (later revised and uploaded to gridforge by Andreas as v1.013) - Reviewed revised table - Jem added legend and fixed the formatting of the table. - Discussed using 'document' to mean 'profile or specification' in certain cases. Agreed it's ok, if it is in a context that does not cause confusion. The usage should be explained in advance, perhaps by putting a sentence in the "Terminology" section. - Section 3.3: - Added text (bullets) as proposed by Hiro. But the two sets say similar things. Reduced to one. - Also made the distinction between the bullets clearer (mandatory/optional distinction). - Started making a distinction between 'profile' and 'Profile' - Andreas will re-check usage during his review (done) - Added statement that informational profile references must also be consistent. - Added acknowledgments. - Discussed whether to have separate Contributors but decided that it is not important for this document. - Discussed who to add. Looked up recent review meetings and put a list together. - The list needs to be reviewed. - Introduction - An introduction section is needed. - Andreas to do a first pass. (done) - Adoption of profile - It was discussed and agreed on an earlier call that it is not correct to talk about a profile being implemented/adopted. But some text is needed to explain why. - Drafted text (profiles define compliance targets not implemention targets) and Andreas will review and possibly revise. (done) - Review Dave S's comment on adding more explanation on why adoption level does not apply to the entire referenced specification but only to those parts that are used in a conformance target. - Added text and Andreas will review and possibly revise for next version (done). - Jem will send his working draft to Andreas. Andreas will revise and upload the next draft within the day. (done) * Basic Profile review Tom could not make the call. Reviewed some BP security issues with Takuya. - Andreas cannot confirm the security related artifacts on the BP tracker. He asked Takuya to check these and post a comment in each artifact whether it can be closed or not. Andreas will then close them. - Appendix E review (security) - A number of minor comments from Hiro. - l.782 WS-Addressing reference should be to 1.0 - l.785 Delete the line - l.810-830: The XML fragment needs reformating - l.830-845: Dangling references - Takuya to check comments on appendix E and make updates. (Talk with Tom about getting the pen on the document or just update the appendix and send it to Tom.)

1 0

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Fred Maciel 24 Jun '05

24 Jun '05

Marty, > FACT: Not everyone is enamored with WSRF, meaning that WSRF > is unlikely to > be "just there" in the tooling and infrastructure anytime soon. Re-read my e-mail again and tell me, where did I write "WSRF" there? You are putting words in my mouth. I don't care much what is used as a profile (if the IP of the protocols there is clear, and for instance I can write free software without nasty legal attacks -- I have an ugly scar on that one). What I care is that it's *one* profile, and things are interoperable. > OGSA-WG can choose to stick its collective head in the sand > and hope that > this issue goes away, By leaving the market choose, that's exactly what we are doing. :-) > Again, to stress, I personally just want convergence. That's exactly what I want too. Regards, Fred Maciel.

2 1

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Fred Maciel 23 Jun '05

23 Jun '05

Hi Steven, > > Try to steer the discusion past that one (or around it), so > that we can get > > to the next problem: > > The purpose of the BOF is to explore if there is interest in > developing > a second OGSA profile. I don't see this as a discussion point > within the > BoF unless their is overlap.. and isn't this what the GFSG examines? - When I sent that e-mail the agenda was not that clear, and in fact it still isn't -- it's time for a formal agenda listing what is going to be discussed, and especially what is *not* going to be discussed. Notice that I posted that e-mail as an attempt to make things clearer, and I'm saying that this subject is improductive and worth avoiding. - The word "second" above is important, because that's when it stops being "only one". So if the session leaders don't take care the "(1) Are multiple base profiles OK to begin with?" subject will come up, directly or indirectly, and a lot of time will be wasted in religious discussions among people who disagree with the GFSG policy. > > (3) What are the plans for the "WS-I-only" profile? > > What is being proposed is not a WS-I only OGSA profile. WS-I (basic & > security profiles) define a set of specifications and how Just to clarify, the use of quotation marks above was intentional due to the lack of a name, and I agree with what you said. > > I agree multiple basic profiles are bad idea wrt interoperability > > and architecture perspective. > > But may be critical to wider grid adoption which is why I believe GGF > accepts multiple approaches. IMHO it is a pity that this policy still > seems to be resisted... may be we should drop the O in OGSA? > > Recall, that the 'OGSI profile' did not gain wide adoption. Exploring > different approaches can only help to improve understanding. What is > important IMHO is to bring all approaches into a standards process so > that whatever mechanisms that are used are defined. Once > defined natural selection can drive their evolution. I won't be able to go to the MWS-BOF (I'll be in the OGSA-EGA session), so I'll leave my opinion registered here, very briefly. The risk is that if we leave it for the market to decide, the market won't choose against one or another profile, but it will choose against OGSA as a whole. The people willing to pay for OGSA functionality won't be able to get different components from different parties to work together because they won't fit the same profile, won't speak the same protocols, etc.. The fact that the architecture is theoretically unified will mean nothing because, from their point of view, in practice things simply do not work, period. OGSA as a brand will be meaningless. Who wins then? I have a few guesses, but I am not stupid enough to list them in public forum. Being sarcastic, on the letter "O", perhaps the GGF was truly Open around GGF6, when OGSA was just an architecture among many, nothing special. But the GFSG chose it as the "flagship architecture" of the GGF, stating at least a preference. Allowing multiple profiles without preferences moves things back in the direction of GGF6, which for some people is wonderful, and for others, disastrous. (Again, I'm being sarcastic, don't waste your time taking this too seriously). Regards, Fred Maciel Consensus is the absence of leadership -- Margaret Thatcher

3 2

Re: [ogsa-wg] Profile definition v13
by Tom Maguire 23 Jun '05

23 Jun '05

Yeah, I get it now. Checking on the history and starting internal discussions. 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 Davanum Srinivas <davanum(a)gmail.com> wrote on 06/23/2005 12:26:08 PM: > Tom, > > Have you read the IBM license for WS-Security > (http://www.ibm.com/ibm/licensing/977Q/2112.shtml) Apache will not > sign this license as-is. I can email you the details of our objections > to this license if you want me to. The concerns are VERY similar to > the concerns Apache had for sender-id > (http://www.apache.org/foundation/docs/sender-id-position.html) If > you read the IBM license (or Microsoft's) you will see that it is next > to impossible for an open source project to comply to the license > requirements. > > Thanks, > dims > > On 6/23/05, Tom Maguire <tmaguire(a)us.ibm.com> wrote: > > It is unclear to me after reading through the threads what is the license > > issue. > > > > 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 > > > > > > > > Steve Loughran > > <steve_loughran@h > > pl.hp.com> To > > Sent by: ogsa-wg <ogsa-wg(a)gridforum.org> > > owner-ogsa-wg@ggf cc > > .org davanum(a)gmail.com > > Subject > > Re: [ogsa-wg] Profile definition > > 06/23/2005 08:23 v13 > > AM > > > > > > > > > > > > > > > > > > > > Andreas Savva wrote: > > > I've uploaded v13 of the Profile definition. This includes a lot of > > > edits from Jem and from the review done in the last (yesterday) call. > > > > > > > > https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf- > ogsa-profile-definition/en/13 > > > > > > > > > > > > One little troublespot with the profile is that unless IBM and Microsoft > > are willing to adapt their IPR licensing policy for WSSecurity, there > > may shortly not be any functional open source WS-Security implementations > > > > the summary of the current state is: > > > > http://marc.theaimsgroup.com/?l=incubator-general&m=111894292828449&w=2 > > > > and the licenses in question are > > > > http://www.microsoft.com/mscorp/ip/standards/ > > http://www.ibm.com/ibm/licensing/977Q/2112.shtml > > > > Unless these two vendors come to an amenable position, there isn't going > > to be an apache implementation (and that includes an end to WSS4J), > > which is going to prevent it from entering the 'community' section, or > > being broadly used. > > > > Now, who was planning on using WSS4J in their products? > > > > -steve > > > > > > > -- > Davanum Srinivas -http://blogs.cocoondev.org/dims/

1 0

Profile definition v13
by Andreas Savva 23 Jun '05

23 Jun '05

I've uploaded v13 of the Profile definition. This includes a lot of edits from Jem and from the review done in the last (yesterday) call. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-profil… Tom, Dave: Since you are the authors, one (or both) of you should review and accept or reject changes. Especially the ones that may affect the intended meaning. -- Andreas Savva

4 3

RE: [ogsa-wg] Minor comments on documents
by Treadwell, Jem 23 Jun '05

23 Jun '05

Hmm, it seems to me that they're more likely to be written by other groups than by OGSA-WG, and OGSA-WG should also be considered a domain-expert group, so I don't see any reason to call us out explicitly. For now I've removed "and their design teams" phrase - does anyone have any objection to just leaving it like that? Note also that in the intro para we do say that OGSA-WG "manages" the overall process. - Jem > -----Original Message----- > From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com] > Sent: Thursday, June 23, 2005 12:23 AM > To: Andreas Savva > Cc: Treadwell, Jem; Djaoui, A (Abdeslem); ogsa-wg > Subject: Re: [ogsa-wg] Minor comments on documents > > Hi Andreas, Jem, Abdeslem, > > I agree with Andreas. How about the following? > > "which are written and maintained by the OGSA-WG or the > appropriate domain-expert working groups" > > Thanks, > ---- > Hiro Kishimoto > > Andreas Savva wrote: > > Jem, Abdeslem > > > > I think it's inappropriate to mention design teams in this context, > > since they do not have a formal role. The document itself would be > > labelled as the output of the working group, not of the design team. > > > > Treadwell, Jem wrote: > > > >> Hi Abdeslem, my first thought was that that's too low > level, but we > >> do mention design teams elsewhere in the doc, so I've added it to > >> both of these bullets. > >> > >> Thanks, > >> > >> - Jem > >> > >> > >> > >>> -----Original Message----- > >>> From: owner-ogsa-wg(a)ggf.org > [mailto:owner-ogsa-wg@ggf.org] On Behalf > >>> Of Djaoui, A (Abdeslem) > >>> Sent: Wednesday, June 22, 2005 11:20 AM > >>> To: Treadwell, Jem; Hiro Kishimoto; Steven Newhouse; Tom Maguire > >>> Cc: ogsa-wg > >>> Subject: RE: [ogsa-wg] Minor comments on documents > >>> > >>> Jem > >>> > >>> After your sentence > >>> > >>> > >>>> Service Description documents, which are written and > >>> > >>> maintained by the > >>> > >>>> appropriate domain-expert working groups, > >>>> > >>> > >>> Should you add "or design teams" at the end. I am raising this > >>> because for informations services there is no plan to form a WG. > >>> > >>> Abdeslem > >>> > >>> -----Original Message----- > >>> From: owner-ogsa-wg(a)ggf.org > [mailto:owner-ogsa-wg@ggf.org]On Behalf > >>> Of Treadwell, Jem > >>> Sent: Wednesday, June 22, 2005 3:21 PM > >>> To: Hiro Kishimoto; Steven Newhouse; Tom Maguire > >>> Cc: ogsa-wg > >>> Subject: RE: [ogsa-wg] Minor comments on documents > >>> > >>> > >>> Hiro/Steve/Tom, > >>> > >>> My comments also embedded... > >>> > >>> > >>> > >>>> -----Original Message----- > >>>> From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] > >>> > >>> On Behalf > >>> > >>>> Of Hiro Kishimoto > >>>> Sent: Wednesday, June 22, 2005 9:29 AM > >>>> To: Steven Newhouse > >>>> Cc: ogsa-wg > >>>> Subject: Re: [ogsa-wg] Minor comments on documents > >>>> > >>>> Thanks Steven, > >>>> > >>>> My comments inline <HK>. > >>>> ---- > >>>> Hiro Kishimoto > >>>> > >>>> Steven Newhouse wrote: > >>>> > >>>> > >>>>> OGSA WSRF Basic Profile 1.0 (v018 June 13th 2005) > >>>>> > >>>>> Page 1: Status of this memo > >>>>> Is there not a WSRF missing from this opening line? > >>>>> e.g. '... write normative OGSA services based around the > >>>>> > >>>> > >>>> WSRF set of > >>>> > >>>> > >>>>> specifications.' > >>>>> > >>>> > >>>> <HK> > >>>> Good catch! Your text works for me. > >>>> </HK> > >>>> > >>> > >>> JT: I'll leave this one for Tom, as he has the pen again > right now. > >>> > >>> > >>> > >>>>> OGSA Roadmap (v010 June 6th 2005) > >>>>> > >>>>> Section 2, Point 1, Bullet 3: Should these service description > >>>>> documents not be 'owned' by the working group developing > >>>>> > >>>> > >>>> the service? > >>>> > >>>> > >>>>> The text implies to me that the OGSA-WG writes them... > >>>>> > >>>> > >>>> which I don't > >>>> > >>>> > >>>>> think is the case. > >>>>> > >>>> > >>>> <HK> > >>>> Good point. Let's add something like "domain-expert WG > writes this > >>>> service description (scenario document) if appropriate." > >>>> </HK> > >>>> > >>> > >>> JT: Here's my update, in line (I think!) with Hiro's suggestion: > >>> > >>> * Service Description documents, which are written and > maintained by > >>> the appropriate domain-expert working groups, describe > the services > >>> in the area in natural language, listing the interfaces and > >>> operations defined by each service. > >>> > >>> * Scenario documents, also written by domain-expert > working groups, > >>> demonstrate how these services can implement the use > cases, using a > >>> combination of natural language and UML. > >>> > >>> > >>> > >>>>> Section 2.2: > >>>>> Should there not be some statement that OGSA profiles should be > >>>>> developed/revised outside the OGSA-WG in theor own WG? > >>>>> > >>>> > >>>> <HK> > >>>> I think they can if their Profile abide by OGSA branding > guideline. > >>>> </HK> > >>>> > >>> > >>> JT: I inserted this text at what is now line 199, > *before* the para > >>> beginning "Members of the OGSA-WG": > >>> OGSA Recommended and Informational Profiles may be > developed either > >>> by the OGSA-WG or by domain-expert working groups, but it is > >>> important to note that they must adhere to GGF's forthcoming OGSA > >>> branding guidelines, which are discussed in section 2.3. > >>> > >>> Let me know if you see any issues with this, as I'll be > posting this > >>> for final call very soon. > >>> > >>> Thanks! > >>> > >>> - Jem > >>> > >>> > >> > >> > >> > >> > > > > > > >

1 0

RE: [ogsa-wg] Minor comments on documents
by Djaoui, A (Abdeslem) 23 Jun '05

23 Jun '05

Jem After your sentence > Service Description documents, which are written and maintained by the > appropriate domain-expert working groups, Should you add "or design teams" at the end. I am raising this because for informations services there is no plan to form a WG. Abdeslem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org]On Behalf Of Treadwell, Jem Sent: Wednesday, June 22, 2005 3:21 PM To: Hiro Kishimoto; Steven Newhouse; Tom Maguire Cc: ogsa-wg Subject: RE: [ogsa-wg] Minor comments on documents Hiro/Steve/Tom, My comments also embedded... > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Hiro Kishimoto > Sent: Wednesday, June 22, 2005 9:29 AM > To: Steven Newhouse > Cc: ogsa-wg > Subject: Re: [ogsa-wg] Minor comments on documents > > Thanks Steven, > > My comments inline <HK>. > ---- > Hiro Kishimoto > > Steven Newhouse wrote: > > OGSA WSRF Basic Profile 1.0 (v018 June 13th 2005) > > > > Page 1: Status of this memo > > Is there not a WSRF missing from this opening line? > > e.g. '... write normative OGSA services based around the > WSRF set of > > specifications.' > > <HK> > Good catch! Your text works for me. > </HK> JT: I'll leave this one for Tom, as he has the pen again right now. > > > OGSA Roadmap (v010 June 6th 2005) > > > > Section 2, Point 1, Bullet 3: Should these service description > > documents not be 'owned' by the working group developing > the service? > > The text implies to me that the OGSA-WG writes them... > which I don't > > think is the case. > > <HK> > Good point. Let's add something like "domain-expert WG writes > this service description (scenario document) if appropriate." > </HK> JT: Here's my update, in line (I think!) with Hiro's suggestion: * Service Description documents, which are written and maintained by the appropriate domain-expert working groups, describe the services in the area in natural language, listing the interfaces and operations defined by each service. * Scenario documents, also written by domain-expert working groups, demonstrate how these services can implement the use cases, using a combination of natural language and UML. > > Section 2.2: > > Should there not be some statement that OGSA profiles should be > > developed/revised outside the OGSA-WG in theor own WG? > > <HK> > I think they can if their Profile abide by OGSA branding guideline. > </HK> JT: I inserted this text at what is now line 199, *before* the para beginning "Members of the OGSA-WG": OGSA Recommended and Informational Profiles may be developed either by the OGSA-WG or by domain-expert working groups, but it is important to note that they must adhere to GGF's forthcoming OGSA branding guidelines, which are discussed in section 2.3. Let me know if you see any issues with this, as I'll be posting this for final call very soon. Thanks! - Jem

2 1

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Dave Berry 23 Jun '05

23 Jun '05

Marty, I don't know how much debate you want on the list before the BOF itself, but could you perhaps answer two questions to help set the context? 1. Please could you clarify the status of WS-Transfer, WS-Eventing and WS-Enumeration in the terms of the OGSA Profile template? I.e. have they been submitted to an SDO, are they draft or evolving, etc.? 2. I can see that WS-Transfer specifies some of the functionality of WSRF and WS-Eventing is largely equivalent to WS-BaseNotification, but what has WS-Enumeration to do with this? From a brief reading, it seems to specify functionality that is independent of either stack. Dave. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Marty Humphrey Sent: 21 June 2005 15:28 To: 'Ogsa-Wg' Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 Hi Ian et. al., A very good question! ("can you define the goals of the BOF more precisely other than "not WSRF"?) I sent this email in part to hear from the community how "broad" they might like it to be. That is, we're being flexible. If someone wants to talk about one of these specific topics, we will certainly try our best to accommodate. Note that by default I believe the discussions will center around WS-Transfer, WS-Enumeration, WS-Eventing, et. al. I will talk about my team's use of WS-Transfer, WS-Enumeration, and WS-Eventing. I think we're in a very good position to discuss the pros and cons of these specs as compared with WSRF (as our project has implemented/used both). Let me answer the question in a different way. GGF Chair Mark Linesch said recently: "Our approach with the OGSA architecture along with our collaborative work on OGSA profiles is to: (1) describe 'the most traveled paths through the forest' rather than to dictate that there is only one path; and (2) to continue to highlight that multiple, overlapping paths may not be in the interests of the industry over time" (http://news.taborcommunications.com/msgget.jsp?mid=403500&xsl=story.xsl) Simply, we believe that there has been sufficient "hallway discussions" on BOTH (1) and (2) that it makes good sense to gather people to discuss BOTH of these topics in a realistic and productive way. - Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia ________________________________________ From: Ian Foster [mailto:foster@mcs.anl.gov] Sent: Tuesday, June 21, 2005 9:54 AM To: Marty Humphrey; 'Ogsa-Wg' Cc: 'Marty Humphrey' Subject: Re: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 Marty, Steven: It is of course feasible, in principle, to define many different profiles for OGSA. E.g., one could build one on WS-Transfer and friends, one could build one that uses a different construct than the WS-Addressing EPR to address things, one could define one that uses JINI mechanisms, one could define one that uses CORBA, one could define one that renames all of the current WSRF and WS-Notification calls to be slightly different (oh wait, that's the first in the list (-: ), etc. Given the wide variety of possible alternative profiles, it would be helpful for those like me who are considering attending the BOF to know what more specifically what the goal of this work is going to be. The name doesn't provide any information, other than to imply, perhaps, that the interfaces on which the WSRF profile builds are not in some manner "minimal" and/or "simple." I.e., can you define the goals of the BOF more precisely other than "not WSRF"? Regards -- Ian. At 09:11 AM 6/21/2005 -0400, Marty Humphrey wrote: Folks, There have been a number of informal conversations lately about the feasibility/value/implications of a possible non-WSRF-based profile for OGSA. To bring all interested parties together at the same time, a BOF has been scheduled for Tuesday June 28 noon-1:30 (unfortunately at the same time as the EGA session, but there were no good times available). The agenda is still being finalized, but we expect to broadly discuss the pros/cons of such an effort, and, if the BOF attendees decide that such an effort would be valuable, produce a concrete plan for the formation of a Working Group. Here is the information that Steven Newhouse provided for the GGF organizers: "A BOF meeting to discuss the creation of a WG to define an OGSA Basic Profile that builds upon a minimal set of simple web services. The output of the group would be a document, similar in nature to the OGSA WSRF Basic Profile that would allow OGSA services to be rendered using an alternative set of WS specifications." I hope you can attend this (hopefully) productive and constructive session! -- Marty and Steven Marty Humphrey Assistant Professor Department of Computer Science University of Virginia _______________________________________________________________ Ian Foster www.mcs.anl.gov/~foster Math & Computer Science Div. Dept of Computer Science Argonne National Laboratory The University of Chicago Argonne, IL 60439, U.S.A. Chicago, IL 60637, U.S.A. Tel: 630 252 4619 Fax: 630 252 1997 Globus Alliance, www.globus.org

4 9

RE: [ogsa-wg] Minor comments on documents
by Treadwell, Jem 23 Jun '05

23 Jun '05

Hi Abdeslem, my first thought was that that's too low level, but we do mention design teams elsewhere in the doc, so I've added it to both of these bullets. Thanks, - Jem > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Djaoui, A (Abdeslem) > Sent: Wednesday, June 22, 2005 11:20 AM > To: Treadwell, Jem; Hiro Kishimoto; Steven Newhouse; Tom Maguire > Cc: ogsa-wg > Subject: RE: [ogsa-wg] Minor comments on documents > > Jem > > After your sentence > > Service Description documents, which are written and > maintained by the > > appropriate domain-expert working groups, > > Should you add "or design teams" at the end. I am raising > this because for informations services there is no plan to form a WG. > > Abdeslem > > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org]On > Behalf Of Treadwell, Jem > Sent: Wednesday, June 22, 2005 3:21 PM > To: Hiro Kishimoto; Steven Newhouse; Tom Maguire > Cc: ogsa-wg > Subject: RE: [ogsa-wg] Minor comments on documents > > > Hiro/Steve/Tom, > > My comments also embedded... > > > -----Original Message----- > > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] > On Behalf > > Of Hiro Kishimoto > > Sent: Wednesday, June 22, 2005 9:29 AM > > To: Steven Newhouse > > Cc: ogsa-wg > > Subject: Re: [ogsa-wg] Minor comments on documents > > > > Thanks Steven, > > > > My comments inline <HK>. > > ---- > > Hiro Kishimoto > > > > Steven Newhouse wrote: > > > OGSA WSRF Basic Profile 1.0 (v018 June 13th 2005) > > > > > > Page 1: Status of this memo > > > Is there not a WSRF missing from this opening line? > > > e.g. '... write normative OGSA services based around the > > WSRF set of > > > specifications.' > > > > <HK> > > Good catch! Your text works for me. > > </HK> > > JT: I'll leave this one for Tom, as he has the pen again right now. > > > > > > OGSA Roadmap (v010 June 6th 2005) > > > > > > Section 2, Point 1, Bullet 3: Should these service description > > > documents not be 'owned' by the working group developing > > the service? > > > The text implies to me that the OGSA-WG writes them... > > which I don't > > > think is the case. > > > > <HK> > > Good point. Let's add something like "domain-expert WG writes this > > service description (scenario document) if appropriate." > > </HK> > > JT: Here's my update, in line (I think!) with Hiro's suggestion: > > * Service Description documents, which are written and > maintained by the appropriate domain-expert working groups, > describe the services in the area in natural language, > listing the interfaces and operations defined by each service. > > * Scenario documents, also written by domain-expert working > groups, demonstrate how these services can implement the use > cases, using a combination of natural language and UML. > > > > Section 2.2: > > > Should there not be some statement that OGSA profiles should be > > > developed/revised outside the OGSA-WG in theor own WG? > > > > <HK> > > I think they can if their Profile abide by OGSA branding guideline. > > </HK> > > JT: I inserted this text at what is now line 199, *before* > the para beginning "Members of the OGSA-WG": > > OGSA Recommended and Informational Profiles may be developed > either by the OGSA-WG or by domain-expert working groups, but > it is important to note that they must adhere to GGF's > forthcoming OGSA branding guidelines, which are discussed in > section 2.3. > > Let me know if you see any issues with this, as I'll be > posting this for final call very soon. > > Thanks! > > - Jem > >

3 2

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Dave Berry 22 Jun '05

22 Jun '05

Marty, The reason I asked about the status of the specifications was to clarify what sort of profile document could be produced at the present time. OGSA profiles are governed by a set of rules (https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-pr ofile-definition/en/12). Currently, if a group were to publish a profile document, it would have to be an Informational Profile. It could not be a Recommended Profile because the specifications are not yet in a standards body. Of course, this does not preclude people working on a draft profile with the intent of moving it into the publication process at some later date. I suggest that a question for the BOF to discuss is, given the above process, at what point does it become worth spending time on a draft profile? (I am not presuming an answer to this question one way or another). Switching to the question of WS-Enumeration, your answer seems to validate my initial concern. The issue that WS-Enumeration attempts to address is real and is considered in part by various working groups in the data area, but to me it doesn't seem part of a basic profile. Of course, the fact that I haven't seen a technical reason that links WS-Enumeration closely to the other specs doesn't mean that such a reason doesn't exist! Dave. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Marty Humphrey Sent: 22 June 2005 12:45 To: 'Ogsa-Wg' Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 > 1. Please could you clarify the status of WS-Transfer, WS-Eventing > and WS-Enumeration in the terms of the OGSA Profile template? I.e. > have they been submitted to an SDO, are they draft or evolving, etc.? As you know, there is a 4-step process by which these specs will become standards: [1] "Develop", in which the spec is published; [2] "Broader Participation", in which there are feedback and interop workshops (resulting in possibly revising and republishing the specs); [3] "Standardization", in which the specs are submitted to a standardization body, which then can modify the spec as well and eventually ratify; [4] "Profiles", in which a separate document shows how to *combine* specs, generally resulting in a "subsetting" of the original specs. On Dec 1, 2004, Intel hosted a "feedback" workshop (step [2]), above, for WS-Enumeration and WS-Transfer. The companies attending the workshop included AMD, Computer Associates, Dell, HP, IBM, Intel, Microsoft, SAP, Sharp, Sonic, Sun, veritas, et. al. Although I can't entirely confirm this, it looks like the following companies brought implementations of WS-Enumeration/WS-Transfer to this workshop: Microsoft, Dell, Intel, NetIQ, Sun, and WebMethods. On Feb 19, 2004, Tibco hosted a "feedback" workshop for WS-Eventing. Attendees included Microsoft, BEA, IBM, NEC, Sonic, etc. On April 15, 2004, Microsoft hosted an "interop" workshop on WS-Eventing ("The outcome of the workshop was the demonstration of interoperability among all the 7 implementations." The seven implementations were from BEA, Canon, Epson, Microsoft, Ricoh, Sonic, and Systinet.) It looks like there will be another WS-Eventing workshop, although the date/time have not been announced. The most recent specs are: -- WS-Eventing: Aug 2004 (Authors: IBM, BEA, Computer Associates, Microsoft, Sun, and Tibco). This new version modifies the original version (Jan 2004, I believe) to reflect the workshops. -- WS-Enumeration: Sept 2004 (Authors: Systinet, Microsoft, Sonic, BEA, Computer Associates). This is the first version of the spec. -- WS-Transfer: Sept 2004 (Authors: Systinet, Microsoft, Sonic, BEA, Computer Associates). This is the first version of the spec. There's an interesting graphic that shows some of the progress from Microsoft's perspective here: http://msdn.microsoft.com/webservices/graphics/workshop-timeline.gif (this is taken from http://msdn.microsoft.com/webservices/community/workshops/default.aspx) > 2. I can see that WS-Transfer specifies some of the functionality of > WSRF and WS-Eventing is largely equivalent to WS-BaseNotification, but > what has WS-Enumeration to do with this? From a brief reading, it > seems to specify functionality that is independent of either stack. I can see this point -- in our initial designs and experimentation with WS-Transfer and WS-Eventing, we chose to not utilize WS-Enumeration. But we are increasingly considering WS-Enumeration as an important part of the story. >From Felipe Cabrera of Microsoft: "Many scenarios require data exchange using more than just a single request/response message pair. Types of applications that require these longer data exchanges include database queries, data streaming, the traversal of information such as namespaces, and enumerating lists. Enumeration, in particular, is achieved through establishing a session between the data source and the requestor. This session is established using the Enumerate operation, which provides an enumeration context that is then used in subsequent operations. Successive messages within the session transport the collection of elements being retrieved. No assumptions are made on the approach used by the service to organize the items that will be produced. What is expected is that under normal processing circumstances, the enumeration will produce all the underlying data before the end of the session.... In its simplest form, WS-Enumeration defines a single operation, Pull, which allows a data source, in the context of a specific enumeration, to produce a sequence of XML elements in the body of a SOAP message.... Three more request/response operations are defined in WS-Enumeration: Renew, GetStatus, and Release.... State information regarding the progress of the iteration can be maintained between requests by either the data source or the consuming service.... In addition to enumerating the data entities present in a Web service, it is convenient to be able to perform several basic operations on them. These operations are introduced in the WS-Transfer operation." I hope this helps, Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia

2 1

RE: [ogsa-wg] call tonight
by Treadwell, Jem 22 Jun '05

22 Jun '05

FYI that I've picked up the pen again on the Definition doc, just in case anyone else is thinking about it - I'm addressing Hiro's comments. We can review it tonight. Tom, if you guys are getting the same weather we are I hope it's inside :0) - Jem > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Tom Maguire > Sent: Wednesday, June 22, 2005 4:59 PM > To: 'Ogsa-Wg' > Subject: [ogsa-wg] call tonight > > Folks, > > Apologize. When I suggested Wednesday for BP discussion I > had forgotten that my son's graduation is this evening. > > Tom > > BP 1.0 v020 is on GridForge > > > 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

call tonight
by Tom Maguire 22 Jun '05

22 Jun '05

Folks, Apologize. When I suggested Wednesday for BP discussion I had forgotten that my son's graduation is this evening. Tom BP 1.0 v020 is on GridForge 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

Final call for OGSA Roadmap v1.0
by Treadwell, Jem 22 Jun '05

22 Jun '05

Hi, v14 of the OGSA Roadmap has been uploaded to http://tinyurl.com/9ssa9. I plan to submit the document to the GGF Editor this Friday, June 24th, so the deadline for comments is either midnight Thursday June 24th, in whatever timezone you happen to be in, or 8am US/Eastern in absolute time. Any comments received after that will be assigned to a tracker, and addressed during the public comment period. Thanks to all who have commented and contributed - the level of detail we've been working at today tells me we must have nailed all the big issues pretty well :0) - Jem ________________________________ 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

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Djaoui, A (Abdeslem) 22 Jun '05

22 Jun '05

Hi For me the main issues to address are: A) Do we start from the web services design principle of COMPOSABILITY of specifications and profiles? B) If the answer is YES then how are we going to make sure that varoius new GGF profiles and specifications are indeed composable with each other. Once we have composable profiles it really doesn't matter how many profiles we have. You can use one them or all of them, it is less tidy than having one basic profile but its workable. If we throw away the design principle of composability, then I am afraid it is back to pre-OGSA pre-Web services era. Abdeslem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org]On Behalf Of Subramaniam, Ravi Sent: Wednesday, June 22, 2005 6:29 AM To: Ian Foster; Marty Humphrey; Ogsa-Wg Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 Hi Marty, The BOF and the motivations you describe sound like a good idea. It would be great to hear your perspectives especially since you have experience with the described specs (WS-RF/WSN and WS-T, WS-E, WS-Enum). I think this is also a good test for the general policy that OGSA has adopted of admitting different profiles that are consistent with the general architecture. There has been a discussion around "lack of interoperability" with multiple profiles but without visiting the profiles that are compatible with the architecture one cannot decide which is the most appropriate (from one or many of the criteria like implementation easy, expressiveness, composability etc). Prematurely deciding that only one profile is the right way to go may not be beneficial in the long run. Given the way the industry has evolved, there is a process of "natural selection" and the most sophisticated or theoretical best solution has not won out in most cases. I agree with Mark's observations. Theoretically the degrees of freedom in the number of profiles seem infinite but I don't think in reality it will pan out into the more than a few since the "affinity" of these specs to be in a profile would constrain the number. Having said this, it would still make sense to be concrete in your discussion of what would be the primary motivation of the BOF and subsequent WG. Your points in response to Ian's question could be added to the formal description of the intent of the BOF. Thanks for spawning this discussion. Ravi PS: I just read Fred's comments in this thread. I think his points make sense. You may want to state that the need for alternate profiles as a primary assumption (not to be debated) and move on to the salient aspects of what the alternate profiles to be debated in the BOF are. _____ From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Ian Foster Sent: Tuesday, June 21, 2005 7:43 AM To: Marty Humphrey; 'Ogsa-Wg' Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 Marty: Thanks, that makes a lot of sense. And Mark puts it nicely: poetically, even (-: Ian. At 10:28 AM 6/21/2005 -0400, Marty Humphrey wrote: Hi Ian et. al., A very good question! ("can you define the goals of the BOF more precisely other than "not WSRF"?) I sent this email in part to hear from the community how "broad" they might like it to be. That is, we're being flexible. If someone wants to talk about one of these specific topics, we will certainly try our best to accommodate. Note that by default I believe the discussions will center around WS-Transfer, WS-Enumeration, WS-Eventing, et. al. I will talk about my team's use of WS-Transfer, WS-Enumeration, and WS-Eventing. I think we're in a very good position to discuss the pros and cons of these specs as compared with WSRF (as our project has implemented/used both). Let me answer the question in a different way. GGF Chair Mark Linesch said recently: "Our approach with the OGSA architecture along with our collaborative work on OGSA profiles is to: (1) describe 'the most traveled paths through the forest' rather than to dictate that there is only one path; and (2) to continue to highlight that multiple, overlapping paths may not be in the interests of the industry over time" ( http://news.taborcommunications.com/msgget.jsp?mid=403500 <http://news.taborcommunications.com/msgget.jsp?mid=403500&xsl=story.xsl> &xsl=story.xsl) Simply, we believe that there has been sufficient "hallway discussions" on BOTH (1) and (2) that it makes good sense to gather people to discuss BOTH of these topics in a realistic and productive way. - Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia ________________________________________ From: Ian Foster [ mailto:foster@mcs.anl.gov] Sent: Tuesday, June 21, 2005 9:54 AM To: Marty Humphrey; 'Ogsa-Wg' Cc: 'Marty Humphrey' Subject: Re: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 Marty, Steven: It is of course feasible, in principle, to define many different profiles for OGSA. E.g., one could build one on WS-Transfer and friends, one could build one that uses a different construct than the WS-Addressing EPR to address things, one could define one that uses JINI mechanisms, one could define one that uses CORBA, one could define one that renames all of the current WSRF and WS-Notification calls to be slightly different (oh wait, that's the first in the list (-: ), etc. Given the wide variety of possible alternative profiles, it would be helpful for those like me who are considering attending the BOF to know what more specifically what the goal of this work is going to be. The name doesn't provide any information, other than to imply, perhaps, that the interfaces on which the WSRF profile builds are not in some manner "minimal" and/or "simple." I.e., can you define the goals of the BOF more precisely other than "not WSRF"? Regards -- Ian. At 09:11 AM 6/21/2005 -0400, Marty Humphrey wrote: Folks, There have been a number of informal conversations lately about the feasibility/value/implications of a possible non-WSRF-based profile for OGSA. To bring all interested parties together at the same time, a BOF has been scheduled for Tuesday June 28 noon-1:30 (unfortunately at the same time as the EGA session, but there were no good times available). The agenda is still being finalized, but we expect to broadly discuss the pros/cons of such an effort, and, if the BOF attendees decide that such an effort would be valuable, produce a concrete plan for the formation of a Working Group. Here is the information that Steven Newhouse provided for the GGF organizers: "A BOF meeting to discuss the creation of a WG to define an OGSA Basic Profile that builds upon a minimal set of simple web services. The output of the group would be a document, similar in nature to the OGSA WSRF Basic Profile that would allow OGSA services to be rendered using an alternative set of WS specifications." I hope you can attend this (hopefully) productive and constructive session! -- Marty and Steven Marty Humphrey Assistant Professor Department of Computer Science University of Virginia _______________________________________________________________ Ian Foster www.mcs.anl.gov/~foster Math & Computer Science Div. Dept of Computer Science Argonne National Laboratory The University of Chicago Argonne, IL 60439, U.S.A. Chicago, IL 60637, U.S.A. Tel: 630 252 4619 Fax: 630 252 1997 Globus Alliance, www.globus.org <http://www.globus.org/> _______________________________________________________________ Ian Foster www.mcs.anl.gov/~foster Math & Computer Science Div. Dept of Computer Science Argonne National Laboratory The University of Chicago Argonne, IL 60439, U.S.A. Chicago, IL 60637, U.S.A. Tel: 630 252 4619 Fax: 630 252 1997 Globus Alliance, www.globus.org <http://www.globus.org/>

3 3

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Djaoui, A (Abdeslem) 22 Jun '05

22 Jun '05

Please see inlined comments <AD/>. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org]On Behalf Of Marty Humphrey Sent: Wednesday, June 22, 2005 4:57 PM To: 'Ogsa-Wg' Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 I want to clarify this ... Yes, composability is certainly important, both with regard to the specifications/standards as well as the profiles. With regard to composability of *profiles*, everyone agrees that WS-I BP 1.1 supports composability, and WS-I "Simple SOAP Binding Profile 1.0" and WS-I "Attachments Profile 1.0" support composability, but no one would attempt to layer WS-I "Simple SOAP Binding Profile 1.0" onto WS-I "Attachments Profile 1.0" (or the other way around). So they're not "composable" in this sense. <AD> Yes I agree the change from BP 1.0 to 1.1 was partly driven by a need to allow COMPOSITION of RELEVANT profiles. For the the example 3 profiles above: If your web service is not using attachement you would compose BP 1.1 with SSBP1.0, if it is using attachements you will need to compose BP1.1 and AP1.0. These can be seen as different bindings. >From a user point of view these are the only meaningful compositions (you either want to use SOAP with attachement or without.). When there is a tight coupling between profiles, the profile document itself should state how it is intended to be used or composed with other profiles. If other binding protocols become available (MTOM for example) you would need BP1.1 with MTOM 1.0 or whatever. But of course you web service could support many bindings .... But I take your point that some compositions might not make sense. </AD> I see an analogous situation for some (all?) "OGSA Profiles" -- particularly the WSRF Profile and any potential profile coming out of this BOF. <AD> If by analogous situation you mean non composable, I disagree. A more sensible approach would be to allow all OGSA basic profiles to be implemented together, (although higher related profiles will only compose with their corresponding profile). This is starightforward when the profiles rely on different specifications. When they refer the same specification, care should be taken not to have contradictory statements that lead to non-composability problems. </AD> Note that you might say that a WSRF profile could layer on a "WS-I OGSA Profile", but then I would question the very existence/purpose of this "WS-I OGSA Profile" (as it would seem to add no functionality above WS-I Basic Profile 1.1 and WS-I Basic Security Profile 1.0). <AD> Yes I agree. I was thinking more along the lines of a new profile based on WS-Transfer and WS-Eventing. The new profile and WSRF profile should be made to live happily together. So people will have the choice of two OGSA stacks. But there shouldn't be anything stopping them from implementing both stacks. Abdeslem </AD> -- Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia > -----Original Message----- > From: Tom Maguire [mailto:tmaguire@us.ibm.com] > Sent: Wednesday, June 22, 2005 8:01 AM > To: Djaoui, A (Abdeslem) > Cc: Ian Foster; Marty Humphrey; Ogsa-Wg; owner-ogsa-wg(a)ggf.org; > Subramaniam, Ravi > Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 > > +1 to the composabiltiy aspect. Certainly you should be able to compose > any number of profiles together. Each one with their > own comformance claim. > > 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 > > > > "Djaoui, A > (Abdeslem)" > <A.Djaoui(a)rl.ac.u To > k> "Subramaniam, Ravi" > Sent by: <ravi.subramaniam(a)intel.com>, "Ian > owner-ogsa-wg@ggf Foster" <foster(a)mcs.anl.gov>, > .org "Marty Humphrey" > <humphrey(a)cs.virginia.edu>, > "Ogsa-Wg" <ogsa-wg(a)gridforum.org> > 06/22/2005 06:36 cc > AM > Subject > RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 > on Tues June 28, noon-1:30 > > > > > > > > > > > Hi > > For me the main issues to address are: > A) Do we start from the web services design principle of COMPOSABILITY of > specifications and profiles? > B) If the answer is YES then how are we going to make sure that varoius > new > GGF profiles and specifications are indeed composable with each other. > Once we have composable profiles it really doesn't matter how many > profiles > we have. You can use one them or all of them, it is less tidy than having > one basic profile but its workable. > If we throw away the design principle of composability, then I am afraid > it > is back to pre-OGSA pre-Web services era. > > > Abdeslem > > > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org]On Behalf > Of Subramaniam, Ravi > Sent: Wednesday, June 22, 2005 6:29 AM > To: Ian Foster; Marty Humphrey; Ogsa-Wg > Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, > noon-1:30 > > Hi Marty, > > The BOF and the motivations you describe sound like a good idea. It > would be great to hear your perspectives especially since you have > experience with the described specs (WS-RF/WSN and WS-T, WS-E, > WS-Enum). I think this is also a good test for the general policy > that OGSA has adopted of admitting different profiles that are > consistent with the general architecture. > > There has been a discussion around "lack of interoperability" with > multiple profiles but without visiting the profiles that are > compatible with the architecture one cannot decide which is the most > appropriate (from one or many of the criteria like implementation > easy, expressiveness, composability etc). Prematurely deciding that > only one profile is the right way to go may not be beneficial in the > long run. Given the way the industry has evolved, there is a process > of "natural selection" and the most sophisticated or theoretical > best > solution has not won out in most cases. I agree with Mark's > observations. Theoretically the degrees of freedom in the number of > profiles seem infinite but I don't think in reality it will pan out > into the more than a few since the "affinity" of these specs to be > in > a profile would constrain the number. > > Having said this, it would still make sense to be concrete in your > discussion of what would be the primary motivation of the BOF and > subsequent WG. Your points in response to Ian's question could be > added to the formal description of the intent of the BOF. > > Thanks for spawning this discussion. > > Ravi > > PS: I just read Fred's comments in this thread. I think his points > make sense. You may want to state that the need for alternate > profiles as a primary assumption (not to be debated) and move on to > the salient aspects of what the alternate profiles to be debated in > the BOF are. > > > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf > Of Ian Foster > Sent: Tuesday, June 21, 2005 7:43 AM > To: Marty Humphrey; 'Ogsa-Wg' > Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, > noon-1:30 > > Marty: > > Thanks, that makes a lot of sense. And Mark puts it nicely: > poetically, even (-: > > Ian. > > At 10:28 AM 6/21/2005 -0400, Marty Humphrey wrote: > > Hi Ian et. al., > > A very good question! ("can you define the goals of the BOF more > precisely > other than "not WSRF"?) I sent this email in part to hear from the > community > how "broad" they might like it to be. That is, we're being flexible. > If > someone wants to talk about one of these specific topics, we will > certainly > try our best to accommodate. > > Note that by default I believe the discussions will center around > WS-Transfer, WS-Enumeration, WS-Eventing, et. al. I will talk about > my > team's use of WS-Transfer, WS-Enumeration, and WS-Eventing. I think > we're in > a very good position to discuss the pros and cons of these specs as > compared > with WSRF (as our project has implemented/used both). > > Let me answer the question in a different way. GGF Chair Mark > Linesch > said > recently: "Our approach with the OGSA architecture along with our > collaborative work on OGSA profiles is to: (1) describe 'the most > traveled > paths through the forest' rather than to dictate that there is only > one > path; and (2) to continue to highlight that multiple, overlapping > paths may > not be in the interests of the industry over time" > ( > > http://news.taborcommunications.com/msgget.jsp?mid=403500&xsl=story.xsl > ) > Simply, we believe that there has been sufficient "hallway > discussions" on > BOTH (1) and (2) that it makes good sense to gather people to > discuss > BOTH > of these topics in a realistic and productive way. > > - Marty > > Marty Humphrey > Assistant Professor > Department of Computer Science > University of Virginia > > > ________________________________________ > From: Ian Foster [mailto:foster@mcs.anl.gov] > Sent: Tuesday, June 21, 2005 9:54 AM > To: Marty Humphrey; 'Ogsa-Wg' > Cc: 'Marty Humphrey' > Subject: Re: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, > noon-1:30 > > Marty, Steven: > > It is of course feasible, in principle, to define many different > profiles > for OGSA. E.g., one could build one on WS-Transfer and friends, one > could > build one that uses a different construct than the WS-Addressing EPR > to > address things, one could define one that uses JINI mechanisms, one > could > define one that uses CORBA, one could define one that renames all of > the > current WSRF and WS-Notification calls to be slightly different (oh > wait, > that's the first in the list (-: ), etc. > > Given the wide variety of possible alternative profiles, it would be > helpful > for those like me who are considering attending the BOF to know what > more > specifically what the goal of this work is going to be. The name > doesn't > provide any information, other than to imply, perhaps, that the > interfaces > on which the WSRF profile builds are not in some manner "minimal" > and/or > "simple." I.e., can you define the goals of the BOF more precisely > other > than "not WSRF"? > > Regards -- Ian. > > At 09:11 AM 6/21/2005 -0400, Marty Humphrey wrote: > > Folks, > > There have been a number of informal conversations lately about the > feasibility/value/implications of a possible non-WSRF-based profile > for > OGSA. > > To bring all interested parties together at the same time, a BOF has > been > scheduled for Tuesday June 28 noon-1:30 (unfortunately at the same > time as > the EGA session, but there were no good times available). The agenda > is > still being finalized, but we expect to broadly discuss the > pros/cons > of > such an effort, and, if the BOF attendees decide that such an effort > would > be valuable, produce a concrete plan for the formation of a Working > Group. > > Here is the information that Steven Newhouse provided for the GGF > organizers: > > "A BOF meeting to discuss the creation of a WG to define an OGSA > Basic > Profile that builds upon a minimal set of simple web services. The > output of > the group would be a document, similar in nature to the OGSA WSRF > Basic > Profile that would allow OGSA services to be rendered using an > alternative > set of WS specifications." > > I hope you can attend this (hopefully) productive and constructive > session! > > -- Marty and Steven > > Marty Humphrey > Assistant Professor > Department of Computer Science > University of Virginia > _______________________________________________________________ > Ian Foster www.mcs.anl.gov/~foster > Math & Computer Science Div. Dept of Computer Science > Argonne National Laboratory The University of Chicago > Argonne, IL 60439, U.S.A. Chicago, IL 60637, U.S.A. > Tel: 630 252 4619 Fax: 630 252 1997 > Globus Alliance, www.globus.org > > > _______________________________________________________________ > Ian Foster www.mcs.anl.gov/~foster > Math & Computer Science Div. Dept of Computer Science > Argonne National Laboratory The University of Chicago > Argonne, IL 60439, U.S.A. Chicago, IL 60637, U.S.A. > Tel: 630 252 4619 Fax: 630 252 1997 > Globus Alliance, www.globus.org >

1 0

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Fred Maciel 22 Jun '05

22 Jun '05

Hi all, > A very good question! ("can you define the goals of the BOF > more precisely other than "not WSRF"?) I sent this email in part to hear > from the community > how "broad" they might like it to be. That is, we're being > flexible. If someone wants to talk about one of these specific topics, we > will certainly try our best to accommodate. I think that different people will see this from different angles, and if we don't understand the different "problems" involved the BOF can get messy. So let me try to decompose the problem, hoping that it will help the steering of the BOF. (1) Are multiple base profiles OK to begin with? > Let me answer the question in a different way. GGF Chair Mark > Linesch said [...] Yes, but some of us (I included) think that multiple base profiles is a bad idea, no matter what Mark Linesch said. Suffices to say that this is a religious discussion, in which all sides have strong opinions beforehand, spend a long time in a heated discussion, but nobody is be able to change anybody else's opinion. The ones we had in the OGSA-WG weren't fun. Try to steer the discusion past that one (or around it), so that we can get to the next problem: (2) How do the protocols sets in this area (the WSRF+WSN set, and the WS-Transfer etc. set) compare to each other? That one should be an interesting one, especially to end FUD. I'm looking forward to what you have to say. That should give the background to: (3) What are the plans for the "WS-I-only" profile? > Here is the information that Steven Newhouse provided for the GGF > organizers: > > "A BOF meeting to discuss the creation of a WG to define an OGSA Basic > Profile that builds upon a minimal set of simple web services. The output of This seems to be the main subject of the BOF, right? As you said, you are being flexible, and you have an interest in (2), but if we don't take care we won't even get to (3) in 1 1/2 hour. Anything else? Regards, Fred Maciel Hitachi America R&D

4 4

ByteIO WG Status
by Mark Morgan 22 Jun '05

22 Jun '05

Hiro asked me to send out a short, 5 line status report for ByteIO. We are currently in the process of finishing the first draft, skeleton versions of both the recommendation document for ByteIO and for the Use Case Document. Our hope was to have these out before GGF but that isn't likely to quite happen. Instead, the documents will probably come out within a few weeks of GGF. In the mean time, discussions on the telecoms have lead us to adopt a dual interface model for byteio -- one supporting random block oriented access, and another for more stream like resources (i.e., with session state). These interfaces have in part been implemented in prototypes as proofs of concept. GGF will probably entail looking at these along with the use cases. -Mark -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.cs.virginia.edu mmm2a(a)virginia.edu (434) 982-2047

1 0

Teleconference minutes - 20 June 2005
by Andreas Savva 22 Jun '05

22 Jun '05

Minutes attached. Also https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050620/en/1 -- Andreas Savva OGSA Teleconference - 20 June 2005 ================================== * Participants Mike Behrens (R2AD, LLC) Francisco Vilar Brasileiro (UFCG) William Huey Hiro Kishimoto (Fujitsu) Takashi Kojo (NEC) Fred Maciel (Hitachi) Tom Maguire (IBM) Dejan Milojicic (HP) Andreas Savva (Fujitsu) Stuart Schaefer (Softricity) Ayla Debora Dantas de Souza (UFCG) Ravi Subramaniam (Intel) Jun Tatemura (NEC) Pete Ziu (Northrop Grumman) Apologies: Jay Unger, Andrew Grimshaw Minutes: Andreas Savva * CDDLM review The purpose of this preview is to prepare for the scheduled joint session at GGF14. CDDLM: Configuration Description, Deployment, and Lifecycle Management [Presentation available at https://forge.gridforum.org/projects/ogsa-wg/document/cddlm-ogsa-intro/en/1 ] This WG was seeded from work done for the SmartFrog research project. But there have been substantial contributions from other sources, namely Softricity, and NEC. The schedule has been aggressive. It has helped that the core number of members is small. There is a WSDM relation especially towards the end. CDDLM uses WSDM. There is also a relation with CIM. But CDDLM does not use CIM at the moment. (A joint session is planned to explore possibilities further.) The WG has two documents towards the end of the GGF publication pipeline: CDDLM Foundation and SmartFrog. There is also another document recently submitted: Configuration Description Language (XML spec.) Also the WG is doing a last call within the WG on two other documents: Deployment API and Component model. These documents conclude the work the WG set out for itself. CDDLM-WG has kept a low profile with respect to OGSA. Mostly due to the tight internal schedule but also because OGSA has been in flux. There is an understanding that the CDDLM-WG might have to revisit the first versions of its specifications and revise them; after getting implementation experience and to make them fit in OGSA better. There are three in-house reference implementations planned by HP, Softricity, NEC. Also an outside one (UFCG). CDDLM work uses WSDM. There have been a number of problems because of this decision but in general the group is happy with this choice. There is also thinking about doing an interop, picking up on the WSDM interop and adding own scenarios. CDDLM-WG would like to place itself on the OGSA Roadmap and also would like to know how it fits in the bigger OGSA picture. And what it might have to revise later to fit better in the architecture. There is also a relation with OASIS SDD TC and GGF ACS-WG. There might be a need to refactor the CDDLM specifications to fit better with the work planned by these groups. - Is CDDLM compliant with the WSDM specification? - The interfaces are based on the WSDM OASIS Standard. - WS-Addressing and WSRF are used. - The main problem has been the moving target that all these specs pose. Also the mismatch in the version of WS-Addressing specs that WSDM used (3 different versions) - Which parts of WSRF / WSN are used? - Get resource property, Query resource property - Base Notification - Resource lifetime - Joint sessions at GGF14 - CDDLM is most closely related to EMS. - BES assumes the container is already setup. But OGSA has not specified how that is done yet. So there is a clear point for CDDLM to plugin. In any case this is a good point to start the discussion. - Therefore the most appropriate OGSA sessions are sessions #4 (EMS Architecture, 6/28) and session #9 - Since few people in OGSA-WG are familiar with the CDDLM work a high level presentation and then drilling down would be a good way to start. - These sessions would be a good opportunity to start discussing the position of CDDLM in OGSA. - CDDLM-WG also has demos that they can show OGSA-WG - Also OGSA is planning a number of joint sessions with WSDM. This would be a good time for CDDLM-WG to ask questions or put forward requests to WSDM. (Especially since WSDM has a F2F planned for the next day.) - How is CDDLM planning to proceed? - Working in GGF has had a number of advantages. Keeping the number of participants small has allowed more progress in a short time. It is likely that some work will continue in GGF CDDLM-WG but might also refine or posibly move some work to other places. - Have to work out the CIM relation as well as relation to other groups. * GGF14 agenda review - Security session moved to 6/29; using the early bird session slot. - Noone on the call plans to join the GGF14 sessions by phone. Hiro will also ask on the list and if there is no interest he will *not* setup a bridge. - [2pm 6/29] WSDM Demo (perhaps on a blackberry or simulator) - There are many conflicts this time. But OGSA-WG cannot complain since it is using 12 sessions in total. - BES contact? Talk to Darren Pulsipher or Steve Newhouse; Andrew is on vacation. * Roadmap document review - Jem has made a number of changes based on feedback he received; including but not limited to Hiro's and Dave B's comments. - l.495: "CGS:" mention probably points to SRIM work. But CGS is no longer active and has handed that work over to DAIS. > Changed CGS to DAIS - l.465-470: Sentence deleted as unnecessary. - l.560-565: SCRM-WG will be formed this week. Also expect WS-Naming-WG to be approved. - l.394: needs revision (Jem to do and check with Mark) - Table 4.4: GWD-R-P is wrong. It should be GWD-R. Action: Andreas to send Jem the link to the document that defines the various document types (GFD.1) (done) Action: Andreas to send Jem the JSDL 1.0 link. (done) - Information and monitoring architecture section does not have any dates. (Only TBD). But there will not be discussion about this before GGF14. Agreed to leave it as is. - Is there a WS-addressing 1.0 implementation? - Amazon was mentioned as one company doing one. - IBM is doing an implementation. Also there is an Apache project doing an implementation. Action: Tom will check whether there is a public version of the BaseNotification 1.3 - BaseNotification 1.3 is draft and evolving - BaseNotification 1.2 is draft and not evolving - Reviewed all entries in the master spreadsheet, corrected them and added comments. Action: Jem will work out the last remaining details. He will then post a cleaned up copy to gridforge, announce a final call (within 1-2 days) and then submit to the GGF Editor. - Submit to the Editor deadline is Friday - Final call deadline is Thursday - Post cleaned up copy deadline is Tuesday or Wednesday latest. * Profile definition review - Andreas confirmed with Dave S and uploaded draft 11. - Accepted draft 10 changes; only new modifications show. These were reviewed last week and re-checked today. - Agreed that the Table does not have to be identical to the ones in the Roadmap or Profiles. It is enough to be reasonably close. Action: Jem will fix the table formatting, do an overall review and upload a new version. - There will be another review of this document on Wednesday * WSRF Basic Profile 1.0 review - The big change is in Appendix C. - Appendix A has also been updated - Appendix B: the extensibility points have been updated - Left the reference to BaseNotification to 1.2 - But will update to show changes to 1.3 - l.450: cleanup - l.395: Latha posted a comment about confusion around MUST/SHOULD usage. (The intention is not to encourage the use of UseNotify. But this will change again with the update to 1.3.) - If there is a public version of BaseNotification the BP will be updated to refer to 1.3 draft - Security followup (Marty's comment): Frank to provide some informative text. Otherwise waiting for followup during public comment. - Security writeup issue: Tom will confer with Takuya and update the specificaion. - A new version will be uploaded over the next couple of days. - A final review will be done at the next call (Wednesday). * GGF14 preparation - Jem will put some slides together for a Roadmap presenation. * Next call - WSRF Basic Profile and Profile Definition final review - GGF14 preparation

1 0

RE: [ogsa-wg] Minor comments on documents
by Treadwell, Jem 22 Jun '05

22 Jun '05

Hiro/Steve/Tom, My comments also embedded... > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Hiro Kishimoto > Sent: Wednesday, June 22, 2005 9:29 AM > To: Steven Newhouse > Cc: ogsa-wg > Subject: Re: [ogsa-wg] Minor comments on documents > > Thanks Steven, > > My comments inline <HK>. > ---- > Hiro Kishimoto > > Steven Newhouse wrote: > > OGSA WSRF Basic Profile 1.0 (v018 June 13th 2005) > > > > Page 1: Status of this memo > > Is there not a WSRF missing from this opening line? > > e.g. '... write normative OGSA services based around the > WSRF set of > > specifications.' > > <HK> > Good catch! Your text works for me. > </HK> JT: I'll leave this one for Tom, as he has the pen again right now. > > > OGSA Roadmap (v010 June 6th 2005) > > > > Section 2, Point 1, Bullet 3: Should these service description > > documents not be 'owned' by the working group developing > the service? > > The text implies to me that the OGSA-WG writes them... > which I don't > > think is the case. > > <HK> > Good point. Let's add something like "domain-expert WG writes > this service description (scenario document) if appropriate." > </HK> JT: Here's my update, in line (I think!) with Hiro's suggestion: * Service Description documents, which are written and maintained by the appropriate domain-expert working groups, describe the services in the area in natural language, listing the interfaces and operations defined by each service. * Scenario documents, also written by domain-expert working groups, demonstrate how these services can implement the use cases, using a combination of natural language and UML. > > Section 2.2: > > Should there not be some statement that OGSA profiles should be > > developed/revised outside the OGSA-WG in theor own WG? > > <HK> > I think they can if their Profile abide by OGSA branding guideline. > </HK> JT: I inserted this text at what is now line 199, *before* the para beginning "Members of the OGSA-WG": OGSA Recommended and Informational Profiles may be developed either by the OGSA-WG or by domain-expert working groups, but it is important to note that they must adhere to GGF's forthcoming OGSA branding guidelines, which are discussed in section 2.3. Let me know if you see any issues with this, as I'll be posting this for final call very soon. Thanks! - Jem

1 0

Minor comments on documents
by Steven Newhouse 22 Jun '05

22 Jun '05

OGSA WSRF Basic Profile 1.0 (v018 June 13th 2005) Page 1: Status of this memo Is there not a WSRF missing from this opening line? e.g. '... write normative OGSA services based around the WSRF set of specifications.' OGSA Roadmap (v010 June 6th 2005) Section 2, Point 1, Bullet 3: Should these service description documents not be 'owned' by the working group developing the service? The text implies to me that the OGSA-WG writes them... which I don't think is the case. Section 2.2: Should there not be some statement that OGSA profiles should be developed/revised outside the OGSA-WG in theor own WG? Cheers, Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

2 1

Profile definition draft 12 uploaded
by Treadwell, Jem 22 Jun '05

22 Jun '05

Hi, I fixed the table and made some other minor edits, and I've now uploaded Profile Definition v12. It's available at http://tinyurl.com/93mpp. - Jem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Andreas Savva Sent: Monday, June 20, 2005 8:51 AM To: 'ogsa-wg' Subject: [ogsa-wg] Profile definition draft 11 uploaded I've uploaded draft 11 of the OGSA Profile Definition. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-pro file-definition/en/11 The changes were described in a previous email by Hiro last week, and also discussed during the Wed. call. (http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/06/msg00063.htm l) Draft 11 is basically the same as draft 10-a that was attached to Hiro's email. I made some additional minor revisions and cleanup: accepting old changes and deleting obsolete comments. -- Andreas Savva

2 2

RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30
by Subramaniam, Ravi 22 Jun '05

22 Jun '05

Hi Marty, The BOF and the motivations you describe sound like a good idea. It would be great to hear your perspectives especially since you have experience with the described specs (WS-RF/WSN and WS-T, WS-E, WS-Enum). I think this is also a good test for the general policy that OGSA has adopted of admitting different profiles that are consistent with the general architecture. There has been a discussion around "lack of interoperability" with multiple profiles but without visiting the profiles that are compatible with the architecture one cannot decide which is the most appropriate (from one or many of the criteria like implementation easy, expressiveness, composability etc). Prematurely deciding that only one profile is the right way to go may not be beneficial in the long run. Given the way the industry has evolved, there is a process of "natural selection" and the most sophisticated or theoretical best solution has not won out in most cases. I agree with Mark's observations. Theoretically the degrees of freedom in the number of profiles seem infinite but I don't think in reality it will pan out into the more than a few since the "affinity" of these specs to be in a profile would constrain the number. Having said this, it would still make sense to be concrete in your discussion of what would be the primary motivation of the BOF and subsequent WG. Your points in response to Ian's question could be added to the formal description of the intent of the BOF. Thanks for spawning this discussion. Ravi PS: I just read Fred's comments in this thread. I think his points make sense. You may want to state that the need for alternate profiles as a primary assumption (not to be debated) and move on to the salient aspects of what the alternate profiles to be debated in the BOF are. ________________________________ From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Ian Foster Sent: Tuesday, June 21, 2005 7:43 AM To: Marty Humphrey; 'Ogsa-Wg' Subject: RE: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 Marty: Thanks, that makes a lot of sense. And Mark puts it nicely: poetically, even (-: Ian. At 10:28 AM 6/21/2005 -0400, Marty Humphrey wrote: Hi Ian et. al., A very good question! ("can you define the goals of the BOF more precisely other than "not WSRF"?) I sent this email in part to hear from the community how "broad" they might like it to be. That is, we're being flexible. If someone wants to talk about one of these specific topics, we will certainly try our best to accommodate. Note that by default I believe the discussions will center around WS-Transfer, WS-Enumeration, WS-Eventing, et. al. I will talk about my team's use of WS-Transfer, WS-Enumeration, and WS-Eventing. I think we're in a very good position to discuss the pros and cons of these specs as compared with WSRF (as our project has implemented/used both). Let me answer the question in a different way. GGF Chair Mark Linesch said recently: "Our approach with the OGSA architecture along with our collaborative work on OGSA profiles is to: (1) describe 'the most traveled paths through the forest' rather than to dictate that there is only one path; and (2) to continue to highlight that multiple, overlapping paths may not be in the interests of the industry over time" (http://news.taborcommunications.com/msgget.jsp?mid=403500&xsl=story.xsl ) Simply, we believe that there has been sufficient "hallway discussions" on BOTH (1) and (2) that it makes good sense to gather people to discuss BOTH of these topics in a realistic and productive way. - Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia ________________________________________ From: Ian Foster [mailto:foster@mcs.anl.gov] Sent: Tuesday, June 21, 2005 9:54 AM To: Marty Humphrey; 'Ogsa-Wg' Cc: 'Marty Humphrey' Subject: Re: [ogsa-wg] OGSA-MWS-BOF at GGF14 on Tues June 28, noon-1:30 Marty, Steven: It is of course feasible, in principle, to define many different profiles for OGSA. E.g., one could build one on WS-Transfer and friends, one could build one that uses a different construct than the WS-Addressing EPR to address things, one could define one that uses JINI mechanisms, one could define one that uses CORBA, one could define one that renames all of the current WSRF and WS-Notification calls to be slightly different (oh wait, that's the first in the list (-: ), etc. Given the wide variety of possible alternative profiles, it would be helpful for those like me who are considering attending the BOF to know what more specifically what the goal of this work is going to be. The name doesn't provide any information, other than to imply, perhaps, that the interfaces on which the WSRF profile builds are not in some manner "minimal" and/or "simple." I.e., can you define the goals of the BOF more precisely other than "not WSRF"? Regards -- Ian. At 09:11 AM 6/21/2005 -0400, Marty Humphrey wrote: Folks, There have been a number of informal conversations lately about the feasibility/value/implications of a possible non-WSRF-based profile for OGSA. To bring all interested parties together at the same time, a BOF has been scheduled for Tuesday June 28 noon-1:30 (unfortunately at the same time as the EGA session, but there were no good times available). The agenda is still being finalized, but we expect to broadly discuss the pros/cons of such an effort, and, if the BOF attendees decide that such an effort would be valuable, produce a concrete plan for the formation of a Working Group. Here is the information that Steven Newhouse provided for the GGF organizers: "A BOF meeting to discuss the creation of a WG to define an OGSA Basic Profile that builds upon a minimal set of simple web services. The output of the group would be a document, similar in nature to the OGSA WSRF Basic Profile that would allow OGSA services to be rendered using an alternative set of WS specifications." I hope you can attend this (hopefully) productive and constructive session! -- Marty and Steven Marty Humphrey Assistant Professor Department of Computer Science University of Virginia _______________________________________________________________ Ian Foster www.mcs.anl.gov/~foster Math & Computer Science Div. Dept of Computer Science Argonne National Laboratory The University of Chicago Argonne, IL 60439, U.S.A. Chicago, IL 60637, U.S.A. Tel: 630 252 4619 Fax: 630 252 1997 Globus Alliance, www.globus.org <http://www.globus.org/> _______________________________________________________________ Ian Foster www.mcs.anl.gov/~foster Math & Computer Science Div. Dept of Computer Science Argonne National Laboratory The University of Chicago Argonne, IL 60439, U.S.A. Chicago, IL 60637, U.S.A. Tel: 630 252 4619 Fax: 630 252 1997 Globus Alliance, www.globus.org <http://www.globus.org/>

1 0

No Resource Management teleconference today
by Fred Maciel 21 Jun '05

21 Jun '05

Hi, (I sent this e-mail to the mailing list yesterday but apparently the GGF filters ate it and belched loudly, so here it goes again). Given that both our discussions with OGSA-BES and the broader CIM-GLUE-JSDL comparison didn't progress much since last week, let's postpone the teleconference on Tuesday. This week I'll be organizing the contents of the GGF14 sessions (ours, and the WSDM-related ones). Stay tuned. See you in GGF14, Fred Maciel Hitachi America R&D

1 0

Proposed agenda for June 22nd call
by Hiro Kishimoto 21 Jun '05

21 Jun '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 22nd Wednesday from 5pm to 7pm (CDT). If you plan to join GGF14 session by phone, please let me know by Wednesday. We will setup phone bridge only by request. 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: 0622 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-20050613/en/1 https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050615/en/1 Agenda bashing 2) GGF14 session preparation (30 min) For each session, confirm who does what OGSA session plan https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan/en… 3) Profile definition final review (40 min) Jem will upload the revised version shortly. 4) OGSA basic profile final review (40 min) Tom will upload the revised version shortly. 5) Wrap up (10 min) AOB June 27-30 GGF14 in Chicago ---- Hiro Kishimoto

3 4

CDDLM overview presentation slides
by Hiro Kishimoto 21 Jun '05

21 Jun '05

Hi all, Dejan's slides attached. It was explained at today's call. It is also uploaded to GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/cddlm-ogsa-intro/en/1 Thanks Dejan for your presentation. -- Hiro Kishimoto

1 0

Roadmap v13 uploaded - Re: Open issues (Re: [ogsa-wg] Roadmap doc v12 uploaded)
by Treadwell, Jem 20 Jun '05

20 Jun '05

Hi, I just uploaded v13, which is the version we'll review tonight. It addresses Hiro's "nitpick" mail, and Dave B's comment. For one or two of Hiro's comments I've highlighted the text in question, but haven't changed it. I haven't addressed any of the comments below - those are for discussion tonight. Also note that in this version some of the spec reference tables are dated June 20th, while some are June 16th. I'll sync them all up for the final submission; the June 20th tables reflect Hiro's comments. I haven't uploaded the spreadsheet, as I've only made a minor change and it's likely that more will come from tonight's call. You can find Roadmap v13 at http://tinyurl.com/78fly. - Jem -----Original Message----- From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com] Sent: Monday, June 20, 2005 1:52 AM To: Treadwell, Jem; Ogsa-Wg Subject: Open issues (Re: [ogsa-wg] Roadmap doc v12 uploaded) Thanks Jem, I've proof read v12 and found several issues. I will send out two emails; real issues and nits. This email contains real issues. (a1) page 9 table 3-6 We should put date for "OGSA information and monitoring architecture 1.0" if possible. (a2) page 14 table 4-10 (a3) page 16 table 4-14 (a4) page 17 table 5-2 Can we add "standard is approaching" mark to "Implemented" and "WS-Addressing" cell? I have no clue. (a5) page 17 table 5-2 "WS-BaseNotification 1.2" should read "WS-BaseNotification 1.3" Thanks, ---- Hiro Kishimoto Treadwell, Jem wrote: > Hi, > > I've now uploaded v12 of the Roadmap document, with various minor > edits and updated specification tables, in line with last Monday's review. > > I've also uploaded the standards spreadsheet, updated with the changes > we agreed on Monday, plus citation data from Tom. It was > difficult/tedious to navigate around all the pages, so I've also added > a new Index page which contains links to all the other pages and some > useful buttons. However, 1) You'll need to enable macros to use the > buttons (though you shouldn't need them unless you're editing), and 2) > I've found that Excel does odd things to the buttons - like resizing > them, changing the font at will, and inverting the shadows. If it > happens to you, don't worry about it :0) > > I think there's still some detail we could add for the various specs, > but I'll leave it as is for now. I promised I'd get this out on > Wednesday, and I have about 30 seconds left. > > The docs are at: http://tinyurl.com/aez86 . > > - Jem > ________________________________ > > 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

Teleconference minutes (June 13 & 15)
by Andreas Savva 20 Jun '05

20 Jun '05

Minutes from last week have been uploaded to gridforge. https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050613/en/1 https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050615/en/1 -- Andreas Savva

1 0

Profile definition draft 11 uploaded
by Andreas Savva 20 Jun '05

20 Jun '05

I've uploaded draft 11 of the OGSA Profile Definition. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-profil… The changes were described in a previous email by Hiro last week, and also discussed during the Wed. call. (http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/06/msg00063.html) Draft 11 is basically the same as draft 10-a that was attached to Hiro's email. I made some additional minor revisions and cleanup: accepting old changes and deleting obsolete comments. -- Andreas Savva

1 0

RE: Open issues (Re: [ogsa-wg] Roadmap doc v12 uploaded)
by Dave Berry 20 Jun '05

20 Jun '05

Section 2.2, Paragraph 7 (pages 5/6): In the light of the discussion of Section 2.3, should this paragraph use "conformance" rather than "compliance"? Dave. > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Hiro Kishimoto > Sent: 20 June 2005 06:52 > To: Treadwell, Jem; Ogsa-Wg > Subject: Open issues (Re: [ogsa-wg] Roadmap doc v12 uploaded) > > Thanks Jem, > > I've proof read v12 and found several issues. I will send out > two emails; real issues and nits. > > This email contains real issues. > > (a1) page 9 table 3-6 > We should put date for "OGSA information and monitoring architecture > 1.0" if possible. > > (a2) page 14 table 4-10 > (a3) page 16 table 4-14 > (a4) page 17 table 5-2 > Can we add "standard is approaching" mark to "Implemented" and > "WS-Addressing" cell? I have no clue. > > (a5) page 17 table 5-2 > "WS-BaseNotification 1.2" should read "WS-BaseNotification 1.3" > > Thanks, > ---- > Hiro Kishimoto > > Treadwell, Jem wrote: > > Hi, > > > > I've now uploaded v12 of the Roadmap document, with various > minor edits > > and updated specification tables, in line with last > Monday's review. > > > > I've also uploaded the standards spreadsheet, updated with > the changes > > we agreed on Monday, plus citation data from Tom. It was > > difficult/tedious to navigate around all the pages, so I've > also added a > > new Index page which contains links to all the other pages and some > > useful buttons. However, 1) You'll need to enable macros to use the > > buttons (though you shouldn't need them unless you're > editing), and 2) > > I've found that Excel does odd things to the buttons - like resizing > > them, changing the font at will, and inverting the shadows. If it > > happens to you, don't worry about it :0) > > > > I think there's still some detail we could add for the > various specs, > > but I'll leave it as is for now. I promised I'd get this out on > > Wednesday, and I have about 30 seconds left. > > > > The docs are at: http://tinyurl.com/aez86 . > > > > - Jem > > ________________________________ > > > > 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

RE: [ogsa-wg] GGF14 OGSA-WG session plan
by Dave Berry 20 Jun '05

20 Jun '05

FYI, The OGSA-D sessions will be at the following times on Wednesday 29th: 7.30-9.00 General overview & outreach (?) 9.00-10.30 Data transfer (?) 6.00-7.30 Transactions We are asking the GGF team whether it is possible to swap our first two sessions, as we're not convinced we'll get a good audience for an outreach session at 7.30 a.m. Dave. > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Hiro Kishimoto > Sent: 18 June 2005 07:55 > To: Ogsa-Wg > Subject: Re: [ogsa-wg] GGF14 OGSA-WG session plan > > Hi all, > > Wednesday is already very crowded and we found that there is no > conflict-free slot ;-P > > It seems that the least painful clash is 7:30-9am, security goes > into this early bird slot. > > Revised schedule attached. Also uploaded to the GridForge. > > https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_se ssion_plan/en/11 > > Thanks, > ---- > Hiro Kishimoto > > Hiro Kishimoto wrote: > > Hi all, > > > > GGF14 session plan is now available online and I've copied > > date/time/room information into OGSA-WG session plan table. > > > > Per Takuya's request, I am now asking GGF office to swap > > information session (#11) and security session (#10). > > I will update this change if GGF office accepts our > > request. > > > > > https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_se ssion_plan/en/10 > > > > > > If you plan to call-in any of our design team sessions by > > phone, please let me know by Monday (June 20) US time. > > We will set up phone bridge for you. > > > > Thanks, >

1 0

Roadmap doc v12 uploaded
by Treadwell, Jem 20 Jun '05

20 Jun '05

Hi, I've now uploaded v12 of the Roadmap document, with various minor edits and updated specification tables, in line with last Monday's review. I've also uploaded the standards spreadsheet, updated with the changes we agreed on Monday, plus citation data from Tom. It was difficult/tedious to navigate around all the pages, so I've also added a new Index page which contains links to all the other pages and some useful buttons. However, 1) You'll need to enable macros to use the buttons (though you shouldn't need them unless you're editing), and 2) I've found that Excel does odd things to the buttons - like resizing them, changing the font at will, and inverting the shadows. If it happens to you, don't worry about it :0) I think there's still some detail we could add for the various specs, but I'll leave it as is for now. I promised I'd get this out on Wednesday, and I have about 30 seconds left. The docs are at: http://tinyurl.com/aez86 . - Jem ________________________________ 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 2

OGSA-WG Proposed agenda for June 20th call
by Hiro Kishimoto 18 Jun '05

18 Jun '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 20th Monday from 5pm to 7pm (CDT). The upcoming call is for cross-WG discussion with CDDLM-WG and three documents (hopefully) final review. 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: 0620 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) GGF13 session schedule update (10 min) OGSA session schedule https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan/en… GGF on-line schedule page (not 100% up-to-date) http://tinyurl.com/ext3m 3) CDDLM-WG cross discussion (60 min) The intent of the meeting is to familiarize OGSA with CDDLM-WG's progress, to get OGSA-WG's feedback, and agree on the next steps. Most importantly to plan our meeting at GGF with the OGSA-EMS architecture team. (OGSA-WG #4 "EMS architecture" session, June 28 (Tues), 2:30-4pm at Wellington 1) Dejan, CDDLM-WG co-chair, comes up with a brief presentation on where CDDLM-WG are, where they are going, etc. and carrying it over to GGF14. 4) Three documents final review (40 min) OGSA roadmap 1.0 Jem has uploaded the revised version to the GridForge. - http://tinyurl.com/aez86 OGSA profile definition 1.0 Andreas will upload the revised version shortly. OGSA basic profile 1.0 Tom will upload the revised version shortly. 5) Wrap up (10 min) AOB June 22th (Wed) GGF14 preparation June 27-30 GGF14 ---- Hiro Kishimoto -- Hiro Kishimoto

1 0

GGF14 OGSA-WG session plan
by Hiro Kishimoto 18 Jun '05

18 Jun '05

Hi all, GGF14 session plan is now available online and I've copied date/time/room information into OGSA-WG session plan table. Per Takuya's request, I am now asking GGF office to swap information session (#11) and security session (#10). I will update this change if GGF office accepts our request. https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan/en… If you plan to call-in any of our design team sessions by phone, please let me know by Monday (June 20) US time. We will set up phone bridge for you. Thanks, -- Hiro Kishimoto

1 1

OGSA Naming WG status report
by Hiro Kishimoto 17 Jun '05

17 Jun '05

Status report: Progress on both the charter and WSNR (WS Naming resolution). RNS moved back to GFS until through document publication, i.e., after public comment Resolution modification to support base profile use case done and discussed Open issue remains "names" - which are just a string. Andrew -- Hiro Kishimoto

2 5

Any additions to "example projects" section in OGSA Roadmap?
by Treadwell, Jem 16 Jun '05

16 Jun '05

Hi, Section 8 of the OGSA Roadmap document describes some open-source projects that are working with OGSA concepts and specifications, and by doing so are contributing to the OGSA effort. The current text of the section is below. If anyone would like to add a few lines about any other project, please pass them on to me before the end of this week. We plan to do final review of the document on Monday next week, so please don't delay if you want to get something to me. Please keep your submission fairly short and in line with the style of what you see below, and be specific about what is being implemented. Also note that although the section is currently entitled "Open-Source Software Projects" commercial projects or other non-open-source projects can be included, provided they fit the criteria of contributing to the development of OGSA. We'll change the section heading if appropriate. Thanks! - Jem Open-Source Software Projects OGSA is expected to be implemented by multiple open-source software (OSS) projects and commercial software vendors. OSS projects such as Globus, the Business Grid Computing Project, the NextGrid Project, the NAREGI Project, University of Virginia Global Bio Grid, UK e-Science, and others will contribute. The Globus Toolkit (Globus) is one example of a major OSS grid project. The Globus Alliance is contributing to the development of OGSA by supporting the design and implementation of open-source software that implements specifications detailed in OGSA Profiles, and the participation of the implementers of that software in relevant standards processes. With its current version, GT4, based on early implementations of WSRF and WS-Notification and including implementations of all relevant security standards, Globus provides a comprehensive software infrastructure that allows developers and users to work with OGSA concepts now. Additional standards will be incorporated into future versions of the toolkit as they evolve. The Globus Consortium is a group of companies with a common interest in promoting the development and adoption of the Globus Toolkit for commercial use. Consortium participants also have a strong interest in standards in general, and in OGSA in particular. The team at the University of Virginia (UVA) is committed to implementing several pieces of the OGSA Roadmap described here. Specifically, UVA will implement open versions of ByteIO, BES, RNS, and the WS-Naming specifications. The Business Grid Computing Project (BG) is based on the OGSA Architecture specification. It is developing several services using specifications described in this Roadmap. In particular, BG will make available as open source software implementations of the Application Contents Service, JSDL, and WS-Agreement. BG intends to use the OGSA WSRF Basic Profile 1.0. The National Research Grid Initiative (NAREGI) is a Japanese national e-science grid project aiming at developing a computational infrastructure for supporting scientific and engineering research. One of the primary goals of the NAREGI Project is to contribute to the GGF standardization activities. NAREGI has been interested in, participated in, and, where possible, given feedback to numerous GGF working groups and research groups. Amongst the various groups, NAREGI has recently placed high emphasis on the OGSA-WG activities, being the first project or group to implement the EMS architecture described in the OGSA Architecture v1.0 specification, in its alpha incarnation of the software stack that was released in 1Q 2005. Future plans will have NAREGI contribute to and provide reference implementations for Basic Execution Services (BES), Resource Selection Services (RSS), and Application Contents Service (ACS). ________________________________ 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>

3 4

OGSA BES status report
by Hiro Kishimoto 15 Jun '05

15 Jun '05

OGSA-BES status F2F held in London end-of-May. First draft strawman GGF document underway and on Gridforge, basic interfaces defined. Decisions we are a service - including metadata/attribute/resource properties we are not going to use WS-Agreement Metamodel for attributes under discussion. Should we use CIM? Some other, e.g., Condor terms? Issue: how much "management" should go into container interface? -- Hiro Kishimoto

1 0

RM teleconference minutes -- June 14, 2005
by Fred Maciel 15 Jun '05

15 Jun '05

Hi, Here are the minutes. Regards, Fred Maciel.

1 0

OGSA-D telcon agenda for June 22nd - Data transfer, GGF preparation
by Dave Berry 15 Jun '05

15 Jun '05

Dear all, Next week's telcon will be on Wednesday (22nd June), at the usual time of 8:00am PDT / 11:00am EDT / 4:00pm BST / 5:00pm CEST. PIN for this call: 632 065 UK Dial In: 0845 245 0224 US Dial In: 1866 838 0046 International Dial In: +44 1452 542309 Here is a provisional agenda for next week. 1) Early discussion (5 min) Note taker assignment Roll call Minutes approval (http://tinyurl.com/cb5go) Agenda bashing 2) Action report (5 min) - Allen to ask Julie to swap the 7:30 and 9:00 sessions at GGF. - Allen and Dave to prepare talks for review at next week's telcon. - Allen and Dave to mail co-chairs of other groups once the revised schedule is confirmed. - Dave to write short report for OGSA WG - Allen to attend OGSA WG call - Stephen to update replication use case - Dave to write to LSG-RG about security - Ann will organise the security notes we've taken so far into a coherent memo that we can take to the security working groups. - Dave will discuss security with the NeSC security people. - Dave will approach the OGSA WG security design team about a joint meeting. - Dave to revamp section 3 of the architecture document. 3) GGF preparation (25 min) - GGF session plan - Other sessions: LSG-RG, OGSA, Security, Data area, other data WGs,... - Review of draft slides 4) Data transfer (20 min) 5) Wrap up (5 min) AOB DONM Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

OGSA-D status report
by Dave Berry 15 Jun '05

15 Jun '05

Here is a report of OGSA-D activity for the last month, as input for tonight's OGSA call. ---- Our f2f meeting in London produced very useful technical discussion. It was especially valuable to have representatives of several major activities present. We have a working draft of the architecture document for discussion at GGF. Work on this document has made significant progress but it still contains many holes. Recently we have begun work on a companion scenarios document; this is needed to show how the elements of the architecture fit together. We have begun work on a memo about security concerns for data services. Our aim is to initiate a dialogue with security teams to make sure that their work addresses our needs. We note that other groups (such as the LSG-RG) also have activity in this area. We have three sessions scheduled for GGF14. One is an outreach session at which we will present our work. The other two are technical sessions, on data transfer and transactions. Telcon minutes are available on the OGSA-D WG GridForge site. ---- Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

Proposed agenda for June 15th call
by Hiro Kishimoto 15 Jun '05

15 Jun '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 15th 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: 0615 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Inauguration of a new co-chair (congratulations Tom!) Telecon minutes approval (if available) Document submission status GGF14 session schedule Agenda bashing 2) OGSA fellow WG status report (20 min) OGSA-ByteIO WG OGSA-BES WG OGSA-data WG OGSA-naming WG 3) OGSA next step discussion (60 min) Since we will complete key deliverables at GGF14, it is time to list up, prioritize, and choose next work item(s) of OGSA-WG for '05H2 and '06. Hiro will send out first-cut laundry list as starting point. 4) Wrap up (10 min) AOB June 20th (Mon) CDDLM cross-WG session, EMS architecture, document review June 22th (Wed) GGF14 preparation, document review ---- Hiro Kishimoto

2 2

RE: [ogsa-wg] RM teleconference reminder -- container properties
by Andrea Westerinen (andreaw) 14 Jun '05

14 Jun '05

Sorry for the resend, but I updated the spreadsheet based on our conversation on the RM call today. Andrea > -----Original Message----- > From: Andrea Westerinen (andreaw) > Sent: Tuesday, June 14, 2005 10:59 AM > To: 'Fred Maciel'; GGF - ogsa-wg ml; ogsa-bes-wg(a)ggf.org > Subject: RE: [ogsa-wg] RM teleconference reminder -- > container properties > > Here are my updates for the call today ... > > Andrea > > > -----Original Message----- > > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] > On Behalf > > Of Fred Maciel > > Sent: Monday, June 13, 2005 5:50 PM > > To: GGF - ogsa-wg ml; ogsa-bes-wg(a)ggf.org > > Subject: [ogsa-wg] RM teleconference reminder -- container > properties > > > > Hi, > > > > On the next teleconference we will continue discussing the > > container's properties, as we did last week. I and Andrea > are working > > on a strawman mapping JSDL and CIM (the attached file is > what we have > > as of now). Examples of things to discuss: > > > > - Review the mapping > > - What in JSIM and CIM apply to the container? For > instance, there are > > more properties in a container than just JSIM (e.g. > > properties for monitoring). > > - How do Individual* and Total* JSIM properties apply to the > > container? > > Total* is across containers? > > - etc. > > > > My intention is to take the results of this teleconference > and present > > on the OGSA-BES teleconference on Thursday. > > > > Date: Tuesday, June 14th, at the following times: > > - 11:00-12:00 US Pacific (GMT - 7) > > - 12:00-13:00 US Mountain (GMT - 6) > > - 13:00-14:00 US Central (GMT - 5) > > - 14:00-15:00 US Eastern (GMT - 4) > > - 18:00-19:00 GMT > > - 19:00-20:00 UK (GMT + 1) > > - 20:00-21:00 Central Europe (GMT + 2) > > - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. > > > > 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: 0614 > > Explanation: > > > > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg > > 00077.html > > > > See you there, > > > > Fred Maciel > > Hitachi America R&D > > > >

1 0

RE: [ogsa-wg] RM teleconference reminder -- container properties
by Andrea Westerinen (andreaw) 14 Jun '05

14 Jun '05

Here are my updates for the call today ... Andrea > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On > Behalf Of Fred Maciel > Sent: Monday, June 13, 2005 5:50 PM > To: GGF - ogsa-wg ml; ogsa-bes-wg(a)ggf.org > Subject: [ogsa-wg] RM teleconference reminder -- container properties > > Hi, > > On the next teleconference we will continue discussing > the container's properties, as we did last week. I and Andrea > are working on a strawman mapping JSDL and CIM (the attached > file is what we have as of now). Examples of things to discuss: > > - Review the mapping > - What in JSIM and CIM apply to the container? For instance, > there are more properties in a container than just JSIM (e.g. > properties for monitoring). > - How do Individual* and Total* JSIM properties apply to the > container? > Total* is across containers? > - etc. > > My intention is to take the results of this teleconference > and present on the OGSA-BES teleconference on Thursday. > > Date: Tuesday, June 14th, at the following times: > - 11:00-12:00 US Pacific (GMT - 7) > - 12:00-13:00 US Mountain (GMT - 6) > - 13:00-14:00 US Central (GMT - 5) > - 14:00-15:00 US Eastern (GMT - 4) > - 18:00-19:00 GMT > - 19:00-20:00 UK (GMT + 1) > - 20:00-21:00 Central Europe (GMT + 2) > - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. > > 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: 0614 > Explanation: > > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg > 00077.html > > See you there, > > Fred Maciel > Hitachi America R&D > >

1 0

I have the pen on the standards xls <EOM>
by Tom Maguire 14 Jun '05

14 Jun '05

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

RM teleconference reminder -- container properties
by Fred Maciel 14 Jun '05

14 Jun '05

Hi, On the next teleconference we will continue discussing the container's properties, as we did last week. I and Andrea are working on a strawman mapping JSDL and CIM (the attached file is what we have as of now). Examples of things to discuss: - Review the mapping - What in JSIM and CIM apply to the container? For instance, there are more properties in a container than just JSIM (e.g. properties for monitoring). - How do Individual* and Total* JSIM properties apply to the container? Total* is across containers? - etc. My intention is to take the results of this teleconference and present on the OGSA-BES teleconference on Thursday. Date: Tuesday, June 14th, at the following times: - 11:00-12:00 US Pacific (GMT - 7) - 12:00-13:00 US Mountain (GMT - 6) - 13:00-14:00 US Central (GMT - 5) - 14:00-15:00 US Eastern (GMT - 4) - 18:00-19:00 GMT - 19:00-20:00 UK (GMT + 1) - 20:00-21:00 Central Europe (GMT + 2) - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. 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: 0614 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

Teleconference minutes - 8 June 2005
by Andreas Savva 13 Jun '05

13 Jun '05

Minutes attached. Outline: * Document review process * WSRF Basic Profile (BP) review * Roadmap review Gridforge: http://tinyurl.com/5fxfd/minutes-20050608/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 8 June 2005 ================================= * Participants Mike Behrens (R2AD, LLC) Hiro Kishimoto (Fujitsu) Fred Maciel (Hitachi) Tom Maguire (IBM) Mark Morgan (UVa) Takuya Mori (NEC, ANL) Andreas Savva (Fujitsu) Jem Treadwell (HP) Jay Unger (IBM) Apologies: Andrew Grimshaw Minutes: Andreas Savva * OGSA co-chair nomination Tom has received approval from management. * Document review process With three documents nearing completion the group discussed how best to complete the review process. 1. Put a clean copy with all changes accepted on gridforge (today or as soon as possible). Turn on line numbers (by 5 lines by page) for these versions to make it easier for people to refer to specific places in the text. 2. Assign people to go through entire document and do an overall check for consistency, with a special view on the flow of the text, completeness, etc. (Everyone is welcome to contribute to this effort.) 3. Assign people to verify (specific) trackers that are currently in the fixed state (One person per tracker; and maybe more than one tracker per person) The group also discussed how to do comments. There were two proposals: 1. Comments in the document and send document to the list 2. Send text email to the list pointing to the location in the document that needs revision. The overall preference was for the second option (text emails) rather than sending documents around. Partly for bandwidth reasons and partly due to issues of serialization and merging multiple document versions. But if a reviewers decide that a lot of editing is required then they should ask for, or take the pen (by sending an email to the list) and make the changes in the document. The deadline for completing the review is Monday, June 13. ** Basic Profile review volunteers - Proofreading (overall) - Dave Snelling (Tom to ask) - Jay Unger - Mike Behrens - Hiro Kishimoto - (And other people that Tom has asked already) - Tracker verification - Andreas Savva ** Profile definition review volunteers - Proofreading (overall) - Tom Maguire - Andreas Savva - Mike Behrens - Tracker verification - Not needed. All artifacts are closed. ** Roadmap review volunteers - Proofreading - Hiro Kishimoto - Takuya Mori - Tracker verification - Tom Maguire * WSRF Basic Profile (BP) review ** Should the referenced specs be updated? The WSRF BP is referring to an old (2004), somewhat inconsistent, set of specs for WS-Addressing, WSRF and WS-N. (Ref. WS-Addressing discussion). A number of recent developments might offer an opportunity to fix this: - WS-Addressing specs (last call) - The OASIS WSRF TC has a ballot closing at the end of this week (Sat., June 11 (1pm Eastern)) to send out the WSRF set of committee draft documents for public review - The WS-N group is planning to release committee drafts of the Base Notification specification (perhaps July 1) and also of Topics (and maybe also brokered notification). So it looks like there will be an updated, consistent set of documents to refer to. The problem is whether, and how, to keep the deadline for submitting the document to the GGF Editor (next week) and also make sure that the WSRF Basic Profile can be updated to use these specs when they come out. At the very least the changes required to the BP would be to the References, Namespaces and links to imported schemas. - For the WSRF and WS-Addressing specification these are (almost) known. - But the WS-N ones are not completely fixed yet. A number of scenarios were discussed: 1. Wait for the new versions to come out, update the BP and submit 2. Submit the document as-is and then put a public comment that it should be updated with the new WSRF+ set of specifications when they come out. 3. Put a comment in the document that it will be updated with the new WSRF+ set of specs and submit it as-is. - Scenario (3) was rejected since it clearly bends the rules too much. - Scenario (1) is the safest one but it keeps the BP queued and waiting for the updated specifications. - Scenario (2) follows the GGF process---the editors/authors are also encouraged to submit comments. But if there is a delay in the release of the referenced specs then the BP goes through as-is; or if there is a need for more changes than anticipated then a second round of public comment would be required. The remaining issue about scenario (2) was whether we are relaxing the submission rule as defined by "Profile Definition". The key point is whether the current draft of the BP, referencing old WS-Addressing, WSRF and WS-N drafts, qualifies for submission to the GGF Editor. In other words are the references used 'stable' and could the BP proceed to R-P status, potentially without any of the above changes. It was argued that the definition of 'stable' is that specifications must be at least 'committee drafts'. And that the existing referenced specs, even if they are not called 'committee drafts' have been through a similar process and are therefore of an equivalent level. In particular, it was proposed that the new OASIS type of "working draft" is equivalent to a "committee draft" since there is a vote by the TC to make such documents public. There was no consensus, however. The preference on the call was for scenario (2) and (1) in that order. The 'stable' reference rule needs more clarification, however. Action: Hiro to follow up on the definition of 'stable' and whether the specifications in question satisfy that rule. Also, if the group decides to go with (2) then the group has to discuss and agree on what the public comment should say. ** Section 4.1.1: ResourcePropertiesNames Defines syntax of resource properties, but there is no explanation of the meanings of most of these, what their values may be and why. Action: Tom will add an appendix with pseudo schema (mini spec) and additional text for each property. (A definition along the lines of R0415 and R0416.) ** Appendic C: Basic profile schema - There is a duplicate definition. - The definitions are incomplete (see above) Action: Tom will add cardinalities; perhaps add these in the mini-spec. ** Section 4.3: Serialization of XPath 1.0 response The mini-schema was defined to avoid the ambiguity in the XPath spec. But why did not other people try to solve it, already? The WSRF TC, for example, is aware of this problem but decided that it did not have the authority to fix this. (Out of scope.) The W3C, which has the authority to address this problem, also has not done anything. But the W3C does not mandate XPath 1.0. In the WSRF BP 1.0 XPath 1.0 is mandated so a solution had to be provided. Action: Tom will add explanation to the BP on the necessity of defining the XPath 1.0 response serialization. ** Numbering of R & E statements Numbering is inconsistent. Some numbers are based on section numbers; some on subsection. Action: Tom will make them consistent; suggestions welcome. ** Appendix A There are three references to UDDI specs. Agreed that the list needs cleanup. Action: Tom to clean up list and in particular remove the UDDI binding template reference. ** Appendix B Also needs cleanup. * Roadmap review Jem has done some work on how to keep tables consistent. Tom has also independently done some work on this. They seem to have arrived to the same solution. - Use an excel spreadsheet for the master table and produce separate smaller tables in separate sheets for each specific spec. These smaller tables refer to row/column in the master sheet. Considered linking the spreadsheets directly to the Roadmap using OLE but rejected this during the call since it is not a platform-neutral method. (People using Macs could not use the Word document.) Therefore it was agreed that the master table and sub-tables should be done in Excel. And a 'view' or 'image' of the sub-tables should be provided for use in the Word document.

2 1

OGSA-D telcon agenda for June 15th - Use cases,
by Dave Berry 13 Jun '05

13 Jun '05

Dear all, This week's telcon will be on Wednesday (15th June), at the usual time of 8:00am PDT / 11:00am EDT / 4:00pm BST / 5:00pm CEST. PIN for this call: 632 065 UK Dial In: 0845 245 0224 US Dial In: 1866 838 0046 International Dial In: +44 1452 542309 Here is a provisional agenda for this week. 1) Early discussion (5 min) Note taker assignment Roll call Minutes approval Agenda bashing 2) Action report (5 min) - Dave to reconfigure tracker mail [Done] - Dave to reply to Torsten of the TM-RG, inviting him to our session [Done] - Ann will organise the security notes we've taken so far into a coherent memo that we can take to the security working groups. - Dave will discuss security with the NeSC security people. - Dave will approach the OGSA WG security design team about a joint meeting. - Allen will approach the OGSA-AuthZ WG about a joint meeting. - Stephen to iterate on the replication use case. [Done] - Dave to revamp section 3 of the architecture document. 3) WG status (5 min) - Trackers - GGF working drafts - GGF session plan 4) Use cases (20 min) 5) Security requirements for data grids (20 min) 6) Wrap up (5 min) AOB DONM Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

Proposed agenda for June 13th call
by Hiro Kishimoto 13 Jun '05

13 Jun '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 13th Monday from 5pm to 7pm (CDT). Since our plate is full on Monday, I propose to postpone OGSA fellow WG status report to Wednesday. 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: 0613 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval http://tinyurl.com/5fxfd/minutes-20050608/en/1 http://tinyurl.com/5fxfd/minutes-20050606/en/1 http://tinyurl.com/5fxfd/minutes-20050601/en/2 http://tinyurl.com/5fxfd/minutes-20050518/en/1 http://tinyurl.com/5fxfd/minutes-20050516/en/1 http://tinyurl.com/5fxfd/minutes-20050511/en/1 http://tinyurl.com/5fxfd/minutes-20050509/en/1 Agenda bashing 2) OGSA roadmap review (30 min) Jem has uploaded the revised version to the GridForge. - http://tinyurl.com/aez86 Look forward to proofread and tracker verification. 3) OGSA WSRF BP 1.0 review (30 min) Discuss and decide when we submit BP 1.0. >From June 8th minutes > 1. Wait for the new versions to come out, update the BP and submit > 2. Submit the document as-is and then put a public comment that it > should be updated with the new WSRF+ set of specifications when > they come out. > Action: Hiro to follow up on the definition of 'stable' and whether > the specifications in question satisfy that rule Tom has uploaded the revised version to the GridForge. - http://tinyurl.com/5fxfd/draft-ggf-ogsa-wsrf-basic-profile Look forward to proofread and tracker verification. 4) OGSA profile definition review (30 min) Tom has uploaded the revised version to the GridForge. - http://tinyurl.com/5fxfd/draft-ggf-ogsa-profile-definition Look forward to proofread and tracker verification. 5) Wrap up (10 min) AOB June 15th (Wed) fellow WG status report & OGSA-WG next step discussion June 20th (Mon) CDDLM cross-WG session, EMS architecture June 22th (Wed) GGF14 preparation ---- Hiro Kishimoto

2 3

RE: Resilient References? (Re: [ogsa-wg] ogsa London f2f minutes uploaded)
by Savas Parastatidis 13 Jun '05

13 Jun '05

Mark (that's Mark McKeown), You are assuming HTTP here while most (if not all) of WS-* specs do not make that assumption. While what you are describing with HTTP headers may work indeed, they are all tied to HTTP. We are now seeing SOAP processors supporting other transport protocols as well (e.g. Indigo and Axis 2 support SOAP over TCP/IP). (note that I am treating HTTP as a transport protocol here and now as an application protocol :-) Regards, -- Savas Parastatidis http://savas.parastatidis.name > -----Original Message----- > From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of > Mark McKeown > Sent: Friday, June 10, 2005 4:32 PM > To: Mark Morgan > Cc: ogsa-wg(a)ggf.org > Subject: RE: Resilient References? (Re: [ogsa-wg] ogsa London f2f minutes > uploaded) > > > Hi folks, > I have read the WS-Naming strawman and been trying to follow > the discussion on resilient references on the list. Putting EPRs inside > EPRs seems a bit strange to me - the following seems simpler (the > obvious inspiration is tinyurl) ... > > <wsa:EndpointReference> > <wsa:Address>mailto:mark.mckeown@manchester.ac.uk</wsa:Address> > <ws-name:Handle>http://www.thegrid.com/a4dfg</ws-name:Handle> > </wsa:EndpointReference> > > Where "Handle" is used as an identifier/name and is mandated to be > a HTTP/S URI. To resolve the Handle a client does a HTTP GET on the > URI to get a new EPR, (client gets 404 if resolution is not supported, > 410 if the service/resource is gone/terminated). > > I can see a number of advantages to this: > > *) It is simple and easy to implement. > > *) The Cache-Control headers in HTTP can be used to pass on information > to the client to indicate how long it can cache an EPR for - this > is an optional optimization. > > *) If-Modified-Since HTTP header could be supported so a client will only > retieve a new EPR if the one it has is stale - again an optional > optimization. > > *) The "Handle" is easy to pass around between users - it can be pasted > into a mail message and the reciever can use HTTP GET to retrieve the > EPR. > > *) HTTPS can be used when trust is important. > > *) The service developer can make his EPRs "resilient" whenever he wants, > ie he creates an EPR with a "Handle" but only later makes the "Handle" > URI live. > > Effectively the low level HTTP protocol could be used to bootstrap the > higher level SOAP protocol. Perhaps there are strong reasons why this > approach was not considered? > > cheers > Mark > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Mark Mc Keown RSS > Mark.McKeown(a)man.ac.uk Manchester Computing > +44 161 275 0601 University of Manchester > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > On Fri, 10 Jun 2005, Mark Morgan wrote: > > > > when Mark writes: "...the general idea we have is to in fact > > > possibly have a method who's signature is EPR resolve( [EPR] > > > ) Where the parameter EPR is optional..." > > > > > > Does this "optional" mean that the schema for the input > > > message parameter of the resolve operation will have an > > > optional "EPR"; it should either be empty or consist of a single EPR? > > > > Borrowing the pseudo syntax used in the "Web Services Base Notification > 1.2 > > Working Draft 03, 21 June 2004" and replacing the given template for the > > NotificationMessage syntax with appropriate naming elements, what I mean > is > > this: > > > > > > <ogsa-naming:Resolve> > > <ogsa-naming:ResolutionMessage> > > <ogsa-naming:TargetEPRHint>? > > wsa:EndpointReference > > </ogsa-naming:TargetEPRHint> > > </ogsa-naming:ResolutionMessage> > > </ogsa-naming:Resolve> > > > > > If so, what does the "optional" mean for the implementors of > > > that porttype/operation "EPR resolve( [EPR] )"? > > > Does the service implementation have to cater for both options? > > > > No, it doesn'. It can implement the empty parameter one, or both the > empty > > parameter one and the one that takes an EPR as a parameter. See below > for > > explanation. > > > > > Or can it just return an error for the one it doesn't implement? > > > > No, this would not be correct I don't believe. > > > > > And then what does the "optional" mean for the client's processing? > > > If the schema indicates that the client could either call the > > > resolve operation with or without the original EPR, how does > > > it know which option to choose? Should it just try the one it likes? > > > > The important points to recall here are: > > 1) There are two EPRs involved in this communication conversation. > > One is the obvious one listed as an optional parameter. For clarity, > let's > > call that parameter the "Hint EPR". The other EPR is the implicit one > which > > would be indicated in the SOAP headers to which the communication is > taking > > place. Let's call that EPR the "Resolver EPR". > > 2) The Resolver EPR is created with whatever information the > > implementor of the resolution services feels is appropriate. It's up to > > that service to generate an EPR with enough information to do the > > resolution. > > 3) The Hint EPR is just that -- a hint. It should not be considered > > the end all source of information for resolution. > > > > What we imply by all of this is that a resolution service should be able > to > > deal with a resolution message that does not include any EPR as a > parameter > > by virtue of the fact that the Resolution EPR to which the resolution > > messages are addressed is created by that service with enough > information to > > completely carry out the resolution. If an EPR is given as a parameter > to > > that resolution service, the service MAY choose to use that hint to more > > efficiently resolve the endpoint in question, but is not required to do > so. > > In otherwords, a resolution service implementor may choose to implement > code > > that uses the optional EPR parameter if available, but MAY also choose > to > > ignore it. > > > > >From the client perspective, it should be the case that the client may > > equally choose to send either an empty message (since this is guaranteed > to > > work), or one with an EPR (since a service may choose to ignore this > > parameter). In this way the client is free to pick either one -- the > > parameterless one if it feels inclined to go with no hints, or the > message > > with an EPR if the client feels like this extra hint may be useful. > > > > So, in what cases would the EPR parameter be useful should the client > decide > > to send it and should the service decide to use it? Well, in the > general > > case, we have found that it is tremendously useful (bordering on > necessary) > > sometimes for a client to indicate to a resolution service that that > client > > has already tried to communicate with a given binding (EPR) and that the > > resolution service might want to go to extra efforts (i.e., instead of > just > > looking the binding up in a cache or table) to determine whether or not > a > > more suitable EPR exists. > > > > -Mark > > > > > Thanks, Frank. > > > >

2 1

Future of OGSA, Web Services in Hands of IT Community
by Hiro Kishimoto 13 Jun '05

13 Jun '05

Mark Linesch's article in GRIDtoday. Grid computing is increasingly being viewed as a critical component of the next phase of distributed computing. The key to realizing the benefits of Grid computing is standardization, so that the diverse resources that make up a modern distributed environment can be discovered, accessed, allocated, monitored and, in general, managed as a single virtual system -- even when provided by different vendors and/or operated by different organizations. Standardization of Grid computing is being led by the Global Grid Forum (GGF). GGF has developed the Open Grid Services Architecture (OGSA) and is working throughout the international community to champion this "architectural blueprint" and the associated specifications that will enable the pervasive adoption of Grid computing for business and research worldwide. http://news.taborcommunications.com/msgget.jsp?mid=396791 -- Hiro Kishimoto

1 0

OGSA Representation to the Israel Grid Alliance
by Hiro Kishimoto 13 Jun '05

13 Jun '05

Hi all, Steve ask us to send a representative from the OGSA team to hold a one day workshop on the technical aspects of OGSA at a meeting being developed by the Israeli Association of Grid Technologies (IGT). I propose to put it on an agenda tomorrow. Any volunteers? Thanks, ---- Hiro Kishimoto

1 0

Unapproved teleconference minutes
by Andreas Savva 12 Jun '05

12 Jun '05

The following (unapproved) minutes are now on gridforge: http://tinyurl.com/5fxfd/minutes-20050606/en/1 http://tinyurl.com/5fxfd/minutes-20050601/en/2 http://tinyurl.com/5fxfd/minutes-20050518/en/1 http://tinyurl.com/5fxfd/minutes-20050516/en/1 http://tinyurl.com/5fxfd/minutes-20050511/en/1 http://tinyurl.com/5fxfd/minutes-20050509/en/1 We'll be approving these next Monday, 6/13. -- Andreas Savva Fujitsu Laboratories Ltd

2 1

Roadmap v11 and standards tracking spreadsheet uploaded
by Treadwell, Jem 11 Jun '05

11 Jun '05

Hi, My mind is now clinically numb. I've uploaded a new roadmap, with changes as agreed on Monday - see the markup for significant changes. All standards tables are now pictures, pasted from the new standards spreadsheet, which is uploaded to the same folder. I won't try to describe the spreadsheet as we discussed it on Wednesday, but it is worth browsing. Having spent the past few hours getting the first set of worksheets set up, it *is* tedious to work with, but copying the sheets into the document is simple (though also tedious for this particular document!), and I can't think of a better way to do it right now. I'm very open to suggestions for improvements/simplifications to the spreadsheet. We *do* need to review some of these versions etc. - e.g. RNS versions of WS-Addressing and WS-ResourceProperties are not in line with the RNS document. But for now I'm going to leave it alone. If anyone wants to make some updates, I promise not to do anything else before Monday's call, so you can grab the pen. Thanks to all who responded for this version; everyone enjoy the weekend. Oh, and the documents are both at http://tinyurl.com/aez86. - Jem ________________________________ 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

Questions on OGSA WSRF Basic Profile 1.0
by Mark McKeown 10 Jun '05

10 Jun '05

Hi folks, Sorry if these are dumb questions... I was looking through WSRF Basic Profile 1.0, (Revised: Friday, June 10, 2005). > Section 9.1.1 Mandated Secure Transport "All messages are subject to interference and corruption during transmission. The Profile mandates secure transmission of messages." Is there a reference that makes this case? I have looked at the WS-I document "Security Challenges, Threats and Countermeasures" http://www.ws-i.org/Profiles/BasicSecurity/SecurityChallenges-1.0.pdf which indicates that message level security is OK for many threats. WSRF & ACID Section 7 of Web Service Resource Properties 1.2 discusses ACID and WSRF - a WSRF implementor can choose a concurrency policy with regard to updating and retrieving resource properties, so two implementations of a WS-Resource with the same operations and PropertiesDocument could actually have different behaviour leading to interoperability issues for clients - is this any area for a WSRF profile to address? thanks Mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Mark Mc Keown RSS Mark.McKeown(a)man.ac.uk Manchester Computing +44 161 275 0601 University of Manchester ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

4 3

ogsa London f2f minutes uploaded
by Hiro Kishimoto 10 Jun '05

10 Jun '05

Hi all, Mark and Andreas upload F2F minutes to GridForge. Please have a look and approve them tomorrow. > They are now online: > https://forge.gridforum.org/projects/ogsa-wg/document/f2f-minutes-20050524/… > > https://forge.gridforum.org/projects/ogsa-wg/document/f2f-minutes-20050523/… Thanks Mark and Andreas for your excellent minutes! ---- Hiro Kishimoto

6 20

RE: [ogsa-wg] Teleconference minutes - 8 June 2005
by Djaoui, A (Abdeslem) 10 Jun '05

10 Jun '05

Just a comment of the WSRF BP submission to the GGF editors. I am in favor of option 1 simply because I don't see a point of releasing a profile that "very likely" nobody is going to use. I know there are some implementations of the referenced specification out there, but in my view people will find it more efficient to move to the latest versions of the specifications that to try to be compliant with an older version of a profile that is going to be changed soon. Anyway the wait is almost over! Abdeslem /////////// -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org]On Behalf Of Andreas Savva Sent: Friday, June 10, 2005 11:12 AM To: 'ogsa-wg' Subject: [ogsa-wg] Teleconference minutes - 8 June 2005 Minutes attached. Outline: * Document review process * WSRF Basic Profile (BP) review * Roadmap review Gridforge: http://tinyurl.com/5fxfd/minutes-20050608/en/1 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

RM teleconference minutes -- June 7, 2005
by Fred Maciel 10 Jun '05

10 Jun '05

Hi, Here are the minutes of the teleconference. Regards, Fred Maciel.

1 0

Will miss call tonight
by Andrew Grimshaw 08 Jun '05

08 Jun '05

Colleagues, I have some sort of stomach bug - and am not feeling well. Will talk to some of you tomorrow morning. Andrew

1 0

OGSA-BES Thursday telecon
by Andrew Grimshaw 08 Jun '05

08 Jun '05

Note: Will continue to cross-post to OGSA-wg until after GGF 14. Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 Time: 10 AM eastern 0700 Pacific 3 PM UK 4 PM Europe 1 hour Glance will provided at ogsa.glance.net Proposed Agenda: Agenda bashing Discuss DRAFT specification - (will post on gridforge by COB Wednesday in US) Grimshaw will lead Batch/posix porttype proposal - Chris Smith will lead Meta-model discussion - JSDL, CIM, other

1 0

v1.8 of Profile definition updated and uploaded
by Tom Maguire 08 Jun '05

08 Jun '05

Folks, The latest with Ais from 6/1 telecoin are uploaded to Gridforge. Tom 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

3 3

Last CFP: WISE'05 Industrial Track in NYC
by Gagnon, Stephane 08 Jun '05

08 Jun '05

CALL FOR PAPERS ===================================================================== WISE 2005 Industry Track http://elab.njit.edu/wise 6th International Conference on Web Information Systems Engineering November 20-22 2005, New York City, New York http://www.cs.txstate.edu/wise05 ===================================================================== Sponsored by: - Telcordia - IBM - NJIT Supported by: - Object Management Group (OMG) - Integration Consotrium (IC) --------------------------------------------------------------------- The goals of the WISE 2005 Industry Program are to foster exchanges between practitioners and the academics, to promote novel solutions to today's business challenges, to provide practitioners in the field an early opportunity to evaluate leading-edge research, and to identify new issues and directions for future research and development work. We invite submissions on all topics related to web engineering including technologies, methodologies, and applications. Papers can take the form of detailed case studies, technical white papers, new methodologies, new standard specifications, benchmarking models, or any other contributions demonstrating innovative web engineering technologies, methods, and applications. Topics of particular interest include but are not limited to those identified in the conference CFP, as well as those listed below: 1. Technologies: a. Development of new web services standards b. Use of business process automation technologies c. Use of semantic web and grid computing d. Innovative solutions for performance optimization e. Benchmarking of leading runtime environments 2. Methodologies: a. Web engineering with a Model Driven Architecture b. Requirements engineering for web applications c. Software design reusing legacy systems and data d. Quality focus and use of Test Driven Development e. Benchmarking of leading web engineering tools 3. Applications: a. Case studies of major web engineering projects b. Implementation of a Service Oriented Architecture c. Outsourcing and use of Business Services Networks d. Analysis of industry-specific trends and challenges e. Benchmarking models in selecting web IT vendors ---------- Deadlines: ---------- Abstracts due June 10, 2005 Papers due June 17, 2005 Decision notification Aug. 12, 2005 Camera-ready copies due Sept. 16, 2005 ------------------------- Guidelines and Submission: -------------------------- All industrial papers will be peer-reviewed and published in the regular conference proceedings. For easy identification, industrial papers should have as their title "Industry Track: rest of title". Please follow the guidelines of Lecture Notes in Computer Science (LNCS) published by Springer: http://www.springeronline.com/sgw/cda/frontpage/ 0,11855,5-164-2-72376-0,00.html. Please submit your paper online in PDF format: http://elab.njit.edu/wisesubmit For more information, please contact the Industrial Program Chair. ------------------------- Industrial Program Chair: ------------------------- Jen-Yao Chung, IBM T. J. Watson Research (jychung(a)us.ibm.com) ------------------------------- Industrial Program Vice Chairs: ------------------------------- Stephane Gagnon, NJIT (gagnon(a)njit.edu) Shu-Ping Chang, IBM Research (spchang(a)us.ibm.com) ------------------ Program Committee: ------------------ TBA

1 0

Web Services Management Roadmap published
by Hiro Kishimoto 08 Jun '05

08 Jun '05

Heather's email bounced. ---- Hiro Kishimoto Subject: Web Services Management Roadmap published From: Heather Kreger <kreger(a)us.ibm.com> Date: Tue, 7 Jun 2005 14:12:00 -0400 Hello, CA, HP and IBM would like to make you aware of a paper that we have recently published jointly. This paper, 'Management Using Web Services, A Proposed Architecture and Roadmap' characterizes challenges facing the IT systems management community and defines a roadmap and strategy for the evolution of management systems to support emerging business environments. It explains how a common approach for manageability (using Web services infrastructure) can simplify the management solutions for both existing systems and systems based upon emerging Service-Oriented Architectures (SOA). It defines a comprehensive Web services based systems management architecture that supports, integrates, and unifies several popular management models and technologies in a way to manage any IT resource in a platform and language-neutral manner. We believe that WSDM, WSRF, and WS-Notification are some of the foundation standards for this Roadmap. You can get a copy of the management roadmap at one of this links: CA: http://www3.ca.com/technologies/Collateral.asp?CID=70104&ID=3339 HP: http://devresource.hp.com/drc/resources/muwsarch/index.jsp IBM: http://www-128.ibm.com/developerworks/webservices/library/specification/ws-… map/ Thanks, Heather Kreger, IBM Bryan Murray, HP Igor Sedukhin, CA William Vambenepe, HP Heather Kreger STSM, Web Services Lead Architect for SWG Emerging Technologies Author of "Java and JMX: Building Manageable Systems" kreger(a)us.ibm.com 919-543-3211 (t/l 441) cell:919-496-9572

1 0

Fw: Web Services Management Roadmap published
by Tom Maguire 07 Jun '05

07 Jun '05

Note from Heather Kreger, Bryan Murray, William Vambenepe and Igor Sedukhin bounced.... 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 ----- Forwarded by Tom Maguire/Hawthorne/IBM on 06/07/2005 02:23 PM ----- Heather Kreger/Raleigh/IB M To wsdm(a)lists.oasis-open.org, 06/07/2005 02:12 ogsa-wg(a)gridforum.org, PM wsrf(a)lists.oasis-open.org cc Subject Web Services Management Roadmap published Hello, CA, HP and IBM would like to make you aware of a paper that we have recently published jointly. This paper, 'Management Using Web Services, A Proposed Architecture and Roadmap' characterizes challenges facing the IT systems management community and defines a roadmap and strategy for the evolution of management systems to support emerging business environments. It explains how a common approach for manageability (using Web services infrastructure) can simplify the management solutions for both existing systems and systems based upon emerging Service-Oriented Architectures (SOA). It defines a comprehensive Web services based systems management architecture that supports, integrates, and unifies several popular management models and technologies in a way to manage any IT resource in a platform and language-neutral manner. We believe that WSDM, WSRF, and WS-Notification are some of the foundation standards for this Roadmap. You can get a copy of the management roadmap at one of this links: CA: http://www3.ca.com/technologies/Collateral.asp?CID=70104&ID=3339 HP: http://devresource.hp.com/drc/resources/muwsarch/index.jsp IBM: http://www-128.ibm.com/developerworks/webservices/library/specification/ws-… Thanks, Heather Kreger, IBM Bryan Murray, HP Igor Sedukhin, CA William Vambenepe, HP Heather Kreger STSM, Web Services Lead Architect for SWG Emerging Technologies Author of "Java and JMX: Building Manageable Systems" kreger(a)us.ibm.com 919-543-3211 (t/l 441) cell:919-496-9572

1 0

RE: [ogsa-d-wg] OGSA-D telcon agenda for June 8th - Security; Overall Architecture
by Dave Berry 07 Jun '05

07 Jun '05

This message contained a copy-and-paste mistake: "18th May" should of course read "8th June". Dave. > -----Original Message----- > From: owner-ogsa-d-wg(a)ggf.org > [mailto:owner-ogsa-d-wg@ggf.org] On Behalf Of Dave Berry > Sent: 06 June 2005 21:28 > To: ogsa-d-wg(a)gridforum.org > Cc: ogsa-wg > Subject: [ogsa-d-wg] OGSA-D telcon agenda for June 8th - > Security; Overall Architecture > > Dear all, > > This week's telcon will be on Wednesday (18th May), at the > usual time of > 8:00am PDT / 11:00am EDT / 4:00pm BST / 5:00pm CEST. > > PIN for all calls: 632 065 > > UK Dial In: 0845 245 0224 > US Dial In: 1866 838 0046 > International Dial In: +44 1452 542309 > > > Here is a provisional agenda for this week. > > 1) Early discussion (5 min) > Note taker assignment > Roll call > Minutes approval (http://tinyurl.com/88233) > Agenda bashing > > 2) Action report (5 min) > > - Dave to approach transaction RG re GGF session. > - Peter to write a first cut at the Storage section of the > architecture > document [Done] > - Dave to try to arrange data transfer discussion > - Allen to cut and paste material into document before F2F [Done] > - Dave to forward final F2F meeting info [Done] > - Dave to mail round draft F2F agenda [Done] > > 3) WG status (5 min) > > - Trackers > - GGF working drafts > - GGF session plan > > 4) Security requirements for data grids (20 min) > > 5) Overall architecture (20 min) > > 6) Wrap up (5 min) > AOB > DONM > > > Dave Berry > Research Manager, National e-Science Centre > 15 South College St., Edinburgh > Tel: +44 131 6514039 > >

1 0

Proposed agenda for June 8th call
by Hiro Kishimoto 07 Jun '05

07 Jun '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 8th 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: 0608 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 WSRF basic profile review (60 min) Tom has revised and uploaded the document to the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… profile/en/9 3) Wrap up (10 min) AOB June 13th (Mon) Three documents final review & fellow WG status report June 15th (Wed) OGSA-WG next step discussion June 20th (Mon) CDDLM cross-WG session, EMS architecture ---- Hiro Kishimoto

1 0

RE: [ogsa-bes-wg] Minutes of London meeting?
by Hiro Kishimoto 07 Jun '05

07 Jun '05

Hi all, London F2F meeting minutes is now available on the GridForge. https://forge.gridforum.org/projects/ogsa-bes-wg/document/minutes20050522/e… Thanks Andrew and Mark! ---- Hiro Kishimoto -----Original Message----- From: owner-ogsa-bes-wg(a)ggf.org [mailto:owner-ogsa-bes-wg@ggf.org] On Behalf Of Ian Foster Sent: Friday, June 03, 2005 4:51 AM To: Fred Maciel; ogsa-bes-wg(a)ggf.org Subject: [ogsa-bes-wg] Minutes of London meeting? I haven't seen minutes to the London meeting, that Andrew says will be discussed on the next call, were they circulated? Also, I think it would be helpful to have some discussion of the issues that I raised in earlier email concerning scope, to which two people replied supportively. Ian.

1 0

OGSA Roadmap v10 uploaded
by Treadwell, Jem 06 Jun '05

06 Jun '05

Hi, The Roadmap document for tonight's discussion is available at http://tinyurl.com/77pqn. This version is v10. Thanks, - Jem ________________________________ 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

OGSA-D telcon agenda for June 8th - Security; Overall Architecture
by Dave Berry 06 Jun '05

06 Jun '05

Dear all, This week's telcon will be on Wednesday (18th May), at the usual time of 8:00am PDT / 11:00am EDT / 4:00pm BST / 5:00pm CEST. PIN for all calls: 632 065 UK Dial In: 0845 245 0224 US Dial In: 1866 838 0046 International Dial In: +44 1452 542309 Here is a provisional agenda for this week. 1) Early discussion (5 min) Note taker assignment Roll call Minutes approval (http://tinyurl.com/88233) Agenda bashing 2) Action report (5 min) - Dave to approach transaction RG re GGF session. - Peter to write a first cut at the Storage section of the architecture document [Done] - Dave to try to arrange data transfer discussion - Allen to cut and paste material into document before F2F [Done] - Dave to forward final F2F meeting info [Done] - Dave to mail round draft F2F agenda [Done] 3) WG status (5 min) - Trackers - GGF working drafts - GGF session plan 4) Security requirements for data grids (20 min) 5) Overall architecture (20 min) 6) Wrap up (5 min) AOB DONM Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

Proposed agenda for June 6th call
by Hiro Kishimoto 06 Jun '05

06 Jun '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 6th 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: 0606 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 WSRF Basic Profile discussion (50 min) We will try to close all open issues. Tom will upload the revised version to the GridForge. 3) OGSA roadmap discussion (50 min) We will try to close all open issues. Jem will upload the revised version to the GridForge. 4) Wrap up (10 min) AOB June 8th (Wed) Three documents final review June 13th (Mon) Fellow WG status report June 15th (Wed) OGSA-WG next step discussion ---- Hiro Kishimoto

1 0

(Evolving) Consortium Specification Example
by Hiro Kishimoto 05 Jun '05

05 Jun '05

Hi all, At June 1st call, I took an action item to find more suitable example for Consortium Specification and Evolving Consortium Specification. Since EGA does not intend to define standards, they are not a perfect example for "Consortium." After due consideration and research, I arrive at a proposal of "GLUE schema." The GLUE Schema is a proposed specification by the EU-DataTAG and US-iVDGL projects. http://www.cnaf.infn.it/~sergio/datatag/glue/index.htm I think Glue Schema 1.1 is a Consortium Specification and Glue Schema 1.2 is an Evolving Consortium Specification. Hope it helps, ---- Hiro Kishimoto

1 0

Re: [ogsa-wg] RM teleconference on the 7th: sync with OGSA-BES
by Hiro Kishimoto 04 Jun '05

04 Jun '05

Mark's email bounced. ---- Hiro Kishimoto Date: Sat, 4 Jun 2005 09:15:47 -0400 From: "Mark M. Morgan" <mmm2a(a)cs.virginia.edu> To: Fred Maciel <fred-m(a)crl.hitachi.co.jp> Cc: GGF - ogsa-wg ml <ogsa-wg(a)ggf.org>, ogsa-bes-wg(a)ggf.org Subject: Re: [ogsa-wg] RM teleconference on the 7th: sync with OGSA-BES Just a slight correction -- BES has decided to look seriously at using CIM to model the container, but I don't think we can say with 100% assurance that we "will" use it. Also, the main purpose of the teleconference on Tuesday isn't a synchronization point (that will come later after a decision has in fact been made), but rather Fred offered the teleconference as a way for the OGSA-BES team to learn more about CIM and get details that will help the team come to a conclusion about whether or not CIM is appopriate and if so, how to use it. -Mark > Hi, > > And now for something slightly different. OGSA-BES-WG decided to > use CIM to model the container, and we have to work on the semantics > (choosing what to include from CIM) and the rendering (how we show > that). We will use the Resource Management (RM) teleconference as a > way to join the CIM experts and the related OGSA-BES participants to > discuss the details. Examples of things to discuss: > > - Do we choose the container properties by CIM classes or by CIM > property? What do do if a property in a class has nothing to do with > the container? > - How to render these classes and properties so that they can be accessed? > - What are the properties of a container? Jobs? Operating system? Host > information such as CPU architecture? > - How this relates to the short-term milestone of showing JSIM attributes? > > This teleconference will be an important synchronization point > between OGSA-BES and the RM design team, and a golden opportunity to > get lots of questions on CIM answered. On the other hand, we won't > have time to discuss the CIM-GLUE-JSDL comparision in this > teleconference. > > Date: Tuesday, June 7th, at the following times: > - 11:00-12:00 US Pacific (GMT - 7) > - 12:00-13:00 US Mountain (GMT - 6) > - 13:00-14:00 US Central (GMT - 5) > - 14:00-15:00 US Eastern (GMT - 4) > - 18:00-19:00 GMT > - 19:00-20:00 UK (GMT + 1) > - 20:00-21:00 Central Europe (GMT + 2) > - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. > > 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: 0607 > Explanation: > > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.ht > ml > > See you there, > > Fred Maciel > Hitachi America R&D

1 0

RM teleconference on the 7th: sync with OGSA-BES
by Fred Maciel 03 Jun '05

03 Jun '05

Hi, And now for something slightly different. OGSA-BES-WG decided to use CIM to model the container, and we have to work on the semantics (choosing what to include from CIM) and the rendering (how we show that). We will use the Resource Management (RM) teleconference as a way to join the CIM experts and the related OGSA-BES participants to discuss the details. Examples of things to discuss: - Do we choose the container properties by CIM classes or by CIM property? What do do if a property in a class has nothing to do with the container? - How to render these classes and properties so that they can be accessed? - What are the properties of a container? Jobs? Operating system? Host information such as CPU architecture? - How this relates to the short-term milestone of showing JSIM attributes? This teleconference will be an important synchronization point between OGSA-BES and the RM design team, and a golden opportunity to get lots of questions on CIM answered. On the other hand, we won't have time to discuss the CIM-GLUE-JSDL comparision in this teleconference. Date: Tuesday, June 7th, at the following times: - 11:00-12:00 US Pacific (GMT - 7) - 12:00-13:00 US Mountain (GMT - 6) - 13:00-14:00 US Central (GMT - 5) - 14:00-15:00 US Eastern (GMT - 4) - 18:00-19:00 GMT - 19:00-20:00 UK (GMT + 1) - 20:00-21:00 Central Europe (GMT + 2) - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. 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: 0607 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

Agenda for Monday meeting
by Andrew Grimshaw 03 Jun '05

03 Jun '05

All, Our next telecon is Monday, June 6th at 11 AM Eastern time. Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 Will use glance, ogsa.glance.net. 1 hour Proposed Agenda: Agenda bashing WS Name Resolution from the name document sent out last time. I have uploaded this into the OGSA-WG Naming Design team space until we become a regular working group https://forge.gridforum.org/projects/ogsa-wg/document/WS-Naming_version_0/en /1 Specifically discuss a modification to resolution (minor) to allow for resolution of EPR's that do not contain AbstractNames. Mark Morgan will present. Discuss whether the group is OK with moving forward to turning the draft document into a GGF style document for submission to the process. If and only if we finish the above, charter discussions about RNS. Andrew

1 0

Agenda for Thursday BES call
by Andrew Grimshaw 01 Jun '05

01 Jun '05

Note: Will continue to cross-post to OGSA-wg until after GGF 14. Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 Time: 10 AM eastern 0700 Pacific 3 PM UK 4 PM Europe 1 hour Proposed Agenda: Agenda bashing Overview of conclusions from London meeting Minutes approval of London meeting Management interfaces/resource properties, relationship to DMTF etc. Wrap up As an aside I am preparing a DRAFT GGF style document based on the earlier document.

1 0

RE: [ogsa-wg] Three OGSA documents for GGF14 (Roadmap updated)
by Treadwell, Jem 01 Jun '05

01 Jun '05

Hi, I've updated the Roadmap document in line with contributions made at and following the f2f. There are still a couple of pieces missing, but it's getting pretty close to completion now. It's significantly changed from the earlier draft. I had some issues caused by a Word crash, but I believe I've salvaged everything. If you see any problems, let me know. To avoid clutter I accepted lots of minor editing changes and anything we discussed at the f2f, so the markup mostly reflects the items we need to review. The current version (v9) is at http://tinyurl.com/dbvgh. - Jem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Hiro Kishimoto Sent: Tuesday, May 31, 2005 10:45 AM To: 'ogsa-wg' Subject: [ogsa-wg] Three OGSA documents for GGF14 Hi all, OGSA-WG plans to submit the following three documents before GGF14. These are very good shape but still working documents, please turn MS word comments on and read them at the same time. OGSA WSRF Basic Profile 1.0 https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsr f-basic- profile/ OGSA profile definition 1.0 https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-pro file-tem plate/ Defining the Grid: A Roadmap for the Open Grid Services Architecture https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-roa dmap/ Please have a look. ---- Hiro Kishimoto

1 0

Proposed agenda for June 1st call
by Hiro Kishimoto 01 Jun '05

01 Jun '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 1st 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: 0601 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) London F2F meeting evaluation (30 min) Please upload your materials to GridForge Mark, Andrew: please send out draft minutes before the call. 3) Telecon Schedule discussion (20 min) Hiro will send out draft telecon schedule until GGF14 before the call. 4) OGSA profile definition document review (60 min) Since there are only a few comment left, we expect that this is the final review of this document. Tom has revised and uploaded the document to the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-profil… plate/en/7 5) Wrap up (10 min) AOB June 6th (Monday) is for OGSA WSRF basic profile and roadmap document final review. ---- Hiro Kishimoto

1 1

Byte IO WG Meeting on 21st June
by Mark Morgan 31 May '05

31 May '05

At today's ByteIO Telecon, we decided to postpone the scheduled 14 June 2005 telecon to the next week (21 June 2005) due to the simultaneous absences of both Neil and myself. An agenda should proceed that telecon. -Mark -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.cs.virginia.edu mmm2a(a)virginia.edu (434) 982-2790

1 0

Three OGSA documents for GGF14
by Hiro Kishimoto 31 May '05

31 May '05

Hi all, OGSA-WG plans to submit the following three documents before GGF14. These are very good shape but still working documents, please turn MS word comments on and read them at the same time. OGSA WSRF Basic Profile 1.0 https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… profile/ OGSA profile definition 1.0 https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-profil… plate/ Defining the Grid: A Roadmap for the Open Grid Services Architecture https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-roadma… Please have a look. ---- Hiro Kishimoto

1 0

HPDC this year is not at GGF
by Andrew Grimshaw 31 May '05

31 May '05

High Performance Distributed Computing (HPDC) Fourteen Registration Now Open http://www.caip.rutgers.edu/hpdc2005/ HPDC combines the advances in research and technologies in high speed networks, software, distributed computing and parallel processing to deliver high-performance, large-scale and cost-effective computational, storage and communication capabilities to a wide range of applications. The intent of this meeting is to provide a forum in which researchers report on new ideas and technical insights, application teams express the challenges of constructing wide area or scalable high performance applications, and technology creators report on future developments. The Fourteenth IEEE International Symposium on High-Performance Distributed Computing will be a forum for presenting the latest research findings on the design and use of parallel and distributed systems for high end computing, collaboration, data analysis, and other innovative applications. HPDC is the premier conference for high-performance distributed systems and grid computing systems. Come see the latest developments this July in Raleigh-Durham North Carolina. Keynotes by Dan Reed (http://its.unc.edu/its_vc/) and Pratap Pattniak (http://domino.research.ibm.com/comm/pr.nsf/pages/bio.pattnaik.html) head the program. In addition to the keynotes the results of the latest research from around the world will be presented, as well as two half-day tutorials, the first on the Globus toolkit, and the second on Autonomic Computing. As in past years two exciting workshops proceed the full conference. The first, CLADE (Challenges of Large Applications in Distributed Environments) The goal of CLADE is to encourage innovation by addressing the complex issues that arise in large-scale applications of distributed computation, and to promote the development of innovative applications that effectively use distributed resources and adapt to a wide range of heterogeneity and dynamics in space and time. This includes development, deployment, management and evaluations of large scale applications in science, engineering, medicine, business, economics, education, and other disciplines, on Grids and other distributed heterogeneous and dynamic computing environments. The second workshop is High-Performance Interconnects for Distributed Computing. The purpose of HPI-DC is to explore the confluence of WAN technologies with high performance interconnects, as applicable or applied to realistic high end applications. The intent is to create a venue that will act as a bridge between researchers developing tools and platforms for high-performance distributed computing, end user applications seeking high performance solutions, and technology providers aiming to improve interconnect and networking technologies for future systems. Please visit http://www.caip.rutgers.edu/hpdc2005/ for more information and to register for HPDC. See you there. Andrew Grimshaw

1 0

OGSA-D telcon schedule & preparatory work
by Dave Berry 30 May '05

30 May '05

Dear all, At last week's f2f meeting we decided the following timetable for OGSA-D telcons until GGF14. For some of these we are requesting participants to prepare material in advance - most notably, at next week's telcon we will be discussing security requirements for data grids and it would be very useful if you could circulate your thoughts beforehand. We plan to collect these requirements and present them to the OGSA security design team and other interested parties. * Topics June 1st: No telcon this week. June 8th: 1. Security requirements for data grids; participants to circulate notes in advance 2. Overall architecture June 15th: To be decided June 22nd: 1. GGF preparation; speakers to have draft slides ready for review 2. Data transfer June 29th: GGF14 (therefore no telcon) Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

GridToday Security Article by Tony Hey
by Hiro Kishimoto 30 May '05

30 May '05

Hi all, Interesting security article by Tony Hey, Security, Security, Security By Tony Hey, Contributing Author Security is a major issue in Grid computing, and in this article, Tony Hey, director of the U.K. e-Science Program, gives his two cents on the issue. He also recaps a recent meeting in London where experts from around the world gathered to discuss the various problems and issues surrounding Grid security. http://news.taborcommunications.com/msgget.jsp?mid=389414&xsl=story.xsl ---- Hiro Kishimoto

1 0

teleconference on the 31st *CANCELLED*
by Hiro Kishimoto 28 May '05

28 May '05

Fred's email bounced. ---- From: "Fred Maciel" <fred-m(a)crl.hitachi.co.jp> Subject: RM teleconference on the 31st *CANCELLED* Date: Fri, 27 May 2005 19:29:46 -0700 Hi, Most of the week was taken by the face-to-face meetings in London, and Monday is a holiday in the U.S., so I don't think that we'll have anything new to discuss. Let's cancel the teleconference on the 31st. Regards, Fred Maciel Hitachi America R&D

1 0

NO tele-conferenece on May 30th.
by Hiro Kishimoto 28 May '05

28 May '05

Hi all, Thank you very much for all of you who have come to the London F2F meetings. It was very good meetings. We had a lot of productive discussions, dedicated reviews and homework assignments :-) Let's keep the ball rolling, submit our three documents before GGF14, and meet you again in Chicago. Given that we need a respite and the next Monday is US holiday, we agreed that we do NOT have next Monday call. Our next call is on Wednesday June 1st. Enjoy the Memorial Day holiday, ---- Hiro Kishimoto

1 0

Perhaps useful input to BES discussion
by Ian Foster 26 May '05

26 May '05

Dear All: I am sending this draft document in case it is relevant to the OGSA-WG and/or BES discussions. In this document, I use a simple example (a skeleton execution service) to compare and contrast four approaches to representing state, namely WSRF, WS-Transfer, REST, and "state id." I haven't sent this earlier because I'd hoped to integrate numerous comments that I've received from Savas and others. I hope to do so in the next week or two, but perhaps this draft is still of interest. Regards -- Ian. _______________________________________________________________ Ian Foster www.mcs.anl.gov/~foster Math & Computer Science Div. Dept of Computer Science Argonne National Laboratory The University of Chicago Argonne, IL 60439, U.S.A. Chicago, IL 60637, U.S.A. Tel: 630 252 4619 Fax: 630 252 1997 Globus Alliance, www.globus.org

4 6

Proposal to establish Tom Maguire as co-chair
by Hiro Kishimoto 26 May '05

26 May '05

Hi all, As you all must have observed, Tom Maguire has not only been a very active OGSA-WG member since the beginning, but has also been making wonderful contributions to develop our accomplishment, especially the OGSA WSRF Basic Profile and the OGSA profile definition documents. At the London F2F meeting yesterday, all F2F attendees agreed to nominate Tom Maguire as a new OGSA-WG co-chair. Tom has indicated that if this proposal meets the approval of the OGSA-WG, his management, and the GFSG, he will be happy to take on this role. If you have any concerns about this proposal, please communicate with Andrew Grimshaw, our Area Director, or I via email or phone before Thursday June 2nd. In the absence of any objections, we will then forward this OGSA-WG's proposal of new co-chair to the GFSG. Best Regard, ---- Hiro Kishimoto

3 2

Profile definition v1.7 available for review
by Tom Maguire 25 May '05

25 May '05

Folks, I have updated the profile definition with the AIs and comments from the London F2F. Please review so that we can finalize on the telecon scheduled for review. Tom https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-profil… . 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

Tom's apology for F2F
by Hiro Kishimoto 24 May '05

24 May '05

Tom's email bounced. ---- Hiro Kishimoto Date: Sun, 22 May 2005 22:15:00 -0400 From: Tom Maguire <tom.maguire(a)suscom.net> Subject: Re: [ogsa-wg] Dial-in number for London F2F meeting I'll be dialing in at 4:30 AM ET. (9:30 AM BST). Speak to you then. Sorry not there in person personal family matters,,, Tom Hiro Kishimoto wrote: > > >Hi all, > >It turns out that the meeting room at IC does not have phone line. >Thus a phone bridge is not working. > >If you plan to dial in, we may try to use skype instead. > >Sorry for any inconvenience. >---- >Hiro Kishimoto

1 0

Re: [ogsa-wg | Basic Profile - 1367] Appendix A KeyInfoElement; why not ds:KeyInfoElement
by Takuya Mori 23 May '05

23 May '05

Hi All, I'm sorry for making a comment on the issue. The point with not reusing that element was that there are certain semantics associated with what we want to represent in the EPR metadata and reusing the KeyInfo element as specified by the dsig spec looses those semantics. From: Sourceforge Tracker Monitor <noreply(a)forge.gridforum.org> Subject: [ogsa-wg | Basic Profile - 1367] Appendix A KeyInfoElement; why not ds:KeyInfoElement Date: Mon, 23 May 2005 05:42:57 -0500 > > David Snelling changed 1367 on 2005-05-23 11:42:56 > > > > Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1367&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1367&group_id…) > > Summary: Appendix A KeyInfoElement; why not ds:KeyInfoElement > Project: Open Grid Services Architecture > Tracker: Basic Profile > Artifact ID: 1367 > Category: <None> > Group: <None> > Status: Pending > Priority: 2 > Last Modified By: David Snelling > Last Modified: 2005-05-23 11:42:56 > Submitted By: Tom Maguire > Submit Date: 2005-04-13 20:37:49 > Assigned To: Takuya Mori > File(s): <None> > Description: > Why create a new element and not use the digsig element for key info > ---------------------------------------------------------------------- > Comment By: David Snelling (2005-05-23 11:42:56) > no comments on those. Except the ds:keyinfo; I think we should be using it > instead of our own namespace. I will be updating the doc but not before > 12. I will be 'virtually present' on the phone. There will be a clean > copy of BP and Prof Def in your inbox by Sat AM ET. > > Tom > > > ---------------------------------------------------------------------- > Comment By: Tom Maguire (2005-04-20 20:58:05) > email discussion on why not ds namespace > ---------------------------------------------------------------------- > Comment By: Tom Maguire (2005-04-13 20:38:37) > Mailing list discussion follow on to current thread > ---------------------------------------------------------------------- > > > View the Basic Profile : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…) > > ________________________________________ > Modify your monitoring preferences: https://forge.gridforum.org/monitoring/monitorPreference.php (https://forge.gridforum.org/monitoring/monitorPreference.php) > Turn off monitoring for this Tracker: https://forge.gridforum.org/tracker/?group_id=42&atid=780&aid=1367&func=mon… (https://forge.gridforum.org/tracker/?group_id=42&atid=780&aid=1367&func=mon…)

1 0

communication of assertions
by Takuya Mori 23 May '05

23 May '05

Hi All, This message is intended to start the discussion on the WSRF-BP Tracker Item #1323 (and hopefully to close it). TI#1323 Summary: Communication of assertions Description: Profiles for common assertions in headers or Proxy Certificate I'd like to propose to add the following to the WSRF Basic Profile 1.0 ---- 8.1.x or 8.x Communications of assertions Senders MAY send assertions that can be used for policy decisions including access control decision by receivers with SOAP messages. The assertions MUST be SAML assertions or X509 attribute certificates and senders and receivers MUST adhere to the Basic SEcurity Profile or SAML Token Profile Version 1.0 when sending assertions. R08xx When communicating SAML assertions, a SENDER and a RECEIVER MUST comply with SAML Token Profile Version 1.0 R08xx When communicating X509 attribute certificates, a SENDER and a RECEIVERMUST comply with the Basec Security Profile Version 1.0 Section 5. ---- Here is some background on my proposal. I think's it is better not to use proxy certificate as a mean for communication of assertions, because there is no standardized way of embedding assertions in X509 certificates as certificate extentions, thus, developing such a standard would be too costly. ---- Takuya Mori

1 0

OGSA WSRF Basic Profile v013 posted
by Tom Maguire 23 May '05

23 May '05

Sorry for the late post. Lastest BP was posted last night 5/22. Tom 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

Dial-in number for London F2F meeting
by Hiro Kishimoto 23 May '05

23 May '05

Hi all, Dial-in number for London F2F meeting is as follows. These numbers work for Sunday through Thursday. This is provided by Fujitsu Laboratories of Europe. Thanks Dave for your support. UK toll free: 0808 1005145 US toll free: 1866 2485984 JP toll free: 0034 800400552 Pass code: 2051278 See "BT MeetMe Global Access numbers sheet" for another countries. Thanks, ---- Hiro Kishimoto

2 3

GGF14 day one schedule
by Hiro Kishimoto 20 May '05

20 May '05

Hi all, Per my homework assignment at the last Wednesday call, I've asked Julie and Steve about GGF14 schedule and the following is Julie's answer. Also, GGF14 web page has been updated accordingly. > The opening plenary is on Tuesday with workshops and the Gridwise > tutorial on Monday. WG/RG Sessions will be scheduled from Tuesday, June 28- Thursday, June 30. Thanks Julie and Steve, ---- Hiro Kishimoto

1 0

Agenda for BES on Sunday
by Andrew Grimshaw 19 May '05

19 May '05

AGENDA Objective: Not only discuss - but write the draft BES specification for subsequent tuning prior to GGF in Chicago. 10:00-10:30 Organization Grimshaw Introductions Agenda bashing 10:30-11:00 - Overall Service Structure Grimshaw What are the parts? E.g., service "factory-like" components - see original document, "management" aspects, etc. There will be a strawman presented 11:00-12:15 Submit/create/info/destroy interface - see existing documents Short background on JSDL Steve McGough (Note: please read the current JSDL specification before arriving) JSDL "profile" to use, i.e., what subset of JSDL do we expect BES to understand 12:15-12:30 Recap and summarize 12:30-13:30 Short lunch and informal discussions 13:30-15:00 "Management" aspects of BES containers Resource model presentation by Fred Maciel - 30 min 15:00-15:15 Break 15:15-16:30 Break up into groups and write sections 16:30-18:00 Integrate and discuss sections 18:00-21:00 Beer, dinner, and gossip

1 0

OGSA Data WG status report
by Dave Berry 19 May '05

19 May '05

Dear all, Here is a short update of OGSA-D activity. The OGSA-D (OGSA Data Architecture working group was officially approved in late April by the GGF Steering committee. The WG now has its own place in Grid Forge and its own mailing list (ogsa-d-wg(a)ggf.org) The group continues to hold weekly teleconferences, every Wednesday at 8 AM PDT (4 PM BST). The last two calls have focused on replication and storage management. The Data Architecture document is evolving with new material on replication and DAIS being added in recent weeks. We will hold a face to face meeting on May 26 at Imperial College in London, following the OGSA WG face to face meeting. We plan to have multiple sessions at GGF-14 including a community update session, one on data transfer and one possibly on transactions. Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

BES telecon
by Andrew Grimshaw 19 May '05

19 May '05

All, Recall there is no telecom this week. (I had thought there was - but on checking last week's mail there is not.) We will be sending out an agenda for Sunday later this afternoon. Note: we will be starting at 10 am, not 9:00. Andrew

1 0

The latest GGF14 session plan
by Hiro Kishimoto 19 May '05

19 May '05

Hi all, The latest GGF14 session plan also includes "OGSA fellow WGs' session information." Dave Berry gave us OGSA-data WG's plan and it is now on the second worksheet of the MS excel sheet. https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan/en… Thanks Dave, ---- Hiro Kishimoto

1 0

Revised London F2F meeting agenda draft
by Hiro Kishimoto 19 May '05

19 May '05

Hi all, I've updated meeting attendees and the day four (May 26, Thu) agenda for OGSA-D meeting. You can download it from the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/OGSA_2005_May_F2F_Age… n/5 Thanks Dave Berry for the information. See you guys in London! ---- Hiro Kishimoto

1 0

Proposed agenda for May 18th call
by Hiro Kishimoto 18 May '05

18 May '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on May 18th 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: 0518 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) London F2F meeting update (20 min) Draft agenda and logistic information; https://forge.gridforum.org/projects/ogsa-wg/document/OGSA_2005_May_F2F_Age… 3) GGF14 session plan review (20 min) Updated session plan; https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan 4) OGSA roadmap discussion (40 min) Jem will upload revised version before the call. 5) Wrap up (10 min) AOB We will have F2F meeting in London next week. ---- Hiro Kishimoto

1 0

Resigning as OGSA-WG co-chair
by Ian Foster 18 May '05

18 May '05

Dear All: As you all know, I have been OGSA-WG chair since the formation of OGSA-WG. However, over the last year, I have not been engaging at anything like the level required of a WG chair. This is due partly to an increasing number of other demands on my time, partly to changing funding profiles at Argonne which leave me with no explicit support for GGF work, and partly (I have to admit) to my temperament, which does not deal well with regular phone calls and meetings. My lack of engagement has not explicitly hindered OGSA-WG, because Hiro has been doing such an amazing job. However, while Hiro has emphasized to me that it is useful to have me engaged even at a low level, I have been finding it increasingly embarrassing to be holding this position when I am not doing the work. In addition, I believe that there is an opportunity cost: we could be engaging someone else as co-chair who would do far more than I. The last straw, from my perspective, is that I have just discovered that I am not able to attend next week's OGSA-WG F2F due to another commitment. For these reasons, I hereby resign as OGSA-WG co-chair. I plan to stay involved in OGSA-WG where this makes sense, but I don't want to have any management role. I want to emphasize that this resignation does not reflect in any way a lack of commitment to GGF or OGSA by myself or my Globus colleagues. We plan to continue our engagement in GGF and OGSA standards development, to the extent that resources permit, and to implement GGF and OGSA specifications whenever feasible. I won't say "it's been a pleasure working with you all" as I plan to continue to be engaged! Regards -- Ian.

2 1

RM - teleconference minutes - May 17. 2005
by Fred Maciel 17 May '05

17 May '05

Hi, Here are the minutes (attached file). Regards, Fred Maciel.

1 0

ByteIO Use Case Template Document
by Mark Morgan 17 May '05

17 May '05

After this morning's telecon, we have update the ByteIO Use Case Template document and placed it in GridForge at https://forge.gridforum.org/projects/byteio-wg/document/UseCaseTemplate/en/1 . We plan on discussing draft use cases at the face to face meeting in London next week. -Mark -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.cs.virginia.edu mmm2a(a)virginia.edu (434) 982-2790

1 0

Revised GGF14 session plan & London F2F meeting agenda
by Hiro Kishimoto 17 May '05

17 May '05

Hi all, Based on the today's discussion, I've updated GGF14 session plan and upcoming London F2F meeting agenda. https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan/en… https://forge.gridforum.org/projects/ogsa-wg/document/OGSA_2005_May_F2F_Age… n/2 If you have any questions or comments, please let me know. Thanks, ---- Hiro Kishimoto

1 0

RM - teleconference reminder
by Fred Maciel 17 May '05

17 May '05

Hi, Our next teleconference is on Tuesday, May 17th, at 11 AM PDT. The screen sharing information is below: Topic: fmaciel's meeting Date: Tuesday, May 17, 2005 Time: 11:00 am, Pacific Daylight Time (GMT -07:00, San Jose) Meeting number: 738 971 522 Meeting password: ogsa-rm Please click the following link to see more information, or to join the meeting. <https://btconferencing.webex.com/btconferencing/j.php?ED=86419472&UID=28627 157> See you then, Fred Maciel.

1 0

OGSA-D telcon agenda for May 18 - F2F planning
by Dave Berry 16 May '05

16 May '05

Dear all, This week's telcon will be on Wednesday (18th May), at the usual time of 8:00am PDT / 11:00am EDT / 4:00pm BST / 5:00pm CEST. PIN for all calls: 632 065 UK Dial In: 0845 245 0224 US Dial In: 1866 838 0046 International Dial In: +44 1452 542309 Here is a provisional agenda for this week. 1) Early discussion (5 min) Note taker assignment Roll call Minutes approval (attached, http://tinyurl.com/b4qxv) Agenda bashing 2) Action report (5 min) - Dave & Allen to add GGF working drafts to agenda for May 18 call [Done] - Dave & Allen to finalize session plan at May 18 call and send in session requests ASAP after that. - Dave & Allen to make F2F agenda discussion to be part of the May 18 call [Done] - Dave & Allen to publish approximate start and end times for the F2F ASAP to allow people to finalize travel plans. - Dave & Allen to make sure the F2F on May 26 should include a session to discuss how to identify data and how to get the bits into and out of storage. - Peter to write a first cut at the Storage section of the architecture document. - Dave to try to arrange data transfer discussion. - Mario to further update the access section. - Dave to approach transaction RG re GGF session? 3) Document status (15 min) - Reports from contributors 4) WG status (15 min) - GGF working drafts - GGF session plan 5) F2F agenda (15 min) - ByteIO - How to identify data and how to get the bits into and out of storage - Document structure 6) Wrap up (5 min) AOB DONM Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

Proposed agenda for May 16th call
by Hiro Kishimoto 16 May '05

16 May '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on May 16th 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: 0516 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html Since Tom and Dave are at WSRF F2F and cannot make the call, we will have BP and Profile definition discussion at London F2F. Fred has the kindness to give us introduction on recently released EGA reference model. Please download and read their document before the call. 1) Early discussion (10 min) Note taker assignment Roll call Telecon minutes approval (if available) Agenda bashing 2) London F2F meeting update (20 min) Draft agenda and logistic information; https://forge.gridforum.org/projects/ogsa-wg/document/OGSA_2005_May_F2F_Age… 3) GGF14 session plan review (20 min) Updated session plan; https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan 4) EGA reference model introduction (60 min) The EGA Reference Model has been released on May 11th. It can be downloaded from the EGA site: http://www.gridalliance.org/ Fred has the kindness to give us introduction on recently released EGA reference model. Please download and read their document before the call. 5) Wrap up (10 min) AOB May 21 (5-7pm CDT) F2F preparation, roadmap discussion See telecon schedule until May F2F: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule ---- Hiro Kishimoto

2 1

GGF14 session plan
by Hiro Kishimoto 15 May '05

15 May '05

Hi all, We has discussed GGF14 session plan at today's call. The attached is the agreed draft plan revised by Fred. Many thanks Fred. It is also uploaded to the GridForge. https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan/en… Thanks, ---- Hiro Kishimoto

1 1

RM teleconference minutes - May 9, 2005
by Fred Maciel 14 May '05

14 May '05

Hi, Here are the minutes of the teleconference (attached file). Regards, Fred Maciel.

2 1

ByteIO WG Status
by Hiro Kishimoto 14 May '05

14 May '05

Mark's email bounced. ---- Hiro Kishimoto From: "Mark Morgan" <mmm2a(a)virginia.edu> Subject: ByteIO WG Status Date: Fri, 13 May 2005 10:45:50 -0400 All, Hiro requested that I send a brief paragraph out to the ogsa mailing list to give status for the byteio-wg. The ByteIO WG is now an official OGSA WG. We have a mailing list that you can subscribe to if you like (byteio-wg(a)ggf.org) Our telecons are every other Tuesday (the next one being on 17 May 2005) at 10am Eastern. So far we have discussed the following topics: * Telecon Schedules * Use Case Template Document * Technological Issues with bulk data transfer The bulk data transfer issues revolve around trying to come up with a bulk data transfer solution that is well supported and adopted without sacrificing flexibility and interoperability with other WS specifications. We want to make sure that solutions which work for firewalls, NATs, security, etc. are viable for whatever bulk data transfer mechanisms we come up with. We have looked at a number of different options including PBIO, DIME Attachments, MTOM, etc. Initial reactions seem to be to support to some degree user-specifiable transfer options. The main problem with picking eitehr DIME or MTOM is availability and stability of the spec. We have also sent out to the mailing lists (both byteio, and ogsa) the use case template document that we want comments on. We will use this to write up the use case document and discussions on both feedback from the template and initial use cases to start on next week's telecon. -Mark -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.cs.virginia.edu mmm2a(a)virginia.edu (434) 982-2790

1 0

RM - host model comparison
by Fred Maciel 14 May '05

14 May '05

Hi, Here is the start of the host part of the CIM-GLUE comparison. It only includes the GLUE 1.2 classes for matchmaking CIM processor and memory-related classes for now. Regards, Fred Maciel.

1 0

Draft agenda for 2005 May F2F meeting
by Hiro Kishimoto 13 May '05

13 May '05

Hi all, I've upload an early draft for upcoming London F2F meeting agenda to the gridForge. https://forge.gridforum.org/projects/ogsa-wg/document/OGSA_2005_May_F2F_Age… n/1 or http://tinyurl.com/cppse Please have a look and please let me know if you want to add some additional topic to discuss or find any mistakes. We will discuss it at upcoming Monday call. Andrew, Steve, Darren: Please provide OGSA-BES meeting agenda Dave, Allen, Mark, Neil: Please provide data & byteIO meeting agenda Thanks, ---- Hiro Kishimoto

2 1

Proposed agenda for May 11th call
by Hiro Kishimoto 11 May '05

11 May '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on May 11th 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: 0511 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 (May 9th) - Andreas will send out May F2F meeting update (if any) Agenda bashing 2) GGF14 session plan (20 min) Fred has revised and sent out updated session plan. Thanks Fred, https://forge.gridforum.org/projects/ogsa-wg/document/GGF14_session_plan Joel Replogle, new GGF Standards Facilitator, asked us to let him know our session plan at GGF14. In order to avoid conflict with related WG's session, OGSA-WG should schedule proactively. The deadlines are: Documents - Deadline for submitting working drafts is May 27, 2005. Session - Deadline for session requests for a WG or RG is Jun 3, 2005. 3) OGSA fellow WG monthly reporting session (40 min) - OGSA-ByteIO WG - OGSA-Data WG - OGSA-BES WG - OGSA-naming WG 4) OGSA roadmap discussion (40 min) >From Jem's email. > Hi, I just uploaded version 7 of the Roadmap document - you can find it > at http://tinyurl.com/8p6mj. In this version I created the major > sections we'll need to complete, including the data I received from Dave > B and Andrew, and accepted all changes so that we have a clean starting > point (there were no significant changes other than insertion of these > sections). > > If you're providing roadmap data, please use the latest version of the > document as your base - you can cut/paste your section or send the whole > document for merging. Thanks Jem, 5) Wrap up (10 min) AOB May 16 (5-7pm CDT) TBD May 19 (5-7pm CDT) F2F preparation See telecon schedule until May F2F: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule ---- Hiro Kishimoto

1 1

EGA Reference Model released
by Fred Maciel 11 May '05

11 May '05

Hi, The EGA Reference Model has just been released today. It can be downloaded from the EGA site: http://www.gridalliance.org/ I'm reading it now, and the contents are really good. I'm looking forward to the joint session in GGF14. Regards, Fred Maciel.

1 0

Proposed agenda for May 9th call
by Hiro Kishimoto 10 May '05

10 May '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on May 9th 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: 0509 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 (April 27th) https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050427/en/1 May F2F meeting update (if any) Agenda bashing 2) GGF14 session plan (20 min) Joel Replogle, new GGF Standards Facilitator, asked us to let him know our session plan at GGF14. In order to avoid conflict with related WG's session, OGSA-WG should schedule proactively. The deadlines are: Documents - Deadline for submitting working drafts is May 27, 2005. Session - Deadline for session requests for a WG or RG is Jun 3, 2005. 3) OGSA basic profile review (40 min) The latest draft (v012) https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-basic-… le/en/7 4) OGSA profile definition review (40 min) The latest draft (v1.5) https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-profil… plate/en/4 5) Wrap up (10 min) AOB May 11 (5-7pm CDT) Roadmap discussion, fellow WGs status reporting May 16 (5-7pm CDT) TBD May 19 (5-7pm CDT) F2F preparation See telecon schedule until May F2F: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule ---- Hiro Kishimoto

2 3

Agenda for May 12 call
by Andrew Grimshaw 09 May '05

09 May '05

All, Attached are the (short) minutes from the last call. Note: The call-in information has changed!!! Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 Proposed Agenda: Agenda bashing Continue agreement discussion 20 - minutes Discussion of the question of "how basic is basic?" Steven asked a good question on the call two weeks ago. To paraphrase, is for example, file staging out of scope - because file staging is itself a service that would be invoked and managed by a "job manager". I'll give a more precise definition on the call. Note this is the last call before the F2F on Sunday in London. Steven, do we have a local yet? Andrew

1 0

WS-Naming
by Andrew Grimshaw 09 May '05

09 May '05

All, After a bit of a delay we are ready to start discussions on naming. A few things. First, finding a time that does not collide with other OGSA/GGF calls was a challenge. We decided on Mondays at 11 AM eastern. Dial in information: Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 The first call will be on Monday, May 16. The proposed agenda is: Charter - specifically scope and timing of documents. Suitability of existing standards and systems to fill the requirements. Specifically, WS-Addressing by itself, WS-Discovery, and Handle. Note to supporters of Handle. The license on the web site is very restrictive. I personally feel it is unacceptable as it stands. Evidence that a different license model is now in use is needed to continue examining Handle in my view. The May 23 call will not take place. Instead interested parties will caucus at the OGSA F2F meeting in London. Second, I am attaching three documents. The strawman draft WS-Name document that we presented in Korea, the naming requirements document draft that the naming design team in OGSA developed, and a revised charter. Andrew Grimshaw

1 0

Roadmap document v7 uploaded
by Treadwell, Jem 09 May '05

09 May '05

Hi, I just uploaded version 7 of the Roadmap document - you can find it at http://tinyurl.com/8p6mj. In this version I created the major sections we'll need to complete, including the data I received from Dave B and Andrew, and accepted all changes so that we have a clean starting point (there were no significant changes other than insertion of these sections). If you're providing roadmap data, please use the latest version of the document as your base - you can cut/paste your section or send the whole document for merging. Thanks! - Jem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Treadwell, Jem Sent: Wednesday, May 04, 2005 6:18 PM To: ogsa-wg Subject: RE: [ogsa-wg] RE: Proposed agenda for Wed May 4th call (need schedule input!) Or maybe not... Only Mark Morgan, Mike Behrens and I were on the call by 6:10, so no meeting was held, and no minutes will be posted :0) I received input from Dave Berry and Allen Luniewski for the Data Architecture doc, which I'll merge into the Roadmap doc, along with anything else I receive. See you on Monday... - Jem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Treadwell, Jem Sent: Wednesday, May 04, 2005 5:49 PM To: ogsa-wg Subject: RE: [ogsa-wg] RE: Proposed agenda for Wed May 4th call (need schedule input!) Hi, I received some input, so we'll go ahead with the call. I'll have a glance session running at ogsa.glance.net, with a session-id of 0504. - Jem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Treadwell, Jem Sent: Wednesday, May 04, 2005 4:16 PM To: ogsa-wg Subject: [ogsa-wg] RE: Proposed agenda for Wed May 4th call (need schedule input!) Hi, I haven't received any schedule input for the roadmap. If anybody is planning to have any to discuss at today's meeting can you please let me know, even if you don't have it ready yet? If there's no roadmap input to discuss, and if nobody has any other business for the agenda, we won't have a meeting tonight. If that's the case I'll send a follow-up message by 5:45 pm US Eastern time. Thanks, - Jem -----Original Message----- From: Treadwell, Jem Sent: Tuesday, May 03, 2005 11:58 AM To: 'ogsa-wg' Subject: Proposed agenda for Wed May 4th call (need schedule input!) Hi, Wednesday's call is intended for discussion of schedule information for the roadmap document. Hiro sent a series of requests to working group and design team leads last week, asking for input for their sections based on the template we reviewed last week. For those who received Hiro's mail: If you're able to provide input for this week's meeting, please try to send it to me in time for me to merge it into the Roadmap doc, so that we can review a single document. If you can't do that, we can still review your input as a separate document, and I can merge it later, but please try to get it to me before the meeting. Thanks! Below is the proposed agenda for the meeting. - Jem The following is a proposed agenda for OGSA-WG telecon on Wednesday May 4th 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: 0504 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 Agenda bashing 2) OGSA roadmap document review (60 min) Jem will upload a new version of the document with schedule info before the call (if schedule info has been provided). Tracker for the roadmap: https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&at id=789 3) Wrap up (10 min) AOB See telecon schedule until May F2F: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule ---- Jem Treadwell

1 0

RM teleconf ** more info **
by Fred Maciel 09 May '05

09 May '05

Hi again, I just scheduled screen sharing for the teleconference. Let's give it a try. The information below should suffice. Regards, Fred Maciel. ----------------------------- Topic: OGSA RM teleconf Date: Monday, May 9, 2005 Time: 11:00 am, Pacific Daylight Time (GMT -07:00, San Jose) Meeting number: 731 075 248 Meeting password: ogsa-rm Please click the following link to see more information about the meeting, including its agenda, or to join the meeting. <https://btconferencing.webex.com/btconferencing/j.php?ED=86316762&UID=28389 037>

1 0

OGSA-D telcon agenda for May 11 - Storage Management
by Dave Berry 07 May '05

07 May '05

Dear all, Here are the planned topics for upcoming telcons: May 11 - Data storage May 18 - Document review & plan for F2F May 25 - no call? May 26 - F2F, Imperial College London This week's telcon will be on Wednesday (11th May), at the usual time of 8:00am PDT / 11:00am EDT / 4:00pm BST / 5:00pm CEST. PIN for all calls: 632 065 UK Dial In: 0845 245 0224 US Dial In: 1866 838 0046 International Dial In: +44 1452 542309 Here is a provisional agenda for this week. 1) Early discussion (5 min) Note taker assignment Roll call Minutes approval (attached, http://tinyurl.com/d8fvd) Agenda bashing 2) Action report (5 min) - Dave to try to arrange data transfer discussion. - Allen to mail Steve about adding Allen and Dave as GridForge admins [Done] - Mario to further update the access section. - Dave to approach transaction RG re GGF session? 3) WG status (5 min) 4) F2F update (5 min) 5) Technical content (35 min) - Storage Management 6) Wrap up (5 min) AOB DONM Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

RM comparison proposal
by Fred Maciel 07 May '05

07 May '05

Hi, Here is a *proposal* for the *format* of the comparison, still without meaningful content. Let's discuss it on the teleconference on Monday. Regards, Fred Maciel Hitachi America R&D

1 0

RM design team -- teleconf minutes and pointers to docs
by Fred Maciel 06 May '05

06 May '05

Hi, First of all, here are the minutes of the teleconference (attached file). BTW, our next teleconference will be next week, at the same time (Tuesday, 11AM PDT). I'll post a reminder on Monday. Here is a list of pointers on the specs that we are going to analyze: - GLUE 1.1: the schemas are in http://www.cnaf.infn.it/~sergio/datatag/glue/index.htm We'll work on the part under the " Computing (FINAL)" link. I also found a good presentation on GLUE 1.1 today. It also metions a certain CRM-WG... :-) http://www.dma.unina.it/~murli/SummerSchool/presentations/InformationModeli… - GLUE 1.2: the development can be followed in the mailing list archives -- see the "Mailing list (archive) " link in the first URL above. The latest draft can be found under: http://www.hicb.org/pipermail/glue-schema/2005/frm00057.html - 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, which does not match the spec though: https://forge.gridforum.org/projects/cgs-wg/document/JSIM_UML/en/1 - CIM: the schemas are under: http://www.dmtf.org/standards/cim JSIM is in 2.9.1 preliminary. Try 2.9.0 to get also UML files. - JSDL: the latest snapshot is at: https://forge.gridforum.org/projects/jsdl-wg/document/draft-ggf-jsdl-spec/e… There's a nice introduction at: https://forge.gridforum.org/projects/jsdl-wg/document/JSDL-Introduction/en/ Did I forget anything? Regards, Fred Maciel.

2 2

GGF14 joint session proposals
by Fred Maciel 06 May '05

06 May '05

Hi, (1) The WSDM TC is proposing a joint session with the OGSA-WG in GGF14. Accepted? Apart from that, WSDM will have many activities in GGF14: - A plenary kind of session (29th, 2:00p - 3:30p) in which they will demo WSDM - A "deep dive" session to do a more in-depth technical explanation of the spec - A joint session with the CDDLM-WG, which is already using WSDM in its specs - A face-to-face meeting on the 30th (full-day). (2) The DMTF UCWG (Utility Computing WG) would like to have a joint session with the OGSA-WG. The target is the OGSA-WG as a whole, but especially EM. To give some context, when they draw the diagram of the context they are in, they end up with something like the EM diagram. A joint meeting would be great to align the two. (BTW, the EGA is also requesting a joint session, but I hear that Andrew is co-ordinating that one). (3) I'll probably book a couple of sessions as work sessions for the RM design team to work on models, which might require some coordination with OGSA-BES. More on that later. Regards, Fred Maciel.

1 0

***SPAM*** Family seeking for urgent assistance
by donna mills 05 May '05

05 May '05

FROM:Mr. Davis Edward. TEL: 0027 722 780 966 Fax: 0027 11 7252009 Please reply with alternative email: d_family30(a)yahoo.co.uk Attn: Owner / Ceo. This might be a surprise to you about where I got your contact address. I got your address from the intenet, website of South African Chamber of Commerce in johannesburg, South Africa. My name is Mr. Davis Edward,the elder son of late Mr. Samuel Edward, of Masingo Province of Zimbabwe. During the current war against the farmers in Zimbabwe from the supports of our President Robert Mugabe, to claim all the white-owned farms to his party members and his followers, he ordered all white farmers to surrender all their farms to his party members and his followers. My father is one of the richest farmers in our country and because he did not support President Mugabe's ideas. President Mugabe's, supporters invaded my father's farm and burnt everything in the farm, killing my father and made away with a lot of items in my father's farm. Before my father,s death he made it known to me that he deposited with one of the Security Company in Johannesburg, South Africa the sum of US$30.5 Million (Thirty Million Five Hundred Thousand United States Dollars).with the Security and Finance Company here in South Africa. Then after the death of my father, we decided to move to the Republic of South Africa where he had deposited the money in the Security Company as valuables. After reading about you on the internet I believe that some body like you will be capable of handling this kind of transaction so I decided to contact you to assist me to transfer this found out of South Africa because as I and my families were (Refugee) Asylum seekers we are not allowed to operate any bank transaction within South Africa. We have agreed to offer you 20% of the total sum for your assistance, 5% will be mapped out for any expenses that we may incurred in the course of this transaction and 75% will be for me and my family . Besides that my family and I would like you to look for us any profitable business we can invest this found on, in your country. All I want you to do is to furnish me with your full personal phone and fax numbers for easy communication. You can contact me on the above Telephone number.I asure you that this transaction is 100% risk free and absolutely confidential. Thanks and God bless. Best Regards. Mr. Davis Edward. (for the family) Please address the fax to Mr. Davis Edward.

1 0

RE: [ogsa-wg] RE: Proposed agenda for Wed May 4th call (need schedule input!)
by Treadwell, Jem 04 May '05

04 May '05

Or maybe not... Only Mark Morgan, Mike Behrens and I were on the call by 6:10, so no meeting was held, and no minutes will be posted :0) I received input from Dave Berry and Allen Luniewski for the Data Architecture doc, which I'll merge into the Roadmap doc, along with anything else I receive. See you on Monday... - Jem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Treadwell, Jem Sent: Wednesday, May 04, 2005 5:49 PM To: ogsa-wg Subject: RE: [ogsa-wg] RE: Proposed agenda for Wed May 4th call (need schedule input!) Hi, I received some input, so we'll go ahead with the call. I'll have a glance session running at ogsa.glance.net, with a session-id of 0504. - Jem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Treadwell, Jem Sent: Wednesday, May 04, 2005 4:16 PM To: ogsa-wg Subject: [ogsa-wg] RE: Proposed agenda for Wed May 4th call (need schedule input!) Hi, I haven't received any schedule input for the roadmap. If anybody is planning to have any to discuss at today's meeting can you please let me know, even if you don't have it ready yet? If there's no roadmap input to discuss, and if nobody has any other business for the agenda, we won't have a meeting tonight. If that's the case I'll send a follow-up message by 5:45 pm US Eastern time. Thanks, - Jem -----Original Message----- From: Treadwell, Jem Sent: Tuesday, May 03, 2005 11:58 AM To: 'ogsa-wg' Subject: Proposed agenda for Wed May 4th call (need schedule input!) Hi, Wednesday's call is intended for discussion of schedule information for the roadmap document. Hiro sent a series of requests to working group and design team leads last week, asking for input for their sections based on the template we reviewed last week. For those who received Hiro's mail: If you're able to provide input for this week's meeting, please try to send it to me in time for me to merge it into the Roadmap doc, so that we can review a single document. If you can't do that, we can still review your input as a separate document, and I can merge it later, but please try to get it to me before the meeting. Thanks! Below is the proposed agenda for the meeting. - Jem The following is a proposed agenda for OGSA-WG telecon on Wednesday May 4th 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: 0504 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 Agenda bashing 2) OGSA roadmap document review (60 min) Jem will upload a new version of the document with schedule info before the call (if schedule info has been provided). Tracker for the roadmap: https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&at id=789 3) Wrap up (10 min) AOB See telecon schedule until May F2F: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule ---- Jem Treadwell

1 0

RE: [ogsa-wg] RE: Proposed agenda for Wed May 4th call (need schedule input!)
by Treadwell, Jem 04 May '05

04 May '05

Hi, I received some input, so we'll go ahead with the call. I'll have a glance session running at ogsa.glance.net, with a session-id of 0504. - Jem -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Treadwell, Jem Sent: Wednesday, May 04, 2005 4:16 PM To: ogsa-wg Subject: [ogsa-wg] RE: Proposed agenda for Wed May 4th call (need schedule input!) Hi, I haven't received any schedule input for the roadmap. If anybody is planning to have any to discuss at today's meeting can you please let me know, even if you don't have it ready yet? If there's no roadmap input to discuss, and if nobody has any other business for the agenda, we won't have a meeting tonight. If that's the case I'll send a follow-up message by 5:45 pm US Eastern time. Thanks, - Jem -----Original Message----- From: Treadwell, Jem Sent: Tuesday, May 03, 2005 11:58 AM To: 'ogsa-wg' Subject: Proposed agenda for Wed May 4th call (need schedule input!) Hi, Wednesday's call is intended for discussion of schedule information for the roadmap document. Hiro sent a series of requests to working group and design team leads last week, asking for input for their sections based on the template we reviewed last week. For those who received Hiro's mail: If you're able to provide input for this week's meeting, please try to send it to me in time for me to merge it into the Roadmap doc, so that we can review a single document. If you can't do that, we can still review your input as a separate document, and I can merge it later, but please try to get it to me before the meeting. Thanks! Below is the proposed agenda for the meeting. - Jem The following is a proposed agenda for OGSA-WG telecon on Wednesday May 4th 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: 0504 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 Agenda bashing 2) OGSA roadmap document review (60 min) Jem will upload a new version of the document with schedule info before the call (if schedule info has been provided). Tracker for the roadmap: https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&at id=789 3) Wrap up (10 min) AOB See telecon schedule until May F2F: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule ---- Jem Treadwell

2 1

RE: Proposed agenda for Wed May 4th call (need schedule input!)
by Treadwell, Jem 04 May '05

04 May '05

Hi, I haven't received any schedule input for the roadmap. If anybody is planning to have any to discuss at today's meeting can you please let me know, even if you don't have it ready yet? If there's no roadmap input to discuss, and if nobody has any other business for the agenda, we won't have a meeting tonight. If that's the case I'll send a follow-up message by 5:45 pm US Eastern time. Thanks, - Jem -----Original Message----- From: Treadwell, Jem Sent: Tuesday, May 03, 2005 11:58 AM To: 'ogsa-wg' Subject: Proposed agenda for Wed May 4th call (need schedule input!) Hi, Wednesday's call is intended for discussion of schedule information for the roadmap document. Hiro sent a series of requests to working group and design team leads last week, asking for input for their sections based on the template we reviewed last week. For those who received Hiro's mail: If you're able to provide input for this week's meeting, please try to send it to me in time for me to merge it into the Roadmap doc, so that we can review a single document. If you can't do that, we can still review your input as a separate document, and I can merge it later, but please try to get it to me before the meeting. Thanks! Below is the proposed agenda for the meeting. - Jem The following is a proposed agenda for OGSA-WG telecon on Wednesday May 4th 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: 0504 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 Agenda bashing 2) OGSA roadmap document review (60 min) Jem will upload a new version of the document with schedule info before the call (if schedule info has been provided). Tracker for the roadmap: https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&at id=789 3) Wrap up (10 min) AOB See telecon schedule until May F2F: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule ---- Jem Treadwell

1 0

OGSA BP call on today?
by Srinivasan, Latha 04 May '05

04 May '05

Is the OGSA BP call on today from 1-3pm ET? -Latha

1 0

Proposed agenda for Wed May 4th call (need schedule input!)
by Treadwell, Jem 03 May '05

03 May '05

Hi, Wednesday's call is intended for discussion of schedule information for the roadmap document. Hiro sent a series of requests to working group and design team leads last week, asking for input for their sections based on the template we reviewed last week. For those who received Hiro's mail: If you're able to provide input for this week's meeting, please try to send it to me in time for me to merge it into the Roadmap doc, so that we can review a single document. If you can't do that, we can still review your input as a separate document, and I can merge it later, but please try to get it to me before the meeting. Thanks! Below is the proposed agenda for the meeting. - Jem The following is a proposed agenda for OGSA-WG telecon on Wednesday May 4th 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: 0504 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 Agenda bashing 2) OGSA roadmap document review (60 min) Jem will upload a new version of the document with schedule info before the call (if schedule info has been provided). Tracker for the roadmap: https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&at id=789 3) Wrap up (10 min) AOB See telecon schedule until May F2F: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule ---- Jem Treadwell

1 0

Fw: [ogsa-wg] Monday May 2 Teleconference: BP and Profile Template
by Tom Maguire 02 May '05

02 May '05

Folks, just as well. not sure we had enough of the stakeholders to close down issues other then what we have tonight. Tom 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 ----- Forwarded by Tom Maguire/Hawthorne/IBM on 05/02/2005 06:41 PM ----- David Snelling <David.Snelling@U K.Fujitsu.com> To Sent by: ogsa-wg <ogsa-wg(a)gridforum.org> owner-ogsa-wg@ggf cc .org Subject [ogsa-wg] Monday May 2 04/29/2005 10:56 Teleconference: BP and Profile AM Template Folks, We have a teleconference on Monday afternoon/night. We should try to close all issues on the Basic Profile and the Profile Template. Time: 18:00-20:00 Eastern Free: +1-866-639-4741 Toll: +1-574-935-6703 PIN: 8980700 Agenda: 1) Early discussion Note taker assignment Roll call Agenda bashing 2) Profile Template discussion 3) Basic Profile discussion 4) Wrap up AOB Tracker numbers: Tracker 1322: Tracker 1323: Tracker 1363: Tracker 1367: Tracker 1365: Tracker 1257: -- 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

Agenda for Thursday May 5th BES telecon
by Andrew Grimshaw 02 May '05

02 May '05

All, We had a very good telecom last Thursday. Mark Morgan will be sending out the minutes early next week. I am attaching the powerpoint that we worked on. We decided to discuss "agreement" on the next telecom. Karl Czajkowski is going to send us a link to the most recent document that we should read. I also recommend reading the most recent JSDL documents. Agenda: Agenda bashing Approve minutes Presentation of WS-Agreement - Karl can you do this? Discussion

2 2

Teleconference minutes - 27 April 2005
by Andreas Savva 02 May '05

02 May '05

Minutes attached. Gridforge: https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050427/en/1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 27 April 2005 =================================== * Participants Peter Ziu (Northrop Grumman) Jem Treadwell (HP) Andreas Savva (Fujitsu) Steven Newhouse (OMII) Mark Morgan (UVa) Tom Maguire (IBM) Fred Maciel (Hitachi) Hiro Kishimoto (Fujitsu) Mike Behrens (R2AD, LLC) Minutes: Andreas Savva * April 25 Minutes approved with no changes * Roadmap document review Revision by Jem posted on gridforge. Sec.2, p4-5: "OGSA Compliance Tests" : Does this mean a compliance suite, or simply a description of what tests should be performed. "Practical criteria" seems to change the initial meaning (suite) to something else. Ultimately it will need to reflect GGF's position on the development of compliance test suites. Action: Jem to raise as issue in the tracker. (Done) Sec. 2.2, p5: First sentence. Hiro wants to add a sub-subsection to describe other normative documents that are part of OGSA. This sentence seems a bit strange. p6: "... initial set of three such profiles..." Remove list and revise along the lines of "define some profiles" and give the ones listed there as examples. They may be augmented later. - 'Extension' is probably a better term than 'add-on' or 'higher level' profile to describe profiles 'using' other profiles. - The OGSA profile definition reference comes at the end and seems a bit late. This section is a summary of that document and this fact does not come out clearly enough. For example 'adoption' and 'status' are mentioned but it is not clear that they are defined in more detail in the referenced document. Action: Consider changing the place of the citation and making clearer what information is in the referenced document. (Jem) Sec. 2.4: Agreed that this is a placeholder and will not try to revise further at this time. Hiro and Dave are working on a document within the GFSG. This section will be updated once the GFSG document is completed. Action: Jem to accept visible changes for now. ** Review of template for 'development schedule' sections - Change 'interface' to 'document' since not all specs define interfaces. For example, JSDL defines a document type. - Agreed not to add non-GGF OGSA related spec schedules here. - Proposal to change the name of the "Basic Profile" to something else. - This is not a roadmap document issue. It should be raised against the BP tracker. Action: Steven to submit the title change as an issue on the BP tracker. (Done) - The target is for each summary to be one page or less. - Basic profile referenced specs: The status is the **expected status** of those specification when the BP is likely to go into public comment. The status of the referenced specs will have to be fixed later on, when the roadmap document comes closer to submission. Also the roadmap document itself will have to be updated periodically. Action: Jem to add a statement that OGSA-WG will update the roadmap document periodically since it contains information that may change over time. - Candidates for provinding information for each section: - Data Architecture: Dave B, Allen L. - ByteIO: Mark M - BES: Andrew/Darren Pulsipher/Steven N - WS-Agreement: Karl C or Chris S - JSDL: Andreas - RNS: Andrew - ACS: Should ACS be included in this list or not? It is related to the EMS architecture but it is not used by any profile at the moment. If ACS is added then maybe related efforts such as CDDLM or other EMS activities should also be added. - Need to make criteria for inclusion in the roadmap document clearer. Revisit this issue. - Basic Profile: Tom M - Naming Profile: Andrew - Data Profile: Dave B - Basic EM profile: Hiro - Security Profile: Frank S - But it is not clear that a separate security profile is being planned. Hiro to confirm. Action: Candidates need to be confirmed. Hiro to follow up. Action: Jem will revise and upload the next version of the roadmap document. He will also merge in any new information provided using the template draft. * Next week Japan is on vacation next week (Golden Week). Hiro and Andreas will not be attending the calls. - Monday: Template profile definition review (Tom to chair the meeting) - Wednesday: Roadmap document review (Jem will chair the meeting)

1 0

Resource Management design team teleconference
by Fred Maciel 02 May '05

02 May '05

Hi again, The first teleconference of the Resource Management design team will be next Tuesday, May 3rd, from 11AM to noon PDT. My apologies to those in Japan, this was one of the few slots available (I'll sync with you in the OGSA teleconferences). The proposed agenda is: (1) CIM-Glue-JSDL comparison, mainly: - decide the format of the comparison - decide a few milestones (London OGSA F2F and GGF14) - divide the work (2) Discuss ways to lower the bar for people to start using WBEM and related software on their projects. (Is there anyone knowledgeable in the DMTF academic alliance partnerships? Any experiences document?). (3) Time allowing, discuss the state of GGF-DMTF liaisons, incuding the OGSA-related work. Dial-in: Toll Free: (888) 422-7120 Int'l Access: (608) 250-0194 Participant code: 693305 See you there, Fred Maciel.

2 1

RE: [ogsa-wg] [Fwd: Hotel links]
by Dave Berry 02 May '05

02 May '05

Folks, Which hotel are we choosing: the Rydges or the Concord? Dave. -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Andreas Savva Sent: 27 April 2005 23:11 To: 'ogsa-wg' Subject: [ogsa-wg] [Fwd: Hotel links] Here's Andrew's email [F2F Hotel information] I was asked to forward. Andreas

2 1

Revised OGSA related telecon schedules
by Hiro Kishimoto 01 May '05

01 May '05

Hi all, Attached is updated OGSA related telecon schedules. I've add "resource management" call on Tuesday and updated OGSA general call, OGSA-ByteIO, and OGSA-D. Thanks Neil, Dave Berry, and Fred for arranging your calls. ---- Hiro Kishimoto

1 0

Data: telcon agenda for May 4 - WS-DAI & ByteIO
by Dave Berry 29 Apr '05

29 Apr '05

Dear all, Here are the planned topics for upcoming telcons: May 4 - Data access (WS-DAI and ByteIO) May 11 - Data storage May 18 - Document review & plan for F2F This week's telcon will be at the usual time of Wednesday (4th May), at 8:00am PDT / 11:00am EDT / 4:00pm BST / 5:00pm CEST. PIN for all calls: 632 065 UK Dial In: 0845 245 0224 US Dial In: 1866 838 0046 International Dial In: +44 1452 542309 Here is a provisional agenda for this week. 1) Early discussion (5 min) Note taker assignment Roll call Minutes approval (attached) Agenda bashing 2) Action report (5 min) - Fred to send notes on how to use Majordomo to Allen and Dave. - Dave to try to arrange data transfer discussion. - Allen to write up naming use cases for passing to OGSA WG (after review in our WG). - Ann and Allen to clean up the draft and mail it around. 3) WG status (5 min) 4) F2F planning (5 min) 5) Technical content (35 min) - WS-DAI - ByteIO 6) Wrap up (5 min) AOB DONM Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

1 0

Monday May 2 Teleconference: BP and Profile Template
by David Snelling 29 Apr '05

29 Apr '05

Folks, We have a teleconference on Monday afternoon/night. We should try to close all issues on the Basic Profile and the Profile Template. Time: 18:00-20:00 Eastern Free: +1-866-639-4741 Toll: +1-574-935-6703 PIN: 8980700 Agenda: 1) Early discussion Note taker assignment Roll call Agenda bashing 2) Profile Template discussion 3) Basic Profile discussion 4) Wrap up AOB Tracker numbers: Tracker 1322: Tracker 1323: Tracker 1363: Tracker 1367: Tracker 1365: Tracker 1257: -- 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

Telecon Minutes for OGSA BES (21 April 2005 and 28 April 2005)
by Hiro Kishimoto 29 Apr '05

29 Apr '05

Mark's email bounced. ---- Hiro Kishimoto Subject: Telecon Minutes for OGSA BES (21 April 2005 and 28 April 2005) Date: Thu, 28 Apr 2005 13:10:08 -0400 Here are the two telecon minutes documents from the first to OGSA BES teleconferences. Andreas, can you point Me at the correct place on gridforge to be putting these? -Mark -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.mark-morgan.net mark(a)mark-morgan.net ------=_NextPart_000_0012_01C54BF3.9A259EA0 Content-Type: text/plain; name="Minutes - 28 April 05 BES.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Minutes - 28 April 05 BES.txt" Minutes for BES Telecon -- 28 April 2005 Attendees --------- Andrew Grimshaw Mark Morgan (Minutes) Steven Newhouse Darren Pulsipher Fred Maciel Tom McGuire Andreas Savvas Karl Czajkowski * Many presentations at GGF had something at the bottom end that started = up services - create - instantiate - submit - etc. - Took some kind of JSDL or something and returned some kind of handle -- EPR -- etc. - Since that seemed like fairly consistent pattern, can we agree that = that is the pattern that we are looking for for factory like operations? -- Yes * Last call we agreed that we were going to work with both legacy jobs = and service instantiation. Is there a consensus that this is the basic = approach that we want to be taking here? - No dissagreement. * Karl brings up WS-Agreement. - Concern about WS-Agreement is that going with it could stall the = pipe. - We are under pressure to have something tangiable come out of this process in a fairly short period of time. -- Waiting on WS-Agreement could hurt that. - On the other hand, it seems like if we could come up with a basic = thing here, we could sometime in the future refactor in terms of = WS-Agreement. - Is there agreement that we should wait on WS-Agreement? -- Would like to know more about the timing for WS-Agreement? -- Current plan in the group is to try and have the next rev for GGF = in Chicago for another comment period. Hoping that this will be a "pat on the back" comment period so the hope is that it might be ready in a soon time frame (a few months). - Is the draft in gridforge close to what is expected to be presented = in Chicago? How closely does this match what we are talking about here. -- WS-Agreement is a WSRF based approach. Current issues include technical issues so the technology isn't frozen...there will be changes, but the basic idea is pretty close. -- The factory pattern is to create an agreement. The operatoin is called createAgreement and it returns an EPR which is the agreement (in the synchronous case) or an EPR which you have to talk to to = see if the agreement was accepted (in the asynch. case). -- That pattern isn't too far from what we have here. -- The big difference is that what we are talking about here in BES is that there are other things that we have put into the container = that are more specific to container like things then to a general agreement. - Propose to the group, put on the agenda for next week, a discussoin = of how we want to deal with agreement. -- Karl to send out mail with links to which documents we should be looking at. -- Karl to confirm the projected schedule for agreement. * Current Prototype - What is the purpose of submissionIdentifier? -- This is a message identifier, like UUID. -- Question whether or not we really need this because JSDL already = has it. -- If it's already in JSDL, then we don't need this parameter. -- The objective is to eliminate duplicate requests. -- We'll take the parameter out as an input, but replace it with a comment to indicate that we need this duplication detection somewhere -- either at message/SOAP layer, or perhaps in JSDL. - Do we want to presume that something like WS-Names will be finished = in time? - Leave it for now that it will be defined elsewhere. If we get down = the pipe and WS-Names aren't there, we will have to get more concrete and = get back to it. - Punt for now on faults -- one of the things we will have to figure out later is the fault model. -- Mentioning the faults is good, but it's not time to talk about the mechanism. --- We'll have a call later with "bring your own favorite faults". * getActivityStatus: - We have a container for services that can be a hosting environment of some kind, or something else. - Will model some physical resource out there. - What other kinds of things do we want to be able to do to containers. - One is, give me the activity or status of one or more named things = that have been instantiated on this thing. -- One of the arguments we've had on this is that, on the one hand, if everything is WSRF, then I should directly talk to the named input. -- This goes for a few of the operations. -- The argument is to say that having two different functions is to have two different ways to do things. -- But, sometimes you want to talk to the container to do something to a down or unresponsive object, or you want to do bulk operations. -- If we have these get status things and the terminate one in particular -- sometimes you have to kill something that isn't responsive. - Talking about the model, or the rendering, or both? One of the = problems the OGSA WG has to address very soon is the resource model for OGSA = in general (and mangement model) vs. the individual thing for individual services and containers. A lot of the things that we are going to be doing on containers are going to look like management things. You = can't just pull it away from the service -- they are inter-twined. -- We are to have a discussion of this in London. - You also have things that even a scheduler wouldn't care about that a manager may care about like changing the policy on how to throw out jobs on an overloaded (or overcommitted) resource. -- Andrew told Hiro that he would prepare an example of the kinds of places this would show up. - Karl votes in favor of this. Some discussion to separate notion of job management from aggregate job management (kill this job, kill all jobs). -- Managers didn't like the ability to get the status of all jobs. -- In reality, you end up crippling systems to satisfy requirements. -- Security strickly speaking is out of scope, but in practice you have to think about it. -- Let's make the assumption that someone above us is going to handle security, maybe with a document where they pass in there user identification or credentials. The underlying system will handle that. You have to make assumptions that the implementation will handle this stuff as long as you believe that the user's = credentials will be passed. Leave it up to the implementers to implement or some security/policy working group. - There has to be some linkage back to the original JSDL document. The schema (format) of this document TBD. -- It needs to have the activity identifier and the activity state. -- You return multiple activity states -- you may have multiple data staging -- how do I match them up. --- You need to be able to name the states and match them up with things in the JSDL document. -- Should the BES include data staging in it? --- If you are thinking about the workflow to run a job is something that could take place outside of the BES interface. --- If there is an overall job manager, it could start a small job or service that does the staging for you. That's a separate job. --- Depending on how we decide to do BES, you could make all data staging irrelevant. ---- We need to dive into this more deeply. ---- How simple can we make BES by pulling out things like staging? ---- How simple "SHOULD" we make it? * No desire to make the calls long then 1 hour. * Final discussoin briefly is about the terminate with prejudice = function. - Is returning the right thing to do? -- We shouldn't return anything. -- Boolean isn't rich enough. -- You could get something back saying it's dead, there's nothing there, it's going down, etc.....from a practical sense, there's a bunch of terminate status as well.... -- It should either be an empty output, or some kind of fault model or something. -- We should think about whether or not this is synchronous or asynrchronous. -- Decide to make output empty (we get an empty return or ack right away). -- It's asynchronous in terms of the functionallity, not the RPC. * Successful meeting - Mark to send out notes - Andrew to clean up slides (like AbstractName -> WS-Name). * Agenda for next week is to discuss the agreement document and also to = get the minutes approved. This WG is on the agenda for the next steering group = call next week. No expectations of problems. Expectation is for approval on Tuesday. ------=_NextPart_000_0012_01C54BF3.9A259EA0 Content-Type: text/plain; name="Minutes - 21 April 2005 - BES.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Minutes - 21 April 2005 - BES.txt" OGSA BES BoF Telecon (21 April 2005) Attendees --------------- Mark Morgan (Minutes) Fred Maciel Hiro Kishimoto Andrew Grimshaw Steven Newhouse Darren Pulsipher Kabushige (NAREGI) Ravi Harei Tom McGuire Chris Smith Karl Czajkowski Dave Snelling Jem Treadwell Agenda Bashing ------------------------ * Get Charter Finalized * If we get through that, the future telecon schedule and the timeline Some things we could knock off the list of future discussions Finalize Charter ----------------------- * Two modification that have been made to this document vs. the one that was sent out before GGF13 in Korea - Scoping -- Only legacy, or service instantiation too - Do we want to define what the interface is on the things that get returned from instantiation - Stronger wording for communicating and interactinvg with the OGSA WG reguarlly * Solicit a Volunteer to maintain the GridForge Site -- no volunteers. * Andrew added sentence about OGSA-WG interaction. * Need stronger language like Data and ByteIO -- like review meeting at every milestone before the document is sent out. - Will this slow us down? - Having a review meeting is OK, but the question is do we need blessing, or is this just a presentation. * Does it hurt to have a review meeting? * Will OGSA have a veto power? - No, you can publish without, but if you want to use the ogsa name, then you have to have approval. * We linked into the charter that we are going to be working along the lines of the OGSA-WG -- why do we need a second ratification? - The thing is, the charter talks about the spirit of these two WGs, but in the final analysis the two WG could have a diametrically opposed view and it would be up to the GFSG editor to sort it out. - Because of this, we're perfectly comfortable with this. - Some have said that the current language is fine as it is as long as it is understood that the language doesn't mean veto. - The GGF rules say that the OGSA WG does NOT have veto power. - If one WG starts having veto power over another, then that has to come from somewhere. * Scope - Changed one thing in the initial scope doc....should it be just for legacy job management or for also web service intsantiation management? -- A number of people said that we shouldn't limit it. -- Can view legacy job as a special case. -- A lot of systems that have been discussed are the same whether or not the thing being launched is a legacy job. -- Decision to allow for the general case. * Goals - Having a draft recommendation document by GGF14. -- This is aggressive, but think we can do that. -- Hoping we can refer to a bunch of stuff in JSDL. - Not sure how well JSDL will cover service instantiation. -- JSDL has the concept of being able to add any type of service. -- Either it will end up being that we will have to add some extensibilities on JSDL, or we will provide feedback to the JSDL group on things we need. - Intention at UVa is to do an implementation of the spec. so that we can write an experience document for Sept. -- We need that before we can push the doc. all the way through. - The next deadline is can we have fought out all the details by Nov in order to get a public document out. - We don't want to say that the doc. in June is a proposed standard, but we do want to make it publically available. -- It will be a publically available working group draft. - What about the Experience Doc. -- Not clear from the process how we should handle this. -- Assuming we do one at UVa, we will write up our experience with that, since it's info doc, we could bring it to the WG, then they could decided whether or not to make it a WG info doc. -- OMII is aiming to also have an implementation. So supposedly we'd have the real document for the GGF editor and for review in the end of October. * Management Issues - It's boiler plate for the steering committee. - Platform is agreeing to praticipate at some level. * OGSA is very focused on interoperability issues, this is why the Base Profile is so important. Not only OGSA WG but aslo GFSG wants to see ogsa prefixed wg like this is based on the basic profile or not. What does this working group think about the Basic Profile. - Andrew frames question this way: There may in the end be several basic profiles. - What he would rather have the working group focus on is the issues such as "What are the interfaces", "What are the attributes or meta data that are relevant" as opposed to the particular mechanics that are used to manipulate them. - That said, take attributes (which could be Resource Properties) -- We can define them as attributes or meta data, but then say that the way that they would be rendered in the OGSA BP would be as resource properties. That way we don't close the door on others. It's not as strong as what you want to put in. - But, if you don't define how you access informtaion and capabilities, then you don't have a complete interface. If you leave it open, then you throw interoperability out the window. - Yes, you have to describe an access mechanism, but there is no reason you can't define multiple access mechanisms. -- At least one should be based on Basic Profile. That is fine. - Everyone can agree that we might want a resource property for a container that is called "Processor Architecture" (like JSDL). -- Clearly in a WSRF based impl, this would be a resource property that you can do a get on, but not a set. But, are we going to focus on what these properties are, but not how you get them. Can't we say, one way to get them is the WSRF way. -- What we don't want to do is to proclude other ways of doing things in other ogsa profiles that may happen in the future. - When we put together the rough working group back in GGF 5. Back then we explicitly tied ourselvces to OGSI. That was a mistake. It seems very dangerous to have a technology option in the charter. But are we referencing a technology option (WSRF), or the basic profile which could change. Couldn't this change in the future. If there was a phrase about using a profile from the OGSA working group, then that's fine. - On one of the last OGSA phone calls, we clarified that WSRF is not mandidated in the profile, but it does say that if you use stateful resources, then you use WSRF. But nothing says we have to have stateful resources. As long as the use of an OGSA profile is in here (and it's important to say "a" profile, not "the" profile). * This is in the charter now, everyone agrees with this. * There are two levels of infrastructure defined - WS-I base one - WSRF on top of that. - Clearly this is going to be a debate that will swing back and forth over time -- to a large extent, it's important for interoperability. - However, to hammer stuff out here at the beginning, it's OK. Let's define things in terms of the ideas, and then later we can have a "rendering" of the model with a specific technology. - Some are skeptical of this -- seems like at the end of the day we really need to have WSDL. -- Let's do everything in IDL right up front. Later we can do the mappings afterwords. Eventually we will need WSDL. Not much agreement on this. IDL seems useful to some people, others would prefer to go straight to XML -- Ultimately we need WSDL, but why can't we use IDL in the interim. But, is this discussion really necessary wrt the charter. * We've asked to be called ogsa-bes, then if we think we are rendering the ogsa architecture, then we should reference the ogsa documents in this. - If this is uncomfortable to some people, then we should drop the ogsa brand. - What isn't clear is whether or not the ogsa brand is open or closed to alternative profiles. - Many would rather keep the ogsa brand on the working group. - The WSRF v. WS-Transfer battle will have to be fought in the OGSA WG. - Should we say that if other profiles come up, that we would try to do our best to render all available profiles? -- Not quite everyone. -- Seems like we don't need to put this in the charter. * Seems like we can say that everyone agrees and we can send this into the steering committee. * Also seems like we will be an SRM. * Would like to hold telecons every week * The WG chairs will put together an agenda before early next week to get comments. * We'll have a telecon next Thursday. * On the OGSA WG call on next Monday, Andreas will be giving a presentation of the JSDL specification * We might also want to take a look at the SAGA groups outputs. - They have an API and they might be an endpoint consumer for what we put together. * Daren, Steven and Andrew will put togheter an agenda for next week. * Charter to go in this afternoon. * Re: F2F in may. There has been a plan to have the F2F in conjunction with the OGSA F2F on May 22nd in london at Imperial College. - We'll work something out for a telecon bridge. - We'll work something out for Karl. ------=_NextPart_000_0012_01C54BF3.9A259EA0--

1 0

ByteIO WG Mailing List and Minutes from Last Call
by Hiro Kishimoto 29 Apr '05

29 Apr '05

Neil's email bounced. ---- Hiro Kishimoto Subject: ByteIO WG Mailing List and Minutes from Last Call Date: Thu, 28 Apr 2005 15:35:53 +0100 Dear All, the ByteIO WG charter has been approved and our mailing list is now setup! To subscribe, please send a message to majordomo(a)ggf.org with just the following line in the body of the message: subscribe byteio-wg my.email(a)ddress.org (substituting your own email address) We have fortnightly telcons at 14:00 UTC - the schedule for the next telcons and the details for participating are below. Notes from our previous telcon are attached to this message, and will be posted online once our GridForge account is setup. Date of next Telcon: 3 May 05 at 14:00 UTC (09:00 CDT / 10:00 EDT / 15:00 BST / 16:00 CEST) Call details: - UK Dial In: 0845 245 0224 - US Dial In: 1-866-838-0046 - International Dial In: +44 1452 542309 - PIN Number: 369786 Agenda of future telcons: - 3 May: discuss draft template for use cases and discuss initial use cases - 17 May: continue looking at use cases, discuss bulk data transfer protocols, and requirements for F2F meeting - 26 May: OGSA Data and ByteIO F2F in London (extreme discussion of documents) - 31 May: Discussion of arrangements for GGF, discussion of prototype specification and draft documents - 14 June: Further discussion of specification and use case documents - 26-29 June: GGF14 Chicago Best regards, neil -- << NOTE ROOM CHANGE, OTHER DETAILS REMAIN CONSTANT >> Neil P Chue Hong | T: [+44] (0)131 650 5957 Project Manager, EPCC | F: [+44] (0)131 650 6555 Rm 2409, JCMB, Mayfield Rd. | E: N.ChueHong(a)epcc.ed.ac.uk Edinburgh, EH9 3JZ, UK | W: http://www.epcc.ed.ac.uk "A film is like a battleground. It's love, hate, action, violence, death - in a word, emotion." - Sam Fuller ------=_NextPart_000_00FE_01C54C07.FFAE1D10 Content-Type: text/plain; name="20050419 byteio.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="20050419 byteio.txt" Minutes from the ByteIO Telcon on 19/4/05 ----------------------------------------- Attending: Mark Morgan, UVa (MM) Neil Chue Hong, EPCC (NCH) Dave Berry, NeSC (DB) Mario Antonioletti, EPCC (MAA) Date of next Telcon: 3 May 05 at 14:00 UTC (09:00 CDT / 10:00 EDT / = 15:00 BST / 16:00 CEST)=20 Call details: - UK Dial In: 0845 245 0224 - US Dial In: 1-866-838-0046 - International Dial In: +44 1452 542309 - PIN Number: 369786 Agenda of future telcons: - 3 May: discuss draft template for use cases and discuss initial use = cases - 17 May: continue looking at use cases, discuss bulk data transfer = protocols, and requirements for F2F meeting - 26 May: OGSA Data and ByteIO F2F in London (extreme discussion of = documents) - 31 May: Discussion of arrangements for GGF, discussion of prototype = specification and draft documents - 14 June: Further discussion of specification and use case documents - 26-29 June: GGF14 Chicago Discussion of data transfer protocols ------------------------------------- MM had looked at WebDAV, does it really apply?=20 Also at PBIO, looks like an alternative to XDR. Bill Allcock recommended looking at XIO as well for background. Does ByteIO fit more at the client API level? MAA: What does PBIO stand for? - MM will pass on link MTOM will be in WSE3.0 but unclear when it will be released. Axis2 has MTOM in plans, but not yet done. NCH try to ask Microsoft Europe contact whether WSE3.0 is coming out = soon and whether DIME will still be around. Discussion of use cases ----------------------- Came up with a use case from the point of view of an NFS server = accessing a ByteIO web service. Then a more grid aware application, = which knows about ByteIO interface, so can make decisions. Have a client = which wishes a more connection oriented view of a ByteIO stream, = establishes an endpoint, which marks a particular position in a file. One of the things which pops up is a way of locking the data source. Avaki allowed the placing of an advisory lock, which is used by NFS = protocol, but doesn't seem to be heavily utilised. People worry about it = but don't often do anything about it. Simple cases don't need locking but we will probably have a lot of = people standing up at next GGF saying we need locking :-) DAIS discussion of use case has revealed a possible hole in their = specification to do with getting data into a data service (rather than = getting data out). =20 DB contacted the NEC guys, and they sent along a simple visualisation = application use case. Use Cases - write some down, come up with a template on what we want to = get from a use case, reformat our use cases into this format. what functionality will be layered on top of ByteIO [MM] Mail out a draft template for use cases for next Telcon. ------=_NextPart_000_00FE_01C54C07.FFAE1D10--

1 0

[ogsa-wg | Roadmap - 1398] Compliance Tests
by Sourceforge Tracker Monitor 28 Apr '05

28 Apr '05

A new artifact has been added: 1398 Submitted by: Jem Treadwell Submitted date: 2005-04-28 10:05:05 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=789&aid=1398&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=789&aid=1398&group_id…) Summary: Compliance Tests Project: Open Grid Services Architecture Tracker: Roadmap Artifact ID: 1398 Category: <None> Group: <None> Status: Open Priority: 3 Last Modified By: Jem Treadwell Last Modified: 2005-04-28 10:05:05 Submitted By: Jem Treadwell Submit Date: 2005-04-28 10:05:05 Assigned To: Jem Treadwell File(s): <None> Description: Version 6, section 2, list item 3 (OGSA Compliant Software) says: "We may also expect that a set of OGSA Compliance Tests will be developed that define the practical criteria that must be satisfied for a software system to be called OGSA-Compliant." We need to clarify whether this is intended to mean a software suite, or simply a description of what tests should be performed. Ultimately it will need to reflect GGF's position on development of compliance test suites. View the Roadmap : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

[ogsa-wg | Basic Profile - 1397] Better name for Basic Profile
by Sourceforge Tracker Monitor 27 Apr '05

27 Apr '05

A new artifact has been added: 1397 Submitted by: Steven Newhouse Submitted date: 2005-04-28 00:08:39 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1397&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1397&group_id…) Summary: Better name for Basic Profile Project: Open Grid Services Architecture Tracker: Basic Profile Artifact ID: 1397 Category: <None> Group: <None> Status: Open Priority: - Last Modified By: Steven Newhouse Last Modified: 2005-04-28 00:08:39 Submitted By: Steven Newhouse Submit Date: 2005-04-28 00:08:39 Assigned To: &lt;None&gt; File(s): <None> Description: The current 'OGSA Basic Profile' should be renamed, e.g. OGSA WSRF Basic Profile, to better describe what it is about and allow other basic profiles to be developed in the future. View the Basic Profile : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

[Fwd: Hotel links]
by Andreas Savva 27 Apr '05

27 Apr '05

Here's Andrew's email [F2F Hotel information] I was asked to forward. Andreas

1 0

Resource Management design team teleconference
by Fred Maciel 27 Apr '05

27 Apr '05

Hi, I want to re-start the activities of the resource management design team, and a teleconference will be a nice way to do it. We need to put everybody in sync and get the work started. The main subject of the teleconference will be the CIM-Glue-JSDL comparison, which will be useful for EM (Execution Management) as a whole, and in the short term it will be a much needed input to BES (Basic Execution Service). We need to decide the format of the comparison, get a few milestones (London F2F and GGF14), divide the work, etc. (We'll also need to think about manageability on EM, which might be the start of the profiling. But I'd start that when BES gets more concrete). Another possible subject is whether we need to think of ways to lower the bar for people to start using WBEM and related software on their projects. Say, profiles, or a GGF experimental document? Now, please cue in the Mission Impossible theme song and let's decide a time slot for the teleconference. Here are some suggestions, please e-mail me your availability. (Anybody from Japan interested in participating?). - Monday until 13:00 PDT - Tuesday 10-12 PDT - Thursday 14:00 and later, PDT Thanks in advance, Fred Maciel.

2 1

Agenda for April 28 OGSA-BES conference call
by Andrew Grimshaw 27 Apr '05

27 Apr '05

The BES teleconference is scheduled for this Thursday, April 28,(US) at 10 AM eastern. The dial in number (thanks IBM) is: Free: +1-800-664-6895 Toll: +1-719-955-1126 passcode: 285178 Screen share service will be provided. URL: http://ogsa.glance.net <http://ogsa.glance.net/> Session key: 0428 Agenda for April 28 OGSA-BES conference call Agenda bashing Basic interface discussion - try to reach agreement (no pun intended) Review of concepts presented at BOF in Korea Common theme Some_sort_of_handle submit(JSDL_doc job_description) // Note, this punts the discussion of what we need in the JSDL to a later discussion Then a set of management functions for jobs Strawman interface (based on Steven's document) Propose slight modification to extend it beyond legacy jobs, and give the handle a "type", e.g., WS-Name instantiate(JSDL_doc job_description) Set of management functions Wrap-up

1 0

NO OGSA BP CALL TODAY
by Tom Maguire 27 Apr '05

27 Apr '05

There will be an updated OGSA BP spec to grid forge today. 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