Open Stack

Hey Josh, I’d like to thank you for a very productive discussion that we had at the summit, seems to be a great achievement for us in terms our collaboration and collective vision of both technologies. This was the first time I was able to clearly see how to align our capabilities better and hence provide tremendous usability benefits for the community.

Totally support bi-weekly meetings, let me take this part and figure out the schedule that would work for everyone of us.

Thanks
 
Renat Akhmerov
@ Mirantis Inc.



On 15 May 2014, at 22:30, Joshua Harlow <harlowja at yahoo-inc.com> wrote:

> Looks good to me,
> 
> We had a good 'meetup' in one of the breakout rooms on the second floor
> (those rooms are pretty useful!)
> 
> This does seem like a good step toward making both groups successful and
> from the discussion I think we have a decent vision of how this can/could
> work out in the future and moving forward (and even some other neat ideas
> on related areas were also discovered/discussed, which is pretty cool).
> 
> I'll writeup some more these as TF blueprints next week and we can
> continue there (iterating on them and getting some code
> produced/adjusted/refactored). The timeline maybe we should continue
> thinking about as I'm still sure on the 'final' date but I agree with the
> get started now and we can start to 'approximate' what the date would be
> as we get a better 'feeling' for it (K seems like a good estimate).
> 
> Another idea:
> 
> The bi-weekly meetings between teams/individuals/other on IRC seemed like
> a good idea (to at least sync and discuss ideas and such), maybe we should
> continue those. What do u guys think?
> 
> -----Original Message-----
> From: Dmitri Zimine <dz at stackstorm.com>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev at lists.openstack.org>
> Date: Thursday, May 15, 2014 at 1:06 PM
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev at lists.openstack.org>
> Subject: [openstack-dev] [Mistral][TaskFlow] Integration plan
> 
>> Renat, Joshua, Dmitri and Timur discussed the integration path for
>> Mistral and TaskFlow.
>> Quick summary - guys please correct any mistakes or omissions:
>> 
>> Taskflow - Mistral integration plan
>> 1) Mistral: define the set of workflow primitives, define correspondent
>> DSL
>> 	- Driven by user requirements. Keep to minimal. Implement in Mistral.
>> 2) Taskflow: break out flow scheduler (decision maker) and persistence
>> 	- it'll be a low level "library" interference, Joshua has details
>> 	- once done, ready to re-prototype integration, iterate until happy
>> 3) Move the primitives to TaskFlow (both teams)
>> 
>> 4) Integrate TaskFlow into Mistral (replace Mistral workflow engine with
>> TaskFlow engine)
>> 
>> Once integration complete, Mistral DSL will continue to work, all
>> TaskFlow and Mistral workflows will be interchangeable, the code reused.
>> 
>> DZ. 
>> 
>> PS. When do we do it? We didn't commit to a date,
>> but IMO (DZ) we start now, and with some luck get integrated in K cycle.
>> 
>> 
>> 
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev