[OASIS Issue Tracker] Commented: (TOSCA-2) Review Proposal: TOSCA support for simple web application deployment use cases via YAML app manifest

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

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

Dale Moberg commented on TOSCA-2:
---------------------------------

During TC discussions of "canonical" and "alternative" encodings, and how XML instances could fulfill a canonical role with respect to alternative encodings, I raised the following questions: Here let yaml be an alternative encoding, t-instance a canonical "model" as rendered in XML.  It was suggested that a t-instance could be translated into yaml, and in fact possibly translated in multiple ways. 1. What needs to be preserved in such a translation? 2. Would it be necessary to understand yaml equivalence classes with respect to t-instance translations? 3. Would (or should) the group agree on construction rules that would produce a single "representative" yaml instance for a given t-instance, and leave yaml instance equivalence issues to yaml users? 4. Could proponents wishing tof provide a translation, explain what the translation is supposed to preserve and what is "inessential notational differences" between the t-instance and a representative yaml instance that results from doing a translation? In general, I was hoping to get some clarification on what the consensus view on what needs to be done to resolve TOSCA-7. Calling the t-instance canonical did not allow me to understand just what "being canonical" amounted to. 

> Review Proposal: TOSCA support for simple web application deployment use cases via YAML app manifest
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TOSCA-2
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-2
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Spec
>    Affects Versions: WD1
>            Reporter: Diane Mueller
>            Assignee: Diane Mueller
>             Fix For: WD1
>
>
> Proposal: TOSCA support for simple web application deployment use cases via YAML app manifest 
> Before going too deep with creating a interoperable portable framework for supporting complex application deployments on the cloud.  TOSCA should ensure that the simple web applications, those using common web frameworks like spring, play, django, rails, psgi, or node.js, have basic requirements of apache or nginx as web servers,  and need to deploy a mysql, redis, mongodb or other open source databases - are easily supported with whatever approach we decide to take. Many aspects of an application  can be affected by cloud infrastructure that one chooses to install the application on. This process can be made easier and others more difficult depending on the level of complexity involved in specifying the the apps configuration and deployment requirements  - even for the simplest of web applications.

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