[OASIS Issue Tracker] (TOSCA-179) 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=42855#comment-42855 ] 

Paul Lipton  edited comment on TOSCA-179 at 8/21/14 3:30 AM:
-------------------------------------------------------------

Presented to the TC on 7 August. Matt asked: "Matt asks Moshe - how could the state of the resource be guaranteed - who is responsible for achieving the state in case of retry, who will clean the resources if something fails?" (from chat)

Also from chat: 
[13:30] David Edery (Scribe - ALU): Moshe answers that in case of failure the whole operation could be aborted. State remains the same until the operation is executed successfully. On a time consuming operation the state will stay the same until the operation is finished. Same goes for retry.
[13:31] David Edery (Scribe - ALU): Matt raises his concern that if the script is executed only part way - artifacts are left and the operator needs to clean the artifacts. There should be strict rules for the operator for all cases.



was (Author: lippa02):
Presented to the TC on 7 August. Matt asked: "Matt asks Moshe - how could the state of the resource be guaranteed - who is responsible for achieving the state in case of retry, who will clean the resources if something fails?" (from chat)

Also from chat: 
[13:30] David Edery (Scribe - ALU): Moshe answers that in case of failure the whole operation could be aborted. State remains the same until the operation is executed successfully. On a time consuming operation the state will stay the same until the operation is finished. Same goes for retry.
[13:31] David Edery (Scribe - ALU): Matt raises his concern that if the script is executed only part way - artifacts are left and the operator needs to clean the artifacts. There should be strict rules for the operator for all cases.
[13:32] David Edery (Scribe - ALU): Paul makes a motion to adjourn the meeting
[13:32] David Edery (Scribe - ALU): The meeting is adjourned informally


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