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-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=35800#action_35800 ] 

Paul Lipton  commented on TOSCA-12:

Principle comments from TC meeting of 31 Oct 2013 [one more coming from Dale later]. Apologies if any skipped. See TC minutes for more complete information and conversation (1):

* Karsten Beins (Fujitsu): Upon Karsten's question Richard confirmed that the proposed compositeNode types target the modelling of abstract layers (e.g. IaaS, PaaS, App) and thereby support the concept of composition, which can ease fundamentally the job of model development, and can also help us to avoid an inflationary definition of normative node types.

* Simon Moser (co-chair)1: Question: rootRelationshipTypes only the "creation" lifecycle phase, but not on the *descrution* or other lifecycle phases?
Juergen Meynert (scribe Fujitsu): Proposed Abstract Interfaces so far are valid for deployment.

* Paul Lipton (co-chair) conference: POSSIBLE CONSIDERATION/ACTION: Paul suggested that RootRelationshipType (slide 23) may require complementary interfaces for ending the relationship, e.g., preUnConfigure, Unconfigure, postUnConfigure sort of interfaces.
Paul Lipton (co-chair) conference: Richard seemed to think this was worthy of further consideration.

* Juergen Meynert (scribe Fujitsu): Root Relationship Types (HostedOn, DependsOn, ConnectsTo) sufficient or subtypes required?

* Juergen Meynert (scribe Fujitsu): Dale asks whether capability types might be required. Richard replied, that the model might be incomplete in some way.

(1) minutes at: https://www.oasis-open.org/committees/download.php/51252/TOSCA_TC_Minutes_2012-10-31.docx 

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