OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [camp] [OASIS Issue Tracker] Updated: (CAMP-30) Parameter Scheme


I'm not sure I completely understand this proposal.

From previous discussion, my understanding (which could be incorrect) was that templates will be allowed to list which attributes of an instance can be specified in the POST that creates that instance.

But I see the same technique being used to register the PDP, where the PDP URL is a parameter. The PDP URL, although a "parameter" for the POST is *not* an attribute of any resource. Not sure which attribute metadata URL you would point to for this.

-Anish
--

On 02/22/2013 04:45 PM, OASIS Issues Tracker wrote:

      [ http://tools.oasis-open.org/issues/browse/CAMP-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Otto updated CAMP-30:
----------------------------

     Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/48366/camp-30-2013-02-22.doc  (was: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/48135/camp-30-2013-02-04.doc)

Revised proposal. Trimmed examples of Maps, and integrated proposal with the proposal for CAMP-50.

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
            Priority: Critical

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.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]