[OASIS Issue Tracker] Created: (TOSCA-107) Use Case: Handling errors on Operations during (and post) deployment (i.e. an Error Model)

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

Use Case: Handling errors on Operations during (and post) deployment (i.e. an Error Model)
------------------------------------------------------------------------------------------

                 Key: TOSCA-107
                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-107
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Task
          Components: Interop
         Environment: Use case for development against TOSCA-v1.0-cs01.
            Reporter: Matthew Rutkowski 
            Assignee: Derek Palma


Is there an error model? What information is available regarding the execution results of a plan? What is the final representation of the complete deployment?

Example:
TBD

Notes:
Matt: Many thoughts here to break out...
Derek: need std. set of errors (semantics) if operation fails (imp or decl). Perhaps a best practice. If scripting how can you write a generic script for any TOSCA engine.

Reference:
https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48514/ConsiderationsFor2TierWebApplications.docx

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