Monday, 2014-08-18

*** mustapha has joined #openstack-zaqar01:51
mustaphaHey! peps01:51
*** kgriffs|afk is now known as kgriffs02:02
*** kgriffs is now known as kgriffs|afk02:07
*** cpallares has quit IRC03:03
*** chandankumar has joined #openstack-zaqar05:00
*** AAzza_afk is now known as AAzza06:54
*** AAzza is now known as AAzza_afk07:56
*** flwang1 has joined #openstack-zaqar08:30
*** julienvey has joined #openstack-zaqar09:03
*** flwang1 has quit IRC09:34
*** flwang1 has joined #openstack-zaqar09:35
openstackgerritSergey Lukjanov proposed a change to openstack/zaqar-specs: Fix .gitreview due to the repo rename/move  https://review.openstack.org/11477910:29
*** flwang1 has quit IRC10:37
*** flwang1 has joined #openstack-zaqar10:38
*** flwang1 has quit IRC10:49
*** flwang1 has joined #openstack-zaqar11:06
*** vkmc has joined #openstack-zaqar11:10
*** vkmc has joined #openstack-zaqar11:10
*** fifieldt has joined #openstack-zaqar11:23
*** mpanetta has joined #openstack-zaqar11:56
openstackgerritFei Long Wang proposed a change to openstack/zaqar: Zaqar is depending on python-keystoneclient  https://review.openstack.org/11494412:04
*** mpanetta has quit IRC12:06
*** mpanetta has joined #openstack-zaqar12:07
*** mpee|away has joined #openstack-zaqar12:20
vkmcmalini|afk, hi! I was trying to spot why is the tempest-dsvm gate failing... the renaming in https://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/jenkins_job_builder/config/devstack-gate.yaml looks fine, what am I missing?12:20
*** flwang1 has quit IRC12:37
*** AAzza_afk is now known as AAzza12:38
*** sriram has joined #openstack-zaqar12:43
*** itisit has joined #openstack-zaqar13:26
*** malini has joined #openstack-zaqar13:26
*** amitgandhinz has joined #openstack-zaqar13:40
*** kgriffs|afk is now known as kgriffs13:41
*** kgriffs is now known as kgriffs|afk13:42
*** chandankumar has quit IRC13:42
*** ametts has joined #openstack-zaqar13:47
malinihello!!13:58
vkmchi malini!13:58
maliniheyyy vkmc! how are you?13:59
vkmcall good and you?13:59
malinigood :)13:59
maliniI just submitted a new patchset to update devstack - marconi —>zaqar13:59
vkmcoh cool :)14:00
maliniWill get the tempest one out shortly14:00
vkmcawesome14:01
vkmcI was checking that earlier today14:01
vkmcwe also have to perform the rename in Tempest14:02
*** mpanetta_ has joined #openstack-zaqar14:03
openstackgerritNataliia Uvarova proposed a change to openstack/zaqar: Improve benchmarking tool  https://review.openstack.org/11223614:06
*** mpanetta has quit IRC14:11
*** itisit has left #openstack-zaqar14:36
*** itisit has joined #openstack-zaqar14:41
*** kgriffs|afk is now known as kgriffs14:42
prashanthr_|afkgood morning ! :)14:42
*** prashanthr_|afk is now known as prashanthr_14:43
vkmchi prashanthr_!14:44
prashanthr_vkmc: Hello ! :)14:44
prashanthr_pencils down day of gsoc today14:44
vkmcyuuup14:45
vkmcwe have to submit the final evaluations tomorrow14:45
vkmcand then the code sample14:45
prashanthr_vkmc: True :)14:47
*** cpallares has joined #openstack-zaqar14:47
kgriffshi everyone. sorry for being MIA friday... lots of meetings14:52
vkmcAAzza, hey! did flaper87|afk address your comments in https://review.openstack.org/#/c/106346/?14:53
vkmchi kgriffs!14:53
kgriffswhat's all this pencil's down business?14:57
kgriffsgsoc is coming to a close?14:57
*** alcabrera|afk is now known as alcabrera14:57
vkmckgriffs, yes... today is the last day of GSoC14:57
kgriffsoh!14:58
alcabreragood morning, all. :)14:59
alcabrerayeah, GSoC/OPW both end today. Firm "pencil's down" date is today.14:59
alcabrera"end" as in - time to start the final eval.14:59
kgriffsI hope everyone learned some cool stuff this summer that will be useful in future adventures. :D14:59
alcabreraoh yeah! I hope so, too. :)15:00
vkmcthanks kgriffs, alcabrera!15:01
vkmcI feel I learned a lot although I know I still have a long way to go15:02
vkmcand I'm happy I finally could get officially involved with the Marconi/Zaqar project15:02
alcabreraI have so much to learn, as well. It never ends!15:02
alcabrerahurray, vkmc!15:03
vkmctrue that... it never ends, and I'm glad it's like that in our profession15:04
vkmcwe won't ever get bored15:04
vkmchope I can keep learning from you guys, you are amazing developers with an incredible experience15:05
kgriffsYou cease to be wise when you think you have learned everything there is to know.15:05
AAzzakgriffs: not sure :) i think no, we agreead to use sorting by name, but after he updated patch, he removes sorting totally, so it is better to clarify with him tomorrow.15:07
kgriffskk15:07
prashanthr_True. Gsoc was one of the greatest experiences :)15:08
vkmcAAzza, cool :) thanks15:09
vkmcAAzza, could you leave record of that in the tracker?15:12
vkmcAAzza, well spotted btw15:12
*** mpanetta_ is now known as mpanetta15:14
*** chandankumar has joined #openstack-zaqar15:20
kgriffsprashanthr_: btw, how's the redis work going?15:27
prashanthr_kgriffs: I was not well for two days :(15:27
prashanthr_recovering today15:27
prashanthr_Will resume work tomorrow15:27
kgriffsoh, sorry to hear that. get well soon!15:29
prashanthr_thank you kgriffs !!15:29
*** julienvey has quit IRC16:01
*** chandankumar has quit IRC16:10
*** AAzza is now known as AAzza_afk16:11
*** kgriffs is now known as kgriffs|afk16:29
*** reed has joined #openstack-zaqar16:30
*** kgriffs|afk is now known as kgriffs17:06
kgriffsmalini: is there a tempest patch or something that I can +1 ?17:35
malinikgriffs: yes..let me get u the link17:35
malinikgriffs: devtstack needs to go first https://review.openstack.org/#/c/111399/17:36
malinitempest https://review.openstack.org/#/c/114980/17:36
* kgriffs clicks17:37
kgriffsok, I +1's the devstack patch17:39
kgriffsonce that lands, I'll do tempest17:39
malinithanks kgriffs!17:39
kgriffsthanks for submitting those!17:39
maliniI just pinged the devstack core reviewers17:39
maliniyw :)17:40
vkmc:) and once those get merged we have to ninja approve https://review.openstack.org/#/c/114776/17:40
kgriffssure thing17:41
vkmcoh kgriffs, how can I regenerate the conf file?18:06
vkmcthe transport options are missing18:06
kgriffsthere is a script for doing that18:08
kgriffstools/config/generate_sample.sh18:08
kgriffsit is sort of broken on Mac (or used to be) FYI18:08
vkmcthanks18:09
kgriffsshould really be ported to python, but nobody has taken the time to do it yet. :p18:09
kgriffsmalini, vkmc: I learned something interesting last week18:13
vkmckgriffs, what did you learn?18:14
maliniI am curious too..18:14
kgriffsif you use a tiered NTP setup, meaning You run your own NTP box close to your servers, and then have that NTP server, in turn, sync with the public pool, you are supposed to get clock sync to ~500 microseconds18:15
maliniI am sure mpanetta wud apprciate tht info18:16
kgriffsthat is pretty cool, because it means we may be able to switch to using timestamp-based IDs after all. The trick is, you artificically delay each queue by V variance18:16
vkmcand what would happen if the delay isn't added?18:17
kgriffswhere V = max_expected(clock_drift + db_latency + context_switch_overhead + fudge_room)18:18
kgriffsvkmc: what might happen is that in between calculating the timestamp-based ID and persisting to the DB, you can have a temporal inversion. Let me see if I can make a little drawing to explain...18:19
kgriffs(in any case, it can ultimately lead to a message getting missed by a client)18:19
kgriffsthe delay-queue scheme isn't perfect... there is always the chance that something crazy will happen that will cause a message to take 10 seconds to persist, but it seems like that should be manageable by ops just ensuring there is always enough headroom/capacity on the deployment to prevent overload.18:21
kgriffslots of notes here, but they are a bit scatter-brained at the moment: https://gist.github.com/kgriffs/2f83c10654f1ace06fc318:22
vkmcit's good because we count with more information, but there is always the chance of something going wrong18:23
vkmctime is one of the more complex problems in computing18:23
vkmcs/more/most18:23
kgriffsyep, sure is18:23
* vkmc clicks18:23
kgriffsI'll be back in a few minutes18:24
vkmcthanks for sharing :)18:24
*** kgriffs is now known as kgriffs|afk18:24
vkmchm the generate_sample.sh is not working http://paste.openstack.org/show/96956/18:28
vkmcas kgriffs|afk warned18:29
*** alcabrera is now known as alcabrera|afk18:33
*** kgriffs|afk is now known as kgriffs18:43
kgriffshere is the explanation for the race condition and need for a "variance" window: http://www.educreations.com/lesson/view/delayed-queues/23270365/?ref=appemail18:53
vkmccool18:54
vkmcofftopic, how we call the service Zaqar provides? Message Queing service, Message Queueing service, Queues service, Messaging service18:56
vkmc?18:56
vkmcI remember we chatted about this in a meeting18:56
kgriffsgood question. iirc the idea was to put the focus on "messages"18:57
kgriffsprogram name ought to be changed to something like18:57
kgriffsOpenStack Messaging and Notifications Service18:57
kgriffsbrb (meeting)18:58
*** kgriffs is now known as kgriffs|afk18:58
vkmcright, let's add that to the etherpad so we all follow that convention19:02
*** kgriffs|afk is now known as kgriffs19:25
*** malini has quit IRC19:32
*** AAzza_afk is now known as AAzza19:58
*** vkmc has quit IRC19:58
*** vkmc has joined #openstack-zaqar19:58
*** vkmc has joined #openstack-zaqar19:58
*** alcabrera|afk is now known as alcabrera20:04
vkmckgriffs, btw I saw the variance window explanation :) it makes sense20:22
vkmcI wonder though which is the criteria on choosing the length of the window20:23
kgriffsthere are several factors20:23
kgriffsfirst is the expected clock drift between webheads (boxes running uwsgi or gunicorn)20:23
kgriffsthen you have to decide how long a given worker thread (probably a green thread) may ever stall20:24
kgriffsthen you have to think about how long it might take to persist the message in the DB20:25
kgriffsthose last two basically determine the time window between assigning a timestamp-based ID, and then actually writing it to the DB, after which is can be read back out by a subsequent client request20:26
kgriffsdoes this make any sense? :p20:26
vkmcthat is part of the variation formula you detailed before20:27
vkmcyes :)20:27
kgriffsyeah20:27
vkmcif the variation is enough then this will work as expected20:28
vkmcbut what if the variation is not enough20:28
kgriffsthen you have the potential to miss messages20:28
kgriffsthe potential will increase as the client request frequency increases20:29
alcabrerathat variation factor would also need to be recalculated for every update in the software, every update in the hardware20:29
kgriffs(and as the number of outliers increases due to insufficient V)20:29
kgriffsalcabrera: adding a fudge factor can mitigate the risk there, also provide some wiggle-room to keep ahead of system load by adding capacity so things to slow down to the point that outliers become more common.20:30
kgriffsbut yeah, you would also need to be careful about software not slowing things down, and hardware changes20:31
alcabrerarisk can be reduced, I agree20:31
alcabreraand risk can be further reduced by enforcing homogeneous hardware on deployments20:31
alcabrerathe unfortunate part is that no guarantee can be made20:31
kgriffsit will always be there, however. On the upside, you get better scaling options since you don't need to rely on a centralized counter mechanism thingy20:32
alcabreraas long as time is used as the consistency mechanism20:32
kgriffsyep. This is the fundamental tradeoff in a stateless message feed design. Atom Hopper has the same problem.20:32
kgriffsit may also provide some insight into why some queuing systems do not guarantee message delivery, ordering20:34
alcabreraagreed ^20:34
alcabreraif you guarantee FIFO, you have a CP system20:34
kgriffsspeaking of ordering, as long as your clock granularity is below expected throughput, ordering is virtually guaranteed. otherwise not. :p20:34
alcabreraFIFO == linearizable20:34
kgriffshow does google solve it?20:35
alcabrerathere's the hardware clocks approach, in one paper20:35
kgriffsyep, that's what I was about to say20:35
kgriffs #cheaters20:35
alcabrera:P20:35
mpanetta#bigmoney :P20:35
kgriffs #notopenstack20:36
* kgriffs needs a hug20:36
* mpanetta gives kgriffs a GPS clock source instead.20:36
* kgriffs goes off to find a turing machine to play with20:36
alcabrera:)20:37
alcabreraas long as zaqar clearly advertises that it does not guarantee FIFO, I think it's okay to move away from the atomic counter scheme20:37
* alcabrera offers hugs to all20:38
kgriffsalcabrera: we would also have to rescind the delivery guarantee. "In extenuating circumstances a client may miss a message. But here is how you make the risk of that virtually zero..."20:39
alcabrerayup!20:39
alcabrera"at least once" and "at most once" properties are also lost without a mechanism to enforce consistency20:39
alcabrera**linear consistency20:40
kgriffshmmm, I'm trying to decide if you can still guarantee "at most once". I think you can?20:40
kgriffsoh, I guess it would depend on not having a collision in the timestamp value. so you have to granular enough to support expected throughput.20:41
alcabreraif shards diverge because of a network partition, that might also cause problems with "at most once"20:41
kgriffs100-nanoseconds should be enough. ;)20:41
alcabrerawell, once we get to shard pools20:41
alcabreraas it is, a network partition would just result in "not found"20:41
alcabreraor 50020:41
kgriffsyeah20:42
kgriffsanyway, lots of juicy CS problems in this "humble" project of ours. :p20:42
alcabreraoh yeah! :D20:42
alcabrerayou chew on distributed systems, you20:42
alcabrerayou're forced to the forefront of CS20:42
alcabrera:)20:42
kgriffssrsly.20:42
alcabreracuriously, the same thing happens with program correctness20:42
alcabreraand performance20:43
alcabreraand..20:43
alcabreranaming!20:43
alcabrera>.>20:43
kgriffsmeeting in 15 min20:45
kgriffsalcabrera: NAME ALL THE THINGS!20:46
* kgriffs dies trying20:46
alcabreraD:20:46
* alcabrera revives kgriffs20:46
kgriffsThe three hardest things in CS20:46
kgriffs1. Time-based algorithms20:46
kgriffs2. Naming stuff20:47
kgriffs3. Responding to ALL Hacker News comments20:47
alcabrerathat third one is just painful. >.>20:47
alcabreraI don't even look at HN any more20:47
kgriffsit's the new slashdot. :p20:47
kgriffsa victim of the dehumanizing nature of the internets20:48
kgriffs(p.s. - read this! http://www.amazon.com/Leaders-Eat-Last-Together-Others-ebook/dp/B00G3L0ZTQ)20:48
kgriffsalcabrera: that reminds me...20:49
kgriffshttp://trololololololololololo.com/20:49
alcabrera:P20:50
alcabrerai wasn't aware of the history behind tro(lo * 10) 'til just now20:51
alcabreraTIL: http://knowyourmeme.com/memes/trololo-russian-rickroll20:51
vkmctrololololo20:51
vkmclololo20:51
* vkmc sings20:51
*** AAzza is now known as AAzza_afk20:54
vkmcmeeeeting21:01
alcabreraheading out. you all have an awesome meeting! :)21:01
vkmcalcabrera, babai o/21:02
*** alcabrera is now known as alcabrera|afk21:05
vkmckgriffs, meeting?21:06
*** itisit has quit IRC21:08
kgriffsoh, crap21:11
kgriffslost track of time21:11
kgriffsvkmc: nobody around?21:12
vkmchere :)21:13
vkmclet's ping people21:13
flwangmeeting?21:14
vkmc!21:14
*** mpanetta has quit IRC21:26
*** sriram has quit IRC21:27
*** malini has joined #openstack-zaqar21:31
*** malini has quit IRC21:33
*** malini has joined #openstack-zaqar21:33
*** itisit has joined #openstack-zaqar21:51
*** cpallares has quit IRC21:51
*** vkmc_ has joined #openstack-zaqar22:10
*** vkmc has quit IRC22:11
vkmc_:( darn22:13
*** vkmc_ is now known as vkmc22:13
*** vkmc has quit IRC22:13
*** vkmc has joined #openstack-zaqar22:13
vkmcmy connection died22:14
*** flwang1 has joined #openstack-zaqar22:14
vkmckgriffs, so... I asked, how do you feel about the graduation22:14
*** amitgandhinz has quit IRC22:15
kgriffsI was feeling optimistic until that thread blew up22:15
kgriffsTBH, I don't see why a project has to be "perfect" before it graduates, but that seems to be the prevailing wind and I am honestly too burned out to fight it any more22:16
vkmcI think that the barrier is high22:17
vkmcbut we have what it takes22:17
vkmcand Zaqar team already faced the graduation process before22:17
kgriffsfor us to have a good chance, we'll have to start socializing each of the "concerns raised" on the ML or something22:23
kgriffs(see relevant section of https://etherpad.openstack.org/p/marconi-graduation)22:23
kgriffsdo one at a time, in order of least controversial to most.22:24
*** malini has quit IRC22:26
vkmcyeah22:27
kgriffsvkmc: different topic22:27
vkmcsure22:27
kgriffsit just occurred to me that you would only have to delay queues when listing messages. claiming messages doesn't have that race condition problem22:27
kgriffs(since you don't provide a marker)22:28
kgriffsI'm really tempted to do a timestamp-ID patch for mongo driver and benchmark it22:28
vkmcyeah with claims you access with the id22:29
vkmcthe problem is on accesing the collection22:29
vkmcright?22:29
kgriffsit's when you list messages - page through them with a marker22:30
kgriffsthe problem occurs because you use a marker that would be based on the timestamp ID22:30
* kgriffs is glad to tell someone all this in case he is hit by a bus tomorrow22:30
vkmchaha22:30
kgriffsROFL - https://twitter.com/flaper87/status/501490742955892737/photo/122:32
vkmcoh pls no22:32
vkmclol22:32
*** staphae has joined #openstack-zaqar22:40
staphaeauthenticating with keystone?22:42
*** malini has joined #openstack-zaqar22:44
*** kgriffs is now known as kgriffs|afk22:46
*** itisit has quit IRC22:51
malini,,,,,lop[22:51
malini[]=p-ko ./,;'\]]22:52
*** malini has left #openstack-zaqar22:53
*** itisit has joined #openstack-zaqar22:54
*** sriram has joined #openstack-zaqar23:06
*** staphae has quit IRC23:09
*** amitgandhinz has joined #openstack-zaqar23:16
*** amitgandhinz has quit IRC23:20
*** itisit has quit IRC23:28
*** sriram has quit IRC23:47
*** itisit has joined #openstack-zaqar23:55

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