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=36279#action_36279 ] 

Paul Lipton  commented on TOSCA-12:

Document posted by Dale covering preliminary use case and discussion related to "connects to" and other items as part of response to his action recorded at: https://www.oasis-open.org/apps/org/workgroup/tosca/members/action_item.php?action_item_id=3667. 

TITLE: Hybrid Cloud App Consumer of External Services

DESCRIPTION: Variations on the SugarCRM model to capture a user story where an on-premise identity provider database is to be consulted as part of the app authentication/authorization process. Specialization of the normative base relationship type of "connects to" is illustrated in some tosca topology diagrams. Use of requirements and capabilities, properties, and other Tosca features may be useful in capturing some aspects of desired connectivity for hybrid cloud configuration issues.

See document at: https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/51869

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