Wednesday, 2017-03-29

*** wanghao has joined #openstack-zaqar00:15
openstackgerritMerged openstack/zaqar-ui master: Imported Translations from Zanata  https://review.openstack.org/44945901:02
*** yanyanhu has joined #openstack-zaqar01:26
*** zhurong has joined #openstack-zaqar02:04
*** mpanetta has quit IRC02:05
*** mpanetta has joined #openstack-zaqar02:06
*** wanghao has quit IRC03:02
*** wanghao has joined #openstack-zaqar03:03
openstackgerritFeilong Wang proposed openstack/zaqar master: Using generic instead of v3 for identity  https://review.openstack.org/45115403:08
flwangwxy_: ping03:08
wxy_flwang, here03:09
flwangwxy_: see this https://review.openstack.org/451090 ?03:09
*** wanghao_ has joined #openstack-zaqar03:10
wxy_flwang, yeah, I'm fixing the test now.03:10
flwangwxy_: cool03:12
flwangI checked keystone config03:12
flwangkeystone doesn't use the 'enabled' as well03:12
*** wanghao has quit IRC03:13
flwangbtw, i'm testing the performance of swift03:14
flwangand i found it's very slow than mongo03:15
wxy_flwang, have you found some reason?03:25
flwangyou mean the swift driver?03:27
flwangi think it just because the communication is http :( it's slow03:27
flwangwxy_: have you found the reason why https://review.openstack.org/#/c/451090/ failed ?03:47
wxy_yeah03:48
flwangcool03:49
wxy_flwang, But I'm not suer it's related to the falcon or cors.03:51
flwangoh, really?03:51
wxy_flwang, fixing now.03:51
flwanginteresting03:51
flwangwxy_: feel free to upload patch set on my patch03:51
wxy_flwang, ok03:52
wxy_flwang, such as zaqar.tests.unit.transport.wsgi.v2_0.test_messages L39003:52
wxy_flwang, the value of "self.srmock.headers_dict['location']" is changed. So the test failed.03:53
wxy_flwang, before is "v2/xxxx", now is "http://www.xx.org/v2/xxxx"03:53
flwangah, because the cors is impacting the location?03:54
wxy_flwang, Perhaps, or falcon's test frame03:56
wxy_flwang, I'll try to fix it today.03:56
flwangok, thanks03:57
*** flwang1 has quit IRC04:05
openstackgerritwangxiyuan proposed openstack/zaqar master: Remove enabled option for CORS  https://review.openstack.org/45109004:14
*** XueFeng has joined #openstack-zaqar04:52
*** flwang1 has joined #openstack-zaqar05:21
*** nadya has joined #openstack-zaqar05:38
*** rcernin has joined #openstack-zaqar05:39
*** nadya has quit IRC05:41
*** XueFeng has quit IRC05:44
openstackgerritwanghao proposed openstack/zaqar-specs master: Service Queue in Zaqar  https://review.openstack.org/44943305:53
*** zhurong has quit IRC05:54
*** pcaruana has joined #openstack-zaqar06:24
openstackgerritwanghao proposed openstack/zaqar-specs master: Service Queue in Zaqar  https://review.openstack.org/44943306:46
*** XueFeng has joined #openstack-zaqar06:50
*** tesseract has joined #openstack-zaqar07:14
*** amoralej|off is now known as amoralej07:24
openstackgerritwangxiyuan proposed openstack/zaqar master: Remove enabled option for CORS  https://review.openstack.org/45109007:34
*** zhurong has joined #openstack-zaqar07:34
*** flwang1 has quit IRC07:35
*** nadya has joined #openstack-zaqar08:22
*** wanghao has joined #openstack-zaqar08:25
*** wanghao_ has quit IRC08:27
thervewanghao, Let me know if you want to chat about the service queue spec08:29
wanghaotherve: sure08:30
therveDon't hesitate to write stuff in that etherpad, too08:31
wanghaotherve: okay08:32
wanghaothe use case can be updated to BP in launchpad.08:33
wanghaoI'll do it.08:33
therveIs there something in launchpad?08:33
therveI couldn't find it08:33
wanghaohere is bp link: https://blueprints.launchpad.net/zaqar/+spec/service-queue-in-zaqar08:37
wanghaoI saw your etherpad too,  that's a good place we can talk about this feature.08:37
wanghaoI'm reading it now,  some stuff will be there later.08:42
thervewanghao, Your spec should use that name in the "Implements", FWIW08:57
wanghaotherve: yeah,  I changed the name today, must forget to update it.08:58
therveOK08:58
wanghaotherve: some thoughts be the etherpad, btw.08:58
thervewanghao, I understand you last thought, but it needs to be much more details on how it works08:59
therve"user query queues with his own token" That only works for queue list. What happens when you get messages from the service queue?09:00
wanghaotherve: en, since an arg is the queue_name when getting messages,  Zaqar will find the queue is not belong to user's project but the queue is a service queue. that will allow zaqar to return messages to user.09:03
wanghaotherve: do you think it works?09:04
thervewanghao, There is an order issue here. Authentication happens first. We only get to the queue controller *after*09:06
therveI don't understand how " Zaqar will find the queue is not belong to user's project" works09:06
therveIt's possible it's simple, but you need to explain it to me :)09:08
wanghaotherve: it like this: user with his own token, and get it wrong queue name,  that'll pass the authentication, right.09:14
wanghaotherve: Zaqar will return HTTP not found now.09:15
thervewanghao, Yeah09:15
therveI think I see where you're going, and I don't like it :)09:15
therveYou mean every time we don't find a queue, we look in the service project to find if the queue exists?09:16
wanghaotherve: em, we find the service queue with the name if it didn't belong to user.09:17
thervewanghao, What if you have a queue with the same name in your project?09:17
wanghaotherve: yes, that is a problem...09:19
therveOK, so I'm glad we talked about it, because I don't think it's the proper solution :)09:19
thervewanghao, We should remove the ambiguity, and have the user says "I want queue X in project Y", and manage the authorization ourselves, I think09:20
wanghaotherve: yes, I'll think it more.09:23
thervewanghao, It's a little bit tricky, because I believe if we reuse X-PROJECT-ID, the keystone middleware will reject the auth09:24
thervewanghao, Maybe use a new header for that purpose09:24
wanghaotherve: emm, you mean user bring service project id in new header?09:29
thervewanghao, Yeah, or simply a header saying "I want a service queue"09:30
therveWe can manage the translation server side09:30
wanghaotherve: or we need a new api,  just need project own by user and project own by service.09:30
therveYeah that's an option. There are pros and cons to both approaches09:31
wanghaotherve: yes, do you think we need to know user want which project's service queue.09:33
thervewanghao, I think so, unless omitting it has a benefit that I don't see09:35
wanghaotherve: okay, that's great to discuss this with you,  I'll update our ideas to spec.09:36
therveThanks!09:36
wanghaotherve: thank you too :)09:42
openstackgerritShu Muto proposed openstack/zaqar-ui master: Use common Angular view for Queues panel  https://review.openstack.org/43342909:45
*** yanyanhu has quit IRC09:51
*** yanyanhu has joined #openstack-zaqar09:52
*** XueFeng has quit IRC10:17
*** yanyanhu has quit IRC10:23
*** stanchan has quit IRC10:48
*** nadya has quit IRC11:00
*** zhurong has quit IRC11:34
*** nadya has joined #openstack-zaqar11:52
*** amoralej is now known as amoralej|lunch11:56
*** wanghao has quit IRC12:21
*** wanghao has joined #openstack-zaqar12:21
*** wanghao has quit IRC12:21
*** wanghao has joined #openstack-zaqar12:22
*** wanghao has quit IRC12:22
*** wanghao has joined #openstack-zaqar12:22
*** wanghao has quit IRC12:23
*** wanghao has joined #openstack-zaqar12:24
*** wanghao has quit IRC12:24
*** wanghao has joined #openstack-zaqar12:24
*** wanghao has quit IRC12:24
*** wanghao has joined #openstack-zaqar12:25
*** wanghao has quit IRC12:25
*** wanghao has joined #openstack-zaqar12:26
*** wanghao has quit IRC12:26
*** wanghao has joined #openstack-zaqar12:26
*** wanghao has quit IRC12:27
*** wanghao has joined #openstack-zaqar12:27
*** wanghao has quit IRC12:28
*** wanghao has joined #openstack-zaqar12:28
*** wanghao has quit IRC12:28
*** nadya has quit IRC12:38
*** wanghao has joined #openstack-zaqar12:59
*** amoralej|lunch is now known as amoralej13:17
*** zhurong has joined #openstack-zaqar13:21
*** mpanetta has quit IRC13:33
*** mpanetta has joined #openstack-zaqar13:33
*** zhurong_ has joined #openstack-zaqar14:06
*** zhurong has quit IRC14:07
*** nadya has joined #openstack-zaqar14:09
*** zhurong_ has quit IRC14:18
*** wanghao has quit IRC14:49
*** rcernin has quit IRC15:05
*** wxy| has joined #openstack-zaqar15:09
*** eliqiao has quit IRC15:33
*** eliqiao has joined #openstack-zaqar15:37
*** eliqiao has quit IRC15:46
*** eliqiao has joined #openstack-zaqar15:53
*** tesseract has quit IRC15:58
*** nadya has quit IRC16:04
*** wxy_ has quit IRC16:24
*** wxy| has quit IRC16:37
*** nadya has joined #openstack-zaqar16:42
*** nadya has quit IRC16:46
*** nadya has joined #openstack-zaqar16:46
*** eliqiao has quit IRC17:01
*** eliqiao has joined #openstack-zaqar17:02
*** mpanetta has quit IRC17:12
*** mpanetta has joined #openstack-zaqar17:13
*** nadya has quit IRC17:18
*** flwang1 has joined #openstack-zaqar17:47
*** eliqiao has quit IRC17:49
*** eliqiao has joined #openstack-zaqar17:50
*** pcaruana has quit IRC17:52
*** amoralej is now known as amoralej|off18:07
*** nadya has joined #openstack-zaqar18:07
*** rbrady is now known as rbrady-afk18:12
*** nadya has quit IRC18:13
*** openstackstatus has joined #openstack-zaqar18:45
*** ChanServ sets mode: +v openstackstatus18:45
*** flwang1 has quit IRC19:26
*** eliqiao has quit IRC19:28
*** openstackgerrit has quit IRC19:33
*** eliqiao has joined #openstack-zaqar19:33
*** flwang1 has joined #openstack-zaqar20:24
*** Guest6666 has quit IRC20:28
*** Guest6666 has joined #openstack-zaqar20:29
flwangtherve: around?21:23
flwangtherve: are you available for a talk about swift driver?21:23
therveflwang, Yep21:34
flwangcool21:35
flwangi just done some tests with the swift driver21:35
flwangand i got some numbers you may be interested in21:35
flwanggenerally the mongo driver will take about 50-80ms for a post request21:36
flwangswift driver needs to take 280-320ms for a same request21:36
*** rbrady-afk is now known as rbrady21:36
flwangi know it's a very rough test with osprofiler21:36
flwangbut it just gives me some ideas21:37
therveOK, that's not too bad21:37
flwangso do you think if there is anything we can do to improve the performance of swift driver21:37
therveI'm not sure there is much we can do21:38
therveI'd have to check with the swift guys21:38
therveI don't think it supports many advanced features like pipelining21:39
thervePossibly if we can make auth faster that would speed things up21:39
flwangright21:42
flwangand with the swift driver, could i use the zaqar user and service tenant in the uri?21:43
flwangin my test, seems it doesn't work well21:44
therveYeah? That's what devstack uses IIRC21:45
therveYou're probably just missing a role21:45
flwangthe reseller role?21:45
flwangok, i will double check it21:46
flwangand another thing i found is, after the TTL, the object/message has gone, but you can still see it when list the queue, are you aware of it?21:46
therveYeah I think it's handled in the code21:47
therveYou mean when you do message list? Maybe I missed the check somewhere21:48
flwangwith openstack object show you got 404, it's right21:48
flwangbut you can see the object by openstack object list21:49
flwangi will test it again and open a bug if it's reproducable21:49
flwangtherve: and as for this, https://etherpad.openstack.org/p/zaqar-service-queue do you think overall it's a useful, it's trying to do the similar thing like Nabu21:50
therveYeah sure it's not like nabu got any traction :)21:51
flwanghah21:52
therveThe spec needs way more details though21:52
flwangif we can get it in zaqar, then we can easily write a publisher in ceilometer or searchlight to forward notifications21:52
therveNot sure what you mean. Get nabu in zaqar?21:54
flwangi mean service queue21:55
flwangsorry21:55
therveOK sure21:57
therveYeah that's fine, we need to flash out how that works21:57
therveIt's still not clear to me how that would look like21:57
flwangin my mind, it means service user can create queue in tenant's project to forward messages21:59
flwangwe just need to sort the auth problem out21:59
therveYeah that's not what I'm thinking, so you need to convince me :)22:00
therveJust name collision in the user project is tricky22:01
therve(IE IMO it's much easier to allow user to do reads in the service project, than to allow services to do writes in the user project)22:02
flwangha, but put all the queues in service tenant, we may have to handle the quota, billing stuff22:06
flwangthough it's not a real problem for zaqar22:06
flwangwe just hand off the problem to the others22:06
flwangbut i can see the pros of put queues in service tennat22:07
therveBilling uses for infrastructure is kind of fishy22:07
flwangso basically, you like the idea, but you just want to keep the queues in service tenant and let tenant user can access them, right?22:07
therveYou can still bill them for Zaqar API usage22:07
flwangright22:08
therveThat seems easier to achieve to me22:08
flwangand that's most of the messaging services are doing22:08
flwangI don't really mind doing that in service tenant22:08
therveIn any case, we need a precise plan :)22:10
flwangagree22:10
flwangi'm really happy to see you're interested in this spec22:10
therveI mean that's a use case I'd like to see in OpenStack since forever22:12
flwanghah22:13
flwangif so, i will do my best to get it in22:13
*** rbrady is now known as rbrady-afk22:44
*** mpanetta has quit IRC23:27
*** stanchan has joined #openstack-zaqar23:30

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!