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

[Fwd: Re: [cddlm] In preparation for the CDDLM/ACS joint session at GGF14 (re-send)]
by Keisuke Fukui 19 Jul '05

19 Jul '05

FYI, -------- Original Message -------- Subject: Re: [cddlm] In preparation for the CDDLM/ACS joint session at GGF14 (re-send) Date: Mon, 18 Jul 2005 13:17:18 +0100 From: Steve Loughran <steve_loughran(a)hpl.hp.com> To: Keisuke Fukui <kfukui(a)labs.fujitsu.com> CC: 'cddlm-wg(a)ggf.org' <cddlm-wg(a)ggf.org> References: <42B92AB0.3080802(a)labs.fujitsu.com> <42B94FBC.70406(a)hpl.hp.com> <42BB559D.6020600(a)labs.fujitsu.com> <42BBD923.1010509(a)hpl.hp.com> <42BC935C.4090501(a)labs.fujitsu.com> <42C92E87.6090508(a)hpl.hp.com> <42D1D6EF.5010108(a)labs.fujitsu.com> Keisuke Fukui wrote: > Steve, > > # Let me re-send this since I forget the attachment:-) > > Thanks for your update on this. > > Considering your comments below, we discussed a WS interface utilizing > the uri identification as you proposed. Please take a look at the > attachment > to this e-mail. This depicts how the ACS Repository Interface > "GetContents()" > can work with multiple protocols. It is very similar with the AddFile() > as it > returns an uri. In our interface, Register() that pushes files into the > repository > returns EPR to the entry, then the GetContents() with protocol and keys > to the > subpart of the archive entry selects what and how the files can be > retrieved > from the repository. It will allow the http to be used among the other > protocols > supported by the implementation of the repository. > > Do you think this work for your use case? > > -Keisuke > > slide1. Yes, this should work. I like the listing of supported protocols, it eliminates much uncertainty. slid2: the use case should show that the http request is being made by a separate application (not the client), which GETs the URL that is extracted from the GetContents response message and then handed to the application. This emphasises that an application at a different location (and with no cookie history, a different IP address,...) will be doing the retrieval. slide3: The contents of the fetch would include a message which contains an identifier/uri to the actual attachment. Otherwise the app is assuming that only one attachment comes in a message, which is not always the case. MTOM is the future of soap attachments, even if support today is patchy-to-nonexistent. Its operation should look similar, except that the data will appear by the time it comes through the soap stack to be an inline base64 element of very large size (and presumably different copy/clone semantics or the implementation will leak files the way axis1.x does) I'd recommend a response message that can take either a uri or inline data, so the same request/response can work for the different types. 4. Caching/performance. If the URL-fetching app is written with the assumption that the repository is some distance away, or intermittently unreachable, it will want to download the resource and cache it. So an HTTP HEAD request may be needed, or a GET with a lastModifiedSince (or better yet, an etag). -steve

1 0

Skelton for wg draft of ACS spec.
by Keisuke Fukui 15 Jul '05

15 Jul '05

Folks, I'm attaching the skelton for wg draft of ACS Spec. as we discussed in the call. It follows the table of contents that we discussed at May face-to-face meeting with the requirements and glossary we reviewed at meetings. Introduction description is migrated as they are from the strawman. We will also incorporate the introductory description that Tom proposed in the GGF14 session and Role description. Then we will proceed to incorporate other portions once after they got reviewed in the group. Please take a look of it and verify we can start with it. Thanks, -Keisuke

1 0

Teleconference minutes - July 6
by Sachiko Wada 13 Jul '05

13 Jul '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. It is also available at Gridforge: https://forge.gridforum.org/projects/acs-wg/document/minutes-20050706/en/1 Sachiko ====================================================================== ACS Teleconference ----------------------------------------------------------------------- Date and Time: July 6 20:15-21:30 EDT 2005 / July 7 9:15-10:30 JST, 2005 Participants: Keisuke Fukui (Fujitsu) Tom Studwell (IBM) Peter Ziu (Northrop) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ------------------------------------------------------------------------ * File upload and retrieval in the interaction with CDDLM. Keisuke's proposal for the data transport was discussed and the overall idea was accepted. ACS may specify which protocol is required. SwA is the candidate. After the refined diagram approved, Keisuke will send it to the CDDLM ml by next Monday. * August face-to-face dates. Place: RTP in N.C Date: August 1-2 is first candidate. * Draft writing schedule by face-to-face. Agreed to focus on the ARI first. Action: Keisuke, to post the skeleton of the latest working draft reflecting TOC refinement at the May F2F. * Issues list update closed #1523 "Demonstrate the recommended interface between ACS and CDDLM" closed #1536 "Refine the glossary description" Comment: WebDav have capabilities involving the version control. Keep an eye on it w.r.t. #1522. * CDDLM and EMS telconf They decided to have a session in OGSA F2F end of August. At this moment we are not requested to be the session. * Next call Date: Jul 13 Wed 20:00 EDT/Jul 14 Thu 9:00 JST Calling #: will be announced later

4 6

FW: FW: [acs-wg] scrm-pvt - first draft of Landscape Information doc for ACS
by Ziu, Peter 12 Jul '05

12 Jul '05

Hiro, Attached is ACS's landscape contribution to SCRM. Pete -----Original Message----- From: owner-acs-wg(a)ggf.org [mailto:owner-acs-wg@ggf.org]On Behalf Of pete(a)ziu.net Sent: Monday, July 11, 2005 9:18 PM To: Keisuke Fukui Cc: acs-wg(a)ggf.org Subject: Re: FW: [acs-wg] scrm-pvt - first draft of Landscape Information doc for ACS Keisuke, Thank you very much for the valuable comments. I will encorporate them and resend the updated doc for Wed. Pete Ziu 571.235.0208 (c) mailto:pete@ziu.net (h) mailto:5712350208@tmomail.net (sms) To "Ziu, Peter" <peter.ziu(a)ngc.com> cc acs-wg(a)ggf.org bcc Subject Re: FW: [acs-wg] scrm-pvt - first draft of Landscape Information doc for ACS Keisuke Fukui <kfukui(a)labs.fujitsu.com> Sent by: owner-acs-wg(a)ggf.org 07/12/2005 09:25 AM ZE9 <font size=-1></font> Hi Pete, Thanks for compilation of the information. It is fine for the most part. Item 9: English. Item 15, 16: GGF, I guess. However, for the URI for the rules, the admin of the scrm will find the most appropriate URI. So let's leave them as blank. Or "(GGF)" looks better? Item 18: Not sure if we can fill here with planned but not yet visible implementation. I guess this corresponds to the adoption columns standard status table we saw at the GGF14 scrm meeting. So I think "NAREGI project and Business Grid project has plans" would be a fair description. Item 19: We are not referring CDDLM *normatively*, but will just demonstrate or introduce the capability to interact with CDDLM. For the Solution Installation, we will eventually refer it in some way, but not yet. So I think "We are expecting that OASIS SDD is referred normatively." would be a fair description. Item 20: Yes. Let's fill here with "OGSA v1" These are the all comments from me. I don't have any issues on all others you filled. My apologies to my late response. -Keisuke Ziu, Peter wrote: > Does anyone have any comments/corrections on/to this document before it > goes to Hiro? (see attached) If we could get a review of this document > on the agenda for next meeting (or just comments in email) it would be > greatly appreciated. > > Pete. > > -----Original Message----- > *From:* owner-acs-wg(a)ggf.org [ mailto:owner-acs-wg@ggf.org]*On Behalf Of > *pete(a)ziu.net > *Sent:* Thursday, July 07, 2005 7:16 PM > *To:* kfukui(a)labs.fujitsu.com > *Cc:* acs-wg(a)ggf.org > *Subject:* [acs-wg] scrm-pvt - first draft of Landscape Information doc > for ACS > > Keisuke and group, > > I have been requested by Hiro to submit the SCRM draft Landscape > Information doc for ACS specification to him, so that he may pass it up > to SCRM. This is an informational document about all specs of interest > within SCRM, to help sort out the numerous efforts in the management > space. I have updated the form I originally sent to you to the latest > draft version. I have inserted comments since it is in need of review. I > would like to make sure I am properly reflecting ACS facts. Tom, might > you find time to review as well (especially the check box things[Ziu, Peter] ) ? Do you > think we might be able to review next meeting? > > Pete Ziu > 571.235.0208 (c) > mailto:pete@ziu.net (h) > mailto:5712350208@tmomail.net (sms) >

1 0

Roles in ACS
by Keisuke Fukui 12 Jul '05

12 Jul '05

Folks, As for the roles description, I agree that the proposed definitions contributes to the better understanding of the ACS for those who read the document. Especially Producer and Consumer are what are missed in the previous draft. So I'd like to include them in the chapter 3 Architecture in the specification. My proposal here is to make the description for the Replicator to be a note rather than a separate role. It can be placed as, for example (please brush up my English here if you can): -------------------------------------------------------------------------------- Note: The entity that acts as both the consumer and the producer can provide combined feature of those, for example, replicating and recreating an archive for modified use for other task and/or by another client. They can also register the archive to another instance of ACS. -------------------------------------------------------------------------------- In my mind, the replicator is a special case for the producer and the consumer. It doesn't act as the central part of the ACS use cases, either. The above fits better to that view and contributes to the better understanding for those who read the specification. Any comments? -Keisuke -------------------------------------------------------------------------------- 1.1.1 Roles ACS identifies three broad categories of roles of users of the ARI. Note that these roles are used purely for the purposes of describing the ARI. These roles are not explicitly identified or enforced by ARI. The roles are: •Producer – owner of an application that is to be archived into ACS. This role supports create, update, and delete operations on an AA. •Consumer – users of ARI that want to retrieve information about an AA or retrieve portions of an AA. This role only supports Get operations. •Replicator – a special version of Consumer that enables getting a formatted version of the complete AA for the purposes of recreating the AA in another instance of ACS. --------------------------------------------------------------------------------

1 0

FW: [acs-wg] scrm-pvt - first draft of Landscape Information doc for ACS
by Ziu, Peter 12 Jul '05

12 Jul '05

Does anyone have any comments/corrections on/to this document before it goes to Hiro? (see attached) If we could get a review of this document on the agenda for next meeting (or just comments in email) it would be greatly appreciated. Pete. -----Original Message----- From: owner-acs-wg(a)ggf.org [mailto:owner-acs-wg@ggf.org]On Behalf Of pete(a)ziu.net Sent: Thursday, July 07, 2005 7:16 PM To: kfukui(a)labs.fujitsu.com Cc: acs-wg(a)ggf.org Subject: [acs-wg] scrm-pvt - first draft of Landscape Information doc for ACS Keisuke and group, I have been requested by Hiro to submit the SCRM draft Landscape Information doc for ACS specification to him, so that he may pass it up to SCRM. This is an informational document about all specs of interest within SCRM, to help sort out the numerous efforts in the management space. I have updated the form I originally sent to you to the latest draft version. I have inserted comments since it is in need of review. I would like to make sure I am properly reflecting ACS facts. Tom, might you find time to review as well (especially the check box things? Do you think we might be able to review next meeting? Pete Ziu 571.235.0208 (c) mailto:pete@ziu.net (h) mailto:5712350208@tmomail.net (sms)

3 3

Re: FW: [acs-wg] scrm-pvt - first draft of Landscape Information doc for ACS
by pete＠ziu.net 12 Jul '05

12 Jul '05

Keisuke, Thank you very much for the valuable comments. I will encorporate them and resend the updated doc for Wed. Pete Ziu 571.235.0208 (c) mailto:pete@ziu.net (h) mailto:5712350208@tmomail.net (sms) To "Ziu, Peter" <peter.ziu(a)ngc.com> cc acs-wg(a)ggf.org bcc Subject Re: FW: [acs-wg] scrm-pvt - first draft of Landscape Information doc for ACS Keisuke Fukui <kfukui(a)labs.fujitsu.com> Sent by: owner-acs-wg(a)ggf.org 07/12/2005 09:25 AM ZE9 <font size=-1></font> Hi Pete, Thanks for compilation of the information. It is fine for the most part. Item 9: English. Item 15, 16: GGF, I guess. However, for the URI for the rules, the admin of the scrm will find the most appropriate URI. So let's leave them as blank. Or "(GGF)" looks better? Item 18: Not sure if we can fill here with planned but not yet visible implementation. I guess this corresponds to the adoption columns standard status table we saw at the GGF14 scrm meeting. So I think "NAREGI project and Business Grid project has plans" would be a fair description. Item 19: We are not referring CDDLM *normatively*, but will just demonstrate or introduce the capability to interact with CDDLM. For the Solution Installation, we will eventually refer it in some way, but not yet. So I think "We are expecting that OASIS SDD is referred normatively." would be a fair description. Item 20: Yes. Let's fill here with "OGSA v1" These are the all comments from me. I don't have any issues on all others you filled. My apologies to my late response. -Keisuke Ziu, Peter wrote: > Does anyone have any comments/corrections on/to this document before it > goes to Hiro? (see attached) If we could get a review of this document > on the agenda for next meeting (or just comments in email) it would be > greatly appreciated. > > Pete. > > -----Original Message----- > *From:* owner-acs-wg(a)ggf.org [mailto:owner-acs-wg@ggf.org]*On Behalf Of > *pete(a)ziu.net > *Sent:* Thursday, July 07, 2005 7:16 PM > *To:* kfukui(a)labs.fujitsu.com > *Cc:* acs-wg(a)ggf.org > *Subject:* [acs-wg] scrm-pvt - first draft of Landscape Information doc > for ACS > > Keisuke and group, > > I have been requested by Hiro to submit the SCRM draft Landscape > Information doc for ACS specification to him, so that he may pass it up > to SCRM. This is an informational document about all specs of interest > within SCRM, to help sort out the numerous efforts in the management > space. I have updated the form I originally sent to you to the latest > draft version. I have inserted comments since it is in need of review. I > would like to make sure I am properly reflecting ACS facts. Tom, might > you find time to review as well (especially the check box things? Do you > think we might be able to review next meeting? > > Pete Ziu > 571.235.0208 (c) > mailto:pete@ziu.net (h) > mailto:5712350208@tmomail.net (sms) >

1 0

[Fwd: Re: [cddlm] In preparation for the CDDLM/ACS joint session at GGF14]
by Keisuke Fukui 11 Jul '05

11 Jul '05

FYI, As we discussed at the call last week, I have sent the multiprotocol specification for GetContents to cddlm-wg and Steve. Let's see what happen. -Keisuke

1 0

GGF14 minutes
by Sachiko Wada 11 Jul '05

11 Jul '05

Folks, Here are the minutes of the ACS sessions at GGF14. Please review them and address your comments, if any. They are also available at GridForge: https://forge.gridforum.org/projects/acs-wg/document/ggf14_minutes_session-… https://forge.gridforum.org/projects/acs-wg/document/ggf14_minutes_session-… Sachiko ====================================================================== GGF14 ACS Session #1 (CDDLM and ACS joint session) ----------------------------------------------------------------------- Date and Time: June 28 14:30-16:00 CDT 2005 Lead: Keisuke Fukui (Fujitsu) Notes: Sachiko Wada (Ascade) ------------------------------------------------------------------------ * 14:30 Agenda bashing * 14:40 Short Overview of ACS Material:"Overview of ACS" from GGF13 Meeting Materials Keisuke explained briefly about the ACS concepts and service behavior. There are some questions from CDDLM team. Q. What is the Application Archive(AA)? A. AA contains an Archive Descriptor and Application Contents such as application binary and configuration data. AA also contains a Deployment Descriptor. Q. Why is the repository required. A. Storing the application contents in the repository (ACS) inside the Grid System prior to deployment phase is useful to ensure secure and efficient data transport avoiding firewall problems. Standardization for the repository interface can enable interoperability between heterogeneous Grid Systems. Q. Who will develop the reference implementations. A. Business Grid and NAREGI have the plan. * 15:00 CDDLM and ACS sequence Material:"Sequence for the possible ACS-CDDLM-interaction" Sequence 1: CDDLM standalone case. We answered to the questions from the audience. As a result, it is confirmed that there is no problem in our understanding of the CDDLM service behavior. - AddFile operation returns url which is used to retrieve uploaded files by Component Endpoints. - Purpose of the Deployment API is to create Components that are the actual deployment engines. - How to clean up the System is an issue. - Client must implement the Component Endpoint which has service specific deployment logic. Sequence 2, 3: CDDLM and ACS Collaboration We went through a brainstorming about data transportation and security. There is no objection on the sequence at end. - GetContetns should support multiple contents retrieval. - Steve recommended HTTP to retrieve data. - EPR can utilize WS-Naming capabilities. - Server authentication may sufficient within the Grid System. * 15:50 wrap up ====================================================================== GGF14 ACS Session #2 ----------------------------------------------------------------------- Date and Time: June 30 11:00-12:30 CDT 2005 Lead: Keisuke Fukui (Fujitsu) Notes: Sachiko Wada (Ascade) ------------------------------------------------------------------------ * 11:00 Agenda bashing * 11:05 Relationship to OASIS SDD TC After SDD TC status update from Tom, we discussed the form of the relationship between ACS and SDD. - Agreed to have official liaison with OASIS SDD TC. - SDD includes a notion that can be translated into Application Deployment Descriptor (ADD) which may be contained in Application Archive (AA). - ACS should gather requirements for ADD and provide them to SDD. - There is a schedule mismatch. SDD held a first meeting on 1 June and will continue working on use cases for a couple of months, while ACS plans to write up the final (or at least close to final) draft until next GGF. We'll find how we can fit these each other soon. * 11:18 Glossary definition refinement Material:"d1Glossary" We read through the proposed glossary document. - The glossary was approved as the baseline to continue discussion. * 11:40 Continue work on Repository interface Material:"ACS-ARI" We discussed about the proposed ARI specification. The following comments were made, but we only cover the first few pages during the session. We agreed to continue discussion over the mail and teleconferences, toward the face-to-face (F2F) in August. - Section 1.1 should be move to the introductory part of the draft doc. - Need more discussion on the role "Replicator". This is connected to the "Transfer" operation. Use case approach may be desired on this issue. - Data Transport. We will utilize existing data transport protocol for Register(or Create), GetContents operation. A mechanism for protocol selection is expected. - We have two types of reference for external reference here: A reference to be resolved by ACS and a reference to be resolved by consumer; we should check the contents for the former when the actual file is retrieved (= when a reference is resolved). For the latter, however, we cannot ensure the reference is valid since the it may be changed over the time and we don't know when it is resolved. - We will continue discussions about the interface name; Register or Create. * 12:15 Next step - Agreed to have F2F meeting early in August. - Next regular call is on 6 June. * 12:40 End of session

1 0

scrm-pvt - first draft of Landscape Information doc for ACS
by pete＠ziu.net 07 Jul '05

07 Jul '05

Keisuke and group, I have been requested by Hiro to submit the SCRM draft Landscape Information doc for ACS specification to him, so that he may pass it up to SCRM. This is an informational document about all specs of interest within SCRM, to help sort out the numerous efforts in the management space. I have updated the form I originally sent to you to the latest draft version. I have inserted comments since it is in need of review. I would like to make sure I am properly reflecting ACS facts. Tom, might you find time to review as well (especially the check box things? Do you think we might be able to review next meeting? Pete Ziu 571.235.0208 (c) mailto:pete@ziu.net (h) mailto:5712350208@tmomail.net (sms)

1 0