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-105) Use Case: Using "Required Container Feature" to describe Artifact Type requirements


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

Frank Leymann  commented on TOSCA-105:
--------------------------------------

A TOSCA Container needs to support all Artifact Type referred to by the Implementation Artifacts and at least one Deployment Artifacts of a Node Type Implementation (or Relationship Type Implementation, respectively): otherwise, it cannot process the service template and must reject it. Furthermore, the Implementation/Deployment Artifacts may depend on the availability of special features like APIs to get access to libraries, repositories etc - these requirements are expressed as Required Container Features.  A container that does not offer these features cannot process a corresponding service template and must reject it. 

> Use Case: Using "Required Container Feature" to describe Artifact Type requirements
> -----------------------------------------------------------------------------------
>
>                 Key: TOSCA-105
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-105
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Interop
>         Environment: Use case for development against TOSCA-v1.0-cs01.
>            Reporter: Matthew Rutkowski 
>            Assignee: Travis Tripp
>
> How does Required Container Feature interact with Artifact Type?
> given implementation will be based on artifacts of various types and the container must be able to support executing them.  
> Example:
> A node type having 2  NodeTypeImpls: 
> 1) Chef Impl (Needs Chef cookbook support).
> 2) Script Impl (needs script exec. Environment).
> Notes:
> Travis: Node Type Implementations include RequiredContainerFeatures, but this is not used in the examples. As it stands today, it seems to be implying one or all of the following assumptions:
> 1) You have to look at both the artifact types and the required container features to determine if a node type implementation is actually supported.
> 2) There isn't any normative set of required container features.
> Matt: We left off a discussion of this suggesting that artifacts may export reqs/caps (as do node types).
> Matt: 2 scenarios? one for artifact exec. support, one for container (environment) for APIs?
> This JIRA issue is intended to develop the first scenario/use case focusing on Artifact requirements.
> Reference:
> https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48640/ArtifactTypes_RequiredContainerFeatures%20-%20HP.pptx

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