Friday, 2016-09-16

*** Suyi_ has quit IRC00:06
*** tqtran has quit IRC00:22
*** asettle has joined #openstack-swift00:23
*** asettle has quit IRC00:28
*** thumpba has quit IRC00:29
timburkeoh yeah, i nearly forgot about https://review.openstack.org/#/c/331369/00:41
patchbotpatch 331369 - swift - Always set swift processes to use UTC00:41
timburkewhat a headache that was to hunt down!00:41
claygdo you have a bug report?00:42
timburkehadn't bothered. apparently no one else uses email.utils.mktime_tz on pre-2.7.4 python? (what suckers!)00:43
clayglike it's a great story reading the commit message - but I have no idea how to duplicate the bad and validate this patch fixes it?00:44
claygwas the problem inthe response headers?  the logging?00:44
claygis it purly a belts and braces correctness thing (those are good too!)00:44
claygawesome - and the tests just validate that the code calls the method that it was changed to call ;)00:45
clayg*you* probably don't even remember :P00:45
claygmaybe you do - you've got a better memeory than the rest of us :P00:45
timburkeclayg: the problem was in parsing a client-provided date header. you'll want a precise saio and some custom middleware...00:45
claygrofl - no i definately do not want that :D00:46
claygbut it would be nice to understand the pre-req to review the patch - maybe comments? nope... how do you remember why this patch exists?!  did you write down - am i missing it?  Do you really have that good of a memory!?00:47
timburkeeven if the test actually described the problem, you'd need some old python to make it fail before the patch. probably better to view it as a belt & braces-style patch00:47
timburkeclayg: there's the other patch! https://review.openstack.org/#/c/330888/00:51
patchbotpatch 330888 - swift3 - Stop using email.utils.mktime_tz00:51
claygtimburke: so it *is* just a belts and braces thing?  or it would be if the swift3 thing got merged?00:52
claygtimburke: oh i guess anyone calling email.utils.mktime_tz from middleware would get the weird/mixed results on precise python?00:53
timburkethe second one. also, it'll save anyone who writes some custom middleware that... yeah00:53
claygtimburke: so it's probably not outside of the relam of possibility to write a unittest that would fail before your change on oldish-precise-python then yeah?00:54
*** m_kazuhiro has joined #openstack-swift00:55
claygeven if only one other person verifies it fails one time - it'd still probably be helpful to read the asserts and understand what the failure mode looks like then00:55
*** thumpba has joined #openstack-swift00:55
clayg"w/o this change this stdlib function call breaks on old python because of stuff you do in process init" seems like more than belts and braces - it's a sound fix for a terrible weird edge case that I'm sure was annoying to track down!00:56
*** gyee has quit IRC00:56
timburkeplus i'm sure there are some lurking pitfalls (in god-knows where) to do with that crazy tz-schizophrenia we've got going on00:56
clayg:'(00:57
*** asettle has joined #openstack-swift00:57
timburkei'll see what i can do to make the tests a little more useful00:57
pdardeauclayg: timburke: when you guys say "old" python, how far back is that? 2.6.x?00:58
timburkepdardeau: 2.7.3, like precise ships00:59
claygis the '+0000' format that we stick into TZ from the gmtime call just like stright up wrong?  the UTC+0 format seems to make the time.tzname attr more better?01:00
claygtimburke: like i'm not sure I buy the os.environ change at all?  sigh01:01
*** asettle has quit IRC01:01
claygportante: ^ *you* should review this TZ nonsense when timburke gets done figuring it out :P01:01
timburkeclayg: that's how you change TZ, though -- https://docs.python.org/2/library/time.html#time.tzset01:02
timburke"The environment variable TZ specifies how this is done."01:02
claygtimburke: you should link to those docs in the updated change/bug report01:04
timburkei did! it was footnote 3!01:04
*** neha__ has quit IRC01:05
claygFurther, while we would change os.environ['TZ'], we would *not* call01:05
claygtime.tzset [3], which seems like a Bad Thing01:05
clayginstead say "like it says in the docs [3]"01:05
claygIMHO - sorry I missed it01:05
claygalso the *3rd* footnote reminds me of http://blog.equalrightsinstitute.com/wp-content/uploads/2015/06/IM.png01:07
kota_good morning01:08
timburkeclayg: ok, you wanna see the bad? `python -c 'import os, time; print "Before:\n  %s\n  %s\n  %s\n" % (time.gmtime(0).tm_year, time.localtime(0).tm_year, time.timezone); os.environ["TZ"] = "+0000"; print "After:\n  %s\n  %s\n  %s\n" % (time.gmtime(0).tm_year, time.localtime(0).tm_year, time.timezone)'`01:14
timburkei think i can make a unittest out of that...01:14
claygtimburke: yeah I mean I was really just trying to understand the problem - sometimes the unittests make it obvious what was broke - but in this case the unitests were not the answer - talkig with you about it was01:18
clayg... sort of - i mean - I guess the weird internal state of the time module getting out of whack with the env it somewhat easy to understand as wrong01:18
claygin that light I think doing what the docs say is a pretty clear win?01:19
claygI think that as long as your system was already configured for that timezone the change should have basically no effect?01:19
claygpresumably the time module calls tzset once when it's started - and it's only when the TZ environ is modified during runtime that this matters?01:20
claygtimburke: maybe we should just do it earlier and import time later?01:20
clayg... well i'm fine with tzset too if that's the only problem - how does this only effect old python tho?01:20
timburkenope, this (may) affect current python code, too. swift3's use of mktime_tz was only bad on old python, though01:22
clayginteresting..01:22
timburkeso the unittest i eventually write (demonstrating the time module getting out of whack) will pop on modern platforms01:22
claygtimburke: cool!01:23
claygtake that swift process initilization code!  no more screwing up stdlib module internal state for you!~01:23
*** vinsh has joined #openstack-swift01:24
claygtimburke: I wonder if when portante added that the time module was being initialized at a diffent time in the process lifetype and somehow maybe this was just a regression or if this never really worked right?01:24
*** _JZ__ has joined #openstack-swift01:27
timburkewell, it certainly did what we wanted it to do (stop stat'ing /etc/blahblahblah all the time), and since we generally recommend running in UTC anyway (makes merging log files *so* much easier) i'm guessing no one really noticed01:29
*** _JZ___ has joined #openstack-swift01:30
*** _JZ_ has quit IRC01:30
*** _JZ__ has quit IRC01:33
*** _JZ___ has quit IRC01:36
*** tsg has joined #openstack-swift01:45
*** _JZ_ has joined #openstack-swift01:49
*** mingyu has joined #openstack-swift01:54
*** ANTI-torture has joined #openstack-swift01:56
*** ANTI-torture has quit IRC02:02
*** manous has quit IRC02:05
*** _JZ_ has quit IRC02:07
*** _JZ_ has joined #openstack-swift02:07
openstackgerritTim Burke proposed openstack/swift: Always set swift processes to use UTC  https://review.openstack.org/33136902:08
*** thumpba has quit IRC02:08
*** mingyu_ has joined #openstack-swift02:09
*** mingyu has quit IRC02:09
*** tsg has quit IRC02:10
*** Jeffrey4l has quit IRC02:16
*** manous has joined #openstack-swift02:17
*** manous has quit IRC02:22
*** manous has joined #openstack-swift02:25
*** vinsh has quit IRC02:27
*** catintheroof has joined #openstack-swift02:27
*** bkeller` has quit IRC02:31
*** vinsh has joined #openstack-swift02:33
*** bkeller` has joined #openstack-swift02:34
*** thumpba has joined #openstack-swift02:35
*** sgundur_ has joined #openstack-swift02:35
*** vinsh has quit IRC02:36
*** vinsh has joined #openstack-swift02:36
* portante wonders about that portante02:40
*** vinsh has quit IRC02:40
*** sgundur_ has quit IRC02:44
*** sgundur_ has joined #openstack-swift02:49
*** klamath has quit IRC02:53
*** asettle has joined #openstack-swift02:59
*** sgundur_ has quit IRC03:00
*** mingyu_ has quit IRC03:02
*** asettle has quit IRC03:03
*** nadeem has joined #openstack-swift03:13
*** mingyu has joined #openstack-swift03:23
*** tsg has joined #openstack-swift03:30
*** manous has quit IRC03:32
*** vinsh has joined #openstack-swift03:36
*** vinsh has quit IRC03:37
*** vinsh has joined #openstack-swift03:37
*** _JZ_ has quit IRC03:38
*** thumpba has quit IRC03:40
*** thumpba has joined #openstack-swift03:40
*** vinsh has quit IRC03:41
*** mingyu_ has joined #openstack-swift03:42
*** mingyu has quit IRC03:43
*** manous has joined #openstack-swift03:44
*** mingyu_ has quit IRC03:45
*** manous has quit IRC03:49
*** manous has joined #openstack-swift03:50
*** tsg_ has joined #openstack-swift03:53
*** tsg has quit IRC03:53
*** mingyu has joined #openstack-swift03:54
*** manous has quit IRC03:55
*** thumpba has quit IRC03:58
*** thumpba has joined #openstack-swift03:58
*** thumpba has quit IRC03:58
*** thumpba has joined #openstack-swift03:59
*** thumpba has quit IRC03:59
*** manous has joined #openstack-swift03:59
*** thumpba has joined #openstack-swift03:59
*** thumpba has quit IRC04:00
*** mingyu has quit IRC04:06
*** mingyu has joined #openstack-swift04:07
*** ukaynar has joined #openstack-swift04:23
*** ppai has joined #openstack-swift04:27
*** dmorita has quit IRC04:30
*** psachin has joined #openstack-swift04:36
*** rcernin has quit IRC04:37
*** caiobrentano_ has joined #openstack-swift04:39
*** caiobrentano__ has quit IRC04:41
*** klamath has joined #openstack-swift04:41
mahaticclayg: oh going by your last comment, I thought we're gonna call it a day by invalidating_hash for this lp bug #1301728. I thought of writing another patch on splitting out stuff04:42
openstackLaunchpad bug 1301728 in OpenStack Object Storage (swift) "tombstone (.ts) object will never be deleted if the hash_suffix exists in the hashes.pkl " [High,In progress] https://launchpad.net/bugs/1301728 - Assigned to Mahati Chamarthy (mahati-chamarthy)04:43
*** nadeem has quit IRC04:45
mahaticclayg: I updated the patch 346865 to only invalidate hash. We're not messing up by making listdir calls with that I believe. Do you still think splitting out get_ondisk_files and cleanup_disk_files in this patch is better?04:45
patchbothttps://review.openstack.org/#/c/346865/ - swift - Delete old tombstones04:45
*** klamath has quit IRC04:46
mahaticnotmyname: awesome t-shirts! do you have a designer? ;)04:48
*** tsg_ has quit IRC04:57
*** chsc has joined #openstack-swift04:59
*** asettle has joined #openstack-swift05:01
*** _JZ_ has joined #openstack-swift05:05
*** asettle has quit IRC05:05
*** _JZ_ has quit IRC05:07
*** manous has quit IRC05:07
*** chsc has quit IRC05:11
*** tqtran has joined #openstack-swift05:13
*** baojg_ has quit IRC05:13
*** baojg has joined #openstack-swift05:14
*** manous has joined #openstack-swift05:19
*** dmorita has joined #openstack-swift05:30
*** ChubYann has quit IRC05:31
*** dmorita has quit IRC05:35
*** rcernin has joined #openstack-swift05:43
*** silor has joined #openstack-swift05:44
openstackgerritKota Tsuyuzaki proposed openstack/swift: *WIP* Try to fix doubtful code  https://review.openstack.org/37127405:48
*** silor1 has joined #openstack-swift05:57
*** silor has quit IRC05:57
*** silor1 is now known as silor05:57
*** thumpba has joined #openstack-swift06:01
*** ukaynar has quit IRC06:02
*** thumpba has quit IRC06:06
*** klrmn has quit IRC06:11
*** rcernin has quit IRC06:14
*** rcernin has joined #openstack-swift06:19
*** pcaruana has joined #openstack-swift06:23
*** ukaynar has joined #openstack-swift06:28
*** klamath has joined #openstack-swift06:30
*** manous has quit IRC06:33
*** klamath has quit IRC06:35
*** silor has quit IRC06:37
*** vern has quit IRC06:40
*** vern has joined #openstack-swift06:43
*** hseipp has joined #openstack-swift06:44
*** manous has joined #openstack-swift06:45
*** manous has quit IRC06:50
*** manous has joined #openstack-swift06:50
*** manous has quit IRC06:55
*** tgtanya has joined #openstack-swift06:57
*** manous has joined #openstack-swift06:58
*** david-lyle_ has joined #openstack-swift06:59
*** david-lyle has quit IRC07:00
*** CrackerJackMack has quit IRC07:00
*** sams-gleb has joined #openstack-swift07:10
*** tmoreira has quit IRC07:18
*** manous has quit IRC07:18
*** cschwede has quit IRC07:19
*** tmoreira has joined #openstack-swift07:24
*** cschwede has joined #openstack-swift07:25
*** geaaru has joined #openstack-swift07:26
*** rledisez has joined #openstack-swift07:26
*** david-lyle has joined #openstack-swift07:28
*** oshritf__ has joined #openstack-swift07:28
*** oshritf_ has joined #openstack-swift07:28
*** ukaynar has quit IRC07:28
*** david-lyle_ has quit IRC07:29
*** manous has joined #openstack-swift07:31
*** CrackerJackMack has joined #openstack-swift07:31
*** tqtran has quit IRC07:33
*** Jeffrey4l has joined #openstack-swift07:37
*** kong has quit IRC07:41
*** joeljwright has joined #openstack-swift07:42
*** ChanServ sets mode: +v joeljwright07:42
*** oshritf_ has quit IRC07:56
*** oshritf__ has quit IRC07:56
*** oshritf__ has joined #openstack-swift08:00
*** oshritf_ has joined #openstack-swift08:00
*** thumpba has joined #openstack-swift08:01
*** openstackgerrit has quit IRC08:03
*** openstackgerrit has joined #openstack-swift08:04
*** jordanP has joined #openstack-swift08:11
*** klamath has joined #openstack-swift08:19
*** asettle has joined #openstack-swift08:20
*** klamath has quit IRC08:24
*** oshritf__ has quit IRC08:29
*** oshritf_ has quit IRC08:29
*** thumpba has quit IRC08:30
*** tgtanya has quit IRC08:42
*** tgtanya has joined #openstack-swift08:42
*** manous has quit IRC09:17
*** daemontool has joined #openstack-swift09:49
*** donagh has joined #openstack-swift09:51
*** tgtanya has quit IRC09:57
*** daemontool has quit IRC09:59
openstackgerritKota Tsuyuzaki proposed openstack/swift: *WIP* Try to fix doubtful code  https://review.openstack.org/37127410:01
*** klamath has joined #openstack-swift10:08
openstackgerritAlistair Coles proposed openstack/swift: Enable object server to return non-durable data  https://review.openstack.org/21527610:12
*** klamath has quit IRC10:12
kota_acoles: nice, do you find the reason why the unit test fails?10:12
kota_i'm just looking for with looking at the code.10:13
*** acoles_ is now known as acoles10:13
acoleskota_: not yet, i just added an exception handler to get soem more detail when the test fails10:14
kota_ok, good call. maybe similar thing with mine at patch 37127410:14
patchbothttps://review.openstack.org/#/c/371274/ - swift - *WIP* Try to fix doubtful code10:14
kota_I also am digging...10:14
*** tsg has joined #openstack-swift10:16
*** tsg_ has joined #openstack-swift10:20
*** tsg has quit IRC10:20
acoleskota_: I don't like the 0 in this line https://github.com/openstack/swift/blob/79a8388fbf1e0a43abe196ad2f35e94414963c19/test/unit/proxy/controllers/test_obj.py#L2230-L2230, I think that could result in no fragments being generated, still looking into that. No idea why that would just start burning us though.10:22
*** ppai has quit IRC10:22
kota_looking10:23
kota_hmm, sounds reasonable, it would make an empty string.10:24
kota_try it with my local10:24
kota_acoles:^^10:24
acolesyep. I will change it to 1 once the current patchset runs in jenkins, so we can see the new logs before and after the change10:25
*** daemontool has joined #openstack-swift10:26
*** thumpba has joined #openstack-swift10:27
acoleskota_: here's latest test failure log - the object doe not seem to have any fragments ?!? http://logs.openstack.org/76/215276/42/check/gate-swift-python27-ubuntu-xenial/eda0258/console.html#_2016-09-16_10_19_16_48190210:27
acoleskota_: I'll change that 0 and see if it helps10:28
kota_acoles: your thought is correct, I can see same error if the string is empty. wait a while, I'm preparing the snipets10:29
acoleskota_: okay. I need a coffee so bbiab10:29
*** dmorita has joined #openstack-swift10:31
*** thumpba has quit IRC10:32
kota_acoles: it was reproduced, https://gist.github.com/bloodeagle40234/b9c3677fddd7deecb7efcc96a42b502510:32
kota_"[:1]" does work, so that "random.randint(1, 1000)" for that seems to work10:34
kota_or "random.randin(1, segment_size)" is better?10:35
kota_randint10:35
*** dmorita has quit IRC10:36
acoleskota_: with your local diff, do other tests fail as well?10:36
kota_hmm... interesting if it is the reason why gerrit fails, we've not been doing actually *random* content body10:36
acoleskota_: I mean this diff https://gist.github.com/bloodeagle40234/b9c3677fddd7deecb7efcc96a42b502510:37
kota_wait a sec, i ran just a test.10:37
acoleskota_: yeah, are we just getting unlucky that that one test repeatedly gets a 0 from the randint?10:37
kota_nosetests reports errors=18 yes, other tests also fail if we use the stub.10:38
*** kong has joined #openstack-swift10:38
kota_maybe, something exits from fixed random seed?10:38
acolesyes, I just did it here too10:38
kota_interesting10:38
openstackgerritAlistair Coles proposed openstack/swift: Enable object server to return non-durable data  https://review.openstack.org/21527610:40
acoleskota_: let's see what jenkins thinks ^^10:40
kota_woo, i made a wrong patch when running other tests, but anyway, other tests got failures or errors (5 errors and 12 failures actually)10:41
kota_if i tested with my diff above10:41
acoleskota_: same for me, 5 + 1210:45
kota_acoles: ok, I'm starting to look at again with the diff from patch set 40.10:46
kota_it looks small enaough +146, -52 :D10:46
*** silor has joined #openstack-swift10:47
kota_acoles: ah, you addressed my comment for etag!? thanks! when reading subscription mail from gerrit including your response, I thought it could be in follow up10:50
acoleskota_: re. your comments about the scenarios passed to _test_get_ondisk_files - I agree that the scenarions ('.durable') are a little confusing, but I'd rather not make the test more complex. as a follow up I would rather clean up the scenario declarations.10:51
acoleskota_: re. etags - I added a check (well, I spent a day thinking about how to manage buckets for each (timestamp, etag) tuple, wrote code, deleted code, gave up and simply added a check :)10:52
acoleskota_: and a test. so now, even in worst case, pyeclib will not be passed frags from different etag objects10:52
kota_acoles: yey, simple solution.10:53
acoleskota_: maybe random seed gets set to a fixed value during test run - https://github.com/openstack/swift/blob/488f88e30abe2b9d67ce43697e3abc63c75699b7/test/unit/cli/test_ring_builder_analyzer.py#L131-L13110:53
acoleskota_: which calls https://github.com/openstack/swift/blob/89388bf232b54ec0adf5cb815efff23cd479e2c1/swift/common/ring/builder.py#L430-L43110:53
kota_acoles: yeah, and I had looked other place which setting the random seed for concrete testing result (can not point out for now though)10:54
*** kei_yama has quit IRC10:57
kota_acolse: btw, it is a bit far from EC but in replication case with same timestamp but different etag10:58
acolesthats the only place I can find random.seed() in swift10:59
acoleskota_: yep?10:59
kota_acoles: replication case seems safe to get the object becase one object-server should have complete object inside (some other object-server has different object though.10:59
kota_acoles: and then10:59
kota_acoles: if proxy got a failure (e.g. timeout) and doing fast_forward (redirecting to another object-server)11:00
*** silor1 has joined #openstack-swift11:00
kota_acoles: I'm wondering we could get mixed content... maybe?11:00
*** silor has quit IRC11:00
*** silor1 is now known as silor11:00
kota_am i getting crazy thought?11:00
rsFFahale_:11:01
kota_so e.g. object-server A: ts1 etag:a object-sever B:ts1, etag:b. proxy got a failure when draining etag a object and redirecting object-server B with the range for the rest.11:02
acoleskota_: looking11:02
kota_it looks jut forwarding the range...11:03
kota_exactly as you said, that situation (same timestamp but different etag) happens so rarely though.11:05
acoleskota_: looks like there is a check for etag equality when doing a fast_forward to a new node https://github.com/openstack/swift/blob/44a861787a60346aded8be2a54ef4e16accccbb6/swift/proxy/controllers/base.py#L1212-L122011:06
acolesphew!11:06
kota_ah yeah!11:07
kota_sorry, i missed it11:07
acoleskota_: in general, different etags at same timestamp breaks the fundamental presumption of swifts consistency model11:07
acoleskota_: with replica policy the object will survive and be readable but will never become consistent so no claim can be made over its durability (there may only ever be one replica of one content)11:08
kota_yes11:09
acolesin other words, 'don't go there' :D11:09
acolesbut I feel better that we now at least have a guard in the EC getter bucket11:10
kota_completely agree, great.11:11
kota_and thanks acoles!11:11
acoleskota_: success! http://logs.openstack.org/76/215276/43/check/gate-swift-python27-ubuntu-xenial/af85962/console.html#_2016-09-16_10_44_58_39429911:11
kota_acoles: yey!!!!!11:11
acoleskota_: I suspect that the one new test I added in patchset 41 caused the randint to fall on 0 for test_GET_with_only_handoffs, because the new test comes first alphabetically.11:14
* acoles hates test coupling11:15
acoleskota_: but still curious that it only worked out that way on jenkins11:16
kota_exactly.11:17
kota_ah, I learned,  self.assertEqual({obj1['etag'], None}, collected_etags) <- this is equal!!!  that is an expression of "set"11:17
*** suresh__ has joined #openstack-swift11:25
kota_done. that looks the greatest one from ever pacht sets.11:26
suresh__Hii all, What is the default chunksize of object when size is less than 5 GB11:26
suresh__pls someone help11:26
kota_suresh__: what do you mean the "chunk size"? the objects in your hardware devices? or network transfer chunk size?11:29
suresh__kota: if we upload > 5GB file we will use "swift upload test_container -S 1073741824 large_file"11:31
suresh__here 1073741824 is chunksize right?11:31
kota_suresh__: got it, it's a size for each segments of static large object11:31
openstackgerritKota Tsuyuzaki proposed openstack/swift: EC Fragment Duplication - Foundational Global EC Cluster Support  https://review.openstack.org/21916511:32
suresh__like this if i want to upload 3GB file what is the default chunk size?11:32
kota_suresh__: let me check11:33
suresh__kota: pls let me know if you got the answer11:35
kota_suresh__: it looks like no default value, if you don't specify the option, swift client doesn't break the original object into chunks, so you will see the raw object in the container.11:35
*** sanchitmalhotra has quit IRC11:36
kota_just a 3GB file in the swift, if i read the code correctly.11:36
kota_jowelright might know more detail, I'm not so good guy about swift client.11:37
* kota_ is thinking it seems the NW for developers in my office is going to down, so it's time to go back home!11:39
*** catintheroof has quit IRC11:39
* kota_ is using mobile NW tentatively11:40
*** suresh__ has quit IRC11:40
*** klamath has joined #openstack-swift11:56
*** m_kazuhiro has quit IRC11:58
*** joeljwright1 has joined #openstack-swift12:00
*** asettle has quit IRC12:01
*** klamath has quit IRC12:01
*** asettle has joined #openstack-swift12:01
*** asettle has quit IRC12:06
*** pdardeau has quit IRC12:07
*** baojg has quit IRC12:10
*** baojg has joined #openstack-swift12:12
*** asettle has joined #openstack-swift12:12
*** joeljwright1 has quit IRC12:21
*** catintheroof has joined #openstack-swift12:27
*** porunov has joined #openstack-swift12:44
*** thumpba has joined #openstack-swift12:44
porunovHello everyone! Does somebody use JOSS (Java Client for Swift)? Could you please help me to figure out how to upload a manifest file? I want to use SLO but it missed in documentation how to use SLO.12:49
*** StraubTW has joined #openstack-swift13:09
*** thumpba has quit IRC13:17
*** janonymous has quit IRC13:28
*** klamath has joined #openstack-swift13:45
*** daemontool has quit IRC13:46
*** klamath has quit IRC13:50
*** vinsh has joined #openstack-swift13:52
*** asettle has quit IRC14:06
*** tongli has joined #openstack-swift14:06
*** asettle has joined #openstack-swift14:07
*** asettle has quit IRC14:07
*** asettle has joined #openstack-swift14:07
openstackgerritAlistair Coles proposed openstack/swift: Unset random seed after rebalancing ring  https://review.openstack.org/37156414:08
*** asettle has quit IRC14:12
*** _JZ_ has joined #openstack-swift14:12
*** asettle has joined #openstack-swift14:13
jrichliporunov: SLO docs are here http://docs.openstack.org/developer/swift/overview_large_objects.html#module-swift.common.middleware.slo14:16
jrichliporunov: but I don't know about JOSS14:17
*** asettle has quit IRC14:18
*** asettle has joined #openstack-swift14:18
*** porunov has quit IRC14:19
*** asettle has quit IRC14:23
*** asettle has joined #openstack-swift14:23
*** porunov has joined #openstack-swift14:29
*** sgundur_ has joined #openstack-swift14:31
*** sams-gleb has quit IRC14:31
porunovjrichli: I mean using SLO with JOSS. Do you know how to use SLO with JOSS?14:32
jrichliporunov: no, sorry. I don't know about JOSS.14:33
*** vinsh has quit IRC14:35
*** sgundur_ has quit IRC14:36
*** sgundur_ has joined #openstack-swift14:45
*** vinsh has joined #openstack-swift14:47
*** vinsh has quit IRC14:47
*** vinsh has joined #openstack-swift14:48
tdasilvaporunov: looking quickly through the joss api, it seems like their upload object api doesn't take metadata14:48
*** janonymous has joined #openstack-swift14:48
tdasilvaporunov: http://joss.javaswift.org/future-features.html lists support for large objects as being a future thing, but seems to focus more on DLO14:48
tdasilvaor actually for slo, what you need is not a header, but a query param14:50
tdasilvaso yeah, sounds like you would need a special api for that14:50
*** kong has quit IRC14:51
*** tsg_ has quit IRC14:55
*** klamath has joined #openstack-swift14:57
*** nikivi has joined #openstack-swift15:04
*** philipw_ has quit IRC15:05
*** philipw has joined #openstack-swift15:05
*** rcernin has quit IRC15:15
acolesnotmyname: clayg: if you want to discuss patch 215276 I can be available later (after noon your time), ping me on signal/text. looks like clayg might have some concerns about the overall strategy.15:17
patchbothttps://review.openstack.org/#/c/215276/ - swift - Enable object server to return non-durable data15:17
*** _JZ_ has quit IRC15:18
*** acoles is now known as acoles_15:18
*** chsc has joined #openstack-swift15:20
*** klrmn has joined #openstack-swift15:23
*** klrmn has quit IRC15:29
*** tsg_ has joined #openstack-swift15:30
*** tsg__ has joined #openstack-swift15:32
porunovtdasilva: Here is their supported features. http://joss.javaswift.org/feature-matrix.html . There is "Large Object Creation". I think that they support SLO15:32
*** dmorita has joined #openstack-swift15:33
tdasilvaporunov: good point, still it could refer to DLO, it's somewhat vague, but you could be right15:35
*** tsg_ has quit IRC15:35
tdasilvaporunov: javadocs does list a ObjectManifest and QueryParameter class15:36
*** silor has quit IRC15:36
tdasilvaporunov: but it's not very clear to me how to use them....have you tried opening an issue on their github page and asking the question there?15:36
tdasilvai'm not sure if joss devs hangout here15:37
*** dmorita has quit IRC15:37
mahaticclayg: I'll check back your comments if any, on patch 346865 over the weekend, fyi.15:39
patchbothttps://review.openstack.org/#/c/346865/ - swift - Delete old tombstones15:39
*** ukaynar has joined #openstack-swift15:40
*** ukaynar has quit IRC15:41
notmynamegood morning15:41
notmynamenear-final summit room layout has been published http://lists.openstack.org/pipermail/openstack-dev/2016-September/103851.html15:43
*** psachin has quit IRC15:44
notmynamemahatic: my sister is the tshirt designer15:44
*** nadeem has joined #openstack-swift15:47
porunovtdasilva: I've opened 2 issues (it was another questions). It seems that they abandoned this project. But nevertheless it is the only Java API which I found to be workable with tempauth. I also tried jclouds and openstack4j but they didn't work.15:49
*** oshritf_ has joined #openstack-swift15:50
*** oshritf__ has joined #openstack-swift15:50
tdasilvaporunov: mm..too bad if they did abandon the project, although if you look at the history in github it seems they have had recent commits and even a release only 15 days ago15:51
*** pdardeau has joined #openstack-swift15:57
*** pdardeau has quit IRC15:57
*** pdardeau has joined #openstack-swift15:57
porunovtdasilva: Yes, but they hadn't any commits from Nov 30, 2014 till Jan 12, 2016. Also they don't answer questions on GitHub and don't have a documentation about their features. Of course I may be wrong but who knows. Nevertheless it is still nice API15:59
*** oshritf_ has quit IRC16:00
*** oshritf__ has quit IRC16:00
*** oshritf_ has joined #openstack-swift16:01
*** oshritf__ has joined #openstack-swift16:01
*** tsg_ has joined #openstack-swift16:03
*** rledisez has quit IRC16:03
*** tsg__ has quit IRC16:06
claygacoles_: i'm around; reading backlog16:10
*** oshritf_ has quit IRC16:12
*** oshritf__ has quit IRC16:12
*** ukaynar has joined #openstack-swift16:15
zaitcevporunov: It's quite sad that there's no good library. Did you try to develop a fix and submit it (e.g. where the query parameter is needed)? Some maintainers are more receptive if they see a patch.16:19
openstackgerritTravis McPeak proposed openstack/swift: Updating Bandit config file  https://review.openstack.org/36506516:20
*** hseipp has quit IRC16:21
*** asettle has quit IRC16:22
*** asettle has joined #openstack-swift16:23
claygapparently I don't know how timzones work - when I was in Central time UK was only 6 hours away :'(16:23
zaitcevSounds about right.16:23
zaitcevMountain is 7, Pacific is 816:24
claygright - need to remember *8* hours different now16:24
zaitcevShift by 1 in winter.16:24
zaitcevExcept in Arizona16:24
notmynameand Indiana, I think16:24
zaitcevWhen I fly, I immediately set my watch to GMT zone, because otherwise it's easy to set oneself up for a massive miscalculation. Also weather broadcast by ground stations has timestamps in GMT, so you know immediately how current an observation is.16:26
*** nadeem has quit IRC16:26
*** nadeem has joined #openstack-swift16:27
*** asettle has quit IRC16:27
*** sgundur_ has quit IRC16:32
*** nikivi has quit IRC16:32
*** nikivi has joined #openstack-swift16:34
*** nowz has joined #openstack-swift16:37
nowzHI everyone16:38
nowzI'm new User16:38
*** Suyi_ has joined #openstack-swift16:41
MooingLemurhellp16:50
MooingLemurhello, even16:51
timburkekota_: suresh_: yeah, with swiftclient if you don't specify -S <chunk_size>, no chunking occurs and you'll have a single 3GB object16:51
*** sgundur_ has joined #openstack-swift16:53
*** tqtran has joined #openstack-swift16:53
*** klrmn has joined #openstack-swift16:53
MooingLemurdoes swift-object-replicator use ephemeral IPv4 loopback sockets to talk to itself?16:54
zaitcevDo you mean to talk to swift-object-server on the same node or something? I don't think swift-object-replicator listens at all.16:55
MooingLemurI'm running into a situation where the object replicator seems to hang very easily (CentOS 7) and running strace shows most of the forked processes in futex(), one of them is in select(0,... and the remaining one is poll([fd=5...16:56
patchbotError: Missing "]".  You may want to quote your arguments with double quotes in order to prevent extra brackets from being evaluated as nested commands.16:56
MooingLemurthat process doing the poll has these in the output of lsof16:57
MooingLemurswift-obj 16427 swift    5u     IPv4           82879052       0t0      TCP 127.0.0.1:37528->127.0.0.1:56907 (ESTABLISHED)16:57
MooingLemurswift-obj 16427 swift    6u     IPv4           82879053       0t0      TCP 127.0.0.1:56907->127.0.0.1:37528 (ESTABLISHED)16:57
notmynamehello nowz16:57
*** janonymous has quit IRC16:58
MooingLemurI haven't yet seen this problem on my Gentoo hosts, but it's happening all the time on the new CentOS hosts.  I'm guessing this local socket is a side effect of some python library that swift is using, and the fact that it's using localhost sockets may not even be pointing to the actual problem. :P16:59
MooingLemurWhen it gets into this state, swift-object-replicator ignores SIGTERM16:59
*** _JZ_ has joined #openstack-swift17:00
MooingLemurand I don't see anything in syslog from swift-object-replicator to indicate any particular event17:00
MooingLemurit simply stops logging17:00
zaitcevA library is a reasonable guess, but I don't know what library triggers that.17:01
zaitcevAnd I see that it's the same PID.17:01
*** nowz has quit IRC17:02
*** geaaru has quit IRC17:03
MooingLemurhttps://bpaste.net/show/2c08a731a980 <-- strace -fp of the main pid of swift-object-replicator left for a few minutes17:05
*** tsg_ has quit IRC17:06
*** _JZ_ has quit IRC17:07
*** dmorita has joined #openstack-swift17:08
MooingLemurit does have a number of TCP connections open to various object server instances in the cluster (port 6000) and netstat shows 0 in the sendq and recvq for all established connections17:09
MooingLemuris there any introspection interface to the object replicator that I can use that might tell me more about the state that it's in?  Maybe a SIGUSR1 or something? :)17:10
MooingLemurheh, I guess for now I'll have to write a cron to restart the object replicator if it hasn't seen any syslog lines from it in the last 10 minutes17:14
zaitcevOr add a watchdog into its main loop. It's an open source, you know.17:15
MooingLemur:)17:15
zaitcevI tend to see these things a challenges, so I guess I would resurrect my old patch that tracebacks every thread and at least figure out where the Python goes.17:17
zaitcevIt was called "guru meditation"17:17
*** tsg_ has joined #openstack-swift17:17
zaitcevI can throw it up into a gist for you to look at, but if you reach for cron first, this may not be your style17:18
zaitcevhttp://www.zaitcev.us/things/swift/swift-2.7-nogurumed.diff17:20
zaitcevIt's basically diff -R of what you need and you have to apply it to replicator in particular17:20
*** jordanP has quit IRC17:20
MooingLemurit's more about deadlines at the moment.  I'd love to take time debug, but I've already got a framework for checking syslog (an enhanced version of swift-drive-audit that knows our syslog format, is aware of dm-cache, and handles lighting the fault light on the chassis)17:22
MooingLemurs/debug/to debug/17:22
MooingLemurbut I will grab that patch.  Thanks for the info :)17:23
*** rvasilets___ has joined #openstack-swift17:25
*** nikivi has quit IRC17:29
*** ChubYann has joined #openstack-swift17:37
claygwhoa17:48
*** nadeem has quit IRC17:49
claygthe loop back socket stuff is eventlet threadpools17:49
claygI think earlier versions used different stuff - but loopback sockets were more crossplatform?17:50
claygI seem to recall not seeing them for a long time - then they showed up - i freaked out - torgomatic_ said it was cool tho and that was the resonablable explination he gave17:50
zaitcevSo basically maybe steal an eventlet from Fedora 23 and stuck it into CentoOS 7, see if that magically cures eveything.17:51
claygat somepoint I think I did verify that if your eventlet uses it's tpool you see those connections17:51
claygMooingLemur: i've seen the object replicator lock up for ... different reasons17:52
claygMooingLemur: I'm not sure the loopback/eventlet-threadpool has anything to do with it17:52
*** joeljwright has quit IRC17:53
claygMooingLemur: there's a log line that you sometimes see emitted in this state -> https://bugs.launchpad.net/swift/+bug/157527717:53
openstackLaunchpad bug 1575277 in OpenStack Object Storage (swift) "object-replicator goes into bad state when lockup timeout < rsync timeout" [High,Confirmed]17:53
claygMooingLemur: can you grep for "Lockup detected.. killing live coros"17:53
claygMooingLemur: by all means work around what ever issues you find in production in whatever way is convient for you to do - but please please please value us as a community enough to make sure any issues you work around have good bugs open for them!17:55
claygMooingLemur: thank you!17:56
*** porunov has quit IRC18:03
claygtimburke: you've been reviewing patch 215276 - and I assume have some familiarity with the issues it's addressing?18:07
patchbothttps://review.openstack.org/#/c/215276/ - swift - Enable object server to return non-durable data18:07
clayglp bug #1469094 - the oldest and most commmon18:07
openstackLaunchpad bug 1469094 in OpenStack Object Storage (swift) "Timeout writing .durable can cause error on GET (under failure)" [High,Confirmed] https://launchpad.net/bugs/1469094 - Assigned to paul luse (paul-e-luse)18:07
clayglp bug #1624176 - newerish bug also quite common (broken in proxy already addressed in the reconstructor)18:08
openstackLaunchpad bug 1624176 in OpenStack Object Storage (swift) "500 ServerError trying to read EC object with duplicate frags" [High,Confirmed] https://launchpad.net/bugs/162417618:08
clayglp bug #1624088 - a *durability* issue18:08
openstackLaunchpad bug 1624088 in OpenStack Object Storage (swift) "EC missing durable can prevent reconstruction" [Critical,Confirmed] https://launchpad.net/bugs/162408818:08
clayglp bug #1484598 - a complicated web of not-well-understood spookyness that introduces a bunch of complexity18:08
openstackLaunchpad bug 1484598 in OpenStack Object Storage (swift) "Proxy server ignores additional fragments on primary nodes" [High,In progress] https://launchpad.net/bugs/1484598 - Assigned to paul luse (paul-e-luse)18:08
clayganyway - Al's patch got a +2 from Kota - I was thinking about running in through another round adding some followups and sticking a +A on it18:09
clayg... any obvious objections or thoughts?18:09
clayg... anyone else? notmyname?18:09
notmynameoh hai18:09
claygnotmyname: !!!!18:09
claygnotmyname: I'm in a bad mood today!  :D18:10
notmynamethen I'm glad you're WFH and can't throw things at me ;-)18:11
timburkeclayg: seems like a plan. i'd kinda written off that review as a fait accompli between your previous +2 and kota_'s current +218:11
claygyou know me - i mostly just yell and curse - but I do that when i'm in a good mood - so what can you do18:11
claygtimburke: rofl!18:12
claygIf you stick enough Closes-Bug on a patch it is *definately* a fait accompli18:12
claygI18:12
claygI've never heard that term before - thank you18:12
timburkeleast i could do for introducing me to lagniappe18:14
clayghaha18:14
claygsigh... we're going to have to start writing developer docs for our internal API's :'(18:15
claygeven ssync is FAR to complicated to not have descriptive prose - MIME expect 100 continuing object servers - whatever the heck that json RPC thing the containers servers' do18:16
timburkeyep. over and above what we might want to write for middleware developers18:17
timburkehttp://docs.openstack.org/developer/swift/development_middleware.html#creating-your-own-middleware is ok, but it doesn't even *touch* on trying to write your own auth middleware, say, or how/when to use footers, or...18:17
claygfooters :'(18:18
timburkewhat? they're great! love 'em! but without already knowing about them or digging through a lot of code, there's no way i'd discover them18:19
notmynametimburke: can you hop in #openstack-operators please?18:23
claygtimburke: the idea of adding metadata not known when you start a PUT to an object as an atomic item is fine (vs say a non-atomic PUT/POST on the same connection pipeline with the same timestamp) - but I don't like the implementation of MIME streaming - as far as inventing a protocol to support footers I think we could have done better18:25
*** chlong_ has quit IRC18:27
timburkeclayg: ah, but the beauty is, from a middleware developer's perspective, it doesn't matter!18:39
clayghaha18:41
*** nikivi has joined #openstack-swift18:42
timburkeman, i love some of the things we've done with swiftclient lately! now we can say things like `swift download $(swift stat "$CONTAINER" "$DLO" | grep Manifest | sed -e 's/^[^:]*: //' -e 's!/! --prefix=!')`19:05
claygtimburke: that sed syntax is sorta spooky to me - but from context it looks roughly like you're downloading all of the segments of a DLO by pulling it's Manifest value out of the HEAD/stat request?19:08
timburkeyup!19:08
claygfwiw - i also like --prefix on download - is that new(ish)?19:08
timburkeoxinabox might be interested as a temporary workaround for https://bugs.launchpad.net/python-swiftclient/+bug/162156219:09
openstackLaunchpad bug 1621562 in python-swiftclient "Download large objects concurrently" [Wishlist,Confirmed]19:09
timburkeclayg: yep; added when i did...umm... where was it....19:09
*** ukaynar has quit IRC19:10
*** ukaynar has joined #openstack-swift19:10
timburkenope! i was thinking of delete growing --prefix in patch 19088719:12
patchbothttps://review.openstack.org/#/c/190887/ - python-swiftclient - Use bulk-delete middleware when available (MERGED)19:12
timburkedownload --prefix has been around a while; swifterdarrell added it for 1.5.0!19:13
claygoh that swifterdarrell - he's so great19:13
openstackgerritClay Gerrard proposed openstack/swift: Add probetest for not uncommon EC failure  https://review.openstack.org/37177119:13
*** McMurlock1 has joined #openstack-swift19:21
*** sgundur_ has quit IRC19:25
MooingLemurclayg: Thanks for the bug pointer, my rsync timeout is set to 3600 at the moment due to inter-region replication and long-running rsyncs were getting killed prematurely when it was set to 900.  I will increase the lockup_timeout and see what happens19:28
*** nikivi has quit IRC19:28
*** david-lyle has quit IRC19:30
*** david-lyle has joined #openstack-swift19:30
MooingLemurzaitcev, clayg: sorry if my tone was a little short.  Sometimes I feel like I shouldn't bother opening bugs unless I have something more useful to say than "it locks up".  I wish I had more time to dedicate to working on these issues :)19:31
MooingLemurclayg: I couldn't find that string in the logs, but I do remember seeing a message similar to that.  However, it could have just been in the replicator source.19:32
*** StraubTW has quit IRC19:33
*** sgundur_ has joined #openstack-swift19:37
claygMooingLemur: sometimes a bug report is just the start of a conversation - someone later might say "I saw it too!" - https://xkcd.com/979/19:38
*** StraubTW has joined #openstack-swift19:38
claygMooingLemur: and you weren't short/curt/whatever - don't worry about it - it's irc19:38
*** StraubTW has quit IRC19:39
*** StraubTW has joined #openstack-swift19:39
*** StraubTW_ has joined #openstack-swift19:40
*** david-lyle has quit IRC19:43
*** StraubTW has quit IRC19:44
*** ukaynar has quit IRC19:46
tdasilvanotmyname: is there a policy or process for closing bugs that we think are no longer valid?19:47
tdasilvaor that might have been fixed by an unknown patch?19:47
notmynametdasilva: beyond simply marking them as closed? nope. no other process19:48
notmynametdasilva: so either mark it as fix released or invalid and leave a comment on the bug with your thinking19:48
claygtdasilva: if there's not a good way to a/b test "yes, this is fixed on master" - you could try to add your thinking/tests and set it to incomplete19:49
claygbut if it's fixed you can just say how you know it's fixed and then close it19:49
clayg... that's what'd I'd do19:49
claygnotmyname: lol - i just said the same thing you did - sorry19:49
claygtdasilva: listen to notmyname19:49
tdasilvaclayg, notmyname: ok, my other question was 'what's launchpad for close', i guess notmyname said: 'fix released'19:50
notmynameyeah. fix released19:50
tdasilvanotmyname, clayg: thanks!19:51
openstackgerritThiago da Silva proposed openstack/swift: Return 404 on a GET if tombstone is newer  https://review.openstack.org/37115019:53
claygtdasilva: PROBETEST !! that's awesome!19:57
*** openstackstatus has quit IRC19:58
tdasilvaclayg: thanks for the tip, i hope it's going in the right direction20:00
*** openstackstatus has joined #openstack-swift20:01
*** ChanServ sets mode: +v openstackstatus20:01
clayghrmm... apparently my tox.ini isn't flagging H233 like it should e20:09
*** chsc has quit IRC20:09
claygor at least not automatically on buffer save :\20:10
openstackgerritClay Gerrard proposed openstack/swift: Add probetest for not uncommon EC failure  https://review.openstack.org/37177120:10
clarkbclayg: you may need to rebuild the virtualenv if its a new hacking rule (tox -r will do this)20:10
notmynamelooks like the tox.ini comments say we ignore H233, but it's not in the ignore line :-(20:11
notmynameah. it's timburke's fault20:12
timburkeyup, forgot to remove it20:12
openstackgerritJohn Dickinson proposed openstack/swift: remove comment saying we ignore H233. we actually check it  https://review.openstack.org/37179020:13
notmynameCRITICAL BUG FIX20:13
notmynametimburke: ;-)20:13
notmynametimburke: I'm definitely not casting any stones here20:13
*** sgundur_ has quit IRC20:15
tdasilvatimburke: you should have put a -1 and added a comment about missing #Closes-Bug flag :P20:15
*** AndyWojo has quit IRC20:16
*** AndyWojo has joined #openstack-swift20:17
claygidk, it's not like my flake8 plugin to vim is readying the comment?20:21
claygit's unltimatley flake8 that reads the tox.ini - and it blew up from the command line - i'm not sure why my vim is missing it20:21
timburkeclayg: does your flake8 plugin to vim know about hacking?20:22
claygtimburke: yes, it seems that somehow what I thought used to work for starting my editor to respect the local flake8 in the virtualenv is no longer working - i was only getting the checks of my system flake820:30
*** Jeffrey4l has quit IRC20:35
*** Jeffrey4l has joined #openstack-swift20:35
openstackgerritTim Burke proposed openstack/swift: Turn on F812 check  https://review.openstack.org/37179920:36
notmynametimburke: uh oh. I think you might have stepped in it20:37
timburkethat list is gonna keep getting shorter and shorter! eventually we won't even be worth *mentioning* on http://flake8.readthedocs.io/en/latest/user/configuration.html !20:37
notmynameIIRC that was the biggest point of contention back when we went from whitelist checks to blacklist checks20:37
timburke*why*? there were only *three* violations, most of them in tests20:38
*** baojg_ has joined #openstack-swift20:40
*** baojg has quit IRC20:43
MooingLemurclayg: I might have found something relevant: warning Unexpected file /srv/node/f1s23/objects/785930/04a/2ff82a8a0ae1c31397e2fce2edc4104a/.1420009299.86614.data.fLw0Bm: Invalid Timestamp value in filename u'.1420009299.86614.data.fLw0Bm'20:44
MooingLemurlast log line on one of the boxes before it froze20:44
patchbotfroze20:44
* MooingLemur eyes patchbot :>20:45
MooingLemurerr, not froze, but last line before object-replicator decided not to do any more work20:45
notmynameMooingLemur: patchbot is rather neurotic these days20:47
notmynameI think my next step is to write an IRC bot from scratch to be as simple as possible20:47
MooingLemurhehe20:48
MooingLemurclayg: however, that might be a red herring, since that's not like that on other boxes that have stalled replicators20:50
*** myoonnyc has quit IRC20:50
*** baojg_ has quit IRC20:51
claygtimburke: what the passive agressive who now?  why are we on flake8's docs?!20:52
claygWHY ARE ANY OPNSTACK CUSTOM H RULES ON FLAKE8'S DOCS!?20:52
*** baojg has joined #openstack-swift20:52
notmynamewow20:53
zaitcevOpenStack is a major project, you know.20:53
zaitcevLook at the Summit attendance.20:54
notmyname"let's take a look at an open source project that's using our tool. look at how terrible they are. instead of proposing a fix, we'll just keep it as-is as a bad example and warning to others"20:54
MooingLemurWas there ever code released in swift to clean up stale rsync dotfiles in object directories?20:57
notmynamehttps://review.openstack.org/#/c/293177/20:57
MooingLemurI remember being around for the discussion of the issue20:57
patchbotpatch 293177 - swift - Auditor will clean up stale rsync tempfiles (MERGED)20:57
notmynamethat was in 2.7.020:58
MooingLemurroger :)20:58
MooingLemurthanks20:58
*** sgundur_ has joined #openstack-swift21:00
*** baojg has quit IRC21:00
*** dmorita has quit IRC21:00
*** dmorita has joined #openstack-swift21:07
*** sgundur_ has quit IRC21:08
*** StraubTW_ has quit IRC21:09
notmynamehttps://gitlab.com/pycqa/flake8/issues/22821:12
*** _JZ_ has joined #openstack-swift21:17
*** wasmum has quit IRC21:18
*** nadeem has joined #openstack-swift21:20
*** wasmum has joined #openstack-swift21:20
*** _JZ_ has quit IRC21:22
pdardeautorgomatic_: notmyname: on comments on patch 336323, i'll be looking into some md5 related stuff soon21:26
patchbothttps://review.openstack.org/#/c/336323/ - swift - Add checksum to object extended attributes21:26
*** dmorita has quit IRC21:28
*** tsg__ has joined #openstack-swift21:30
*** caiobrentano_ has quit IRC21:32
pdardeaunotmyname: torgomatic_: i created lp 1624556 (wishlist) for utility to add metadata checksum on existing objects21:32
openstackLaunchpad bug 1624556 in OpenStack Object Storage (swift) "Create utility to add metadata checksums" [Undecided,New] https://launchpad.net/bugs/162455621:32
patchbothttps://review.openstack.org/#/c/1624556/21:32
*** tsg_ has quit IRC21:33
*** tsg__ has quit IRC21:36
*** klamath has quit IRC21:37
*** klamath has joined #openstack-swift21:37
openstackgerritTim Burke proposed openstack/swift: Store SLO Etag and size in sysmeta  https://review.openstack.org/34753821:38
openstackgerritTim Burke proposed openstack/swift: Turn on F812 check  https://review.openstack.org/37179921:45
timburkeok, so there were *four* places...21:45
*** dmorita has joined #openstack-swift21:47
*** tsg__ has joined #openstack-swift21:58
openstackgerritMerged openstack/swift: Enable object server to return non-durable data  https://review.openstack.org/21527622:11
*** catintheroof has quit IRC22:31
openstackgerritTim Burke proposed openstack/swift: Include metadata in PUT/POST responses  https://review.openstack.org/35755922:37
*** tsg__ has quit IRC22:44
*** david-lyle has joined #openstack-swift22:48
*** Jeffrey4l has quit IRC22:48
*** Jeffrey4l has joined #openstack-swift22:49
*** McMurlock1 has quit IRC22:59
*** Jeffrey4l has quit IRC23:21
*** Jeffrey4l has joined #openstack-swift23:22
*** nadeem has quit IRC23:24
*** rvasilets___ has quit IRC23:27
*** Suyi_ has quit IRC23:44
*** dmorita has quit IRC23:59

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