[OASIS Issue Tracker] (TOSCA-179) CLOSE - Add "timeout" and "retry" keynames to an operation

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

    [ https://issues.oasis-open.org/browse/TOSCA-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59608#comment-59608 ] 

Matthew Rutkowski  commented on TOSCA-179:
------------------------------------------

The TC determined that "timeout" and "retry" declarations would not be considered for the TOSCA model and impinge upon specific implementations.  In addition, consideration of state of the model when a timeout occurs during any operation (and corrective actions) would be beyond the scope of the Simple Profile.

> CLOSE - Add "timeout" and "retry" keynames to an operation
> ----------------------------------------------------------
>
>                 Key: TOSCA-179
>                 URL: https://issues.oasis-open.org/browse/TOSCA-179
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>            Reporter: Moshe Elisha
>            Assignee: Moshe Elisha
>
> 1. Allow the user to define a timeout for a single operation execution. On expiration, the TOSCA container will mark the execution as failed with an indication that the cause was timeout.
> We can choose a default time unit for this value, we can decide of a pattern "20 m" or we can have another keyname "timeout_unit" that will describe it.
> IMHO, I think that seconds is the minimal time unit that will be required and it is a good default.
> 2. Allow the user to define a retry for an operation execution. 
> If an operation fails to execute (exit code != 0 or timeout), the TOSCA container will execute the operation again until reaching the number of retries.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)