Hi team, Here are the minutes of the GGF16 sessions. Please review it and point out where the record is not correct, if any. They are also available at Gridforge: https://forge.gridforum.org/projects/acs-wg/document/ggf16-minutes-session-1... https://forge.gridforum.org/projects/acs-wg/document/ggf16-minutes-session-2... Also, all the materials can be downloaded from GridForge: https://forge.gridforum.org/docman2/ViewCategory.php?group_id=147&category_id=1215 Thank you, Sachiko ====================================================================== GGF16 ACS Session #1 ----------------------------------------------------------------------- Date and Time: Feb 14 13:30-15:00 EET 2006 Lead: Keisuke Fukui (Fujitsu) Notes: Sachiko Wada (Ascade) ------------------------------------------------------------------------ * Overview of ACS Material: ACS Overview, Sample AA Keisuke gave a brief introduction of ACS specification and a sample application archive which contains AAD, CDL and JSDL. [Q&A] NAREGI: The sample AA includes only one binary. Can I include multiple binaries in a single AA? Keisuke: Yes. This is just a simplest example. * NAREGI-PSE presentation Material: NAREGI_PSEwithACS NAREGI PSE team introduced the PSE architecture, which implements an Application Pool based on ACS 1.0. The presentation included a short demonstration. [Q&A] Keisuke: I understand that the PSE didn't include JSDL as a part of the AA, because parameters are different for each submission of the Job. However, a template JSDL may be included in an AA so that user can retrieve it and modify it with job specific parameters. Keisuke: Is there relationship between AA instances? NAREGI: Yes, we maintain the relationship outside of ACS repository. Mike: Can I obtain the source code? NAREGI: Not yet. But the open source will be available at NAREGI site by next GGF. * Business Grid Computing Project Material: ACS sample implementation by Business Grid Computing Keisuke presented the overview of their implementation on behalf of Business Grid Computing team. No question. ====================================================================== GGF16 ACS Session #2 ----------------------------------------------------------------------- Date and Time: Feb 14 15:30-17:00 EET 2006 Lead: Keisuke Fukui (Fujitsu) Notes: Sachiko Wada (Ascade) ------------------------------------------------------------------------ * Detailed Discussion for Next Step Material: R2AD Vision Starting with Mike's presentation of his idea about ACS future use case, ACS next step was discussed in detail. Keisuke: Regarding to the slide 4, what is the typical use case for the "large complex multi-node system"? Mike: Executing parallel tasks across multiple grid systems. For example, video streaming service which processes the images on the fly. Keisuke: As for "Distribution Challenges" on slide 9, these challenges may be addressed by the other WG/RGs in GGF or existing technologies. For example, OGSA data team addresses data distribution and replication. NAREGI: We have a requirement to maintain relationship between single source code and multiple libraries, and we decided to keep the relationship information outside of the AA. Keisuke: Since the specification is expected to be composable with other standards/technologies and applicable to various systems, it is preferable to manage the relationship between AAs in domain specific way. Mike: My suggestion is adding meta data to AA, such as linkage and type of AA. In some case, conditional linkage will be useful. Keisuke: To specify meta data, we need to model the relationship based on use case analysis. When we find a appropriate representation for models or relationship, which covers diversity of the ACS enabled systems, it is the time the specification address to this. Mike: How about having placeholders in AA for the meantime? NAREGI: We are interested in which direction ACS 2.0 will go. Currently NAREGI PSE has the following plans: - Full Support of ACS V1.0 - AA management based on policy and role. Keisuke: The ACS-WG welcomes the feedback from NAREGI team or any other projects about what is the requirements and how they implement them on top of ACS Spec. 1.0.