OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

Frank Leymann  commented on TOSCA-179:

I do have a series of questions on this.

1. What should be done in case the retry threshold is reached? 
E.g. should deployment of the overall service template continue in case there are no dependencies on the failed node template? Or should the deployment of the overall service template be considered to be failed? 

2. What is the operational semantics of an operation that did not return within the timeout period?
E.g. the operation may have completed successfully its processing but returning itself failed, i.e. by restarting the operation the result may have an unexpected outcome (non-idempotent operations).

3. What does failing of deployment of a service template mean?
E.g. should the node templates that got already successfully deployed be automatically undeployed/decommissioned? If this is not done payments for the already created node instances may apply.

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]