Zane Bitter <> wrote on 10/16/2013 08:25:38 AM:

> To answer your question, the key thing that Heat does is take in two 
> declarative models and generate a workflow to transform one into the 
> other. (The general case of this is a stack update, where the two models 

> are defined in the previous and new templates. Stack create and delete 
> are special cases where one or the other of the models is empty.)
> Workflows don't belong in HOT because they are a one-off thing. You need 

> a different one for every situation, and this is exactly why Heat exists 

> - to infer the correct workflow to reify a model in any given situation.

Thanks for a great short sharp answer.  In that light, I see a concern. 
Once a workflow has been generated, the system has lost the ability to 
adapt to changes in either model.  In a highly concurrent and dynamic 
environment, that could be problematic.

OpenStack-dev mailing list

Reply via email to