Wednesday, 2014-09-17

*** malini has quit IRC00:01
*** kgriffs is now known as kgriffs|afk00:03
*** amitgandhinz has quit IRC00:03
*** flwang1 has quit IRC00:10
*** jeffrey4l__ has joined #openstack-zaqar00:12
*** openstackgerrit has quit IRC00:31
*** openstackgerrit has joined #openstack-zaqar00:32
*** echevemaster has quit IRC00:45
*** cpallares has joined #openstack-zaqar00:45
*** kgriffs|afk is now known as kgriffs00:54
*** kgriffs is now known as kgriffs|afk01:04
*** echevemaster has joined #openstack-zaqar01:16
*** jeffrey4l__ has quit IRC01:21
*** jeffrey4l__ has joined #openstack-zaqar01:37
*** echevemaster has quit IRC01:48
*** vipul has quit IRC01:48
*** dmitryme has quit IRC01:48
*** echevemaster has joined #openstack-zaqar01:54
*** vipul has joined #openstack-zaqar01:54
*** dmitryme has joined #openstack-zaqar01:54
*** kgriffs|afk is now known as kgriffs01:55
*** sebasmagri has quit IRC01:57
*** sebasmagri has joined #openstack-zaqar01:58
*** sebasmagri is now known as Guest5716301:59
*** kgriffs is now known as kgriffs|afk02:05
*** cpallares has quit IRC02:22
*** alcabrera is now known as alcabrera|afk02:46
*** kgriffs|afk is now known as kgriffs02:55
*** jeffrey4l__ has quit IRC03:04
*** kgriffs is now known as kgriffs|afk03:05
*** jeffrey4l has joined #openstack-zaqar03:17
*** vkmc has quit IRC03:33
*** prashanthr_ has quit IRC03:45
*** prashanthr_ has joined #openstack-zaqar03:47
*** prashanthr_ has quit IRC03:54
*** prashanthr_ has joined #openstack-zaqar03:55
*** kgriffs|afk is now known as kgriffs03:56
*** echevemaster has quit IRC04:00
*** Guest57163 is now known as sebasmagri04:02
*** sebasmagri is now known as Guest8027604:03
*** prashanthr_1 has joined #openstack-zaqar04:05
*** kgriffs is now known as kgriffs|afk04:06
*** Guest80276 is now known as sebasmagri04:06
*** sebasmagri has joined #openstack-zaqar04:06
*** sebasmagri has joined #openstack-zaqar04:06
*** prashanthr_ has quit IRC04:07
*** jeffrey4l has quit IRC04:11
*** prashanthr_ has joined #openstack-zaqar04:13
*** prashanthr_1 has quit IRC04:14
*** prashanthr_ has quit IRC04:22
*** jeffrey4l has joined #openstack-zaqar04:30
*** prashanthr_ has joined #openstack-zaqar04:45
*** kgriffs|afk is now known as kgriffs04:57
*** kgriffs is now known as kgriffs|afk05:07
*** sgotliv has joined #openstack-zaqar05:09
*** prashanthr_1 has joined #openstack-zaqar05:30
*** prashanthr_ has quit IRC05:31
*** prashanthr_1 has quit IRC05:34
*** prashanthr_ has joined #openstack-zaqar05:47
*** kgriffs|afk is now known as kgriffs05:58
*** kgriffs is now known as kgriffs|afk06:08
*** jeffrey4l has quit IRC06:11
openstackgerritOpenStack Proposal Bot proposed a change to openstack/zaqar: Imported Translations from Transifex  https://review.openstack.org/12207006:12
*** flaper87|afk is now known as flaper8706:20
*** jeffrey4l has joined #openstack-zaqar06:24
*** kgriffs|afk is now known as kgriffs06:59
*** kgriffs is now known as kgriffs|afk07:09
*** kgriffs|afk is now known as kgriffs08:00
*** sgotliv has quit IRC08:07
*** kgriffs is now known as kgriffs|afk08:09
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Cleanup technical debt  https://review.openstack.org/12165608:14
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Rename `shard` to `pool`  https://review.openstack.org/12149408:14
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Use queue_creation to send queue's metadata  https://review.openstack.org/12156408:14
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Add support for `pop` implemented in v1.1  https://review.openstack.org/12015508:14
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Respect queue's lazy creation  https://review.openstack.org/12156508:14
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Always pass a project_id  https://review.openstack.org/12159608:14
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Add support for flavor to the client library  https://review.openstack.org/12153408:14
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Fix functional tests  https://review.openstack.org/12156308:14
*** flwang1 has joined #openstack-zaqar08:19
openstackgerritJeffrey Zhang proposed a change to openstack/zaqar: Remove config sample and generate it using code  https://review.openstack.org/12208908:26
openstackgerritJeffrey Zhang proposed a change to openstack/zaqar: Fix the redis opts  https://review.openstack.org/12209308:45
*** kgriffs|afk is now known as kgriffs09:00
*** kgriffs is now known as kgriffs|afk09:10
*** sgotliv has joined #openstack-zaqar09:17
*** sgotliv has quit IRC09:57
*** malini has joined #openstack-zaqar10:00
*** jeffrey4l has quit IRC10:01
*** kgriffs|afk is now known as kgriffs10:01
*** jeffrey4l has joined #openstack-zaqar10:04
*** kgriffs is now known as kgriffs|afk10:11
*** tmu_ is now known as tmu10:34
*** sgotliv has joined #openstack-zaqar10:37
*** myra has quit IRC10:37
*** kgriffs|afk is now known as kgriffs11:02
*** prashanthr_ has quit IRC11:05
*** kgriffs is now known as kgriffs|afk11:12
*** malini has quit IRC11:27
*** vkmc has joined #openstack-zaqar11:32
*** vkmc has quit IRC11:32
*** vkmc has joined #openstack-zaqar11:32
vkmcgood morning o/11:33
vkmcflaper87, hey Fla, how are you?11:50
vkmcI'm checking https://review.openstack.org/#/c/120155/4/zaqarclient/queues/v1/api.py11:50
vkmcaccording to the API spec, shouldn't it be delete?11:50
vkmchttps://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1#Delete_Multiple_Messages11:51
vkmcI mean, there is no POP method, we implemented it with DELETE11:52
vkmchttps://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1#Endpoints_Synopsis11:52
vkmcsorry I misread your fix -.-11:53
vkmcrm -rf ^11:54
*** sgotliv has quit IRC12:01
*** kgriffs|afk is now known as kgriffs12:03
flaper87goooooooooooooo morning12:03
flaper87vkmc: and I wrote my comment in the wrong line12:04
flaper87that's my bad :(12:04
*** sgotliv has joined #openstack-zaqar12:04
vkmcflaper87, hey :)12:05
vkmcit seemed odd to me when I reviewed TBH, I misunderstood https://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1#Delete_Multiple_Messages12:06
flaper87vkmc: hehe, indeed :D12:06
vkmcflaper87, how are you doing?12:07
flaper87vkmc: I'm good, you?12:07
flaper87the wait is kinda killing me12:08
flaper87we're at 7 -1 and 6 +112:08
vkmcI'm fine too12:08
flaper87if ttx changes his mind, we're in12:08
vkmcyes... it's truly a bummer12:08
flaper87but he doesn't seem to be around12:08
vkmcI was going to send you a tweet or something when I saw jpipes vote haha12:08
flaper87haahahahaha12:08
vkmcand his feedback12:08
vkmc(probably you were f5 in dreams)12:09
vkmcs/f5/hitting f512:09
flaper87kinda,12:09
vkmcI dunno... keep away from gratuation for one vote12:10
vkmcone 'hesitant' vote12:10
vkmcthat shouldn't be allowed haha12:10
flaper87what really worries me right now and I think this was not discussed enough is that holding back zaqar will affect its adaption really bad12:11
flaper87holding it back for 1 more cycle means that it'll be released with other openstack projects in 1 year12:11
flaper87that's way too much time12:11
vkmcwhat I don't understand12:12
vkmcwell... not understand... what I cannot conceive12:12
*** kgriffs is now known as kgriffs|afk12:12
vkmcis the fact that there are no plans for changing anything in the core in the next cycle12:13
vkmcwe may be discussing and clearing up the whole messaging or queue dillema12:13
vkmcbut nothing else12:13
vkmcdo we really need a cycle to do that?12:14
flaper87right12:14
vkmcshouldn't it be more fair to get graduate and make sure that situation is defined by K-1?12:14
flaper87yeah, that's what I'm still trying to explain to ppl12:14
flaper87we know what we are and where we are headed12:14
vkmcwe have a summit in between, if needed, we could have some sort of session to sit together and discuss what is Zaqar trying to be and how we are planning to do it12:15
vkmcsit together with those who doesn't understand Zaqar position I meant12:15
flaper87TBH, I'm tired of doing that12:15
vkmcyeah I understand that12:15
flaper87I prefer dedicating time to those who already understand it and want to use it12:15
vkmcbut integration also means having to explain others what we are up to12:15
flaper87instead of using that time to explain it to others and start discussing what queuing and messaging is12:16
flaper87right but we've done that for 2 cycles12:16
vkmcyeah, but it seems that it's not enough :(12:16
vkmcdon't get me wrong12:16
flaper87I think there's people that need to do their homework12:16
vkmcI don't want to waste time explaining what Zaqar is12:16
flaper87that's why I don't think we should dedicate more time to this "explaining zaqar' thing12:16
flaper87We failed 1 time and some people learned from it12:17
flaper87they dug into zaqar and tried to udnerstand12:17
flaper87we made mistakes and we worked on those things12:17
flaper87that's what really frustrates me12:18
vkmcyeah, it's obvious that there is a good predisposition from Zaqar side12:18
flaper87We've put so much time reaching out to people12:18
flaper87explaining what zaqar is and collecting use cases12:18
vkmcright now, as ttx admitted, is TC's fault12:18
vkmcmaybe we should poke TC so they keep an eye on us12:18
vkmcbut that is expected from their side, not from ours12:19
flaper87I'm not expecting the TC to sya: "Hey we screwed so lets approve regardless of what the project does". What I'd like is to make people understand that we know where we are headed and regardless of the result of the queuing/messaging discussion there are still use cases for it and people *want* it12:19
flaper87the API is stable and we've several different deployments covered12:19
vkmcyeah12:19
vkmcthat is what I wanted to say in last TC meeting12:20
vkmcit doesn't matter if we are a messaging system, a queue, or a jar of nutella12:20
flaper87LOL @ jar of nutella12:20
flaper87FWIW, I said it and zaneb said that too12:20
flaper87"I don'12:20
flaper87ops12:20
flaper87he said something like: "I don't care how you call it"12:21
vkmcit has been demostrated that Zaqar has several use cases for integrated projects and for other projects as well12:21
vkmcyea I think I remember now12:21
flaper87I'm not willing to make 3 guys happy at the cost of sacrificing use-case12:21
flaper87use-cases*12:22
vkmcthat is way more polite that my way of expressing it haha12:22
vkmcyeah12:22
vkmcbtw, why they say that removing get by id we won't qualify as a messaging system?12:22
flaper87that's why I said: "Regardless of the result of this discussion, it ain't going to change"12:22
vkmcAFAIK there is no contraint about message system features12:22
flaper87right... At this point, I think it's just a matter of perception, really12:23
vkmcthey have to start thinking out of the box12:23
flaper87vkmc: PM ;)12:24
flaper87anyway12:24
flaper87I still have hope that ttx will reconsider his vote12:24
flaper87but that's the only hope I have left12:24
vkmcyeah, I was thinking to leave a gentle review with this thoughts12:25
vkmcI'm not sure12:25
vkmcif there is a slightly chance to get some of the -1's flip to our side12:26
vkmcwe should take it12:27
vkmcflaper87, ^12:28
flaper87yeah, feel free to do it. I added a couple of comments last night. One of them saying what we discussed here12:29
vkmccool12:30
*** malini has joined #openstack-zaqar12:35
*** malini has quit IRC12:48
*** jchai has joined #openstack-zaqar12:54
*** kgriffs|afk is now known as kgriffs13:04
*** sriram has joined #openstack-zaqar13:08
*** mpanetta has joined #openstack-zaqar13:12
*** kgriffs is now known as kgriffs|afk13:13
*** mpanetta has quit IRC13:16
*** mpanetta has joined #openstack-zaqar13:16
*** echevemaster has joined #openstack-zaqar13:17
*** malini has joined #openstack-zaqar13:47
*** malini has left #openstack-zaqar13:47
*** malini has joined #openstack-zaqar13:47
malinihello!!13:49
vkmchi malini!13:50
malinihow are you?13:50
*** sgotliv has quit IRC13:51
vkmcgood good and you?13:51
vkmclast news on the Zaqar graduation http://ttx.re/next-steps-for-zaqar.html13:52
vkmc:/13:52
flaper87and you can tell by the face13:53
flaper87:D13:53
vkmcyeah...13:53
vkmcspoiler alert13:53
mpanettablah13:53
maliniI saw the votes y'day evening :(13:53
maliniBut I am determined not to let some folks lack of understanding ruin my day13:54
flaper87vkmc: malini girls, would you have time to go through the client reviews today?13:54
maliniflaper87: you have pop-tarts?13:54
vkmcflaper87, I'm doing that, check out https://review.openstack.org/#/c/121534/413:54
vkmc+1 malini13:54
flaper87malini: I have gummy bears that I'm willing to share13:55
maliniflaper87: I can live with tht13:55
flaper87actually, these ones are called: "funny puzzle"13:56
flaper87WTF ?13:56
vkmcthere is something I'm not getting... hmm in L338 here https://review.openstack.org/#/c/121563/4/zaqarclient/tests/queues/queues.py why you assert that the length of the messages list is 1 instead of 3?13:56
vkmcand in L354 0 instead of 113:56
flaper87vkmc: that's a falcon bug13:56
flaper87well, not really a bug13:56
flaper87lemme explain13:56
vkmcsure13:56
flaper87requests serialices ids as ?ids=1&ids=2&ids=313:57
flaper87however, falcon doesn't know how to parse that13:57
flaper87it knows how to parse ids=1,2,313:57
vkmcaha...13:57
flaper87I talked with kgriffs|afk and that's comming in 0.213:57
flaper87we need to have a fix for that in the client, though13:57
flaper87but the fix is in the CLI patch13:57
flaper87once all that lands, I'll fix the test13:57
vkmcdoesn't the endpoint expects ?ids=1,2,3?13:58
flaper87there's no standard on that, TBH13:58
vkmcit seems odd to have ?ids=1&ids=2&ids=313:58
flaper87there's no "URL-rfc" explaining how multiple parameters must be specified13:58
flaper87AFAIK13:58
flaper87vkmc: yup but it's quite common13:59
vkmcnow that I'm reading... yeah13:59
vkmcit's quite common for different parameters though13:59
vkmcanyhow14:02
vkmcthat is on the request14:03
vkmcbut when you get the set of messages14:03
vkmcyou get an iterator with the messages14:03
flaper87right14:05
*** kgriffs|afk is now known as kgriffs14:05
flaper87but since falcon is not parsing the `ids` thing correctly, it's just getting 1 id and sending 1 message back14:05
vkmcoic14:06
flaper871 is wrong for sure, I just can't fix it in that specific patch14:06
flaper87:P14:06
flaper87once the CLI patch lands with the fix for it, I'll update the test14:06
vkmcdon't we require Falcon update for that?14:07
*** sgotliv has joined #openstack-zaqar14:07
flaper87vkmc: we can either wait for falcon to support `ids=&ids=&ids` or just serialize our ids in a way that falcon knows how to parse `ids=1,2,3`14:07
vkmcflaper87, fair enough14:08
flaper87vkmc: this is the fix I'm referring to https://review.openstack.org/#/c/120966/4/zaqarclient/queues/v1/core.py,cm14:08
*** jchai is now known as jchai_afk14:08
flaper87read my comments there and let me know if you agree14:08
vkmckewl14:09
vkmcI agree14:09
*** kgriffs is now known as kgriffs|afk14:14
*** amitgandhinz has joined #openstack-zaqar14:23
vkmcflaper87, L73 https://review.openstack.org/#/c/121564/4/zaqarclient/queues/v1/queues.py what happens if the queue already exist? just updates the metadata?14:27
vkmcit's not in the wiki, we should add it14:27
vkmchttps://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1#Create_Queue14:27
*** jeffrey4l has quit IRC14:28
flaper87vkmc: yup14:33
flaper87AFAIK14:33
flaper87it just overwrites it14:33
flaper87we need to work on the support for `patch`14:33
*** alcabrera|afk is now known as alcabrera14:34
vkmck14:34
*** sebasmagri has quit IRC14:36
*** jeffrey4l has joined #openstack-zaqar14:36
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Cleanup technical debt  https://review.openstack.org/12165614:41
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Rename `shard` to `pool`  https://review.openstack.org/12149414:41
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Use queue_creation to send queue's metadata  https://review.openstack.org/12156414:41
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Respect queue's lazy creation  https://review.openstack.org/12156514:41
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Always pass a project_id  https://review.openstack.org/12159614:41
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Add support for flavor to the client library  https://review.openstack.org/12153414:41
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Fix functional tests  https://review.openstack.org/12156314:41
flaper87vkmc: malini ^^^14:42
vkmcthanks flaper8714:42
maliniit is weird why it carries over my prev +2 https://review.openstack.org/#/c/121656/14:43
flaper87malini: it carries it if I didn't change the code14:44
flaper87and I didn't touch that patch14:44
vkmcflaper87, you added the warning14:45
maliniso why did you have a new patchset? coz of dependency?14:45
flaper87malini: yes14:45
flaper87vkmc: the warning is another patch14:45
flaper87AFAIK14:45
vkmcoh14:45
vkmcmakes sense now14:45
vkmcmagic git14:45
openstackgerritJeffrey Zhang proposed a change to openstack/python-zaqarclient: CLI support for message CRUD operations  https://review.openstack.org/12096614:45
jeffrey4lflaper87, Added the FIXME comments14:47
flaper87jeffrey4l: will take a look now14:47
jeffrey4lthx14:48
vkmcflaper87, https://review.openstack.org/#/c/121534/14:50
flaper87vkmc: ? :)14:51
vkmcflaper87, can you check the schema?14:51
flaper87vkmc: mmh, I swear I responded14:51
*** sebasmagri has joined #openstack-zaqar14:51
flaper87vkmc: it's `flavors_name` it has to match the ref14:51
vkmcflaper87, yeah, I meant there is a required param missing14:52
flaper87and the pool_name and capabilities are in the flavor_data14:52
flaper87ah, mmh.14:52
flaper87wah yeah so here's the thing14:52
flaper87vkmc: it's a required param here: https://review.openstack.org/#/c/121534/4/zaqarclient/queues/v1/flavor.py,cm14:52
vkmcyes14:53
flaper87the reason I didn't make it required in the core module is because people should know what they're doing if they're using the core module14:53
flaper87:)14:53
flaper87I had a 10mins discussion with myself on that14:53
vkmcand what happens if no pool_name is passed there?14:53
flaper87"Should I add a bunch of required arguments in the core module? or should I tell the user to read the spec?"14:54
flaper87vkmc: zaqar will raise 40014:54
flaper87core module is a lower-level module14:54
vkmcok..14:54
flaper87if the users use it, they must know what they're doing14:54
*** kgriffs|afk is now known as kgriffs14:54
flaper87if they don't then zaqar will make sure to let them know14:55
vkmcflaper87, and in here? https://review.openstack.org/#/c/121534/4/zaqarclient/queues/v1/core.py14:55
vkmcbtw, why your gerrit is fancier that mine?14:55
flaper87vkmc: go to settings and enable the "new ui"14:57
flaper87;)14:57
flaper87vkmc: same thing, the pool should be in the flavor_data dict14:58
vkmcok14:59
vkmcwell, no more comments on that patchset15:01
vkmcI added this as a response to the comments I made before15:01
* vkmc enables new ui15:01
vkmchttp://alltheragefaces.com/img/usercreated/4f71bfdabd626.png15:04
*** jchai_afk is now known as jchai15:04
alcabreragood morning. :)15:05
jeffrey4lgood evening ;p15:06
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Cleanup technical debt  https://review.openstack.org/12165615:08
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Use queue_creation to send queue's metadata  https://review.openstack.org/12156415:08
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Respect queue's lazy creation  https://review.openstack.org/12156515:08
openstackgerritFlavio Percoco proposed a change to openstack/python-zaqarclient: Always pass a project_id  https://review.openstack.org/12159615:08
vkmcok, I'm lost with the new ui15:08
* vkmc goes back to the old ui15:08
flaper87vkmc: replied to all your comments :D15:09
flaper87and addressed them15:09
vkmcflaper87, yup I saw them15:10
vkmchi alcabrera! :)15:13
alcabreraheya vkmc. :)15:14
vkmcflaper87, thaaaaaanks for being so patient :p15:14
flaper87vkmc: thank YOU for being patient and reviewing all those patches15:14
vkmcoh we deserve tons of poptarts <315:15
alcabrera^15:16
* alcabrera hands out poptarts, tons of them15:16
*** jeffrey4l_ has joined #openstack-zaqar15:17
vkmcyaaaay15:17
vkmcflaper87, can you rebase this? https://review.openstack.org/#/c/121478/115:17
flaper87vkmc: yup, I wil15:18
*** jeffrey4l has quit IRC15:20
vkmc:)15:23
vkmcalcabrera, if you have a moment later, can you review this one? https://review.openstack.org/#/c/121424/15:23
alcabrerasure thing, vkmc!15:24
vkmcthx!15:24
flaper87kgriffs: if you've a chance, could you go through the client patches again?15:24
flaper87malini: ^15:24
alcabreraflaper87, vkmc: all word-smithed on #121424 (-1)15:28
vkmcthx alcabrera15:31
alcabreranp vkmc. :)15:31
kgriffsflaper87: I'll see what I can do. But I won't lie. I am behind on some other work that I put aside to do benchmarking for Zaqar over the last couple days.15:34
* flaper87 is back15:34
flaper87kgriffs: sure, no worries!15:34
flaper87I think I'll go ahead and ninja-approve some patches15:35
flaper87unless malini has time to go through them now15:35
maliniflaper87: all the client patches?15:35
malinion it now15:36
flaper87malini: awesome, thanks15:36
flaper87malini: if there are concerns, feel free to ping me directly15:36
flaper87sorry for the rush, I just don't want to miss the 18th deadline15:36
maliniok15:36
flaper87:D15:36
*** jchai is now known as jchai_afk15:39
malinivkmc, flwang, kgriffs: Can you take a look at this one https://review.openstack.org/#/c/121596/ if you have a minute?15:42
vkmcmalini, sure thing15:44
malini& this https://review.openstack.org/#/c/121596/ :)15:44
malinithey are the same :D15:44
kgriffsflaper87: re rally15:44
kgriffsthere are some sorts of tests/graphs that I don't see it reporting right now15:44
kgriffsI think we can contribute to make those happen15:44
kgriffsmalini: will you be able to at the rally hangout on thur?15:45
kgriffsI have daddy duty @ home turns out15:45
flaper87boris-42: there?15:46
malinikgriffs: sure..I just need some background on what/why & also when15:46
kgriffsok15:46
flaper87Did you read my messages w.r.t the Rally hangout ?15:46
flaper87Is tomorrow 21 UTC a good time for you ?15:46
flaper87kgriffs: what graphs ?15:46
*** ametts has joined #openstack-zaqar15:46
kgriffsso here is an example of what is currently reported15:47
kgriffshttp://logs.openstack.org/76/110876/2/check/gate-rally-dsvm-glance/76dd628/rally-plot/results.html.gz15:47
kgriffsmaybe I'm just not understanding the charts15:47
kgriffswhat does "iteration" mean?15:48
flaper87number of calls ?15:48
kgriffsI don't understand what "order number of method's call" is15:48
flaper87mmh15:48
flaper87boris-42: ^15:48
flaper87:D15:48
kgriffsmaybe rally can already do this, but I would like the ability to say15:49
kgriffswe want to track X against increasing load15:50
maliniflaper87: I think I am done with all the client patches15:50
malinilet me know if I missed anything15:50
kgriffswhere X is (latency, throughput, stdev, min, max, etc.)15:50
kgriffsand then I would like to say15:50
kgriffslet's now run all that again and increase the cluster size, then compare side-by-side to see how things scale15:51
flaper87malini: thanks a lot15:51
malinithank you!15:51
flaper87kgriffs: oh mmh15:52
kgriffsfinally, you might show a histogram of per-request latency for all clients15:52
flaper87I don't think it can do it now15:52
flaper87AFAIU all that is in the works15:52
flaper87but we definitely need i15:52
flaper87it15:52
kgriffsok15:52
kgriffsoh, also it would be great to graph that against CPU and disk I/O on the cluster nodes15:53
flaper87vkmc: you're missing this one: https://review.openstack.org/#/c/121596/15:53
flaper87:D15:53
* kgriffs wants the moon15:53
*** prashanthr_ has joined #openstack-zaqar15:53
kgriffsfinal thought15:53
kgriffsidk what the gates run on now15:53
flaper87those are important metrics for us.  Does rally report that already?15:53
*** jeffrey4l__ has joined #openstack-zaqar15:53
flaper87i mean, even if not graphed, does it have info about CPU usage?15:53
kgriffsbut perhaps we can get Rackspace to donate some onmetal boxes for a weekly large-scale test. this would happen out-of-band (not gated on each patch)15:54
vkmcflaper87, no I don't :P15:54
kgriffsflaper87: idk about cpu usage. you'd have to use munin or something15:54
kgriffsstatsd15:54
kgriffswhatever you like15:54
flaper87vkmc: gerrit says you reviewed it at "15:54
flaper875:54 PM"15:54
flaper87:P15:54
vkmcflaper87, gerrit is lying15:54
vkmcflaper87, I reviewed it at 12.55PM15:54
flaper87oh ok, me shuts gerrit down15:55
flaper87kgriffs: yeah, I'll write this down and talk to boris15:55
kgriffsmaybe the swift folks could lend us a hand as well, since I have to think they care about performance at least as much as we do. :)15:55
* vkmc plays the timezone card15:55
kgriffsflaper87: so maybe you can talk to notmyname as well15:55
flaper87I'm pretty sure you just woke him up15:56
flaper87:D15:56
kgriffslol15:56
flaper87you mentioned his nick and his baby in less than 10s15:56
*** jeffrey4l_ has quit IRC15:56
flaper87ok, I gtg for a bit guys15:56
flaper87brb15:56
kgriffskk15:56
openstackgerritJeffrey Zhang proposed a change to openstack/zaqar: Add genconfig to tox.ini  https://review.openstack.org/12219015:56
*** ametts has quit IRC15:57
*** jeffrey4l__ has quit IRC16:02
*** ametts has joined #openstack-zaqar16:08
*** prashanthr_1 has joined #openstack-zaqar16:20
prashanthr_1Gooood morning :)16:20
*** jchai_afk is now known as jchai16:21
*** jeffrey4l__ has joined #openstack-zaqar16:22
jeffrey4l__flaper87, my patch https://review.openstack.org/#/c/122093/ does three thing. 1) fix the redis opt  typo in setup.cfg 2) add the redis to oslo.config.generator.rc 3) fix the reconnect_sleep default value type.  So the better way is split this commit into three or just describe it in commit summary?16:22
prashanthr_1kgriffs: Good morning :) I just had a small question about https://bugs.launchpad.net/zaqar/+bug/136381116:22
openstackgerritA change was merged to openstack/python-zaqarclient: Add support for `pop` implemented in v1.1  https://review.openstack.org/12015516:22
*** jeffrey4l__ is now known as jeffrey4l16:24
openstackgerritA change was merged to openstack/python-zaqarclient: Rename `shard` to `pool`  https://review.openstack.org/12149416:24
openstackgerritA change was merged to openstack/python-zaqarclient: Add support for flavor to the client library  https://review.openstack.org/12153416:26
openstackgerritA change was merged to openstack/python-zaqarclient: Fix functional tests  https://review.openstack.org/12156316:27
kgriffsprashanthr_1: sorry, gotta run - be back in an hour or so (lunch group)16:30
prashanthr_1Sure kgriffs :)16:31
*** kgriffs is now known as kgriffs|afk16:31
openstackgerritA change was merged to openstack/python-zaqarclient: Use queue_creation to send queue's metadata  https://review.openstack.org/12156416:32
openstackgerritA change was merged to openstack/python-zaqarclient: Respect queue's lazy creation  https://review.openstack.org/12156516:33
*** jeffrey4l_ has joined #openstack-zaqar16:33
openstackgerritJeffrey Zhang proposed a change to openstack/zaqar: Add the redis opts to the generate sample shell script  https://review.openstack.org/12209316:34
openstackgerritJeffrey Zhang proposed a change to openstack/zaqar: Add genconfig to tox.ini  https://review.openstack.org/12219016:34
*** sgotliv has quit IRC16:37
*** jeffrey4l has quit IRC16:37
boris-42flaper87 hi there16:38
boris-42kgriffs|afk hi there16:38
openstackgerritA change was merged to openstack/python-zaqarclient: Always pass a project_id  https://review.openstack.org/12159616:40
openstackgerritA change was merged to openstack/python-zaqarclient: Cleanup technical debt  https://review.openstack.org/12165616:41
*** jeffrey4l_ has quit IRC16:46
notmynamekgriffs|afk: flaper87: yo. I wasn't online at all yesterday and just got through my 401 unread emails. now going through IRC buffers16:56
notmynamekgriffs|afk: flaper87: sorry the vote went the way it did yesterday (from what I heard)16:57
notmynamekgriffs|afk: flaper87: I see (recently in my buffer) that you were talking about me wrt perf in zaqar. let me know what you need16:57
*** prashanthr_1 has quit IRC17:00
*** ametts has quit IRC17:00
*** amitgandhinz has quit IRC17:00
*** fifieldt_ has quit IRC17:00
*** prashanthr_1 has joined #openstack-zaqar17:00
*** ametts has joined #openstack-zaqar17:00
*** amitgandhinz has joined #openstack-zaqar17:00
*** fifieldt_ has joined #openstack-zaqar17:00
*** echevemaster has quit IRC17:00
*** kgriffs|afk is now known as kgriffs17:01
boris-42flaper87 kgriffs so guys17:01
*** echevemaster has joined #openstack-zaqar17:01
boris-42flaper87 kgriffs  "iterations" means order number of call of method that is benchmark17:02
boris-42flaper87 kgriffs we are creating load by calling multiple times the same method (that is called benchmark scenarios)17:02
boris-42flaper87 kgriffs  in graphs we have duration / iteration17:03
*** kgriffs is now known as kgriffs|afk17:11
*** sgotliv has joined #openstack-zaqar17:46
*** sgotliv has quit IRC17:51
*** sgotliv has joined #openstack-zaqar17:53
*** sgotliv has quit IRC17:53
*** sgotliv has joined #openstack-zaqar17:53
*** kgriffs|afk is now known as kgriffs18:02
*** kgriffs is now known as kgriffs|afk18:12
*** kgriffs|afk is now known as kgriffs18:24
*** AAzza is now known as AAzza_afk18:28
*** AAzza_afk is now known as AAzza18:46
*** kgriffs is now known as kgriffs|afk18:59
*** prashanthr_ has quit IRC19:09
*** jchai is now known as jchai_afk19:11
*** jchai_afk is now known as jchai19:18
*** AAzza has left #openstack-zaqar19:28
*** malini has quit IRC19:31
*** jogo has joined #openstack-zaqar19:32
jogoI have a random question19:36
vkmcjogo, shoot :)19:37
jogohow does zaqar compare to the properties that SQS has19:38
jogohttp://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/DistributedQueues.html19:38
jogono guarantee of in order delivery19:39
jogoat least once delivery19:39
jogoand message sample19:40
jogovkmc: ^19:40
vkmcjogo, as in SQS message order is not guaranteed19:41
vkmcsequence information is required19:41
jogovkmc: is that true just for your API specs or do any existing backends have that behavior?19:42
vkmcjogo, for the API specs19:42
jogovkmc: so no backends have that behavior?19:43
vkmcjogo, AFAIK, no19:43
jogook, what about the other two properties19:43
vkmcI might be wrong though19:43
jogovkmc: anyone else who may know?19:44
vkmckgriffs|afk, malini|afk, alcabrera around? ^19:45
alcabreraI'm here.19:45
alcabreraI remember there was a time when zaqar guaranteed FIFO for the mongodb backend19:46
alcabreraI'm not sure if this still holds19:46
alcabreraFIFO itself guaranteeing things like: order is preserved, once-and-only-once, at-most-once19:46
alcabrerajogo: ^19:46
vkmcI'm not sure if it also true for the Redis driver19:47
alcabreraI'm not sure, either19:47
vkmcflaper87, ^19:47
jogowhat about the message sample property?19:48
jogovkmc alcabrera: so I ask because as far as I can tell, those properties are what helps amazon SQS scale really well19:48
jogoand if zaqar is trying to cover the SQS use case then I would assume it would hold the same properties as well19:49
alcabreramessage sample... let's see...19:49
alcabrerainteresting19:50
alcabrerajogo: by design, zaqar gives you all messages avaialble (paginated)19:50
alcabreraso it is different here19:50
vkmcjogo, of course, makes sense :)19:51
alcabrerait seems like SQS shards messages across storage differently19:51
jogoalcabrera: yeah, how does zaqar shard?19:51
alcabrerawhereas zaqar instead shards queues19:51
alcabreradifferent queues may live on different storage nodes19:51
jogoalcabrera: that sounds like individual queues are limited in size etc19:51
jogoand can be hurt by noisy neighbor syndrom etc19:52
alcabrerapossibly19:52
alcabrerayeah, there's definitely capacity problems if one queue gets too big. :)19:52
jogoalcabrera: yup19:53
flwang1flaper87: I'm reading your mail19:53
jogoalcabrera: so where/how can I get further information on this19:53
alcabrerajogo: check out the wiki: https://wiki.openstack.org/wiki/Zaqar, and feel free to ask more questions in here19:54
jogoalcabrera: hmm, I am thinking of posting this to the ML so flaper87 and others can chime in19:57
*** flwang1 has quit IRC19:57
jogoalcabrera: as these sound like questions that the wiki should answer19:58
alcabrerago for it, jogo. it's a good way to clarify these sorts of things, and I imagine many others are also curious about these properties of zaqar.19:58
alcabrerawith regards to asking on the ML19:58
jogoalcabrera: yeah, and I wanted to get a head start and getting answers to these questions well before the end of next cycle19:58
alcabreraawesome! :)19:59
vkmcthe long polling property was planned for K20:00
vkmchttps://blueprints.launchpad.net/zaqar/+spec/long-poll20:00
alcabrerathanks vkmc!20:01
vkmcnow wrt shared queues, I remember there was some plans too20:02
*** amitgandhinz has quit IRC20:16
*** amitgandhinz has joined #openstack-zaqar20:16
*** amitgandhinz has quit IRC20:21
jogoalcabrera vkmc: thanks, I started a ML thread20:36
alcabrerathanks, jogo. :)20:36
jogohttp://lists.openstack.org/pipermail/openstack-dev/2014-September/046271.html20:36
vkmcjogo, thanks!20:37
*** ametts has quit IRC20:40
*** ametts has joined #openstack-zaqar20:59
*** malini has joined #openstack-zaqar21:01
flwangjogo: thanks for the fantastic summary, but seems I can't see the image in you mail21:13
jogoflwang: I cut and pasted the middle part from http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/DistributedQueues.html (link at the bottom)21:14
flwangawesome21:15
* flaper87 back21:21
flaper87jogo: just read the backlog21:21
flaper87jogo: did you read this? https://wiki.openstack.org/wiki/Zaqar/Frequently_asked_questions#How_does_Zaqar_compare_to_AWS_.28SQS.2FSNS.29.3F21:21
flaper87is not very informative21:21
flaper87but it has something21:21
flaper87I'm sure we have a more detailed page21:21
flaper87but I can't find it21:21
flaper87fucking wiki21:21
flaper87jogo: just read your email, I'll likely reply tomorrow but thanks for raising those questions21:22
*** mpanetta has quit IRC21:23
*** sriram has quit IRC21:26
openstackgerritVictoria Martínez de la Cruz proposed a change to openstack/zaqar: Added checks enforcements rule to the developers manual  https://review.openstack.org/12142421:28
flaper87boris-42: there?21:29
flaper87vkmc: flwang malini around?21:29
vkmcflaper87, here21:29
flaper87and kgriffs|afk21:29
flaper87just a quick and hopefully not long request21:29
flwangflaper87: ~~~21:30
flwanglistening21:30
flaper87I'd like us to start working on the integration with other projects21:30
flwangawesome21:30
vkmc+100021:30
flaper872 projects that I'd like us to target first are: Heat and Horizon21:30
flaper87We've collected some use cases here: https://etherpad.openstack.org/p/zaqar-integrated-projects-use-cases21:30
flaper87I'll send an email tomorrow to start the discussion with people in those teams21:30
flaper87however, before sending that email, I'd like us to think a bit on how we can help them21:31
flwangI have mentioned that with kgriffs|afk about the integration21:31
flaper87and what we need to do so21:31
flwangand IMHO, it can prompt Zaqar a lot21:31
flaper87so, it'd be really nice if you could take 15 mins and add comments to those etherpads21:31
flaper87for example: Would you use prod/con or pub/sub for each use-case?21:32
flaper87Would you recommend separate queues or just 1 ?21:32
flaper87etc21:32
vkmcI can take a look to the Horizon ones21:32
vkmcit has been a while since I don't contribute to Horizon, but I'd truly like to go back to it21:32
flaper87there's no much we can add without interacting with each team but lets at least add something that can help starting the discussion21:32
flaper87vkmc: awesome21:32
vkmcand I know some Horizon folks, so I can ask them21:33
vkmcof course that the core questions would go to the ml21:33
flwangI can help on the heat+zaqar+ceilometer21:33
flaper87flwang: lets focus on heat and horizon for now21:34
flwangI think the heat's painpoint is how the ceilometer trigger the auto scale21:34
flaper87it'd be unrealistic to try to help them all at once21:34
flwangfine21:34
*** malini has quit IRC21:34
vkmctrue that21:34
flaper87we don't need to cover all the use cases, we can work on those in a per-milestone basis21:35
*** jchai has quit IRC21:35
vkmc:)21:35
vkmcflaper87, I'd also like to chat about the features jogo mentioned SQS has21:36
vkmcand add documentation for them if we are providing it, or discuss about the possibility of adding them, if we are not21:37
vkmcbbl21:39
flaper87we're providing it or well, we provide something better21:40
flaper87:D21:40
flaper87ok, we can talk about it later21:40
flaper87when you're back21:40
*** alcabrera is now known as alcabrera|afk21:52
vkmcback21:54
* vkmc wanna know 21:55
vkmc:D21:55
vkmcits too late for you though, we can chat tomorrow21:55
flaper87vkmc: so21:59
flaper87Zaqar guarantees FIFO which is something SQS, as stated in that link, doesn't do22:00
flaper87FIFO, however, depends on the backend driver22:00
flaper87if the backend storage can't guarantee FIFO then there's nothing Zaqar can do there22:00
flaper87Message distribution happens at a storage level, the storage itself will replicate the data and distribute it22:01
flaper87Just as for FIFO, the smarter the backend is with data distribution and replication, the more benefits the user will have22:01
flaper87With mongodb it'd be easy to have a per-region distribution22:01
flaper87with redis that's not really possible22:01
jogoflaper87: sounds good22:02
flaper87Messages are not distributed across multiple storage nodes, zaqar talks to 1 pool and the pool is responsible for doing the remaining job22:02
vkmcgreat22:02
flaper87jogo: you've a preview :D22:02
* flaper87 tries to stay away from work when is midnight but vkmc keeps forcing him to get back to it22:03
flaper87:P22:03
*** flwang1 has joined #openstack-zaqar22:03
flaper87(jooooooooooooooooooke)22:03
vkmcoh I told you we can chat tomorrow22:03
vkmcalthough I appreciate you are letting me know now22:03
flaper87vkmc: i know I know22:03
jogoflaper87: I am concerned about the implications of FIFO on scaling etc22:03
vkmc:D22:03
jogoflaper87: and how sharding is by queue and not messages22:04
jogoflaper87: anyway I look forward to seeing your email22:04
vkmcwe should document this in the how we compare to AWS section, I wasn't aware of mongo FIFO guarantee22:04
flaper87jogo: re FIFO, that's a fair concern. Depending on the storage it may have different costs22:04
flaper87jogo: and re sharding, we have thought about making the sharding key configurable. It really depends on the consumption pattern22:05
flaper87depending on whether the queue is write heavy or read-heavy it may be better to keep messages together in 1 shard or distributed in several22:06
flaper87I'll explain this thoughts better in the email22:06
jogoflaper87: kk22:06
flaper87these*22:06
vkmcmakes sense22:06
jogoflaper87: w.r.t. sharding model IMHO zaqar should be able to automatically select which one makes the most sense22:08
jogoand not add yet another config option22:08
flaper87jogo: now that we have flavors, we could do that in a more reliable way. there are some other related issues. For example, we're not using 1 db per queue because there's a chance we could hit mongodb's namespaces limit. This means that the sharding key selected will apply to all queues stored in the database `N`22:11
flaper87jogo: TBH, there are still some experiments left to do in sharding environments22:12
flaper87right now we prefer to recomend using replica sets22:12
flaper87which are safer and also easier to scale at the cost of requiring more space on disk22:12
flaper87(due to replication)22:13
flaper87kk, gtg now :)22:15
flaper87have a great rest of the day y'all22:15
*** flaper87 is now known as flaper87|afk22:16
vkmcthanks flaper87|afk, enjoy the rest of your evening o/22:16
*** sgotliv has quit IRC22:21
*** ametts has quit IRC23:08

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