[OASIS Issue Tracker] Commented: (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>]

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

Frank Leymann  commented on TOSCA-107:
--------------------------------------

The operations that plans invoke define faults as part of their signature. When the execution of an operation fails, a corresponding fault is returned and thrown in the plan. Plan languages like BPMN or BPEL allow to catch these faults and react accordingly (e.g. following alternative paths; kick-off compensation processing etc).  Non-operation related faults can be send to a plan and received their; the flow of actions once such a fault is received is modelled in the plan. 

The result of the execution of a plan can be returned as a "result message". Also, a process engine maintains an execution log which can be accessed at any point in time to get aware about what happend. 

> 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