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-9) Environment Dependencies of Plans and Operations

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

Frank Leymann  commented on TOSCA-9:

I am absolutely fine with specifying in TOSCA that BPMN 2.0 is the default language for defining plans.

Wrt "artifacts", we need be more specific.

We define "implementation artifacts" as the "executables" realizing operations. The spec lists potential types of operations, i.e. WSDL port type operations, REST interfaces, and scripts.  WSDL port types are often implemented as servlets but also as EJBs (in addition to corresponding Windows components). Thus, we should add EARs to Derek's list. REST interfaces are often realized as servlets, i.e. from a Java perspective JAR files or WAR files should be fine.  The list of script languages is fine with me, but I need to delegate the list of scripts to others (this is not my skill area). 

We define "deployment artifacts" as the "executables" realizing node types/templates. When a node type/template represents infrastructure, i.e. OS or middleware (DBMS, App Server,...) assuming images is fine. The list of VM image formats to be supported needs to be discussed. Also, we need to include AMIs (or references to them) because of their frequent use. But if we move from infrastructure up towards the implementation, we need to support artifacts that represent service- and process-oriented applications. Thus, the artifact types include WSDL files, BPEL- and BPMN files, EAR/JAR files (implementing the WSDL port types) and so on.

Summary:  The list is an excellent base, but we should consider to extend it in order to reflect applications that are often (expected to be) run in a cloud environment. 

> Environment Dependencies of Plans and Operations
> ------------------------------------------------
>                 Key: TOSCA-9
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-9
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Spec
>    Affects Versions: CSD1
>            Reporter: Frank Leymann 
>            Priority: Minor
> We started a discussion on dependencies of plans on the target environment of cloud services.  This discussion was held in the context of TOSCA Issue 4.  But TOSCA Issue 4 is more focused on fixing a problem with interface definitions.  
> The main purpose of this issue is to discuss conceptual and architectural aspects on environment dependencies of plans and operations, as well as the relation of plans and operations. 

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]