[OASIS Issue Tracker] Commented: (CAMP-30) Parameter Scheme

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

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

Tobias Kunze  commented on CAMP-30:
-----------------------------------

In general I am for such a facility, but it is unclear to me how one would provide values for such "templatized" templates. The difference between a <Type>Template and an <Type> (instance) has been so far that the platform completes the <Type> with runtime information and the way a <Type>Template is instantiated is by transitioning the <Type>Template (or perhaps just its AssemblyTemplate) to the "started" state IIRC. We'd need a separate channel for user values to be added before this happens. Your suggestion

    POST /12342/AssemblyTemplates/1
    [...]

    {name: foo}

strikes me as a PATCH, really.  Also, wouldn't you want to create a copy first? Or perhaps an explicit "instantiate" followed by a PATCH? Just looking for ideas here.


> Parameter Scheme
> ----------------
>
>                 Key: CAMP-30
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-30
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Adrian Otto
>            Assignee: Adrian Otto
>
> Create a well defined template parameter scheme that can be used to express special labels in template resource attributes that are used for supplying values upon instantiating entities using the template. In addition to a template parameter label, we also need a standard mechanism to specify values for the labels when using the API.
> This feature can be used for supplying a unique name to an Application Assembly at the time it is created and started. This would allow multiple Application Assemblies to be created from the same template to run concurrently, and offer a way to easily tell them apart from each other. The scheme should be flexible such that it works for Component Templates as well, so that it can be used for passing in configuration parameters that are employed by a downstream configuration management system.

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