02:02:07 #startmeeting zaqar 02:02:08 Meeting started Tue Jan 24 02:02:07 2017 UTC and is due to finish in 60 minutes. The chair is flwang. Information about MeetBot at http://wiki.debian.org/MeetBot. 02:02:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 02:02:11 The meeting name has been set to 'zaqar' 02:03:01 #topic roll call 02:03:04 o/ 02:03:20 hi 02:03:34 i didn't update the agenda, since it should be same 02:03:55 i think our focus is still get the swift driver in and the subscription confirmation email part 02:04:07 and fix the sqlmigration issue 02:04:22 yes, how the sql issue going? 02:04:44 i have fix the issue, but I need to get the test work 02:05:24 So this wee is O-3 release? 02:05:52 Could this be done before O-3? 02:06:28 hmm... i think we can merge swift driver with no doubt, but as for the sqlmigration issue, i don't know, i may need your help 02:07:02 I'd like to help any problem if I can. 02:07:30 about the swift driver. I tested some days. It works for me. 02:07:37 and yes, this week is for o-3 02:08:14 but the end of this week is the Chinese spring festival 02:09:07 Yes, So I hope these two feature could be merged in this week if they are ready. 02:09:28 yep, me too 02:11:37 About the subscription confirm patch, I won't +2 because I'm one of the coders. 02:12:01 ok, that's fine 02:12:04 And I haven't test it with a real email system 02:12:27 Don't know whether it works although the code look fine now. 02:12:36 I tested last time, but as i pointed out, wanghao missed some important steps 02:12:52 so i'm not really sure if we can get it fix in this week 02:12:53 ping wanghao_ here? 02:12:58 i will test it tomorrow 02:13:12 wxy: yes 02:13:39 We can talk more about the subscription confirm patch here. 02:13:43 wanghao_: have you fixed the logic issue i figured out last time? 02:13:54 Hope it can be merged in this week. 02:14:11 flwang: yes, I added unsubscriber confirmation process. 02:14:38 ok, i will verify it asap 02:15:14 flwang: user can click the unsubscriber link in html, and then zaqar will send a notification email to user. 02:16:00 cool 02:17:10 wanghao_: and the swift backend patch. 02:17:18 please review it.:) 02:17:24 wxy: sure 02:17:28 awesome 02:17:37 btw, 春节快乐 02:17:45 in case I forget :) 02:17:52 hah 02:17:53 flwang: haha 02:18:12 you guys did a great job in this cycle 02:18:17 THANK YOU! 02:18:57 flwang: You too :) 02:20:33 flwang: when will we have a chat about the work listin Pike? 02:21:03 at summit :) ? 02:21:05 s/listin/list in 02:21:21 PTG? 02:21:47 we're very close to the point that we should stop adding more stuff but polish the gear 02:22:28 yep, PTG is a good time, but most of us won't be there 02:22:50 so i prefer anytime after the Ocata and you guys back 02:23:05 i mean we can discuss it any time, such as now 02:23:26 flwang: agree 02:23:36 because we don't have any critical bug now and only the two features which are very close to finish 02:24:13 https://blueprints.launchpad.net/zaqar 02:24:17 I have a bp in Pike that is removing the pool group. 02:25:00 after a quick glance for our bp list 02:25:26 i think we can pick up the cors support and notification policy 02:26:15 but the more important stuff is a workable plan to improve the performance and stability 02:28:19 yes, performance and stability is the most important job. 02:28:25 we can pick some bps in the list that fits this goal. 02:29:27 cors-- I can do this one. 02:29:48 wxy: awesome 02:30:09 personally,i think it's very useful for websocket support 02:31:26 Can we open a etherpad to track the Pike work? 02:31:30 and in Pike, I'd like to polish the sqlalchemy driver, and swift driver 02:31:31 sure 02:31:44 that is we did for each cycle 02:32:42 Cool, Actually I have no clear thought at this moment. So I'd like to leave my comment later. 02:33:27 #link https://etherpad.openstack.org/p/zaqar-pike-summit 02:33:39 let's use this etherpad to track the ideas/assignments 02:33:53 which can be used for summit design session as well 02:34:01 flwang: So fast. 02:34:05 I can try the notification-delivery-policy, looks very interesting. 02:34:32 wanghao_: yep, that's a feature you can see in sns and aliyun's notification service 02:34:44 flwang: yeah 02:34:52 in Pike, i won't do any new feature 02:35:07 basically just polish somewhere :D 02:35:24 great 02:35:42 oh, btw, i will run for the PTL for Pike cycle if there is nobody want to go for it 02:35:48 flwang: Looking forward to your work. 02:36:07 flwang: +1 02:36:55 and another thing everybody needs to keep in mind is encouraging more people to join this cute project 02:37:05 we're still a small team, need more contributors 02:38:53 flwang: yes, I'd like to introduce our project and invite people to join us if I'll share something to others. 02:39:03 cool, thanks 02:39:17 anything else you guys want to discuss? 02:39:24 #topic open discussion 02:39:59 https://review.openstack.org/#/c/423023/ 02:40:39 that patch looks fine for me 02:40:46 we can merge it quickly 02:40:49 cool 02:41:41 thanks, just waiting jenkins happy 02:43:34 flwang: oh, there is a issue when I used sendmail. How to change the from address, did you some doc for it? 02:44:00 flwang: I tried some way but it didn't work. 02:44:19 wanghao_: you mean the 'from' in current code doesn't work? 02:44:20 wanghao_: that' 02:44:36 wanghao_: that's the reason why I can't test your code. 02:44:40 wanghao_: :( 02:44:43 flwang: no, it's not our code. 02:45:06 flwang: just I used sendmail in my devstack env to test the confirmation patch. 02:45:57 flwang: our code has made the email, but sendmail can't send it to my gmail sucessfully. 02:46:02 wanghao_: i can't remember the details when I developed the code about 2-3 years ago 02:46:14 i'm still use the same laptop, so seems it still works 02:46:32 at least, in my test, the 'from' looks correct 02:46:49 flwang: okay, that's fine. 02:47:00 did you try to send to your huawei email account/ 02:47:01 ? 02:47:19 flwang: I try to send the fiberhome email account. but still failed. 02:47:25 i didn't try with gmail, but with my company email account because it's faster 02:47:33 ok 02:47:38 i see we can discuss it later 02:47:40 offline 02:47:44 flwang: okay 02:48:13 ok, awesome 02:48:24 i'm going to close this meeting, thanks for joining 02:48:31 thanks. 02:48:34 #endmeeting