01:00:56 <flwang> #startmeeting zaqar 01:00:57 <openstack> Meeting started Tue Oct 17 01:00:56 2017 UTC and is due to finish in 60 minutes. The chair is flwang. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:00:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:01:01 <openstack> The meeting name has been set to 'zaqar' 01:01:04 <flwang> #topic roll call 01:01:08 <flwang> anybody around? 01:01:52 <flwang> gecong_: gengchc_: around? 01:01:56 <gecong_> yep 01:02:00 <flwang> cool 01:02:21 <gengchc_> yes 01:02:25 <flwang> gecong_: firstly, congrats for joining the core team and thanks for all your contribution in the past days 01:02:33 <flwang> gengchc_: thanks for joining 01:02:47 <gecong_> you are welcome 01:02:59 <gecong_> thanks 01:03:26 <flwang> generally, we use this etherpad to track the agenda of zaqar meeting but we didn't use it much recently, see https://etherpad.openstack.org/p/zaqar-meeting-agenda 01:03:49 <flwang> this week is the queens milestone 1 release 01:04:10 <flwang> so today i'd like to revisit the plans/blueprints for queeens 01:04:20 <flwang> to make sure if we're on track 01:04:20 <gecong_> ok 01:05:16 <gengchc_> ok 01:05:37 <flwang> https://etherpad.openstack.org/p/zaqar-queens-plan 01:06:00 <flwang> this is the link we're using to track the tasks we'd like to do in Queens 01:07:06 <flwang> do you have any topic to discuss today? 01:07:32 <gecong_> Support more backoff functions in Zaqar -- in work 01:07:54 <gecong_> Bascially pool group is useless in Zaqar, it is time to remove it -- in work bu gengchc 01:07:57 <flwang> gecong_: yep, is it ready for review? 01:08:20 <gecong_> not yet, in a few days 01:08:49 <flwang> ok, pls let us know when it's ready for review 01:08:56 <gecong_> Support Redis as mgmt storage backend -- in work bu gengch and gecong 01:09:18 <gengchc_> yes,I work on pool group function, code is almostly completed, I work on unittest. 01:09:19 <gecong_> np , thanks 01:10:02 <gecong_> Support Token Session in Zaqar for improving performance -- I will contact with wanghao today 01:10:26 <gengchc_> redis as the management of storage function, the code is almostly completed, I and gecong work on unittest. 01:10:27 <flwang> I added comments on the redis mgmt spec https://review.openstack.org/#/c/504379/4/specs/queens/support-redis-as-mgmt-storage-backend.rst if you can address those comments, I'm happy to approve it 01:10:55 <gengchc_> ok 01:10:58 <gecong_> ok 01:11:44 <flwang> gecong_: I'm really interested in the spec Support Token Session in Zaqar for improving performance 01:12:11 <gecong_> ok , I will discuss with wanghao for this today 01:12:29 <flwang> so you guys are working on 3 blueprints now, redis, pool group and retry policy, that's good enough for this cycle 01:12:47 <flwang> and I know Lance, keystone ptl is working on the policy in code 01:12:54 <gecong_> yes 01:12:55 <wxy_> policy in code is inited by lance 01:13:00 <wxy_> yeah 01:13:01 <flwang> and chandankumar is working on the tempest plugin 01:13:11 <wxy_> It's in good shape. 01:13:30 <flwang> wxy_: yep, i saw you're reviewing it, thanks 01:13:57 <flwang> generally, given the size of our team, I think we have enough things to do 01:13:59 <wxy_> Anyone who is interested in can push the follow patches. 01:14:07 <flwang> wxy_: which one? 01:14:13 <wxy_> policy in code 01:15:20 <wxy_> Lance only complete queue and message refactor. 01:15:58 <flwang> do we have to finish all of them in one cycle? 01:16:35 <wxy_> I think we should, it's not very hard. 01:17:32 <wxy_> And this one https://review.openstack.org/#/c/511749 . Need your review comment. 01:18:38 <gengchc_> [https://review.openstack.org/#/c/511749] can't open. 01:19:00 <flwang> seems gerrit is down? 01:19:18 <flwang> anyway, I will take a look later, if it's necessary, i can pick it up 01:19:20 <gecong_> yes 01:19:37 <flwang> i was busy recently, but should be available in next couple of weeks 01:20:12 <wxy_> prepare for summit? 01:20:28 <gecong_> I will review it today 01:20:38 <flwang> wxy_: vote for TC and internal Horizon migration/performance 01:20:50 <flwang> s/vote/run 01:20:56 <gengchc_> I will review it too. 01:21:05 <wxy_> thanks, team. 01:21:08 <gecong_> I have voted for TC already 01:21:12 <wxy_> flwang: cool. 01:21:18 <flwang> wxy_: any idea for this Support Token Session in Zaqar for improving performance ? 01:21:35 <gengchc_> I have voted for TC too. 01:22:39 <flwang> thanks for all the comments/updates. i think we're basically on track for the plans on Queens 01:23:08 <wxy_> flwang: No, It needs more detail I think. 01:23:19 <flwang> wxy_: ok, no problem 01:25:03 <flwang> gengchc_: gecong_any updates from the your production? 01:25:40 <flwang> i mean zaqar on ZTE developer platform 01:26:39 * wxy_ leave for some internal work. 01:26:52 <gecong_> yesterday, I attend a meeting about openfog messageing 01:27:46 <flwang> any info can be shared? 01:27:51 * wxy_ is coming 01:29:17 <gecong_> it is about edge computer 01:30:13 <flwang> gecong_: ok 01:30:34 <gecong_> they need messgae solution 01:30:55 <flwang> as you know, the adoption of zaqar is still low, so please feel free recommend Zaqar wherever you can :) 01:31:11 <gecong_> I will discuss with them in following days 01:31:45 <gecong_> yes, I will introduce zaqar to them 01:31:48 <flwang> if it's not a private mailing thread, you can involve me 01:32:09 <gecong_> sure 01:32:27 <gecong_> I am glad to hear that 01:32:51 <flwang> cool, thanks 01:33:25 <flwang> and one thing you could mention to them is, zaqar can work without the other openstack services 01:33:49 <flwang> the only work they may need is a plugin for auth 01:34:03 <gecong_> they need most is communction between DCs 01:34:24 <flwang> ok, we can discuss the details offline 01:34:34 <gecong_> ok 01:34:37 <flwang> #topic bugs 01:35:01 <flwang> Luckily(unfortunately), now we don't have much bugs on backlog 01:35:11 <flwang> but I expect bugs in our code 01:36:04 <gecong_> I think if we commit our bp, there will be a lot of bugs 01:36:14 <flwang> as you may know, zhenyuyang from YiYun is working on deploying zaqar 01:36:19 <gecong_> :) 01:36:34 <flwang> so I may work with him to figure out any potential issue and get them fixed 01:36:59 <flwang> that's the plan 01:37:05 <flwang> #topic open discussion 01:37:06 <gecong_> ok 01:37:23 <flwang> is there anything else you want to discuss? 01:37:44 <gecong_> not from me 01:37:57 <wxy_> Please register the bugs if possible. 01:38:05 <flwang> wxy_: absolutely 01:38:08 <wxy_> I have a question: Does anyone know what's the current situation about the CI/CD? I found both Jenkins and Zuul. What's the relationship? 01:38:48 <gecong_> I think they will immigrate to zuul V3 01:38:49 <flwang> actually, Zaqar is also on Catalyst Cloud roadmap for a while, but we have to deploy LBaaS and Magnum firstly due to the low requirements in New Zealand for messaging :( 01:39:35 <gecong_> CI/CD is not stable recently 01:39:53 <flwang> wxy_: i didn't dig into the details of the CI, but I assume the Zuul v3 will replace Jenkins job? 01:40:05 <wxy_> gecong_: Which one is the primary? Now When I do recheck, it seems that only jenkins goes, but zuul does nothing. 01:40:39 <gecong_> and py27 is always fail 01:40:47 <wxy_> flwang: So do we need to do some work in project-config? 01:41:19 <flwang> wxy_: i assume no, but will see 01:41:26 <wxy_> flwang: OK. 01:41:48 <gecong_> I don't know , I think they are debugging the zuul V3 01:42:19 <wxy_> Ok, That's all for me. THanks. 01:42:36 <flwang> BTW, another thing in my mind randomly is, is it possible to rewrite zaqar with Go? 01:42:52 <flwang> or at least some parts of Zaqar to improve the performance 01:43:02 <flwang> but the idea is very unclear now 01:44:03 <wxy_> flwang: what's the progress that Go in Swift? I think we can learn something from it. 01:44:29 <gengchc_> If We can improve performance, can you consider using go or c language? 01:44:39 <flwang> wxy_: the problem is zaqar is only one process 01:44:48 <flwang> so it's a little bit hard to rewrite part of it 01:45:09 <wxy_> Emm, yeah. 01:45:10 <flwang> gengchc_: that's my thought, but I'm not sure if language is really the bottleneck, TBH 01:45:25 <flwang> maybe just the websocket part> 01:45:26 <flwang> ? 01:45:51 <flwang> i don't know, just random thinking 01:47:29 <gengchc_> I use two nodes to test zaqar based on redis+mongo+haproxy, almost 2000 messages /seconds,but there is big different from tecent(120000/s) 01:48:01 <flwang> because the status of Trove makes me thinking, we may need to do some changes to get a big improvement 01:49:09 <flwang> 不破不立 01:49:20 <wxy_> lol 01:49:25 <gecong_> support 01:49:34 <gengchc_> I agree. 01:50:01 <flwang> wxy_: my long term goal, just like Gnocchi, actually Zaqar could be an open source messaging project out of OpenStack world 01:50:22 <wxy_> Zaqar standalone. 01:50:35 <wxy_> All projects now want to standalone. :) 01:50:43 <flwang> so my goal is creating an open source messaging service with HA, low latency and good scalability 01:50:55 <flwang> wxy_: no, I say we can 01:51:00 <flwang> but we don't have to 01:51:09 <flwang> in a visible future 01:51:22 <flwang> but I mean we need to have a big goal 01:51:39 <wxy_> yes, sir. 01:51:45 <gecong_> yes sir 01:52:09 <flwang> gengchc_: I'm interested in the performance you mentioned " from tecent(120000/s)" 01:53:07 <gengchc_> I see it in tecent website. 01:53:07 <flwang> I will create a separated etherpad for performance tunning 01:53:43 <flwang> and we can collect the performance from different public clouds and work out a reasonable goal 01:53:47 <flwang> then focus on that 01:53:57 <gecong_> ok 01:54:02 <gengchc_> ok 01:55:02 <flwang> ok, i think that's us 01:55:17 <gengchc_> cent website: https://cloud.tencent.com/product/cmq 01:55:18 <wxy_> another thing: FYI, Keystone has a bp called unified limits. It's related to Quota. Now Lance and I are trying to take over it. Zaqar can wait for it for the quota requirement IMO. 01:55:29 <flwang> anything else? we can continue discussion in zaqar channel 01:55:47 <gengchc_> tecent website: https://cloud.tencent.com/product/cmq 01:55:47 <flwang> wxy_: yep, good to know. 01:56:00 <flwang> gengchc_: thanks, i will take a look 01:56:07 <flwang> ok, i'm going to close the meeting 01:56:10 <flwang> thanks for joining 01:56:12 <gecong_> ok 01:56:16 <flwang> #endmeeting