[OASIS Issue Tracker] Commented: (TOSCA-142) WD02 - Define normative Artifact Types (including deployment/packages, impls., and runtime types)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Thomas Spatzier  commented on TOSCA-142:
----------------------------------------

A comment on Node Type Implementations: we recently discussed to leave Node Type Implementation out of the simple profile and cover everything with just Node Types. They now allow for defining implementation and deployment artifacts, so no need for an additional indirection.

Different runtimes can be handled by having different, specialied Node Types. E.g. for a generic MySQL node type, we could have a sub-type MySQL_Linux and another type MySQL_Windows, each with the respective artifacts and scripts. Compared to object oriented programming, a kind of factory will have to select the right concrete sub-type for an abstract super-type.

We still have to figure out how the selection of the right sub-type works (features, requirements etc.)

> WD02 - Define normative Artifact Types (including deployment/packages, impls., and runtime types)
> -------------------------------------------------------------------------------------------------
>
>                 Key: TOSCA-142
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-142
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Profile-YAML
>    Affects Versions: CSD1
>            Reporter: Matthew Rutkowski 
>            Assignee: Thomas Spatzier 
>             Fix For: CSD1
>
>
> A) Runtime Types:  
>     - It has been suggested we have "Software Library" types such: PHP and Java
>     - perhaps these can be "Features" that are expressed as capabilities of WebServers and as Requirements by WebApplication Node Types
> B) Deployment Types:
>      - We know that we need to express RPMs, ZIP an TAR in someway and describe what dependent "provider" tooling is needed on different platforms to accomplish an installation
>   - Thomas commented on "RPM" types the following: "Or should we make this more generic like "OS-Package" that can have a type "rpm", "deb" etc. and then the respective installer gets selected based on package type?"
> C) Implementation Types:
>    - We know we need to describe "Bash" (.sh) scripts.  If so (and OpenStack is a target impl. for TOSCA YAML), we should look at defining (normatively) Chef and Puppet as well.
>   - Thomas commented: "I would make this more generic, e.g. "Script" which can have a script language property to select the interpreter"

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