[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=36724#action_36724 ] 

Matthew Rutkowski  commented on TOSCA-142:
------------------------------------------

In relation to runtime types, I already noted that "Feature" may be the way to go... and then perhaps model features as exports from artifact types.  it should be noted that we have 3 choices:

1.	 In interop, at one point, we modeled PHP as a "node"
2.	 Should it be a node or artifact type with features?
3.	 Can we represent these things as just Features?  


> 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