We are starting the conference now.... -Keisuke Keisuke Fukui wrote:

Here is an info. for the call tomorrow.

My applogies that I ran out of time during the last call. To have meeting time concise and more effective, I added time allocation for Agenda.

See you there!

-Keisuke

### Logistics for the call Date & Time: Apr 20 Tue 20:00 EDT/Apr 21 Wed 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111

### Proposed Agenda

1. Agenda bushing and roll call. (5min)

2. Date for F2F (15min) May 18 would be the fastest candidate for the meeting, considering the GGF guideline that call for four week advance announcement. It can be pushed a week or so, depending on the participants schedule. I believe that it is essential to get general agreement on how to create the Working Group draft of acs spec. Goal: Decide tentative dates and place for F2F.

3. Research updates on CDDLM, security, etc.(15min) Please report your findings on these, if any. Goal: Find the refinement to the current requirements description.

4. Issues list (30min) As Sachiko pointed out, it is worth think about what are the issues to create WG draft right now. Attached is my last post describing issues in my mind. Please raise your comments and/or bring up yours. Goal: Create an issues list with actions.

Sachiko Wada wrote:

...

Hi team,

Here is the proposed teleconference schedule from Keisuke.

Next call: Apr 20 Wed 20:00 EST/Apr 21 Thu 9:00 JST

If anyone has problems with this, please feel free to respond to this message.

# Keisuke, let us know the calling info.

By the way, I assume that we have agreed to cooperate to develop ACS specification but I don't think that we have agreed the process. I wonder how I can contribute to our work.

We are going to write up a first working draft by GGF14, late June. It is about time to take some concrete actions. Deciding who writes which part of the document is one way, but there may be some issues left that need to be discussed before starting to write. If there are such issues I want to summarize them first. (Keisuke listed up such issues previously and we have already been discussing about Naregi requirements, but do they enough?)

So, I'd like to hear your opinion about this at the next telconf. ... Does this make sense?

Regards,

Sachiko Wada

------------------------------------------------------------------------

Subject: Re: [acs-wg] For the WG draft of the ACS Spec. From: Keisuke Fukui <kfukui@labs.fujitsu.com> Date: Thu, 24 Mar 2005 13:44:47 +0900 To: acs-wg@ggf.org

To: acs-wg@ggf.org

Folks,

As I announced I propose agenda for our discussions.

I believe we need to visit a number of issues and considerations prior to have a WG draft of the ACS specification, which includes:

- the new requirements from NAREGI PSE, - relationship to other GGF WGs, such as CDDLM-WG and planned WGs for Execution Management System, - collaboration with IUDD standardization group and - recruiting involvement from the European communities.

I will describe them in a bit more detail below:

a) the new requirements from NAREGI PSE - including source code to be compiled for each target platform at or prior to the deployment of the application. - storing compiled binaries for target platforms in the repository. - storing (caching) the input and output data pairs through the lifecycle of the multiple executions of the application. b) relationship to the deployment API and component mode being discussed in the CDDLM-WG. - 'addFile' interface in the deployment API looks to be a candidate contact point with ACS, for example, "register" interface of ARI. - where the ACS interfaces should stand in the CDDLM's lifecycle model. - other (expected) GGF WGs such as OGSA design teams. c) collaboration with IUDD standardization group - Archive standard will be output from IUDD standardization. How can we contribute to it, to archive the common format for the grid deployment. Probably we should discuss Grid specific consideration at ACS, then report our outcome to the IUDD group. - Repository interface standard for Grid system will be output from GGF ACS. d) recruiting involvement from the European communities. One of the comments I got after the sessions is that we should seek for the participants from European Grid communities since they share much with our usecase and scope. We need a research on this possibility. UniGrid, EGEE, omii, and more...

My plan is having a brainstorming on all of these agenda. Originally, it was planned to discuss about our plan including the above at ACS-WG#2 session. It turned out, however, more difficult to perform this at the presence of the audience explaining what is being discussed and with the limit of time. To do the brainstorming the items, we have options below:

- Tele-conferences several times, one or two hours each. - Face-to-face meeting probably one or two days. At the U.S. East coast or in Japan.

We can do either or both depending on our schedule, in addition to the regular mailing list discussion. Since we have not discussed the items at the GGF13, I hope we discuss on this as soon as possible. Can we have a tele-conference to talk about these next week? My proposal for the time is 3/30 Wed 19:00EST (3/31 Thu 9:00JST). Please respond if this works for you.

Also, please feel free to add agenda and give your feedback to the above. I hope that we are starting a great work from here.

-Keisuke

Folks, Here is an agenda for the call tomorrow. See you there! ### Proposed Agenda 1. Agenda bashing, role call, note taker & time keeper. (10min) 2. Planning for the face-to-face. (30 min) I attached proposed time table at the end. 3. Updates (10 min) 4. Wrap up. (5 min) ### Logistics for the call Date & Time: May 18 Wed 20:00 EDT/May 19 Thu 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111 Proposed Timetable for the face-to-face meeting on May 23 and 24 *** DAY 1 *** 1. Agenda bashing, role call, note taker & time keeper. (10min) 2. OASIS SDD TC updates (1 hour) - history - plan and milestones - relationship to GGF CDDLM-WG - collaboration with ACS-WG; scope, participation ... 3. ACS issues list overview (1 hour) - Itemization - Use of the tracker in gridforge. 4. Interface between ACS and CDDLM. (1 hour) - Summary report on CDDLM component model. - "addFile" in CDDLM deployment API. There are two possible mapping (relationship) between them and ACS/ARI. 5. Security (1 hour) - General understanding on the range of the security topics in ACS. - Minimum requirements on ACS spec. - (There are multiple and extensive topics and issues in security area. To what extent, we need to address those. Authentication, authorization, encription, digital signiture, etc..) 6. Other items in issues list (0.5 hour) - Specification on the data transport to be used with ACS. - WSDM management interface in ACS. - Updates on OGSA naming activity. 7. New use cases (1 hour) - Shipping - Federation 8. Interoperability Goal (1 hour) - Target systems. - Range or scope. *** DAY 2 *** 9. NAREGI integration (1 hour) - Use case description in the WG draft. - ACS interface example to NAREGI type of deployment engine. - Requirements 1: multiple compiled binaries in ACS. - Requirements 2: data caching in ACS. 10. WG draft writing plan. (1 hour) - Review of the table of contents. - Editorial work. - Drafting additional contents, for example, new use cases, security requirements, ARI interface detail including WSDL, AAF in detail. 11. GGF14 session plan (1 hour) - Deadlines Draft document deadline: May 27, 2005 Session request deadline: June 3, 2005 - Chairs update - critical updates and training: Monday, 27 June 2005 12. Management and/or strategy in the ACS activity. (1 hour) - Regular teleconference - Recruiting in the European Grid community. 13. OGSA roadmap report and SCRM collaboration (1 hour)

Folks, Here is an agenda for the call tomorrow. See you there! ### Proposed Agenda 1. Agenda bashing, role call, note taker & time keeper. (10min) 2. Wrap up for F2F (15 min) Review action items list and issues list (updated and attached) Decide the deadlines. KF will register them on tracker once approved. Goal: Confirm who and what by GGF14. 3. Updates (15 min) SDD TC call by KF. CDDLM interface, if any.. 4. Wrap up. (5 min) ### Logistics for the call Date & Time: Jun 2 Thu 20:00 EDT / Jun 3 Fri 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111 -Keisuke Title: Issues on the ACS specification. (Rev. 20050523d2) Date: May 23, 2005 Created by: Keisuke Fukui - Clarify the requirements on version control. - Demonstrate the recommended interface between ACS and CDDLM - 'addFile' interface in the deployment API looks to be a candidate contact point with ACS, for example, "register" interface of ARI. - where the ACS interfaces should stand in the CDDLM's lifecycle model. AI-1: Sachiko, to post the proposed sequence for interaction with CDDLM. AI-2: All, to make comment on the sequence with CDDLM. AI-3: Tom, to propose a name for ARI interfaces (functions) - Demonstrate the recommended interface between ACS and NAREGI type deployment engine. i.e. separate archives for different binary from the same source code, or in multiple binaries in a single archive. conclusion: flat description of the archive will work. AI-4: Tom, to send a SDD hierarchy info to NAREGI PSE team. - Decide the detail service interface for ACS (ARI). - Find the interoperability target and scope in other grid activity. e.g. EGEE, omii, etc. We need a research on possibilities. conclusion: pursue only when European grid is OGSA based. - Find appropriate candidates for reference implementations. AI-5: Tom, to ask David Martin about reference implementation. - Collect use case descriptions to be shown in the spec. conclusion: Current one is suffice. AI-6: All, to review the current draft of the ACS specification . - Find values and issues in storing (caching) the input and output data pairs through the lifecycle of the multiple executions of the application. conclusion: postponed. - Decide the minimum set of requirements on security specification in ACS. AI-7: Mike, to make a research on authentication/authorization. AI-8: Pete, to make a research on signature/integrity. - Find the appropriate level of the security description in ACS specification regarding to overview, requirements and/or normative specifications. See above. - Define the relationship of the SDD specification and ACS specification AI-9: Tom, to update the section of AAF in the current draft of the ACS spec. - Converge the Archive Descriptor schema into IUDD schema in SDD TC. See above. - Define the collaborate with OASIS SDD TC. - Archive standard will be output from SDD standardization. How can we contribute to it, to archive the common format for the grid deployment. Probably we should discuss Grid specific consideration at ACS, then report our outcome to the SDD TC. See above. - Repository interface standard for Grid system will be output from GGF ACS. - Define the collaboration with other (expected) GGF WGs such as OGSA design teams. BEM? Open Issues in Strawman Draft of the ACS Spec. - More appropriate name and its abbreviation for Application Archive (AA). [3.1 Definition of Application Archive] - Details of Register interface, and method of uploading the entity to be registered. [5.1.1 Register] - Details of Remove interface. [5.2.2 Remove] - How to specify the Application Content in getContent interface. [5.2.3 GetContent] - Whether the putContent interface is necessary or not. [5.2.4 PutContent] - Details of events. [5.3.1 event of AA updating and 5.3.2 event of AA deletion] - List up and details of types of Application Contents. [6.4 Application Contents] - Clean up the relationship with DCML. [7.3.1 DCML] - Details of security [8 Security Consideration] - Details of samples [9 Samples] - Details of schema definition [10 Schema Definition] Title: Action Items (Rev. 20050523d2) Date: May 23, 2005 Created by: Keisuke Fukui

From the "Issues List": AI-1: Sachiko, to post the proposed sequence for interaction with CDDLM. AI-2: All, to make comment on the sequence with CDDLM. AI-3: Tom, to propose a name for ARI interfaces (functions) AI-4: Tom, to send a SDD hierarchy info to NAREGI PSE team. AI-5: Tom, to ask David Martin about reference implementation. AI-6: All, to review the current draft of the ACS specification . AI-7: Mike, to make a research on authentication/authorization. AI-8: Pete, to make a research on signature/integrity. AI-9: Tom, to update the section of AAF in the current draft of the ACS spec.

From minutes: AI-10: Fukui, to send the request for two sessions in GGF14 by June 3. AI-11: Fukui, to add "Clarify the requirements on version control" to the issues list. AI-12: Fukui, to check the possibility of a joint session with CDDLM-WG at GGF14. AI-13: Fukui, to register the reviewed draft of the ACS spec. by May 27.

Folks, Here is an agenda for the call tomorrow. See you there! ### Proposed Agenda 1. Agenda bashing, role call, note taker & time keeper. (5 min) 2. Proposed sequence for possible ACS/CDDLM interface (15 min) Verify the proposal (Check consistency with the current docs.) See Sachiko's post. Goal: Clear the issues and prepare the material for joint session at GGF14. 3. Updates (15 min) Review the action items list status on tracker. Are we using the tracker effectively? It looks like simply a list on the net. Basic Filter can't filter those with "open OR pending". Looks like that we can't specify columns to be shown or not to be. Review the issues list. Should we register them to the tracker, too? Updates on security, etc, if any.. 4. Wrap up, Next meeting(5 min) ### Logistics for the call Date & Time: Jun 8 Wed 20:00 EDT / Jun 9 Thu 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111 -Keisuke

Folks, Here is an agenda for the call tomorrow. See you there! ### Proposed Agenda 1. Agenda bashing, role call, note taker & time keeper. (5 min) 2. 2nd round for the proposed sequence for possible ACS/CDDLM interface (10 min) We didn't find any issues with it at the meeting last week. Check if Tom has issues or comments. See Sachiko's post. Goal: Confirm we are all ok with the proposal. 3. GGF14 Session plan (10 min) ACS-WG#1: (CDDLM) sequence, AA entry EPR as an optional parameter for CDDLM initialize(), req. analysis on data transport/event notification from CDDLM. ACS-WG#2: (ACS Spec. review) see below for the proposed topics. Goal: Make consensus on the agenda. 4. Draft writing schedule by GGF14. (10 min) We'd like to add contents to the current draft so that we can progress our discussion at GGF14 sessions. Possible candidates are show below (names are proposed drivers for each topic): - Glossary definition refinement. (KF) - Security/Signature discussion for ACS (Mike/Pete) - Repository interface detail, (KF) including portTypes, fault types, synchronous and asynchronous interface, event notification. - CDDLM interface (Sachiko; almost ready) - AAF/SDD refactor (Tom) - Data transport/event notification (TBA) Goal: Make consensus on the agenda. 5. Updates (10 min) Review the action items list status on tracker. Review the issues list. Updates on security, etc, if any.. 6. Wrap up, Next meeting(5 min) ### Logistics for the call Date & Time: Jun 15 Mon 20:00 EDT/Jun 16 Tue 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111 -Keisuke

Folks, Here is an agenda for the call tomorrow. See you there! ### Proposed Agenda 1. Agenda bashing, role call, note taker & time keeper. (5 min) 2. Review of the minutes for the last call. (5 min) Goal: Reconfirm our understanding for GGF14. 3. Draft writing schedule by GGF14. (20 min) We'd like to add contents to the current draft so that we can progress our discussion at GGF14 sessions. Possible candidates are show below (names are proposed drivers for each topic): - Glossary definition refinement. (KF) - Posted. - Security/Signature discussion for ACS (Mike/Pete) - Repository interface detail, (KF) - Posted. including portTypes, fault types, synchronous and asynchronous interface, event notification. - CDDLM interface (Sachiko) - Posted. - AAF/SDD refactor (Tom) - Data transport/event notification (TBA) I'd like the meeting materials merge into the draft spec. to facilitate the discussion effectively. Goal: Make consensus on the agenda. 4. Updates (10 min) Review the action items list and issues status on tracker. Updates on CDDLM, security, etc, if any.. 5. Wrap up, Next meeting(5 min) ### Logistics for the call Date & Time: Jun 22 Mon 20:00 EDT/Jun 23 Tue 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111 -Keisuke

Folks, In the call today, we will review the issues list we generated at May F2F and find which we can close now. https://forge.gridforum.org/tracker/index.php?group_id=147&atid=805&filter=&f_artifact_id=&f_priority=&f_assigned_to=&f_artifact_status=&f_category=&f_artifact_group=&group_id=147&atid=805&sort0=priority I think that #1523, #1536 can be closed today if you agree. Please point out any others to be closed. We'd like to clear up the rest of the issues by August F2F. -Keisuke Keisuke Fukui wrote:

5. Updates (10 min) Review the issues list.

Folks, I made an initial schedule in CDT time by mistake (using the setting for GGF14). Now I changed it to correct time, but 20:15 EDT/9:15 JST. You can access the bridge now. I'm not sure if we can start before the scheduled time. Sorry for your inconveniences. -Keisuke Keisuke Fukui wrote:

I made a mistake to reserve the bridge. Stand by to fix the problem... Keisuke Fukui wrote:

...

Folks,

Here is an agenda for the call tomorrow. See you there!

### Proposed Agenda 1. Agenda bashing, role call, note taker & time keeper. (5 min) 2. File upload and retrieval in the interaction with CDDLM. (10 min) Please comment to my post on this. 3. August face-to-face dates. (5 min) Candidate from the GGF14 session: Dates: 1st week of the August Place: RTP in N.C 4. Draft writing schedule by face-to-face. (10 min) Review the table of contents, plan to include outcomes of the sessions. 5. Updates (10 min) Review the issues list. Updates on security, etc, if any.. 6. Wrap up, Next meeting(5 min)

### Logistics for the call Date & Time: Jul 6 Mon 20:00 EDT/Jul 7 Tue 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111

-Keisuke

Folks, Here is an agenda for the call tomorrow. See you there! ### Proposed Agenda 1. Agenda bashing, role call, note taker & time keeper. (5 min) 2. August face-to-face dates. (5 min) Candidate from the GGF14 session: Dates: Aug. 1, 2 Place: RTP in N.C 3. Tentative Glossary definition. (5 min) Attached is a version of the final glossary we discussed, with some clean ups. Please check the attached glossary if it is ok as a tentative glossary to start with. 4. Create or Register. (10 min) Is it better to have Create in stead of Register? There will be two create: Creating an AA file at clients site with IDE and creating an AA entry in the repository. We need clarify these. Creation of WS resource doesn't need to be "Create"; Creating a subscription to the events is called "Subscribe". If we use "Create", probably the Destroy will be better choice for "Remove" in the current doc. 5. Roles in ACS for the draft spec. description. (10 min) See my previous post on this. 6. Data transport in GetContents. (10 min) No response from Steve. (To be reconfirmed). Protocol option mechanism may be applied to register. For the register, in case of http is used, should we allow both http server hosted by ACS and http server outside of the ACS? For the former case, register *response* should include uri. For the latter case, register *request* should take the uri to the server. 7. Updates (10 min) Versioning Extensions to WebDAV. Is this one with generic purpose or WebDAV specific? If any.. 8. Wrap up, Next meeting(5 min) ### Logistics for the call Date & Time: Jul 13 Wed 20:00 EDT/Jul 14 Thu 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111 -Keisuke

Here are my updates: (See attached file: d2Glossarytws.doc) 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@us.ibm.com "The optimist sees opportunity in every danger; the pessimist sees danger in every opportunity." Winston Churchill, Sir (1874-1965) Keisuke Fukui <kfukui@labs.fuji tsu.com> To Sent by: Keisuke Fukui owner-acs-wg@ggf. <kfukui@labs.fujitsu.com> org cc acs-wg@ggf.org Subject 07/13/2005 08:09 Re: [acs-wg] Agenda for the Call on PM Jul 13 Wed 20:00 EDT/Jul 14 Thu 9:00 JST Sorry. I'm forgot attaching. -Keisuke Keisuke Fukui wrote:

3. Tentative Glossary definition. (5 min) Attached is a version of the final glossary we discussed, with some clean ups. Please check the attached glossary if it is ok as a tentative glossary to start with. [attachment "d2Glossary.doc" deleted by Thomas Studwell/Raleigh/IBM]

Folks, Here is an agenda for the call tomorrow. See you there! ### Proposed Agenda 1. Role call, note taker & time keeper, agenda bashing. (5 min) 2. Review of the "proposed schedule for the spec. writing." (10 min) Please refer to the previous post titled as above. 3. Continued discussion of use case for archive creation (20 min) Clarify the real issues behind the two use cases and find what is the decision making factor. 4. Updates (10 min) Meeting with NAREGI PSE (by KF). They will implement their own version control and won't rely on the ACS on version control and they simply register and remove the archive rather than keep updating. Also, the signature is not required on AA in their use case. Though they are planning their own meta data repository because they believe most will be their use case specific, I requested to let us examine if we can incorporate items in a manner that ACS doesn't interpret the meaning, but can keep it as a part of the AAD. If any.. 5. Wrap up, Next meeting(5 min) Total: 50 min ### Logistics for the call Date & Time: Jul 27 Wed 20:00 EDT/Jul 28 Thu 9:00 JST Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 7771111 -Keisuke