On 09/01/15 01:07, Angus Salkeld wrote:
I am not in favor of the --continue as an API. I'd suggest responding to resource timeouts and if there is no response from the task, then re-start (continue) the task.
Yeah, I am not in favour of a new API either. In fact, I believe we already have this functionality: if you do another update with the same template and parameters then it will break the lock and continue the update if the engine running the previous update has failed. And when we switch over to convergence it will still do the Right Thing without any extra implementation effort.
There is one improvement we can make to the API though: in Juno, Ton added a PATCH method to stack update such that you can reuse the existing parameters without specifying them again. We should extend this to the template also, so you wouldn't have to supply any data to get Heat to start another update with the same template and parameters.
I'm not sure if there is a blueprint for this already; co-ordinate with Ton if you are planning to work on it.
cheers, Zane. _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
