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=35919#action_35919 ] 

Paul Lipton  commented on TOSCA-12:
-----------------------------------

From meeting of 14 November: see minutes for further details/context. 

[13:06] Krishna Raman (Scribe - Red Hat): Discussing TOSCA normative types proposals.

[13:10] Paul Lipton (co-chair) WebEx: From 31 October meeting on slide 23 relationship type: 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.

[13:13] Paul Lipton (co-chair) WebEx: sorry, I didn't see you Derek. Hang on

[13:21] Paul Lipton (co-chair) WebEx: @Krishna - can you try to capture the basic points. Speakers (Dale/Derek) could you please help in the chat?

[13:24] Paul Lipton (co-chair) WebEx: From Derek (partial): common use case to set up and tear down nodes all the time (like in JuJu)
In practice, the kind of connectivity, e.g., 1-1, 1-many, etc. needs to be modeled. The actual protocols are better done with generic properties. You dont want an explosion of types.

[13:24] Paul Lipton (co-chair) WebEx: I don't have Dale's comments/questions. Dale, please help.


[13:25] Derek Palma (Vnomic)1: I recommend making relationship/connections life-cycles as close to node life-cycles as possible.

[13:26] Derek Palma (Vnomic)1: The TC should decide if it wants to support dynamic connection setup/teardown as part of the "typical" lifecycles.

[13:26] Derek Palma (Vnomic)1: as a standard use case


[13:27] Paul Lipton (co-chair) WebEx: Dale (please fill in and correct): Consider SDNs. A lot of complexity related to preconditions in a network. It doesn't follow the cable anymore. We may need to decide scope -- how much will TOSCA facilitate networks, bridges, etc.? This is a discussion happening in open source groups.

[13:32] Paul Lipton (co-chair) WebEx: NOTE: We will leave the chat open for final statements and corrections for exactly 5 minutes after adjournment of the TC.

[13:33] Dale Moberg (Axway): Dale wants the declarative boundary on Connections sharpened up.

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