Hi team, Here are the minutes of our first F2F. Please have a look and make comments if any. The minutes will soon be uploaded to the gridforge together with the input materials. Regards, Sachiko ====================================================================== ACS F2F DAY1 ----------------------------------------------------------------------- Date and Time: May 23 10:00-18:30 EDT 2005 Location: Northrop Grumman, Washington, D.C. Participants: Keisuke Fukui (Fujitsu) Peter Ziu (Northrop) Thomas Studwell (IBM) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ------------------------------------------------------------------------ 10:10 Agenda bashing, role call, note taker & time keeper. Self introduction and reorganizing of the time table. --------------------------------------------------------------------------- 10:45 ACS Overview & Security Guest: Mike Smeltzer Material: Application Contents Service (Mike) [ACS-R2AD-v3b.ppt] ACS Security Considerations (Mike) [Security-f2f-May05.ppt] Conclusion: Our draft won't cover comprehesive topics in security area, but covers only essential topics as the specification. We agreed on the scope of responsibilities of ACS specification. - The Authentication, Authorization and Accounting issues should be comprehensively covered in OGSA and relevant activitiy outside of ACS-WG. ex) How to verify the user and service credentials. - ACS should support some mechanisms to assure the integrity of archives. ex) signature for tampering detection (and encryption), etc --------------------------------------------------------------------------- 12:20 OASIS SDD TC updates Material: IUDD Overview (Tom) Introduction: Tom explained about SDD overview and its standardization status. - OASIS had approved to establish the SDD-TC. - The TC activity will start in early June. Relationship to ACS - AAF may include additional information to SDD. --------------------------------------------------------------------------- 12:50 LUNCH --------------------------------------------------------------------------- 13:40 Re-scheduling --------------------------------------------------------------------------- 13:50 ACS requirements and issues list overview Material: Current requirements list (Keisuke) [20050523ACSstrawman-requirements.doc] Conclusion: We reviewed each of the requirements description which is to be merged into the WG draft spec. In addition, we discussed about the following issues. * Distributing repository This capability is one effective use case of ACS, but is not mandatory. It can be implemented on top of current specification of ACS. It need not to be included in the requirements list. * Consistency ACID property is generally preferable, but it's about the availability and reliability topics of the implementation and is out scope of ACS specification. ACS specification should define a simple specification essential for consistency check of archive. * Relationship between jobs and archives ACS need not to be aware of the relationship between jobs and archives, i.e. which job refers to which archive. Rather it should provide with the external reference to each of archives in the repository. The relationship should be maintained by Job Managers. * Versioning Version management is needed for each archive and not for each content in the archive. Different versions, such as Version 1.1 and version 1.2, should be referenced by different EPRs. Whether the older version is available or not is not concluded. --------------------------------------------------------------------------- 16:00 Review of the NAREGI PSE information. (KF; 30 min) Material: NAREGI PSE with ACS (NAREGI) [naregi-pse-scenario-20050524-correction.pdf] Conclusion: We reviewed the NAREGI PSE material and gathered questions. The questions list was posted to the ML by Keisuke. [Tue, 24 May 2005, "Re: [acs-wg] NAREGI PSE material for F2F meeting"] --------------------------------------------------------------------------- 17:20 OGSA roadmap document Conclusion: - We agreed not to include WSDM as a referenced specification. ACS spec. may use WSDM for manageability but it's not functional part of the ACS specification. --------------------------------------------------------------------------- 17:45 Requirements discussion (continued) See above. --------------------------------------------------------------------------- 18:10 Wrap up DAY1 and planning for DAY2 Rescheduling of the timetable for the next day. 18:30 End of DAY1 ====================================================================== ACS F2F DAY2 ----------------------------------------------------------------------- Date and Time: May 24 8:00-17:00 EDT 2005 Location: Northrop Grumman, Washington, D.C. Participants: Keisuke Fukui (Fujitsu) Peter Ziu (Northrop) Thomas Studwell (IBM) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ------------------------------------------------------------------------ 8:00 NAREGI integration Guests: Hitohide Usami (NII) Motohiro Yamada (Fujitsu) Shigeo Kawata (Utsunomiya Univ.) Material: NAREGI PSE with ACS (NAREGI) [naregi-pse-scenario-20050524-correction.pdf] Conclusion: In current NAREGI architecture: - Source files and binary files are stored in separate repositories. - Deployment is done statically prior to execution phase. - Relationship information among the archives are maintained outside of the ACS repository. The structure is simply flat. - Relationship information is just for deployment and not for execution time. The NAREGI use case is one of the simple case of using ACS and is very good input for ACS requirements. We agreed to continue collaborating with NAREGI PSE team and exchange information. --------------------------------------------------------------------------- 9:40 agenda bashing & re-scheduling timetable --------------------------------------------------------------------------- 10:10 Interface between ACS and CDDLM Material: CDDLM overview (Sachiko) [CDDLM.doc] Conclusion: "AddFile" method in the deployment API is a push to the system interface. When ACS repository work with CDDLM services, it is expected that the contents would be pulled from the ACS repository since they are already stored inside of the grid domain. We will make the a sequence diagram to continue further discussion. We discussed whether the naming of ARI method "Register" is appropriate. One of the opinion is that it should be "Create" since the operation in fact creates an archive in a repository. Other than "create", "Add", "Store" are proposed as alternatives. Tom will make a proposal on this (AI-3). --------------------------------------------------------------------------- 11:10 GGF14 session plan Conclusion: Plan two sessions: - #1 Joint session with CDDLM - #2 Detailed discussion based on the first session. avoiding conflict with: - CDDLM - CDDLM/WSDM joint session - JSDL(?) required equipment - phone connection --------------------------------------------------------------------------- 11:45 Other items in issues list * WSDM management interface in ACS. Material: WSDM (Mike [wsdm--f2f-May05.ppt] Conclusion: We agreed to create manageability-related section in the draft which says like "manageability is provided through MOWS". We may specify the ACS specific manageable capabilities in addition to WSDM required/optional capabilities. Specific capabilities regarding to the WSDM that are required or defined as an option will be specified in the final draft. - WSDM required - WSDM optional - ACS required (and WSDM optional) - ACS optional (and WSDM optional) * Updates on OGSA naming activity. Material: Naming Status (Mike) [naming-status-f2f-May05.ppt] Conclusion: We can use EPRs in the spec, because WS-Naming will be a extension of WS-Addressing (EPR). We can relay on WS-Naming concerning resiliency of the reference. We simply follow the output of the WG and need not to specifically discuss about this inside ACS. * Specification on the data transport to be used with ACS. Conclusion: We recognized the importance of data transportation but couldn't discuss in detail lack of the input. We will continue this discussion. --------------------------------------------------------------------------- 12:40 LUNCH break --------------------------------------------------------------------------- 13:45 New use cases (Mike; 1 hour) Guest: Mike Fetterman (DISA) Conclusion: Mike F. explained his use case, which can be relevant to future ACS. --------------------------------------------------------------------------- 15:20 WG draft writing plan Material: TOC of current ACS draft (Keisuke) Conclusion: We reviewed and revised the TOC of the initial draft. The modified version was uploaded on the ACS project page. [/Current Drafts/draft-ggf-acs-spec-20050527] --------------------------------------------------------------------------- 16:20 Management and/or strategy in the ACS activity. Conclusion: Schedule for weekly (at least by GGF14) regular teleconference is confirmed: - Wed 8:00 pm(EDT)/Thu 9:00 am(JST), every week --------------------------------------------------------------------------- 16:30 Wrap up F2F meeting and review of action items. Material: Issues on the ACS specification (Keisuke) [20050523IssuesList.txt] Conclusion: We reviewed the issues list and established action items. The issues list with action items was posted to the ML. [30 May 2005, "[acs-wg] Issues List and Action Items from the F2F."] ----------------------------------------------------------------------- 17:00 End of DAY2 ======================================================================