[OASIS Issue Tracker] Commented: (TOSCA-20) Spec issues identified in creating Service Template in YAML for More Complicated PHP Use Case.

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

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

Tobias Kunze  commented on TOSCA-20:
------------------------------------

For convenience, here are the original issues (I've completed the missing sentence in issue 4):


1. Node Type components need to be addressable, either via interfaces or in a more structured way. Component role must be understood (e.g. what is PHP, what is ZF)
  - Suggest to introduce "Component" as a technical term, denoting the, well, components of a NodeType. Also, suggest that these components are addressed using period (".") as a separator
2. Some NodeTypes are "abstract", e.g. "my-app". Static files (kind of) become part of *static-server and Code (kind of) becomes part of *zend-server.php
3. "Require"/"Provide" is a much more flexible mechanism than just referencing NodeTypes with "DerivedFrom".
4. The inheritance aspects of the "DerivedFrom" element need to be complemented with a separate, immutable form that occurs when a NodeType is provided by the platform. E.g. if a ServiceTemplate, NodeTemplate, etc. that another ServiceTemplate, NodeTemplate, etc. inherits from is provided by an third party or otherwise has specific constraints, it must be able to mark the relevant fields as immutable
5. When a NodeType is provided, the ability to express requirements (e.g. applying to resource allocation or specific run modes) becomes important
6. The NodeType ID field is superfluous
7. NodeTypes should have a "Version" field
8. NodeTypeProperties need "name", "value", and optionally maybe "type" (verify)
9. Naming and capitalization is odd, e.g. "NodeTypeProperties" vs "requestURI" vs "name"


> Spec issues identified in creating Service Template in YAML for More Complicated PHP Use Case.
> ----------------------------------------------------------------------------------------------
>
>                 Key: TOSCA-20
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-20
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Spec
>    Affects Versions: CSD03
>            Reporter: Paul Lipton 
>            Assignee: Tobias Kunze 
>             Fix For: CSD03
>
>
> These issues identified in document from Tobias. Decisions taken in meeting of 6/7. 

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