Wednesday, 2016-05-18

*** shu-mutou-AFK is now known as shu-mutou00:05
Eva-iflwang: many patches I made recently didn't required much patch sets and reviewing, so maybe they're good. Maybe this one will be good too. I don't know.00:07
Eva-iflwang: if I understand correctly, when pooling is enabled in Zaqar, the configuration options section [drivers:message_store:mongodb] isn't used, right?00:14
*** tqtran has quit IRC00:45
Eva-iryansb: hello. Maybe you know ^?00:49
flwangEva-i: yes00:51
flwangEva-i: if the pooling is enabled, then messages will go into pools00:51
Eva-iflwang: oki, thank you00:52
flwangEva-i: can you give this a quick review https://review.openstack.org/#/c/317116/ ?00:52
flwangit fixes the rally job00:52
Eva-iflwang: no, I don't like this fix00:53
flwangEva-i: why?00:53
Eva-iflwang: it doesn't solve the real cause. The real problem will still exist in keystone client after merge of this patch. What if real users will have such load on zaqar and it will fail their expectations? I find it good that this test loads zaqar enough for it fail. As long as it fails, there's a reminder that something has to be fixed in keystone client.00:59
flwangEva-i: you're point does make sense, but that also means if we leave it as failed, we also can't test any performance of zaqar, see my point?01:02
flwangsince you won't open it the link anymore01:02
Eva-iflwang: I don't find rally job critical, because it only tests queues now. I find the problem in keystone/rally/apache/devstack critical, and we better not close our eyes on it.01:09
Eva-iflwang: my bug report should be updated, it's invalid now: https://bugs.launchpad.net/python-keystoneclient/+bug/1544839. I don't have time to find where's the real cause of such behavior.01:10
openstackLaunchpad bug 1544839 in python-keystoneclient "Job gate-rally-dsvm-zaqar-zaqar fails since the recent Rally patch" [Undecided,Incomplete]01:10
Eva-iMaybe it's not in keystone client, as commenters say01:12
flwangEva-i: so it's a apache config issue of devstack?01:14
Eva-iflwang: maybe01:14
Eva-iflwang: one of the commenters says this01:15
Eva-iflwang: but someone else has to check01:15
-openstackstatus- NOTICE: Gerrit is about to be restarted to help with page timeouts01:47
flwangEva-i: ok, i will leave it a while01:50
*** mpanetta_ has joined #openstack-zaqar01:57
*** mpanetta_ has quit IRC02:01
openstackgerritEva Balycheva proposed openstack/zaqar: DNM: Zaqar production installation guide - old  https://review.openstack.org/26885102:11
openstackgerritEva Balycheva proposed openstack/zaqar: Add Zaqar production installation guide  https://review.openstack.org/26885102:13
*** lei-zh has joined #openstack-zaqar02:16
Eva-iflwang: finally uploaded install guide. =) It is up-to-date and working, Though doc team will probably find many style problems if I try to upload it to the official place.02:25
flwangEva-i: we may keep it in our tree based on the new way02:30
Eva-iflwang: install guides will be hosted in project repos, right?02:32
flwangi think so02:34
*** mdnadeem has joined #openstack-zaqar02:51
*** njohnston-- is now known as njohnston__03:54
*** njohnston__ has quit IRC03:56
*** njohnsto_ has joined #openstack-zaqar03:57
*** njohnsto_ is now known as njohnston__03:57
*** flwang1 has quit IRC04:58
*** njohnston__ has quit IRC05:01
*** njohnsto_ has joined #openstack-zaqar05:08
*** njohnsto_ has quit IRC05:17
*** rcernin has joined #openstack-zaqar05:47
*** david-lyle has quit IRC06:05
*** njohnsto_ has joined #openstack-zaqar06:14
*** njohnsto_ has quit IRC06:19
*** jtomasek has joined #openstack-zaqar06:45
*** rcernin has quit IRC06:47
*** prashanthraghu has joined #openstack-zaqar06:47
*** rcernin has joined #openstack-zaqar06:51
*** dynarro has joined #openstack-zaqar07:18
*** AAzza has quit IRC07:35
*** david-lyle has joined #openstack-zaqar07:57
*** mpanetta_ has joined #openstack-zaqar07:59
*** mpanetta_ has quit IRC08:04
*** AAzza has joined #openstack-zaqar08:10
*** njohnsto_ has joined #openstack-zaqar08:16
*** njohnsto_ has quit IRC08:20
*** dynarro has quit IRC08:32
*** prashanthraghu has quit IRC08:38
*** vipuls has joined #openstack-zaqar08:42
*** Kevin_Zheng_ has joined #openstack-zaqar08:42
*** kgriffs_alt has joined #openstack-zaqar08:45
*** ameade has quit IRC08:45
*** vipul- has quit IRC08:45
*** kgriffs has quit IRC08:45
*** Kevin_Zheng has quit IRC08:45
*** odyssey4me has quit IRC08:45
*** david_cu has quit IRC08:45
*** vkmc has quit IRC08:45
*** vkmc has joined #openstack-zaqar08:45
*** vkmc has quit IRC08:45
*** vkmc has joined #openstack-zaqar08:45
*** kgriffs_alt is now known as kgriffs08:46
*** Kevin_Zheng_ is now known as Kevin_Zheng08:46
*** odyssey4me has joined #openstack-zaqar08:46
*** kong has quit IRC08:48
*** wxy has quit IRC08:49
*** ameade has joined #openstack-zaqar08:55
*** kong has joined #openstack-zaqar08:56
*** wxy has joined #openstack-zaqar09:03
openstackgerritwangxiyuan proposed openstack/zaqar: Make the notifier max_workers configurable  https://review.openstack.org/30844309:10
*** prashanthraghu has joined #openstack-zaqar09:15
*** Kevin_Zheng has quit IRC09:16
*** Kevin_Zheng has joined #openstack-zaqar09:21
*** shu-mutou is now known as shu-mutou-AFK10:17
*** lei-zh has quit IRC10:21
*** AAzza has quit IRC10:50
*** AAzza has joined #openstack-zaqar10:50
*** GB21 has joined #openstack-zaqar11:02
*** Kevin_Zheng has quit IRC11:11
*** njohnsto_ has joined #openstack-zaqar11:13
*** njohnsto_ has quit IRC11:18
*** njohnsto_ has joined #openstack-zaqar11:27
*** GB21 has quit IRC11:32
*** GB21 has joined #openstack-zaqar11:33
*** prashanthraghu has quit IRC11:49
*** mpanetta_ has joined #openstack-zaqar12:00
*** mpanetta_ has quit IRC12:05
*** prashanthraghu has joined #openstack-zaqar12:18
*** GB21 has quit IRC12:19
*** njohnsto_ has quit IRC12:29
*** Kevin_Zheng has joined #openstack-zaqar12:46
*** njohnsto- has joined #openstack-zaqar13:05
*** njohnsto- is now known as njohnston--13:06
*** dynarro has joined #openstack-zaqar13:30
*** ametts has joined #openstack-zaqar13:49
*** prashanthraghu has quit IRC13:50
*** njohnston-- is now known as njohnston__14:00
*** mpanetta_ has joined #openstack-zaqar14:01
*** mpanetta_ has quit IRC14:01
*** mpanetta_ has joined #openstack-zaqar14:02
*** dynarro has quit IRC14:26
*** Kevin_Zheng has quit IRC15:01
*** rcernin has quit IRC15:24
*** njohnston__ is now known as njohnston15:25
*** itisha has joined #openstack-zaqar15:26
*** njohnston has quit IRC16:37
Eva-iflwang: Hello. Please take my "lazy queues in subscriptions" task, if you think this task needs to be done in N-1. Otherwise I'd like to make it myself in N-2.16:39
*** AAzza has quit IRC17:41
*** tqtran has joined #openstack-zaqar17:43
*** AAzza has joined #openstack-zaqar17:43
*** flwang1 has joined #openstack-zaqar18:54
*** pt_15 has joined #openstack-zaqar19:03
*** flwang1 has quit IRC19:18
*** flwang1 has joined #openstack-zaqar19:26
*** njohnston has joined #openstack-zaqar19:27
*** mpanetta_ has quit IRC19:46
openstackgerritMerged openstack/python-zaqarclient: Updated from global requirements  https://review.openstack.org/30316419:53
*** flwang1 has quit IRC19:58
*** ametts has quit IRC20:13
*** ametts has joined #openstack-zaqar20:30
*** ametts has quit IRC21:07
EmilienMflwang: I found new bugs in Zaqar21:29
EmilienMa patch in zaqar between 1 week ago and today broke our CI21:29
EmilienMsee failure: http://logs.openstack.org/20/316520/3/check/gate-puppet-openstack-integration-3-scenario002-tempest-centos-7/52af87a/console.html#_2016-05-18_20_28_10_26521:30
EmilienMvkmc: ^21:31
flwangEmilienM: clicking...21:33
EmilienMzaqar logs are in http://logs.openstack.org/20/316520/3/check/gate-puppet-openstack-integration-3-scenario002-tempest-centos-7/52af87a/logs/zaqar21:34
flwangEmilienM: so it's breaking the tempest cases21:35
*** flwang1 has joined #openstack-zaqar21:35
flwangit's weird since it can pass the tempest gate, am i missing something?21:35
EmilienMare you running tempest in your gate?21:35
flwangEmilienM: ah, i see. I have proposed the patch, but not yet. That makes much more sense.21:37
flwangEmilienM: i will fix it, thanks for the heads up21:37
flwangand that's a good example, we should enable tempest in our gate asap21:38
EmilienMyeah.. please :-)21:39
EmilienMflwang: please let me know (email or IRC) when the fix is up21:39
EmilienMwe're going to disable zaqar testing in the meantime :(21:39
flwangEmilienM: sorry? do you mean you're going to disable zaqar testing no matter if we fix the bug?21:40
flwangor just for now?21:40
EmilienMjust tonight :-)21:40
flwangEmilienM: awesome, thanks21:40
EmilienMno worries, we want to keep testing zaqar :P21:41
flwangEmilienM: cooooooooool21:41
EmilienMflwang: do you have a launchpad about this problem?21:42
EmilienMor any review in gerrit already?21:43
EmilienMso I can monitor it21:43
flwangEmilienM: for this, no, i'm going to file one21:43
EmilienMok I'll wait before posting the patch to disable tests, please let me know URL21:43
flwangEmilienM: sure21:44
therveflwang, You shouldn't add a new gate with tempest. You may want to move in-tree integration tests to tempest, though21:46
EmilienMtherve: right21:47
EmilienMpuppet CI is using in-tree tests21:47
flwangtherve: that's another option right?21:53
therveflwang, Sorry?21:53
flwangtherve: so you mean just using the tempest test replace current integration test?21:54
flwangnow our tox-integration is calling the tests under zaqar.tests.functional21:55
therveflwang, Kinda. I mean reusing test infrastructure from tempest, so that when you run zaqar integration tests with tempest runner21:56
flwangso it it possible executing the tempest test as well? are you talking about this?21:56
therveBasically all the tests should be in-tree is my point21:56
flwangtherve: yep, it's in tree. see https://review.openstack.org/30247921:56
EmilienMflwang: I'm going to bed in 2 min21:56
EmilienMI'll push without launchpad URL, let me know when you did it21:57
flwangEmilienM: here is link https://bugs.launchpad.net/zaqar/+bug/158335821:57
openstackLaunchpad bug 1583358 in zaqar "Zaqar tempest test failed" [Undecided,New]21:57
EmilienMah :)21:57
flwangEmilienM: sorry, was in a standup meeting21:57
EmilienMthx, good night21:57
flwanggood night21:57
therveI guess I misunderstood the problem then :)21:58
flwangtherve: :) i think the problem is21:59
flwangwe merged your patch, but it broke our tempest test21:59
flwanghowever, we haven't enable tempest in our gate21:59
flwangso we're not aware of that issue21:59
flwangbut Puppet CI is using zaqar's tempest, so Puppet CI failed :)22:00
EmilienMwe're running tempest in our gate22:00
EmilienMso we test what you're doing22:01
flwangEmilienM: yep, that's cool22:01
flwangat least, we have a gate guard :D22:01
therveOK that makes a bit more sense22:03
therveThough I don't understand why they fail :)22:03
flwangtherve: me too, but i'm going to figure it out :D22:05
flwangtherve: btw, do you like Zane's idea about zaqar + mistral?22:05
therveI haven't digested it yet22:05
flwangtherve: http://lists.openstack.org/pipermail/openstack-dev/2016-May/095376.html22:06
therveYeah I saw I just need some time :)22:09
therveTotally agree with his point about webhooks being tricky though22:09
therve(And zaqar implementation is suboptimal at best)22:10
flwangtherve: cool, glad to know you like the idea, so did i22:10
therveI didn't say that, did I?22:11
flwanghaha22:13
flwangtherve: anyway, pls drop your comments no matter you like or not :) thanks22:14
flwangtherve: since your opinion are invaluable for us22:14
therveThat's very nice of you22:14
therveMy opinion is not even invaluable to me :)22:15
flwangtherve: btw, is it true that heat will drop out the autoscaling stuff?22:15
flwangand which will be done in Senlin?22:15
therveNot that I know22:16
therveWe may not improve autoscaling much more, though22:16
flwangtherve: btw, do you think it's a good idea to let aodh talk with zaqar and then let zaqar to trigger heat's autoscaling?22:18
flwangthe benefit is you got a queue and the trigger can be tried(will do it in Newton)22:18
flwangi just wondering if we(zaqar team) should pay effort on this case to improve current autoscaling22:19
therveIt's somewhat interesting, but not really important IMHO22:22
flwangok, got, thanks22:23
therveflwang, BTW the tempest failure is because they're using falcon 0.322:27
therveSo we wouldn't have caught it the gate anway22:27
therveanywa22:27
flwangtherve: oh, really, why?22:27
therveBecause we use 1.022:27
flwangi assume when they installed zaqar, the new falcon version will be installed22:28
*** itisha has quit IRC22:29
therveIt's possible they're using packages and the new version is not package yet22:31
thervepackaged22:31
flwangtherve: possibly, but i think we still should figure out a good way so that the code can work with 0.322:33
flwangbtw22:33
flwangdo you think we should backport the patch or just bump the falcon version for those stable releases?22:33
therveYou mean restrict?22:33
flwangmitaka and the old ones22:33
flwangyep22:34
therveYour call :)22:34
therveMayb we need to fix working with 0.3 before backporting22:34
therveOr not backport and enforce 1.0 in master22:34
flwangtherve: yep, that's my plan, if we can figure out a way to let the code work with 0.3, then all good22:34
*** Eva-i has quit IRC22:35
therveIt may be tricky, given that extra parameter22:35
flwangtherve: yep :(22:35
therveEnforcing 1.0 in master sounds fine to me22:35
flwangbut if we don't backport, we have to restrict the falcon version for all the old releases22:35
therveWe need to anyway22:36
therveBecause the code won't work for < 0.322:36
flwangi see. so we need restrict it like falcon>=0.1.6 and <1.0.022:38
flwangthen bump master with >=1.0.022:38
flwangif we can't figure out a way to let the code work with the old verions :(22:39
therveYeah I think that would work22:39
*** pt_15 has quit IRC22:46
flwangtherve: cool, thanks22:55
*** mpanetta_ has joined #openstack-zaqar23:20
*** mpanetta_ has quit IRC23:20
*** mpanetta_ has joined #openstack-zaqar23:21
openstackgerritFei Long Wang proposed openstack/zaqar: Restrict falcon version  https://review.openstack.org/31837123:26

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