← Prev in month ← Prev in thread
Next in thread → Next in month →

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

From
OASIS Issues Tracker <>
Date
2014-12-02T14:54:18+00:00
ID
Thread
[OASIS Issue Tracker] (TOSCA-179) DEFER - Add "timeout" and "retry" keynames to an operation
[ https://issues.oasis-open.org/browse/TOSCA-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52571#comment-52571 ] 

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

TOSCA TC approved deferment of this issue at the 2014-11-20 meeting.  See https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/54595/TOSCA%20Minutes%202014-11-20.docx

> DEFER - 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)
← Prev in month ← Prev in thread
Next in thread → Next in month →