20:03:08 #startmeeting taskflow 20:03:09 Meeting started Thu Jul 18 20:03:08 2013 UTC. The chair is jlucci. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:03:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:03:12 The meeting name has been set to 'taskflow' 20:03:22 Yeah - sorry bout that. Just wanted to make sure we had people here first. (: 20:03:50 So, first time running this - not entirely sure where to start here 20:04:07 I guess we can start with stuff that's been going on this past week? 20:04:16 #topic rollcall 20:04:25 role I suppose 20:04:34 haha 20:04:35 I never could spell. 20:04:48 The meeting would be more exciting with bread people anyway. :P 20:06:19 I'm going to go ahead and assume we're the only three here - so let's go ahead and jump into what everyone's been working on 20:06:57 So, I know Kevin had finished up some database persistence stuff - just waiting on a review from harlowja 20:07:51 As for me, I've still been in distributed land. I fixed the issue with celery notifications not firing off correctly (the thing we talked about yesterday kebray) 20:08:20 So, as of now, I'm just fixing up little bugs here and there 20:08:57 Going to write more robust test cases and hopefully be done with that in the very near future 20:09:25 kebray, changbl - any updates? 20:09:49 jlucci You think it'll be ready for others to starting giving it a whirl? e.g. would you want distributed included in a formal build when harlowja makes one? 20:10:03 I have been looking through the code, trying to catch up with you. Tons of work here after Yun Mao left, slow progress here 20:10:24 I want to say yes - but I don't think I have enough test cases yet to assure that it's 100% bug proof 20:10:27 progress: I submitted TaskFlow talk for the summit: #link https://wiki.openstack.org/wiki/TaskFlow/HavanaSummitPresentationAbstract 20:10:29 np changbl 20:10:40 harlowja codes very fast. haha 20:10:48 :) 20:10:59 And awesome kebray! 20:11:30 Good stuff going on there 20:11:46 Oh, and I know Josh submitted another patch for the multi-threaded flow today as well 20:12:56 #topic release date 20:13:10 So the next topic on the agenda was the release of taskflow 20:13:14 Regarding the when/how 20:13:37 I think last time we had sort of settled on doing a release oslo copy-paste style and then moving onto pypi once we had a more stable api 20:14:23 So, as far as I know that's still the plan. As far as an initial release date, does anyone have any strong suggestions? 20:14:43 the plan sounds good 20:15:03 :D 20:15:05 do we plan to integrate taskflow into havana release? 20:15:40 changbl I don't think it's up to us. 20:15:45 It's up to the individual projects. 20:15:54 e.g. Cinder will integrate it as a library dependency. 20:16:02 For their release for Havana. 20:16:04 We definitely want to have a good-candidate release out before havana 3 however 20:16:25 We need at least two openstack projects to take dependencies on TaskFlow before Oslo says they will accept us. 20:17:06 I see, so Cinder is one, is there others? 20:17:38 Yes - harlowja is working on nova 20:17:43 harlowja is working on Nova. 20:17:46 cool 20:17:51 Trove may at some point pull it in.. they are interested. 20:17:56 We have a lot of interest in heat as well, but that probably won't be for a while 20:18:00 they have a lot on their plate right now 20:18:19 i see, thanks for the update:) 20:18:24 And, my goals are to get TaskFlow to where I want it for Heat.. but, Heat integration is definitely not even an option until post Havana. 20:18:55 Yeah, we've gotten some core members to start looking at the project, so that's definitely a good step forward 20:19:17 There are alternatives available today in Heat… which, are currently sufficient… the path to mass scalability is a bit unclear, as are feature richness.. such as pause, retry, resume, revert, etc. for tasks. 20:19:21 TaskFlow solves these problems. 20:19:55 So, I'm hopeful the Heat community will see the value and adopt TaskFlow… but, there is existing code that is evolving in Heat as well, so timing is uncertain of when/if it makes sense to pull in TaskFlow for Heat. 20:21:34 yupyup 20:21:48 Do we have some ultimate goal of taskflow? become part of Heat? or Oslo? 20:22:00 We would eventually like to become part of oslo 20:22:28 Which is why we're initially trying to get cinder to adopt our usage 20:22:46 We need to be in two existent projects to be considered for oslo 20:23:03 Then TaskFlow will become the base library for Convection. 20:23:04 er two existing projects * 20:23:23 #link https://wiki.openstack.org/wiki/Convection 20:23:58 ok 20:25:08 So, I really don't have anything else on the agenda right now. Everything is pretty much locked down. We're just getting to the point where we want to cut a release. 20:25:13 Which is good news. (: 20:25:35 yeah~ 20:25:59 So, I guess at this point I shall open up the floor to any additional queries / thoughts. 20:26:08 nothing from me today. 20:26:15 same here 20:26:20 Awesome. haha 20:26:30 Whelp. Thanks all for coming then! 20:26:40 #endmeeting