Monday, 2014-11-17

*** vanham has joined #openstack-zaqar01:08
vanhamHey yall. Good night.01:08
vanhamI'm trying to setup zaqar here as per https://github.com/openstack/zaqar/blob/master/README.rst01:08
vanhamBut when I try to run zaqar-server -v it gives me the following http://paste.openstack.org/show/133991/01:09
vanham(something like object has no attribute 'PKI_ASN1_FORM)01:09
*** X019 has joined #openstack-zaqar01:19
*** vanham has quit IRC01:30
*** achanda has quit IRC01:39
*** achanda has joined #openstack-zaqar01:43
*** davideagnello has joined #openstack-zaqar02:12
*** achanda has quit IRC02:13
*** jeffrey4l has joined #openstack-zaqar02:28
*** X019 has quit IRC02:32
*** X019 has joined #openstack-zaqar02:44
*** bradjones has quit IRC02:44
*** fifieldt has quit IRC02:45
openstackgerritJeffrey Zhang proposed openstack/zaqar: Remove the outdated openstack common modules  https://review.openstack.org/13388602:45
*** bradjones has joined #openstack-zaqar02:46
openstackgerritJeffrey Zhang proposed openstack/zaqar: pooling conf is using a wrong deprecated conf  https://review.openstack.org/13293702:47
*** boris-42 has quit IRC03:07
*** achanda has joined #openstack-zaqar03:14
*** achanda has quit IRC03:19
*** jeffrey4l has quit IRC03:51
*** jeffrey4l has joined #openstack-zaqar04:03
*** achanda has joined #openstack-zaqar04:53
*** davideagnello has quit IRC05:16
*** davideagnello has joined #openstack-zaqar05:16
*** duanhf has joined #openstack-zaqar05:26
*** sgotliv has joined #openstack-zaqar05:26
*** sgotliv has quit IRC06:20
*** davideagnello has quit IRC06:30
*** jeffrey4l has quit IRC06:46
*** exploreshaifali has joined #openstack-zaqar06:47
exploreshaifaliflaper87: around?06:57
*** achanda has quit IRC07:02
*** jeffrey4l has joined #openstack-zaqar07:06
*** miqui_ has quit IRC07:22
*** jeffrey4l has quit IRC07:37
*** exploreshaifali has quit IRC07:39
*** exploreshaifali has joined #openstack-zaqar07:41
*** jeffrey4l has joined #openstack-zaqar07:43
*** exploreshaifali has quit IRC08:02
*** exploreshaifali has joined #openstack-zaqar08:05
*** dynarro has joined #openstack-zaqar08:08
*** fifieldt has joined #openstack-zaqar08:09
*** exploreshaifali has quit IRC08:16
*** davideagnello has joined #openstack-zaqar08:18
*** davideagnello has quit IRC08:23
*** duanhf has quit IRC08:23
*** reed has joined #openstack-zaqar09:13
*** sgotliv has joined #openstack-zaqar09:20
*** flaper87 has quit IRC09:43
*** flaper87 has joined #openstack-zaqar09:43
*** jeffrey4l has quit IRC09:50
*** doraly_ has joined #openstack-zaqar09:51
*** sgotliv has quit IRC09:57
*** jeffrey4l has joined #openstack-zaqar10:04
*** achanda has joined #openstack-zaqar10:06
*** achanda has quit IRC10:10
*** boris-42 has joined #openstack-zaqar10:33
*** dynarro has quit IRC10:38
*** doraly_ has quit IRC10:38
*** exploreshaifali has joined #openstack-zaqar10:52
exploreshaifaliflaper87, around?11:01
flaper87exploreshaifali: hey hey11:01
flaper87yeah, not for long, almost lunch time11:02
flaper87but I'll be back later11:02
exploreshaifaliflaper87, all right11:02
flaper87exploreshaifali: what's up? how are you doing? Hope you had a great weekend11:02
exploreshaifalihave a happy lunch11:02
exploreshaifaliflaper87, yes!11:02
exploreshaifalicheckout https://etherpad.openstack.org/p/exploreshaifali-opw-split-layers11:03
exploreshaifalifrom line 1611:03
* flaper87 clicks11:03
flaper87exploreshaifali: 'sup ?11:05
flaper87exploreshaifali: btw, feel free to submit a patch for that code, we can discuss over reviews too11:05
flaper87it's probably easier to write comments there11:05
flaper87exploreshaifali: you can mark the patch as work-in-progress11:05
flaper87ok brb11:05
exploreshaifaliflaper87, okay... what is 'sup?11:06
*** flwang1 has joined #openstack-zaqar11:14
flwang1flaper87: morning11:15
openstackgerritMerged openstack/zaqar: Let the test client serialize request's body  https://review.openstack.org/13421011:31
openstackgerritShaifali Agrawal proposed openstack/zaqar: Split Control and Data planes of Storage layer  https://review.openstack.org/13491011:37
*** vkmc has joined #openstack-zaqar11:38
vkmcmorniiiiiiiiing11:40
flwang1vkmc: morning11:43
vkmchey :)11:43
*** openstackgerrit has quit IRC11:48
*** openstackgerrit has joined #openstack-zaqar11:49
exploreshaifalimorning vkmc  :)11:50
vkmchi exploreshaifali!11:53
vkmcsaw you started working on your bp11:53
vkmckudos!11:53
exploreshaifali\o/11:53
exploreshaifaliflaper87, vkmc wrote first post http://shaifaliagrawal.wordpress.com/2014/11/16/switch-on-to-openstack/11:54
vkmcthat's so great!11:55
* vkmc follows exploreshaifali's blog11:56
exploreshaifali:)11:56
flaper87flwang1: morning11:56
flaper87vkmc: morning11:56
* flaper87 is back11:57
flaper87exploreshaifali: awesome!11:57
exploreshaifaliflaper87, :D11:57
vkmcflaper87, 'sup dud :)11:57
flaper87exploreshaifali: awesome post11:59
flaper87vkmc: helllllllllllllllooooooooooooooooooooooooo11:59
flaper87vkmc: all good, you?11:59
flaper87hope you had a great w/e11:59
vkmcflaper87, good too! yeah it was great :) I went to the beach hehe12:00
flwang1flaper87: just post a comment for the remove queue spec12:00
vkmcflaper87, yours?12:00
flaper87exploreshaifali: is your blog in openstack's planet?12:00
flwang1flaper87: now working on a poc of notification12:00
flaper87flwang1: thanks for reviewing the specs12:00
flaper87we'll discuss them in today's meeting12:01
flaper87I'll probably send an email to the mailing list about that one12:01
exploreshaifaliflaper87, Thanks!,  I added my blog in OPW planet but not in openstack planet12:01
flaper87exploreshaifali: if not, here's how you can add it https://wiki.openstack.org/wiki/AddingYourBlog12:01
flwang1flaper87: it would be nice12:01
exploreshaifaliok :)12:01
flwang1flaper87: as for the notification's subscription body, I'm still keen to know your thoughts12:02
flaper87did you read my last comments?12:03
flaper87oh, you also replied12:03
*** dynarro has joined #openstack-zaqar12:03
*** doraly_ has joined #openstack-zaqar12:03
*** doraly_ has quit IRC12:05
*** dynarro has quit IRC12:05
*** dynarro has joined #openstack-zaqar12:05
*** dynarro_ has joined #openstack-zaqar12:06
flwang1flaper87: yep12:07
flaper87flwang1: replied, I'll update the spec12:07
flwang1flaper87: cool12:07
flwang1flaper87: thank you12:07
flaper87flwang1: fWIW, the s/queue/topics/ change is parallel and completely optional12:07
flaper87we don't have to do it, I do see value in it12:07
flaper87if you read my last comments, I proposed keeping the URL and just changing the way it works under the hood12:07
flaper87that'd allow people to use it in the URL *and* the message body.12:08
flwang1flaper87: yep, i noticed that12:08
flaper87taking small steps, basically12:08
*** sgotliv has joined #openstack-zaqar12:09
vkmcflaper87, this should be targeted to k-2 https://review.openstack.org/#/c/134015/2/specs/kilo/migrate-to-topics.rst12:09
flaper87vkmc: probably, that's something I'd like to discuss in today's meeting12:10
flwang1vkmc: I think so12:10
flaper87vkmc: pls, add a comment there12:11
vkmcflaper87, will do12:11
flaper87the thing is, it's quite a change, leaving it for k-2 means we might introduce some aweful regresions late in the game12:11
flaper87but generally, yeah, I agree with you both12:11
vkmcwe should focus on end persistent transport, notifications and fifo for k-112:11
flaper87k-2 sounds better for a change that is actually optional12:11
flaper87vkmc: totally agree12:11
vkmcbut yeah, lets discuss about this later today :)12:12
vkmcI'll leave some comments in the specs, which btw, are great... thanks for working on those flaper8712:12
flwang1flaper87: I think I will miss the meeting12:17
flaper87flwang1: :(12:17
flwang1it's UTC 3:00 right?12:17
flaper87flwang1: anything you want to say now?12:18
flaper87flwang1: yeah12:18
flaper87flwang1: pls, drop your comments on those reviews before the meeting12:18
flwang1http://www.worldtimebuddy.com/?pl=1&lid=100,2179537&h=10012:20
flaper87flwang1: also, it'd be great if you could review these patches before you go to sleep https://review.openstack.org/#/q/status:open+project:openstack/zaqar+branch:master+topic:bug/1383604,n,z12:20
flaper87flwang1: yeah, I know it's late for you12:20
flaper87flwang1: next week's is 21 UTC, FWIW12:20
flaper87vkmc: is your spec ready for review?12:21
flwang1flaper87: sure, I will review them before sleep :)12:21
flaper87http://www.theregister.co.uk/2013/11/14/amazon_kinesis_launch/12:22
vkmcflaper87, sure... I have to polish the work items, but maybe you can give me some pointers there12:22
flaper87http://azure.microsoft.com/en-gb/services/event-hubs/12:22
flaper87vkmc: awesome, will do12:22
flwang1flaper87: vkmc: i'm going to sleep, have a nice day, guys12:31
flaper87flwang1: g'night!12:33
flaper87flwang1: thanks12:33
*** flwang1 has quit IRC12:33
vkmcflwang1, nite :)12:33
vkmcflaper87, lemme know when you have a moment to discuss about the notifications spec12:34
vkmcor if you prefer doing that during the meeting12:34
flaper87vkmc: we can do it now, I'm in review specs mode before the meeting12:35
vkmcflaper87, cool... well, I'm not sure about subscriptions handling12:37
vkmcfirst, a suscription has to be created12:37
vkmcand then you access them from /v2/subscriptions/{s}/listen12:37
vkmcwouldn't make more sense to have subscriptions as a topic/queue attribute?12:38
vkmckickban me if I'm saying nonsense12:38
flaper87that's just if you subscribe using a persistent transport (the listen step, I mean)12:38
flaper87vkmc: it's not nonsense, you know there are no dumb questions but dumb answers ;)12:39
vkmckewl12:39
vkmcwell, for the case of non persistent transports12:39
flaper87vkmc: I still have to update the spec but the topic will be part of the subscription body12:39
vkmcthe accesing is slightly different, but the same12:39
flaper87topic/queue12:39
vkmc /v2/subscribe12:39
flaper87lets just talk about queues until the change happens - assuming it will.12:39
vkmcit will12:39
flaper87Here's what I had in mind, lemme know what you think12:40
vkmck12:40
*** dynarro has quit IRC12:40
*** dynarro_ has quit IRC12:40
flaper87I want to subscribe my mobile APN to messages going into queue A12:40
flaper87I send a POST request to /v2/subscriptions/ with a body that contains:12:40
flaper87{"queue": ..., "listener": ..., "hooks?": ...}12:41
flaper87Every time a messages goes into queue A the notifications trigger will be called and it'll notify all the listeners12:41
flaper87Does that make sense?12:42
vkmcyeah12:42
vkmcI was expecting suscriptions to be inside the queues endpoint though12:43
vkmca client subscribes to a queue12:43
vkmcyou don't need the client to send a 'I want to subscribe to queueu A' message to the server12:43
flaper87mmh, that's a good point, btw.12:44
flaper87mmh, what if I want to subscribe listener L to multiple queues ?12:44
vkmcwell yeah, in that case perhaps your approach is better12:45
flaper87Mind adding a comment for that ?12:45
vkmcsure12:45
flaper87I'll comment back and hopefully kgriffs|afk will take a look as well12:45
vkmcin the case a listener L want to subscripbe to queue A, B and C, then L will have to POST messages for all the queues12:45
vkmcmaking it less performant probably12:46
vkmcbut, but,... we have to check if leaving subscriptions control to each of the queues makes things easier to handle12:47
*** sgotliv has quit IRC12:47
vkmcin your approach, we should keep a data structure with all the subscriptions and make sure it is updated12:48
vkmcah well >.>12:48
flaper87yeah, I kinda prefer your proposal because we could re-use the metadata model12:49
*** cpallares has joined #openstack-zaqar12:49
flaper87"model12:50
flaper87"12:50
*** dynarro_ has joined #openstack-zaqar12:50
*** dynarro has joined #openstack-zaqar12:50
vkmcflaper87, I'll leave a comment in the spec so we can discuss it with someone else12:50
vkmcnow... lets hide from cpallares12:50
flaper87but mmh, I wonder if that's clear enough API-wise12:50
* vkmc hides12:50
* flaper87 hides12:50
vkmcwhat do you mean... clear enough API-wise?12:50
* cpallares looks around and doesn't see anyone12:51
flaper87/v2/queue_name/subscriptions/12:51
flaper87/v2/notifications/subscriptions/12:51
* vkmc thinks 'success!' 12:51
vkmcflaper87, that is subjective12:52
flaper87sorry, I got distracted12:52
vkmcfor me the first one is clearer because I was expecting it to be like that12:52
flaper87what I wanted to say is: The think I liked about the later is that it keeps both things separate12:52
vkmcyeah12:52
flaper87but again, I think I prefer your proposal12:52
vkmcbut... should those be separated?12:53
vkmclets check some other messaging solutions12:53
flaper87and it fits perfectly with the "lets mix these 2 things together" kind of idea we had12:53
vkmcyeah12:53
flaper87in AMQP, you just listen on a queue what changes is what messages are sent to that queue12:54
flaper87based on the routing key, etc12:54
vkmcI'm afraid that if we remove the queue concept as a container that would stop making sense12:54
vkmchow would the endpoint look when we remove queues?12:54
*** exploreshaifali has quit IRC12:55
flaper87vkmc: exactly12:56
flaper87I think I was thinking in a queue-less scenario when I wrote that spec12:57
vkmcit makes sense12:57
* flaper87 thinks: It's funny that queue-less kinda sounds like clueless12:57
vkmcno moar queuein' up!12:58
vkmcAMQP 1.0 http://qpid.apache.org/releases/qpid-proton-0.8/protocol-engine/python/api/proton.Messenger-class.html#subscribe12:59
flaper87LOL13:00
vkmc:x13:00
vkmc./v2/subscribe13:00
vkmcwe don't have to forget that AMQP 1.0 != Zaqar though13:01
*** sgotliv has joined #openstack-zaqar13:01
vkmcwe should make things the best we can do for our use cases and stuff13:01
openstackgerritFlavio Percoco proposed openstack/zaqar: Claim post requires a body  https://review.openstack.org/13421413:02
flaper87vkmc: exactly13:03
flaper87although, we should consider amqp 1.0 is basically topic based13:03
flaper87vkmc: https://review.openstack.org/#/c/134214/ <- just updated commit message13:03
vkmcyeah of course13:04
vkmcso13:04
vkmchow would Zaqar look like when we get rid of queues?13:04
vkmcIMO notifications would be tightly coupled to that scenario13:04
vkmcs/queue/topic13:05
flaper87vkmc: that's still an open question13:08
flaper87vkmc: as in, 2s...13:08
vkmchttp://docs.aws.amazon.com/sns/latest/api/API_Subscribe.html subscriptions in SNS13:09
flaper87vkmc: https://review.openstack.org/#/c/129192/2/specs/kilo/notification-api.rst,cm <- flwang comments here13:09
vkmcyeap, saw those13:09
flaper87vkmc: but AWS has 2 separate services13:09
vkmcyeah13:09
flaper87not sure how good it'd be to follow it semantic wise13:09
flaper87vkmc: back to notifications13:09
vkmcright now we are more comparable to SNS than SQS13:09
flaper87actually no, I mixed thse13:09
flaper87anyway13:10
flaper87what I wanted to say is that we may want to keep supporting queues in the URL and just change the logic under-the-hood13:10
vkmcoic13:10
flaper87We could allow both, queue's in the URL and in the message body13:10
flaper87and encourage people to move away from URL queue's calls13:10
flaper87but I think that'll create lots of confussion13:11
vkmcI'm afraid so13:11
flaper87IMHO, we should either go all in or abstain from doing it13:11
vkmcexactly13:12
vkmcsomething to have in mind is that... we are no longer the 'queueing' system13:12
vkmcif we keep the concept of 'queue' in our API, that would bring some misconceptions13:12
flaper87right13:14
vkmc'ya know13:14
vkmcwe should be careful about that13:15
*** dynarro_ has quit IRC13:19
*** dynarro_ has joined #openstack-zaqar13:19
*** doraly__ has joined #openstack-zaqar13:20
*** dynarro has quit IRC13:20
cpallaresIt's colder here than it was in London. It's -3 :'(13:33
vkmcthat's low :o13:34
vkmcwe are expecting 32 C for today, wanna come? :)13:34
* cpallares is freezing13:34
cpallaresvkmc: I'm on the next plane to Bahia Blanca.13:35
vkmchahaha13:35
*** jeffrey4l has quit IRC13:41
*** jeffrey4l has joined #openstack-zaqar13:41
flaper87I've been thinking about that13:43
flaper87I mean, I love winter13:44
flaper87I probably loe winter more than summer13:44
flaper87but summer is nicer for "outside" activities13:44
flaper87which are a "must have" for remotees13:44
cpallaresflaper87: You've been thinking about going to Bahia blanca?13:44
cpallaresflaper87: Or about -3 weather?13:44
flaper87cpallares: no, that was a half-written idea :P13:44
flaper87I've been thinking about going to southern countries during northern winter13:45
*** davideagnello has joined #openstack-zaqar13:45
vkmcchasing the sun13:45
flaper87or I should probably just move back to Venezuela and forget about seasons13:45
flaper87erm, fuck no, I'd rather travel every 6 months13:45
vkmcnah13:45
flaper87not that I don't travel already13:45
vkmcyou don't want to do that13:45
vkmclol13:45
flaper87s/travel/move/13:46
flaper87I could also go to Israel13:46
vkmcI want to move to New Zealand as flwang13:46
cpallaresflaper87: Southern California. Sunny all day everyday.13:46
vkmcand live in a hobbit house13:46
* cpallares wants to live a hobbit house13:47
cpallaresvkmc: http://hobbithouses.tumblr.com/13:47
flaper87vkmc: you know you can have a hobbit house there and have penguins coming for tea every day, right?13:47
vkmc<313:47
flaper87cpallares: but, but, but, it's Cali... :/13:47
flaper87Well, I could totally live in Santa Barbara13:48
cpallaresLOL13:48
*** kragniz has joined #openstack-zaqar13:48
cpallaresflaper87: Weren't you complaining about Santa Barbara?13:48
flaper87cpallares: no no, SFO13:48
cpallaresOr was it Santa Clara?13:48
flaper87and Santa Clara13:48
flaper87I would never live in SFO and I'm sick of conference organized in Santa Clara13:48
flaper87there's NOTHING to do there13:48
vkmcflaper87, building a hobbit house in Argentina would be like going out in your front yard and yelling 'hey, I want to get mugged'13:49
flaper87I mean, do people even live there? There's just 1 Hyatt, 1 Hilton and VTA13:49
flaper87at least the VTA has free wifi13:49
flaper87.....13:49
*** davideagnello has quit IRC13:49
cpallaresvkmc: haha13:50
flaper87vkmc: LOOOOOOOOOL13:50
kragnizthis seems to be where the cool kids live13:50
vkmccpallares, similar to getting of the plane in Ezeiza with a Red Hat13:51
flaper87kragniz: this is the coolest channel EVER13:51
flaper87stay and see for yourself13:51
cpallaresvkmc: how is your red hat? did it survive?13:51
cpallaresvkmc: Needless to say your cookies did not survive.13:51
kragnizflaper87: may I come and live here if I have nothing to do with messaging? :D13:51
cpallaresvkmc: But mostly because I ate them.13:52
flaper87kragniz: absolutely13:52
kragnizflaper87: cool beans!13:52
flaper87you'll definitely end up having something to do with messaging13:52
vkmccpallares, it did! I lost the pin though :(13:52
flaper87;)13:52
flaper87we're good at giving others things to do13:52
kragnizflaper87: D:13:52
cpallaresvkmc: ah but that's the coolest part13:52
vkmccpallares, haha hope you enjoyed those13:52
flaper87kragniz: does swift re-write ring any bell ?13:52
kragnizvkmc: I want a hobbit hole13:52
kragnizflaper87: D:13:52
vkmckragniz, feel free to lurk here... its something we frequently do here13:53
vkmc:D13:53
vkmckragniz, +1 for the hobbit hole! haha13:53
flaper87I like hobbit holes but as bad as it sounds, when I see them I kind of remember teletubbies' house http://www.talbotfarmlandscapes.co.uk/wp-content/files_mf/telebubbies_682_1002431a.jpg13:54
kragnizvkmc: they look so cosy13:54
cpallaresflaper87: LOL13:54
kragnizflaper87: heh13:54
vkmcflaper87, you didn't compare LOTR with Teletubbies13:54
vkmc>.>13:54
flaper87vkmc: no no, I compared Bilbo's house to Teletubbies'13:55
flaper87Obviously, the later must have been fans of LOTR13:55
kragnizflaper87: and by extension the rest of the shire!13:55
*** kgriffs|afk is now known as kgriffs13:55
flaper87I'm just making a point here. The idea is so cool that teletubbies adopted it13:56
vkmcoh no, kgriffs is back13:56
flaper87Thing is, they added  speaking vacuum cleaners to it13:56
flaper87and other disgusting things13:56
cpallaresflaper87: And their tummies are TVs, no?13:57
vkmcflaper87, seems you are a real Teletubbies fan13:57
kragnizwe know flaper87's true passions now13:57
cpallaresvkmc: He's secretly a fan13:57
* kgriffs lurks13:57
vkmckragniz, +2 we do!13:57
cpallaresvkmc: He's had time to think about their Tolkien archiitecture influence.13:57
flaper87LOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOL13:57
* flaper87 has a younger siblins as cpallares does13:57
vkmccpallares, yeah... he have done research on that13:58
flaper87>.>13:58
vkmcyeah... sure... younger siblings13:58
cpallaresvkmc: He's had time to formulate theories13:58
vkmccpallares, he probably has a notebook with diagrams and stuff13:58
kragnizflaper87: how do you see the parallels between the sun and the eye of sauron?13:58
flaper87I just wish sauron would've targetted them instead of the Hobbits13:58
flaper87kragniz: dude, have you seen the face of that sun? It's scarier thatn Sauron's eye13:59
flaper87iiuuugh13:59
flaper87than*13:59
flaper87vkmc: cpallares LOOOL, I do13:59
* flaper87 looks around13:59
flaper87kgriffs: welcome back to the best channel ever14:00
flaper87kgriffs: meeting in 1h14:00
cpallaresflaper87: Have you had time to formulate why they're all different heights? Is there a symbolism between hobbits, dwarfs, elves, and wizards? :P14:00
cpallareskgriffs: What's your stance on the teletubbies and their appropriation of hobbit houses?14:00
kgriffslol14:00
kgriffsteletubbies always gave me the creeps14:00
vkmcits a really creepy... tv show?14:01
kgriffsI prefer to not think of them corrupting the Tolkien world14:01
kgriffs:p14:01
kgriffsI lump teletubbies in with barney and other children's shows that should be banned from the planet for the good of all mankind.14:03
flaper87cpallares: re #2, the just liked it and they didn't think about the fact that they are way taller. This is the reason their house is bigger than the Hobbit's version14:03
*** sriram has joined #openstack-zaqar14:03
flaper87kgriffs: +214:03
flaper87:P14:03
cpallaresvkmc: Looking at a youtube video of it I'd say it's more like wtf than creepy https://www.youtube.com/watch?v=TmQ--bESNXA14:04
kragnizsomeone is doing research14:05
kragnizhelp us14:05
vkmcdon't make me click on that14:05
vkmclol14:05
flaper87cpallares: you are not really expecting me to believe that you hadn't seen the show ever14:05
flaper87I won't ever believe that14:05
kragnizto be fair, I've only seen clips of it14:05
cpallaresflaper87: haha unlike you I actually had young siblings who occasionally watched the show.14:06
flaper87cpallares: I dooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo have younger siblings14:06
flaper87kragniz: LUCKY YOU!14:07
flaper87kragniz: but I won't forget that and be prepared for the next summit.14:07
kragnizflaper87: the bits I saw scarred me for life, though14:07
flaper87kragniz: tequila + teletubbies14:07
cpallaresflaper87: OH GOD NO14:07
vkmcthat is a bad idea14:07
vkmchorrible idea14:07
cpallaresvkmc: ALWAYS14:07
kragnizflaper87: that doesn't sound good D:14:07
flaper87cpallares: vkmc don't worry, we'll just watch him suffering14:08
cpallareslol14:08
flaper87which makes it a good idea for us14:08
vkmcflaper87, we could do something like the Clockwork Orange14:08
* kragniz has regrets for joining this channel14:08
vkmcnah that is too mean14:09
flaper87kragniz: come one, you'll forget those regrets when we'll start messing with kgriffs14:09
flaper87vkmc: LOOOL14:09
flaper87s/one/on/14:09
kragnizflaper87: heh14:10
cpallaresIt's always kgriffs fault.14:10
flaper87kragniz: ^ THIS14:10
cpallaresThe tequila idea that night was kgriffs fault.14:10
* kragniz shakes his fist at kgriffs 14:10
cpallareskgriffs is just a bad influence on all of us.14:10
vkmcClockwork Orange's eye scene http://media.tumblr.com/tumblr_m3cvklT7Yz1qhfkar.jpg (not suitable for sensitive people)14:11
* kgriffs can't help it14:11
vkmcah well14:11
* vkmc goes back reviewing14:11
* kragniz goes back to figuring out sqlalchemy-migrate wizardry14:13
cpallares /me goes back to playing in the snow14:14
kragnizcpallares: jelly :(14:15
*** mpanetta has joined #openstack-zaqar14:25
*** jchai has joined #openstack-zaqar14:25
*** ametts has joined #openstack-zaqar14:28
*** cpallares has quit IRC14:33
*** cpallares has joined #openstack-zaqar14:34
vkmcflaper87, https://review.openstack.org/#/c/132348/1 +2 +A?14:40
*** malini has joined #openstack-zaqar14:44
*** cpallares has quit IRC14:46
*** cpallares has joined #openstack-zaqar14:47
flaper87vkmc: yeah14:50
vkmck14:53
vkmcmeeting in 4'!14:56
vkmcflaper87, I just noticed that cannot +2 +A, I'm not core in zaqar-specs14:58
flaper87vkmc: oh, mmh14:59
flaper87why is there a separate group for that?14:59
vkmcdunno14:59
flaper87it's kgriffs fault for sure14:59
vkmcyou tell me14:59
vkmchaha14:59
vkmcprobably yes14:59
flaper87meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeting14:59
vkmcMEETING! >.<15:00
flaper87dynarro_: cpallares vkmc kgriffs kragniz flwang zhiyan EVERYONE! ^^^^^^^^^^^^^^15:00
flaper87join #openstack-meeting-315:00
cpallareshey you got the channel right :P15:00
cpallaresflaper87: But it's actually #openstack-meeting-alt-3-alt-215:00
flaper87cpallares: LOL, I think you spent way too much time in Paris15:00
flaper87;)15:00
flaper87:D15:01
flaper87cpallares: LOOOL15:01
vkmcjeffrey4l, #openstack-meeting-315:03
vkmcwpf, #openstack-meeting-315:03
jeffrey4li am in15:03
vkmc:) cool15:06
*** exploreshaifali has joined #openstack-zaqar15:16
kragniztotes joining this15:18
vkmcexploreshaifali, join us on the team meeting :) #openstack-meeting-315:19
*** amitgandhinz has joined #openstack-zaqar15:20
zhiyanvkmc: https://review.openstack.org/#/c/103825/ - the spec for osprofiler idea15:23
vkmchey zhiyan! :)15:23
vkmcthanks for that15:23
zhiyanvkmc: hey!, sorry for the delay sending for the link15:24
vkmcnot a problem15:24
zhiyanvkmc: last week i'm a little busy to handle my filmily issue.15:25
zhiyanvkmc: ^^ any ideas pls let me know. and guide me in zaqar pls !15:25
zhiyanthanks!15:25
vkmczhiyan, I'll check it after the team meeting (if you want to join, its happening in #openstack-meeting-3)15:25
vkmczhiyan, and of course, it would be great to give you a hand with Zaqar :)15:26
zhiyanvkmc: BIG thanks!15:26
vkmc:) my pleasure15:28
zhiyan:))15:29
*** achanda has joined #openstack-zaqar15:49
* vkmc picks the minutes15:59
kragnizflaper87: what did I get volunteered for this time D:16:00
kgriffsvkmc: thanks!16:01
vkmcbtw, I setted up the etherpad16:02
vkmcfor the serialization protocols selection https://etherpad.openstack.org/p/zaqar-serialization-protocol-ws16:02
vkmcthere is nothing relevant yet16:02
*** davideagnello has joined #openstack-zaqar16:07
*** achanda has quit IRC16:09
*** reed has quit IRC16:13
*** reed has joined #openstack-zaqar16:13
*** davideagnello has quit IRC16:28
* flaper87 needs to write some code, really16:31
kragnizflaper87: you're a manager now16:32
kragnizflaper87: welcome to the ruling class16:32
flaper87kragniz: omg, of all the insults you could've used, you had to use that one16:33
kragnizflaper87: I went there16:33
flaper87damn, that one was a very low kick16:33
* kragniz makes flaper87's fingers type code16:34
vkmclunch time >:)16:50
kragnizvkmc: the evil face makes it sound like your lunch is nefarious in some way16:51
openstackgerritFlavio Percoco proposed openstack/zaqar: Update oslo-config-generation code  https://review.openstack.org/13501217:00
*** reed has quit IRC17:02
openstackgerritShaifali Agrawal proposed openstack/zaqar: Split Control and Data planes of Storage layer  https://review.openstack.org/13491017:04
flaper87yay, I submitted a patch17:10
flaper87>.>17:10
*** reed has joined #openstack-zaqar17:15
*** sgotliv has quit IRC17:19
*** dynarro_ has quit IRC17:28
*** doraly__ has quit IRC17:28
exploreshaifaliflaper87, I too submitted a patch ;)17:32
kragnizpatches everywhere! \o/17:33
exploreshaifali\o/17:33
*** davideagnello has joined #openstack-zaqar17:56
exploreshaifaliif possible pleaset review https://review.openstack.org/#/c/134910/ so that I can start for step 218:06
exploreshaifaliflaper87, ^18:06
vkmcexploreshaifali, you explained the different steps in an etherpad?18:14
vkmcmake sure to make commit messages more general because those are going to be read by people that are not familiar with your internship18:14
exploreshaifalivkmc, I will keep that in mind regarding commit messages :)18:15
vkmcsure :)18:15
*** amitgandhinz has quit IRC18:15
exploreshaifalivkmc, in ether pad same steps were explained18:15
vkmcgreat18:15
exploreshaifalivkmc, https://etherpad.openstack.org/p/exploreshaifali-opw-split-layers18:16
vkmcexploreshaifali, cool, I'm taking a look18:19
exploreshaifaliyeah :)18:19
vkmcsomething I'm not sure about is L8418:19
vkmcI mean... you want to separate MANAGEMENT from MESSAGES18:20
vkmcand by summing the options you are duplicating conf params18:20
exploreshaifalivkmc, L84 or L94 here https://review.openstack.org/#/c/134910/2/zaqar/queues/storage/mongodb/options.py18:22
vkmcL84 in your change18:22
vkmcMESSAGE_MONGODB_OPTIONS = COMMON_OPTIONS + ( ...18:22
exploreshaifaliok got it18:23
vkmcI'm taking a look to the zaqar-scratch etherpad18:23
vkmcI might be missing something18:23
*** achanda has joined #openstack-zaqar18:25
exploreshaifalithere are many options which are common in both, such options are in COMMON_OPTIONS18:25
*** cpallares has quit IRC18:25
exploreshaifaliat one place18:26
*** cpallares has joined #openstack-zaqar18:26
*** jchai is now known as jchai_afk18:27
exploreshaifaliand then created 2 different variables to hold all the options needed for corresponding plane18:27
exploreshaifalivkmc, ^*18:27
exploreshaifalivkmc, also if there is surety that MANAGEMENT_MONGODB_OPTIONS will not going to alter in future18:29
exploreshaifaliwe can get rid of L83 too18:29
*** achanda has quit IRC18:30
vkmcthat sounds good but18:32
vkmcfor one plane you are using the common options18:32
vkmcand for the other one, the common options plus the partitions conf18:32
vkmcone is the subset of the other18:33
vkmcoptions should be disjoint sets18:33
exploreshaifaliit is because one need more options than other18:33
exploreshaifalioh they should be disjoint set!18:34
vkmcthat is what I want to understand :) if one if for management and the other is for messages, then the options should be different18:34
vkmcbut maybe I'm missing something18:35
*** achanda has joined #openstack-zaqar18:35
vkmcah well, apart from that doubt I have the change looks good exploreshaifali18:35
vkmclet's wait for other reviewers comments18:35
exploreshaifalias per as I understood, all these options are specifying details of a database for zaqar.conf file18:35
vkmcexactly yes :)18:36
exploreshaifaliso now if we have two sections of mongodb one for management database and one for message database18:36
exploreshaifaliwe will be having some options common18:37
*** jchai_afk is now known as jchai18:37
exploreshaifalibut their values could be different18:37
exploreshaifalithat is the problem18:37
vkmcyup18:37
vkmcoptions would overlap18:37
exploreshaifaliokay, all the alteration one want to do in zaqar.conf, should be done manually18:38
exploreshaifaliright?18:38
vkmcyeah18:38
vkmcyou deploy Zaqar by setting the required confs in zaqar.conf18:38
exploreshaifaliyes18:39
exploreshaifalihmm... so we can have  few common options like database-name different18:39
exploreshaifalithat is it should not be in common18:39
exploreshaifaliother few options like max_entry and max_retry can be in common18:40
exploreshaifalivariable18:40
vkmcso... for what I can understand from https://etherpad.openstack.org/p/zaqar-scratch18:43
vkmc(wait for it) lol18:45
exploreshaifali:D18:46
vkmcyeah still doesn't make much sense for me18:47
vkmcflaper87, kgriffs ^18:47
exploreshaifalione option is there18:47
exploreshaifalilet me try to put it on ethrpad18:47
vkmcsure18:47
exploreshaifalivkmc, stucked need to think more18:51
exploreshaifalivkmc, from where all these options get value?18:52
vkmcexploreshaifali, lets wait for flaper87's feedback on this :)18:53
vkmcexploreshaifali, all those options are crunched in zaqar.conf18:53
exploreshaifalilike there is an option `'ssl_keyfile`18:53
vkmcsome of them have default values, some of them not18:53
exploreshaifaliit does not have default value18:53
vkmcbut the user is the one who was to initialize those according to their settings18:53
exploreshaifaliand in zaqar.conf it will be commented18:53
exploreshaifalifine18:54
kgriffsvkmc: what doesn't make sense?18:54
exploreshaifalithen we can do somethind like18:54
vkmckgriffs, the separation of MONGODB group in MANAGEMENT and MESSAGES18:54
vkmcI was checking this etherpad https://etherpad.openstack.org/p/zaqar-scratch18:54
vkmcit probably makes sense, but I don't understand it :|18:55
kgriffsoh18:57
exploreshaifalican we do something like just create a function that will set detault values of different options18:57
kgriffsiirc, the idea was that most options are pretty generic and can be shared regardless of whether the DB connection is being set up for the admin data or the message data18:57
exploreshaifalifrom line 518:57
kgriffsbasically, connection specific options that are defined by the python driver for said data stores are the same18:58
exploreshaifalikgriffs, https://review.openstack.org/#/c/134910/2/zaqar/queues/storage/mongodb/options.py18:59
vkmckgriffs, yeah, that makes sense18:59
kgriffsthen there are options that are specific to the "application layer", i.e., our project's business logic18:59
kgriffsso that's the basic idea18:59
*** amitgandhinz has joined #openstack-zaqar19:00
* kgriffs clicks link19:00
*** flwang1 has joined #openstack-zaqar19:01
*** malini1 has joined #openstack-zaqar19:01
*** flwang1 has quit IRC19:03
*** malini has quit IRC19:03
kgriffsvkmc: ok, so what is the concern with this patch?19:03
vkmckgriffs, IIRC that would generate two groups with common options duplicated in zaqar.conf19:04
vkmcis it like that?19:05
kgriffsyes, that is correct. But you really are configuring two different backends, one for management and one for messages19:05
kgriffsyou should be able to configure them with different settings19:05
vkmcoic19:05
kgriffsI suppose we could have a "common" section and "inherit19:06
vkmcthat is what I was missing then :)19:06
exploreshaifalikgriffs, but I think one option database name should also be not in common variable19:06
kgriffsbut I think that would actually be more confusing19:06
exploreshaifalidatabase name should also be different for both management and messages isn't it?19:07
exploreshaifaliI didn't got your point regarding 'commom' and 'inherit'19:07
kgriffsexploreshaifali: right, if the operator wants to point both drivers to the same DB cluster, it would be prudent to use different DB names/namespaces19:08
kgriffsexploreshaifali: re inherit19:08
kgriffsI was just saying we could define a common section in the config where you could put options that are common across driver types19:09
kgriffsbut then you would have to have a way to override them for each driver19:09
exploreshaifaliokay19:09
kgriffsand in the end I think it is simpler to just say you need to configure all the options independently19:09
kgriffsespecially since I think we are going to recommend using different backend clusters for each anyway19:10
exploreshaifaliyes this would be more easy19:10
kgriffsso I think the patch as-is makes sense19:10
kgriffsalso keep in mind that for every DB there may not be both management and message drivers.19:11
kgriffsaaaaanyway19:11
vkmcit does :) thanks exploreshaifali and sorry for the confusion I caused19:11
kgriffsone question I had though19:11
vkmcI learned a few things ;)19:11
kgriffswas if we need to clone those options19:11
exploreshaifalivkmc, not at all it made things clear to me too19:12
kgriffsor does oslo config make copies when you register the options?19:12
exploreshaifalikgriffs, why do we need to clone the options?19:13
exploreshaifalijust to have a recovery?19:13
kgriffslet me just grep the 2,448 lines of cfg.py19:13
kgriffs(srsly. you couldn't break that module up to make it any smaller?)19:14
exploreshaifalisure19:14
vkmcIIRC oslo clone those kgriffs19:14
vkmcwhen those are registered19:14
kgriffshttps://github.com/openstack/oslo.config/blob/master/oslo/config/cfg.py#L180519:15
kgriffsdoesn't look like it19:16
kgriffsquestion is, does the state get stored directly by those opts...19:16
vkmcnow I don't know for sure :)19:19
kgriffshmmm, there is this namespace thingy...19:20
kgriffshttps://github.com/openstack/oslo.config/blob/master/oslo/config/cfg.py#L211819:20
kgriffshttps://github.com/openstack/oslo.config/blob/master/oslo/config/cfg.py#L232319:21
kgriffsOK, looks like the Opt class proxies to an instance of _Namespace class19:22
kgriffshttps://github.com/openstack/oslo.config/blob/master/oslo/config/cfg.py#L141419:22
* vkmc watches how kgriffs brain works19:22
exploreshaifalilol vkmc19:23
kgriffsand yeah, that in turn just proxies to config parser instance19:23
kgriffshttps://github.com/openstack/oslo.config/blob/master/oslo/config/cfg.py#L152919:23
kgriffsTLDR; We can share instances of Opt since state is actually maintained by this _Namespace class19:24
vkmcso... options are not cloned but the state is handled differently according to the namespace19:26
vkmcin this case, the group name19:26
vkmchopefully that's what kgriffs mean19:30
vkmclol19:30
kgriffsyeah, I'm still looking19:30
vkmcthanks kgriffs :)19:30
kgriffsI'm still fuzzy re the relationship between groups and namespace19:30
kgriffsit seems like namespace may just include all groups actually19:30
kgriffsso maybe namespace is "config file" vs. "cli options"?19:31
kgriffsi don't know19:31
kgriffs:p19:31
kgriffsanyway, I think we know enough for now19:31
vkmclet's try and see what happens (?)19:32
vkmczhiyan, I checked out the OSProfiler spec19:39
vkmczhiyan, it looks great!19:39
vkmczhiyan, and I think Zaqar would be really beneficiated from it19:39
vkmcI'll write the spec so other devs can review it19:39
vkmcprobably I'll have it done by tomorrow19:39
exploreshaifalikgriffs, whenver you get time, please give a thought to flaper87's last comment here https://bugs.launchpad.net/python-zaqarclient/+bug/135888919:43
*** jchai is now known as jchai_afk19:56
kgriffsexploreshaifali: commented20:00
exploreshaifalikragniz, thanks, will look at it :)20:01
exploreshaifalioh sorry kgriffs ^^20:01
*** jchai_afk is now known as jchai20:09
*** sgotliv has joined #openstack-zaqar20:14
*** sgotliv has quit IRC20:14
*** sgotliv has joined #openstack-zaqar20:14
openstackgerritVictoria Martínez de la Cruz proposed openstack/zaqar-specs: Add a persistent transport alternative  https://review.openstack.org/13456720:21
*** flwang1 has joined #openstack-zaqar20:25
*** sgotliv has quit IRC20:43
*** exploreshaifali has quit IRC20:45
openstackgerritVictoria Martínez de la Cruz proposed openstack/zaqar-specs: Add a persistent transport alternative  https://review.openstack.org/13456720:48
*** openstackgerrit has quit IRC20:49
*** openstackgerrit has joined #openstack-zaqar20:49
openstackgerritFlavio Percoco proposed openstack/zaqar: Update oslo-config-generation code  https://review.openstack.org/13501220:50
flaper87vkmc: kgriffs ^ pls :) it's an easy review20:50
flaper87I think claims are broken in the sqlalchemy driver20:51
flaper87claims expiration20:51
flaper87oh lord, I hate this driver20:51
flaper87oh wait, mmh20:54
flaper87damn20:54
*** achanda has quit IRC20:54
* vkmc hides20:55
*** davideagnello has quit IRC20:59
*** sgotliv has joined #openstack-zaqar21:00
flaper87kgriffs: do you recall why we're doing this? https://git.openstack.org/cgit/openstack/zaqar/tree/zaqar/queues/storage/sqlalchemy/messages.py#n30221:01
flaper87I mean, if the claim expired and someone is deleting the message, why are we raising that exception?21:01
*** davideagnello has joined #openstack-zaqar21:01
flaper87ah wait, there's an if statement missing there21:02
flaper87I htink21:03
kgriffslooking21:03
flaper87yeah, htink... >.>21:03
kgriffsi vaguely recall this being part of an effort to make all the drivers behave consistently21:06
flaper87the error there is that we're not checking if the claim has expired21:07
flaper87which we do for the mongo driver21:07
kgriffsoic21:07
flaper87damn, I hate this driver21:07
kgriffsaren't we about to kill it?21:07
kgriffs:)21:07
kgriffsor do we need to keep it around after all?21:07
flaper87no no, I already wrote a spec for that21:08
flaper87:P21:08
flaper87https://review.openstack.org/#/c/134248/21:08
kgriffsthe downside is people will say they don't want to deploy anything other than mysql or pg21:08
flaper87one thing though, I think we mentioned something about keeping it around for the management thing21:08
kgriffsflaper87: yeah, that's true21:08
kgriffsbut that is a small subset of the current driver21:08
flaper87we can keep it outside the code base21:08
flaper87we don't need to delete the code21:08
flaper87seriously, we ain't have enough resource to maintain this driver21:09
kgriffsthat was my next question21:09
flaper87if someone wants to step up, I think we'll be more than happy to keep it21:09
flaper87resources*21:09
kgriffsBTW, keystone middleware is still using memcached directly, not dogpile?21:11
kgriffsseems like that is what I saw last time I checked21:11
kgriffsI'd like to get All the Things able to use Redis21:11
flaper87I think they are already using dogpile21:12
kgriffskeystone service is21:12
flaper87wah ok21:12
kgriffsbut I'm not so sure about the middleware21:12
flaper87then no, it's not21:12
kgriffsif only I could clone myself I'd be happy to work on that. :p21:13
kgriffsit would be nice to sort of get Redis into lots of OS deployments21:13
kgriffsthen projects can leverage it in interesting ways without running into the "we don't want to have to manage one more DB thing" pushback21:14
kgriffsIMHO, it is a good candidate for "that other thing" beyond MySQL21:14
kgriffswhereas memcached is fairly limited, Redis can do a lot more and would unlock some interesting use cases for projects, not just Zaqar.21:15
*** malini1 has quit IRC21:15
kgriffs</soapbox>21:15
flaper87LOL21:15
flaper87but yeah, I agree with21:15
flaper87you21:15
flaper87:P21:16
flaper87btw, I dunno how the sqlalchemy thing passes tests21:16
flaper87really21:16
flaper87it's dark magic21:16
kgriffslol21:16
kgriffsno, it's Alchemy21:16
kgriffsOS X dictionary defines Alchemy as " a seemingly magical process of transformation, creation, or combination"21:17
kgriffslol21:17
kgriffsdark magic indeed. :p21:17
*** fifieldt_ has joined #openstack-zaqar21:22
vkmca magical process of joining stuff together and wasting tons of resources21:22
kgriffsI think if we add a swift driver then that can be our "i don't like mongo" alternative21:23
kgriffsas well as our "i don't want to deploy anything else than what I already have" answer21:23
*** fifieldt has quit IRC21:23
flaper87really, I dunno how this driver works21:23
flaper87we don't even check on claims expire time21:23
flaper87when getting messages21:23
kgriffsspeaking of which, do we have a spec for the swift work?21:23
flaper87we just check on the id21:23
flaper87kgriffs: zhiyan will work on one21:24
mpanettakgriffs: You don't like mongo? *sniff sniff* :P21:24
kgriffsoh, I like it21:24
notmynamehttp://2.bp.blogspot.com/-YhcOntV_57M/UslUK8g059I/AAAAAAAAPy4/f8IZZVotRxQ/s1600/put-that-evil-on-me.gif21:24
flaper87I had a really quick chat with notmyname  about it21:24
flaper87notmyname: LOL21:24
flaper87It might work if we figure out how to align all plates on December 31st at midnight (PST) before the firworks happen in China21:25
flaper87kgriffs: ^21:25
flaper87planets*21:25
flaper87fireworks*21:25
flaper87YES, I'M HUNGRY21:25
kgriffslol21:25
flaper87and that's the easy part21:26
flaper87:P21:26
kgriffsheh21:26
kgriffsso, the heat guys were keen on the idea of using swift21:26
notmynameor are they keen on not deploying mongo?21:26
kgriffswere there other people asking for it besides them?21:26
kgriffsnotmyname: idk, good question21:26
kgriffsI think they are already using swift and it just seemed like a natural progression?21:27
* kgriffs is admittedly fuzzy on the details21:27
*** achanda has joined #openstack-zaqar21:28
*** exploreshaifali has joined #openstack-zaqar21:30
flaper87kgriffs: btw, i think we've a problem. That patch that did some magic with the logging might have enabled more logging than it should21:30
flaper87kgriffs: https://review.openstack.org/#/c/135012/ <- now >.>21:31
flaper87it's an EASY one21:31
flaper87:D21:31
kgriffsbash no mor? srlsy?21:31
flaper87YEAH!21:31
kgriffshttp://stream1.gifsoup.com/view1/1603965/bill-and-ted-air-guitar-o.gif21:32
flaper87and no more sample file to keep update21:32
flaper87(well that one already landed)21:32
flaper87hahah21:32
* flaper87 wants a new badge everytime he does something like: #0day +13, -21821:32
kgriffshmm21:32
* flaper87 wants a new badge everytime he does something like: +13, -21821:32
kgriffshttps://review.openstack.org/#/c/135012/2/etc/oslo-config-generator/zaqar.conf21:32
kgriffshow do I know all the right namespaces are included? ;)21:33
flaper87kgriffs: I copied them from our previous file21:33
flaper87:P21:33
kgriffswfm21:33
flaper87*cough* you should know them all, btw *cough*21:33
* flaper87 doesn't even know what a namespace is21:33
* vkmc stopped reading for a while now 21:34
kgriffsflaper87: looks like tempest is borked21:36
kgriffshttps://review.openstack.org/#/c/13501221:36
flaper87I hate it when tests force me to do the right thing21:38
flaper87jsut rechecked, it can't be related to the patch21:39
* flaper87 should've read the logs21:39
flaper87:s21:39
*** reed has quit IRC21:41
*** reed has joined #openstack-zaqar21:42
*** reed has quit IRC21:42
*** jchai is now known as jchai_afk21:44
*** reed has joined #openstack-zaqar21:52
*** amitgandhinz has quit IRC21:58
*** amitgandhinz has joined #openstack-zaqar21:58
*** sriram has quit IRC22:07
*** jchai_afk is now known as jchai22:08
*** kgriffs is now known as kgriffs|afk22:19
*** mpanetta has quit IRC22:20
*** exploreshaifali has quit IRC22:20
*** davideagnello has quit IRC22:36
*** davideagnello has joined #openstack-zaqar22:36
*** mpanetta has joined #openstack-zaqar22:39
*** cpallares has quit IRC22:46
*** jchai has quit IRC22:50
*** mpanetta has quit IRC23:02
*** vkmc has quit IRC23:11
*** kgriffs|afk is now known as kgriffs23:19
*** ametts has quit IRC23:23
*** kgriffs is now known as kgriffs|afk23:29
*** amitgandhinz has quit IRC23:37
*** reed has quit IRC23:41
*** davideagnello has quit IRC23:48
*** davideagnello has joined #openstack-zaqar23:53
*** achanda has quit IRC23:57

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