[OASIS Issue Tracker] Commented: (TOSCA-12) Set of Basic Node Types for Defining Topology Templates

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

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

Derek Palma commented on TOSCA-12:
----------------------------------

Here is a proposal with the following objectives:

Propose a simple and concise set of "Core" Entities and Relations for TOSCA useful for any application deployment in a cloud

Enable users to easily subclass from Core versus having to invent top level objects

Enable domain experts to easily define their own specialized entities and relations

Assemble application stacks and topologies using relations with strong typing

Enable template validation

Don't try to define entire set of subclasses ever needed. E.g. all operating system types, VM Image types, ... or policy types or deployment artifact types

Apply this to the SugarCRM usecase as a concrete example

Focus on Iaas case now, and represent Paas case next

Defer connectsTo relation


The following documents are available.

Overview slides:
	http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45635/latest

UML diagrams (pdf):
	http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45636/latest

UML diagrams (visio):
http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45637/latest



> 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: Improvement
>          Components: Spec
>            Reporter: Frank Leymann 
>
> 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