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