Teleconference minutes - July 13
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-20050713/en/1 Sachiko ====================================================================== ACS Teleconference ----------------------------------------------------------------------- Date and Time: July 13 20:00-21:30 EDT 2005 / July 14 9:00-10:30 JST, 2005 Participants: Keisuke Fukui (Fujitsu) Tom Studwell (IBM) Peter Ziu (Northrop) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ------------------------------------------------------------------------ * August face-to-face dates. Agreed F2F meeting plan: Dates: Aug. 1, 2 Place: RTP in N.C Keisuke, Pete, Mike, Keisuke and Sachiko will attend. Tom has kindly accepted hosting the meeting. Teleconference equipment, projector and power supply are available. * Tentative Glossary definition. The refined glossary Keisuke sent has approved. * Create or Register. Discussion on "Create or Register" issue didn't reach conclusion. This issue seems not just a naming matter but concern with the usage scenario of AA creation. Tom and Keisuke will send a picture of their own model to ml, then continue work on deepening our understandings on mailing list. Action: Tom, Keisuke, to send a picture of their own model. * Roles in ACS for the draft spec. description. Keisuke suggested to make the description for the Replicator to be a note rather than a separate role. Finally we agreed to keep Replicator remained in the introductory part of Working Draft because Replicator may have specific capabilities rather than Consumer/Producer, especially related to security. Action: Keisuke, to send skeleton of the latest Working Draft merging the agreed glossary and ARI part for more discussion. * Data transport in GetContents. - Interaction with CDDLM We will wait for their feedback. - Register interface The issue is "in case of http is used, should we allow both http server hosted by ACS and http server outside of the ACS?" Discussion was postponed due to time restriction. * Versioning Extensions to WebDAV Kisuke's question: Isn't this specific to WebDAV? Although its capability seems to meet some of the ACS requirements, it may not applicable to ACS since we won't stick to the WebDAV protocol. Action: All, to keep an eye on this. * Next call Date: Jul 20 Wed 20:00 EDT/Jul 21 Thu 9:00 JST Calling #: will be announced later
Folks, I attach two slides in response to the below "Action" for my part. Sachiko Wada wrote in "[acs-wg] Teleconference minutes - July 13":
* Create or Register. Discussion on "Create or Register" issue didn't reach conclusion. This issue seems not just a naming matter but concern with the usage scenario of AA creation. Tom and Keisuke will send a picture of their own model to ml, then continue work on deepening our understandings on mailing list. Action: Tom, Keisuke, to send a picture of their own model.
I retouched the diagram we discussed at the last GGF14 to depict the use case I have in mind as in (1) or (2) in the first slide. The description in the strawman spec. seen "4. Example Usage" corresponds to the view, though it now needs to be modified to convey more precise image for this. I believe that one of the main theme in ACS is to ease the submission and the following management of the application related files, (3) deviates a bit from our initial purpose. -Keisuke
Here is my perspective on the use cases. (See attached file: AA_CreateUseCases.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@us.ibm.com "The optimist sees opportunity in every danger; the pessimist sees danger in every opportunity." Winston Churchill, Sir (1874-1965) Keisuke Fukui <kfukui@labs.fuji tsu.com> To Sent by: acs-wg@ggf.org owner-acs-wg@ggf. cc org Subject [acs-wg] An AA creation use case 07/19/2005 02:54 AM Folks, I attach two slides in response to the below "Action" for my part. Sachiko Wada wrote in "[acs-wg] Teleconference minutes - July 13":
* Create or Register. Discussion on "Create or Register" issue didn't reach conclusion. This issue seems not just a naming matter but concern with the usage scenario of AA creation. Tom and Keisuke will send a picture of their own model to ml, then continue work on deepening our understandings on mailing list. Action: Tom, Keisuke, to send a picture of their own model.
I retouched the diagram we discussed at the last GGF14 to depict the use case I have in mind as in (1) or (2) in the first slide. The description in the strawman spec. seen "4. Example Usage" corresponds to the view, though it now needs to be modified to convey more precise image for this. I believe that one of the main theme in ACS is to ease the submission and the following management of the application related files, (3) deviates a bit from our initial purpose. -Keisuke [attachment "Who_creates_AA.ppt" deleted by Thomas Studwell/Raleigh/IBM]
Folks, Today we gone through a good amount of discussion in the call on this. I'm comfortable with trying to find a better placement of the things in this way. I also appreciate Pete's time check today:-) I think it's valuable for us to brainstorm this so that we can have a logically correct, feasible and adoptable specification for our purpose. Having said that, I'd like to clarify the real point of the discussion: At first I thought it is a matter of whether register() or create(), then it turned out that it is the use case where the archive is created. Now it again becomes ambiguous to me what is the real matter behind the two different definitions for AA (or AA file). I'd like to ask everyone which of the below is the real issue we are facing: - Name for the things to be registered; i.e. AA file in my diagram, or Archive description and Application contents file(s) (includes DD) in Tom's one. If this is an issue, I can be so much flexible about how we can call it (them). - A physical format of the archive; a zip is described in the strawman. If this is an issue, we can focus on this topics. However, it is not mentioned as this so far. - Partial update of the archive in the repository (It seems to me a separate issue that can be discussed independently.) - Assuming IDE products to be bound to ACS specification (IMHO, it's desirable, but the decision remains up to the vendors.) - Or anything else? FYI, when I say we will standardize transport format of AA, it is to me means to define: - An XML schema of the Archive Descriptor (AD). - At least one physical format of the archive that contains everything needed either in real entity or in external reference. - Required piece of information (or file), optional one and extension mechanisms in an archive besides the AD. Is it a wrong assumption? Please be open to discussion. I'm trying to be fair in the process. I'm just struggling for the best way to address to everyones points. I appreciate any contributions to improve our concept. Thanks in advance! -Keisuke
participants (3)
-
Keisuke Fukui -
Sachiko Wada -
Thomas Studwell