May 2005 - acs-wg - lists.ogf.org

Next Call
by Sachiko Wada 27 Jul '05

27 Jul '05

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

4 24

Teleconference minutes - 5/18
by Sachiko Wada 03 Jun '05

03 Jun '05

Hi team, Here is the minutes of the teleconf today. 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-20050518/en/1 See you next week! Regards, Sachiko ====================================================================== ACS Teleconference ----------------------------------------------------------------------- Date and Time: May 18 20:00-21:20 EST 2005 / May 19 9:00-10:20 JST, 2005 Participants: Keisuke Fukui (Fujitsu) Peter Ziu (Northrop) Thomas Studwell (IBM) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ------------------------------------------------------------------------ ** Topics 1. Agenda bashing, role call, note taker & time keeper. (10min) 2. Planning for the face-to-face. (30 min) Starting time: - first day: 10:00 a.m. - second day: 8:00 a.m. Details about the facility and how to enter it will be announced later by Pete. Agenda items: -------(start of f2f agenda) >> 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 ... Owner: Tom Time allocation: (45 min) Action: >> 3. ACS issues list overview (1 hour) >> - Itemization >> - Use of the tracker in gridforge. Also to review the requirements description to be merged into the WG draft spec. Owner: Keisuke Time allocation: 1 hour Action: Keisuke will make a draft of issues list by F2F. Everybody, to append missed items if there is any. >> 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. Owner: Keisuke and Sachiko Time allocation: 1 hour Action: Everybody, provide with relevant information. >> 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..) possible topics - access control - signature - on which specificaiton wil ACS depend? - 'safe' ? Owner: Mike Time allocation: 30 min (Mike will post the required time) Action: Mike is asking somebody to join the meeting to discuss about this. >> 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. Owner: Mike Time allocation: 30 min. Action: Everybody, to provide with relevant information. >> 7. New use cases (1 hour) >> - Shipping >> - Federation - Mike will present 15 min slides on his use case. - use cases for supplying to SDD (or talk about this in session 2) Tom will present the existing SDD use cases. - naregi Keisuke asked them to write their use case. NAREGI team cannot attend this session but they will attend first session of 2nd day. Owner: Mike Time allocation: (need more than 1 hour) Action: Keisuke, to get information from NAREGI PSE team in advance. >> >> 8. Interoperability Goal (1 hour) >> - Target systems. >> - Range or scope. other actvities which may have relationship with ACS - EGA - EGEE - OMII Owner: Keisuke Time allocation: Action: Everybody, to provide with relevant information. >> *** 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. NAREGI team will attend over the phone. Owner: Keisuke Time allocation: Action: Keisuke, to arrange a call bridge. >> >> 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. Owner: Keisuke Time allocation: Action: >> 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 - avoid conflicting with CDDLM/WSDM joint session Owner: Keisuke >> 12. Management and/or strategy in the ACS activity. (1 hour) >> - Regular teleconference >> - Recruiting in the European Grid community. Owner: Keisuke >> 13. OGSA roadmap report and SCRM collaboration (1 hour) - expected users - referenced specifications Owner: Mike -------(end of f2f agenda) Keisuke will revise the time table and post it on the acs-wg list. 3. Updates (10 min) no updates 4. Wrap up. (5 min)

3 5

GGF14 Session requests
by Keisuke Fukui 01 Jun '05

01 Jun '05

Folks, I have submitted two session requests as we discussed at the F2F meeting. https://forge.gridforum.org/tracker/?func=detail&atid=557&aid=1482&group_id… https://forge.gridforum.org/tracker/?func=detail&atid=557&aid=1483&group_id… -Keisuke

2 1

TeleConference for this week.
by Keisuke Fukui 31 May '05

31 May '05

Folks, I have reserved a call bridge tentatively on June 2 EDT, as we discussed. 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 If you have a problem, please state here. Agenda will be posted later. (We will review action items list from F2F.) -Keisuke

2 1

Freeconference.com
by Keisuke Fukui 31 May '05

31 May '05

Folks, I'm wondering if we are to use freeconference.com for our teleconferences. I found that the numbers they provided are not toll free in the U.S. (It look like to me and it doesn't make any difference from outside of the U.S.) If you are OK, I can keep using the freeconference.com and will reserve one for this week. -Keisuke

3 3

Register Interface
by Michael Behrens 31 May '05

31 May '05

Thinking about the register interface name, I'd thought of "deposit" the other day when trying to explain it to someone. Did we come to a consensus as to whether or not ACS actually created the Application Archive (AA) with the service invocations or was it accepting it as a parameter? If it is actually creating one, then having the create is still valid, in addition to the other which would be invoked as part of transferring an AA between ACS containers or from a business manager to the ACS. -- Michael Behrens R2AD, LLC (571) 594-3008 (cell) *new* (703) 714-0442 (land)

1 0

Issues List and Action Items from the F2F.
by Keisuke Fukui 30 May '05

30 May '05

Folks, Thank you for participating the F2F meeting. I believe we had a heated discussion to synchronize what we have in mind and gained a good progress toward the GGF14. I also express special appreciations to those who joined over the phone line in late evening to discuss about the NAREGI PSE integration. Attached are the Issues List we reviewed at the end of the meeting and the action items list extracted. I have added one issue at the head of the list and numbered each of the AIs (action items). Everyone please point if there is any to be corrected by the regular call this week. I'm planning to put them in tracker in acs-wg project page, once we have verified. Thanks for your contributions! -Keisuke P.S. I wrote to Dejan of CDDLM about the joint session at GGF14 to discuss about interface between CDDLM and ACS, and got a positive answer to meet together. I will request a session to invite his team. Milojicic, Dejan S wrote: > Hi Keisuke, > > I am fully supportive. Would you like to schedule a session and make > sure to specify that there be no conflict with other CDDLM sessions? > > Thanks, > > Dejan. > Title: Issues on the ACS specification. (Rev. 20050523) 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. AI-2: All, to make comment on the sequence. AI-3: Tom, to propose a name for 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 SDD hierarchy 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 ref. implementation. - Collect use case descriptions to be shown in the spec. conclusion: Current one is suffice. AI-6: All, to review the current one. - 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. - 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. 20050523) Date: May 23, 2005 Created by: Keisuke Fukui >From the "Issues List": AI-1: Sachiko, to post the proposed sequence for interaction. AI-2: All, to make comment on the sequence. AI-3: Tom, to propose a name for interfaces (functions) AI-4: Tom, to send SDD hierarchy to NAREGI PSE team. AI-5: Tom, to ask David Martin about ref. impl. AI-6: All, to review the current one. 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. >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.

1 1

[Fwd: ACS status]
by Keisuke Fukui 25 May '05

25 May '05

FYI,

1 0

Today's conference call number and ID
by Ziu, Peter 24 May '05

24 May '05

Phone: 1.877.602.8687 Conference ID 8952382

1 0

NAREGI PSE material for F2F meeting
by Motohiro YAMADA 24 May '05

24 May '05

Folks, Here is a material for the following agenda. We welcome your questions or comments. Regards, -- Motohiro Yamada >>>>> On Mon, 23 May 2005 09:55:25 +0900, >>>>> kfukui(a)labs.fujitsu.com (Keisuke Fukui) wrote: > > *** DAY 1 (May 23) *** (snip) > 16:45 Review of the NAREGI PSE information. (KF; 30 min) > - Material will be posted on the acs-wg by noon EDT. > - Review the information if there are questions or issues. > - Return comments or questions to PSE team to prepare the call > in the next morning.

2 3