Very helpful, thanks! I have some comments: I can envision some cases where a DD would not be present, in which case the AAD should indicate so. Slide 4: Agree about #3 not being needed. I think the idea of having a tool for the end user (like the portal in #2), is important. I think we will need to support an import/export capability somehow, in addition to transfer. Export/Import Requirement? ---------- Original Message ---------------------------------- From: Sachiko Wada <sachiko@ascade.co.jp> Date: Wed, 29 Jun 2005 21:09:45 +0900
Folks,
I sorted out my considerations about ACS based on the yesterday discussion. I'd like your comments eigher on the ml or at the session. Or if you don't think it makes sence, just ignore this.
Sachiko.
-- Michael Behrens, CTO 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
Mike, Michael Behrens wrote:
Very helpful, thanks! I have some comments:
Yes. Good job, Sachiko. And thanks for your comments, Mike.
I can envision some cases where a DD would not be present, in which case the AAD should indicate so.
Agreed. We need specify how it can be indecated so.
Slide 4: Agree about #3 not being needed. I think the idea of having a tool for the end user (like the portal in #2), is important.
Agreed. #2 can be discussed and/or implemented on top of the ACS spec., and separately from the ACS spec. itself.
I think we will need to support an import/export capability somehow, in addition to transfer.
Export/Import Requirement?
Which are you talking about cloning or external reference thing here? Can't it be realized through current set of the interfaces? -Keisuke
---------- Original Message ---------------------------------- From: Sachiko Wada <sachiko@ascade.co.jp> Date: Wed, 29 Jun 2005 21:09:45 +0900
Folks,
I sorted out my considerations about ACS based on the yesterday discussion. I'd like your comments eigher on the ml or at the session. Or if you don't think it makes sence, just ignore this.
Sachiko.
-- Michael Behrens, CTO 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
I can envision some cases where a DD would not be present, in which case
Good job Sachiko-san. I have some of my own comments and comment to Mike's comment below. Chart 2: [A]DD includes the Lifecycle management procedures. so just add the comment "specifies how to deploy, configure, run, terminate, ..." to point to ADD object. The SDD artifacts are the other objects, eg, Executables, User Data, Configuration. Change this to be ADD rather than DD. Chart 3: AAF defines an XML document for exchanging the complete AA. It is not necessary that AAF be used within any ACS Instance for storing the AA. It is ONLY necessary for transferring a complete AA in and out of ARI. Chart 4: User provides a collection of information and the AC and ADD for a AA they wish to have created. They do not, as a Producer, generate an AA per se, the exception is a case where the user wishes to create a replica but I call this a Replicator function rather than a Producer function (and very important reason that we agree on and keep the roles distinct). We need to develop the type of information that needs to be included in the collection but it has things like Description, Owner, Access Rights, etc. Chart 5: good chart for focusing our conversations on the ARI and AAD. We need to talk more on this. Chart 6: GetContents vs GetArchive need some conversation. Comment about Mike's comment: the AAD should indicate so. [TWS] My comment is that I can not see a case where this would be true. Need some discussion on this. 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) "Michael Behrens" <behrens@r2ad.com > To Sent by: <acs-wg@ggf.org>, Sachiko Wada owner-acs-wg@ggf. <sachiko@ascade.co.jp> org cc Subject 06/29/2005 10:06 Re: [acs-wg] ACS considerations AM Please respond to behrens Very helpful, thanks! I have some comments: I can envision some cases where a DD would not be present, in which case the AAD should indicate so. Slide 4: Agree about #3 not being needed. I think the idea of having a tool for the end user (like the portal in #2), is important. I think we will need to support an import/export capability somehow, in addition to transfer. Export/Import Requirement? ---------- Original Message ---------------------------------- From: Sachiko Wada <sachiko@ascade.co.jp> Date: Wed, 29 Jun 2005 21:09:45 +0900
Folks,
I sorted out my considerations about ACS based on the yesterday discussion. I'd like your comments eigher on the ml or at the session. Or if you don't think it makes sence, just ignore this.
Sachiko.
-- Michael Behrens, CTO 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
Tom, Thanks for your comments. Though we will also cover these and many are understandable, I and Sachiko felt difficulty in understanding your comment below: Thomas Studwell wrote:
Chart 4: User provides a collection of information and the AC and ADD for a AA they wish to have created. They do not, as a Producer, generate an AA per se, the exception is a case where the user wishes to create a replica but I call this a Replicator function rather than a Producer function (and very important reason that we agree on and keep the roles distinct). We need to develop the type of information that needs to be included in the collection but it has things like Description, Owner, Access Rights, etc.
Sachiko pointed me that there may be some discrepancy between us on understanding the use cases here. Does your comment above means (3) is your main use case? FYI, I thought the case (1) would be the bottom line one, then (2) will be realized as a more value added form of the service implementations. In my opinion, (3) is questionable because I don't see points here. I understand that Mike and Sachiko is also doubtful about (3)
Slide 4: Agree about #3 not being needed.
We can discuss more at the next session. -Keisuke
participants (3)
-
Keisuke Fukui (on the road) -
Michael Behrens -
Thomas Studwell