[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-21) Clarify whether App Developers/Admins can assume what the Assembly Template tree looks like until post-deploy
[ http://tools.oasis-open.org/issues/browse/CAMP-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32771#action_32771 ]
Adrian Otto commented on CAMP-21:
---------------------------------
I have been putting together a set of slides to discuss this.
In general, the point of the discussionc omes down to whether the PDP is:
1) for using as a detailed deployment plan (imperative template), or
2) a less specific model description (declarative teplate).
In case #1, the answer to the question about making assumptions about what post-deploy looks like could be "yes".
In case #2, the answer is most certainly "no".
Case #1 is non-portable, while case #2 is. Should we pick one answer, or should we describe the two scenarios, and the merits of each?
> Clarify whether App Developers/Admins can assume what the Assembly Template tree looks like until post-deploy
> -------------------------------------------------------------------------------------------------------------
>
> Key: CAMP-21
> URL: http://tools.oasis-open.org/issues/browse/CAMP-21
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Improvement
> Components: Spec
> Reporter: Anish Karmarkar
> Assignee: Gilbert Pilz
> Priority: Critical
>
> The resources described by CAMP (e.g. Assembly Template, Application Component Template) represent (among other things) points of management control. Different providers may support different levels of management granularity. For, example, consider the Tomcat sample application. This application is made up of a single WAR file (sample.war) that contains a static HTML file (index.html), a JSP file (hello.jsp), and a servlet class (Hello.class).
> One provider could choose to model this application as an Assembly Template with a single Application Component Template consisting of the sample.war file. Another provider could choose to model the application with multiple Application Component Templates - one for the static, index.html file and one for the Servlet/JSP files (hello.jsp and Hello.class). It depends on the level of management granularity implemented by the provider.
> Unless they have out-of-band knowledge of their target platform, App Developers/Admins can't assume anything about the structure of the post-deploy Assembly Template tree other than the fact that one app => one Assembly Template. Any assumptions they do make about this structure may constrain the portability of their app to other platforms.
> [This issue was raised by Gilbert Pilz and was drupal issue # 1092
--
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]