re we would not have to redo
it again.
--
Kirill Izotov
вторник, 15 апреля 2014 г. в 11:13, Joshua Harlow написал:
> Sure, its not the fully complete lazy_engine, but piece by piece we can get
> there.
>
> Of course code/contributions are welcome, as such things will benefi
l
they are all finished. The whole idea of sub-flows within the scope of direct
conditional transitions is a bit unclear to me (and probably us all) at the
moment, though I'm trying to rely on them only as a means to lesser the
complexity.
[1] https://review.openstack.org/#/c/86470
--
Kir
ectly fine for TaskFlow to evaluate python
conditions rather than implementing YAQL, though there should be a place for us
to pass the condition evaluation logic we are using.
--
Kirill Izotov
вторник, 15 апреля 2014 г. в 8:02, Joshua Harlow написал:
> Can we describe exactly what re
w thus block us from integration and require substantial
changes in TaskFlow engine design. Inability to make such changes will directly
result in Mistral not being able to meet its requirements and thus rendering
the whole project useless for its users
sly, but will be a
part of public API of TaskFlow so we can be sure it would work exactly the same
way it worked yesterday.
--
Kirill Izotov
пятница, 4 апреля 2014 г. в 2:04, Ivan Melnikov написал:
>
> I'm trying to catch up this rather long and interesting discussion,
>
w-and-proposal
What do you think, guys, is this the way to go?
--
Kirill Izotov
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Sure, +1 for both.
--
Kirill Izotov
четверг, 20 марта 2014 г. в 3:52, Dmitri Zimine написал:
> +1 for Nikolay - he's indeed the most involved in all aspect.
> and yes I am up to doing it.
>
> DZ.
>
> On Mar 19, 2014, at 4:35 AM, Renat Akhmerov (mailto:rakhme.
