Thursday, 2016-01-28

flwangas for 153581100:12
flwangi'm wondering if you can get the message id00:12
Eva-iflwang: oh00:12
flwangbecause at that stage, the message hasn't been written into db00:12
flwangand i don't think it's a bug00:14
Eva-iflwang: you're right, this complicates things much, I'll try to find a solution00:14
flwangit's most like a small feature00:14
flwangdon't care about the message id, unless there is a user jump in to require that00:15
Eva-ihm, together with therve we decided it's not a small feature, it's a small bug00:16
Eva-iI guess it's half small feature and half bug00:16
Eva-iflwang: okay, maybe we can at least add queue name to notification?00:17
flwangEva-i: yep, sure00:17
*** malini has left #openstack-zaqar00:17
Eva-iflwang: I'll modify the bug report then00:18
flwangEva-i: cool, thanks :)00:18
*** Qiming has quit IRC00:27
openstackgerritFei Long Wang proposed openstack/zaqar: Fix the TTL issue of subscriptions for MongoDB  https://review.openstack.org/27046400:39
flwangEva-i: as for the message id, it trigged me something01:03
Eva-iflwang: what it is?01:06
flwangkgriffs mentioned that we may should generate the message id by zaqar instead of by db01:06
kgriffsflwang actually, I saw somewhere the other day that they were having trouble synchronizing even atomic clocks with google spanner, but I think that if messages for any given queue are constrained to a cluster operating on the same local network, synchronizing to a local time server may give enough granularity.01:09
kgriffswould require further research and testing, but might be fruitful01:10
flwangkgriffs: do you think the python uuid lib can fit our requirement?01:10
Eva-iflwang: is so, in which Zaqar's driver layer the message id generation can be located?01:13
flwangEva-i: depends if we want to pass it to notification driver01:14
flwangi mean the pipeline01:14
*** Qiming has joined #openstack-zaqar01:22
*** flwang1 has quit IRC01:22
kgriffshmm, assuming you mean uuid version 1, that would give a theoretical granularity of 100 ns, and it will sort correctly01:25
kgriffsthat granularity is more than enough01:26
kgriffsalthough clocks will be very very unlikely to be synced within a 100 ns01:26
kgriffsbut if you could sync within 100 microseconds, that would support 10K id's created/sec without any collisions01:29
kgriffs(check my on my math)01:30
kgriffsto be honest, though, I wouldn't use the uuid module for this since it has a lot of checks and bit manipulation you don't need to waste CPU cycles on (not to mention it creates an object each time). Also, it takes up 128 bits in its binary form (more when encoded).01:33
kgriffsanyway, I gotta run, but there's some food for thought :)01:34
*** flwang1 has joined #openstack-zaqar01:35
Eva-ikgriffs: thank you01:36
kgriffssure thing!01:36
flwangkgriffs: thank you01:38
Eva-iSo I'm not sure, if I'm right, but if we want to include message id to notifications, we have two main options: 1. Generate message id in the transport layer 2. Do something with pipelines, for example, add additional pipeline after storage layer or make hook in storage layer, it can be done as decorator on storage layer methods.01:38
Eva-iHm. Solution 1 is bad. Better not to give subscribers message ids, before adding messages to database.01:43
flwangEva-i: so let's leave the message id for now and add a TODO in the code until we can figure out a good way to do that01:46
Eva-iflwang: want to hear a third solution I'm thinking of? If it's possible, it's the greatest solution.01:47
Eva-i*the third01:47
flwang?01:48
*** shakamunyi has joined #openstack-zaqar01:48
flwangEva-i: that's the 3rd?01:51
Eva-iflwang: not sure if it will work: 3. In the 'NotifierDriver' stage in a hook function make a manual call to the storage driver to get the result. Then inspect the result and take out message id. In the end of the hook function return the result, which will stop further moving through the pipeline (the same request will not get into the storage driver again) and allow transport layer to get the result.01:56
Eva-iflwang: of course in this case the user must ensure that the 'NotifierDriver' stage is the last in the pipeline, otherwise other stages, which the user has chosen in the pipeline, will not run.01:59
flwangit's the greatest?02:03
Eva-iflwang: it's the greatest solution a poor intern like me can imagine.02:04
flwanghaha02:05
flwangEva-i: we need a spec for that02:05
flwangwe do have some tech debt, we can pay them one by one :)02:06
Eva-iflwang: so you like that? I can make a spec for that, but before I'll try to make a quick prototype.02:07
Eva-ito see if it works02:07
flwangsorry, i didn't mean i like that02:07
flwangit's complicated for me at the first glance02:07
flwangi mean we need more discussion02:07
Eva-iflwang: so you mean the discussion can be done during spec review?02:09
*** shakamunyi has quit IRC02:10
*** shakamunyi has joined #openstack-zaqar02:10
*** shu-mutou has quit IRC02:15
flwangEva-i: or before drafting the spec02:15
flwangEva-i: i don't have time now to dig into it, at the first glance, it's complicated than the bug described02:16
flwangso hence why i said we need more discussion to avoid wasting time02:16
Eva-iflwang: oki, It will be just few lines of code(<10). I'll test the prototype during weekend.02:18
Eva-i(on my free time)02:20
flwangcool02:22
*** shu-mutou has joined #openstack-zaqar03:07
*** mdnadeem has joined #openstack-zaqar03:08
*** lei-zh has joined #openstack-zaqar03:08
Eva-iflwang:if I'm not mistaken, Zaqar will drop support for redis in the future?03:38
flwangEva-i: why you say that?03:41
flaper87o.003:42
flaper87no please03:42
flaper87:D03:42
Eva-iflwang: I don't know, maybe I misheard someone telling someone about it.03:42
flaper87Eva-i: we did that for sqlalchemy03:42
flwangflaper87: i can't believe you're around03:43
Eva-iflaper87: aha, I see, thank you03:43
flaper87flwang: I'm always around03:43
flaper87:D03:43
flaper87Also, I'm in UTC-4:3003:43
flaper87i know, i know... it's hard to keep up with my traveling03:43
flaper87:D03:43
flaper87it's like 11:30pm now03:43
flwangnot too late :)03:44
Eva-ifor me it's 6:45 am =)03:45
Eva-iit's like I live in another country03:45
Eva-igoing to sleep soon03:46
Eva-iis redis easy to install and start using it with Zaqar just like mongodb? I'd like to test some things.03:47
flaper87Eva-i: it is03:48
flaper87probably easier03:48
Eva-iflaper87: oki03:49
flwangflaper87: do you like the permanent subscription idea?03:51
flaper87flwang: haven't read about it03:51
flaper87where is it?03:51
flaper87is it a spec?03:52
flwangif user don't pass in TTL for subscription, then it will be a permanent subscription03:52
flwangunless user delete it03:52
flwanghttps://review.openstack.org/#/c/270464/203:52
flwangflaper87: ^03:52
*** flwang1 has quit IRC04:01
*** lei-zh has quit IRC05:16
zigoHi there !05:38
zigoThere's no tag for zaqar-ui.05:38
zigoCould someone tag a Mitaka .0b2 release so I can package it in Debian?05:38
zigoflaper87: Can you do it?05:38
zigoAlso, everything is called *-dashboard, it'd be nice to have zaqar-ui renamed as zaqar-dashboard too...05:39
*** lei-zh has joined #openstack-zaqar05:46
*** boris-42 has joined #openstack-zaqar07:17
*** barra204 has joined #openstack-zaqar08:16
*** shakamunyi has quit IRC08:19
*** mdnadeem has quit IRC08:19
*** mdnadeem has joined #openstack-zaqar08:20
*** achanda has quit IRC09:01
*** Qiming has quit IRC09:54
*** rcernin has joined #openstack-zaqar10:18
*** lei-zh has quit IRC10:40
*** Qiming has joined #openstack-zaqar10:54
flaper87zigo: oh mmh, that's weird. I thin I can but it'll need the PTLs +1 anyway11:44
flaper87think*11:44
zigoflaper87: There's no tag at all currently in that repo.12:31
thervezigo, It hasn't been released12:47
therveI don't think it's worth packaging just yet12:47
zigotherve: Could it be renamed zaqar-dashboard, just out of consistency?12:47
therveI don't know12:47
zigoWell, please consider it... :P12:48
*** amitgandhinz has joined #openstack-zaqar13:54
*** pradk has quit IRC13:58
*** sriram has joined #openstack-zaqar14:11
*** pradk has joined #openstack-zaqar14:40
*** pradk has quit IRC14:47
*** pradk has joined #openstack-zaqar14:50
*** mdnadeem1 has joined #openstack-zaqar14:56
*** ametts has joined #openstack-zaqar15:06
*** malini has joined #openstack-zaqar15:23
*** Qiming has quit IRC15:24
*** achanda has joined #openstack-zaqar15:32
*** achanda has quit IRC15:43
*** amitgandhinz has quit IRC16:40
*** amitgandhinz has joined #openstack-zaqar16:41
*** mdnadeem1 has quit IRC16:58
*** mdnadeem1 has joined #openstack-zaqar17:02
*** csoukup has joined #openstack-zaqar17:08
*** mpanetta has joined #openstack-zaqar17:09
*** mdnadeem1 has quit IRC17:18
*** kgriffs is now known as kgriffs|afk17:21
*** kgriffs|afk is now known as kgriffs17:27
*** amitgandhinz has quit IRC17:52
*** amitgandhinz has joined #openstack-zaqar18:01
*** kgriffs is now known as kgriffs|afk18:06
*** boris-42 has quit IRC18:13
*** pradk has quit IRC18:20
*** csoukup has quit IRC18:33
*** pradk has joined #openstack-zaqar18:34
*** kgriffs|afk is now known as kgriffs18:36
*** AJaeger has joined #openstack-zaqar19:20
AJaegerflwang: are you already awake?19:21
*** mpanetta has quit IRC19:29
*** mpanetta has joined #openstack-zaqar19:30
*** malini has quit IRC20:42
AJaegerseems we're not finding a common time, flwang ;(21:00
*** rcernin has quit IRC21:02
Eva-iAJaeger: Hi. Usually flwang is active this time. If he'll not appear tomorrow, you can probably consider writing an email to him.21:17
Eva-iAJaeger: hm... probably I'm wrong, because his weekend will start tomorrow21:18
*** rcernin has joined #openstack-zaqar21:27
*** amitgandhinz has quit IRC21:43
*** flwang1 has joined #openstack-zaqar21:48
*** sriram has quit IRC21:58
*** Eva-i has quit IRC22:14
*** Eva-i has joined #openstack-zaqar22:42
*** flwang1 has quit IRC22:45
*** flwang1 has joined #openstack-zaqar22:55
*** Eva-i has quit IRC23:00
*** Eva-i has joined #openstack-zaqar23:00
*** flwang1 has quit IRC23:30
*** Qiming has joined #openstack-zaqar23:32
*** kgriffs is now known as kgriffs|afk23:44

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