Folks, I have added items in issues in spec tracker from the GGF15 review sessions. (This time I added "GGF15" as a group. It doesn't show up in the column, but the below link lead you to the filtered with the value.) https://forge.gridforum.org/tracker/index.php?group_id=147&atid=805&filter=basic I also added remaining TBD items in the spec to the tracker as you can see following the below link (leads you to the "TeleCons" group): https://forge.gridforum.org/tracker/index.php?group_id=147&atid=805&filter=basic If you are to see the entire tracker items, select "Any" for Gruop. Please help us to close those in time by Oct. 27. Thanks! Mike, In the GGF15 sessions, we got two comments form CDDLM forlks. Could you please create the tracker items for those listed below?
* Chapter 5 Steve suggested specifying an ACS Fault type as base of other faults. Stuart suggested that whole tree structure of AAs should be retrieved from Application Repository. Currently users of ACS can retrieve the immediate parent and children of an AA. ACTION: - Mike, to rephrase the Steve's suggestion as an remained issue in ACS-WG. - Mike, to rephrase the Stuart's suggestion as an remained issue in ACS-WG.
I appreciate your efforts on this very much!! -Keisuke Sachiko Wada wrote:
Hi team,
Here are the minutes of the GGF15 sessions. Please review it and point out where the record is not correct, if any.
I will upload the minutes to the gridforge later.
Sachiko
====================================================================== GGF15 ACS Session #1 ----------------------------------------------------------------------- Date and Time: Oct 5 14:00-15:30 EDT 2005 Lead: Keisuke Fukui (Fujitsu) Notes: Sachiko Wada (Ascade) ------------------------------------------------------------------------ We reviewed the ACS specification version 0.51. https://forge.gridforum.org/projects/acs-wg/document/draft-ggf-acs-spec-0.51...
* TOC no comments
(Chapter 1 and 2 was pushed after the rest of the draft.)
* Chapter 3 We reviewed chapter 3 in the draft and OGSA EMS section posted by Mike. The comments from Pete and Sachiko and TBD items are covered and addressed in the draft. ACTION: - Mike, to reconfirm about comment D10 to Pete. (section 3.1.4) - Mike, to draw diagram for section 3.1.4 which describes multiple job creation from a single AA. Issues: - Consider if the digest values can be used to verify cached reference.
====================================================================== GGF15 ACS Session #2 ----------------------------------------------------------------------- Date and Time: Oct 5 18:00-19:30 EDT 2005 Lead: Keisuke Fukui (Fujitsu) Notes: Sachiko Wada (Ascade) ------------------------------------------------------------------------ We continued reviewing the ACS specification.
* Chapter 3 (continued) We continued reviewing chapter 3. Hiro sent comments on section 3.3.4 and we adopted the comments. ACTION: - Mike, to change the diagram simpler since we need not describe whole EMS architecture. (section 3.3.4) Issues: - Revisit comment S18 and S20. (section 3.2.2) - Decide how we can address to the naming issues in the draft, i.e. which of the WS-Name or EPR to be used. OGSA seems to be moving to use WS-Name instead of EPR but have not reach consensus yet.
* Chapter 4 ACTION: - Mike, to confirm to Pete weather the description of section 4.5 replication is sufficient.
* Chapter 5 Steve suggested specifying an ACS Fault type as base of other faults. Stuart suggested that whole tree structure of AAs should be retrieved from Application Repository. Currently users of ACS can retrieve the immediate parent and children of an AA. ACTION: - Mike, to rephrase the Steve's suggestion as an remained issue in ACS-WG. - Mike, to rephrase the Stuart's suggestion as an remained issue in ACS-WG. Issues: - Detailed discussion about resource properties. Should we add manageability properties ? This is related Manageability section. - TBD remained that whether we should use getAAD instead of GetResourceProperty in order to retrieve AAD. - Make clear that who (ApplicationRepository or ApplicationArchive) sends the Notification when AA is created and updated.
The list of the changes to the draft will be posted later. Also, the updated version of the draft will be uploaded to the document manager. The review of the remained chapters will be continued on the tele-conferences aiming at the submission by the end of October.