02:21:53 #startmeeting zaqar 02:21:54 Meeting started Tue Aug 14 02:21:53 2018 UTC and is due to finish in 60 minutes. The chair is wanghao. Information about MeetBot at http://wiki.debian.org/MeetBot. 02:21:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 02:21:58 The meeting name has been set to 'zaqar' 02:22:55 First of all, I want to appreciate everyone who still be here to contribute zaqar project. 02:23:33 we all knew that we have a tough time in Rocky cycle. 02:24:27 yeah 02:24:57 gengchgc is still unregitster 02:25:00 So in Stein, we need to regroup our works, our bps, our bug fixes, our reviews. 02:25:17 gecong: okay we can wait him for a while 02:26:12 he may need "/msg NickServ identify " 02:26:27 to identify himself 02:29:15 okay let's go on this 02:30:23 anyway, in this meeting, I just want to mention guys that we could plan and start our works in Steion release. 02:30:40 Not only bps, but also our reviews, 02:30:46 http://stackalytics.com/report/contribution/zaqar-group/30 02:30:51 ok 02:30:53 Here is our review report 02:31:03 https://etherpad.openstack.org/p/zaqar-stein-plan 02:31:16 and our stein work list here ^ 02:31:55 so just pick up your interesting work or new ideas in Zaqar. 02:33:22 okay, so anyone have any suggestions or ideas to our team? 02:33:28 flwang: gecong 02:33:59 Delete message with claim ID 02:34:16 I would like to do this bp 02:34:22 gecong: yeah cool 02:34:47 It seems that /msg NickServ identify is ivalide command 02:35:11 gengchc is still unregisetr 02:35:22 is right? 02:35:27 not sure if we still want to add more functions 02:36:13 i would like to rethink the notification scenario of zaqar 02:36:49 because I believe in the serverless case, user still need the notification service 02:37:54 flwang: so now we have in notification, could fix the serverless case? 02:38:45 we still have some works in notification like topic resource, and email enhancement. 02:41:31 not very familiar with serverless detail, so if there is any request from it. I'd like to discuss it. 02:42:07 not a request, just typical serverless cases 02:42:23 okay 02:43:26 that means when function in serverless done, it need a notification to end user to know that. right? 02:45:39 hi,guys 02:46:03 welcome back gengchc 02:47:23 https://etherpad.openstack.org/p/zaqar-stein-plan 02:48:07 I would like [3.Query queue where the pool] 02:49:06 I participate in [7.Remove pool group totally] 02:49:18 gengchc2_: welcome ! 02:49:24 notification will bridge different funtions 02:49:48 flwang: I see.. 02:50:23 seems now we have in notificaiton could not support this scenario 02:50:59 kind of 02:52:46 this I think it's very useful in real scenario for serverless, combine qinling and zaqar. 02:54:21 What is the architecture of serverless? 02:55:25 not very familiar, but you can know about it from qinling project. 02:56:23 feilong also should go deep into it too. 02:56:52 ok , I will go deep into it later 02:57:02 lingxian and i had a presentation at sydney summit 02:57:09 you can see it on youtube 02:58:47 yeah very interesting topic 02:59:51 flwang: so feilong, you can write your idea about notificaion for serveless scenario in spec? I'm very interesting it too. 03:01:10 not sure if it's suitable to be a spec, but I'm sure that's one of direction to make zaqar more useful in the future 03:01:46 yes 03:02:39 flwang: spec or etherpad just for our discussion, 03:02:56 just want more guys to see the idea. 03:03:10 sure 03:03:16 thanks 03:04:11 gengchc2_: also thanks your work for zaqar, some important works really need to be done in stein. 03:04:25 gecong: you too :) haha 03:04:33 haha 03:05:30 okay, seems time is up. 03:06:04 thanks guys for this meeting, it's a good start in Stein cycle. 03:06:16 thanks 03:06:42 so hope guys to continue your work, and we will discuss the process until next meeting. 03:07:18 ok 03:07:37 #endmeeting