June 2006 - ogsa-wg - lists.ogf.org

Telecon schedule on the wiki
by Hiro Kishimoto 19 Jun '06

19 Jun '06

Hi all, OGSA weekly telecon schedule up until July F2F meeting is now on the wiki page. https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Telec… If you have any comments or questions, please let me know. Thanks, -- Hiro Kishimoto

1 0

No call on June 19th
by Hiro Kishimoto 18 Jun '06

18 Jun '06

Hi all, Since June 19th does not work for many folks, "Info Model discussion" should be moved to Thursday June 22. Thus we have no call on June 19th and have full agenda on 22nd. Minutes from June 15: > - Because it is not clear who can attend on Monday the consensus > was to move the Info Model discussion from Monday to another > day, e.g., Thursday. > > ACTION: Hiro to look into re-scheduling the Info Model rendering > discussion to another day (Thursday?) <*NEXT CALL*> June 22 (Thu): Information model (Ellen and Fred) EMS scenarios (Steven and Andreas) Roadmap 1.1 (Hiro, ChrisJ, and Jem) Security & BSP Public Comments review (Frank and Takuya) June 26 (Mon): Architecture & Glossary 1.5 (Andreas and Jem) CDDLM & EMS (Jun and Hiro) June 29 (Thu): Security & BSP Public Comments review (Frank and Takuya) July 3 (Mon): Independence day (no call) July 6 (Thu): EMS scenarios (Steven and Andreas) Thanks, -- Hiro Kishimoto

1 0

Teleconference minutes - 15 June 2006
by Andreas Savva 16 Jun '06

16 Jun '06

Attached. https://forge.gridforum.org/sf/go/doc13618?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 15 June 2006 ================================== * Participants Hiro Kishimoto (Fujitsu) Andreas Savva (Fujitsu) Dave Snelling (Fujitsu) Jem Treadwell (HP) Jay Unger (IBM) Apologies: Tom Maguire, Michael Behrens, Frank Siebenlist Minutes: Andreas Savva * Summary of Actions ACTION: Hiro to look into re-scheduling the Info Model rendering discussion to another day (Thursday?) ACTION: Andreas will categorize OGSA 1.5 issues and send the list to Dave Snelling. ACTION: Andreas and Hiro to talk offline about how to start sending ical invitations. * Minutes June 12 approval postponed (no quorum) * Security discussion postponed * Actions review - Hiro will upload updated F2F agenda (mainly updates to the attendees list) - Done - Hiro to talk with Chris Smith and clarify meaning of pre-script - Sent email, waiting. - Hiro to send Chris J the names of the people that provided Roadmap sections in the past. - Done - Jay will contact Platform (Chris Smith) and Condor (Miron Livny) to get feedback on pros / cons of the two rendering approaches (postpone until June 19); and - Darren/Andreas will take the Modeling position paper and discuss it within the JSDL-WG as well (postpone until June 19) - Jay has talked with Miron. There is no written material ready yet. - Andreas has raised the issue on the JSDL call. Overall it is not clear to people if this rendering choice boils down to anything more than a style choice. - People interested in this topic were asked to come to the OGSA call. - Because it is not clear who can attend on Monday the consensus was to move the Info Model discussion from Monday to another day, e.g., Thursday. ACTION: Hiro to look into re-scheduling the Info Model rendering discussion to another day (Thursday?) * OGSA 1.5 Review ** OGSA 1.5: Architecture review - Andreas has uploaded Geoffrey Fox's presenation. He is reviewing it and will identify which issues relate to the document (there is at least one) and which do not. Items that do not relate to the document will be answered separately, perhaps as part of a Q&A on the WG's wiki. - Jay is also willing to provide answers to some of the issues. ACTION: Andreas will categorize OGSA 1.5 issues and send the list to Dave Snelling. ** OGSA 1.5: Glossary review - Reviewed Jem's proposed updates. (Details on Jem's updated draft.) - Agreed that the definition for 'provisioning/deployment' should be left for later; depending on whether there is sufficient consensus to change it. In any case the usage in the Arch document has not changed. ** Next steps - Agreed to do a final text review 2 weeks from now. It is ok to do the reviews of the two documents separately if necessary. * Other business: OGSA Calendar - Andreas has set up and been updating an online google calendar. It has been visible to a small number of people. The plan is to make it publicly available so that people can refer to an up to date view of the teleconference and meeting schedule. - Jay proposed starting to send ical invitations to the list. Since the calendar account is on the list the online calendar view will be automatically updated---no need to manually enter events. - For example, Hiro would send an ical invitation instead of (or in addition to) the normal agenda. - The other advantage is that Hiro could get information on who intends to attend. This might be useful for F2F planning, e.g., identify who plans to join which session by phone. - Agreed to schedule a short discussion (update) again on the Monday teleconference ACTION: Andreas and Hiro to talk offline about how to start sending ical invitations.

1 0

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

15 Jun '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 15th Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: 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 Telecon minutes approval (June 12th) https://forge.gridforum.org/sf/go/doc13593?nav=1 July F2F meeting update (if any) Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA authorization call-out proposal review (Frank 20 min) > - Frank is now consulting with people in GGF (David Chadwick, Von > Welch) on whether his approach can be defined within the AuthZ > group. If there is no agreement then he will accept the XACML > group's decision. > > - Review status again on the June 15 teleconference. > 3) Basic Security Profile public comment review (Takuya 20 min) Public comment periods will end June 20th. Takuya will lead the evaluation and possible response to already posted comments: https://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf-editor… https://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf-editor… 4) Architecture & Glossary 1.5 comment review (Andreas and Jem 40 min) > - Discussed what to do if no more comments are received. Agreed that > since this is a minor revision a second round of public comment is > not necessary. The group will make whatever minor changes are > needed and submit the document to the GGF Editor. > > - The glossary has more comments but it expected that if no other > comments are received the documents can be revised and > re-submitted in June. 5) Wrap up (10 min) AOB <*NEXT CALL*> June 19 (Mon): Information model (Ellen and Fred) June 22 (Thu): EMS scenarios (Steven and Andreas) Roadmap 1.1 (Hiro, ChrisJ, and Jem) June 26 (Mon): Security & BSP Public Comments review (Frank and Takuya) CDDLM & EMS (Jun and Hiro) June 29 (Thu): Architecture & Glossary 1.5 (Andreas and Jem) July 3 (Mon): Independence day (no call) July 6 (Thu): EMS scenarios (Steven and Andreas) <*ACTION ITEMS*> > From June 12 call - Hiro will upload updated F2F agenda (mainly updates to the attendees list) - Hiro to talk with Chris Smith and clarify meaning of pre-script - Jun will correct the CDL XML examples written by Hiro. - Hiro to send Chris J the names of the people that provided Roadmap sections in the past. > From June 8 call - EMS team (Steven, Andreas, Donal) to review data staging scenario (section 5 of https://forge.gridforum.org/sf/go/doc13591?nav=1 ) (postpone until June 22) - Add sequence diagrams to the scenarios: (postpone until June 22) - Andreas will do the "Install application" scenario (3.1) - Mike will do the "Install application using ACS" scenario (3.3) - Other volunteers welcome. (Andreas will ask Donal for the EPS scenario) - Andreas will merge draft scenarios and sequence diagrams to the "EMS Architecture Scenarios" document (postpone until June 22) > From May 22 call - Jay will contact Platform (Chris Smith) and Condor (Miron Livny) to get feedback on pros / cons of the two rendering approaches (postpone until June 19) - Darren/Andreas will take the Modeling position paper and discuss it within the JSDL-WG as well (postpone until June 19) > From April 5 F2F meeting - Marvin to send e-mail that explains concerns on compliance suite by GGF & EGA. Deferred - Frank to write up and send to the list a one page summary of the authorization call-out proposal. (April 24 call, postpone until June 14) - Jay check and find out relatively small funding to Globus to develop document on their security work (April 6 F2F) - Hiro to schedule a discussion in the OGSA F2F after the converged specs drafts are released to discuss which sets of specs to use within OGSA. (April 4 F2F) -- Hiro Kishimoto

2 1

Regrets
by Maguire_Tom＠emc.com 15 Jun '06

15 Jun '06

Sorry, unexpected eval that I have been pulled into. Tom +1 (845) 729-4806 Blackberry Connect for Palm

1 0

Interim July F2F meeting agenda
by Hiro Kishimoto 15 Jun '06

15 Jun '06

Hi all, The latest agenda for Interim July F2F meeting is now on GridForge. https://forge.gridforum.org/sf/go/doc13607?nav=1 Thanks, -- Hiro Kishimoto

1 0

Glossary: Provisioning/deployment definitions
by Treadwell, Jem 14 Jun '06

14 Jun '06

Hi, On Thursday's call we'll be looking at the two open trackers for the Glossary 1.5. Tracker 1775 says: Reconsider the definition of provisioning (and maybe deployment), per the minutes of the 3/13/2006 OGSA telecon, and depending on the eventual definition agreed by BES & CDDLM. Defer until the next OGSA version if it is premature at v1.5. We need to make a decision on Thursday as to whether to change these definitions for this version. I haven't heard of any agreement on this in the other groups, but if (despite the attraction of a Glossary discussion) you're not going to be on Thursday's call and you have input about this, please let me know. We'll also be reviewing the remaining items in tracker 1770. Thanks! - Jem

1 0

OGSA Roadmap editors meeting notes
by Christopher Jordan 14 Jun '06

14 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Attendees: Chris Jordan, Patricia Kovatch (SDSC) Dona Dickinson (NGC) Mike Behrens (R2AD) The meeting consisted primarily of an overview of proposed organizational/preparational tasks, listed below with responsible parties Getting Contact Information for all groups (Chris will get from Hiro, Dona will maintain future list) Getting new document list for inclusion in next Roadmap document (Chris will discuss with Hiro, Jem, and OGSA-WG) Chris feels that section 1 needs to be rewritten to provide a more general motivation, as the current version focuses on follow-on activities to the release of the OGSA 1.0 Architecture document. One proposed addition/replacement for this section is a more detailed history of the GGF/OGSA efforts, and their relationship to other ongoing Grid Services standards work. (Chris has agreed to begin work on this) Chris: The areas of section 2 regarding "OGSA process and compliance", and the ability of implementations to claim various levels of OGSA-conformance seems to need re-examination or clarification - It is not clear to the editing team how a "compliance test" for some of the involved standards documents would be implemented, and the number of levels of conformance seems overly complex. It is also not clear how the various levels relate to the ability of implementations to interoperate. Also need clarification on OGSA process discussion. (It was suggested that the process and compliance material might be best placed in a related but separate document. This topic has been deferred for later discussion, ideally with Hiro, Jem, and possibly the entire group) All participants agreed that the document should include at least a more detailed summary of lower-level standards which OGSA and related documents build upon or assume some implementation of (I.E. XML, Schemas, WSDL, WSRF, etc), without including detailed tracking information for each of these standards. (Mike Behrens will work on gathering status and relationship information for Web services standards. The OGSA community is actively encouraged to submit individual visions of the software/ standards stack) Mike Behrens suggested that it would be helpful to include a new section on the future vision of OGSA and how that fits within the overall grid computing landscape. What documents have been proposed, and what are needed? The above topic relates to Gap Analysis, a topic which was deferred for later discussion, once we have a better sense of how the new version of the document will take shape. Open Items: The overall vision for the roadmap, and the new documents to be included, probably need to be discussed in an official forum - Chris will propose to Hiro either a session at the OGSA F2F in July, or a discussion on one of the weekly conference calls, to try and get some feedback from the group on both topics. We still need to reformat the data in the spreadsheet into a relational database or other, more manageable form - it was generally agreed that the current status spreadsheet is frightening, at best. We may need a shared web-space backended by a relational database to manage both the project and the technical data involved. it is possible that R2AD may be able to host this space, if GridForge is determined to be inadequate to the needs of the project. The final item is the question of whether a call should be held this wednesday - Chris will be on travel next week, so will be available this week, then unavailable until the last week of june. If Hiro and Jem are available to discuss some of the open items and topics listed above, I believe a call could be useful. Otherwise, I propose we stick to e-mail and schedule the next call for Wednesday, June 28th. Thanks to all the participants. Comments and questions are welcome. - ---------------------------------------------------- Chris Jordan HPC Systems Engineer High End Computing Systems Group San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEjaYBPCVtcXn6kg8RAgExAKDipRS05Yap0XKAjqi6r3iHzG5uKACeMu4t wdbqWdg0Wi490ecb9xtlygU= =sUgz -----END PGP SIGNATURE-----

1 1

GGF OGSA HPC Profile WG created
by Marty Humphrey 13 Jun '06

13 Jun '06

Folks, Just a quick announcement that the OGSA HPC Profile WG has been formed in the GGF. If you are interested in subscribing to the email list, see the forwarded email, below, for instructions). Recently, we have had discussions on the BES and JSDL mailing lists that follow-up on our OGSA HPC Profile BOF at GGF17 (see http://www.ggf.org/mail_archive/ogsa-bes-wg/2006/06/maillist.html and http://www.ggf.org/mail_archive/jsdl-wg/2006/06/maillist.html) We will start to continue these discussions on this new OGSA HPC mailing list. In addition, the gridforge project web page has been created: https://forge.gridforum.org/sf/projects/ogsa-hpcp-wg We will be uploading the current docs in the next couple of days. It's taking a little bit of time to convert the current docs (particularly the use-case doc) into the appropriate GGF format. Note that Gridforge recently changed -- Users from the previous version will need to click the 'Forgot Password' link to set a new password (the authentication scheme changed in the new version). -- Marty -----Original Message----- From: Joel Replogle [mailto:replogle@ggf.org] Sent: Wednesday, June 07, 2006 4:36 PM To: Marty Humphrey Cc: theimer(a)microsoft.com Subject: osga-hpcp-wg email list Marty/Marvin - I just received word that the email list has been set up. Sorry for the delay. You can invite whomever you'd like to subscribe themselves to the list by sending an email message to "majordomo(a)ggf.org" with the following line in the body of the message (subject is ignored): subscribe ogsa-hpcp-wg Thanks, Joel ------------------------------------------------------------------------ ----------- Joel Replogle - Manager of Standards, Global Grid Forum replogle(a)ggf.org http://www.ggf.org <http://www.ggf.org/>

1 0

Teleconference minutes - 12 July 2006
by Andreas Savva 13 Jun '06

13 Jun '06

Gridforge url: https://forge.gridforum.org/sf/go/doc13593?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 12 June 2006 ================================== * Participants Jem Treadwell (HP) Jun Tatemura (NEC) Andreas Savva (Fujitsu) Fred Maciel (Hitachi) Hiro Kishimoto (Fujitsu) Chris Jordan (SDSC) Mike Behrens (R2AD, LLC) Apologies: Tom Maguire Minutes: Andreas Savva * Summary of New Actions ACTION: Hiro will upload updated F2F agenda (mainly updates to the attendees list) ACTION: Hiro to talk with Chris Smith and clarify meaning of pre-script ACTION: Jun will correct the CDL XML examples written by Hiro. ACTION: Hiro to send Chris J the names of the people that provided Roadmap sections in the past. * June 8 minutes approved with no changes * July F2F updates ACTION: Hiro will upload updated F2F agenda (mainly updates to the attendees list) * Action item review - EMS team to review data staging scenario (section 5 of https://forge.gridforum.org/sf/go/doc13591?nav=1) ... - Add sequence diagrams to the scenarios ... - Andreas will merge draft scenarios and sequence diagrams ... Above three actions to be re-reviewed on the next EMS call. - Jay will contact Platform (Chris Smith) and Condor ... - Darren/Andreas will take the Modeling position ... Above two actions to be re-reviewed on the next Information Modeling call * CDDLM & EMS - Reviewed Hiro's presenation and XML documents. - Jun pointed out that codebase is used incorrectly. It should be used in the BLAST declaration not in the PosixApplication. - Also it is not clear what the meaning of pre-script is. ACTION: Hiro to talk with Chris Smith and clarify meaning of pre-script ACTION: Jun will correct the CDL XML examples written by Hiro. - What should be the granular unit of components? - It may be better to define 'filesystem' or 'database' as separate components since they may be re-usable in other contexts. For example, they might be usable also by a 3-tier application component. - It was agreed that this kind of refinement is needed. But it is not a showstopper for delivering the top level CDL for the EMS sequence scenarios. - For the EMS scenarios the following CDL documents are needed: - Original CDL from the repository; - CDL modified by JM before submission to Deployment service (portal) - CDL after deployment (can be retrieved by JM to refine the JSDL document) [The deltas should be fairly small.] - Some explanation on what the constructs in the CDL document mean would also be useful since not everyone will have read the CDDLM documents. - Also highlighting what information (if any) is expected to taken from the JSDL document and used in CDL (and vice versa) - In the simplest case it is 'hostname' and path to the installed executable. - Andreas volunteered to review these CDL documents before the EMS call to make sure they provide the expected information. - What is filesystem 'normal' and 'temporary'? - These are JSDL terms defining filesystem persistency. They only address the simplest cases. More information (e.g., performance characteristics) may be added in but such information is not standardized by JSDL---though there may be examples in the spec. - Chris J mentioned that there has been some work on a Data Scenario (for GFS) that looks at how to represent a global filesystem (available locally or as a separate resource). It will eventually be included in the Scenarios document that Dave B mentioned on the last call. * New Gridforge issues - The new WG page is different from the old one. Many links that Jem had added in the past are missing. - Andreas talked to Joel and was told that the new page is autogenerated from the live charter. - Jem will look into the possibility of customizing a part of the front page. In any case a WG wiki is available so a lot of the information should be put there. - There is a problem with the trackers. Artifacts with multiple files attached were not migrated correctly. (Only one file per artifact made it through; the rest came as 8 bytes.) - Andreas has submitted the issue on the gridforge feedback (wiki) page. The gridforge admins (Joel and Andre) are looking into it. Feedback wiki url: https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ggf-info/wiki/Grid… * Roadmap update - Chris J has had a Roadmap Editor call and has sent the minutes out on the list. - A teleconference with Jem and Hiro and the new team should be arranged. ACTION: Hiro to send Chris J the names of the people that provided Roadmap sections in the past.

1 0