Open Stack

Any reason why it couldn't be used from the start? Just not enough time or
to complicated for now?

If its to complicated, I'd like to know what the alternative is that is
less complicated if you have any inputs. I see quite a bit of code moving
around to accomplish the 'moving things' part and it seems like said
moving around could at the same time break it into small pieces (which
seems to make good sense from a coding, structure, design standpoint).
Maybe that¹s to much for a initial move though, thoughts?

On 5/22/13 3:28 AM, "John Garbutt" <john at johngarbutt.com> wrote:

>On 22 May 2013 06:18, Karajgi, Rohit <Rohit.Karajgi at nttdata.com> wrote:
>>> In terms of using TaskFlow, I am just starting to take a look at the
>>>code.
>>
>> So are you planning to use this TaskFlow
>>(https://github.com/yahoo/TaskFlow) library
>> to implement the blueprint or just unify the code paths with conductor?
>
>My plan is to unify the code paths, moving things into the new compute
>api section of the conductor.
>
>Once its there, the code should be in a position where we can look at
>using TaskFlow to help manage running of that task, and using
>workflows to split up the task into smaller pieces.
>
>John
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev