[ http://tools.oasis-open.org/issues/browse/TOSCA-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30918#action_30918 ]
Doug Davis commented on TOSCA-41:
----------------------------------
on 8/9 conf call, Derek propsed adding a tagging feature and the tc agreed to that general
direction. Concrete proposal coming soon.
> Service Template versioning
> ---------------------------
>
> Key: TOSCA-41
> URL: http://tools.oasis-open.org/issues/browse/TOSCA-41
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Sub-task
> Components: Spec
> Reporter: Derek Palma
>
> Service Template versioning. More specifically, model instance versioning (versus the entities being represented by the model). This kind of versioning treats a Service Template as a single unit (or entity instance) for which we may want to attach a version attribute. The version attribute would imply nothing more than some chronologic ordering in some version domain. Note that it possible to version at a finer granularity such as the Node/Relationship Templates or even versioning sub groups of these as a version set (I am not implying we should do this). The key idea is that we are implying that version n+1 was created based on a copy of version n and we assume this is important information to use to discriminate lineage and compatibility, i.e. that a user or software component may want to select by version.
--
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
