I can't agree more. My point was not using it for v1, but just make sure
everoybody in the team is aware of that kind of transactional framework.
On a second pro, it would make sense to conceptualize transaction model
and think on a move later, even if we're still yet not using it :-)
Taskflow ppl, do you have any kind of code freeze deadline which could
give us a glance on when the first release will be ready for use ?
Thanks,
-Sylvain
Le 22/09/2013 09:39, Dina Belova a écrit :
Hi all,
I think that TaskFlow is an interesting initiative that could provide
us some benefits like good encapsulation of logical code blocks,
better exception handling and management of actions taking place in
Climate core, rollbacks and replays management.
It looks like that we should initially understand our workflows in
Climate and then decide if we should use TaskFlow for them or not.
On Thu, Sep 19, 2013 at 4:54 PM, Sylvain Bauza <sylvain.ba...@bull.net
<mailto:sylvain.ba...@bull.net>> wrote:
Hi Climate team,
I just went through https://wiki.openstack.org/wiki/TaskFlow
Do you think Taskflow could help us in providing ressources
defined in the lease on an atomic way ?
We could leave the implementation up to the plugins, but maybe the
Lease Manager could also benefit of it.
-Sylvain
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Best regards,
Dina Belova
Software Engineer
Mirantis Inc.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
