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:
> I can envision some cases where a DD would not be present, in which case 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)