aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Norris (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-167) thtt
Date Sun, 09 Feb 2014 03:05:19 GMT

     [ https://issues.apache.org/jira/browse/AURORA-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dan Norris updated AURORA-167:
------------------------------

    Summary: thtt  (was: Add on_success and on_failure Constraints to Thermos)

> thtt
> ----
>
>                 Key: AURORA-167
>                 URL: https://issues.apache.org/jira/browse/AURORA-167
>             Project: Aurora
>          Issue Type: Task
>          Components: Thermos
>            Reporter: brian wickman
>            Priority: Trivial
>              Labels: newbie
>
> Currently there is one supported constraint in Thermos: 'order' or if you think of it
another way, "on_finish".
> Constraint(order = ['A', 'B']) means that 'B' should run after 'A' has completed, regardless
of its terminal state.  In a way, this could be translated to Constraint(on_success = ['A',
'B'], on_failure = ['A', 'B'])
> But there shouldn't be anything preventing somebody from doing Constraint(on_success
= ['A', 'B'], on_failure = ['A', 'C']).  E.g. maybe process 'B' sends an e-mail that a deploy
was successful, and process 'C' starts a rollback process.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message