Folks, Attached is the timetable with below updates: - Added some breaks during sessions. - Inserted review slot for the NAREGI PSE material. I got a confirm on the call time from the NAREGI PSE team. Tue 5/24 8:00 EDT = Wed 5/25 21:00 JST I'm still compiling the issues list, but I attach the current one, not to lose your chance to review and apend your own items. Feel free to make comments. I will maintain them. -Keisuke Proposed Timetable for the face-to-face meeting on May 23 and 24 (Rev. 3) Legend: Time Item (Owner; time slot) *** DAY 1 (May 23) *** 10:00 Agenda bashing, role call, note taker & time keeper. (KF; 10 min) 10:10 OASIS SDD TC updates (Tom; 45 min) - history - plan and milestones - relationship to GGF CDDLM-WG - collaboration with ACS-WG; scope, participation ... 10:55 Break 11:10 ACS requirements and issues list overview (KF; 1 hour) - Review the requirements description to be merged into the WG draft spec. - Itemize, prioritize and the issues in a list - Use of the tracker in gridforge. Homework: Keisuke will make a draft of issues list by F2F. Everybody, to append missed items if there is any. 12:10 Interface between ACS and CDDLM. (KF and Sachiko; 1 hour) - Summary report on CDDLM component model. - "addFile" in CDDLM deployment API. There are two possible mapping (relationship) between them and ACS/ARI. Homework: Everybody, provide with relevant information. 13:10 Lunch break 14:30 Security (Mike; 30 min) - General understanding on the range of the security topics in ACS. - Minimum requirements on ACS spec. - (There are multiple and extensive topics and issues in security area. To what extent, we need to address those. Authentication, authorization, encryption, digital signature, etc..) 15:00 Other items in issues list (Mike; 30 min) - WSDM management interface in ACS. - Updates on OGSA naming activity. - Specification on the data transport to be used with ACS. 15:30 Interoperability Goal (KF; 1 hour) - Other activities which may have relationship with ACS - EGA, EGEE, OMII, etc. - Define target systems and scope. Homework: Everybody, to provide with relevant information. 16:00 Break 16:15 Use case walk through (Mike; 30 min) - Current SDD and candidates, naregi. 16:45 Review of the NAREGI PSE information. (KF; 30 min) - Material will be posted on the acs-wg by noon EDT. - Review the information if there are questions or issues. - Return comments or questions to PSE team to prepare the call in the next morning. 17:15 Wrap up day 1 and planning for next day (KF; 30 min) 17:30 End of day 1 ## Why not we go dinner together? *** DAY 2 (May 24) *** 8:00 NAREGI integration (KF; 1 hour) - Use case description in the WG draft. - ACS interface example to NAREGI type of deployment engine. - Requirements 1: multiple compiled binaries in ACS. - Requirements 2: data caching in ACS. Homework: Keisuke, to arrange a call bridge. 9:00 WG draft writing plan. (KF; 1 hour) - Review of the table of contents. - Editorial work. - Drafting additional contents, for example, new use cases, security requirements, ARI interface detail including WSDL, AAF in detail. 10:00 Break 10:15 GGF14 session plan (KF; 1 hour) - avoid conflicting with CDDLM/WSDM joint session - Deadlines Draft document deadline: May 27, 2005 Session request deadline: June 3, 2005 - Chairs update - critical updates and training: Monday, 27 June 2005 11:15 Management and/or strategy in the ACS activity. (KF; 1 hour) - Regular teleconference - Recruiting in the European Grid community. 12:15 Lunch break 13:30 New use cases (Mike; 1 hour) # split and moved from day 1 per Mikes request. - Shipping - Federation 14:30 OGSA roadmap report and SCRM collaboration (Mike; 1 hour) - expected users - referenced specifications 15:00 Wrap up F2F meeting and review of action items. (KF; 30 min) 15:30 End of day 2 Title: Issues on the ACS specification. Date: May 20, 2005 Created by: Keisuke Fukui # This is an early version of the compilation with cut and paste # from earlier communication. To be refined and updated. - Decide the minimum set of requirements on security specification in ACS. - Demonstrate the recommended interface between ACS and CDDLM - Demonstrate the recommended interface between ACS and NAREGI type deployment engine. - Define the relationship of the SDD specification and ACS specification - Decide the detail service interface for ACS (ARI). - Converge the Archive Descriptor schema into IUDD schema. - Find the interoperability target and scope in other grid activity. EGEE, omii, etc. - Find appropriate candidates for reference implementations. - Collect use case descriptions to be shown in the spec. a) the new requirements from NAREGI PSE - including source code to be compiled for each target platform at or prior to the deployment of the application. - storing compiled binaries for target platforms in the repository. - storing (caching) the input and output data pairs through the lifecycle of the multiple executions of the application. b) relationship to the deployment API and component mode being discussed in the CDDLM-WG. - 'addFile' interface in the deployment API looks to be a candidate contact point with ACS, for example, "register" interface of ARI. - where the ACS interfaces should stand in the CDDLM's lifecycle model. - other (expected) GGF WGs such as OGSA design teams. c) collaboration with IUDD standardization group - Archive standard will be output from IUDD standardization. How can we contribute to it, to archive the common format for the grid deployment. Probably we should discuss Grid specific consideration at ACS, then report our outcome to the IUDD group. - Repository interface standard for Grid system will be output from GGF ACS. d) recruiting involvement from the European communities. One of the comments I got after the sessions is that we should seek for the participants from European Grid communities since they share much with our usecase and scope. We need a research on this possibility. UniGrid, EGEE, omii, and more... Open Issues in Strawman Draft of the ACS Spec. - More appropriate name and its abbreviation for Application Archive (AA). [3.1 Definition of Application Archive] - Details of Register interface, and method of uploading the entity to be registered. [5.1.1 Register] - Details of Remove interface. [5.2.2 Remove] - How to specify the Application Content in getContent interface. [5.2.3 GetContent] - Whether the putContent interface is necessary or not. [5.2.4 PutContent] - Details of events. [5.3.1 event of AA updating and 5.3.2 event of AA deletion] - List up and details of types of Application Contents. [6.4 Application Contents] - Clean up the relationship with DCML. [7.3.1 DCML] - Details of security [8 Security Consideration] - Details of samples [9 Samples] - Details of schema definition [10 Schema Definition]
Folks, Here is an updated version of my issues list. I attach the same timetable with the last one for you convenience. -Keisuke Keisuke Fukui wrote:
Folks,
Attached is the timetable with below updates: - Added some breaks during sessions. - Inserted review slot for the NAREGI PSE material.
I got a confirm on the call time from the NAREGI PSE team. Tue 5/24 8:00 EDT = Wed 5/25 21:00 JST ^^^^^^^Tue 5/24 I made reservation for the conference call bridge.
Date & Time: May 24 Wed 8:00 EDT/May 24 Thu 21:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111 Title: Issues on the ACS specification. (Rev. 2) Date: May 20, 2005 Created by: Keisuke Fukui - Demonstrate the recommended interface between ACS and CDDLM - 'addFile' interface in the deployment API looks to be a candidate contact point with ACS, for example, "register" interface of ARI. - where the ACS interfaces should stand in the CDDLM's lifecycle model. - Demonstrate the recommended interface between ACS and NAREGI type deployment engine. i.e. separate archives for different binary from the same source code, or in multiple binaries in a single archive. - Decide the detail service interface for ACS (ARI). - Find the interoperability target and scope in other grid activity. e.g. EGEE, omii, etc. We need a research on possibilities. - Find appropriate candidates for reference implementations. - Collect use case descriptions to be shown in the spec. - Find values and issues in storing (caching) the input and output data pairs through the lifecycle of the multiple executions of the application. - Decide the minimum set of requirements on security specification in ACS. - Find the appropriate level of the security description in ACS specification regarding to overview, requirements and/or normative specifications. - Define the relationship of the SDD specification and ACS specification - Converge the Archive Descriptor schema into IUDD schema in SDD TC. - Define the collaborate with OASIS SDD TC. - Archive standard will be output from SDD standardization. How can we contribute to it, to archive the common format for the grid deployment. Probably we should discuss Grid specific consideration at ACS, then report our outcome to the SDD TC. - Repository interface standard for Grid system will be output from GGF ACS. - Define the collaboration with other (expected) GGF WGs such as OGSA design teams. Open Issues in Strawman Draft of the ACS Spec. - More appropriate name and its abbreviation for Application Archive (AA). [3.1 Definition of Application Archive] - Details of Register interface, and method of uploading the entity to be registered. [5.1.1 Register] - Details of Remove interface. [5.2.2 Remove] - How to specify the Application Content in getContent interface. [5.2.3 GetContent] - Whether the putContent interface is necessary or not. [5.2.4 PutContent] - Details of events. [5.3.1 event of AA updating and 5.3.2 event of AA deletion] - List up and details of types of Application Contents. [6.4 Application Contents] - Clean up the relationship with DCML. [7.3.1 DCML] - Details of security [8 Security Consideration] - Details of samples [9 Samples] - Details of schema definition [10 Schema Definition] Proposed Timetable for the face-to-face meeting on May 23 and 24 (Rev. 3) Legend: Time Item (Owner; time slot) *** DAY 1 (May 23) *** 10:00 Agenda bashing, role call, note taker & time keeper. (KF; 10 min) 10:10 OASIS SDD TC updates (Tom; 45 min) - history - plan and milestones - relationship to GGF CDDLM-WG - collaboration with ACS-WG; scope, participation ... 10:55 Break 11:10 ACS requirements and issues list overview (KF; 1 hour) - Review the requirements description to be merged into the WG draft spec. - Itemize, prioritize and the issues in a list - Use of the tracker in gridforge. Homework: Keisuke will make a draft of issues list by F2F. Everybody, to append missed items if there is any. 12:10 Interface between ACS and CDDLM. (KF and Sachiko; 1 hour) - Summary report on CDDLM component model. - "addFile" in CDDLM deployment API. There are two possible mapping (relationship) between them and ACS/ARI. Homework: Everybody, provide with relevant information. 13:10 Lunch break 14:30 Security (Mike; 30 min) - General understanding on the range of the security topics in ACS. - Minimum requirements on ACS spec. - (There are multiple and extensive topics and issues in security area. To what extent, we need to address those. Authentication, authorization, encryption, digital signature, etc..) 15:00 Other items in issues list (Mike; 30 min) - WSDM management interface in ACS. - Updates on OGSA naming activity. - Specification on the data transport to be used with ACS. 15:30 Interoperability Goal (KF; 1 hour) - Other activities which may have relationship with ACS e.g. EGA, EGEE, OMII, etc. - Define target systems and scope. Homework: Everybody, to provide with relevant information. 16:00 Break 16:15 Use case walk through (Mike; 30 min) - Current SDD and candidates, naregi. 16:45 Review of the NAREGI PSE information. (KF; 30 min) - Material will be posted on the acs-wg by noon EDT. - Review the information if there are questions or issues. - Return comments or questions to PSE team to prepare the call in the next morning. 17:15 Wrap up day 1 and planning for next day (KF; 30 min) 17:30 End of day 1 ## Why not we go dinner together? *** DAY 2 (May 24) *** 8:00 NAREGI integration (KF; 1 hour) - Use case description in the WG draft. - ACS interface example to NAREGI type of deployment engine. - Requirements 1: multiple compiled binaries in ACS. - Requirements 2: data caching in ACS. Homework: Keisuke, to arrange a call bridge. 9:00 WG draft writing plan. (KF; 1 hour) - Review of the table of contents. - Editorial work. - Drafting additional contents, for example, new use cases, security requirements, ARI interface detail including WSDL, AAF in detail. 10:00 Break 10:15 GGF14 session plan (KF; 1 hour) - avoid conflicting with CDDLM/WSDM joint session - Deadlines Draft document deadline: May 27, 2005 Session request deadline: June 3, 2005 - Chairs update - critical updates and training: Monday, 27 June 2005 11:15 Management and/or strategy in the ACS activity. (KF; 1 hour) - Regular teleconference - Recruiting in the European Grid community. 12:15 Lunch break 13:30 New use cases (Mike; 1 hour) # split and moved from day 1 per Mikes request. - Shipping - Federation 14:30 OGSA roadmap report and SCRM collaboration (Mike; 1 hour) - expected users - referenced specifications 15:00 Wrap up F2F meeting and review of action items. (KF; 30 min) 15:30 End of day 2
participants (1)
-
Keisuke Fukui