16:00:42 #startmeeting Mistral 16:00:43 Meeting started Mon Sep 14 16:00:42 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:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:46 The meeting name has been set to 'mistral' 16:00:52 hi everyone! 16:00:56 hi 16:01:11 hi there 16:01:31 hi 16:01:52 other guys? 16:02:18 not today most likely, maybe Winson will join but not folks from ALU, they have a holiday 16:02:22 so let's start 16:03:13 the agenda is at: https://wiki.openstack.org/wiki/Meetings/MistralAgenda 16:03:20 #topic Review Action Items 16:03:57 1. xylan_kong: look at the failing test NegativeCLITests.test_ex_invalid_status_changing, it may be related with https://review.openstack.org/#/c/219870/2 16:04:02 I know it's done ) 16:04:07 yeah 16:04:20 2. rakhmerov, xylan_kong: remind zhenguo about https://review.openstack.org/216729 16:04:40 done 16:04:47 done but there's still some work to merge a patch into infra 16:04:56 it's on review now 16:05:07 3. xylan_kong: review https://review.openstack.org/220439 and Nikolay's documentation patches 16:05:10 this is done 16:05:12 thank you! 16:05:22 4. rakhmerov, zhenguo: help Liat with her patch on tasks screen 16:05:38 this is, honestly, something that I still didn't find time for 16:05:57 zhenguo may have found though but I don't have info about it 16:06:09 xylan_kong: do you know? 16:06:30 maybe zhenguo is busy with some PoC these days 16:07:03 did'nt have enough time for upstream work 16:07:04 ok, I'll try to catch Liat and talk to her about her patches 16:07:06 ok 16:07:08 I see 16:07:26 #action rakhmerov: talk to Liat about her patches 16:07:35 5. rakhmerov or NikolayM: implement task() yaql function 16:07:36 done 16:08:13 although this workstream is not finished, we need to remove deprecated stuff so that we can't use "$.task_name" to access task result 16:08:35 #action rakhmerov: finish all that's left after adding task() yaql function 16:08:45 6. gpaz: try to investigate what may be wrong with expiration policy (look at https://review.openstack.org/#/c/218544/) 16:08:53 he is still looking at it 16:09:03 #action gpaz: try to investigate what may be wrong with expiration policy (look at https://review.openstack.org/#/c/218544/) 16:09:10 7. ^Gal^: make mistral-dashboard debug shine 16:09:48 same 16:09:56 #action ^Gal^: make mistral-dashboard debug shine 16:10:08 this is the patch: https://review.openstack.org/221685 16:10:19 ok, let's move to the next topic 16:10:28 #topic Current status 16:10:38 my status: worked on documentation, fixed dsl docs, checked bug related to env evaluation in with-items, start to work on some bugs 16:11:16 my status: released L-3 last week, this time the delay was about 3 days which I consider ok but we definitely can do better 16:11:53 :-) 16:12:19 also implemented a couple of things: refactored specifications (polymorphic specs, separate validation etc.), fixed a bug with wf cycles, implemented task() function 16:12:39 xylan_kong: what does your smile mean? :) 16:12:53 My status: I have been busy with censor summit topics internally for almost the whole last week, and did some review work in spare time 16:13:13 just for 'we can do it better' 16:13:22 yes, we can :) 16:13:26 sure 16:13:30 we're learning how to 16:13:33 :) alright 16:13:40 I am working on python34 gate, try to make it "green" 16:13:47 cool 16:14:03 I'd suggest we make it in separate patches so that they are not so big 16:14:13 this gate is non-voting anyway 16:14:27 but it would be really cool if we finally did that 16:14:41 akuznetsova: than you very much for volunteering ) 16:14:48 .. thank ... 16:15:50 guys, 2 questions: 1) any roadblocks that you see? 2) xylan_kong: what your availability is going to be for the next couple of weeks? 16:16:03 rakhmerov, no problem) 16:16:14 +1 16:16:49 rakhmerov: I'll be on business trip next week 16:17:19 but I think I have at least 2 hour per day for upstream work 16:18:11 ok, good 16:18:20 next topic 16:18:31 #topic Scoping RC releases 16:19:04 so since we released L-3 we now started working on RC1 release 16:19:54 as far as RC releases, we're not adding any new functionality, especially API changes, and mostly fixing bugs 16:20:08 what I think is ok is to continue with docs and UI 16:20:30 because it doesn't break any compatibility by any way 16:20:33 so 16:21:09 agreed, we can bring new features to discuss at the summit 16:21:20 I've tried to arrange all the bugs that we have and assign the most important ones (IMO) to RC1 and some to RC2 16:21:25 yes 16:22:20 again, this bug<->release assignment is mostly my vision of what we need to be focused on 16:23:02 and hence I'd like to ask you to look through the list of bugs and let me know what you agree/disagree with 16:23:30 in other words, feel free to make your sugguestions 16:23:38 btw, here is a link https://launchpad.net/mistral/+milestone/liberty-rc1 16:24:00 thanks, yes 16:24:54 the main criteria that I was guided is "does it prevent using Mistral in production?" 16:25:26 for example, this one does: https://bugs.launchpad.net/mistral/+bug/1337268 16:25:27 Launchpad bug 1337268 in Mistral liberty "Security issue: passwords are not hidden in logs" [Critical,New] - Assigned to Lingxian Kong (kong) 16:25:50 yes, this is the one I'm struggling with 16:25:51 I know it's a hard one but we have to provide a solution 16:25:56 yep 16:26:18 xylan_kong: I left a comment there, please look at it and let me know your thoughts 16:26:31 rakhmerov: thanks 16:26:32 np 16:26:32 maybe we should change the title of this bug? 16:26:34 even if you agree with the solution it will take pretty long to implement 16:26:43 at least a week 16:26:50 I'll try 16:27:16 akuznetsova: yes, do you have a suggestion? 16:27:38 and I need NikolayM's help as well, NikolayM please also take a look 16:28:19 passwords -> user-specific secure data 16:28:26 ? 16:28:57 yep, How can I help you? 16:29:03 ok 16:29:36 NikolayM: need you input for this problem :) 16:30:04 check this out: https://bugs.launchpad.net/mistral/+bug/1337268 16:30:06 Launchpad bug 1337268 in Mistral liberty "Security issue: user secure info is not protected properly (logs, API, DB)" [Critical,New] - Assigned to Lingxian Kong (kong) 16:30:12 is this title ok? 16:30:36 about how can we solve it elegantly 16:30:36 yes, sounds more 'english' ) 16:30:38 rakhmerov: perfect 16:31:06 akuznetsova: will take it as a compliment :) 16:31:13 ok 16:31:42 rakhmerov: about pagination support at client, we can do it in RC-1? 16:31:45 or leave it to M? 16:31:58 let's try to push it 16:32:14 honestly, I thought it was done when I was going thru the list of bugs 16:32:28 since it's new feature for mistralclient, so it break our rule 16:32:31 xylan_kong: would you like to take it? 16:32:32 no, I just missed it 16:32:47 it's a bug rather 16:32:49 rakhmerov: sure, let me finish my work 16:32:55 it's not new functionality 16:33:18 rakhmerov: ok, I will file a new bug for that 16:33:22 and it may actually be done in a backwards compatible way 16:33:30 yes, please 16:34:04 one thing I'd ask you is to always assign the current milestone for a bug if it's completed 16:34:32 can I? 16:34:44 it's mostly my fault, I know, but I found lots of fixed bugs without milestones 16:35:14 xylan_kong: I mean even if you can't (please check if you can) you can ask me 16:35:21 rakhmerov, I think that xylan_kong doesn't have enough permissions 16:35:24 rakhmerov: ok, sure 16:35:24 xylan_kong: btw, you should be able to 16:35:33 hmm... 16:35:38 rakhmerov: yes, I wish I have 16:36:24 I don't belong to mistral driver team 16:37:08 https://launchpad.net/~mistral-drivers 16:37:17 right there? 16:39:31 ok, let me figure out that 16:39:47 I think it's actually because of the different group 16:39:51 Mistral Bug Team 16:40:07 yes, this one https://launchpad.net/~mistral-bug-team 16:41:53 yes, I'm generally not against of giving you a permission but I think it doesn't work right now in our project 16:42:06 rakhmerov: it's ok 16:42:10 let me figure out something 16:44:10 #action akhmerov: figure out if it's ok to include xylan_kong into Mistral Bug Team 16:44:24 xylan_kong: I'll do it tomorrow. I think it's ok to do it 16:44:37 just need to read a couple of wiki pages :) 16:44:55 alright 16:44:57 rakhmerov: ok, it's not so urgent 16:45:53 guys, any suggestions now on bugs for RC releases? 16:46:12 and you can look at them offline and make your suggestions then 16:47:28 do not forget about bugs here https://bugs.launchpad.net/python-mistralclient 16:49:05 yes, however, we don't have any RC releases for client and we can just release minor versions if needed 16:49:20 assuming that we don't break compatibility, of course 16:49:29 but yes, let's not forget them 16:49:36 ok 16:49:44 #topic Open Discussion 16:50:59 usual question: anything else? 16:51:12 nothing from my side 16:51:15 ok 16:51:16 no 16:51:19 no 16:51:23 please don't forget to review patches 16:51:39 sure :) 16:51:40 remember: core member is primarily core reviewer 16:51:43 not committer 16:51:59 I always call my self core reviewer :-) 16:52:08 and keep reviewing every day 16:52:16 ok, cool 16:52:36 I actually wish we had more good reviewers (don't want to offend anyone) 16:52:59 ok, let's end the meeting 16:53:02 #endmeeting