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

Consultants to Resource Selection Services-WG wanted
by Mathias Dalheimer 25 Apr '05

25 Apr '05

Hi! I am currently working on the charter for the OGSA-RSS group. This group will deal with the Resource Selection Services as specified by the OGSA-WG. I am looking for people from OGSA that are interested in the Resource Selection Services. Since OGSA and OGSA-RSS are closely related, I would appreciate if someone can commit himself to act as a consultant. We've set up a wiki for our charter discussion: http://h63759.serverkompetenz.net:8668//space/Documents/charter I will also participate in the May F2F meeting in London on Sunday and Monday. In case of any questions, please send me an email. Regards, Mathias -- ______________________________________________________________________ Dipl.-Wirtsch. Ing. (Inform.) Mathias Dalheimer Fraunhofer Institut fuer Techno- und Wirtschaftsmathematik (ITWM) Europaallee 10 67657 Kaiserslautern, Germany Phone +49(0)631/303-1827 | mailto:dalheimer@itwm.fraunhofer.de Fax +49(0)631/303-1877 | ______________________________________________________________________

1 0

SAGA use cases and strawman API
by Christopher Smith 22 Apr '05

22 Apr '05

Hey all, In case you missed these announcements. -- Chris

1 0

Proposed agenda for April 25th call
by Hiro Kishimoto 22 Apr '05

22 Apr '05

Hi all, The following is a proposed agenda for OGSA-WG telecon on April 25th 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: 0425 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 20th) https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050420 May F2F meeting update (if any) Agenda bashing 2) OGSA profile definition review (60 min) The latest draft (v1.5) https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-profil… plate/en/4 3) JSDL overview presentation (30 min) The latest JSDL spec: https://forge.gridforum.org/projects/jsdl-wg/document/draft-ggf-jsdl-spec/e… JSDL Introduction presentation: https://forge.gridforum.org/projects/jsdl-wg/document/JSDL-Introduction/en/ 4) Wrap up (10 min) AOB April 27 (noon-2pm CDT) Basic Profile April 27 (5-7pm CDT) Roadmap discussion First week of the May is Japanese holidays (Golden Week). See telecon schedule until May F2F: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule I've attached update schedule as of Today. ---- Hiro Kishimoto

1 0

Reminder: OGSA-BES first teleconference
by Andrew Grimshaw 21 Apr '05

21 Apr '05

All, The first BES teleconference is scheduled for this Thursday, April 21,(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: 0421 The agenda is: Agenda bashing Charter finalization: Scope issues: 1) Legacy only or include "service instantiation" 2) Definition of "job" interface - or leave it to another WG Approval of modification "to communicate and interact regularly with the OGSA-WG". Discussion of future telecon's, e.g., End first agenda Because of the importance of JSDL to our discussions I have included links to the relevant information. JSDL Specification draft information. https://forge.gridforum.org/projects/jsdl-wg/document/draft-ggf-jsdl-spec/en / Also here's the link to the JSDL Introduction presentation: https://forge.gridforum.org/projects/jsdl-wg/document/JSDL-Introduction/en/ Issues for discussion in the following telecon's 1) Agreement or not agreement 2) WSRF or WSRF-neutral 3) Metadata/attributes of containers 4) Interface of the service container 5) Interactions with JSDL - terms and semantics of terms 6) I/O specifications and JSDL terms 7) Service containers as manageable entities Please send us your thoughts on other topics. Andrew Grimshaw Darren Pulsipher Steven Newhouse _____ From: Andrew Grimshaw [mailto:grimshaw@cs.virginia.edu] Sent: Tuesday, April 19, 2005 4:09 PM To: 'ogsa-wg(a)ggf.org'; 'OGSA-BES-bof(a)ggf.org' Subject: OGSA-BES first teleconference All, The first BES teleconference is scheduled for this Thursday, April 21,(US) at 10 AM eastern. The dial in number (thanks IBM) is: Free: +1-800-664-6895 Toll: +1-719-955-1126 passcode: 285178 The agenda is: Agenda bashing Charter finalization: Scope issues: 3) Legacy only or include "service instantiation" 4) Definition of "job" interface - or leave it to another WG Discussion of future telecon's, e.g., End first agenda Issues for discussion in the following telecon's 8) Agreement or not agreement 9) WSRF or WSRF-neutral 10) Metadata/attributes of containers 11) Interface of the service container 12) Interactions with JSDL - terms and semantics of terms 13) I/O specifications and JSDL terms 14) Service containers as manageable entities Please send us your thoughts on other topics. Andrew Grimshaw Darren Pulsipher Steven Newhouse

3 2

JSDL spec link
by Andreas Savva 21 Apr '05

21 Apr '05

During today's call I was asked to send out the url to the current JSDL spec. This will (always) get you the latest snapshot: https://forge.gridforum.org/projects/jsdl-wg/document/draft-ggf-jsdl-spec/e… Also here's the link to the JSDL Introduction presentation that we'll be using for next Monday's call: https://forge.gridforum.org/projects/jsdl-wg/document/JSDL-Introduction/en/ -- Andreas Savva Fujitsu Laboratories Ltd

1 0

Teleconference minutes - 20 April 2005
by Andreas Savva 21 Apr '05

21 Apr '05

Minutes attached. As gridforge is not responding these are not uploaded yet. -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 20 April 2005 =================================== * Participants Pete Ziu (Northrop Grumman) Jay Unger (IBM) Jem Treadwell (HP) Andreas Savva (Fujitsu) Mark Morgan (UVa) Tom Maguire (IBM) Hiro Kishimoto (Fujitsu) Andrew Grimshaw (UVa) Mike Behrens (R2AD, LLC) Minutes: Andreas Savva * Minutes of April 18 approved with no changes * May F2F update - Waiting for room reservation at IC - Many people have already said that they will be attending - More than 13 for the main meeting (Mon & Tue) - More than 11 for the Data (Thu) - Any hotel suggestions? The url sent last week has a lot of information (too many choices) - Andrew stayed at the "John Howard Hotel" last time. It was nice but there was no network connectivity. - Arranging to stay in the same hotel sounds like a good idea but there was no proposal on how to go about arranging it. - Arriving at Heathrow vs Gatwick: Probably no big difference. Heathrow might be more convenient (Heathrow Express). * Basic Profile update - Calls have been very productive; very good progress. - Many but not all artifacts fixed/closed. - Trying to close the rest this week or perhaps early next week. - Planning one more teleconf next week, same day, at the 1-3pm timeslot - There are 11 artifacts resolved: revisions not completed yet. - There are some 'Pending' state issues that need discussion. Have to get specific people on the call to make sure a proper discussion is done. - Remaining are 'fixed'; need people to check them and close them. - How to check 'fixed' better? - Ask people who will review doc to check? - From the BP team's perspective, 'fixed' may be good enough. The OGSA-WG will have to check the document anyway before going through with the submission. It might be a good place to do the 'Closed' transition then. Action: Tom, to help reviewers confirm changes, will cross-link each issue to the specific requirement statement using the 'Category' field. - Overall the document is in good state for GGF14 submission. Action: Tom to send a copy of the BP draft to Marty Humphrey and ask him to review it. * BES BoF update - Scheduled the first call tomorrow morning. Mail has been sent to both the BES BoF list and OGSA-WG list. - There is a revised agenda based on received feedback - Charter bashing is main topic (Is a Naming call being planned? Not yet. Andrew is in the process of contacting the people he has in mind for co-chairs. There is no GFSG tracker artifact for this proposed WG but GGF (Steve C) is aware of it.) * Roadmap document review - Hiro has submitted the issues from the last review (19 in total) Action: Andreas to set up Roadmap tracker in the same way as the BP tracker (same values for status) >(Done) - Jem volunteered to review the document afterwards and verify that the actions are done. - Reviewed by tracker item - "4.3 EM profile" comment: Agree with comment on the section title. Current contents are consistent. - For each section describing a Profile we should include a list of what the "Profile Template" document requires of each profile. The list will offer an indication on what the status of each profile is likely to be. - Agreed to add such a sub-section to each profile section in the Roadmap. - See "Appendix A" of the Profile Template for an example. - Does it address Dave's comment 1374? Probably but need to check. Action: Jay to make a better representation of the table in Appendix A of the Profile Template document. Action: Tom to update the Profile Template with the new version of the table. Action: Hiro to include a sub-section with such a table for each profile in the Roadmap document. - Section 4.3: Statement starting "If appropriate implementation ..." does not add anything. The real issue is the need for standards on resource modelling and resource access. And how resources are modelled in OGSA. This requirement should be stated to clarify why WSDM and WS-CIM are mentioned as possible candidates here. - (The above point triggered a long BES-related side-discussion and how things should tie together. WSRF vs other mechanisms, JSDL, does BES need to care about the resource modelling and how much does, etc. Andrew will do a short write-up to clarify the issues for this section and for BES and send it out for comment.) Action: Andreas will send out the URL to the latest JSDL specification and to a JSDL Introduction presentation. Action: Hiro will schedule the JSDL introduction presentation for next Monday's call (to start after the first hour mark). - Title revision: moved 'version 1.0' for clarity. - Section 1: forward reference to 'profiles' fixed. - Mark Linesch's comment on section 2.0: Decided to bring back old text and add the new text as extra explanation. - Footnote: deleted as obsolete. - Title of section 2: revised. - Conformance testing or tools: Not clear if GGF should be doing this. Something to discuss in the future perhaps; leave out for now. - "OGSA branding" controlled by GFSG: This section will be updated with the GFSG statement when it becomes available. Hiro has sent a draft of this section as a separate document to the GFSG. GGF is planning to obtain a TM and Service mark for OGSA. - Branding at different levels: WG and Document names - Compilant software and who can claim OGSA implementations - Decided to leave the text as a placeholder for now (might need some revision to change the tone) - Adjourned; the review to continue next week. * Next week calls - Monday: Profile template - Wednesday: Roadmap document

1 0

OGSA-WG May F2F meeting inquiry
by Hiro Kishimoto 21 Apr '05

21 Apr '05

Hi all, We've agreed to have May OGSA-WG F2F as follows; Date: May 23 (Mon) and 24 (Tue) for general meeting May 22 (Sun) for optional BES-WG meeting May 26 (Thu) for optional OGSA-data WG and ByteIO-WG meeting Venue: Imperial College London Please let me know your availability once again through the follow URL: http://www.zoomerang.com/members/survey-management.zgi?ID=L22BTBVPACJ4# or http://tinyurl.com/9y5po Thanks in advance. ---- Hiro Kishimoto

1 3

[ogsa-wg | Basic Profile - 1392] Referenced spec status and adoption table
by Sourceforge Tracker Monitor 20 Apr '05

20 Apr '05

A new artifact has been added: 1392 Submitted by: Tom Maguire Submitted date: 2005-04-20 16:04:03 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1392&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1392&group_id…) Summary: Referenced spec status and adoption table Project: Open Grid Services Architecture Tracker: Basic Profile Artifact ID: 1392 Category: <None> Group: <None> Status: Open Priority: 3 Last Modified By: Tom Maguire Last Modified: 2005-04-20 16:04:03 Submitted By: Tom Maguire Submit Date: 2005-04-20 16:04:03 Assigned To: Tom Maguire File(s): <None> Description: as per profile template. add table to appendix. 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

Minutes of OGSA BP telecon -- April 20, 2005
by Srinivasan, Latha 20 Apr '05

20 Apr '05

Hi, I've uploaded the minutes of the OGSA BP call held today, to GridForge. -Latha

1 0

[AI:1368][AI:1369] additional descriptions for the keyinfo exchange
by Takuya Mori 20 Apr '05

20 Apr '05

Dear all, The following is my draft for the additional descriptions for the keyinfo exchange. This is for the action item 1368 and 1369 of the basic profile tracker. Regard, Takuya ---- 8.1.6 Message Level Security Section 8.1.5 defines the usage of XML Encryption as part of the SOAP message security. This profile specifies how the key information for the XML Enryption is exchanged. R0813 When using Message Level Security, the ENDPOINTREFERENCE SHOULD include xxx:KeyInfo element as defined in Appendix A. R0814 When using XML Encryption as part of Message Level Security, the RECEIVER SHOULD provide the key info for encrypting incoming messages to the SENDER prior to the message sending by the SENDER. (More specifically, - the instance should provide the encryption key as part of its endpoint reference resolution and - the consumer should provide the encryption key as part of the endpoint reference in the request message.) R0814 When using XML Encryption as part of Message Level Security, the SENDER SHOULD use the key specified by xxx:KeyInfo element in the endpoint reference of the receiver.

1 0