[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=35167#action_35167 ] 

Gilbert Pilz commented on CAMP-145:
-----------------------------------

The interesting scenario here is:

1.) Consumer (Developer or Developer Admin) deploys PDP or DP onto platform.

2.) Platform is unable to resolve one or more of the requirements in the DP. This could be because the platform does not recognize/support the requirementType or it cannot satisfy some aspect of the requirement (e.g. "I don't offer a database with that much cache")

If the mismatch in (2) is "profound" (e.g. the Consumer needs a message queue that supports AQMP and the Provider does not offer any such services) then this isn't a very interesting scenario. However if the mismatch is "close" we have choice as to how we allow the Consumer to fix it. Either we make them undeploy their app (assuming the app was left deployed after (2)), edit the DP, re-package the PDP (if they are using the DP-within-a-PDP mechanism), and re-deploy or we allow them to edit the DP in-place. "Editing the DP in-place" would be strange and inconsistent if we used some mechanism other than HTTP PUT or HTTP PATCH - right?

The TC needs to decide if this scenario is important enough to warrant supporting in the spec. My sense is that, because CAMP is shooting for broad support across many different PaaS implementations, this scenario is important.

> 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