[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=35164#action_35164 ] 

Anish Karmarkar commented on CAMP-145:
--------------------------------------

Our resource model was developed a while ago and we ignored the PDP and DP, which for a long time was TBD.
Now we do have a DP. We need to ensure that our DP and resource model are closely aligned (if not the same).
With the DP we'll have developers and tools that are going to manipulate the DP model and be familiar with it. If our resource model was aligned with the DP that would be ideal. If devs/admins have to do the same customization in provider-independent PDPs (via DPs) and provider-dependent resource model then it is a win. To that end what makes sense to me is to expose the same DP via our resource model, or better yet make the DP associated with the AT a resource in itself. This means after deployment if an admin was to customize, they deal with the DP as a resource. If the dev wants to muck with the PDP they deal with DP (as a file). Same model, same concepts, same tools, same skills used to deal with predeployment provider-independent portable PDP and provider dependent AT (or whatever we end up calling it).


> 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