[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (TOSCA-12) Set of Basic Node Types for Defining Topology Templates
[ http://tools.oasis-open.org/issues/browse/TOSCA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35902#action_35902 ]
Dale Moberg commented on TOSCA-12:
----------------------------------
Version .5 of the Types draft discusses Relationship types on slides 22 to 26. Under the ConnectsTo remarks (25), known subclaases are introduced
Known Subclasses
IPEndpointRequreiment, HTTPEndpointRequirement, IPEndpointCapability, HTTPEndpointCapability
Subclassing appears to be with respect to the ValidSource, ValidTarget components of the RootRelationshipType. (The Relationship types are Tuple containers of sorts.)
The discussion of what subclass means for specializations needs elaboration. In particular, the types that carry the burden of specializing seem to be part of Requirement and Capatability Type hierarchies that are not discussed as a Normative type system. So the Normative Node Types needs to be connected with Normative XXX Types, where XXX ranges over Relationshiptypes, Requirement types, capability types, and perhaps others (Artifact??) As noted in discussion, this is an incompleteness or scope confusion as of draft .5.
> Set of Basic Node Types for Defining Topology Templates
> -------------------------------------------------------
>
> Key: TOSCA-12
> URL: http://tools.oasis-open.org/issues/browse/TOSCA-12
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Task
> Components: Primer , Spec
> Affects Versions: V1.1_CSD01
> Reporter: Frank Leymann
> Assignee: Derek Palma
> Fix For: V1.1_CSD01
>
>
> TOSCA provides a metamodel that allows users to specify their service templates. For this purpose, Node Types must be defined that are referenced from Node Templates of a Topology Template. It is expected that some particular Node Types will occur frequently (like a "DBMS" Node Type, an "OperatingSystem" Node Type etc). Providing a corresponding set of Node Types by the TOSCA TC will limit the burden of using TOSCA for specifying particular service templates. This in turn will increase the likelihood for broad acceptance of TOSCA in the industry.
> The issue at hand is to agree on a set of such basic Node Types and specify them using the TOSCA language. The corresponding specification should be an additional deliverable of the TOSCA TC. The set of basic Node Types should be "small", i.e. no attempt should be made to specify all Node Types needed to define most cloud applications. Instead, Node Types should be specified that are required by "typical" cloud applications today.
--
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]