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

Teleconference minutes - 22 June 2006
by Andreas Savva 05 Sep '06

05 Sep '06

Attached. Main topics: - BSP public comment review - Information modeling discussion Gridforge: https://forge.gridforum.org/sf/go/doc13624?nav=1 -- Andreas Savva OGSA Teleconference - 22 June 2006 ================================== * Participants Michel Drescher (Fujitsu) Hiro Kishimoto (Fujitsu) Takuya Mori (NEC) Darren Pulsipher (EMC) Andreas Savva (Fujitsu) Dave Snelling (Fujitsu) Marvin Theimer (Microsoft) Jem Treadwell (HP) Pete Ziu (Northrop Grumman) Minutes: Andreas Savva * June 12 minutes approved with no changes * June 15 minutes approved with no changes * Action items review - Andreas will categorize OGSA 1.5 issues and send the list to Dave Snelling. - Done, waiting for response. - Review at next "OGSA 1.5" call. - Andreas and Hiro to talk offline about how to start sending ical invitations. - Done. - Andreas will send an email to the list explaining where the calendar is and what invitations will be sent out. - Jun will correct the CDL XML examples written by Hiro. - No update. - Hiro will probably move the review teleconference to another day. - 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) - Andreas has read it. - Bring to people's attention again at the next EMS call. - 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 has started doing the sequence diagrams in RSM - Darren volunteered to help out - Review again at the next EMS call - Andreas will merge draft scenarios and sequence diagrams to the "EMS Architecture Scenarios" document (postpone until June 22) - Review again at the next EMS call. * Roadmap (postponed) * Authorization (postponed) * BSP Public Comments Reviewed public comments and Takuya's proposed replies 1. Add text explaining that the Secure Channel profile is not required by all ogsa services. The introduction is probably a good place for this. 2. [Basic-Security-Profile] usage. The term is defined in the document. Takuya to check whether such special terms are used consistently and that they stand out. Refer to the WSRF BP for a similar example. 3. Ciphersuites: Agreed that it important to list acceptable ciphers. - As a first step Takuya will list up available ones (from the WS-I BSP); select the ones that are in common use; and then select the ones that are considered sufficiently safe. - Review the list at the next BSP teleconf 4. Multiple keys in keyinfo field? - Takuya to talk to Von in order to understand the use case for multiple keys; and will propose a resolution at the next BSP teleconf. The next BSP review is set for the June 29 teleconference. * Information Model rendering discussion Started with the question of whether a rendering discussion is the right discussion to have. Concluded that talking only about the rendering overlooks more important issues: what the intermediate model should be and how it should be derived. One question is whether it is possible to define tags with semantics sufficiently pinned down to offer users the guarantee that a correct choice will be made when placing a job. For example, what does the system guarantee the user when a job requesting a box with "OS=Linux" (possibly of a specific version). There is enough variance to match with a box that advertises itself in this way but will not be able to run the job for other reasons (configuration etc). And vice versa other boxes that could potentially run the job may be missed. There was some discussion on various lists (BES, JSDL) already about the feasibility of defining equivalence classes but it is unlikely that anything like that can be done in the near term. The best that can be done is to define such terms while leaving some of the details unsaid (in the manner of JSDL). There is a tension between trying to describe something precisely while allowing the necessary looseness. Another issue is how to define the set of terms that people will actually want to use. There are many successful systems that are based mainly on user defined tags (or, equivalently, pre-configured queues that guarantee some kind of resource configuration) that are mainly site specific. It may not be possible to define these tags normatively however. So one key decision for the intermediate model is whether it should be driven by site-specific/defined information; or whether it should be driven from precise definitions like CIM. - There has been success for both sides (noting that Condor successes are often linked to also providing concrete specifications) - Informal definitions might not work across sites and this is a big issue for interoperability. - One community driven way forward would be to set up a framework to define combinations of capabilities; but this is likely to take a long time. GGF has published work with JSDL 1.0. The model is known to have deficiencies but captures a small set of common resource descriptions. The terms & concepts are a distillation of terms already in use at a number of sites running Globus, Unicore, (and to some extent Condor). - There is a compliance issue. For example, what does it really mean to say that a system is JSDL 1.0 compliant? What should the users expectation be and can the vendor deliver accordingly? - CIM has some experience in this area. It precisely enumerates known features (but there is no notion of (algorithmic) equivalence classes). Tentative consensus that both approaches are needed. It is important to be careful not to promise more than can be done with JSDL style resource descriptions. And that keeping these fuzzy to some extent does that. Also that user defined tags are needed. Since JSDL already allows the inclusion of user defined tags (xsd:any) the next question is whether there is a need to also define a framework for users to define their tags or to leave this completely open. Tentative consensus that defining a (or some) generic element with associated well defined matching semantics to allow users to add their own tags is a good idea. Marvin is working on a proposal for such an element and will post it to the relevant list(s). - Jay is also probably thinking along these lines so some offline discussion between Jay and Marvin might be good. - The proposal should be sent mainly to the OGSA Information Modeling team since they are the drivers of this work. And also to JSDL and BES; the other stakeholders in this process.

2 1

No call on July 3rd
by Hiro Kishimoto 04 Jul '06

04 Jul '06

Hi all, Since July 4th is US holiday (Independence day), we have no call on July 3rd. Next call is July 6th Thursday. <*NEXT CALL*> July 6 (Thu): EMS scenarios (Steven and Andreas) July 10 (Mon): Information model (Ellen and Fred) Roadmap 1.1 (Hiro, ChrisJ, and Jem) Security & BSP Public Comments review (Frank and Takuya) CDDLM & EMS (Jun and Hiro) July 13 (Thu): F2F prep (Tom and Hiro) July 17-20: F2F meeting in Chicago (ANL) Enjoy your holiday! -- Hiro Kishimoto

2 1

Teleconference minutes - 29 June 2006
by Andreas Savva 30 Jun '06

30 Jun '06

Minutes attached. https://forge.gridforum.org/sf/go/doc13636?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 29 June 2006 ================================== * Participants Andreas Savva (Fujitsu) Darren Pulsipher (EMC) Steven Newhouse (OMII) Takuya Mori (NEC) Mark Morgan (UVa) Tom Maguire (EMC) Hiro Kishimoto (Fujitsu) Chris Jordan (SDSC) Donal Fellows (UoM) Minutes: Andreas Savva * June 22 minutes approved with no changes * June 26 minutes approved with no changes * Action review - Hiro to confirm contact with (ex-)EGA TC - Explained action background: look into holding a session to investigate how the EGA reference model fits with OGSA now that GGF and EGA have merged. - This would also be interesting for the Roadmap - Add sequence diagrams to the scenarios: (postpone until June 29) - 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 has started doing the sequence diagrams in RSM - Darren volunteered to help out - Review again at the next EMS call (June 29) - Andreas will merge draft scenarios and sequence diagrams to the "EMS Architecture Scenarios" document (postpone until June 29) - Both of these actions are in progress and their status reviewed during this call. [It is ok to close both since the actions activities listed are part of the document preparation and are reviewed separately.] - 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) - Waiting for Jay to get additional material - Waiting for Marvin's proposal - Darren/Andreas will take the Modeling position paper and discuss it within the JSDL-WG as well (postpone until June 19) - It was discussed on a call a few weeks ago and the group is in a wait-and-see state on this issue. Not clear what is new or better with this rendering proposal. - The overall activity is driven by the previous action. Closed. * Security discussion postponed * GGF18 sessions review - Groups get automatic approval if up to 2 sessions - Last call the proposal was for four so AD approval would be needed. - Possible F2F for the Friday. The venue is not fixed yet ACTION: Hiro will send out an email outlining the proposal and aim to confirm it on the next call * CDL documents review Hiro produced and sent out new versions of the CDL documents. A few remaining issues were discussed. - Location of application binary (to deploy from) and format. Agreed that in general the client would not know these (but may know under certain circumstances). So in general - deployer (or perhaps developer) produces (original) CDL - Client produces jsdl - And a repository or some other internal component keeps track of binaries and related information - Permission and Owner of files. - The binary does not have to be owned by the user running the job; user just needs to be able to execute. - Simplest case assume that the correct permissions/ownership are set in the archive - If the desire is to show it as an example in the CDL something like "root.bin 755" or perhaps "blast.blast 755" or 555 is appropriate. - These are also affected by system policy. - pre-script - Hiro has talked with Chris Smith and they have removed the pre-script. - Assume instead that the db is pre-formatted (perhaps by an earlier user job) and that it can be made available by requesting a specific filesystem be made available on the host. - Hiro added 'database' filesystem. ACTION: Hiro to ask Jun and Dejan to check the CDL documents ACTION: Hiro to also make any relevant updates to the Scenarios text ACTION: Jun/Hiro to also prepare the post-deployment BLAST CDL document * EMS Scenarios review Andreas sent out sequence diagrams produced by RSM. It includes a couple of the early scenarios (Direct and Indirect Job execution) and the "Deploy an application" scenario. This sequence diagram is based fairly closely to the text reviewed in earlier calls. Did a walkthrough of the Deploy scenario: - There are too many call outs to generic Information Services. These should be abbreviated in this scenario and expanded and made more concrete in others, e.g., the ACS or EPS scenarios. - Hiro's CDL does not allow the JM to change anything (and hostname is part of the deployment API). Need to look into this further. In any case it is important to also have an example of a post-deployment CDL document. (See action above) - There is a small mismatch between what the scenario describes as the interaction with the deployment service and what CDDLM seems to expect. Need to decide whether the scenarios should show the JM driving the interaction with CDDLM directly or whether there is a deployment service that does it. The next steps are to do the EPS sequence and the ACS sequence. ACTION: Andreas will send the EMS Model exported from RSM to Darren (done) ACTION: Donal will sent out the link to the draft EPS document (done) ACTION: Andreas to upload the sequence diagrams to Gridforge. Andreas will also prepare a revised EMS Scenarios document for the next call.

1 0

CDL document for BLAST
by Hiro Kishimoto 29 Jun '06

29 Jun '06

Hi all, The following is my write up for CDL document for BLAST application based on the dialogue with Chris Smith. So far, I guess we will translate JSDL document to CDL document or extract necessary information from JSDL document and put them into CDL document. However JSDL document does not have a couple of information we need for CDL. (1) Application binary source location and its archive format. (2) File permission on the target server. We can add such necessary information into the JSDL document as extensions. For (2), we can assume default value (e.g. 755). Another possibility is we expect client tooling produce both JSDL document and CDL document at the same time. Advantage of this option is the tooling can guarantee consistency between JSDL document and CDL document. Chris and I agree this is reasonable scenario as our first step. Regarding to BLAST database, we expect client must run prep-job to format BLAST database and BLAST job should mount such formatted database before BLAST run. Formatted database should be reside e.g. /db/ncbiblast/est which should be mounted before BLAST run. The attached files are revised JSDL and CDL documents for review. I value your feedback. -- Hiro Kishimoto

1 0

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

28 Jun '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 29th. 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: 0629 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 & 29) - https://forge.gridforum.org/sf/go/doc13624?nav=1 - https://forge.gridforum.org/sf/go/doc13628?nav=1 Action Items status review (see the bottom of this email) July F2F and GGF18 plan update (if any) Agenda bashing 2) CDDLM & EMS joint discussion (Jun and Hiro, 30 min) Jun and Hiro will send out revised material before the call. minutes form July 12 call > - 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. 3) EMS scenarios (Steven and Andreas, 30 min) Andreas will send out revised scenario document before the call > - EMS team (Steven, Andreas, Donal) to review data staging scenario > (section 5 of https://forge.gridforum.org/sf/go/doc13591?nav=1 ) > Bring to people's attention again at the next EMS call. > (postpone until June 29) > - Add sequence diagrams to the scenarios: (postpone until June 29) > - 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 has started doing the sequence diagrams in RSM > - Darren volunteered to help out > - Review again at the next EMS call (June 29) > - Andreas will merge draft scenarios and sequence diagrams to the > "EMS Architecture Scenarios" document (postpone until June 29) 4) 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. 5) Basic Security Profile Public Comments review (Takuya 20 min) Takuya will send out proposed text change before the call Minutes from June 22nd call > Reviewed public comments and Takuya's proposed replies > 1. Add text explaining that the Secure Channel profile is not > required by all ogsa services. The introduction is probably a > good place for this. > 2. [Basic-Security-Profile] usage. The term is defined in the > document. Takuya to check whether such special terms are used > consistently and that they stand out. Refer to the WSRF BP for a > similar example. > 3. Ciphersuites: Agreed that it important to list acceptable > ciphers. > - As a first step Takuya will list up available ones (from the > WS-I BSP); select the ones that are in common use; and then > select the ones that are considered sufficiently safe. > - Review the list at the next BSP teleconf > 4. Multiple keys in keyinfo field? > - Takuya to talk to Von in order to understand the use case for > multiple keys; and will propose a resolution at the next BSP > teleconf. 6) Wrap up AOB <*NEXT CALL*> July 3 (Mon): Independence day (no call) July 6 (Thu): EMS scenarios (Steven and Andreas) July 10 (Mon): Information model (Ellen and Fred) Roadmap 1.1 (Hiro, ChrisJ, and Jem) Security & BSP Public Comments review (Frank and Takuya) CDDLM & EMS (Jun and Hiro) July 13 (Thu): F2F prep (Tom and Hiro) July 17-20: F2F meeting in Chicago (ANL) Telecon schedule on wiki: https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Telec… <*ACTION ITEMS*> > From June 26 call - Hiro to confirm contact with (ex-)EGA TC > From June 12 call - Jun will correct the CDL XML examples written by Hiro. > 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 ) Bring to people's attention again at the next EMS call. (postpone until June 29) - Add sequence diagrams to the scenarios: (postpone until June 29) - 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 has started doing the sequence diagrams in RSM - Darren volunteered to help out - Review again at the next EMS call (June 29) - Andreas will merge draft scenarios and sequence diagrams to the "EMS Architecture Scenarios" document (postpone until June 29) > 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

OGSA Roadmap Editors call
by Christopher Jordan 28 Jun '06

28 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 OGSA Roadmap Document Editors and assorted interested parties, Please join me for a roadmap planning call, Wednesday June 28th at 3pm PDT/6pm EDT/7am (6/29)Tokyo time. We will begin discussing tasks assignments and action items to start reshaping the document, so if you intend to be actively involved in this process, please either join the call or contact me via e-mail in the next day. Your participation is welcomed and encouraged. I have tentative commitments from a few individuals for specific tasks, so I hope to make it a short call, primarily to allow a last chance for new participants and to make sure we're all on the same page as far as the direction we're taking with the document is concerned. From this point on, I hope to make these regular, approximately bi-weekly calls. The call-in information is: Meeting Title: OGSA Roadmap Editing Meeting Date: June 28, 2006 03:00 PM [Pacific Time] Duration: 1 Hour To Join Audio Conference Primary Dial-In: 1 (800) 559-0862 Alternate Dial-In: 1 (630) 424-1461 Passcode: 6102510# Thanks. - ---------------------------------------------------- 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) iD8DBQFEoepAPCVtcXn6kg8RAnTvAKCffq/ph/L83Dkxlo2kMKmBehaIvQCfR4Yx nYESgGWczSEJEjI0KRGMerM= =0aib -----END PGP SIGNATURE-----

1 0

Teleconference minutes - 26 June 2006
by Andreas Savva 27 Jun '06

27 Jun '06

Attached. Also https://forge.gridforum.org/sf/go/doc13628?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 26 June 2006 ================================== * Participants Jay Unger (IBM) Jem Treadwell (HP) Andreas Savva (Fujitsu) Tom Maguire (EMC) Fred Maciel (Hitachi) Michael Behrens (R2AD, LLC) Susanne Balle (HP) Minutes: Andreas Savva * June 22 minutes approval postponed - no quorum * Action review - 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) - Jay is waiting for material from Miron. * OGSA 1.5 review ** Architecture - Reviewed changes for monolithic issue. - Remaining issues from Geoffrey Fox comments will probably be answered separately. Andreas is talking with Dave S. - Other minor changes to update References per Jem's comment. ** Glossary - Reviewed consumer/producer and agreed to delete the definitions since they do not add anything beyond the normal English meaning of the words. - WS-Notification status is still proposed; leave the comment in until the final draft is put out - WSRF status needs update ** Next step - Andreas will confirm with Dave S about the rest of the comments and then send out final drafts for Architecture and Glossary. * Other documents - WSRF Basic Profile expected to be published soon (finished GFSG review) - Basic Security Profiles finished public comment and now in Author review. * New gridforge - The new gridforge is still not allowing users to put in comments to documents under review. - 'Copying' a document in the old gridforge created a hard link; in the new one it is a separate copy. Andreas had to delete all the working drafts that were linked under the Root folder for convenience. He will put together a summary wiki page to current drafts. - Jem is thinking of keeping track of a document state on the wiki (e.g., draft, public comment, etc). This relates a bit to the Roadmap but is smaller scale; just for the OGSA-WG products. - WG front page needs customization, e.g., move links under "Group Information." - Andreas has linked the public calendar into the OGSA forge site and will be announcing it on the list. * GGF18 planning Based on the current work of the group the main topics should be Information Modeling and EMS. Proposal worked on the call is for 4 sessions and an option for a one day F2F, if necessary. - Information modeling: Two back-to-back sessions (90 minutes each) - Info-Model has an overlap with a number of other groups but it is probably better to keep the discussion within one group (OGSA) for now. - The first session on basic information modeling and the next on its relation/application in other groups (BES/JSDL/RSS). - EMS (Scenarios, CDL, etc): One session (perhaps 45 minutes) - OGSA and EGA reference architecture: One session - With the new OGF it may be worth to start discussing how the EGA work fits in. - Need to confirm contact with the (ex-)EGA TC - (Paul Strong was the previous contact but it looks like he is not involved anymore) - Other topics depending on the July F2F results so a 'placeholder' session might be needed if we have to submit requests by July 7. - Option for a back-to-back F2F. - Not clear if it will be necessary - A couple of possibilities for facilities are IBM (Jay) and Northorp Grumman (Pete Ziu) but confirmation is needed. ACTION: Hiro to confirm contact with (ex-)EGA TC

2 1

Public OGSA calendar
by Andreas Savva 27 Jun '06

27 Jun '06

This is to let you know that I have set up an events calendar for OGSA-WG. It is available through the OGSA-WG Gridforge page as a linked application. Go to https://forge.gridforum.org/projects/ogsa-wg/ and look for the 'Calendar' button. Or choose one of the urls below. Teleconference agendas, interim meeting schedule and other events will be posted to this calendar. More tentative planning/schedule information may initially be on the wiki instead. https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Telec… In addition to the Agendas that Hiro is sending out before the teleconferences we will also start sending *calendar invitations*. If you are a regular participant and you have a client that can respond to such invitations please feel free to do so. If not, the invitations may not display properly, sorry. Calendar links: [View it on Gridforge] https://forge.gridforum.org/sf/linkedapplication/do/viewLinkedApplication/p… or http://tinyurl.com/krhe3 [Subscribe using RSS] http://www.google.com/calendar/feeds/ogsa.wg@gmail.com/public/basic [Subscribe using ICAL] http://www.google.com/calendar/ical/ogsa.wg@gmail.com/public/basic Thanks to Google Calendar. -- Andreas Savva Fujitsu Laboratories Ltd

1 0

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

26 Jun '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 26th Monday from 5pm to 7pm (CDT). I will attend off-site seminar on Monday and Tuesday and cannot make the call. Andreas and Tom will chair this call. The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0626 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) - https://forge.gridforum.org/sf/go/doc13624?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) Architecture & Glossary 1.5 final text review (Andreas & Jem, 60 min) Andreas and Jem will send out final draft before the call > - Andreas categorized OGSA 1.5 issues and sent the list to > Dave Snelling. > - Review at next "OGSA 1.5" call. 3) GGF18 session plan (Tom and Andreas, 30 min) Joel asks us to make session request by July 7th. 4) Wrap up (10 min) AOB <*NEXT CALL*> June 29 (Thu): EMS scenarios (Steven and Andreas) CDDLM & EMS (Jun and Hiro) Security & BSP Public Comments review (Frank and Takuya) GGF18 session plan (Tom and Andreas) July 3 (Mon): Independence day (no call) July 6 (Thu): EMS scenarios (Steven and Andreas) July 10 (Mon): Information model (Ellen and Fred) Roadmap 1.1 (Hiro, ChrisJ, and Jem) Security & BSP Public Comments review (Frank and Takuya) CDDLM & EMS (Jun and Hiro) July 13 (Thu): F2F prep (Tom and Hiro) July 17-20: F2F meeting in Chicago (ANL) Telecon schedule on wiki: https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Telec… <*ACTION ITEMS*> > From June 12 call - Jun will correct the CDL XML examples written by Hiro. > 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 ) Bring to people's attention again at the next EMS call. (postpone until June 29) - Add sequence diagrams to the scenarios: (postpone until June 29) - 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 has started doing the sequence diagrams in RSM - Darren volunteered to help out - Review again at the next EMS call (June 29) - Andreas will merge draft scenarios and sequence diagrams to the "EMS Architecture Scenarios" document (postpone until June 29) > 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

3 2

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

22 Jun '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on June 22nd. 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: 0622 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 12 & 15) https://forge.gridforum.org/sf/go/doc13593?nav=1 https://forge.gridforum.org/sf/go/doc13618?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) Information model (Jay, Andreas and Fred, 30 min) > - 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. You can download current material from here; - Information Modeling in OGSA - Position Paper https://forge.gridforum.org/sf/go/doc13073?nav=1 - BES Information Model https://forge.gridforum.org/sf/go/doc13074?nav=1 - Guidelines on information modeling for OGSA https://forge.gridforum.org/sf/go/doc12798?nav=1 3) Roadmap 1.1 (ChrisJ, Hiro, and Jem, 30 min) Open issues and plan for roadmap 1.1 4) 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. 5) BSP Public Comments review (Takuya 20 min) Public Comments period for BSP ends June 20th. Takuya will report out comments posted and how to handle them. 6) Wrap up AOB <*NEXT CALL*> June 26 (Mon): Architecture & Glossary 1.5 (Andreas and Jem) GGF18 session plan (Tom and Andreas) June 29 (Thu): EMS scenarios (Steven and Andreas) CDDLM & EMS (Jun and Hiro) Security & BSP Public Comments review (Frank and Takuya) GGF18 session plan (Tom and Andreas) July 3 (Mon): Independence day (no call) July 6 (Thu): EMS scenarios (Steven and Andreas) July 10 (Mon): Information model (Ellen and Fred) Roadmap 1.1 (Hiro, ChrisJ, and Jem) Security & BSP Public Comments review (Frank and Takuya) CDDLM & EMS (Jun and Hiro) July 13 (Thu): F2F prep (Tom and Hiro) July 17-20: F2F meeting in Chicago (ANL) Telecon schedule on wiki: https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Telec… <*ACTION ITEMS*> > From June 15 call - Andreas will categorize OGSA 1.5 issues and send the list to Dave Snelling. - Andreas and Hiro to talk offline about how to start sending ical invitations. > From June 12 call - Jun will correct the CDL XML examples written by Hiro. > 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