acs-wg

Download

acs-wg@lists.ogf.org

November 2005

6 participants
12 discussions

[ogsa-wg] Proposed agenda for Nov. 9th call (CDDLM/ACS/GRAAP joint call)
by Hiro Kishimoto 09 Nov '05

09 Nov '05

Hi all, Apologies for cross-posting *ATTENTION* From Oct. 31 and onward telecon starts one hour earlier 5pm EST = 4pm CST = 2pm PST = 10pm UK = 7am JST OGSA-WG revised charter draft has been accepted by GFSG with no change. Congratulations! https://forge.gridforum.org/projects/ogsa-wg/document/OGSA-WG-Charter-2005/… The following is a proposed agenda for OGSA-WG telecon on Nov. 9th Wednesday from 4pm to 6pm (CST). Dial-in numbers for Wednesday: 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: 1109 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (10 min) Note taker assignment Roll call Telecon minutes approval (Nov. 7th) https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20051107/en/1 Since SC05 is next week, can we have a quorum next week? Agenda bashing 2) CDDLM/ACS/GRAAP joint EMS discussion (60 min) > From F2F minutes; > - Action: Agreed on two-pronged approach for CDDLM(+ACS) on one > side and EMS on the other to describe their approaches in > more detail and to then unify those approaches. (Note > these are 3 separate actions.) > - Action(1): CDDLM team volunteered to look into two issues that > were identified as requirements and report back in an > OGSA call > 1. Where to draw the line in the (CDL) provisioning tree > (see above) > 2. How to provide the cost of configuration Dejan already sent out their discussion summary to the list; http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/10/msg00026.html OGSA-WG has already reviewed their summary (see Nov. 7 minutes) and will give these feedbacks to them. https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20051107/en/1 > - Action (2): Andrew provide one paragraph describing his > expectations from the deployment component. (done) > Using this paragraph, CDDLM-WG provides a feedback on > how they match his expectations. Andrew's description; http://www-unix.gridforum.org/mail_archive/ogsa-wg/2005/11/msg00013.html > Actions(3): > - RSS-WG to produce abstract interface (and responsibilities) of EPS > and CSG. > - Clarify responsibilities/functionality of JM > - Andreas to send detailed EMS draft (pre OGSA 1.0) document to > Steven N. EMS team is working on "composition roadmap" https://forge.gridforum.org/projects/ogsa-wg/document/proposed-ems-roadmap/ > Action(4): Set up a team to explore WS_Agreements issues more, > especially relating to allocation and QoS assurance. And > come back to OGSA-WG on how to use WS-Agreement (possibly > evolved) with EMS. Clarify > - How WS-Agreement possibly needs to change to fit in OGSA > EMS > - Set the first review after 30 days; check what can be > done. > - Volunteers: Steven Newhouse (to lead), Dave Berry, Chris > Smith, (Jim Pruyne; not present >GRAAP-WG to confirm) 3) OGSA naming policy discussion (30 min) Tom will have the written proposal (agreed on the previous call) 4) Information model discussion (20 min) > Action: Andrew to review and point out what is needed for the > BES container > - Goal: A preliminary set of attributes that are > needed for the BES container 5) Common UML tool review (if time permit) > - Mike Behrens has some experience with a number of the listed > tools. He volunteered to check out the rest and give an > evaluation next week > - export/import as one required feature > > - One of the IBM participants will follow up and confirm the > procedures needed and that everyone can use the RSM tool, if the > group decides to go with it. 6) OGSA workshop at Israel Grid Alliance (if time permit) Steve Crumb ask us to send a rep to Tel Aviv before or after GGF16. > In my continued efforts to get an OGSA expert to Israel to discuss > the architecture to a primarily technical audience, Avner and I have > settled on the proposal of having an OGSA half-day workshop > immediately after (or before) the Athens event. This would allow for > someone to be roughly in the same geographic area making a quick, > one-day hop to Tel Aviv much more doable. 7) Wrap up AOB <NEXT CALL> Nov. 14 (Mon) OGSA-AuthZ joint call Basic Security Profile document review, Architecture & Glossary 1.5 Nov. 16 (Wed) EMS architecture, information model & CIM profile Nov. 21 (Mon) Architecture & Glossary 1.5 Profile Definition Update Nov. 23 (Wed) NO call (Thanksgiving) Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ -- Hiro Kishimoto

1 0

Teleconference minutes - Oct 26
by Sachiko Wada 01 Nov '05

01 Nov '05

Hi team, Here is the minutes of the last teleconf. Please review it and point out where the record is not correct, if any. I'll upload the minutes to Gridforge later, since I can not access the page now. Sachiko ======================================================================= ACS Teleconference ----------------------------------------------------------------------- Date and Time: Oct 26 20:05-21:40 EDT 2005 / Oct 27 9:05-10:40 JST, 2005 Participants: Keisuke Fukui (Fujitsu) Peter Ziu (Northrop) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ------------------------------------------------------------------------ * Review of the new Chapters for Samples, Schemas, Open Issues and Authors. ** Title Keisuke proposed to use revision # to represent modification instead of changing version like 0.5x. The title of the draft will be "Application Contents Service Specification 1.0 Revision 0". ** Samples - Change example URL from "foo.example.com" to "foo.ggf.org". (Done on Oct 31) - Mike's question: why use ARI rather than QName to specify attributes such as transport method or transport type. Answer: Both are legal as XML Schema, but URI sounds more extensible so that third parties can add their own transport method or type. - Pete's question: Is the directory structure of the AA depicted in the samples, such as data, app, etc., normative? Answer: No. Only the file name of AAD (aad.xml) is normative. - It should be explicitly explained that the example 5 is the case using the extensibility of the transport method. ** Schemas - Pete proposed to include schemas for Deployment Descriptor within ACS namespace. Conclusion: The schema for DD and its URI would be defined by the other specifications than ACS. If it is done so, it can be presented as a value for the type attribute of the Content element, described in Section 6.1 Action: All, to review the draft and make comments. * Review of the remained comments through the document. No comments left at present. * Review of the "Issues in Spec" tracker items. We could not review the "Issues in Spec" during the meeting due to time restriction. Action: All, to review the "Issue in Spec" as shown in below link and make comments. https://forge.gridforum.org/tracker/index.php?group_id=147&atid=805&filter=… * Schedule toward the submission of the draft We had planned to submit to the GGF editor on Oct 31, but it can be pushed by a week or so, if it requires time to review the draft. (NOTE: Submission date has pushed to Nov 7, see Keisuke's mail on Oct 31) [Projection] Mid Nov. Comments from GGF editor received. End Nov. Comments are addressed and returned. Early Dec. 60 day public review starts. Early Feb. review comments are collected. Mid Feb. updated draft is returned to GGF editor. End Feb. approval by GGF. * Updates OASIS SDD TC F2F will be held during Nov. 14-16. Keisuke will attend the meeting. * Next meeting Date & Time: Nov 9 Wed 19:00 EST/Nov 10 Thu 9:00 JST Calling #: will be announced later Note: Nov 2nd and 16th will be skipped.

1 0