Monday, 2016-09-12

*** baojg has joined #openstack-swift00:16
*** takashi has quit IRC00:28
*** baojg has quit IRC00:42
*** m_kazuhiro has joined #openstack-swift00:54
*** mingyu has quit IRC01:01
*** chlong_ has joined #openstack-swift01:12
*** chlong has joined #openstack-swift01:12
zhengyingood morning01:30
zhengyinmattoliverau,kota_: morning01:30
mattoliverauzhengyin: o/01:31
kota_zhengyin: o/01:34
kota_zhengyin: btw, where timezone in you are? it looks Asian Pacific?01:35
kota_s/in you are/are you in/01:35
kota_maybe/01:35
kota_my bad english .. :/01:35
zhengyinkota_: I am in China01:39
kota_zhengyin: gotcha, almostly same timezone with me (maybe 1 hour difference?)01:40
zhengyinkota_:yes, you are an hour faster than me01:41
zhengyinnow, it is 9:41 in China01:41
kota_zhengyin: I'm happy looking contributors in similar timezone in active ;-)01:42
zhengyinkota_: thank you, I just graduated from school, I 阿吗01:44
zhengyinI am a newer in here, I will learn from you and community :)01:46
kota_zhengyin: nice, anytime, feel free to ask everything ;-)01:48
zhengyinkota_: thanks a lot.01:50
zhengyin:)01:51
*** jamielennox is now known as jamielennox|away02:00
*** jamielennox|away is now known as jamielennox02:04
*** vint_bra has joined #openstack-swift02:17
mattoliveraukota_, zhengyin: you clocks are both too slow :P Looks like I'm 2 hours ahead of zhengyin. Although it's Spring here so day light savings will change things soon a suspect :)02:17
*** lifeless_ has quit IRC02:19
zhengyinmattoliverau: you are in our East and in Australia? :)02:23
mattoliverauzhengyin: yup East coast of Australia :)02:23
kota_beach office!!!02:24
jrichlizhengyin: will you be going to the summit in Barcelona?02:25
mattoliveraukota_: that's right!02:25
mattoliveraujrichli: you?02:25
zhengyinmattoliverau: I know Sydney is a seaside city and  it is beautiful02:26
jrichlimattoliverau: yes.  you?  I remember you saying that you were waiting on approval02:26
mattoliveraujrichli: yup \o/. Finally got the approval :)02:26
jrichliYay!02:26
jrichlihope you didnt have to go with a shady hotel miles away!02:27
mattoliverauzhengyin: I'm about 3 hours south (driving) from Sydney, in a costal town on the beach :)02:27
jrichlithe hotel search was a bit challenging to stay in policy this time02:28
mattoliveraujrichli: not this time, Rackspace has a block and actually had room for us Aussies thus time :)02:28
jrichlinice!02:28
*** vint_bra has quit IRC02:29
zhengyinjrichli: sorry, Leadership is not approved,I will not go to the summit in Barcelona,02:29
mattoliverauzhengyin: always next time :(02:30
jrichlizhengyin: I am disappointed to here that we won't get to meet you in person yet :-(  maybe the ... what is it called ... PTG?02:30
jrichlithe dev meetup organized by openstack02:30
jrichliin Feb02:30
*** tqtran has joined #openstack-swift02:31
zhengyinI'm sorry that I can't see you this time02:31
jrichlis/here/hear/  ... yes, jrichli does know how to spell.  most words.02:31
mattoliveraujrichli: good for you, cause I don't :P02:32
jrichlimattoliverau: well, I don't even know many words - but my interactions with acoles has increased my number!02:33
mattoliverauzhengyin: PTG in Atlanta, then Forum (summit) in Boston.. the the next forum would be better cause it'll be in Sydney (but I might be a bit biased) :P02:33
*** lifeless has joined #openstack-swift02:34
mattoliveraujrichli: lol02:34
mattoliverauof course02:34
jrichliCan't wait for Sydney!02:34
*** tqtran has quit IRC02:35
* mattoliverau might go enjoy this Spring weather with a walk on the beach ;)02:35
mattoliveraubbs02:35
jrichlinice, have fun!02:36
zhengyinmattoliverau: have fun :)02:37
zhengyinmattoliverau: do you have time to help me review patch 366689? :)02:45
patchbothttps://review.openstack.org/#/c/366689/ - swift - Add test cases in the common/test_db02:45
*** StraubTW has quit IRC02:49
*** Jeffrey4l has quit IRC02:52
*** Jeffrey4l has joined #openstack-swift02:58
openstackgerritMerged openstack/swift: Add troubleshooting tips to keystoneauth docs  https://review.openstack.org/36686803:15
notmynamehello, again03:17
notmynamezhengyin: I'm sorry I won't see you in barcelona03:17
zhengyinnotmyname: hi, notmyname, I may see you and friends of Community next time :)03:21
notmynamezhengyin: I hope so03:21
zhengyinnotmyname: when is this version released?03:23
*** okdas has quit IRC03:24
notmynamethe next version of swift or the next combined openstack release? well, actually right now it's the same answer03:24
notmynamethe openstack newton release will be on the week of october 3, and it will include swift 2.10.003:25
notmynamehttps://releases.openstack.org/newton/schedule.html03:26
*** okdas has joined #openstack-swift03:26
*** okdas has joined #openstack-swift03:26
notmynamein fact, tonight I'm finishing up a presentation and then looking at the starred patches to see what can land for 2.10.003:26
notmynamespecifically, we need to have the 2.10.0 release by the end of the month. so, basically, any point between now and end of the month we can tag it and call it 2.10.003:27
zhengyinwell, I know and I will commit some patchs before this release :)03:28
notmyname:-)03:29
zhengyinand review some patch03:29
notmynameyes, definitely do reviews. that's very helpful03:29
notmynameI'll be updating https://wiki.openstack.org/wiki/Swift/PriorityReviews soon03:30
notmynamebut in the meantime, looking at the starred reviews is good03:30
notmynameoh. that link isn't in the topic any more03:30
notmynamehang on03:30
zhengyinok, I start to learn to review patch now, and it may have mistake :)03:31
*** ChanServ changes topic to "Let's talk, we're nice. | Reviews: http://goo.gl/mtEv1C | Ideas: https://wiki.openstack.org/wiki/Swift/ideas | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/ | Meetings: https://wiki.openstack.org/wiki/Meetings/Swift"03:32
notmynamehttp://goo.gl/mtEv1C03:32
notmynamezhengyin: don't worry about making review "mistakes". it's not even possible to be a mistake to write down your thoughts on a patch03:33
zhengyinnotmyname: ok,  I will try my best to do it :)03:35
zhengyinnotmyname: thanks notmyname, I will have lunch now :)03:37
*** baojg has joined #openstack-swift03:43
*** baojg has quit IRC03:47
openstackgerritMerged openstack/python-swiftclient: Fix order of arguments in assertIs  https://review.openstack.org/36779804:06
jrichlinew versions of the docs will be released with this, right?  so it'd be good to have patch 35476704:09
patchbothttps://review.openstack.org/#/c/354767/ - swift - Corrections for the API specifications in api-ref04:09
notmynamejrichli: I'd assume those are built at every commit like the ones in doc/04:17
notmynamethat would be a good thing to check, actually04:17
notmynameanyone know the py3 version available in the gate? py34? py35?04:21
*** ppai has joined #openstack-swift04:22
mattoliveraunotmyname: depends on if you get a trusty or xenial cloud server04:26
mattoliverauI think04:26
mattoliverauor maybe it's all 3.5 and it either 3.5.1 or 3.5.2, I can't remember04:27
notmynamemattoliverau: in the context of the tox envs available, do you know?04:27
mattoliveraunot of the top of my head, would need to ask someone in infra, or call out to the infra guys who dont sleep :P .. clarkb?04:29
notmynameyeah, I asked in -infra too ;-)04:29
mattoliverausigh debugging my first attempt at read only container while sharding. Meaning while in sharding state have 2 sqlite containers, and have one node as the pivot point scanner as to get the pivot points as fast as possible to redirect ingress traffic faster and get to the ideal state faster....04:32
mattoliverauand boy, what was I on when I wrote some of this :P04:33
* mattoliverau reworks the sharder yet again04:33
notmynamemattoliverau: did you see the thing clayg posted earlier (IIRC) that was about remote sqlite DBs?04:34
notmynamemattoliverau: "2016-09-07_freenode.txt:11:08 clayg: mattoliverau: holy crap!  https://www.sqlite.org/lang_attach.html  <- from sqlite ML - you can tie two databases together so you can inserting into kind of statements?  pretty wild"04:37
mattoliverauyup, it looks pretty good, book marked it and will give a more detailed look soon, but is based of table names, so you'd need to use different table names in the two.. not that that's nessarily bad.04:38
mattoliverauthe idea is to only have the tables you need in the new database, but at the moment I've making an entire new container db (with pivot tables). Cause it's easier and I need to track things like replication etc as I don't know how long sharding will take.04:39
notmynameso I haven't talked to him about it, but I would *love* to see kota_ working with you on the container sharding problem. if that happened, I think we could get something soon(-sh) in prod04:40
mattoliveraunotmyname: cool! that would be awesome, in any case, I'm just pushing ahead, will try and keep the trello board as up to date as possible. I want to have something that works (with the big database that isn't written to) and see how much better it performs.04:42
mattoliverau^ by/before barcelona04:42
notmynamemattoliverau: I'd love to see sharding in the Ocata release. :-)04:44
openstackgerritMerged openstack/swift-bench: Remove support for py33/py26  https://review.openstack.org/26448604:45
notmynamewow. swift-bench patches merge so quickly04:45
notmynamedozens of seconds, tops.04:45
*** psachin has joined #openstack-swift04:47
mattoliveraulol, I'm sure we have a bunch of tests there :)04:47
mattoliveraunotmyname: I'd love to see it merged.. then I can pick some new feature to work on :)04:48
notmynamehonestly, the think I hate most about swift-bench is that is shines a light on how painfully slow it is to get patches to swift merged.04:48
notmynamemattoliverau: I've got a list. ;-)04:49
mattoliverauit would be good to get more/another eye on the sharding POC, that I hope will be turned in to code... it's gone through so many POCs there is probably cruft from old things that don't need to be done any more.. I try and start from a clean slate each time, but I do get lazy and still finding stiff :P04:50
notmynamepatch 162243 would be nice to land this week04:50
patchbothttps://review.openstack.org/#/c/162243/ - swift - Make object creation more atomic in Linux04:50
mattoliverau+104:52
notmynamemattoliverau: oh was that you echoing what you left in gerrit? ;-)04:52
mattoliveraulol04:52
mattoliveraunotmyname: I keep getting distracted, I'll try and play with it again this week :)04:53
notmynameacoles_: I'd love to see https://review.openstack.org/#/c/215276/ land this week to be in the release, but it's got a -1 from kota_. what do you think about it?04:53
patchbotpatch 215276 - swift - Enable object server to return non-durable data04:53
notmynamemattoliverau: getting close to release time. no time to be distracted ;-)04:53
notmynamemattoliverau: actually, yeah. reviewing that would be more important than container sharding this week04:53
mattoliveraukk :)04:54
notmynameis reedip banerjee online?05:00
*** Jeffrey4l has quit IRC05:00
*** Jeffrey4l has joined #openstack-swift05:00
jrichliprob doesn't have to be in next release, but a change that was talked about with ops way back in Vancouver is in patch 218490 - which is ready to review again05:02
patchbothttps://review.openstack.org/#/c/218490/ - swift - Automatic refresh of memcache config settings05:02
notmynameoh that hasn't landed yet? :-(05:03
notmynameoh. I'm the one who last gave it a -1. carry on05:03
*** chlong_ has quit IRC05:03
*** chlong has quit IRC05:03
jrichli:-)  but i think i addressed all that now05:03
notmynameacoles_ has marked https://review.openstack.org/#/c/348495/ as a critical bug (https://bugs.launchpad.net/swift/+bug/1605597). it affects prod, so it's an important one for the release05:06
openstackLaunchpad bug 1605597 in OpenStack Object Storage (swift) "container sync cannot copy SLOs" [Critical,In progress] - Assigned to Alistair Coles (alistair-coles)05:06
patchbotpatch 348495 - swift - Make container sync copy SLO manifests05:06
notmynameI'm turning in for the night. talk to you tomorrow05:15
notmynametomorrow my plan is to have the priority reviews wiki page updated05:15
*** chlong_ has joined #openstack-swift05:16
*** chlong has joined #openstack-swift05:20
*** chlong has quit IRC05:25
*** ppai has quit IRC05:26
*** tqtran has joined #openstack-swift05:33
*** rcernin has joined #openstack-swift05:33
*** tqtran has quit IRC05:37
zhengyinjrichli: hi, jrichli, do you have time to help me review a patch 355858? thanks :)05:43
patchbothttps://review.openstack.org/#/c/355858/ - swift - simplify code05:43
mattoliveraunotmyname: o/05:44
* mattoliverau sorry me went to make a new coffee and got sidetracked with a cute baby :)05:45
*** ppai has joined #openstack-swift05:52
*** ChubYann has quit IRC05:55
*** chsc has joined #openstack-swift05:55
*** chsc has quit IRC06:01
*** chlong_ has quit IRC06:05
mahaticclayg: just wanted to remind you on patch 346865, while it's still on your mind (somewhat ;)06:05
patchbothttps://review.openstack.org/#/c/346865/ - swift - Delete old tombstones06:05
mahaticof patch*06:06
*** chsc has joined #openstack-swift06:25
*** chsc has quit IRC06:30
*** pcaruana has joined #openstack-swift06:49
*** tesseract- has joined #openstack-swift07:00
*** rledisez has joined #openstack-swift07:06
*** hseipp has joined #openstack-swift07:25
*** tqtran has joined #openstack-swift07:34
*** tqtran has quit IRC07:38
*** oshritf has joined #openstack-swift07:42
*** sams-gleb has joined #openstack-swift07:53
*** asettle has joined #openstack-swift08:02
openstackgerritTuan Luong-Anh proposed openstack/swift: Use ConfigParser instead of SafeConfigParser  https://review.openstack.org/36861708:02
openstackgerritzheng yin proposed openstack/swift: Add test_long_names in the test_account and test_container  https://review.openstack.org/36862708:20
*** joeljwright has joined #openstack-swift08:34
*** ChanServ sets mode: +v joeljwright08:34
*** bikmak has joined #openstack-swift08:55
*** openstackgerrit has quit IRC09:04
*** openstackgerrit has joined #openstack-swift09:05
*** hoonetorg has joined #openstack-swift09:05
*** mingyu has joined #openstack-swift09:07
*** oshritf has quit IRC09:09
*** zhugaoxiao has quit IRC09:16
*** zhugaoxiao has joined #openstack-swift09:17
*** geaaru has joined #openstack-swift09:21
*** trananhkma has joined #openstack-swift09:21
*** tqtran has joined #openstack-swift09:35
*** tqtran has quit IRC09:40
*** mingyu_ has joined #openstack-swift09:44
*** mingyu has quit IRC09:46
*** mingyu has joined #openstack-swift09:59
zhengyinclayg: hi clayg, are you here?10:02
*** mingyu_ has quit IRC10:02
*** mingyu has quit IRC10:02
*** mingyu has joined #openstack-swift10:02
*** mingyu has quit IRC10:07
*** oshritf has joined #openstack-swift10:21
*** kei_yama has quit IRC10:22
*** psachin has quit IRC10:33
*** nikivi has joined #openstack-swift10:37
*** mingyu has joined #openstack-swift10:46
*** diogogmt_ has joined #openstack-swift10:52
*** diogogmt has quit IRC10:53
*** diogogmt_ is now known as diogogmt10:53
*** oshritf has quit IRC10:58
*** acoles_ is now known as acoles11:00
*** trananhkma has quit IRC11:01
*** hoonetorg has quit IRC11:03
acolesnotmyname: as it happens I planned to work on patch 215276 today - Kota has been rescuing it from merge conflict, IIRC it's needed for his Global EC work11:03
patchbothttps://review.openstack.org/#/c/215276/ - swift - Enable object server to return non-durable data11:03
*** silor has joined #openstack-swift11:08
*** mingyu has quit IRC11:09
*** cdelatte has joined #openstack-swift11:10
*** daemontool has joined #openstack-swift11:19
*** silor has quit IRC11:35
*** silor has joined #openstack-swift11:35
*** tqtran has joined #openstack-swift11:37
*** ppai has quit IRC11:38
*** silor has quit IRC11:39
*** silor has joined #openstack-swift11:40
*** tqtran has quit IRC11:41
*** silor1 has joined #openstack-swift11:43
*** silor has quit IRC11:44
*** silor1 is now known as silor11:44
*** bikmak has quit IRC11:45
*** ppai has joined #openstack-swift11:52
*** daemontool has quit IRC11:56
*** daemontool has joined #openstack-swift12:05
zhengyinclayg: hi, clayg. I have a patch 367825 to remove "TODO"  message that you left. I want to know you will add more tests or perhaps you forget to remove "TODO". thanks12:07
patchbothttps://review.openstack.org/#/c/367825/ - swift - delete TODO in test_manager12:07
*** psachin has joined #openstack-swift12:09
*** mingyu has joined #openstack-swift12:10
*** mingyu has quit IRC12:14
*** daemontool has quit IRC12:27
*** daemontool has joined #openstack-swift12:28
*** oshritf has joined #openstack-swift12:35
*** m_kazuhiro has quit IRC12:53
*** mingyu has joined #openstack-swift12:58
*** nikivi has quit IRC12:58
*** Jeffrey4l has quit IRC12:59
*** Jeffrey4l has joined #openstack-swift12:59
*** nikivi has joined #openstack-swift13:08
*** mingyu has quit IRC13:08
*** nikivi has quit IRC13:12
*** mingyu has joined #openstack-swift13:14
*** openstackgerrit has quit IRC13:19
*** openstackgerrit has joined #openstack-swift13:19
*** bikmak has joined #openstack-swift13:22
*** vint_bra has joined #openstack-swift13:32
*** gabor_antal_ has joined #openstack-swift13:34
*** gabor_antal has quit IRC13:34
*** klamath_ has joined #openstack-swift13:35
*** tqtran has joined #openstack-swift13:38
*** ppai has quit IRC13:41
*** tqtran has quit IRC13:43
*** psachin has quit IRC13:43
*** mingyu has quit IRC13:49
*** ametts has joined #openstack-swift13:54
*** lcurtis has quit IRC14:02
*** tongli has joined #openstack-swift14:03
*** bikmak has quit IRC14:13
*** bikmak has joined #openstack-swift14:14
*** kodoku has joined #openstack-swift14:16
kodokuHI, anyone use the module puppet swift for deploy ?14:20
*** bikmak has quit IRC14:24
*** dfg_ has joined #openstack-swift14:25
*** mingyu has joined #openstack-swift14:26
*** baojg has joined #openstack-swift14:27
*** bikmak has joined #openstack-swift14:28
*** ChanServ sets mode: +v tdasilva14:32
*** mvk has quit IRC14:37
*** hoonetorg has joined #openstack-swift14:38
*** bikmak has quit IRC14:43
*** _JZ_ has joined #openstack-swift14:43
*** bikmak has joined #openstack-swift14:45
*** Fin1te has joined #openstack-swift14:46
*** _JZ_ has quit IRC14:47
*** _JZ_ has joined #openstack-swift14:48
*** chsc has joined #openstack-swift14:53
*** mingyu has quit IRC15:05
*** mingyu has joined #openstack-swift15:06
*** daemontool_ has joined #openstack-swift15:07
*** daemontool has quit IRC15:10
*** zul has joined #openstack-swift15:12
*** chsc has quit IRC15:17
*** baojg has quit IRC15:20
*** dfg_ has quit IRC15:24
ntataGood Morning!15:26
*** oshritf has quit IRC15:28
acolesntata: good morning15:28
acoleskota_: I started work on your fanatastic review of optimistic GETs, but only part way through today. There are some mistakes form rebase i think, so I will fix and push a new version once I am finsihed.15:29
acolesfinished*15:29
kota_Thanks acoles! And sorry my bad rebase...15:30
*** sams-gleb has quit IRC15:34
*** Jeffrey4l has quit IRC15:35
acoleskota_: not your fault, just rebase collateral damage :)15:36
*** Jeffrey4l has joined #openstack-swift15:36
*** acoles is now known as acoles_15:37
*** tqtran has joined #openstack-swift15:40
*** thebloggu has joined #openstack-swift15:41
*** thebloggu has quit IRC15:43
*** nikivi has joined #openstack-swift15:43
*** tsg has joined #openstack-swift15:44
*** tqtran has quit IRC15:45
*** corvus is now known as jeblair15:50
*** rcernin has quit IRC15:53
*** pcaruana has quit IRC15:56
*** diogogmt has quit IRC15:57
notmynamegood morning16:00
*** tongli has quit IRC16:01
*** zul has quit IRC16:04
claygzhengyin: checking16:04
*** thumpba has joined #openstack-swift16:06
*** ChubYann has joined #openstack-swift16:08
*** daemontool_ has quit IRC16:09
*** daemontool has joined #openstack-swift16:10
*** dfg_ has joined #openstack-swift16:15
*** takashi has joined #openstack-swift16:15
*** diogogmt has joined #openstack-swift16:19
*** hseipp has quit IRC16:26
*** rledisez has quit IRC16:40
*** Fin1te has quit IRC16:42
*** dmorita has joined #openstack-swift16:45
*** ametts has quit IRC16:45
*** diogogmt has quit IRC16:47
notmynametdasilva: can you look at mattoliverau's comment on https://review.openstack.org/#/c/162243/ ?16:51
patchbotpatch 162243 - swift - Make object creation more atomic in Linux16:51
tdasilvanotmyname: I think ppai replied to mattoliverau's comment16:53
notmynameoh, ok ;-)16:53
*** hurricanerix has quit IRC16:53
notmynameah yes. I'd just seen the emails16:53
tdasilva:)16:54
*** hurricanerix has joined #openstack-swift16:54
notmynameok, so it looks likely that mattoliverau will change his vote when he wakes up. should see the patch land, then, for the release (yay!)16:55
*** tesseract- has quit IRC16:56
*** Suyi_ has joined #openstack-swift17:02
openstackgerritMerged openstack/swift: delete TODO in test_manager  https://review.openstack.org/36782517:14
*** joeljwright has quit IRC17:17
clayg^ phew, glad we got *that* taken care of17:18
*** diogogmt has joined #openstack-swift17:21
*** klrmn has joined #openstack-swift17:21
*** tqtran has joined #openstack-swift17:27
*** ukaynar has joined #openstack-swift17:27
notmynameclayg: now that we got the critical TODO deletion landed...17:29
notmynameclayg: can you take a look at https://review.openstack.org/#/c/348495/? acoles_ has it as a critical bug and it's affecting their prod17:30
patchbotpatch 348495 - swift - Make container sync copy SLO manifests17:30
claygYESSIR!17:31
notmynamethanks :-)17:31
pdardeauclayg: nice posting to ML!17:31
claygpdardeau: no no no - i'm pretty sure this is me -> http://66.media.tumblr.com/tumblr_m9yx3gTr9d1rzupqxo1_500.png17:33
*** asettle has quit IRC17:33
claygyou're comments on the review where *much* more helpful17:33
*** takashi has quit IRC17:34
claygI'm sure there's other contributors like me that feel compleatly illequipped to get involved in these soft mushy OpenStack debates - but it's not because we don't have an opinon on what it is we're supposed to be doing here - so while I maybe can't help review - i sure can vote!17:34
notmynamejrichli: you left a +1 on https://review.openstack.org/#/c/357559/. can you look at it again with an eye to giving it a +2, or do you need timburke to answer your question first?17:35
patchbotpatch 357559 - swift - Include metadata in PUT/POST responses17:35
tdasilvayeah, would be great to see that merged17:35
notmynametdasilva: yeah, why'd timburke add you as co-author? ;-)17:36
jrichliI did want to know Tim's thoughts on my last question17:36
timburkeah, right! yes, my thinking was that there would (eventually) be similar patches for accounts/containers17:37
timburkenotmyname: i could always drop tdasilva... :P17:37
jrichliok.  I jsut wanted to be sure we had thought about whether or not a consistent approach would be ok for acct/cont17:37
jrichlitimburke: no need for that!  I will +2 in a bit17:38
timburkei haven't thought very *deeply* about it, but it seems like it should work fine (provided we document some caveats about eventual consistency and all that)17:38
tdasilvatimburke: i'm actually looking at patch 347538 atm :)17:39
patchbothttps://review.openstack.org/#/c/347538/ - swift - Store SLO Etag and size in sysmeta17:39
timburkeyay!17:40
tdasilvatimburke: at first I thought you were also changing the way the etag is calculated, as in, being the real etag, but no way around that yet17:43
claygacoles_: reading the bug report and commit message for patch 34849517:44
patchbothttps://review.openstack.org/#/c/348495/ - swift - Make container sync copy SLO manifests17:44
timburketdasilva: no there is not :-( although i had some crazy idea a few weeks ago that might let me store an honest-to-god Content-MD5 if you trust your upload connection enough17:45
claygnot sure I agree with the assumption that the destination cluster need not validate the sending clusters manifest - while I think container sync realms supposes some co-ordination between the two clusters they may have different operators on different release/upgrade schedules - i'm not sure exactly how much trust and conformity is really expected and required (lack of experience on my part)17:45
timburkealthough it would require a single connection and, as oxinabox noticed, that'll kill throughput17:46
timburketrade-offs. all about trade-offs17:46
claygacoles_: but secondly, unlike DLO - i'm not sure it's sufficient to sync the manifest before the targeted segments have been sent - obviously in the ideal the slo manifest would exist in the destination iff it's complete and validated in the destination cluster17:47
notmynametimburke: your comment ("...if you trust your upload connection") reminds me of number 1: https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing17:47
claygain't no body wants to give up all that throughput just for checksums17:48
claygacoles_: I think the minimum thing we might be able to get away with is to not have cotainer sync progress halt when it hits a SLO (or any other object that is rejected by the remote cluster's validation for whatever reason?)17:49
*** nikivi has quit IRC17:49
claygnotmyname: did we ever get anything like per-policy constraints?17:50
notmynameclayg: not yet17:50
*** zul has joined #openstack-swift17:50
timburkenotmyname: hey, sometimes you're willing to accept that the object stopped abruptly. the particular use-case that made me think of it was streaming surveillance video -- i have an indefinite amount of data i want to store and i want to minimize my buffering. if the connection drops, w/e, i'll start another one17:50
timburkeclayg: having a useful checksum was just a bonus17:51
*** dfg_ has quit IRC18:04
*** chsc has joined #openstack-swift18:05
claygacoles_: ok, the 409 seems reasonable....18:06
*** Fin1te has joined #openstack-swift18:13
*** nikivi has joined #openstack-swift18:14
*** dmorita has quit IRC18:15
*** dmorita has joined #openstack-swift18:16
*** vinsh has joined #openstack-swift18:17
*** nikivi has quit IRC18:24
*** ukaynar has quit IRC18:26
*** dmorita has quit IRC18:30
notmynamehttps://wiki.openstack.org/wiki/Swift/PriorityReviews has been updated with review priorities for 2.10.018:32
tdasilvanotmyname: are you maintaining that list or is it ok to add there?18:33
notmynamewell, it's a big list already, and based on what has been brought up before. I'd prefer that you coordinate with me before updating it18:34
*** dmorita has joined #openstack-swift18:36
tdasilvanotmyname: ok18:36
tdasilvanotmyname: was hoping patch 361439 would make the cut18:37
patchbothttps://review.openstack.org/#/c/361439/ - swift - Add option to set default version mode18:37
*** dmorita has quit IRC18:39
*** dmorita_ has joined #openstack-swift18:39
jrichlitdasilva: I have held off on that one because clayg gave a convincing argument that the default should remain with past behavior.  At least, that was my take form the discussion.18:40
tdasilvajrichli: oh, I'm not changing the default at al18:40
tdasilvajrichli: the patch only provides the option for operators to change the default if they choose too18:41
claygyeah but you're giving cluster operators the option of changing the default when the mode is underspecified18:41
tdasilvaclayg: correct18:41
claygyeah, i'm pretty sure that's actively hostile to apps that want to make use of swift's versioning18:42
claygand they've already suffered enough18:42
tdasilvaclayg: for current apps, nothing changes (as long as operators don't change anything). This change is geared towards new installations where ideally new apps would not even know about stack mode18:43
claygx-versions-location should die in a fire, x-history-container and x-stack-container FTW!18:43
jrichliyes, that is what I had taken from clayg said before.  that we shouldnt even provide the option.  His reasoning showed me how this is a different case than other configuragbles we add in later18:43
clayg"as long as operators don't change anything" is the worst pre-req for adding an operator tunable in the world!18:43
clayghere's a knob - DO NOT TOUCH IT EVAR18:44
tdasilvait's not DO NOT touch, it's you should know what you are doing and what your users want18:44
tdasilva"openstack for operators and operators for users" ;-)18:44
claygtdasilva: i don't out-right reject that it's *possible* for swift clusters to exist in isolation - but I would like it not to be the expectation that "only apps written after the deployment of this cluster will be used with this cluster"18:44
jrichlii think its more about the fact that the change is visible to the client's actions18:45
claygtdasilva: I think it's a bandaid for us writing a weird/bad bi-modal api18:45
claygyes, we don't want users to have to say x-versions-location AND x-version-mode - that's not great18:45
claygno, we don't want users to not know what they get if they DON'T set x-version-mode18:45
claygwe would prefer they set x-version-history-container and x-version-stack-container and always know what they get18:46
clayg(and hope they never choose x-version-stack-container because they are not mad men)18:46
tdasilvaso you propose yet a new api?18:46
tdasilvathis reminds of a xkcd i saw somewhere18:47
claygi don't think the current one is released - but yes - I think the x-version-mode is weird/bad - it might make sense at the data model layer - and i'm not against leaving the internals exposed - but the one we should document and advertise should look like you're picking between two different things by setting two different things (not by flipping a mode on an old bad crufty thing)18:48
timburketdasilva: or for that matter, one of my comments on https://review.openstack.org/#/c/347538/ -- "I was getting annoyed at needing to send the same value twice, so I found a way to send it three times instead >_<"18:48
patchbotpatch 347538 - swift - Store SLO Etag and size in sysmeta18:48
claygI think the data model is acctually nice - if we had a layer that *just* turned x-version-stack-container and x-version-history-container into the always setting of the two backend flags if you try to change between one or the two it might always overwrite it?18:48
claygtimburke: tdasilva: ok, perhaps I'm in the minority with this mode flag being cumbersome - but I think that fact that tdasilva is suggesting we have a operator tunable to change it smells like I'm not the only one?18:50
claygI would rather it stay as is than expose the tunable tho - i'd be happy to say as much as on the review - but I didn't think that's as helpful as suggesting an alternative path forward - but if no one likes it... maybe i'm better to keep my mouth shut :D18:51
timburkeclayg: i'm actually rather OK with your suggestion -- this thing behaves in two rather different ways; send one of two rather different headers, and error out if you send both18:52
tdasilvaclayg: i don't disagree with it being cumbersome, i just wish we had had this conversation before, so that we wouldn't have to fix it now18:52
claygtdasilva: sorry - i kept meaning to look at it - but it seemed stalled - then by the time it was unblocked it was merged18:53
claygtdasilva: totally unfair for me to complain about it now - but here we are!18:53
tdasilvaclayg: no worries and it is not your fault, i think this was one of those features that actually got very little eyes on it18:54
claygeither way - the more I think the data model the more I think this is just syntactic sugar - i'm sure it'll be easy to gloss up later18:54
timburketdasilva: sounds like versioned_writes all right ;-)18:54
tdasilvalol18:55
*** Fin1te has quit IRC18:56
claygtimburke: tdasilva: so is there something that needs to happen in this release - or is there additional debate - or is the operator default config option useful in addition to any future syntax/ux work?18:56
timburkeclayg: if we get the sugar in this release, we never have to support a user-toggle-able x-versions-mode18:57
jrichlitimburke: so,  ... you already have it working and just need to write the tests, am I right?18:58
timburkelol i'm gonna need more coffee...18:58
claygtimburke: well based on the data model i'm not sure that x-versions-location and x-versions-mode wouldn't always be exposed - with the other two headers as an alias to explictly set them both with one flag?19:00
*** zul has quit IRC19:00
claygwell, i guess we always need to expose x-versions-location - so the question is just about if we continue to persist x-version-history-container as x-versions-location + x-versions-mode19:01
clayg... I kinda still think that's a reasonable model - I don't want to have x-versions-location and x-version-history-container both written down because of some eventual consistency bullshit19:01
*** Fin1te has joined #openstack-swift19:03
*** pcaruana has joined #openstack-swift19:04
tdasilvaclayg: not sure about this release, but i'd almost prefer we take a step back and think the design a bit more. For example, another possibility would be to start from scratch with this a new middleware that uses symlinks19:06
*** tongli has joined #openstack-swift19:06
*** silor has quit IRC19:11
*** asettle has joined #openstack-swift19:14
claygacoles_: so this slo change is surprinsgly small for all the test doc changes you did to make it look big and scary19:19
*** asettle has quit IRC19:26
*** asettle has joined #openstack-swift19:28
*** asettle has quit IRC19:28
openstackgerritMerged openstack/swift: Include correct version in install-guide  https://review.openstack.org/36393819:28
*** asettle has joined #openstack-swift19:28
*** CaioBrentano has joined #openstack-swift19:29
*** hseipp has joined #openstack-swift19:30
CaioBrentanoHi all!! I set weight zero to a device, but it still has some partitions. How is that possible?19:32
glangepartitions on disk?19:32
claygon the disk or assigned in the ring?19:32
*** asettle has quit IRC19:33
claygi guess I could imagine duplicate part assignment on a disk leading to only picking up one part-replica off the disk in the first pass19:33
*** asettle has joined #openstack-swift19:33
jrichliasettle: howdy.  we are preparing for our Newton release.  patch 354767 makes some big improvements on the api-ref.  Are those docs built at every commit like the ones in doc/ ?19:33
patchbothttps://review.openstack.org/#/c/354767/ - swift - Corrections for the API specifications in api-ref19:33
claygfailing the disk would be an option - but if you drain it - probably just doing a second cycle rebalance would be great19:33
claygCaioBrentano: ^^19:34
CaioBrentanoclayg: both! the partitions are assigned in the ring... and the disk still has objects19:36
*** Fin1te has quit IRC19:36
*** StraubTW has joined #openstack-swift19:38
CaioBrentanoclayg: I set weight zero because I want to remove these disks...19:38
*** asettle has quit IRC19:38
claygnotmyname: I sorta think that lp bug #1580678 was fixed by cschwede somewhere along the way?19:38
openstackLaunchpad bug 1580678 in OpenStack Object Storage (swift) "UnicodeDecodeError when rebalancing a ring" [High,In progress] https://launchpad.net/bugs/1580678 - Assigned to Christian Schwede (cschwede)19:38
claygCaioBrentano: so pushing out the rings with the parts unassigned will let the devices drain what they can19:39
*** Guest22444 has joined #openstack-swift19:39
CaioBrentanoclayg: nice! thanks!19:39
claygCaioBrentano: after a replication cycle the devices on the disk should match what's assigned in the ring (which I could imagine might be non-zero iff those parts were already reassigned this min_part_hours)19:39
claygthen for the few remaining parts - you can either wait min_part_hours and rebalance and push again with 0 parts assigned19:40
claygor you could fail the devices - the parts will immediately be reassigned and back filled from the other replicas - but the deleted device will not drain it's parts from the disk - the replicator on that node will simply ignore the deleted device and the parts that are on it19:41
CaioBrentanoclayg: how could this "duplicate part assignment" happen?19:42
Guest22444exit19:44
*** Guest22444 has quit IRC19:44
claygCaioBrentano: old builer codef used to be stupid -> lp bug #145243119:45
openstackLaunchpad bug 1452431 in OpenStack Object Storage (swift) "some parts replicas assigned to duplicate devices in the ring" [High,Fix released] https://launchpad.net/bugs/1452431 - Assigned to Samuel Merritt (torgomatic)19:45
claygCaioBrentano: although, it may not have been that bug specifically depending on your cluster topology - I think the same issue would come up if you had two part-replicas assigned to the same server/zone and you set both of those devices to zero weight in the same pass19:45
claygwhich really - is the desired behavior19:46
notmynameclayg: maybe cschwede fixed that bug at some point. would be good to get confirmation. but you could be thinking of https://bugs.launchpad.net/swift/+bug/1597210 (linked from the bottom of the first one)19:46
openstackLaunchpad bug 1597210 in OpenStack Object Storage (swift) "Downed object-server during a PUT with unicode characters causes UnicodeDecodeError and 500 status code" [Critical,Fix released] - Assigned to Brian Cline (briancline)19:46
CaioBrentanoclayg: thanks!19:49
hogepodgenotmyname: I'm going to ping you on this again, just because I got pinged on it again. https://review.openstack.org/#/c/324739/519:49
patchbotpatch 324739 - python-swiftclient - Insufficent info about read and write ACL syntax19:49
*** hseipp has quit IRC19:50
hogepodgenotmyname: A decision on how to fix the inline docs would be nice. I'm not too invested in how the decision lands, just that there is one.19:50
notmynamehogepodge: I'll need to refamiliarize myself with the question :-)19:50
notmynamehogepodge: ah yes. you have a test or something that is based on docs, and the docs aren't actually how it works19:51
hogepodgenotmyname: tempauth and keystone auth have different ACL syntax. python-swiftclient assumes tempauth19:51
hogepodgenotmyname: yeah, if there's documentation somewhere online that points to how keystone auth does it, that would work for me too. We could link to it and call the job done19:52
notmynamehogepodge: rereading the comments, acoles_ seems to have the right idea--as normal ;-)19:53
notmynamehogepodge: how would you feel about the references to v1 auth api vs non-v1 api?19:53
claygnotmyname: I can't place it - I tought Al fixed something too - there's this one -> https://review.openstack.org/#/c/339360/119:53
patchbotpatch 339360 - swift - Make verbose unicode test output working19:53
notmynamemmotiani: ping. we're talking about your patch 32473919:53
patchbothttps://review.openstack.org/#/c/324739/ - python-swiftclient - Insufficent info about read and write ACL syntax19:53
notmynameclayg: the common theme here is that you keep linking stuff you've put a -1 on ;-)19:54
clayghrm... that doesn't sound so helpful :\19:54
*** zul has joined #openstack-swift19:54
*** Guess456787654 has joined #openstack-swift19:55
claygnotmyname: no look!  i'm helping -> https://review.openstack.org/#/c/338950/19:55
patchbotpatch 338950 - swift - Fix unicode errors in object controller logging (MERGED)19:55
notmynamelol19:55
hogepodgenotmyname: I'm not sure it would clear things up for our target audience. the first thing I'd ask myself was "am I running v1 or non v1?" and then shrug my shoulders19:55
notmynamehogepodge: yeah, but you've got that issue anyway with v2 vs v319:56
MooingLemurif a DELETE on an object only succeeds on one replica, does the client get a 204?19:56
notmynamehogepodge: and I strongly suspect most people shrug and walk away when confronted with that19:56
claygonly *one* - might depend on the result of the other backend requests19:56
notmynameMooingLemur: no. same quorum rules apply to DELETEs as PUTs19:56
hogepodgenotmyname: if I hear19:56
claygnotmyname: MooingLemur: wheeeeelll - except that a backend 404 on DELETE can count towards the q of 204's because the result is the same19:57
claygor something19:57
claygmattoliverau: wrote it19:57
hogepodgenotmyname: keystone vs tempauth, I have a much better chance of saying "It's a keystone system! I know this!"19:57
claygI also think mattoliverau was working on the unicode business19:57
MooingLemurnotmyname: so if it's 404, 204, 404, (404s on handoffs) client'll get what?19:57
notmynameclayg: ah yes. 404 counts as a 2xx for DELETEs19:57
* hogepodge makes oblique jurrasic park reference...19:57
MooingLemuraha, alrighty19:57
MooingLemurbut if all backends return 404, client gets 40419:58
notmynamehogepodge: oooo. can we get 3D models of the cloud to fly over?19:58
claygyeah, maybe a single 204 can make the client see success... that probably makes sense19:58
hogepodgenotmyname: horizon doesn't provide that?19:59
notmynamehogepodge: definitely a missing feature. you can add that to defcore, right? ;-)19:59
*** daemontool has quit IRC19:59
*** tongli has quit IRC20:01
*** MVenesio has joined #openstack-swift20:04
*** tongli has joined #openstack-swift20:07
*** tongli has quit IRC20:12
*** tongli has joined #openstack-swift20:13
torgomaticclayg: can you take a look at patch 344898 when you get a second? I want to make sure I'm saying reasonable things in the review comments.20:15
patchbothttps://review.openstack.org/#/c/344898/ - swift - add dev_losing_part['parts_wanted'] += 120:15
17SAA00LAnotmyname: I am still trying to figure that out. Currently, I am looking at the integration of swift with keystoneauth to see how it works20:16
claygtorgomatic: if you're -1 I probably agree ;)20:16
notmyname17SAA00LA: mmotiani?20:16
17SAA00LAYup.20:16
17SAA00LAOh wait20:16
17SAA00LAwhats that20:17
notmyname17SAA00LA: /nick might help :-)20:17
17SAA00LAI don't understand why is it some random nick. Sorry about that20:19
notmyname17SAA00LA: what part are you still trying to figure out wrt the ACL syntax docs?20:19
claygtorgomatic: so what you're saying there makes sense to me - and I don't understand what exactly Cheng Li is after with his change (beyond what it claims - which is "this changed the code to do the thing I said the code should say"20:20
claygtorgomatic: but looking at the linked lp bug #1605841 - it *seems* like he's trying to address some issue?20:20
openstackLaunchpad bug 1605841 in OpenStack Object Storage (swift) "add dev_losing_part['parts_wanted'] += 1" [Undecided,In progress] https://launchpad.net/bugs/1605841 - Assigned to Cheng Li (shcli)20:20
claygReassigned 128 (50.00%) partitions vs Reassigned 9 (3.52%) partitions after 3.5 -> 3.020:21
torgomaticclayg: yeah, there's something going on in there, but I'm not entirely sure what it is20:21
17SAA00LAnotmyname: to check acl syntax doc, I was trying to setup swift with keystoneauth instead of tempauth. I am currently stuck at the client side authentication with keystoneauth20:21
clayghe also claims that balance gets better20:21
torgomaticclayg: yeah, so maybe the trick is to call set_parts_wanted *after* fiddling with the replica counts?20:23
*** thumpba has quit IRC20:27
jrichlitimburke: thanks for the review on memcache reload!20:27
*** d0ugal has quit IRC20:28
timburkejrichli: sure! the exception handling is the big thing for me; i don't see any reason to fail the request when trying to reload a bad config20:28
*** thumpba has joined #openstack-swift20:29
jrichlitimburke: ok, that sounds like something i can be on board with.  i hope to get to this soon, but it seems my list has just grown over the last few days.20:30
claygtorgomatic: lol - i just said as much on the review20:31
claygtorgomatic: I think we also need to true up our goals and problem statement on the bug report20:31
claygtorgomatic: thanks for reminding me about that20:31
clayg... that patch20:31
torgomaticclayg: phew! that means that it's not completely nuts ;)20:31
claygtorgomatic: no sir you are not!20:31
claygtorgomatic: do you have any good jokes about working on the ring and riding a bike?20:32
torgomaticclayg: that's a very specific thing to joke about; nothing comes to mind. I'll let you know. :)20:36
claygtorgomatic: I don't get it20:37
claygtorgomatic: how about working on the ring is like riding a bike - it's hard to balance - and hurts if you're not careful?20:38
* torgomatic will take it20:38
*** tongli has quit IRC20:39
timburkesomething something velodrome?20:39
claygtimburke: I was trying to get at despire torgomatic20:40
clayg... torgomatic's recent efforts he has *not* forgotten how the ring works ;)20:41
claygoh, *despite even20:41
*** MVenesio has quit IRC20:43
*** d0ugal has joined #openstack-swift20:44
*** pcaruana has quit IRC20:46
openstackgerritMerged openstack/swift: Apply go fmt to tempauth  https://review.openstack.org/36768520:46
claygtimburke: do all the filesystem api's in py3 return unicode?  e.g. os.listdir?20:47
timburkeiirc, yes20:47
claygdo they have any opinion about byte strings from the disk that it can't seem to convert to unicode based on the default locale?  I think there's like a "substitute" mechanic?20:48
timburkeyup; look for "surrogateescape"20:48
timburkehttps://www.python.org/dev/peps/pep-0383/20:48
*** mvk has joined #openstack-swift21:07
openstackgerritTim Burke proposed openstack/swift: Store SLO Etag and size in sysmeta  https://review.openstack.org/34753821:24
*** Guess456787654 has quit IRC21:34
*** vint_bra has quit IRC21:34
claygi love computers *so* much -> "Emit a malformed UTF-16 sequence for every byte in a malformed UTF-8 sequence"  -- the clear RightThingToDo[TM]21:37
*** thumpba has quit IRC21:49
*** CaioBrentano has quit IRC21:56
openstackgerritTim Burke proposed openstack/swift: Bring "egregious range request" comment in line with reality  https://review.openstack.org/36906022:06
*** zigo has quit IRC22:08
*** zigo has joined #openstack-swift22:11
*** zigo is now known as Guest4138822:11
pdardeauclayg: that's where your image is appropriate - http://66.media.tumblr.com/tumblr_m9yx3gTr9d1rzupqxo1_500.png22:13
*** cebruns__ has quit IRC22:13
*** cebruns has joined #openstack-swift22:15
*** Guest41388 is now known as zigo_22:17
*** cebruns has quit IRC22:19
*** thumpba has joined #openstack-swift22:19
*** cebruns has joined #openstack-swift22:21
*** StraubTW has quit IRC22:21
claygpdardeau: not at all - I think you made a genuine contribution to that discussion on that patch and elicited meaningful discourse - nice work!22:22
*** cebruns has quit IRC22:22
pdardeauclayg: thx, but i was referring to your comment about the malformed utf sequence22:23
claygoh - rofl22:24
*** thumpba has quit IRC22:24
claygyeah, idk, there was a somewhat convincing argument in that spec for the byte smuggling surrogateescape strategy!22:24
clayggah "spec" :'(22:25
claygpep22:25
*** cebruns has joined #openstack-swift22:29
*** vint_bra has joined #openstack-swift22:34
timburkehuh. anyone else see this? POST response under fast-post includes an HTML body, but with post-as-copy, there's no body22:40
*** cebruns has quit IRC22:41
*** cebruns has joined #openstack-swift22:42
mattoliveraumorning22:43
claygtimburke: who runs past-as-copy!?22:45
timburkeclayg: my old, janky saio? customers that haven't been watching the release notes with bated breath?22:47
claygtimburke: anyway - confirmed22:47
claygdo you think it's a regression or just an old difference that no one had previously thought to care about?22:48
claygalso it's weird22:48
timburkeno idea. do we have a preference for which way it should behave?22:48
claygi get 202 accepted in both cases22:48
timburkeyup, me too22:48
*** openstackgerrit has quit IRC22:48
claygi'm guessing best_response cooks up the 202 from a collection of the backends on fast-post and probably post-as-copy does something to translate the 201 into a 202 and has always done the wrong thing?22:48
*** openstackgerrit has joined #openstack-swift22:49
timburkei think it might be vaguely related to the swob changes torgomatic has in https://review.openstack.org/#/c/352657/ ?22:50
patchbotpatch 352657 - swift - Support multi-range GETs for static large objects.22:50
claygtimburke: but i'm seeing the difference in behavior on an unrelated change - and that isn't merged?  does that change *fix* it!?22:51
claygi'm not sure where the copy middleware is translating the 201 from the put response into a 202 on post-as-copy?22:52
timburkeit fixes a similar problem that was happening during 416 responses for SLOs22:52
claygoh, _adjust_put_response22:52
timburkeyeah, was just about to send a link to https://github.com/openstack/swift/blob/2.9.0/swift/common/middleware/copy.py#L24922:53
torgomaticthat patch shouldn't affect this; the swob changes there are guarded by "if ranges == []" in range handling; POST shouldn't get anywhere near that code22:53
claygso it might even be *weirder* if 201 returned a body?22:53
timburketorgomatic: i said *vaguely* related :P22:54
timburkeclayg: almost certainly22:54
claygtimburke: ok, so when you file the bug - it'd be great if you could see if the difference existed before the copy middleware extraction22:55
timburkei wonder if we maybe *used to* include a body on PUT? looking at http://developer.openstack.org/api-ref/object-storage/index.html?expanded=create-or-replace-object-detail the example response has `Content-Length: 116` (but no actual body)22:56
timburkealso, we somehow managed to include an example that 408s :-/22:57
claygtimburke: idk :\22:57
*** vint_bra has quit IRC22:59
timburkeugh, and we claim that Date and Last-Modified will look like CCYY-MM-DDThh:mm:ss±hh:mm :-(23:06
timburkehurray for donagh! https://review.openstack.org/#/c/354767/12/api-ref/source/parameters.yaml23:07
patchbotpatch 354767 - swift - Corrections for the API specifications in api-ref23:07
clayghooray for donagh!23:08
*** _JZ_ has quit IRC23:09
*** klamath_ has quit IRC23:13
openstackgerritTim Burke proposed openstack/swift: Include metadata in PUT/POST responses  https://review.openstack.org/35755923:14
*** cebruns has quit IRC23:16
*** cebruns has joined #openstack-swift23:19
*** Guess456787654 has joined #openstack-swift23:22
*** cebruns has quit IRC23:27
*** zul has quit IRC23:28
*** cebruns has joined #openstack-swift23:30
*** kei_yama has joined #openstack-swift23:30
*** tsg has quit IRC23:38
*** Jeffrey4l has quit IRC23:43
*** Jeffrey4l has joined #openstack-swift23:43
*** Guess456787654 has quit IRC23:46

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