Tuesday, 2014-11-18

« Monday, 2014-11-17 Index Wednesday, 2014-11-19 »
*** davideagnello has quit IRC00:02
*** davideagnello has joined #openstack-zaqar00:03
*** davideagnello has quit IRC00:05
*** achanda has joined #openstack-zaqar00:08
*** davideagnello has joined #openstack-zaqar00:08
*** davideagnello has quit IRC00:10
*** davideagnello has joined #openstack-zaqar00:12
openstackgerritMerged openstack/zaqar: Claim post requires a body  https://review.openstack.org/13421400:16
*** kgriffs|afk is now known as kgriffs00:21
openstackgerritBoris Pavlovic proposed openstack/zaqar: Add rally job related files  https://review.openstack.org/13513400:26
boris-42flaper87: around?00:29
boris-42=)00:29
*** kgriffs is now known as kgriffs|afk00:30
*** sgotliv has quit IRC00:38
*** bradjones has quit IRC00:48
*** amitgandhinz has joined #openstack-zaqar00:48
*** bradjones has joined #openstack-zaqar00:49
*** amitgandhinz has quit IRC00:53
*** sriram has joined #openstack-zaqar00:59
*** sriram has quit IRC01:01
*** davideagnello has quit IRC01:04
*** davideagnello has joined #openstack-zaqar01:04
*** sriram has joined #openstack-zaqar01:11
*** davideagnello has quit IRC01:13
*** sriram has quit IRC01:20
*** vkmc has joined #openstack-zaqar01:25
*** jeffrey4l has quit IRC01:26
*** achanda has quit IRC01:31
*** achanda has joined #openstack-zaqar01:32
*** achanda has quit IRC01:36
*** jeffrey4l has joined #openstack-zaqar01:38
*** davideagnello has joined #openstack-zaqar01:49
*** davideagnello has joined #openstack-zaqar01:49
*** jeffrey4l has quit IRC02:10
*** jeffrey4l has joined #openstack-zaqar02:21
*** X019 has quit IRC02:32
*** vkmc has quit IRC02:38
*** X019 has joined #openstack-zaqar02:43
*** kgriffs|afk is now known as kgriffs02:59
*** exploreshaifali has joined #openstack-zaqar03:04
openstackgerritJeffrey Zhang proposed openstack/zaqar: Version discovery for root URI  https://review.openstack.org/13009403:05
openstackgerritMerged openstack/zaqar: pooling conf is using a wrong deprecated conf  https://review.openstack.org/13293703:15
*** exploreshaifali has quit IRC03:34
*** boris-42 has quit IRC03:47
*** flwang2 has joined #openstack-zaqar04:21
*** flwang1 has quit IRC04:21
*** duanhf has joined #openstack-zaqar04:21
*** flwang2 has quit IRC04:25
*** flwang1 has joined #openstack-zaqar04:48
*** achanda has joined #openstack-zaqar05:01
*** miqui has joined #openstack-zaqar05:38
*** boris-42 has joined #openstack-zaqar05:50
*** achanda has quit IRC05:51
*** achanda has joined #openstack-zaqar06:06
*** achanda has quit IRC06:08
*** achanda has joined #openstack-zaqar06:10
*** achanda has quit IRC06:59
*** sgotliv has joined #openstack-zaqar07:14
*** exploreshaifali has joined #openstack-zaqar07:40
*** achanda has joined #openstack-zaqar07:42
openstackgerritJeffrey Zhang proposed openstack/zaqar: Use the oslo.serialization instead of openstack/common/jsonutils  https://review.openstack.org/13518707:51
openstackgerritJeffrey Zhang proposed openstack/zaqar: Use the oslo.serialization instead of openstack/common/jsonutils  https://review.openstack.org/13518707:56
*** achanda has quit IRC08:02
*** exploreshaifali has quit IRC08:07
openstackgerritJeffrey Zhang proposed openstack/zaqar: Remove the outdated openstack common modules  https://review.openstack.org/13388608:08
openstackgerritFlavio Percoco proposed openstack/zaqar: Test message delete when claim expires  https://review.openstack.org/13518908:09
*** miqui has quit IRC08:11
openstackgerritFlavio Percoco proposed openstack/zaqar: Test message delete when claim expires  https://review.openstack.org/13518908:14
*** dynarro has joined #openstack-zaqar08:17
*** dynarro_ has joined #openstack-zaqar08:17
jeffrey4lflaper87, about Update oslo-config-generation code. Now there is no zaqar.conf.sample file. If your PS merged in, we will never get a full sample file from the source code.08:19
jeffrey4lflaper87, ^08:20
flaper87jeffrey4l: we removed the sample file in a previous commit08:20
flaper87jeffrey4l: FWIW, the oslo.log thing will be fixed before the next release08:21
flaper87I think we're fine because we'll fix this before the release08:21
flaper87I'll file a bug for that08:21
flaper87does the above sound good ?08:21
jeffrey4lflaper87, ok. sound good.08:21
flaper87jeffrey4l: in the oslo team, we're working on getting oslo.log done this cycle08:21
flaper87that's why I thought it'd be worth it to still merge the patch08:22
jeffrey4lyup.08:22
flaper87sorry, I dropped a very short comment in that review, I should have explained this better08:22
flaper87brb08:22
jeffrey4lI saw the patch is coming on in the oslo.log08:22
flaper87right08:22
jeffrey4lGot it.08:23
jeffrey4lI am ok with your PS.08:23
flaper87awesome, thanks for the thoughtful review08:27
*** duanhf has quit IRC08:28
jeffrey4lbecause I make a same commit. But i found the openstack/common/log.py issue and wait for the oslo.log's release. The the commit is still lying in my private repos. ;p08:29
openstackgerritMerged openstack/zaqar: Update oslo-config-generation code  https://review.openstack.org/13501208:33
*** sgotliv has quit IRC08:52
*** reed has joined #openstack-zaqar09:09
flwang1flaper87: ping09:42
flaper87flwang1: pong09:48
flwang1flaper87: do you have a few min to discuss the notification?09:48
flaper87flwang1: ^09:48
openstackgerritFlavio Percoco proposed openstack/zaqar-specs: Spec for notification service  https://review.openstack.org/12919209:48
flaper87ops09:48
flaper87flwang1: ^09:48
flaper87I'll do my taskflow research now09:49
flaper87flwang1: yup09:49
flaper87lets discuss09:49
flwang1so for now, we still keep queue and don't want to introduce 'topic' in notification service, is it?09:50
flaper87right, it's not that we don't want to but we don't need it09:50
flaper87flwang1: I added a subscription example to the spec09:51
flwang1flaper87: ok09:51
flaper87I still have to update it a bit more but I wanted you to take a look at that09:52
flwang1yep, i'm reading it09:52
flaper87so I pushed what I had09:52
flwang1thanks for that09:52
flaper87flwang1: what can I say, I'm a nice guy09:53
flaper87:P09:53
flaper87let me turn modesty on09:53
flwang1flaper87: you do and deserved a good-man medal09:54
flwang1flaper87: some questions about the post body09:55
flwang11. source09:55
flwang1source is like a specific term for 'queue'09:55
flwang1it would be hard to switch to 'topic' if we decide to remove queue eventually, IMHO09:56
flaper87flwang1: if we switch to topic, it'll be the topic. Read the source as the container where messages are being sent to09:57
flaper87the implementation won't change, instead of triggering events from queues we would do it from topics09:58
flwang1as for the publisher, did you mean put the uri/address/location into the 'options'?10:01
flwang1instead of having a individual item?10:01
flaper87flwang1: that'd be part of `options`10:02
flaper87publisher is just the type of publisher10:02
flaper87then options is what we pass to the publisher when we create an instance10:03
flwang1flaper87: ok10:04
flwang1I think it works10:05
flaper87w0000000000000000000000000000000000t10:08
flaper87flwang1: I like the way you think10:08
flaper87I still have to figure out the workers thing10:08
flaper87that's going to be hard10:08
flwang1flaper87: yep, so you still prefer to leverage taskflow?10:09
flaper87I HATE PEP810:09
flaper87flwang1: I'm doing some research there, that was my first option, TBH.10:09
flaper87it'd be sad to have to write that code ourselves10:10
flaper87but I need to dig more into how it works10:10
flwang1flaper87: btw, another related question is the code structure10:10
flwang1flaper87: you know, now we're putting the api, storage and transport layer under queues folder/package10:11
flaper87right10:11
flwang1flaper87: but after introduce notification, you know, technically, it's a service which maybe running on the same level as queue/messaging service10:12
*** sgotliv has joined #openstack-zaqar10:12
flwang1flaper87: so my point is it would be a little weird if we still put the notification service code under queue folder10:12
flaper87flwang1: a bit of history there10:12
flwang1in other words, I'm thinking could we move api/storage/transport to upper layer10:13
flaper87At the beginning we wanted to have 2 separate services for that and kept queues separate10:13
flaper87and we moved everything under queues/10:13
flaper87I still think it makes sense10:13
flaper87I mean, we should have notifications/{transport,storage} queues/{transport,storage}10:13
flaper87it'll help to keep code grouped by context10:13
flwang1how about the api?10:14
flaper87and, in the future, it'll be easier to move around if needed10:14
flaper87flwang1: same, each package should've its own API10:14
flaper87thoughts?10:14
flwang1flaper87: ok, it makes more sense for me10:14
flaper87awesome10:14
flaper87:D10:14
flwang1flaper87: and I prefer to implement the mongodb driver firstly, thoughts?10:15
flaper87flwang1: sounds good to me10:16
flwang1flaper87: cool10:16
openstackgerritFlavio Percoco proposed openstack/zaqar: Test message delete when claim expires  https://review.openstack.org/13518910:20
flwang1flaper87: so as for the code structure, does that mean we will have a separate process for notification service?10:22
flwang1flaper87: and user can decide if deploy it based on their requirement?10:22
flwang1I'm seeing many duplicate code :)10:25
*** exploreshaifali has joined #openstack-zaqar10:25
openstackgerritFlavio Percoco proposed openstack/zaqar-specs: Deprecate queues in favor of topics  https://review.openstack.org/13401510:34
flaper87flwang1: no spearate process for notifications10:34
flaper87it'll be the same code10:34
flaper87flwang1: what code is being duplicated?10:34
flaper87Basically everything is different for both packages10:34
flaper87flwang1: we should probably move the bootstrap one level up10:35
flwang1flaper87: that's my point10:35
flaper87flwang1: but just the bootstrap10:35
flaper87I may be missing something, though10:35
flwang1flaper87: me too.10:35
flwang1:)10:35
flwang1if we move the bootstrap to up level, it should be ok10:36
flaper87flwang1: awesome10:36
flaper87I like easy fixes for hard problems10:36
flaper87or not that hard10:36
flaper87whatever, easy fixes are always welcome10:36
flaper87:D10:36
flwang1flaper87: +110:37
flwang1flaper87: I will move the bootstrap and refactor it to distinguish queue and notification code10:38
flaper87flwang1: awesome10:39
flaper87flwang1: btw, I replied to your comments in the s/queue/notification/ spec10:39
flwang1flaper87: cool, thank you, dude10:39
flaper87my pleasure10:41
*** dynarro_ has quit IRC10:44
*** dynarro has quit IRC10:44
*** cpallares has joined #openstack-zaqar11:05
sgotlivflaper87, ping11:21
*** vkmc has joined #openstack-zaqar11:28
vkmcmorning :)11:33
kragnizvkmc: o/11:35
vkmckragniz, \o11:35
exploreshaifalimorning! \o/11:37
openstackgerritOpenStack Proposal Bot proposed openstack/zaqar: Updated from global requirements  https://review.openstack.org/13480311:38
*** bradjones_ has joined #openstack-zaqar11:38
cpallaresvkmc: o/11:39
cpallareskragniz: o/11:39
cpallaresexploreshaifali: o/11:39
*** bradjones has quit IRC11:39
*** bradjones_ is now known as bradjones11:39
*** bradjones has joined #openstack-zaqar11:39
vkmccpallares, \o11:39
kragnizcpallares: \o11:40
exploreshaifalicpallares, \o11:40
*** sgotliv has quit IRC11:43
*** sgotliv has joined #openstack-zaqar11:43
*** duanhf has joined #openstack-zaqar11:43
*** duanhf has quit IRC12:13
flaper87GOOOOOOOOOOOOOOOOOOOOOD MORNING12:24
vkmcexploreshaifali, hi there :) I didn't notice you were around12:25
vkmco/12:25
exploreshaifalivkmc, \o12:25
vkmcflaper87, hi you!12:26
flaper87vkmc: hey hey :)12:35
flaper87https://twitter.com/flaper87/status/53468621684395212812:35
vkmclol12:36
vkmcyes we do12:36
cpallareslol12:36
cpallaresflaper87: o/12:37
cpallares:P12:37
vkmcflaper87, o/12:37
cpallaresvkmc: \o/12:38
vkmckragniz, after the teletubbies/LOTR chat we had yesterday... you cannot get back... you are a zaqarian12:38
vkmccpallares, \o)12:38
exploreshaifaliyes kragniz now you cannot get back ;)12:39
*** malini has joined #openstack-zaqar12:40
* kragniz embraces the zaqar12:41
flaper87LOL12:45
flaper87embrace your future, zaqar will conquer the world and you'll be put in a queue and left there forever12:45
flaper87I should stop watching sci-fi12:45
vkmcomg no12:47
vkmcinfinite ttl12:47
kragnizflaper87: sounds like that queue isn't working very well12:47
vkmckragniz, it works perfect, he assigned an infinite ttl for you... that's obscure magic12:48
kragnizvkmc: D:12:48
kragnizhe knew what he was doing12:48
* kragniz shakes his fist at flaper87 12:49
exploreshaifalikragniz, probably you are the first one to get infinite ttl12:50
exploreshaifaliright vkmc ^12:50
flaper87exploreshaifali: looooooool, good thing you always think positive12:51
flaper87:D12:51
flaper87exploreshaifali: that's right, kragniz you should feel blessed12:51
flaper87>.>12:51
exploreshaifaliflaper87, :D12:51
kragniz<.<12:51
*** X019 has quit IRC12:51
*** cpallares has quit IRC12:56
flaper87btw, I took a deeper look at taskflow, I think it's worth using it, I'll write everything down in the spec12:57
*** cpallares has joined #openstack-zaqar12:57
*** cpallares has quit IRC12:57
*** cpallares has joined #openstack-zaqar12:58
*** cpallares has quit IRC12:58
*** cpallares has joined #openstack-zaqar12:59
kragnizcpallares is showing off her fancy ipv6 address12:59
cpallareskragniz: Yeah, gotta show that off.13:00
cpallaresJust making sure you all are paying attention to it.13:00
*** malini has quit IRC13:03
flaper87ppl, I'm heading to the office, bbib please, make noise, break things but no zaqar13:21
flaper87also, doing reviews would be nice13:21
vkmcflaper87, have fun!13:21
flaper87vkmc: https://review.openstack.org/#/c/134236/ <- this one is blocking another one13:22
flaper87vkmc: yeah, right.... like the office is fun13:22
flaper87:P13:22
flaper87Python Meetup tonight, w000000000000000t13:22
vkmcflaper87, that needs rebase IIRC13:22
flaper87nah13:22
flaper87I mean, yeah but now13:23
flaper87merge won't fail13:23
vkmcoka13:23
flaper87otherwise gerrit would've let us know13:23
flaper87right gerrit? right?13:23
flaper87openstackgerrit: ^ ANSWER YOU $#%#^@$ BOT13:23
flaper87openstackgerrit: rude13:23
vkmcdone done13:23
flaper87awesome, leaving, bbib13:24
vkmc:) ttfn13:24
*** jchai has joined #openstack-zaqar13:51
*** cpallares is now known as cpallares_afk14:00
*** cpallares_afk is now known as cpallares14:02
*** exploreshaifali has quit IRC14:03
*** sriram has joined #openstack-zaqar14:11
*** X019 has joined #openstack-zaqar14:41
*** amitgandhinz has joined #openstack-zaqar14:43
*** jeffrey4l has quit IRC14:45
*** ametts has joined #openstack-zaqar14:51
cpallaresvkmc: Are you working on the persistent transport spec already? Or are you still waiting for the spec to be reviewed?14:51
cpallaresvkmc: I don't remember what part of the API spec still needs to be completed.14:52
vkmccpallares, I haven't started but I should start ASAP14:52
vkmccpallares, do you have a link for the API spec_14:52
vkmcor something so I can see the code14:52
* cpallares looks for it14:52
cpallaresvkmc: https://blueprints.launchpad.net/zaqar/+spec/cross-transport-api-spec14:53
cpallaresthat's the blueprint14:53
*** kgriffs is now known as kgriffs|afk14:53
vkmcI know that, I meant if there is some work already done on that14:54
cpallaresvkmc: https://review.openstack.org/#/c/61476/14:55
vkmccool :)14:56
vkmcI'll check it out later14:57
*** kgriffs|afk is now known as kgriffs14:58
flaper87back15:00
*** dynarro has joined #openstack-zaqar15:00
*** dynarro_ has joined #openstack-zaqar15:00
cpallaresThat was a short meetup15:02
flaper87LOL, the meetup starts in a couple of hours\15:03
*** openstackgerrit has quit IRC15:04
*** openstackgerrit has joined #openstack-zaqar15:04
flaper87we haven't discussed what to do with the message body and whether it makes sense to treat it as a blob as we discussed at the summit15:05
*** jeffrey4l has joined #openstack-zaqar15:06
*** sgotliv has quit IRC15:24
*** sgotliv has joined #openstack-zaqar15:26
*** sgotliv has quit IRC15:30
cpallaresflaper87: what do you mean by blob?15:32
flaper87cpallares: http://es.wikipedia.org/wiki/Binary_large_object15:32
vkmcyeah we have to discuss that15:32
vkmcIMO it makes sense to manage that as a blob15:32
flaper87I mean, right now we required the body to be something json-encodable15:32
*** sgotliv has joined #openstack-zaqar15:32
flaper87but we've discussed a couple of times to stop doing that15:33
flaper87and just treat it as binary data15:33
vkmcsomething json-encodable is too constraining15:33
flaper87but that means we'll have to stop using json :)15:33
flaper87which I'm ok with15:33
vkmcwe can use msgpack15:33
vkmcflaper87, lemme know if you have feedback for this https://etherpad.openstack.org/p/zaqar-serialization-protocol-ws15:34
vkmcright know msgpack wins15:35
* flaper87 wrote some stuff lastnight15:36
*** jeffrey4l has quit IRC15:37
flaper87vkmc: replied to your question there15:37
flaper87LOL15:37
flaper87it still wins15:37
flaper87vkmc: awesome, I'm glad when there's an obvious winner15:37
flaper87vkmc: if you put all this in the spec, I'm here to review it as soon as it's up15:38
flaper87hopefully we can merge it this week15:38
vkmcI already done that15:38
flaper87vkmc: damn, you're fast15:38
vkmchaha15:38
vkmccheck it out, maybe I have to add more details on why we choose msgpack15:38
vkmcI really liked capnproto15:39
vkmcbut it doesn't have support for Javascript15:39
vkmcthe performance for msgpack is not something mindblowing, but at least is more flexible than JSON15:40
openstackgerritFlavio Percoco proposed openstack/zaqar-specs: Spec for notification service  https://review.openstack.org/12919215:40
*** mpanetta has joined #openstack-zaqar15:41
flaper87oh, too bad capnproto doesn't have support for javascript15:41
flaper87I'm sure that's kgriffs fault15:41
vkmcwell.. in fact15:41
vkmcit only has support for C++15:41
kgriffsprobably15:41
kgriffsvkmc: no, it has support for other languages15:41
kgriffslet me find the link15:41
vkmcit does, but its not part of the official project kgriffs15:42
kgriffshttp://kentonv.github.io/capnproto/otherlang.html15:42
kgriffslooks like javascript support is node.js only though15:42
kgriffs(booh)15:42
vkmcthose are being mantained by other users and not being reviewed by the capnproto guy15:42
flaper87vkmc: and rust ;)15:43
vkmcI'm afraid one of those guys will get up one morning and think 'ok, I don't want to keep mantaining this project' and then we have to look for an alternative15:43
kgriffsdepends on how popular this protocol becomes15:44
vkmcyeah15:44
flaper87ok, I guess we can revisit it later15:44
vkmcflaper87, that's a big +1 for capnproto from your side probably :) haha15:44
flaper87kgriffs: I replied to your comment in the FIFO spec, not sure I follow your comment there15:44
flaper87:/15:44
kgriffsi really want rust to succeed15:44
vkmcflaper87, did you see this? http://bjorn.tipling.com/if-programming-languages-were-weapons15:45
vkmcyou won't like it15:45
vkmclol15:45
kragnizkgriffs: same15:45
kragnizit's lovely15:45
kgriffsfwiw, I was talking to the author of python cryptography (the library)(15:46
kgriffshe really wants rust to succeed too15:46
kgriffshe feels like it would make his life easier in the crypto world - I guess the language has some nice features he could use to prevent timing attacks and stuff15:47
kgriffsanyway, I guess we could always contribute to the project instead of just wishing. :p15:47
flaper87ah yeah, I had seen that15:47
vkmcrust as a 3d printed gun is not very accurate15:48
flaper87it'll definitely make his life easier. A language that prevents overflow errors is already a whin15:48
flaper87win*15:48
flaper87if to that we add memory safety, bound checking etc15:48
flaper87anyway15:48
flaper87vkmc: "Implement pools, flavors and stats controllers"15:48
flaper87Do we really need to be support in the websocket protocol>15:49
flaper87?15:49
flaper87I guess we do for consistency, right?15:49
vkmcflaper87, we will try... to keep the 1-1 mapping with the operations already being provided15:49
kgriffsyou can do it iteratively15:49
kgriffsfirst the data plane15:49
kgriffsthen control plane15:49
vkmcyeah15:50
kgriffsflaper87: re your question about FIFO guarantee and it's relationship to guaranteed delivery15:50
kgriffsI think when we talk about this with people we need to be clear that those two things go hand-in-hand15:51
kgriffsbasically, to guarantee delivery we say things have to be ordered FIFO so that when using the pub-sub messaging pattern (listing messages), subscribers do not miss any messages. This is specific to the REST/WSGI driver15:52
kgriffsso, if you say that FIFO is not guaranteed, you are also saying that message delivery is not guaranteed, which I don't want to come as a surprise to anyone15:53
kgriffsdoes that makes sense?15:53
flaper87vkmc: kgriffs agreed, lets add support for that too. I think it'll all happen "for free" to be honest. Once the jsonschema for the whole API is defined, there's not much to do other than making sure the right exceptions are being raised15:54
flaper87kgriffs: ah ok, now I know what you meant.15:55
kgriffskk, I've got to run to a meeting15:56
kgriffso/15:56
flaper87I'll update the spec15:56
flaper87thanks15:56
kgriffssure thing15:56
kgriffsbtw, this is interesting15:58
kgriffshttp://highscalability.com/blog/2014/11/17/aeron-do-we-really-need-another-messaging-system.html15:58
kgriffsttfn15:58
*** kgriffs is now known as kgriffs|afk15:58
*** exploreshaifali has joined #openstack-zaqar16:05
vkmcgood readin16:13
vkmcg16:13
*** sgotliv has quit IRC16:39
openstackgerritFlavio Percoco proposed openstack/zaqar: Correctly stop functional servers  https://review.openstack.org/13423617:05
*** dynarro_ has quit IRC17:16
*** dynarro has quit IRC17:16
*** cpallares is now known as cpallares_afk17:30
*** dynarro has joined #openstack-zaqar17:37
*** dynarro_ has joined #openstack-zaqar17:37
*** dynarro has quit IRC17:37
*** cpallares has joined #openstack-zaqar17:38
*** cpallares has quit IRC17:38
*** dynarro_ has quit IRC17:42
*** cpallares has joined #openstack-zaqar17:52
*** sgotliv has joined #openstack-zaqar18:01
*** vipul has quit IRC18:04
*** vipul has joined #openstack-zaqar18:05
*** sgotliv has quit IRC18:07
*** achanda has joined #openstack-zaqar18:09
*** jchai is now known as jchai_afk18:38
*** achanda has quit IRC18:41
*** achanda has joined #openstack-zaqar18:44
*** cpallares_afk has quit IRC18:48
*** achanda has quit IRC19:34
*** flwang1 has quit IRC19:35
*** reed has quit IRC19:42
*** achanda has joined #openstack-zaqar19:43
openstackgerritMerged openstack/zaqar: Correctly stop functional servers  https://review.openstack.org/13423619:44
openstackgerritOpenStack Proposal Bot proposed openstack/zaqar: Updated from global requirements  https://review.openstack.org/13480319:46
openstackgerritShaifali Agrawal proposed openstack/zaqar: Split Control and Data planes of Storage layer  https://review.openstack.org/13491019:51
*** sgotliv has joined #openstack-zaqar19:54
*** ametts has quit IRC19:57
*** achanda has quit IRC20:04
*** yograterol has joined #openstack-zaqar20:27
*** exploreshaifali has quit IRC20:46
*** jchai_afk is now known as jchai21:00
*** achanda has joined #openstack-zaqar21:05
*** achanda_ has joined #openstack-zaqar21:09
*** achanda has quit IRC21:09
*** sriram has quit IRC21:38
*** flwang1 has joined #openstack-zaqar21:39
*** cpallares1 has joined #openstack-zaqar21:45
*** cpallares1 has left #openstack-zaqar21:45
*** davideagnello has quit IRC21:59
*** davideagnello has joined #openstack-zaqar22:01
*** davideagnello has quit IRC22:10
*** davideagnello has joined #openstack-zaqar22:11
*** sgotliv has quit IRC22:14
*** jchai has quit IRC22:49
openstackgerritFlavio Percoco proposed openstack/zaqar: Used a pooled config for health  https://review.openstack.org/13423722:49
*** davideagnello has quit IRC22:55
*** davideagnello has joined #openstack-zaqar22:57
*** amitgandhinz has quit IRC22:58
*** davideagnello has quit IRC23:08
*** davideagnello has joined #openstack-zaqar23:22
*** yograterol has quit IRC23:28
*** cpallares has quit IRC23:33
*** mpanetta has quit IRC23:34
openstackgerritMerged openstack/zaqar: Used a pooled config for health  https://review.openstack.org/13423723:50
*** boris-42 has quit IRC23:57
« Monday, 2014-11-17 Index Wednesday, 2014-11-19 »

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