02:03:43 #startmeeting zaqar 02:03:44 Meeting started Tue Mar 6 02:03:43 2018 UTC and is due to finish in 60 minutes. The chair is wanghao. Information about MeetBot at http://wiki.debian.org/MeetBot. 02:03:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 02:03:47 The meeting name has been set to 'zaqar' 02:03:56 hi guys 02:03:59 hi 02:04:02 hi 02:04:06 haha 02:04:15 seems wxy not here 02:04:27 o/ 02:04:34 ;) 02:04:40 OK 02:05:03 today we will focous the Rocky plan 02:05:11 so let's jump into it 02:05:18 #topic Rocky plan 02:05:32 https://etherpad.openstack.org/p/zaqar-rocky-plan 02:05:56 here is list of rocky plan, is there anything else missing? 02:07:36 Now we have nine items here, and some have good begin 02:08:18 I want to add to the function[Remove pool group totally in Rocky]! 02:08:38 sure 02:09:25 plz feel free to add yourself to item which you want to join 02:10:00 Gecong and I add to the function[Introduce topic resource for notification]! 02:11:32 From my side, I think the quota, topic resource, remove pool group have higher priority level 02:11:37 gengchc2_: sure 02:11:51 I leave some comment for quota. 02:11:55 we can work together for coding this 02:12:08 It's not ready in Keystone. 02:12:18 wxy: yes, that I want to ask next 02:12:31 wxy: do you think is there anything we can do in Rocky? 02:12:52 wxy: or we just wait the Keystone in S 02:13:05 quota contains two parts: limit and usage 02:13:17 limit will be handled by Keystone. 02:13:42 What Zaqar should do is to query limit from keystone can enforce the usage 02:13:58 so we can prepare the usage in Rocky first? 02:14:27 But it's not easy to just adopt usage without limit. 02:14:46 I suggest we should wait for keystone. 02:14:58 there will be a new oslo lib comming soon. 02:15:45 there is two ways that we can think about, 1 we implement the limit and usage in Rocky by ourselves, and then switch to keystone when it is ready 02:16:00 second way is we will wait for keystone in S 02:16:35 I suggest we wait keystone in s. 02:17:39 I prefer the second way. Quota system is not a easy feature. We should not waste our energy for something which would be deprecated in the future. 02:17:58 okay , no hurry to introduce the quota since we lost it for a long time. 02:19:22 another work is the performance improvement. 02:20:20 gengchc2_: gecong_: I remember you have tested the preformance under keystone cache. 02:20:34 yes 02:20:48 seems still have some issue that impact the performance 02:21:23 so I still hope we can have a deep look in it. wdyt 02:21:34 gengchc2_: could you say more here? I'm sorry that I forget the detail. 02:22:54 There are some issue under the keystone cache:When multiple clients are tested, token will be applied, resulting in a significant decline in performance 02:25:03 Is it the issue for Keystone? 02:25:18 wxy: seems not 02:25:38 we use the keystone cache, it works fine 02:25:44 If we don't use Keystone, and use redis as management and redis as message store, 3200messges --3500messages persecond in 32 core. 02:27:25 but I still didn't get why the performance decline so much when using the keystone cache. 02:27:42 we need time to look into it I think. 02:28:15 we can discuss this more after the meeting. 02:28:24 Multiple clients sometimes apply for token, performance degradate,even if we have applied for a good token in advance. 02:28:44 ok 02:28:55 sure. Maybe we sill need to support long connection for wsgi. 02:30:05 emm, it's maybe a good way. 02:30:50 okay, this performance issue will be the tenth item in this list. 02:31:17 so, if no more plan we want to add, we will jump to next topic. 02:31:41 Can the websocket in zaqar replace the long connection for wsgi? 02:33:14 you mean we suggest to user to use websocket if they want the high performance? 02:33:25 yes 02:33:25 gengchc2_: it could. But websocket in Zaqar is not strong enough and well tested. 02:33:38 ok 02:34:22 wsgi seems to be used more widely. 02:34:49 as a cloud service 02:35:47 okay next topic: meeting time 02:35:55 #topic meeting time 02:36:31 last week, feilong and I discuss the meeting time a little. 02:37:34 do you think it's better to change our meeting time to biweekly? 02:37:37 then , what time do you prefer 02:38:20 I agree 02:38:29 I agree too. 02:38:39 we still hold the meeting at 10:00 UTC+8 in Tuesday 02:38:57 ok 02:39:24 ok 02:39:28 ok 02:39:29 both are OK for me. 02:39:34 sure haha 02:40:20 so, next topic 02:40:30 topic: code review 02:41:10 hope everyone to have more and good reviews in Rocky too. 02:41:19 ok 02:41:23 ok 02:41:44 thanks guys. 02:42:26 last topic, free discuss 02:42:34 #topic free discuss 02:42:46 anything we want to discuss here? 02:43:10 not from me 02:43:23 sure 02:43:33 not from me too. 02:43:39 do you guys go to the summit? 02:44:06 not decided yet 02:44:18 sure, me too 02:45:02 if we can go there, let's drink some beer. 02:45:09 haha 02:45:35 I'll not be there. 02:45:47 :( 02:46:03 next time, you're not go to PTG 02:46:11 go to summit 02:46:13 haha 02:46:24 I wish. 02:46:44 ask for it to your boss, boy! 02:47:03 搬砖少年 02:47:15 hehe 02:48:11 okay, if nothing else want to discuss, we will close this meeting 02:48:15 thanks guys. 02:48:22 thanks 02:48:24 thanks 02:48:33 thanks 02:48:42 #endmeeting