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

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

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


Subject: [OASIS Issue Tracker] Commented: (TOSCA-22) TOSCA Versioning


    [ http://tools.oasis-open.org/issues/browse/TOSCA-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30842#action_30842 ] 

Tobias Kunze  commented on TOSCA-22:
------------------------------------

@Frank: my suggestion would be to do exactly what all the RPM or Deb-based Linux distributions do: have a name part (e.g. a URL) and a version part. The version part can be any string (e.g. "5.3a:20120525:svn23489") although it will be in most cases a typical version number, e.g. "1.4.5". Sorting on version numbers is roughly performed roughly by treating all punctuation and letter/digit transitions as fields and then sorting left-to-right, digits numerically and letters case-insensitively alphabetically. This allows ServiceTemplate authors to make "weird" version numbers from upstream, enclosed software transparent.

For changes in the ServiceTemplate itself, e.g. your case of SugarCRM based on MySQL vs DB2, this would be probably best expressed with a separate name part, e.g. http://vendor.com/service-template/sugarcrm-mysql and http://vendor.com/service-template/sugarcrm-db2.

Again, Linux distros have had an accumulated experience of about probably 50+ years in solving this problem.


> TOSCA Versioning
> ----------------
>
>                 Key: TOSCA-22
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-22
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Paul Lipton 
>            Assignee: Tobias Kunze 
>
> Originally sub-issue 7 in TOSCA-20, called "NodeTypes should have a "Version" field ," no consensus was made on this at the 6/7/12 meeting. This lack of consensus was probably the result of unclear scope. Reconsidering on 6/14, the TC has decided that the scope of the versioning issue is greater than this, e.g., do we mean of model / version of entities / etc., and requests Tobias, as original proposer of the "seed issue" in TOSCA-20, to take ownership of this issue. 
> See minutes from both these meetings. Others are invited to contribute/comment, of course. 

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

        


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