- acs-wg - lists.ogf.org

ACS use cases for SDD TC
by Keisuke Fukui 09 Aug '05

09 Aug '05

Folks, I am supposed to send the ACS requirements (use cases) for SDD TC by the day after tomorrow. If there are additional comments or modifications, please have them discussed here. Sachiko Wada wrote: > > * 9:25 Review of the ACS requirements use case for SDD TC > Material: cb_d3ACSreqsForSDDinput.doc > With one refinement of the sentence from Tom, the requirements are > approved. > The documents can be found here: https://forge.gridforum.org/projects/acs-wg/document/cb_d3ACSreqsForSDDinpu… I will remove the modification history before posting. Thanks in advance! -Keisuke

1 0

Re: [ogsa-d-wg] [acs-wg] Data Use Case Scenarios document
by Michael Behrens 09 Aug '05

09 Aug '05

Albiet a bit late, I just read the use-case document - looks good. With regard to replication, it seems that the ACS-WG might need to consider that portion so I'm also CC'ing this to the ACS team. I presume the use-case is available from the OGSA-D-WG site. Thanks! Stephen Davey wrote: >Hi everyone, >Attached is the beginnings of a list of Data Use Case Scenarios, which >also includes the template sub-sections for each use case described. > >I have basically taken the original OGSA use case template and merged >the "Use Case Situation Analysis" section into the "Summary" section 2.1 >and renamed section 2.4 slightly. I have also deleted sections 2.5 & 2.6 >since security and performance considerations will be part of the Data >Architecture document and would probably have just led to repetition. >This then leaves the sections: >2.1 Summary >2.2 Scenarios >2.3 Involved Resources >2.4 Functional Design >2.5 References > >Hopefully these sections will be all that is needed for the Data >(infrastructure) Use Cases that we have. >Any comments can be discussed on Wednesday 15th June. > >Cheers, >Stephen. > >------------------------------------------------------------------- >Stephen Davey, NextGrid Software Architect, >National e-Science Centre, >15 South College St., Edinburgh, EH8 9AA, UK >Tel: +44 131 6 509820 > > > > -- -- Michael Behrens R2AD, LLC Cell: 571-594-3008 ___________________________________________________________ $0 Web Hosting with up to 200MB web space, 1000 MB Transfer 10 Personalized POP and Web E-mail Accounts, and much more. Signup at www.doteasy.com

2 1

OGSA F2F
by Michael Behrens 06 Aug '05

06 Aug '05

Attached is the proposed brief for the OGSA F2F. I'm not sure if this would be on the CDDLM agenda yet, however it would be good to share regardless. -- Michael Behrens R2AD, LLC (571) 594-3008 (cell) *new* (703) 714-0442 (land)

3 4

f2f minutes
by Sachiko Wada 05 Aug '05

05 Aug '05

Hi team, Here is the minutes of the Aug F2F day 2. Please review it and point out where the record is not correct, if any. We already reviewed the minutes of day 1. I added the name of materials that are now on the GridForge. Thanks Keisuke! The minutes are also available at Gridforge: https://forge.gridforum.org/projects/acs-wg/document/minutes-20050801-f2f.t… (day 1) https://forge.gridforum.org/projects/acs-wg/document/minutes-20050802-f2f.t… (day 2) Sachiko ======================================================================= ACS F2F DAY 2 ----------------------------------------------------------------------- Date and Time: Aug 2 9:10-16:30 EDT 2005 Location: IBM, Durham RTP. Participants: Keisuke Fukui (Fujitsu) Peter Ziu (Northrop) Thomas Studwell (IBM) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ----------------------------------------------------------------------- * 9:10 Role call, note taker, time keeper, agenda bashing. * 9:20 Review of the minutes Minutes approved. * 9:25 Review of the ACS requirements use case for SDD TC Material: cb_d3ACSreqsForSDDinput.doc With one refinement of the sentence from Tom, the requirements are approved. * 9:30 Review of the OGSA F2F slides Material: ACSoverview-OGSA-F2F-Aug05-draft.ppt We reviewed the OGSA presentation material which Mike posted on Aug 2nd. Action: Sachiko, to send the original file of the CDDLM sequence file to Mike. Done on Aug 3. Action: Mike, to send updated presentation material to the ml. Done on Aug 4. * 9:50 What is AAF? Agreed: AAF is a specification which defines the format of AA Document. AA Document logically consists of two elements: AAD and AC. AAD is always required but AC can be empty, in case the empty archive is to be created. AC consists of DD and other artifacts. * 10:50 break * 11:10 Asynchronous Messaging Agreed to allow asynchronous message exchange in case of the use case C that we discussed yesterday below and transfer. C) Create using soap message but with out of band transport for a (part of) the AA document and the uri is provided by the ACS (the ACS client acts as a file server). If we can drop the transfer from the interface and the above, we may ommit the asynchronous interface. On the other hand OASIS ASAP call for asynchronous interface to be provided for certain type of the interfaces, which may applies to ACS. Need more consideration. * 11:40 OGSA document status review by Pete We read through the OGSA Basic Profile. Agreed to keep eyes on OGSA Basic Profile, WS-I and other standards so that ACS won't violate them. * 11:45 Lunch * 13:00 What's AAF (continued) ** IUPF spec Tom explained briefly about IUPF specification which defines physical format of IU package. This spec was submitted to W3C along with IUDD spec. ACS may be able to refer it as physical format for AA. Whether SDD covers IUPF is not sure but Sun proposed SDD should. ** Relationship between AAD and SDD We recognized that there is some common information between AAD and SDD, for example, list of application contents. As for identification, Tom mentioned that the identification for AA and the IU identification are different. We need more discussion on what the AA identification is. We agreed that AAD should not define isolated spec but should extend SDD. We will put a requirement on SDD to make an extension point in their spec. Tom mentioned that the extension point for AAD will be made in IUPF. Keisuke pointed that the schedule since SDD spec will still be under discussion in October when we plan to finish our draft. ** What AAD contains. To realize ARI capability, AAD should contain such kind of information as identification, owner information, file list, and access control of each content. The detailed was not discussed due to time constraint. We will continue the discussion on the ML and telecons. * 14:50 break * 15:10 AA Replication The replication use case proposed by Pete and Mike was recognized as an effective usage scenario of ACS. To what extent ACS should define as normative spec concerning replication and synchronization was the argument point. - One time copy and no synchronization. - One way synchronization. - Two way synchronization. Keisuke said that the third party can take care of the synchronization, for example, management between geographically distributed application contents. There was a discussion the replication (including a one time copy, modification propagation and bi-directional synchronization) should ever to be a part of the part of ACS spec. Keisuke proposed simplest scope for version one for this to be out of scope. We will revisit this in the ML and telecons. There is an OREP-WG, to define the replication mechanism but they seems to be dormant. Sachiko will post some replication sequences to the ml so that we can clarify which properties and operations are needed (or not needed) to achieve the replication capability. Action: Sachiko, to send sequence diagrams as an input for further discussion by next call. * 16:25 Wrap up for day 2 The following topics were not discussed due to time restriction. They are to be discussed at the regular call. - AA Modification - AA Deletion - Version Management The detailed schedule for the spec writing will also be discussed after the all remained topics are cleared.

1 0

NAREGI PSE overview
by Keisuke Fukui (on the road) 03 Aug '05

03 Aug '05

Folks, Here is the overview diagram of the latest relationship between NAREGI PSE and ACS. Although I got the acknowledgment to show you this in prior to the F2F this time, I couldn't introduce this today due to the time constraint. I can give a brief explanation at the next telecon if requested. -Keisuke

1 0

Aug2005F2F materials and minutes
by Keisuke Fukui (on the road) 03 Aug '05

03 Aug '05

Folks, Thanks for a good productive and active discussion today. I feel happy we got so much progress from more than 14 hours. I appreciate all your geneous and contributions given by attendants. Aug2005F2F materials and minutes are stored in the ACS-WG project page under the category: Root Category Meeting Materials and Minutes Aug2005F2F materials and minutes The above category can be reached at: https://forge.gridforum.org/docman2/ViewCategory.php?group_id=147&category_… -Keisuke

1 0

AA Create Use Cases V3.0
by Thomas Studwell 02 Aug '05

02 Aug '05

(See attached file: AA_CreateUseCasesV3.0.ppt) 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 "Things should be made as simple as possible, but not any simpler." Albert Einstein (1879-1955)

1 0

ACS use case description for SDD TC
by Keisuke Fukui (on the road) 02 Aug '05

02 Aug '05

Folks, Attached is the proposed ACS use case description we reviewed today. Please point if there is any update needed. Color code switched as the green: yes, yellow: possibly. Change history removed. -Keisuke

3 2

Proposed timetable for tomorrow and minutes for today.
by Keisuke Fukui (on the road) 02 Aug '05

02 Aug '05

Folks at the F2F, Attached is the proposed time table for tomorrow and minutes for today. We will start tomorrow's discussion with the review of the minutes. -Keisuke ======================================================================= ACS F2F DAY 1 ----------------------------------------------------------------------- Date and Time: Aug 1 9:00-18:30 EDT 2005 Location: IBM, Durham RTP. Participants: Keisuke Fukui (Fujitsu) Peter Ziu (Northrop) Thomas Studwell (IBM) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ----------------------------------------------------------------------- * 9:15 Agenda bashing, role call, note taker & time keeper. * 9:30 AA Creation use case Material: (from Tom) There are two representations of AA: AA on the wire and AA in the repository. Both are logically equivalent. We agreed to call the former as AA Document and the latter as AA Instance. To create an AA Instance, the client sends an AA Document and optional administrative information to the repository. The administrative information is used to add or overwrite information in the AA Document. * 10:45 break * 11:00 AA Creation use case (continued) We discussed five scenarios. Z) Non-ACS IDE, which doesn't know about AA Document, sends administrative information and a collection of Application Content files to the repository in order to create a new AA Instance. 1) ACS IDE, which knows about AA Document, sends an AA Document and optional administrative information to the repository in order to create the corresponding AA Instance. 2) The client uploads files to the portal service, then the service sends an AA Document and optional administrative information on behalf of the client to the repository in order to create the corresponding AA Instance. This scenario is exactly the same as scenario 1 from ARI view. 3) The client uploads files to the repository in order to add or update Application Contents in an existing AA Instance. This is a scenario of AA Updating. 4) The repository (ACS service) sends an AA Document and optional administrative information to another repository to replicate the AA. This is a scenario of AA Replication. We agreed to drop off scenario Z. We agreed to call the operation for scenario 1 and 2 as "Create" instead of "Register". The detailed message exchange format for AA creation (scenario 1 and 2), AA Updating (scenario 3) and AA Replication (scenario 4) will be discussed tomorrow. * 11:45 Lunch * 13:20 Data Transport Material: (from Keisuke and Sachiko) ** Baseline discussion We agreed that ACS (ARI) exposes a list of supported protocols as resource properties. ** Discussion on slide 3: We discussed six scenarios for Create and GetContents operations. A) Create using SwA. B) Create using soap message but with out of band transport for a (part of) the AA document and the uri is provided by the ACS (the ACS acts as a file server). C) Create using soap message but with out of band transport for a (part of) the AA document and the uri is provided by the ACS (the ACS client acts as a file server). D) GetContents using SwA. E) GetContents using soap message but with out of band transport for the AA contents and the uri is provided by the ACS (the ACS acts as a file server). F) GetContents using soap message but with out of band transport for the AA contents and the uri is provided by the ACS client (the ACS client acts as a file server). We agreed that A and D should be supported by default. B: Pros - Client needs not prepare storage. Cons - Message exchange becomes complicated. (At least 3 stages are required to complete transaction) 'Put' is difficult in respect of access control. C: Pros - ACS can select whether ACS stores actual files or references. Message exchange is simple. On-demand expansion of the storage can be explored easier. Cons - The client needs prepare storage. E: Pros - Client needs not prepare storage. This is what we discussed with CDDLM-WG at GGF14. Cons - Message exchange becomes complicated. It may need 3 stages. F: Pros - The operation can be done in 1 stage. Cons - 'Put' is difficult in respect of access control. How do ACS put multiple contents? ** Conclusion Which pattern ACS supports is: Required - A, D Optional - B, C, E(recommended) Not supported - F * 15:10 break * 15:25 Security and signature on ACS Material: (prepared by Sachiko) Keisuke explained the material. We agreed that ACS may not specify what the other standards including OGSA basic profile cover as for the ARI, since they should be treated common to all OGSA services. We need to clarify to what extent OGSA and other standards specify, especially concerning with authorization. Mike will get comments from the OGSA AuthZ co-chair. Action: Mike to report the feedback of the OGSA meeting next Wednesday (US EDT). * 16:30 OGSA F2F presentation The presentation is for EMS team and other OGSA people who may not know much about ACS. The presentation should take less than 10 - 15 minutes. We review the proposed material in the regular teleconference next week. Action: Pete to make the draft presentation by coming Friday. * 17:00 break * 17:15 ACS use case for SDD TC and update ** Updates SDD TC is now collecting use cases and as an input to the TC. Those are available from the TC WWW site. Sun and IBM had already posted their use cases. ACS and CDDLM are requested to input grid related use cases. ** ACS use case Extracted requirements which are relevant to SDD from current ACS requirements. Action: Keisuke to send the ACS requirements document with highlits on those that may apply to the SDD (green: yes, yellow: possibly) to the ml. Action; All to review it and send comments if any. * 18:00 Warp up for day 1

1 0

Directions to IBM meeting site for ACS Face to Face
by Thomas Studwell 02 Aug '05

02 Aug '05

I apologize for not sending this sooner. Two docs. One showing detail map of IBM site in RTP. We are meeting building 675. The second doc shows the route to take from the RDU Airport to IBM Building 675. The Clarion is just south of I40 on Miami Blvd so is less than a mile from the IBM site. Actually JUST past the overpass on the western side of Miami. I think you need to head South, find a place to turn around, and then head North to IBM site but it will be obvious once you are there. (See attached file: from_ RDU airport to_ 4401 Silicon Dr Durham.pdf)(See attached file: sitemap.pdf) 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 "Things should be made as simple as possible, but not any simpler." Albert Einstein (1879-1955)

3 2