02:00:15 <flwang> #startmeeting zaqar
02:00:16 <openstack> Meeting started Tue Sep 19 02:00:15 2017 UTC and is due to finish in 60 minutes.  The chair is flwang. Information about MeetBot at http://wiki.debian.org/MeetBot.
02:00:17 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
02:00:19 <openstack> The meeting name has been set to 'zaqar'
02:00:35 <flwang> #topic roll call
02:00:53 <flwang> any zaqar team member around?
02:00:57 <wanghao_> here
02:01:18 <flwang> wanghao_: only you and me?
02:01:28 <wanghao_> flwang: not sure....
02:02:01 <wanghao_> flwang: seems only us
02:02:04 <flwang> wanghao_: ok, i'd like to know the progress of pool group deprecation and redis mgmt support
02:02:46 <wanghao_> flwang: sure,  gecong and I have updated the spec of pool group deprecation
02:03:13 <flwang> wanghao_: we need to think about how to support the migration of mongodb
02:03:39 <flwang> we may have to provide a script or something to help end user to do that
02:03:48 <wanghao_> flwang: yes,  the raw idea of mine is adding a python script.
02:04:31 <flwang> given it's an admin function, so it won't introduce any downtime here
02:04:32 <wanghao_> after user upgrade Zaqar to Queens, they need to run the script at first.
02:05:09 <wanghao_> flwang: sure
02:05:27 <flwang> cool
02:06:17 <wanghao_> flwang: btw,  it will not be a backward compatible changes.
02:06:22 <flwang> pls update the spec accordingly
02:06:28 <flwang> why?
02:06:52 <wanghao_> flwang: since operator need to mirgate the data after upgrade to Queens.
02:07:31 <wanghao_> and they can't specify pool group in API anymore from Queens.
02:08:10 <flwang> if so, could you please add the api change as well so that i can get a better understanding?
02:08:45 <wanghao_> sure, will update the spec.
02:09:54 <flwang> aewsome
02:10:28 <wanghao_> another thing is the server queue.
02:10:49 <flwang> yep
02:11:22 <wanghao_> if use trust token, that Zaqar didn't need to do anything.
02:12:05 <flwang> have you chatted with zhang lei ?
02:12:11 <flwang> and did he test that?
02:12:39 <wanghao_> yes,  he said he will see the review comment about the trust token.
02:12:54 <wanghao_> but there is no more news from him for a while.
02:13:07 <wanghao_> I will contact him later.
02:13:12 <flwang> ok, thanks
02:13:22 <flwang> and I really appreciate for your effort on this work
02:14:06 <wanghao_> np,  it's an interesting case for Zaqar and Searchlight,  I'd like it.
02:14:10 <flwang> and i'm very happy to see you're working well with gecong
02:14:44 <wanghao_> thanks
02:15:09 <wanghao_> I'm also glad to work with gecong. : )
02:17:32 <flwang> anything else from your side?
02:18:27 <wanghao_> emm, not special,  will commit some spec for Queens,  I write it in our etherpad of queens plan
02:18:44 <flwang> wanghao_: nice
02:19:17 <flwang> as I said before, in this cycle, i won't pick up any feature work, just review and think about how to improve the performance
02:19:47 <gecong> it seem that all the project use gate-tripleo-ci-centos-7-scenario002-multinode-oooq-puppet-nv has fail
02:20:05 <wanghao_> flwang: cool
02:20:27 <gecong> TestVolumeBootPattern fails
02:20:34 <flwang> gecong: ok, that's alright
02:20:48 <flwang> if that's the case, then we can merge the patch
02:21:02 <flwang> gecong: anything else you want to discuss in the meeting?
02:21:08 <gecong> I have no idea what happens
02:21:40 <flwang> haha
02:21:53 <wanghao_> flwang: I will commit a bp that is about improving the performace,  Token Session in Zaqar. gecong will work with me.
02:21:55 <flwang> gecong: ok, i have a question about your benchmarking test
02:21:55 <gecong> when will we begin to do our bp
02:22:04 <flwang> wanghao_: fantastic
02:22:19 <flwang> that's the thing i'd like to do
02:22:23 <wanghao_> flwang: thanks
02:22:28 <gecong> yeah
02:22:35 <flwang> can you explain more about the token session?
02:23:34 <wanghao_> flwang: okay,  the basic idea is Zaqar can support to verify the token with with keytone once, and keep this token valid for a while that means
02:23:41 <wanghao_> no need to verity the token again.
02:24:17 <wanghao_> so that we can save some time for validation with keystone.
02:24:37 <gecong> cool
02:24:59 <flwang> wanghao_: is there any other service doing that?
02:25:13 <wanghao_> flwang: I think not yet.
02:25:24 <flwang> i'm just curious if it's a common/workable approach or we have to do some creative work
02:26:13 <wanghao_> I think we will do it first.
02:27:11 <wanghao_> it's a raw idea,  we can talk about it open.
02:27:43 <flwang> ok, cool
02:27:57 <gecong> flwang : what about benchmarking test? thanks
02:28:06 <flwang> i think there is not much services in openstack caring about performance like Zaqar
02:28:22 <wanghao_> flwang: agree
02:28:23 <flwang> so we have to definitely do something innovation work
02:28:41 <flwang> gecong: you guys mentioned there are some 503 error when using redis driver
02:28:56 <gecong> yes , we are working on it
02:29:00 <flwang> i'm interested in what is it?
02:29:04 <flwang> cool
02:29:51 <gecong> yesterday we find that upack is wrong
02:29:55 <flwang> any people working on the idea of creating a new resource 'topic'?
02:30:11 <gecong> we will di it today, me and gengchc
02:30:22 <flwang> so that we can make the notification service more isolated
02:31:02 <wanghao_> flwang: I'd like to do it
02:31:17 <wanghao_> flwang: and wxy may be here too.
02:31:36 <flwang> i'm not really sure if we should split the notification service out of current zaqar-server process/service
02:31:47 <flwang> but having a 'topic' resource could be a good start
02:32:46 <wanghao_> flwang: I'd be kind of dislike to split the notification service from Zaqar-server.
02:33:00 <gecong> we can work with you about topic wanghao gengchc
02:33:14 <wanghao_> gecong: cool thanks
02:33:39 <flwang> great
02:33:46 <wanghao_> flwang: but adding topic that is necessary
02:34:18 <flwang> a tiny improvement i'd like to do in queens is, the metadata/optioins consistency
02:35:18 <wanghao_> yes
02:35:36 <wanghao_> seems wxy will do that
02:35:38 <flwang> using 'metadata' for queue and 'options' for subscriptions make me uncomfortable
02:36:06 <wanghao_> emm, it's
02:37:18 <flwang> but i don't have a strong feeling how to change it ;(
02:37:20 <flwang> will see
02:37:55 <wanghao_> using metadata in subscription also feel weried a little.
02:39:04 <wanghao_> and we may will keep options in Queens at least, for backward compatiable.
02:42:01 <wanghao_> flwang: you can put your idea on out etherpad.
02:44:56 <flwang> yep
02:45:06 <flwang> hence why i don't have a good idea now :)
02:45:10 <flwang> ok
02:45:20 <flwang> anything else?
02:45:45 <wanghao_> not from me
02:45:54 <gecong> no from me
02:46:11 <gengchc2> After removing the poolgroup, I have some questions about the api design, I think out two designs. Are there better designs? In https://review.openstack.org/#/c/345133/15
02:47:22 <flwang> ok, i will review it
02:47:23 <wanghao_> gengchc2: I will check it out later.
02:47:31 <gecong> ok
02:47:36 <gengchc2> ok
02:47:39 <flwang> now i'm going to close this meeting, thanks for joining
02:47:52 <flwang> #endmeeting