16:00:35 #startmeeting Mistral 16:00:35 Meeting started Mon Feb 2 16:00:35 2015 UTC and is due to finish in 60 minutes. The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:39 The meeting name has been set to 'mistral' 16:00:47 hi! 16:01:43 hi Nikolay 16:01:48 2 mins 16:02:47 hi, sorry, I am a bit late 16:03:48 hi all 16:04:29 no problem 16:04:42 guys, I apologize, pls give me 2 more mins 16:07:55 I'm here 16:07:58 ok 16:08:40 so we didn't actually have any action items 16:09:06 so let's discuss other topics 16:09:22 #topic Kilo-2 progress 16:09:52 release page: https://launchpad.net/mistral/+milestone/kilo-2 16:10:14 I moved a couple of low/medium priority BPs to Kilo-3 16:10:33 but overall it looks ok 16:10:57 so here I would like to discuss just one thing 16:11:27 I think we need to leave only bugs that are possible to fix till this Friday 16:12:09 dzimine, I'd like to ask you to take a look at the bugs and assign all that you're interested in to Kilo-2 16:12:38 it can be done offline to save time 16:12:52 ok. Bugs keep on coming. 16:13:16 yeah 16:13:23 it's bad and good at the same time 16:13:24 :) 16:13:25 but i’ll cast my opinion at existing ones. 16:13:31 ok 16:13:46 the bigger quesiton is are there any critical ones which we want to fix before we call it kilo-2. 16:13:46 and pls can you please take a look at https://bugs.launchpad.net/mistral/+bug/1415886 again 16:13:51 at our comments 16:14:00 I think it's invalid and can be closed 16:14:03 btw, I have found a few usability bugs today (for environments cli) 16:14:22 can you pls file bugs? 16:14:25 for them 16:14:34 rakhmerov, you, tomorrow I will 16:14:48 #action dzimine, look at the bugs and assigned most critical ones to kilo-2 16:14:49 rakhmerov, *yes 16:15:08 #action akuznetsova, file bugs for recently found usability issues 16:15:11 ok 16:15:39 do you want us to discuss them now or take it offline? 16:15:58 me? no 16:16:06 I just have one question 16:16:22 sure, go ahead 16:16:22 I will ask it later in open discussion 16:16:25 ko 16:16:27 ok 16:16:46 so, dzimine, answering your question about critical bugs... 16:17:06 I would really like to fix whatever is related with expressions 16:17:23 and I'll strive to finish result/output refactoring 16:18:04 you guys brough up quite a lot of questions on YAQL. 16:18:10 I've mostly done with the overall picture 16:18:17 yes 16:18:48 I'm shocked why we didn't see all those issues before.. 16:19:15 ok, I think that is pretty much it on this topic 16:19:37 and I actually forgot current status topic 16:20:30 so, on Kilo-2, I think there should be no rush or panic with releasing kilo-2 16:20:39 keep in mind that this is a development milestone 16:20:46 #topic Current Status (by team members) 16:21:13 do we release kilo-2 based on time or based on scope (when we fix this list of bugs/implement min list of BP?) 16:22:40 status: drafterd impl on handling errors to prevent zombie workflows, WIP for early feedback / criticism here https://review.openstack.org/#/c/151975 16:22:43 my status: last week I fixed "publish" functionality, reproduced a bug reported by Winson about parallel tasks (didn't fix it though yet since it turned out to be not so trivial), also keep working task output refactoring (made 1 patch so far) and hoping to get it done in ~2 days 16:22:57 dzimine, based on time 16:23:26 because we're trying to be synced with all core projects in terms of release dates 16:24:06 dzimine, thanks. That's a good patch, I will leave a few comments 16:24:24 status: worked on std.javascript and fix one bug related to with-items and action_context 16:25:39 ok 16:26:00 akuznetsova, dzimine? 16:26:06 status: started to test environments 16:26:12 ok 16:26:46 ooh, dzimine, you already wrote you status 16:26:53 ok, so let's go to 16:27:00 #topic Open Discussion 16:27:27 akuznetsova, you were going to ask something 16:27:31 yes 16:27:33 pls do 16:28:09 how to use environments ? where should I pass env name? During execution creation ? 16:28:53 ok, we have that 'params' thing in start_workflow() method 16:29:15 execution-create cli command has 3 arguments only 16:29:26 wf_name, wf_inputs, params 16:29:27 so environment is either a string (env name) or a dictionary and is passed under 'env' key in 'params' 16:29:38 yes 16:29:41 in params 16:29:56 like {env: } ? 16:30:04 params={'env': 'env_name'} 16:30:08 yep 16:30:35 but in CLI I guess it should be a json string as usually 16:31:19 ok 16:31:29 do you have any more questions? 16:31:40 no, just this one 16:31:47 alright ) 16:32:06 I wanted to pay your attention to just one thing 16:32:25 I sent you an email about YAQL problems and suggestions how to solve them (not for all though) 16:32:45 so please read it carefully and provide your feedback 16:32:56 ok, will do. 16:33:15 we need to fix all this asap 16:34:20 anything else? 16:34:40 I don't have anything 16:35:02 me too 16:35:16 gentlemen? 16:35:47 ok, let's finish then 16:35:50 from me too 16:35:54 thanks to all! 16:35:55 bye 16:35:57 bye! 16:36:02 #endmeeting