- ogsa-wg - lists.ogf.org

[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