<html><body>
<p><tt><font size="2">Georgy Okrokvertskhov <gokrokvertskhov@mirantis.com> wrote on 10/09/2013 03:37:01 PM:<br>
<br>
> From: Georgy Okrokvertskhov <gokrokvertskhov@mirantis.com></font></tt><br>
<tt><font size="2">> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org></font></tt><br>
<tt><font size="2">> Date: 10/09/2013 03:41 PM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] [Heat] HOT Software orchestration <br>
> proposal for workflows</font></tt><br>
<tt><font size="2">> <br>
</font></tt><br>
<tt><font size="2">> Thank you for bringing your use case and your thought here. That is <br>
> exactly tried to achieve in Murano project. </font></tt><br>
<tt><font size="2">> There are important aspects you highlighted. Sometime resource <br>
> model is two high level to describe deployment process. If you start<br>
> to use more granular approach to have defined steps of deployment <br>
> you will finish with workflow approach where you have fine control <br>
> of deployment process but description will be quite complex. </font></tt><br>
<br>
<tt><font size="2">IMHO workflow approaches tend to be heavy-weight. So, I am hoping</font></tt><br>
<tt><font size="2">for more light-weight data-flow constructs and mechanisms that</font></tt><br>
<tt><font size="2">can help with the coordination scenarios I have outlined. Data-flow</font></tt><br>
<tt><font size="2">constructs and mechanisms have had lots of success in other domains,</font></tt><br>
<tt><font size="2">and I wondering why can't we (the Heat community) leverage the related</font></tt><br>
<tt><font size="2">theory and tools!</font></tt><br>
<br>
<tt><font size="2">Thanks,</font></tt><br>
<tt><font size="2">LN</font></tt><br>
<br>
<br>
</body></html>