- acs-wg - lists.ogf.org

Re: Leaving ACS WG
by Keisuke Fukui 22 Jun '06

22 Jun '06

Folks, Since we received the notice of resignation from Tom, I'd like to proceed to ask GFSG approval for removing his name from our ACS-WG co-chair. I believe that we don't need to find his replacement. Our document is very close to GFD-R-P publication and the plan is to pursue the reference implementation and its related technologies for next months. We have a GGF18 event in September, which won't be an issue with this procedure. Please reply to this mail if you have a objection to this. This is the last call before I will send request to our Area Directors next Wednesday June 28 in Japan time. -Keisuke

2 2

Teleconference minutes - Jun 5
by Keisuke Fukui 14 Jun '06

14 Jun '06

Hi team, Here is the minutes of the today's telecon. Please review it and feed back corrections, if you have any. It is also available at the NEW SourceForge: https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.acs-wg/d… # On Jun 3 and 4, the previous gridforge was renewed to the new one. # I'm not very sure if it is fully in production at this moment, but # seems working without problems. - Keisuke ============================================================================== ACS Teleconference Minutes ------------------------------------------------------------------------------ Date and Time: Jun 5 Mon 20:00 EDT / Jun 6 Tue 9:00 JST Participants: Keisuke Fukui (Fujitsu) - minutes Peter Ziu (Northrop) Michael Behrens (R2AD) ------------------------------------------------------------------------------ 1. Role call, note taker & time keeper, agenda bashing. 2. ACS convergence at the OASIS SDD TC. As Tom posted, the SDD TC concluded that it will try to keep alignment with GGF standards, including ACS, JSDL and CDDLM. My idea as a ACS-WG is to keep providing ACS information to them to make sure SDD covers our needs and requirements, then after it is finalized, we can reorganize our specification to have better alignment with it. My expectation is the change to the ACS 1.0 spec. is at a level of name change in the schema rather than hashing the entire structure of AAD document and no impacts on ARI, the repository interface. The migration of the existing implementations of ACS 1.0 should be easy and start after the formal revision of ACS 1.0; that would happen no earlier than 1Q, 2007. All of the SDD TC Document are open to public through the below URI: http://www.oasis-open.org/committees/documents.php?wg_abbrev=sdd You must set a large number for "Number of Documents" field to see whole set of documents. Sorting by column is available on the page. 3. Submission of the final ACS Spec. 1.0 after Public Comments We have finished revision of the document, in response to the public comments collected. The resulted document is uploaded the tracker below: https://forge.gridforum.org/tracker/index.php?aid=1696 We also made replies to comments on the public review tracker: https://forge.gridforum.org/forum/forum.php?forum_id=592 Editor Tracker: https://forge.gridforum.org/tracker/index.php?aid=1696 We expect that it will go through the process soon. 4. GGF17 session and plan for GGF18 I participated several sessions including BES, OGSA at GGF17. No ACS sessions. We anticipate at GGF18 in September to cover reference implementations update including NAREGI PSE, and Business Grid. Mike mentioned making use of open repositories to hold implementation code. 5. Updates Tom is retiring from IBM on June 9th. He will be sending his resignation notice of ACS-WG co-chair. At this moment that we have finalized our ACS Spec. 1.0, we don't need to fill his position immediately. (Tom's resignation notice was posted to acs-wg on Jun 8.) 6. Wrap up, Next meeting(5 min) From now on, we will focus on the reference implementation related activity, including research/supporting work or recruiting the new projects . Next meeting was not scheduled. Separate notice will be posted on demand.

1 1

Leaving ACS WG
by Thomas Studwell 09 Jun '06

09 Jun '06

All, I wanted to let you know that, effective Friday, June 9, I am retiring from IBM and will therefore no longer participate in the ACS workgroup. Consequently I am resigning from my position as co-chair on the ACS WG. I have enjoyed working with all of you, especially Keisuke Fukui, who has put a tremendous amount of energy into ACS. Take care, I wish you all well in continuing your efforts. Thomas W. Studwell Senior Technical Staff Member, Autonomic Computing Architecture IBM Software Group B140/Bldg 500 4205 S Miami Blvd, Durham, NC 27703 (919) 254-7574 Fax: (919) 254-7628 Mobile: (919) 619-1038 studwell(a)us.ibm.com "There is a word for complaining about a problem without proposing a solution - it's called whining." Ric Telford 2006

2 1

Agenda for the Call on Jun 6 Wed 20:00 EDT/Jun 7 Thu 9:00 JST
by Keisuke Fukui 05 Jun '06

05 Jun '06

Folks, Here is an agenda for the call. Watch for the irregular day of the week (Monday evening in US time)! See you there! ### Proposed Agenda 1. Role call, note taker & time keeper, agenda bashing. (5 min) 2. ACS convergence at the OASIS SDD TC. (20 min) As Tom posted, the SDD TC concluded that it will try to keep alignment with GGF standards, including ACS, JSDL and CDDLM. My idea as a ACS-WG is to keep providing ACS information to them to make sure SDD covers our needs and requirements, then after it is finalized, we can reorganize our specification to have better alignment with it. My expectation is the change to the ACS 1.0 spec. is at a level of name change in the schema rather than hashing the entire structure of AAD document and no impacts on ARI, the repository interface. The migration of the existing implementations of ACS 1.0 should be easy and start after the formal revision of ACS 1.0; that would happen no earlier than 1Q, 2007. All of the SDD TC Document are open to public through the below URI: http://www.oasis-open.org/committees/documents.php?wg_abbrev=sdd You must set a large number for "Number of Documents" field to see whole set of documents. Sorting by column is available on the page. 3. Submission of the final ACS Spec. 1.0 after Public Comments (5 min) We have finished revision of the document, in response to the public comments collected. The resulted document is uploaded the tracker below: https://forge.gridforum.org/tracker/index.php?aid=1696 We also made replies to comments on the public review tracker: https://forge.gridforum.org/forum/forum.php?forum_id=592 Editor Tracker: https://forge.gridforum.org/tracker/index.php?aid=1696 4. GGF17 session (5 min) I participated several sessions including BES, OGSA. No ACS sessions. Planning one at GGF18 in September to cover reference implementations update including NAREGI PSE, and Business Grid. 5. Updates (5 min) If there are any others... 6. Wrap up, Next meeting(5 min) Total: 45 min ### Logistics for the call Date & Time: Jun 6 Wed 20:00 EDT/Jun 7 Thu 9:00 JST Dial-in Number: 1-712-432-2000 (Iowa) Participant Access Code: 7771111 -Keisuke

1 1

OASIS SDD TC Formal requirements
by Thomas Studwell 01 Jun '06

01 Jun '06

Dear ACS WG members, attached you will find a link to a document that has been approved by the OASIS Solution Deployment Descriptor Technical Committee as the formal requirements for the SDD specification. This document is a result of compilation of over 200 use cases brought by TC members including representatives from your workgroup. We appreciate your input and we believe that we have captured the requirements needed to meet your use cases. Please take a look at the requirements and provide feedback through your representative, Keisuke Fukui. In addition to these requirements, in our recent face to face meeting the SDD TC voted to work with representatives of the ACS WG to try to converge ACS's AAD with relevant portions of the SDD. Work has already begun in this area and we look forward to agreeing on a converged mapping of key elements necessary in both sets of specifications. We understand that you are nearing approval of your V1.0 specification and any changes would most likely be reflected in later versions of the ACS specification but we believe this convergence is important to industry acceptance of both specifications and look forward to working with your representatives on this matter. Link to SDD Requirements Document: http://www.oasis-open.org/apps/org/workgroup/sdd/document.php?document_id=1… Thomas W. Studwell Senior Technical Staff Member, Autonomic Computing Architecture IBM Software Group B140/Bldg 500 4205 S Miami Blvd, Durham, NC 27703 (919) 254-7574 Fax: (919) 254-7628 Mobile: (919) 619-1038 studwell(a)us.ibm.com "There is a word for complaining about a problem without proposing a solution - it's called whining." Ric Telford 2006

4 3

[Fwd: Uploaded revised ACS Spec. 1.0, which addressed to the public comments]
by Keisuke Fukui 23 May '06

23 May '06

Folks, I have submitted the revised spec. to our area directors. Thanks for your contributions! -Keisuke

1 0

OASIS Solution Deployment Descriptor TC
by Hiro Kishimoto 17 May '06

17 May '06

Hi all, OASIS OASIS Solution Deployment Descriptor TC is developing XML schema for deployment related metadata of multiple software packages (they call solution). Their scope is widely overlapped with CDDLM, ACS, JSDL, and OGSA-EMS. In order to prevent from undesirable divergence, Keisuke Fukui (ACS-WG co-chair) and I have attended to SDD TC F2F meeting this week, introduced our CDDLM/ACS/JSDL specs and ask them to utilize these GGF specifications if appropriate. http://www.oasis-open.org/committees/download.php/18091/ggf-sdd-submission.… http://www.oasis-open.org/committees/download.php/18167/GGF-spec-submission… The F2F meeting went very well and SDD TC agreed that although they chose IUDD V2 specification as their base specification, they will align and converge with ACS/JSDL/CDDLM specs in long team and also short term. It is very good news for both GGF and OASIS. http://www.oasis-open.org/committees/download.php/18210/SDDF2F.html http://www.oasis-open.org/committees/download.php/18208/Strategy%20for%20De… http://www.oasis-open.org/committees/download.php/18209/Deployment%20Descri… If time permits, I will report out and answer questions on this new thrilling opportunity at Thursday's OGSA-WG weekly call. Thanks, -- Hiro Kishimoto

1 0

binary Transport...
by Michael Behrens 14 May '06

14 May '06

I read recently about the W3C recommendations for binary packaging in SOAP called XOP (XML-binary Optimized Packaging) - perhaps we might be able to use that in the future in addition to SWA. Has anyone heard much about it yet and if there is any tooling which supports it yet? http://www.eweek.com/article2/0,1895,1756174,00.asp -- Michael Behrens R2AD, LLC (571) 594-3008 (cell) (703) 714-0442 (land)

1 0

Last call for Application Contents Service Specification 1.0 revision submission
by Keisuke Fukui 09 May '06

09 May '06

Folks, We have finished the revision of the ACS Specification 1.0, addressing to numbers of comments during the public review period. This is the last call for comments before submission to the GGF Editor. If you have comments, please get them to me by 9 am Japan time on Tuesday, May 16. Below is the link for the document: https://forge.gridforum.org/projects/acs-wg/document/draft-ggf-acs-spec-1.0… (no change tracking version:) https://forge.gridforum.org/projects/acs-wg/document/nocb_draft-ggf-acs-spe… Answers to the comments are viewable at: https://forge.gridforum.org/forum/forum.php?forum_id=592 Regards, Keisuke Fukui

1 0

Teleconference minutes - Apr 26
by Keisuke Fukui 30 Apr '06

30 Apr '06

Hi team, Here is the minutes of the today's telecon. Please review it and point out where the record is not correct, if any. It is also available at Gridforge: https://forge.gridforum.org/projects/acs-wg/document/minutes-20060426/en/ - Keisuke ============================================================================== ACS Teleconference ------------------------------------------------------------------------------ Date and Time: Apr 26 20:00-21:25 EST 2006 / Apr 27 9:00-10:25 JST 2006 Participants: Keisuke Fukui (Fujitsu) - minutes Peter Ziu (Northrop) Michael Behrens (R2AD) ------------------------------------------------------------------------------ 1. Role call, note taker & time keeper, agenda bashing. (5 min) 2. ACS Spec. 1.0 Public Comments Results (10 min) - Reviewed changes in the cover page. - Reviewed Section 5.1 and 5.2 Mike pointed out that it is not clear if the client get NotReady state before moving to Ready state. Keisuke will clarify this point in the text. Modification of the state diagram is agreed, to delete the lower arrow starting from the initial state to the Ready state. Pete pointed out that number of pending asynchronous operations can be a Resource Property. We agreed that we leave it to the implementation decision to add a Resource Property for this. There may be lots more which can be additionally provided by implementations. State of the Application Repository itself is not discussed in the document, but it depends on the ACS Repository operational state; if the repository started up, then it is in operational state. If it is shutted down, then it is in non-operational state. - No other outstanding issue at this moment. Please post comments or suggestions if you have any after the call. - Expecting completion of revision in April, addressing all comments except for those involves future extension. We will submit a revision and make response to the comments. - Second revision addressing to the public comments are uploaded https://forge.gridforum.org/projects/acs-wg/document/draft-ggf-acs-spec-1.0… vised/en/ It's under the "Working Draft" folder that I created: Application Contents Service WG : Document Manager : Current Drafts : Working Drafts - Comments can viewable at below link: https://forge.gridforum.org/forum/forum.php?forum_id=592 3. GGF17 session (10 min) No objection raised to cancel the acs session at GGF17 and to have one at GGF18. 4. Updates (5 min) OASIS SDD TC will have F2F meeting during May 15-17. I will attend the meeting and give them introduce Application Archive Format part of our specification. Pete might be able to join the SDD F2F meeting. 5. Wrap up, Next meeting(5 min)

2 2