18:00:36 <flwang1> #startmeeting zaqar 18:00:37 <openstack> Meeting started Mon Jun 13 18:00:36 2016 UTC and is due to finish in 60 minutes. The chair is flwang1. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:41 <openstack> The meeting name has been set to 'zaqar' 18:00:53 <flwang1> #topic roll call 18:00:57 <flwang1> o/ 18:01:07 <flwang1> anybody around? 18:01:09 <Eva-i> o/ 18:01:27 <flwang1> Eva-i: seems only you and me 18:01:35 <vkmc> o/ 18:01:36 <vkmc> and me 18:01:44 <Eva-i> vkmc: hey =) 18:01:51 <flwang1> vkmc: ah, hello 18:01:58 <flwang1> here is the agenda https://etherpad.openstack.org/p/zaqar-meeting-agenda 18:03:32 <flwang1> firstly, i would like to say i did a bad job in Mitaka release for the release job 18:03:44 <flwang1> we missed all the release notes :( 18:04:02 <Eva-i> =/ 18:04:18 <vkmc> ouch yeh 18:04:22 <vkmc> that was something new 18:04:23 <flwang1> and there is almost no way to fix it, though i'm still working on that to figure out a way to do it 18:04:25 <vkmc> I saw them in Trove 18:05:23 <flwang1> and the good thing is in Newton, we will/need force all the critical bug and features patches have the release notes before merging or at least with a followup patch 18:05:26 <Eva-i> it's okay, let's make Newton release nice 18:05:48 <flwang1> so pls keep an eye when you review code 18:06:21 <flwang1> i may make mistake so i need more eyes to monitor, thanks 18:06:24 <Eva-i> flwang1: only info about critical bugs and features should be added to release notes? 18:07:11 <flwang1> Eva-i: technically, anything the end user should be aware of, like upgrade, deprecation,etc 18:07:33 <Eva-i> flwang1: okay 18:09:47 <flwang1> #topic code review 18:10:32 <flwang1> as you may know, in our server side, we are using the functional test of zaqar client for gate job 18:11:02 <flwang1> and sometimes it's causing the interdependent issue especially when adding a new feature 18:11:15 <flwang1> recently, we just enabled the tempest job 18:11:55 <flwang1> and then, we have switched the voting of tempest job and the functional test job 18:12:15 <flwang1> so the interdependent issue has gone, just FYI 18:13:00 <flwang1> and the good thing is we have contributor for the tempest case https://review.openstack.org/#/c/319825/ 18:13:33 <flwang1> it's not a small patch, but not very complicated, pls give it some love :) or bless ;) 18:14:03 <Eva-i> flwang1: first the redis bugs should be fixed? 18:14:12 <flwang1> Eva-i: yes 18:14:13 <Eva-i> flwang1: before giving it love 18:14:17 <Eva-i> flwang1: ok 18:14:47 <flwang1> that's the cost of love :D 18:15:27 <flwang1> and we have two websocket patches on the list https://review.openstack.org/#/c/326897/ and https://review.openstack.org/#/c/326272/ 18:15:52 <flwang1> the first one is related to auth issue, i have reviewed by haven't submitted comments 18:16:52 * vkmc clicks 18:16:58 <flwang1> the 2nd one is removing the subscriptions after closing connection which is the one vkmc and i discussed when she worked on the demo on Paris summit, IIRC 18:17:00 <Eva-i> My plan is: 1. Upload install guide in proper format 2. Review redis patches of bugs stopping tempest gate from passing 3. Review websocket patches. 18:17:28 <vkmc> flwang1, +1 18:17:30 <flwang1> Eva-i: good to know :) 18:17:54 <flwang1> vkmc: so pls help review them, since you're the expert of websocket code ;) 18:18:32 <vkmc> flwang1, sure thing 18:18:45 <flwang1> vkmc: <3 18:19:14 <flwang1> and this one https://review.openstack.org/308736 a client patch related to the version parsing 18:19:59 <flwang1> pls pls pls review it today, since i would like to release a new version for zaqar client asap, because we have merged the 'queue update' patch for client side 18:20:19 <flwang1> we need a new client version asap 18:20:27 <Eva-i> oh okay 18:20:54 <flwang1> you know, now it's the mid of Newton 18:21:41 <flwang1> ok, any patch we should highlight? 18:22:27 <Eva-i> flwang1: I think you highlighted the last patch mentioned 18:22:50 <flwang1> cool :D 18:22:58 <flwang1> #topic spec/features 18:23:25 <flwang1> 1. we have merged the lazy queue support for subscription, yeah!!! thanks Eva-i 18:23:38 <Eva-i> yay 18:25:30 <flwang1> generally, that said Eva-i has resource to do more :D hah 18:25:53 <vkmc> Eva-i++ 18:25:54 <vkmc> :) 18:27:15 <flwang1> 2. subscription confirmation https://review.openstack.org/284555 18:27:55 <flwang1> i think it's ready to be merged and i'm going to approve it today if there is no big concern about it 18:28:14 <flwang1> we can adjust/discuss the details when doing code review 18:28:36 <flwang1> generally, the spec is in a good shape now 18:28:41 <flwang1> any comments? 18:28:53 <Eva-i> I will look at it after highlighted patch 18:31:12 <flwang1> Eva-i: ok, thanks 18:32:20 <flwang1> pls -1 if you have big concern about it, otherwise let's don't block it and discuss details in code review 18:32:50 <Eva-i> flwang1: ok, I understand 18:32:57 <flwang1> it has been reviewed for a long time, we need it in Newton 18:33:02 <flwang1> cool, thanks for the understanding 18:33:18 <flwang1> 3. Notification driver for Mistral https://review.openstack.org/#/c/318202/ 18:33:32 <flwang1> the one is in good shape now 18:33:50 <flwang1> i would like to approve it if there is no object 18:34:10 <flwang1> we don't have a volunteer now 18:34:34 <flwang1> so i may take it and hold on the dead letter queue for a while 18:35:07 <flwang1> Eva-i: vkmc: flaper87: if you are interested in this, pls let me know 18:35:15 <Eva-i> I do not object, because don't know much =/ 18:35:23 <flwang1> Eva-i: :) 18:36:05 <vkmc> same here, I'd need to catch up with that use cse 18:36:29 <flwang1> Eva-i: vkmc: no problem, just ping if you want to join the coding 18:36:35 <vkmc> +1 18:36:37 <vkmc> thanks flwang1 18:36:51 <flwang1> 4. v1.1 deprecation which flaper87 is working on that 18:37:00 <flwang1> though the last patch set is 3 months ago 18:37:23 <flwang1> #link https://review.openstack.org/294611 18:37:47 <flwang1> i may upload a new patch set to that one to make it happen in N-2 18:37:59 <flwang1> so that we have time to fix any regression bug in N-3 18:38:10 <flwang1> pls star it on gerrit :D 18:38:18 <flwang1> that's an important patch for zaqar 18:39:42 <flwang1> ok, any topic from your side? 18:40:26 <flwang1> #topic open discussion 18:40:41 <flwang1> we have 20 mins for open discussion 18:40:57 <flwang1> i have one topic fit this section 18:41:15 <flwang1> i would like to nominate therve for zaqar core 18:41:30 <vkmc> :o 18:41:33 <flwang1> vkmc: Eva-i: flaper87: comments? 18:41:34 <vkmc> totally 18:41:37 <vkmc> +1 18:41:44 <vkmc> so very much in 18:41:46 <vkmc> :D 18:41:48 <Eva-i> flwang1: I'm okay 18:41:56 <flwang1> vkmc: i'm not sure if it's a bad idea, TBH 18:41:59 <Eva-i> flwang1: I thought he was Zaqar core 18:42:10 <flwang1> Eva-i: he is PTL of Heat 18:42:34 <flwang1> he has contributed a lot of code/patches for zaqar, especially for the websocket part 18:42:45 <flwang1> and most of them are critical patches 18:43:01 <flwang1> and he is always active in zaqar channel for critical bugs 18:43:22 <flwang1> and answer questions for new comers 18:43:41 <flwang1> the only 'issue' is he didn't do much code review 18:43:56 <flwang1> and the 'core' in openstack means 'core reviewer' 18:44:17 <Eva-i> mmm 18:44:21 <flwang1> but 18:44:33 <flwang1> i'm sure he is totally qualified 18:45:06 <flwang1> TBH, even we don't nominate him 18:45:22 <flwang1> he will still be around and continually doing the great job 18:45:32 <Eva-i> I think so 18:45:59 <flwang1> so the nomination is most like a recognition for his contribution 18:46:05 <flwang1> does that make sense? 18:47:20 <Eva-i> Yes, it does 18:47:58 <flwang1> and it's a good thing to have a team member from heat which is the good consumer of zaqar 18:48:39 <flwang1> Eva-i: vkmc: flaper87: ok, so i think we're in agreement for this proposal :) and thanks 18:49:42 <flwang1> and another topic is Barcelona summit is calling for topics 18:51:14 <Eva-i> mmm, I don't have topics to propose now 18:51:52 <flwang1> Eva-i: it's a reminder, we should propose some topics about zaqar :) 18:52:05 <flwang1> like we usually do 18:52:10 <Eva-i> flwang1: I think I should mark as "-1" this spec: https://review.openstack.org/#/c/284555. 18:52:39 <flwang1> what's wrong? 18:52:51 <Eva-i> flwang1: mostly because it lacks information about "web page with ajax script". 18:53:14 <flwang1> Eva-i: oh, why do you think it's a problem? 18:53:22 <Eva-i> flwang1: where this page will be hosted and should we add additional option to zaqar. 18:55:10 <flwang1> Eva-i: hmm... it deserves a -1 18:55:39 <flwang1> but like we discussed before, we will host a sample in zaqar tree and maybe move it to zaqar ui in the future 18:56:06 <flwang1> and we do need a config for the place which will be a part of the email template 18:56:13 <flwang1> Eva-i: does that make sense? 18:56:15 <Eva-i> flwang1: so I will ask wanghao to include this info 18:56:29 <Eva-i> flwang1: yes, it does make sense for me, but the spec omits this 18:56:39 <flwang1> Eva-i: yep, agree 18:56:50 <Eva-i> flwang1: okay 18:57:07 <flwang1> Eva-i: i forgot if i mentioned that in the comments or the discussion with you 18:57:32 <Eva-i> flwang1: we have discussed this problem 18:57:34 <flwang1> but i'm sure i mentioned it somwhere :D 18:57:43 <Eva-i> flwang1: now I should tell wanghao to include this info 18:57:52 <flwang1> Eva-i: ok, cool, thanks 19:00:32 <flwang1> ok, that's all 19:00:35 <flwang1> thanks all 19:00:40 <flwang1> #endmeeting