[OASIS Issue Tracker] Commented: (CAMP-145) AssemblyTemplate not very useful

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Alex Heneveld commented on CAMP-145:
------------------------------------

I see two potential improvements:

(1) drop the AT 

(2) replace the AT with server-side DP's (deployment plans)

Re (2), which I really like, the server keeps DP's available -- typically based on the DP's supplied by the user, but referencing ACT's (artifacts) and PCT's (services) registered in the platform.  IOW they are the fleshed out detailed blueprints in response to the user's proposed deployment plans.

This could then even form the basis of a negotiation, e.g. to change something in the fleshed-out DP (eg swap out mysql for postgresql) the user just posts a tweaked variant of the server-side DP, referencing the same artifacts etc as the original DP.

> AssemblyTemplate not very useful
> --------------------------------
>
>                 Key: CAMP-145
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-145
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Task
>          Components: Spec
>            Reporter: Alex Heneveld
>
> The AT is not a very usable format.  I have no clear way to modify it, and it is awkward relating it back to the DP which often generated it.
> Also it is not strictly necessary.  Posting a DP could go straight to an Assembly.  Is it worth keeping?
> It has some useful information, essentially telling the user what assemblies can be created, and what the piece parts are, but on the whole I don't think it pulls its weight, in its current guise.

-- 
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