Monday, 2016-06-20

openstackgerritwangxiyuan proposed openstack/zaqar: Let v2 tempest base on the base tests.  https://review.openstack.org/32416101:10
flwangEva-i: ping02:33
flwangKevin_Zheng: ping02:53
Kevin_Zhenghi02:54
Kevin_Zhengflwang: pong02:59
flwangKevin_Zheng: are you still working on the message/claims api ref?03:00
Kevin_ZhengSorry, I was busy on 2 nova BPs03:01
Kevin_Zhengthe deadline is pretty close in nova03:01
Kevin_Zhengfor non-priorities03:02
Kevin_ZhengI will work on it after this week,03:02
flwangKevin_Zheng: ok, then how about i take over the 'claim' part?03:02
Kevin_ZhengOk03:02
flwangyou can still work on the 'message' part03:02
Kevin_ZhengSure03:02
flwangKevin_Zheng: cool03:02
-openstackstatus- NOTICE: static.openstack.org (which hosts logs.openstack.org) is currently migrating due to a hardware failure. It should be back up shortly.03:11
openstackgerritFei Long Wang proposed openstack/zaqar: Add Claims for api ref  https://review.openstack.org/33151604:43
*** flwang1 has quit IRC05:04
-openstackstatus- NOTICE: static.openstack.org (which hosts logs.openstack.org and tarballs.openstack.org among others) is currently being rebuilt. As jobs can not upload logs they are failing with POST_FAILURE. This should be resolved soon. Please do not recheck until then.05:23
*** ChanServ changes topic to "static.openstack.org (which hosts logs.openstack.org and tarballs.openstack.org among others) is currently being rebuilt. As jobs can not upload logs they are failing with POST_FAILURE. This should be resolved soon. Please do not recheck until then."05:23
*** rcernin has joined #openstack-zaqar06:13
*** pcaruana has joined #openstack-zaqar06:24
*** jtomasek has joined #openstack-zaqar07:11
*** Ravikiran_K has joined #openstack-zaqar07:54
*** wxy123 has joined #openstack-zaqar07:54
*** AAzza has quit IRC08:35
*** AAzza has joined #openstack-zaqar08:35
*** flwang1 has joined #openstack-zaqar08:42
*** flwang1 has quit IRC08:53
*** wxy123 has quit IRC09:08
*** wxy123 has joined #openstack-zaqar09:08
*** flwang1 has joined #openstack-zaqar09:13
*** shakamunyi has quit IRC09:48
*** shakamunyi has joined #openstack-zaqar09:56
*** rcernin is now known as rcernin|lunch10:37
*** ChanServ changes topic to "OpenStack Queuing and Notification Service || Smile :D || Meetings every Monday @ 21:00 UTC/15:00 UTC || Wiki: https://wiki.openstack.org/wiki/Zaqar || Paste: http://paste.openstack.org/ || Send messages and make some noise :D"10:40
-openstackstatus- NOTICE: static.openstack.org is back up. If you have POST_FAILURE and are missing logs from your CI jobs, please leave a 'recheck'.10:40
*** Ravikiran_K has quit IRC10:58
*** rcernin|lunch is now known as rcernin11:53
*** ryansb has quit IRC12:20
*** ryansb has joined #openstack-zaqar12:20
*** ryansb has quit IRC12:20
*** ryansb has joined #openstack-zaqar12:20
*** mdnadeem has quit IRC12:28
*** mdnadeem has joined #openstack-zaqar12:30
*** Ravikiran_K has joined #openstack-zaqar12:45
-openstackstatus- NOTICE: OpenID login from review.o.o is experiencing difficulties, possibly due to transatlantic network performance issues. Things are being investigated13:00
*** ChanServ changes topic to "OpenID login from review.o.o is experiencing difficulties, possibly due to transatlantic network performance issues. Things are being investigated"13:00
therveHum, zaqar-server got broken13:07
therveFails with ArgsAlreadyParsedError13:07
thervehttps://review.openstack.org/#/c/327268/ presumably13:08
*** ChanServ changes topic to "OpenStack Queuing and Notification Service || Smile :D || Meetings every Monday @ 21:00 UTC/15:00 UTC || Wiki: https://wiki.openstack.org/wiki/Zaqar || Paste: http://paste.openstack.org/ || Send messages and make some noise :D"13:14
-openstackstatus- NOTICE: OpenID logins are back to normal13:14
openstackgerritThomas Herve proposed openstack/zaqar: Fix config parsing in zaqar-server  https://review.openstack.org/33166813:21
therveflwang, flaper87, vkmc, Eva-i ^^^ please have a look13:22
therveI thought we had a test for the websocket service13:22
therveAh it's the integration tests we don't run anywhere13:24
therveSigh13:24
flaper87therve: +213:24
*** mdnadeem_ has joined #openstack-zaqar13:30
*** mdnadeem has quit IRC13:33
*** eggmaster has joined #openstack-zaqar13:51
openstackgerritThomas Herve proposed openstack/zaqar: Remove leftovers on websocket disconnections  https://review.openstack.org/32689714:25
*** wxy has quit IRC14:30
*** srwilkers has joined #openstack-zaqar14:38
*** srwilkers has quit IRC14:53
*** srwilkers has joined #openstack-zaqar15:03
*** adu has joined #openstack-zaqar15:16
*** srwilkers has quit IRC15:18
*** srwilkers has joined #openstack-zaqar15:19
*** srwilkers has quit IRC15:33
*** srwilkers has joined #openstack-zaqar15:36
*** pcaruana has quit IRC15:45
*** Ravikiran_K has quit IRC15:47
*** rcernin has quit IRC15:55
*** srwilkers has quit IRC15:56
*** adu has quit IRC16:24
*** rcernin has joined #openstack-zaqar16:53
*** rcernin has quit IRC17:18
*** srwilkers has joined #openstack-zaqar17:26
openstackgerritMerged openstack/zaqar-ui: Ability to add and remove subscriptions  https://review.openstack.org/31185217:27
*** tqtran has joined #openstack-zaqar17:29
*** srwilkers has quit IRC17:37
*** ametts has joined #openstack-zaqar17:39
flwang1therve: ping17:45
flwang1reminder: meeting in 15 mins17:45
therveflwang1, Hey17:50
flwang1therve: i'm looking at this patch https://review.openstack.org/33166817:50
flwang1but i don't really understand what's the problem and why it can pass all the tests17:51
therveBecause we don't start zaqar-server in the tests?17:51
flwang1therve: even in the tempest test?17:52
*** rcernin has joined #openstack-zaqar17:52
therveWell we start it but don't rely on it17:52
therveflwang1, http://logs.openstack.org/97/326897/3/check/gate-tempest-dsvm-mongodb-zaqar/0ec42cf/logs/screen-zaqar-websocket.txt.gz is the error17:52
therveThe tempest tests probably use devstack so uwsgi17:53
therveWe would need to run the integration tests somewhere, but we don't17:53
therve(which is probably on me as I introduced them)17:53
flwang1therve: ah, i see.17:53
flwang1we're using uwsgi to start app directly17:54
therveYeah. But websocket needs zaqar-server17:55
flwang1yep, i see. so it only impact websocket17:55
flwang1and in tempest, we're not testing websocket :(17:56
therve"only" !!!!!17:56
therve:D17:56
flwang1sorry, i shouldn't use 'only' :D17:56
therveWell it impacts everything that uses zaqar-server, which only ought to be websocket17:56
therveBasically the patch merged was completely broken, which is unfortunate17:57
flwang1therve: that's my fault17:58
therveOnly partly :)17:58
flwang1one thing weird is tripleo is using websocket17:59
flwang1how can the author submit pass the test locally?18:00
flwang1meeting, ttyl18:00
therveI don't think the author run tripleo tests18:01
therveAnd I don't know if tripleo has websocket tests areadly, it probably doesn't18:01
flwang1therve: tripleo is using zaqar's websocket, so i assume he did test before posting18:04
flwang1anyhow18:04
*** jtomasek has quit IRC18:09
* flwang1 feel lonely since only me in the openstack-meeting-3 channel :(18:09
therveHeh18:15
flwang1i have cancelled the meeting so i'm free for any chat :D18:17
*** shakamunyi has quit IRC18:17
openstackgerritMerged openstack/zaqar: Fix config parsing in zaqar-server  https://review.openstack.org/33166818:24
openstackgerritFei Long Wang proposed openstack/zaqar: Add Claims for api ref  https://review.openstack.org/33151618:26
*** srwilkers has joined #openstack-zaqar18:37
flwang1eggmaster: ping18:45
*** srwilkers has quit IRC19:16
eggmasterflwang1: pong19:34
*** flwang1 has quit IRC19:39
*** rcernin has quit IRC20:31
*** Eva-i has quit IRC20:41
flwangtherve: back?21:13
*** flwang1 has joined #openstack-zaqar21:22
openstackgerritFei Long Wang proposed openstack/zaqar: Fix debug log missing issue  https://review.openstack.org/33185421:40
flwangtherve: https://review.openstack.org/33185421:45
therveflwang, Yeah21:57
flwangtherve: see above patch21:57
flwangthat's another regression issue after we moving the cli option21:57
flwangall the debug log have gone21:57
therveflwang, So moving the log.setup after the conf parsing seems to work too21:59
therveIt may be a better idea to keep it contained in the the server cmd22:00
flwangyou mean put it at line 49 https://review.openstack.org/#/c/331854/1/zaqar/cmd/server.py ?22:00
flwangit should work, i think22:00
flwanglet me give it atry22:00
therveYep I mean that22:01
flwangyep, it works, i will upload a new patchset22:02
openstackgerritFei Long Wang proposed openstack/zaqar: Fix debug log missing issue  https://review.openstack.org/33185422:02
flwangtherve: would you mind +1ing it?22:02
therveDone22:02
flwangtherve: cool. btw, are you interested in proposing a breakout session about the aodh + zaqar + mistral + heat + senlin?22:03
therveI don't know22:04
therveWhat's a breakout session22:04
flwanga session on openstack summit22:04
flwanghttps://www.openstack.org/summit/barcelona-2016/call-for-presentations/22:05
therveNot really22:07
flwangtherve: ok, no problem22:07
flwangtherve: feel free let me know if you need help for your patch https://review.openstack.org/#/c/329520/22:09
therveI'm okay I think, just need a good amount of tests and cleanups22:10
flwangtherve: cool22:10
flwangfor now, when aodh trigger the webhook of heat, does heat need a token?22:11
therveaodh has a trust webhook as well22:11
therveSo yeah it gets a token22:12
flwangtherve: ok, i see. so can you see any benefit if we use zaqar between aodh and heat for autoscaling?22:13
flwangand should we still prompt heat's autoscaling if you guys are planing to move it out?22:14
therveI don't think we plan to move it out22:14
therveWe still need some kind of trigger22:14
flwang'move out' maybe not a good word22:15
therveHaving zaqar between aodh and heat could have some benefit if we rewrote some of the logic to take into account message that we lose22:15
therveBTW zaqar support in aodh is totally dumb right now22:15
therveI'm not sure we want to advocate it22:16
flwanglast time, when i asked this topic with stevebaker and Zane bitter. I was told auto scaling wont' be the focus on heat22:16
therveRigh22:17
therveRight22:17
therveMoving it out is another topic22:17
stevebakerwell, we'd rather delegate to a dedicated autoscaling service22:17
flwangi see. forgive my bad english22:17
flwangtherve: what do you mean 'dumb'?22:18
flwangtherve: do you mean it has bug so totally doesn't work?22:18
therveflwang, It uses the service user22:18
therveSo the queue is just not accessible22:18
thervestevebaker, Yeah but we probably need some knobs in Heat anyway22:19
flwangtherve: ah, yes. but IIRC, it's using correct tenant, i will take a look22:19
flwangtherve: stevebaker: IMHO, zaqar could be a good broker for the auto scaling in openstack22:20
therveAFAICT it's not22:20
flwangtherve: ok, thanks for the heads up, i will take a look at that22:20
flwangwhat i want to figure out is what's the correct direction for the auto scaling in openstack22:21
flwangso that i can know how can zaqar/i help22:21
flwangcan you guys give me some ideas?22:21
therveI'd say talk to the Senlin guys22:22
therveI tried working on autoscaling for a year and barely manage to do anything, so it's somewhat beyond me :)22:23
flwangtherve: senlin is still using a hook which even doesn't need a token22:24
therveThey use ec2 signature?22:24
flwanguse a confidential UUID22:25
therveMeh that's fine22:26
flwangok22:27
*** ametts has quit IRC22:27
flwangtherve: i just reviewed the aodh zaqar notifier code again22:31
flwangand i can remember now22:31
flwangyep, it's using service tenant and user, but it's creating queues for different tenants22:31
therveWhat do you mean?22:33
flwangok, it's not accurate22:34
flwangit's creating queues with alarm-id + topic22:34
flwangand i understand your concern22:36
flwangfrom the end user's view, they can't create an alarm and subscribe the queue for mistral22:37
flwangsince they don't know the queue name22:37
therveflwang, They can't access the queue anyway?22:37
therveEven if they knew the name it's not in their project22:37
flwangyes22:37
flwangif we can get the project name/id for the alarm, i think we can create the correct client with the project info22:38
flwangthe author discussed with me and they prefer to use this way22:39
flwangit works for current alarms distribution22:39
flwangbut it's not enough for the aodh -> zaqar -> mistral22:39
flwangis that your concern?22:40
therveIt seems that it uses the subscription mechanism to work around that22:40
therveIt may actually be broken because it uses strange configuration names22:41
therveI wonder if anyone ever tested it :)22:41
flwangso technically, if we can create an alarm in aodh with mistral url as the subscriber, then it should work i think22:43
therveProbably not because you can't specify the post body22:43
flwangthe only thing is it doesn't support the post body22:43
flwangyes22:43
flwangthat's what i'm talking :)22:44
flwangi can propose a fix for that and test it in one shot :)22:44
flwangwhich could be a follow up patch along with your patch22:45
therveYou can't do that in aodh though22:46
therveWhat would be better, IMO, is 1) Don't generate the queue name just post straight to the given queue22:47
therve2) Use signed url so that we post to the correct project22:47
therve3) Remove that subscription stuff which is too limited anyway22:47
therveIf the queue is not dynamic, you can now create a proper subscription with a post body with my patch22:48
flwangtherve: but the problem is they(aodh) don't want to change any existing code22:52
therveDon't they? If we can tell them that it doesn't work that could convince them :)22:53
flwang1) when you say "don't geneate queue name", did you mean passing a queue name when creating alarm?22:54
therveYeah instead of using the topic as postfix, use it directly22:55
flwangthat could be a pre-signed url you mentioned in 2), is it?22:55
flwangwhen you say remove the 'subscription stuff', do you mean user have to create subscriptions in zaqar manually?22:56
therveYes22:56
flwanghmm...22:57
flwangif so, the alarm creation is not completed from the aodh's view22:58
flwangam i missing something?22:58
therveWhy?22:58
flwangthat said, after created the alarm,  user's targets can't be notified22:59
flwangunless user create the subscriptions in zaqar manually22:59
flwangmaybe my understanding is wrong, not an aodh expert23:00
therveI don't see why that's a problem to create the subscription23:00
therveYou don't even have to do it after creating the alarm, you can do it before if you want to remove the race condition23:00
flwangwhen creating alarm, user will pass in the webhook/email/whatever they want to be notified/triggered, right?23:01
therveNo they will pass the zaqar queue23:01
flwangok, i know that works23:01
flwangmy point is23:01
flwangis it consistent with current alarms behaviour?23:01
therveWhy not?23:02
therveOK got to go23:06
flwangok, thanks therve, ttyl23:08

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