Thursday, 2015-01-22

*** jd__ has quit IRC00:02
*** annegent_ has joined #openstack-swift00:03
*** ho has joined #openstack-swift00:07
*** abhirc has quit IRC00:12
hogood morning guys!00:13
*** Nadeem has quit IRC00:17
*** lcurtis has quit IRC00:19
*** jd__ has joined #openstack-swift00:26
*** haomaiwa_ has joined #openstack-swift00:26
*** tellesnobrega_ has joined #openstack-swift00:31
*** annegent_ has quit IRC00:32
zaitcevohayou gozaimasu, ho-san00:43
hozaitcev: ohayou gozaimasu. zaitcev-san :)00:54
*** addnull has joined #openstack-swift00:59
*** jasondotstar has joined #openstack-swift01:07
*** lpabon has quit IRC01:18
openstackgerritParantap Roy proposed openstack/python-swiftclient: SwiftClient object beginning with / or ./  https://review.openstack.org/14879101:20
*** addnull has quit IRC01:22
openstackgerritClay Gerrard proposed openstack/python-swiftclient: Fix environment sanitization for TestServiceUtils  https://review.openstack.org/14910801:25
*** tellesnobrega_ has quit IRC01:29
*** addnull has joined #openstack-swift01:29
*** addnull has quit IRC01:33
*** addnull has joined #openstack-swift01:34
*** d0ugal has quit IRC01:55
*** d0ugal has joined #openstack-swift01:55
*** d0ugal is now known as Guest8510401:56
*** dfg_ has joined #openstack-swift01:57
*** ho__ has joined #openstack-swift01:58
*** briancline_ has quit IRC01:58
*** tristanC_ has joined #openstack-swift01:58
*** briancline_ has joined #openstack-swift01:58
*** kragniz_ has joined #openstack-swift01:59
*** mordred_ has joined #openstack-swift02:04
*** amandap_ has joined #openstack-swift02:05
*** ho has quit IRC02:06
*** dfg has quit IRC02:06
*** addnull has quit IRC02:06
*** tristanC has quit IRC02:06
*** amandap has quit IRC02:06
*** AbyssOne_ has quit IRC02:06
*** kragniz has quit IRC02:06
*** mordred has quit IRC02:06
*** dvorkbjel has quit IRC02:06
*** mordred_ is now known as mordred02:06
*** AbyssOne_ has joined #openstack-swift02:06
*** dvorkbjel has joined #openstack-swift02:07
*** addnull has joined #openstack-swift02:08
*** addnull has quit IRC02:12
*** tellesnobrega_ has joined #openstack-swift02:20
*** addnull has joined #openstack-swift02:22
*** addnull has quit IRC02:26
*** abhirc has joined #openstack-swift02:31
*** amandap_ is now known as amandap02:34
*** lcurtis has joined #openstack-swift02:43
*** addnull has joined #openstack-swift02:44
*** addnull has quit IRC02:49
*** addnull has joined #openstack-swift02:54
*** tsg has joined #openstack-swift02:54
*** tsg_ has joined #openstack-swift02:54
*** lpabon has joined #openstack-swift02:55
*** lpabon has quit IRC02:55
*** tsg_ has quit IRC02:56
*** addnull has quit IRC02:59
*** kei_yama has joined #openstack-swift03:02
*** kei_yama has quit IRC03:09
*** kei_yama has joined #openstack-swift03:12
*** bill_az has quit IRC03:18
*** addnull has joined #openstack-swift03:23
*** kei_yama has quit IRC03:24
*** kei_yama has joined #openstack-swift03:25
*** addnull has quit IRC03:28
*** fandi has quit IRC03:28
*** bpap has quit IRC03:30
*** bkopilov has quit IRC03:32
*** jasondotstar has quit IRC03:47
*** zhiyan has quit IRC03:48
*** zhiyan has joined #openstack-swift03:49
*** addnull has joined #openstack-swift03:49
*** annegent_ has joined #openstack-swift03:50
*** addnull has quit IRC03:53
*** tellesnobrega_ has quit IRC04:01
*** addnull has joined #openstack-swift04:34
*** bkopilov has joined #openstack-swift04:34
*** addnull has quit IRC04:38
*** bkopilov has quit IRC04:39
*** addnull has joined #openstack-swift04:51
*** dmsimard_away is now known as dmsimard04:53
*** addnull has quit IRC04:55
*** ppai has joined #openstack-swift04:55
*** annegent_ has quit IRC05:02
*** annegent_ has joined #openstack-swift05:03
*** addnull has joined #openstack-swift05:04
*** dmsimard is now known as dmsimard_away05:07
*** addnull has quit IRC05:09
*** addnull has joined #openstack-swift05:16
*** addnull has quit IRC05:21
*** addnull has joined #openstack-swift05:28
*** tsg has quit IRC05:33
*** addnull has quit IRC05:39
*** annegent_ has quit IRC05:43
*** addnull has joined #openstack-swift05:48
*** SkyRocknRoll has joined #openstack-swift05:54
*** SkyRocknRoll has joined #openstack-swift05:54
*** lcurtis has quit IRC05:55
*** addnull has quit IRC06:04
*** addnull has joined #openstack-swift06:10
*** gvernik has joined #openstack-swift06:12
*** annegent_ has joined #openstack-swift06:13
*** addnull has quit IRC06:14
*** annegent_ has quit IRC06:20
*** addnull has joined #openstack-swift06:22
*** addnull has quit IRC06:25
*** addnull has joined #openstack-swift06:27
*** gvernik has quit IRC06:30
*** addnull has quit IRC06:51
*** addnull has joined #openstack-swift06:58
*** silor has joined #openstack-swift07:04
*** zaitcev has quit IRC07:07
*** addnull has quit IRC07:14
*** nshaikh has joined #openstack-swift07:26
*** addnull has joined #openstack-swift07:30
*** addnull has quit IRC07:34
*** chlong has quit IRC07:38
*** Guest85104 is now known as d0ugal07:42
*** d0ugal is now known as Guest7919507:42
*** Guest79195 is now known as d0ugal07:48
*** d0ugal has joined #openstack-swift07:48
*** addnull has joined #openstack-swift07:55
*** addnull has quit IRC07:57
*** rledisez has joined #openstack-swift08:09
*** geaaru has joined #openstack-swift08:24
*** oomichi_ has quit IRC08:40
*** goodes has quit IRC08:50
*** nottrobin has quit IRC08:50
*** ipolyzos has quit IRC08:51
*** zhiyan has quit IRC08:55
*** goodes has joined #openstack-swift09:00
*** ipolyzos has joined #openstack-swift09:01
*** nottrobin_ has joined #openstack-swift09:01
*** zhiyan has joined #openstack-swift09:02
*** jordanP has joined #openstack-swift09:21
*** jistr has joined #openstack-swift09:24
*** annegent_ has joined #openstack-swift09:27
*** nshaikh has left #openstack-swift09:30
*** annegent_ has quit IRC09:32
*** acoles_away is now known as acoles09:32
*** ahonda has quit IRC09:44
*** nellysmitt has joined #openstack-swift09:50
*** bkopilov has joined #openstack-swift09:57
*** haomaiwa_ has quit IRC10:01
*** fandi has joined #openstack-swift10:02
*** chlong has joined #openstack-swift10:15
*** aix has joined #openstack-swift10:20
*** chlong has quit IRC10:20
*** jasondotstar has joined #openstack-swift10:30
*** jasondotstar has quit IRC10:30
*** chlong has joined #openstack-swift10:33
*** chlong has quit IRC10:37
*** chlong has joined #openstack-swift10:49
*** mahatic has joined #openstack-swift10:55
*** annegent_ has joined #openstack-swift11:16
*** dmorita has quit IRC11:20
*** dmorita has joined #openstack-swift11:21
*** annegent_ has quit IRC11:21
*** nshaikh has joined #openstack-swift11:21
*** kei_yama has quit IRC11:37
*** aix has quit IRC11:38
*** kragniz_ is now known as kragniz11:45
*** dmorita has quit IRC11:46
openstackgerritMerged openstack/swift: Improve object-replicator startup time.  https://review.openstack.org/14017811:54
*** jyoti-ranjan has joined #openstack-swift11:57
jyoti-ranjanHi, I am getting following error:11:58
jyoti-ranjanERROR with Object server 192.168.0.10:6000/d1 re: Trying to get final status of PUT to /v1/AUTH_5674fc4e041c4855aba39537ce24beff/glance/255606aa-5ffc-4440-b67d-619665802ab8: Timeout (10s11:58
jyoti-ranjanAny input to fix will be of great help.11:58
jyoti-ranjanError occurs occassionally.11:58
*** wolsen_ has quit IRC12:00
*** dosaboy has quit IRC12:02
*** xianghui has quit IRC12:02
*** xianghui has joined #openstack-swift12:04
*** dosaboy has joined #openstack-swift12:04
*** wolsen has joined #openstack-swift12:05
*** echevemaster has quit IRC12:14
*** haomaiwang has joined #openstack-swift12:28
*** haomai___ has joined #openstack-swift12:32
*** haomaiwang has quit IRC12:35
*** chlong has quit IRC12:44
*** ho__ has quit IRC12:54
openstackgerritPrashanth Pai proposed openstack/swift: Allow rsync to use compression  https://review.openstack.org/14845412:55
*** km has quit IRC12:56
*** jyoti-ranjan2 has joined #openstack-swift13:14
*** annegent_ has joined #openstack-swift13:16
*** annegent_ has quit IRC13:21
*** tdasilva has joined #openstack-swift13:26
*** marcusvrn_ has joined #openstack-swift13:33
*** bkopilov has quit IRC13:39
*** aix has joined #openstack-swift13:40
*** annegent_ has joined #openstack-swift13:43
*** tristanC_ is now known as tristanC13:47
*** miqui has joined #openstack-swift13:54
*** annegent_ has quit IRC13:57
*** fandi has quit IRC14:02
*** annegent_ has joined #openstack-swift14:04
openstackgerritPrashanth Pai proposed openstack/swift: Allow rsync to use compression  https://review.openstack.org/14845414:14
*** annegent_ has quit IRC14:15
ppaiHi all, is the "id" member in ring structure unique in a machine or across the cluster ?14:19
*** jyoti-ranjan has quit IRC14:19
*** jyoti-ranjan2 has quit IRC14:19
*** tsg has joined #openstack-swift14:20
tdasilvaI think the id is for a device14:33
*** nshaikh has left #openstack-swift14:34
rledisezAFAIK, id is unique and cannot be reused14:34
rledisezthe ring is a python structure, the devices are in an array, the id is the index of the array14:34
rledisezwhen a device is remove, the value is set to None14:34
rledisezso, i think you can considere it is unique in a cluster and not reused14:35
rledisezsorry for the nickname14:35
*** haomai___ has quit IRC14:36
rledisezclayg: hello14:38
rledisezclayg: did you have time to look at my review since i updated the patch following your recommendations? https://review.openstack.org/#/c/137659/14:39
*** SkyRocknRoll has quit IRC14:46
*** fandi has joined #openstack-swift14:51
*** fandi has quit IRC14:53
*** fandi has joined #openstack-swift14:53
*** fandi has quit IRC14:53
ppairledisez, thank you14:54
*** ppai has quit IRC14:59
*** fandi has joined #openstack-swift15:05
*** nellysmitt has quit IRC15:05
*** dmsimard_away is now known as dmsimard15:12
*** lpabon has joined #openstack-swift15:13
*** annegent_ has joined #openstack-swift15:18
*** fandi has quit IRC15:19
*** annegent_ has quit IRC15:20
openstackgerritTakashi Kajinami proposed openstack/swift: Remove redundant container updating after rsync  https://review.openstack.org/14930815:21
*** fandi has joined #openstack-swift15:21
*** fandi has quit IRC15:22
*** bkopilov has joined #openstack-swift15:23
openstackgerritPrashanth Pai proposed openstack/swift: Skip nodes that does not support REPLICATE verb  https://review.openstack.org/14931515:29
*** CrackerJackMack has quit IRC15:32
openstackgerritTakashi Kajinami proposed openstack/swift: Prevent redundant commenting by drive-audit  https://review.openstack.org/14931715:33
*** CrackerJackMack has joined #openstack-swift15:33
openstackgerritTakashi Kajinami proposed openstack/swift: Remove redundant container updating after rsync  https://review.openstack.org/14930815:36
*** annegent_ has joined #openstack-swift15:41
*** annegent_ has quit IRC15:56
*** briancurtin has quit IRC15:57
*** lcurtis has joined #openstack-swift15:59
*** gvernik has joined #openstack-swift15:59
*** briancurtin has joined #openstack-swift16:02
*** lpabon has quit IRC16:04
openstackgerritThiago da Silva proposed openstack/swift: WIP: single-process  https://review.openstack.org/14932916:09
*** bill_az has joined #openstack-swift16:13
*** abhirc has quit IRC16:13
*** nshaikh has joined #openstack-swift16:16
*** hugespoon has joined #openstack-swift16:17
*** annegent_ has joined #openstack-swift16:20
*** fandi has joined #openstack-swift16:36
*** jrichli has joined #openstack-swift16:36
*** annegent_ has quit IRC16:37
*** tsg has quit IRC16:46
*** annegent_ has joined #openstack-swift16:53
*** nshaikh has quit IRC16:54
*** portante has quit IRC16:56
*** ndk_ has quit IRC16:56
*** marcusvrn_ is now known as marcusvrn16:57
*** lcurtis has quit IRC16:58
*** annegent_ has quit IRC17:01
*** IRTermite has joined #openstack-swift17:02
*** portante has joined #openstack-swift17:03
*** ChanServ sets mode: +v portante17:03
*** ndk has joined #openstack-swift17:11
*** abhirc has joined #openstack-swift17:14
*** rledisez has quit IRC17:20
*** MooingLemur has quit IRC17:23
*** tsg has joined #openstack-swift17:25
*** aix has quit IRC17:27
*** abhirc has quit IRC17:30
*** abhirc has joined #openstack-swift17:31
*** annegent_ has joined #openstack-swift17:32
*** MooingLemur has joined #openstack-swift17:33
*** jordanP has quit IRC17:44
*** annegent_ has quit IRC17:44
*** david-lyle has joined #openstack-swift17:50
*** lpabon has joined #openstack-swift17:56
*** nellysmitt has joined #openstack-swift18:00
*** gvernik has quit IRC18:01
*** nellysmitt has quit IRC18:04
*** lcurtis has joined #openstack-swift18:11
*** marcusvrn has quit IRC18:12
*** nellysmitt has joined #openstack-swift18:17
abhircraies: I don;t have any other leads , but if you poke around the #openstack channel u might get some info , also check the openstack dev mailing list18:19
*** zaitcev has joined #openstack-swift18:22
*** ChanServ sets mode: +v zaitcev18:22
*** annegent_ has joined #openstack-swift18:31
*** annegent_ has quit IRC18:33
*** annegent_ has joined #openstack-swift18:46
*** nellysmitt has quit IRC18:47
*** gyee has joined #openstack-swift18:54
*** jistr has quit IRC18:58
*** mahatic has quit IRC18:59
*** annegent_ has quit IRC19:10
*** acoles is now known as acoles_away19:18
claygrledisez - you left! :'(19:19
claygI did look at it, got distracted getting vagrant-swift-all-in-one to support trusty (which i'm not even sure if I pushed up yet...)19:19
clayg... but I needed the newer kernel to functionally test the patch, so trusty seemed like it would be good enough and then didn't get back to review - I'll add it to the list19:20
* clayg yells into to abyss19:21
*** annegent_ has joined #openstack-swift19:22
*** tsg has quit IRC19:23
swifterdarrellclayg: careful... they say it'll yell back19:23
*** silor1 has joined #openstack-swift19:25
*** silor has quit IRC19:27
*** geaaru has quit IRC19:28
*** nellysmitt has joined #openstack-swift19:42
*** annegent_ has quit IRC19:43
*** panbalag has joined #openstack-swift19:58
openstackgerritSamuel Merritt proposed openstack/swift: Optimize replication of targeted devices/partitions.  https://review.openstack.org/14938420:07
*** wasmum has joined #openstack-swift20:21
*** tsg has joined #openstack-swift20:48
claygwtf is this?  -> https://bugs.launchpad.net/swift/+bug/141371120:50
claygopening a grammer bug does *not* fix the typos20:50
tdasilvaclayg: similar to this one: https://bugs.launchpad.net/swift/+bug/136508421:00
mattoliverauMorning21:07
openstackgerritMerged openstack/swift: Implement OPTIONS verb for storage nodes.  https://review.openstack.org/14010321:19
*** tellesnobrega_ has joined #openstack-swift21:24
tdasilvamattoliverau: morning :-)21:29
dmsimardFYI.. Nasty glance bug we've hit with Swift as backend: https://bugs.launchpad.net/glance/+bug/141280221:34
*** fifieldt__ has quit IRC21:37
torgomaticdmsimard: busted uploader, eh? doesn'21:38
torgomatict sound fun21:38
*** fifieldt__ has joined #openstack-swift21:38
dmsimardMy understanding was that glance was chunking files, uploading every chunks21:38
dmsimardbut didn't upload the last chunk21:39
dmsimardor something21:39
*** jodah has joined #openstack-swift21:43
jodahIs there a way to ensure that an object PUT to swift is placed on a particular node?21:44
ahaleif you have access to the rings and the config secrets you can just keep renaming until you get what you want21:45
jodahhahaha - yea21:45
jodahDoes the ring take physical locality of nodes into account - or just ring locality (the docs mention swift attempts to place replicas far apart on the ring)?21:46
jodahBy physical locality I mean something such as placing replicas on different racks21:46
ahaleby zone,  so splitting zones by rack would do that21:47
jodahbut you may (likely?) suffer higher latency by replicating across zones?21:47
ahaleor regions, but i dont really know much about that, someone else will though21:47
ahalemaybe, it depends how you network really21:48
jodahindeed. i think you're probably hitting a few more switches though21:48
ahaleyou can have a separate replication interface and network if it all gets really crazy21:48
jodahbut swift would need to know about those things21:48
ahaleyep thats all in the rings21:48
jodahdoes it replicate across AZs now? or can it?21:48
*** lcurtis has quit IRC21:49
ahaleit depends how you define az21:49
ahalebut yeah it can replicate across continents - though i've only done within datacenters21:49
zaitcevBack it up, guys. Let's first identify who jodah wants "to ensure that an object PUT to swift is placed on a particular node". Is this knowledge visible to client and then you have API to force placement? Or, you want cluster administrator configure ring for locality?21:49
jodahFor an administrator21:50
jodahFor another OpenStack service, really, in my case Trove/Sahara21:50
ahaleok :) i was just going with the questions21:50
zaitcevOkay. Are you willing to take the durability hit that's inevitably associated with locality?21:50
zaitcevOh, it's Sahara21:50
zaitcevI knew it :-)21:51
*** silor1 has quit IRC21:51
jodah;)21:51
jodahwell ideally we'd want 1 copy on the same rack as something, like say, the same rack/host that our VM is on. but of course we'd want Swift to place other replicas in other places21:51
jodah....as it does21:51
zaitcevyeah. well, you can't do that with a DHT, because the hashing is the key21:51
jodahbut still, having 1-2 copies on the same rack would cut down on network saturation.21:51
jodahcould hashing potentially take location into account - like, to be biased towards nodes on the same rack (affinity) or diff racks (anti-affinity)?21:52
jodahlike to only select from nodes that are or are not on the same rack, and hash from those21:52
jodahI'm asking from the perspective of Trove and Sahara, but really the ability to strategically place replicas behind different points of failure (racks) even within the same AZ could be beneficial to Swift as well21:53
ahaleah - I have been thinking around the same things with zerovm and data locality and keep thinking more about storage policies to limit where my data goes in a larger cluster21:53
zaitcevMaybe you should look at Ceph. They allow you to maneuver the placement groups like that.21:54
jodahright - the common thing with all of these is that they're datastores with partitioned/replicated data. and for various reasons - latency, fault tolerance, location matters.21:54
jodaheven the concept of a placement group only gives you affinity - you still want anti-affinity for fault tolerance.21:55
openstackgerritSamuel Merritt proposed openstack/swift: Make ThreadPools deallocatable.  https://review.openstack.org/14564721:55
zaitcevAnyway, I have a feeling that you don't know about the exceedingly ugly kludge that Sahara implemented to force locality into Swift. Not sure if I should point it out, you may sleep better without knowing.21:56
jodahI do21:56
jodahhaha21:56
jodahIt's unfortunate, as all agree21:56
mattoliveraujodah: long story short, no you can't. Swift will use the ring to place the data on different devices, and other then weights and your availablility zones you don't have that much control. But you could use storage policies to have specific sets of storage nodes, and have a little more control that way.21:56
jodahSo I'm interested in looking for a more general solution, particularly since this would benefit Trove as well.21:57
zaitcevAh, okay. So that's why you place the emphasis is on the administrator.21:57
jodahYea21:57
jodahEnd users could benefit from something similar - placement group affinity and anti-affinity - but they don't necessarily need this.21:57
zaitcevListen, we need to put this onto agenda for hackathon in February.21:57
zaitcevpoke notmyname about it21:58
jodahmattoliverau: Is this something that could reasonably be suggested for the future? For the benefit of Sahara/Trove - it would be nice to be able to place objects onto specific nodes, such as those sharing a rack with a particular VM. For the benefit of Swift itself, it would be nice if the same underlying information could be used to influence where the ring places replicas.21:59
tdasilvamattoliverau, zaitcev: wouldn't the write_affinity setting help jodah ?22:14
mattoliveraujodah: you can play with the write affinity on the proxy to force writing to local nodes (or certain regions and or regions first), but if you have more then "replica" availablility zones then you can't garrentee a certian zone as it depends on the where the ring partition is being placed in the cluster which is decided at ring creation/rebalance not run time. If you have a storage policy containing only 3 (or replica22:15
mattoliverau count) availability zones and say these zones are racks, and are evenly balanced, then you can reasonably say one replica would be on each rack22:15
zaitcevtdasilva: I don't know, sorry. I need to know what we have now and what jodah needs overall.22:15
mattoliverau*certain regions or zones first22:15
mattoliverauStill pre coffee for me.. so not quite awake yet :P22:16
jodahGood info22:17
mattoliverautdasilva: yeah it could a little, I was just writing something about that :P22:17
tdasilvamattoliverau: I think a while back you said something about "great minds" :P22:19
mattoliverautdasilva: ;)22:19
jodahI understand that :)22:23
jodahzaitcev: The primary requirement is the need to be able to place an object on a particular host, or at least, onto a particular rack.22:23
jodahThe secondary requirement is the need to instruct Swift to (for certain objects - perhaps) place some replicas on the same rack and others on a separate rack. This implies that Swift has knowledge of host->rack information, which of course it doesn't. But this ability to "place" resources into a specific location is needed by us from Nova as well - so perhaps a common solution for housing this information could make sense.22:23
jodahBoth goals are about exploiting data locality, for minimizing read/write latency, and for fault tolerance by ensuring that replicas are placed behind separate points of failure.22:25
zaitcevYou can create a policy with a more restricted ring for that today... Client has to select it though (presumably it's not the default one). I think ahale mentioned that above.22:25
jodahok - i'll read up on policies22:26
jodahcan a policy be selected per object or are they globally configured?22:26
zaitcevPolicies are per container.22:26
jodahok22:26
*** bpap has joined #openstack-swift22:29
*** dmsimard is now known as dmsimard_away22:32
claygtorgomatic: now someone is going to ask you to move the initialization code in a revivify method and make it so you can call that after youc all terminate to make it _alive again22:35
torgomaticclayg: yes; being wrong never seems to stop people from doing things ;)22:36
jodahDifferent question: When GETting an object from an endpoint given via the list endpoints call available in the middleware, presumably the object is just read from local storage on the host at the endpoint?22:37
torgomaticjodah: that's the theory22:37
zaitcevGood heavens, it's an actual word - http://www.dict.org/bin/Dict?Form=Dict2&Database=*&Query=vivify22:37
jodahlol - i'll assume yes then :)22:37
claygzaitcev: sorry i picked it up from swifterdarrell - i had the same reaction22:37
claygat the time I felt like there was another word i had that ment the same thing but poeple wouldn't freak out when you said it - now I feel like that's the exact word I want when that's what I mean22:38
swifterdarrellclayg: sure it wasn't reify/reified?22:38
zaitcevThe _best_ misunderstanding _ever_.22:39
claygswifterdarrell: jesus, probably22:39
*** annegent_ has joined #openstack-swift22:49
*** abhirc has quit IRC22:50
*** annegent_ has quit IRC22:55
*** hugespoon has quit IRC22:56
*** hugespoon has joined #openstack-swift23:13
*** briancline_ has quit IRC23:14
*** jrichli has quit IRC23:15
*** zaitcev has quit IRC23:26
*** tellesnobrega_ has quit IRC23:31
*** jasondotstar has joined #openstack-swift23:34
*** briancurtin has quit IRC23:41
*** briancurtin has joined #openstack-swift23:41
*** echevemaster has joined #openstack-swift23:46
*** briancurtin has quit IRC23:49
*** david-lyle is now known as david-lyle_afk23:56
*** chlong has joined #openstack-swift23:59

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