OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (CAMP-24) Assembly Template and Assembly trees should be analogous


    [ http://tools.oasis-open.org/issues/browse/CAMP-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31681#action_31681 ] 

Gilbert Pilz commented on CAMP-24:
----------------------------------

I've uploaded a detailed proposal on this issue here: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/47447/CAMP-24-2012-11-12.pdf

This proposal is an attempt to flesh-out the agreement reached at the first face-to-face meeting. My understanding of what we agreed to was that Assemblies (Assembly Templates) should *not* directly reference Platform Components (Platform Templates), etc., but instead should only reference the Application Components (Application Component Templates) that "make up" those Assemblies.

1.) Replaced Figure's 2 and 3 with new figures that more clearly illustrate the agreement (old figures have a thin, solid red line drawn through them). I don't consider these new drawings to be "final", but I think they are a step closer to what we would like the final figures to look like.

2.) Section 5.7, "AssemblyTemplate": Removed the "platformComponentTemplates" and "dependencies" attributes and added the "assemblies" attribute. The "assemblies" attribute is an array of links to all the Assembly instances that have been instantiated from this Assembly Template. I also removed the optionality of the "applicationComponentTemplates" - meaning that you must have at least on Application Component Template in an Assembly Template.

3.) Section 5.8, "ApplicationComponentTemplate": Added "applicationComponentTemplates", "platformComponentTemplates", "applicationComponentRequirements", and "platformComponentRequirements" attributes. One detail we need to decide on is whether or not it is possible for an Application Component to *not* depend on any other Components.

4.) Section 5.14, "Assembly": Removed the "platformComponents" attribute and removed the optionality of the "applicationComponents"  - meaning that you must have at least one Application Component in an Assembly.

5.) Section 5.15, "Application Component": Again, we need to decide if it is possible for an Application Component to exist without any dependencies on Platform Components or other Application Components.

> Assembly Template and Assembly trees should be analogous
> --------------------------------------------------------
>
>                 Key: CAMP-24
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-24
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Anish Karmarkar
>            Assignee: Gilbert Pilz
>
> If you draw out an Assembly Template tree and it's corresponding Assembly tree for a simple application you will notice that the Application Component Templates do not contain any links to the Platform Component Templates or Application Component Templates that they depend upon but the Application Components do contain links to the Platform Components and Application Components. At the very least, this difference needs to be explained in the spec.
> [This issue was raised by Gilbert Pilz and was drupal issue # 1095]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]