Monday, 2015-03-30

openstackgerritMerged openstack/swift: Make ECDiskFile require a fragment index  https://review.openstack.org/16807600:12
*** ho has joined #openstack-swift00:12
hogood morning guys!00:20
notmynamehello00:22
*** dmorita has joined #openstack-swift00:24
*** annegentle has quit IRC00:26
mattoliverauho: Morning00:28
*** annegentle has joined #openstack-swift00:29
honotmyname: mattoliverau: hello, thanks!00:34
hoDo we have priority review in this week?00:35
mattoliverauclayg:  are you doing something on patch 168543, otherwise I'm about to push a patchset to fix the pep8 issue00:36
patchbotmattoliverau: https://review.openstack.org/#/c/168543/00:36
*** haomaiwang has quit IRC00:36
mattoliverauho: there are always priority reviews :P.. but in regards to EC, yeah still some more to be merged, so still more need to be reviewed. Getting closer tho (famous last words)00:37
homattoliverau: thanks! yeah, we always have prioirty reviews :) Can I have patch numbers of priority reviews?00:40
mattoliverauho: they are always on the dash board (in the channel title) and on our priority reviews wiki page.00:41
notmynameho: check out the starred things on http://goo.gl/uRzLBX00:42
*** Gu_______ has joined #openstack-swift00:42
notmynameho: basically for the next ~24 hours (or less), we need to get the final things for the ec beta into the feature/ec branch so that we can begin the merge to master00:42
homattoliverau: notmyname: Do we have any blocking patch to proceed it?00:43
notmynameho: what's "it"?00:44
*** kota_ has joined #openstack-swift00:44
notmynameho: so the 2 starred patches there don't have any blockers00:44
openstackgerritMatthew Oliver proposed openstack/swift: Fix AttributeError and logging in ECAppIter  https://review.openstack.org/16854300:45
honotmyname: from this week we will start merging right? in order to do it, I would like to know00:45
notmynameho: right00:45
honotmyname: whether there is *really* priority reviews00:45
notmynameho: there's nothing blocking the merge except having the right code *to* merge. ie the feature/ec branch00:45
mattoliverauclayg: ^^ pep8 issue fixed00:45
notmynameho: you mean outside of feature/ec?00:45
honotmyname: I understand our current focus is ec.00:46
notmynameho: so for other stuff outside of feature/ec, there's isn't anything on gerrit that must land before feature/ec. of course, there's some good stuff there, but the focus is ec00:47
honotmyname: i see. On dashboard, there are ec related patches. I would like to spend my time for high priority patches is what I wanted to say/do today.00:49
notmynameok :-)00:49
honotmyname: which is high priority "Starred" or "Erasure Code work" on dashboard?00:52
notmynameho: "starred"00:52
honotmyname: thanks! I will try.00:52
notmynameho: the most important thing on ec right now is getting https://review.openstack.org/#/c/165188/ (the reconstructor patch chain) beat into shape and landed. that's the last crucial piece of missing functionality on ec00:53
notmynamewell, that's the first of 3 patches in a dependency chain00:53
honotmyname: thanks. I understand.00:55
kota_notmyname: for now, someone else is working on chainging those?00:55
kota_notmyname: I am worried I could review stale patches on the chain.00:55
kota_nomyname: anways, good morning : )00:56
mattoliveraukota_: morning00:56
notmynamekota_: good question, and good morning00:56
kota_mattoliverau: morning : )00:56
mattoliveraukota_: even stale reviews are good as you may see something that others miss :)00:56
notmynameI'd defer to clayg on that, but AFAIK the major structure of the patches are good. ie if there are additional changes, it's to fix stuff that's found in review00:57
kota_mattoliverau, notmyname: OK, I am going to start to review, today ;-)00:59
mattoliveraukota_: cheers, more eyes on the code the better :)00:59
mattoliverauho: thanks to you as well :)01:00
*** shakamunyi has joined #openstack-swift01:07
*** shakamunyi_ has joined #openstack-swift01:07
*** Gu_______ has quit IRC01:09
openstackgerritClay Gerrard proposed openstack/swift: Fix AttributeError and logging in ECAppIter  https://review.openstack.org/16854301:13
claygmattoliverau: it wasn't even pep8 - it was a whole big mess01:14
claygoh - you had already done the import - yeah that was step 0 i guess :P01:14
mattoliveraulol01:14
claygmattoliverau: you eve seen this one -> https://www.youtube.com/watch?v=SY99U3cpsIw01:16
*** annegentle has quit IRC01:19
clayg... and before you know it you have the engine pulled out of the car01:19
mattoliverauclayg: haha, awesome.. ahhh, so step 0 :P01:20
claygoh shit, the stupid doc comment code :\01:20
openstackgerritClay Gerrard proposed openstack/swift: Fix AttributeError and logging in ECAppIter  https://review.openstack.org/16854301:21
clayg^ yeah that's better!01:24
claygok, dinner time01:24
openstackgerritMerged openstack/swift: Guard against invalid Policy  https://review.openstack.org/16854801:24
claygbbiab01:24
claygoh yeah heh i remember when jd clicked approve on that one... HOURS AGO :P01:25
mattoliverauha, well I'm going to take a lunch break. bbs01:28
*** Guest____ has joined #openstack-swift01:55
openstackgerritDaisuke Morita proposed openstack/swift-specs: Changing Policies spec  https://review.openstack.org/16876102:09
*** BAKfr has quit IRC02:11
*** haomaiwang has joined #openstack-swift02:13
*** BAKfr has joined #openstack-swift02:13
*** annegentle has joined #openstack-swift02:45
*** annegentle has quit IRC02:51
*** shakamunyi__ has joined #openstack-swift02:51
*** david-ly_ is now known as david-lyle02:52
*** shakamunyi has quit IRC02:54
*** shakamunyi_ has quit IRC02:54
*** shakamunyi has joined #openstack-swift02:54
*** branne has joined #openstack-swift03:00
*** haigang has joined #openstack-swift03:04
*** jrichli has quit IRC03:07
*** branne has quit IRC03:17
claygi thought patch 168543 must have not been failing on my machine because i have recon configured and the test doesn't mock it out03:24
patchbotclayg: https://review.openstack.org/#/c/168543/03:24
clayg... but it looks like it is passsing in a mkdtemp as the recon_cache_path - so I don't know what exception is being caught in jenkins03:25
clayghrmm... acctually I had an idea that might help - man I'm really reworking the fake logger here :\03:25
*** sandywalsh has quit IRC03:28
notmynameI'm happy about s/RUGGEDIZE/SSYNC03:28
*** ppai has joined #openstack-swift03:30
claygnotmyname: on master it'll just be REPLICATION -> SSYNC03:30
clayggot a great time for any other breaking protocol changes03:30
mattoliverauclayg: on test_failed_delete_continue_on the lists it asserts are not the same, the error_lines has an additional line (exception): 'Exception dumping recon cache'03:35
*** sandywalsh has joined #openstack-swift03:37
mattoliveraunow to debug to see where that is coming from03:37
claygmattoliverau: yeah i was thinking it was just working for me because I have recon setup - but acctually the test seems to be setting up a mkdtemp rcache path - so I don't know what's going on.03:40
mattoliverauI yeah, now I see you previous msg.. /me fails to read scroll back :P03:40
claygbah, i was just thinking that it'd be nice if the FakeLogger handler did something to include soe of the exception in the log line - there's a few tests that still dig into log_dict because it's the easiest way to get at the exception from exc_info03:44
claygi was playing around with adding like .... '\n%s: %s' % (exc_info[0], exc_info[1]) ... or someting minimal like that to the log lines that include exc_info03:44
claygbut... i'm not really sure I like how it's turning out03:45
claygi really just wish I knew what that gate check failed to dump the recon cache03:45
claygi was about to just mock.patch('.dump_recon_cache') before calling run_once - but i feel like tht's sorta dodging the issue03:45
mattoliverauclayg: it seems to be dying when trying to lock_file on '/var/cache/swift/object.recon' I assume it doesn't exist03:50
mattoliverauat least on my  machine03:50
mattoliveraua mock may be in order03:50
claygwhy is it trying to ... oh03:52
claygi03:52
claygno...03:52
claygisn't it creating the expirer with the recon_cache_path of the mkdtemp?03:52
claygyeah lockfile seems to think it can create the file03:57
mattoliveraulol, if I: x = expirer.ObjectExpirer({'recon_cache_path': self.rcache},03:58
mattoliverau                                  logger=self.logger)03:58
mattoliverauthen the test passes.. turns out we need to pass in the tmp recon cache03:58
mattoliverauclayg:  ^03:58
notmynamemattoliverau: what's different about your saio that makes it fail? works on my machine too03:59
notmynameyou don't have recon set up?03:59
mattoliveraunot, I'm just running the unit tests on the code (as jenkins does)04:00
mattoliverauwow, my typing is awesome today04:00
notmynamewell, me too04:00
notmynamebut I have 'sudo mkdir -p /var/cache/swift \n sudo chown -R swift:swift /var/cache/swift' in my resetswift script04:01
mattoliverauso I'm not running it on a saio, so the cache doesn't exist.. unless I pass the tmpdir created04:01
claygmattoliverau: no i thought the test already did that?04:01
clayglike which line are you doing that in?04:01
mattoliverauit doens't, I had to add it04:01
notmynameline 568, rihgt?04:01
mattoliverau56804:01
mattoliverauyup04:01
mattoliverauthe test passes in an empty config, so I can define the 'recon_cache_path' and use the tmp file the test has created (but isn't passing)04:02
notmynamemattoliverau: and 424 and 37304:02
notmyname(the other tests that are failing04:03
mattoliverauI'll try, I was just debugging one at a time.. give me a sec04:03
claygoh wow - test_container_timestamp_break setts it the self.rcache one time it creates it and the next time it does not04:04
claygmattoliverau: no it's cool - you found it - nice work - i'll audito all the instantiation and make sure they're all using the tempdir04:04
*** thumpba has joined #openstack-swift04:05
notmyname(there are 26 matches for "ObjectExpirer({}" in that file)04:05
claygnotmyname: yeah I think some of them are just testing the process sharding config option stuff - they're easier to read left alone I think04:07
claygnotmyname: I think it's only the ones that call run_once04:07
notmynameclayg: see the Hal youtube video you left in here earlier.... ;-)04:07
mattoliverauok in test_object_timestamp_break, it still fails. but it's becuase the output lines don't match.04:08
mattoliverauparticularly: 'Pass completed in 10s; 0 objects expired' is generated, but is expecting 'Pass completed in 0s; 0 objects expired'04:08
mattoliverauis that just a typo? 10 secs rather then 0 secs04:09
mattoliverauI can debug to find out.. but in case you know04:09
notmynameI need to go put kids to bed04:09
notmynamelooks like there are 4 patches outstanding: 3 for the reconstructor chain and the one you're just looking at04:10
notmynamewhich seems doable, especially as EU comes online04:11
notmynameI'll get the feature/ec_review branch set up in the morning04:11
notmyname(my morning)04:12
notmynameall of those are starred04:13
notmynameok, gotta run. good night04:14
mattoliverauSo test_failed_delete_keeps_entry works with the tmpdir fix if you set the option when the expirer is created _both_ times.04:14
mattoliveraunotmyname: night man04:14
mattoliverauSo I'll go back to timestamp_break and debug some more04:15
mattoliverauopps, yup timestamp_breaks is fixed by the config too.. just make sure you make the change in _both_ places in the test too :P04:16
clayghehehe04:17
claygyeah i got my macro going now - wasted a few mintutes trying to figure out why it wasn't working because I didn't save the buffer - but I think i'm getting close now04:18
claygmattoliverau: thanks for the help!04:18
mattoliverauclayg: nps, anytime :)04:18
claygacctually that may be it04:23
claygok I deleted /var/cache/swift - i'm running all the unittests now04:23
mattoliveraunice04:23
mattoliverauI'm happy to run it for you too.. just running it with those 3 tests changed atm04:24
clayga'ight gerrit try this!04:25
openstackgerritClay Gerrard proposed openstack/swift: Fix AttributeError and logging in ECAppIter  https://review.openstack.org/16854304:25
mattoliverauyay passed on mine now04:28
*** zaitcev has quit IRC04:32
*** zaitcev has joined #openstack-swift04:32
*** ChanServ sets mode: +v zaitcev04:32
zaitcevWeird, Xchat lost its marbles and started hogging CPU for no reason. Could be an attack of some kind.04:33
kota_mattoliverau: congrats04:35
mattoliverauzaitcev: xchat probably just wanted some attention :P04:37
mattoliverauor the internet thinks your too productive that you must be a botnet04:38
*** shakamunyi_ has joined #openstack-swift04:39
zaitcevI'm trying to package Tushar's liberasurecode, and it fails the build of a test binary with rpmbuild. Works fine with plain "make".04:40
mattoliverauclayg: and the new patchet passes on my machine.. plus the test_verioned_manifest tests that were taking up to 20+ seconds each and now < 1/2 as long.. what did you do?04:40
zaitcevFor some reason we already added PyECLib to master's requirements.txt, so I cannot build Swift unless I package the whole enchilada, stat.04:40
mattoliverauzaitcev: bugger :(04:41
*** shakamunyi__ has quit IRC04:41
*** shakamunyi has quit IRC04:41
claygmattoliverau: wat?  no those still take forever on me04:41
*** shakamunyi has joined #openstack-swift04:41
claygzaitcev: yeah i don't know why that got accepted into master already unless infra needed it there to add to global requirements or something?04:42
mattoliverauclayg: maybe my machine just evolved (or found some more CPU) :P04:42
claygmattoliverau: must be!04:42
hoclayg: mattoliverau: You fixed the following three FAILs in test_expirer (patch 168543)? http://paste.openstack.org/show/197386/04:42
patchbotho: https://review.openstack.org/#/c/168543/04:42
mattoliverauho: yup :) I and passes04:43
mattoliveraugerrit has passed py27 check, now just waiting on all the tempest stuff04:43
homattoliverau: thanks! I will rebase it for my review.04:44
mattoliverauho: awesome :)04:45
*** welldannit has joined #openstack-swift04:46
claygho: mattoliverau says their fixed04:47
*** ppai_ has joined #openstack-swift04:47
claygho: i'm looking at your comment son patch 165188 - not sure I prefer the alrger try block to catch the assertion error all in one go04:47
patchbotclayg: https://review.openstack.org/#/c/165188/04:47
mattoliverauwell my tox and gerrit thinks so :)04:47
claygho: using the asssertion error in the debug message is ok maybe - but if it's going to be that wide might have to add exc_info and nab the traceback so you can tell who exactly raised the assertion error - which seems like a bunch of noise for a debug message04:48
*** ppai has quit IRC04:48
*** zaitcev has quit IRC04:49
claygho: I think we sort of assume skipping these invalid hash paths is just part of normal operation - a better place for the traceback would be in the auditor something - maybe quarantine them?  I'm not quite sure04:49
hoclayg: I'm checking my comment and code. Please give a minute04:51
claygho: as far as moving the test methods - yield_hashes is a Manager method - so I think for an organization stand point it's quite reasonable to move them from TestDiskFile to TestDiskFileManager04:51
hoclayg: thanks for the explanation of the moving. I understand.04:52
claygho: well i just applied your diff - and I'm looking at the big try block catching something fairly generic like an AssertionError - it's probably fine i guess -> https://gist.github.com/clayg/b6ae381139621d135d5b04:53
claygho: it *is* a little less code - and I acctually screwed up the exception Assertion: log; conitinue the first time I wrote it (i forgot the continue)04:54
claygso maybe it's better to put everything in one - trying to think if there's anything better we could do - maybe log.debug(exc_info=1) or something?04:54
claygho: hrm... yeah that assertionError message is acctually pretty good04:58
hoclayg: sorry to respond you late. it's touch for me to follow your speed :)04:59
claygho: not it's fine - i'm just thinking out loud - I think you're onto something05:02
claygyeah ok, i'm definately +2 on including the assertion error output05:03
hoclayg: I can not find the info of log.debug(exe_info=1). could you point it out?05:03
*** shakamunyi_ has quit IRC05:04
claygyou can make any log message level include the traceback like logger.exception by passing in exc_info=True05:05
hoclayg: sorry, I found it. type for error can be gotten.05:05
claygyou can think of logger.exception as an alias for log.error(exc_info=True)05:05
claygho well it does the whole traceback - which would be useful if you needed to suss out which of the two or three lines that could have raised that assertion error acctually did05:06
claygbut i'm not sure it's important which one raised the assertion - maybe i would just rather it raise something more specific - like "DiskFileInvalidHashdirContents" or something :\05:07
hoclayg: the messages are quite useful I think and distinguish the line of code.05:08
claygacoles_away: it bugs me that hash_listdir_cleanup calls gather_ondisk_files, then in yeild_hashes after hash_listdir_cleanup we have to call gather_ondisk_files again05:08
claygho: how do they distinguish - i honestly can't tell when hash_listdir_cleanup is raising the assertion or when it's gather_ondisk_files05:09
claygin a few months I won't know if it was one of those or parse_on_disk_filename05:09
claygacoles_away: oh crap - i probably should have named that parse_ondisk_filename (drop the _ in on_disk)05:09
claygbah _gather_ondisk_files and gather_ondisk_files :\05:12
claygon and get_ondisk_files too!05:12
hoclayg: I wanted to say the message is unique string (L2081-2082) http://paste.openstack.org/show/197387/ when i investigate a trouble, I can use the string for grep.05:13
clayg_get_ondisk_file -> get_ondisk_files -> gather_ondisk_files -> _gather_ondisk_files05:14
claygthat's way simple05:14
mattoliverauclayg: lol, so logical :P05:15
claygho: yeah I'm not sure how much it matters to yield_hashes - the point is some hashdir had some garbage in it and was skipped :P05:16
claygho: I *really* don't understand if maybe the second call to gather_ondisk_files in yield_hashes maybe never happens if the path is invalid?05:16
claygho: probably on acoles_away will be able to refactor it05:16
claygs/path is invalid/path contains an invalid file set/05:17
hoclayg: i think so too :-)05:18
*** shakamunyi has quit IRC05:18
claygho: hehe05:20
claygmaybe if ECDiskFileManger just returns the gather_ondisk_files results dict instead of just the files list?05:21
claygI wonder if it'd be wise try and bury the tombstone expiration in gather_ondisk_files - and hash_cleanup_listdir get's a little simpler05:22
*** shakamunyi has joined #openstack-swift05:22
clayg_gather_ondisk_files is sorta trixy with it's little lambda's over the filename05:24
claygand it's updating of the passed in context05:24
claygthat acoles_away :\05:24
mattoliverauclayg: yeah, that did my head in while reading it for the first time :)05:25
claygi think i sorta glassed over trying to grok it and went stright to the tests :D05:25
*** thumpba has quit IRC05:28
claygyay verified!05:40
mattoliveraunice! I for one will +2 it :)05:44
claygbah - it's too much hash_cleanup_listdir can't both find all the files that can be reaped and also select the .data matching the frag_index - unless the result dict can return a list for .data05:53
kota_clayg: are you working on 165188?05:55
claygkota_: yeah thinking about ho's comments and just trying to make the most of acoles work on the gather_ondisk_files methods05:55
kota_clayg: your log seems similer the thing I'm just now writing comments on 16518805:56
claygkota_: oh good - maybe you can figure out the right thing to do05:56
claygi think i'm going to give up and move on down the chain05:56
kota_clayg: ok, I am going to push it right now even though I don't finish my walking though.05:57
kota_clayg: done, right now :D05:58
kota_clayg: I hope it could help your work to figure out the right thing.05:58
*** ktsuyuzaki has joined #openstack-swift06:03
ktsuyuzakiclayg: anyways, I am going to continue to think about ho's comment.06:03
ktsuyuzakiclayg: ah, I am kota_ even the name was changed.06:04
*** kota_ has quit IRC06:05
*** ktsuyuzaki has quit IRC06:05
*** kota_ has joined #openstack-swift06:05
kota_retreiving my name expired w/ timeout.06:06
*** ktsuyuzaki has joined #openstack-swift06:08
ktsuyuzakiwow... my wifi condition seems to have problems...06:09
*** kota_ has quit IRC06:11
claygwhoa06:11
*** kota_ has joined #openstack-swift06:14
*** ktsuyuzaki has quit IRC06:17
*** ktsuyuzaki has joined #openstack-swift06:17
mattoliverauktsuyuzaki or kota_ or whoever you are, pull yourself together man! you seem to becoming two :P06:17
*** kota_ has quit IRC06:18
*** jamielennox is now known as jamielennox|away06:20
ktsuyuzakimattoliverau: wow... ktsuyuzaki and kota_ are same person. ktsuyuzaki is a sub nick on my irc client when kota_ didn't be expired for some reason.06:20
*** silor has joined #openstack-swift06:21
ktsuyuzakihmm...I'm stopping to retry to login until my the network fixed. So sorry.06:22
*** ktsuyuzaki has quit IRC06:22
claygmattoliverau: lol06:23
*** shakamunyi has quit IRC06:25
*** Akshat has joined #openstack-swift06:42
*** nshaikh has joined #openstack-swift06:53
*** SkyRocknRoll has joined #openstack-swift06:54
*** SkyRocknRoll has joined #openstack-swift06:54
*** kota_ has joined #openstack-swift07:00
kota_I'm comming back.07:00
hokota_: welcome back!07:01
mattoliverauYay! Your you again!07:02
*** Akshat has quit IRC07:03
kota_ho, mattoliverau: thanks ; )07:04
*** joeljwright has joined #openstack-swift07:20
*** km has joined #openstack-swift07:31
*** jordanP has joined #openstack-swift07:38
*** ppai_ has quit IRC07:44
openstackgerritMerged openstack/swift: Fix AttributeError and logging in ECAppIter  https://review.openstack.org/16854307:52
*** ppai_ has joined #openstack-swift07:57
claygoh - that's good08:04
claygoh goodness, that was a big change :P08:05
openstackgerritClay Gerrard proposed openstack/swift: Update contianer sync to use internal client  https://review.openstack.org/14379108:07
*** jistr has joined #openstack-swift08:09
claygtorgomatic: patch 166576 is all conflict-y I don't even know08:10
patchbotclayg: https://review.openstack.org/#/c/166576/08:10
openstackgerritMerged openstack/swift: Add Swift Design Principles to CONTRIBUTING.md  https://review.openstack.org/16822108:10
claygcschwede: good morning!08:13
cschwedeclayg: Good Morning - still awake?08:13
claygyeah - i have a thing in the mornig so i'll get started kinda late tomorrow08:16
claygwanna get a jump start08:16
openstackgerritClay Gerrard proposed openstack/swift: Add Fragment Index filter support to ssync  https://review.openstack.org/16518808:17
*** haigang has quit IRC08:18
*** haigang has joined #openstack-swift08:18
*** haigang has quit IRC08:19
openstackgerritHisashi Osanai proposed openstack/swift: Removed an unused variable in decode_segments_from_fragments  https://review.openstack.org/16881008:22
*** admin6_ has joined #openstack-swift08:23
kota_cschwede: still here?08:52
cschwedekota_: Hey Kota! Yes08:53
kota_cshwede: morning08:53
kota_cshwede: your comment on 16518808:53
*** ppai_ has quit IRC08:53
cschwedekota_: i just revoked the comment08:54
cschwedea minute ago :)08:54
kota_cshwede: the "break" at replicated is to stop the for-loop hash_cleanup_listdir08:54
kota_cshwede: oh, really08:54
cschwedeyes, i just realized that as well08:54
*** haigang has joined #openstack-swift08:55
kota_cschwede: oh, sorry for my nosy08:55
cschwedekota_: no worries, good to get some confirmation!08:55
kota_cschwede: : ) In addition, I have a thing to wonder on the patch.08:56
kota_Could you see my comments on patch set 13?08:56
kota_cshwede: espicially about test/unit/obj/test_diskfile.py08:57
cschwedekota_: checking08:57
kota_cshwede: thanks08:58
kota_cschwede: On the EC, diskfile won't have both .meta and .ts because gather_ondisk_files ignores .meta newer than .ts.08:59
kota_cschwede: However the diskfile changes in the patch seems prior to .meta than .ts...09:00
kota_cschwede: I'm not sure it is the right thing but still wondering...09:00
cschwedekota_: regarding the comment in test_diskfile - i think it is called in reverse order, thus newer timestamps are checked first09:05
claygoh yeah I ment to point to acoles_away that there was some comments on the older change sets that he should look at09:05
cschwedekota_: your comment is right if the older timestamps are checked first, but i think this is not the case09:06
*** ppai_ has joined #openstack-swift09:07
kota_cshwede: I still think the reverse order case...09:07
kota_cshwede: in gather_ondisk_file09:08
kota_cshwede: set_valid_fileset() is called only when .durable or .ts found09:09
kota_cshwede: right?09:09
kota_cshwede: and then, if .ts found before .durable found, context['meta'] is assgined None becase have_valid_fileset() is False.09:10
kota_cshwede: in any timestamp cases...i think.09:11
cschwedekota_ yes, but have a look at gather_ondisk_files, that calls _gather_on_disk_file - it will start with the newest file first09:11
kota_cschwede: yes, ts2 is newer than ts1. so the first ts2.meta will appeared in _gather_on_diskf_file.09:13
kota_cschwede: it will be set context['meta'] but set_valid__fileset is not called.09:13
kota_cschwede: and then, ts1 will appear in _gather_ondisk_file it'll make a valid_file set like as context = {'.ts': ts1}09:15
kota_cschwede: oh, sorry I'm looking at _gather_on_disk_file, right now.09:16
kota_cschwede: i.e. ts2.meta is set but dropped when ts1.ts is set and it results in {'.ts': ts1}, i think.09:18
*** bkopilov has quit IRC09:18
kota_because .meta doesn't trigger have_valide_fileset() to be True...09:21
*** bkopilov has joined #openstack-swift09:23
cschwedehmm09:27
cschwedeis there ever a .meta without a .durable context?09:27
kota_cschwede: wait a minutes, I might find the test code on feature/ec branch unit test.09:27
kota_cschwede: In my memory .durable allows to be newer .meta.09:29
kota_cschwede: similar test is here, https://github.com/openstack/swift/blob/feature/ec/test/unit/obj/test_diskfile.py#L731-L73509:30
cschwedekota_: yes, but i’m wondering if there is ever a .meta without a .durable? i don’t think so? and then set_valid_fileset is set in line 2007?09:31
cschwedekota_: your linked test is not the same - the tombstone has the same timestamp, not an older one09:31
kota_cschwede: yes doesn't same, ah, I might miss something...thinkingg...09:32
kota_cschwede: yes, if .durable exists _gather_on_diskf_file call set_valid_fileset.09:36
*** bkopilov has quit IRC09:37
*** bkopilov has joined #openstack-swift09:39
*** acoles_away is now known as acoles09:39
kota_cschwede: I jsut realized I might have misunderstanding, so sorry for that. Maybe it need to take atime to look at more deeply.09:40
acolesmorning!09:41
cschwedekota_: no worries, it’s good to talk about the code!09:41
cschwedeHello Alistair!09:41
kota_acoles: morning!09:41
acolescschwede: hi, just scrolling back,09:41
acoleskota_: hi09:42
kota_acoles: hi09:42
openstackgerritMerged openstack/swift: Removed an unused variable in decode_segments_from_fragments  https://review.openstack.org/16881009:46
acolescschwede: kota_ : i see you were discussing gather_ondisk_files - anything i can help explain?09:47
acolesclayg: yeah the call to hash_cleanup_listdir followed by gather_ondisk_files in yield_hashes has been annoying me all weekend, i just needed a little more time to refactor HCL so i could make a single call to get qhat yield_hashes wants09:49
acoless/qhat//what/09:49
cschwedeacoles: thanks, i think i got it. i’m currently thinking if it might make sense to add a few comment lines into _gather_on_disk_file09:51
acolescschwede: i was going to write a book about it ;)09:52
cschwedehaha, very nice!09:52
acolescschwede: seriously i'll add comments09:53
acolescschwede: kota_ : the gather_ondisk_files -> _gather_ondisk_file makes more sense when you see how simple it is to refactor and share code with the replication get_ondisk_files, but clayg wouldn't let me go that far (yet) ;P10:09
*** dmorita has quit IRC10:17
claygacoles: oh i see how you're putting it on me now10:29
*** ppai_ has quit IRC10:29
acolesclayg: ;)10:30
acolesclayg: thanks for cleaning up the unbound 'files' reference in yield_hashes.10:31
* acoles slaps himself10:31
*** km has quit IRC10:32
*** km has joined #openstack-swift10:32
*** geaaru has joined #openstack-swift10:37
*** bkopilov has quit IRC10:37
*** haigang has quit IRC10:40
*** ppai_ has joined #openstack-swift10:41
*** haomaiwang has quit IRC10:47
*** bkopilov has joined #openstack-swift10:47
claygacoles: well then ho made me change it again10:53
acolesclayg: you mean relocating the excepts?10:53
claygso is everyone happy with 16518810:53
claygacoles: yeah putting everything in one big try10:54
claygi liked getting the assertion error strs in there it turned out10:54
acolesyeah i'm cool with that10:54
acolescschwede: according to this https://docs.python.org/2/library/unittest.html#unittest.TestCase.assertRaises self.assertRaises as a context manager is new in 2.7, but I'm sure I have seen it in swift recently10:55
acolesclayg: i'm happy with 165188 but I am author (or am I ? I have lost track !)10:59
acolesgerrit says i am10:59
acolesi'm annoyed with myself by the duplication in calling hcl then gather_ondisk_files11:00
acoleswhich i could fix now or later.11:00
cschwedeacoles: ah yes, you’re right! i think i saw something similar in swiftclient recently11:05
acolescschwede: but swiftclient still tests py26 i think?11:05
acolescschwede: anyway, since we have just moved those tests i'd prefer not to have to change them in 165188,11:06
cschwedeacoles: fine with me - as i said in the comments, it’s not a blocker for me11:07
cschwedeacoles: just checked - this is where i saw it: https://github.com/openstack/python-swiftclient/blob/master/tests/unit/test_swiftclient.py#L1184-L1185 but that’s not a context manager.11:09
cschwedeheh, the amount of available reviewers to approve patch 165188 is somewhat limited - at least three people submitted patchsets ;)11:12
patchbotcschwede: https://review.openstack.org/#/c/165188/11:12
*** kei_yama has quit IRC11:13
*** ho has quit IRC11:15
openstackgerritKota Tsuyuzaki proposed openstack/swift: WIP: older tombstone is valid rather than newer meta  https://review.openstack.org/16885311:18
kota_cschwede: I wrote a unit for my idea at 16885311:19
kota_cschwede: it might be wrong but i wonder if you could review again whether the assumption is right or not.11:20
kota_patch 168853 is passed in my env so _get_ondisk_files() absolutely return older tombstone rather than newer .meta if no .durable or newer .ts exists.11:23
patchbotkota_: https://review.openstack.org/#/c/168853/11:23
acoleskota_: that test *should* fail because of line 2020 in diskfile.py https://github.com/openstack/swift/blob/feature/ec/swift/obj/diskfile.py#L202011:24
kota_acoles: good test?11:25
kota_acoles: L2020 drops .meta, yes, the newest .meta should be dropped so...11:26
acoleskota_: sorry, ignore my last remark, it should pass11:26
acoleskota_: the .ts will be returned, the .meta will be left on disk11:26
kota_acoles: ok, it fits on my idea.11:27
*** km has quit IRC11:27
cschwedekota_: i think that behavior is as expected (because of the missing .durable)11:27
kota_cschwede: ok, returning back the test_yield_hashes_yields_meta_timestamp on patch 16518811:29
*** SkyRocknRoll has quit IRC11:29
patchbotkota_: https://review.openstack.org/#/c/165188/11:29
kota_I guess, this test doesn't have .durable, right?11:29
kota_if it is true, L1010 on test_diskfile of 165188 patch set14 should be ts1.ts because no .durable file and .ts comes up on the gathering job.11:32
cschwedekota_: i justo observed that you need a .durable and .data to ignore the .ts. I added the following lines to your patch: http://paste.openstack.org/show/197521/11:33
cschwedethat only works if there is a .data, and not if there is only a .durable (which makes sense to me)11:33
kota_cschwede: thanks!11:35
kota_cschwede: yeah, the paste fits my idea. the .data works with the same timestamp .durable it makes me sense. Hoever..11:36
kota_cschwede: test_yield_hashes_yields_meta_timestamp seems not to have .durable, that is the last thing I still wonder...11:37
acoleskota_: line 1010 in tests_diskfile.py is testing replication policy not EC11:38
kota_Oh my god...11:39
kota_acoles: ya, absolutely11:39
kota_acoles, cschwede: so sorry to work for that, it is definitly my mistake...11:40
cschwedekota_: no worries, it’s better we think one more time over all of this!11:41
acoleskota_: see line 1419. I put those tests in because some of the behaviour around .meta files is possibly confusing, so the tests illustrate the behavior11:46
mattoliverauevening all, did you guys need to check out patch 165188, I'm like the only one who hasn't submitted a patchset :P11:46
patchbotmattoliverau: https://review.openstack.org/#/c/165188/11:46
acolesmattoliverau: if you can the i'm sure it would add to your tally of beers in vancouver11:47
kota_acoles: I see, it makes me sense, much appreciated.11:47
acoleskota_: tbh i think that yield_hashes on master is broken when there is a t2.meta and t1.ts - ssync will attempt to replicate the file at t2, but error when trying to open the file since there is no .data11:49
acoleskota_: but I guess no one has used ssync with fast-post meta files much11:51
kota_acoles: lol11:51
acoleskota_: but *thank you* for checking these tests thoroughly11:52
kota_acoles: I didn't notice that too, let's fix that after EC relased on Kilo :-)11:52
kota_acoles: sure, I'm very interested those patches on EC, it's really fun to review awsome patches :-)11:54
*** jistr has quit IRC12:07
*** jistr has joined #openstack-swift12:08
*** Gues_____ has joined #openstack-swift12:15
mattoliverauacoles: you mention in the review "the call to hash_cleanup_listdir followed by gather_ondisk_files can be simplified".. are you planning on doing that now or post beta (or a follow up patch)? Just needing to know if we want to get the change merged now12:15
mattoliveraus/review/patchset comment/12:16
kota_Thanks guys, I'm going to leave my office to go back home : )12:23
acoleskota_: thanks have a good night12:23
*** kota_ has quit IRC12:24
*** panbalag has joined #openstack-swift12:24
acolesmattoliverau: i'm working on it but can be a follow up patch since we are accumulating +'s on 16518812:25
*** Gues_____ has quit IRC12:25
acolesmattoliverau: i'll also add some more commentary to gather_ondisk_files...12:26
acolesmattoliverau: so yeah, maybe follow up is best, keep the train rolling forwards12:26
cschwedeyeah, more merges!12:28
mattoliverauKk, sounds like a plan, thanks acoles, I'll +A and then head to bed :)12:28
acolesmattoliverau: thanks for that!12:29
cschwedeacoles: which patch in https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:feature/ec,n,z is the next most important from your point of view?12:29
acolescschwede: idk! i guess the reconstructor 131872 or container sync path 14379112:33
acolesi assume clayg is not still awake ? ^^12:33
cschwedeacoles: thx, i was thinking the same12:33
mattoliverauDone, night guys! Nice work btw12:33
acolescschwede: i will probably head to 13187212:33
acolesmattoliverau: g'nite12:33
mattoliverauI hope clayg is asleep.. His was online my entire day.. Well pretty much.. He's a machine!12:34
acolesi think "clayg" is actually a globally distributed team12:34
cschwedehaha, that would explain a lot :D12:35
*** Trixboxer has joined #openstack-swift12:36
claygye of little faith12:36
acoles!12:37
openstackgerritClay Gerrard proposed openstack/swift: wip: ec reconstructor probe test  https://review.openstack.org/16429112:37
openstackgerritClay Gerrard proposed openstack/swift: Erasure Code Reconstructor  https://review.openstack.org/13187212:37
claygi've just been busy fixing shit12:37
*** sandywalsh has quit IRC12:37
acolesclayg: ye of little sleep12:37
cschwedejeez!12:37
claygwell how can anyone sleep when there's shit like this -> https://gist.github.com/clayg/959a5d77353a91a4b10a12:38
claygi sent an email to tsg he normally patches shit I have no idea - in the meantime Im just working around it12:39
clayganyway i'm trying to get something going for the reconstrcutor - it needs a bunch more tests12:39
claygbut all the probetests are passing for me relibably I think?12:39
claygya'll figure out what you wanna do with the ssync-fi thing12:39
*** sandywalsh has joined #openstack-swift12:40
claygi'ma take a nap for a few - i won't be on till like idk - 1pm or something PST - so i'll see most of you when you come online in the morning12:40
acolesclayg: its en route to land12:40
acolesclayg: mattoliverau +"A'd12:40
claygpeluse: welcome back (when you get here)12:40
claygsweet - i hope I rebased on the right revision12:41
acolesclayg: rest well12:41
claygwhy *did* we merge the liberasure dependency into master?12:42
clayganyway - we've probably got to update something to mention that whatever liberasure devel headers are required to install swift now?12:42
claygidk, seems strange12:43
claygk - later12:43
*** ppai_ has quit IRC12:45
cschwedeclayg: i submitted it to feature/ec, don’t know why it needed to be on master12:48
cschwedehttps://review.openstack.org/#/c/164172/12:48
*** shakamunyi has joined #openstack-swift12:57
*** annegentle has joined #openstack-swift13:08
*** haigang has joined #openstack-swift13:12
*** shakamunyi has quit IRC13:13
openstackgerritMerged openstack/swift: Add Fragment Index filter support to ssync  https://review.openstack.org/16518813:17
openstackgerritYuan Zhou proposed openstack/swift: EC: Allow proxy to read from all SN in EC policy  https://review.openstack.org/16825413:24
*** chlong has joined #openstack-swift13:36
*** nshaikh has quit IRC13:51
*** dencaval has joined #openstack-swift13:52
*** jrichli has joined #openstack-swift13:56
*** haomaiwang has joined #openstack-swift14:01
openstackgerritChristian Schwede proposed openstack/swift: Check if REST API version is valid  https://review.openstack.org/16892514:17
*** zaitcev has joined #openstack-swift14:21
*** ChanServ sets mode: +v zaitcev14:21
*** haomaiwang has quit IRC14:24
*** haomaiw__ has joined #openstack-swift14:25
*** G________ has joined #openstack-swift14:30
*** lcurtis has joined #openstack-swift14:36
*** egon has quit IRC14:39
*** me has joined #openstack-swift14:42
*** me is now known as Guest5445914:43
*** G________ has quit IRC14:44
*** egon has joined #openstack-swift14:45
*** haomaiwa_ has joined #openstack-swift14:47
*** zul has quit IRC14:47
*** Akshat has joined #openstack-swift14:48
AkshatHi Clayg14:49
AkshatHi Ctennis14:49
Akshatclayg:I still could not overcome that error14:49
*** haomaiw__ has quit IRC14:49
*** haigang has quit IRC14:53
*** zul has joined #openstack-swift14:53
*** G________ has joined #openstack-swift14:53
notmynamegood morning14:58
notmynamelooks like I just barely missed clayg14:59
notmynamein answer to the question posed last night...15:00
*** mahatic has joined #openstack-swift15:00
notmynameyes, pyeclib landed on master because of two things15:00
*** reed has joined #openstack-swift15:01
AkshatHi notmyname15:01
*** zul has quit IRC15:02
*** zul has joined #openstack-swift15:03
notmynamefirst, the global-requirements issues with the feature branch (since resolved, but was an issue). also, we had the openstack requirement for getting dependencies in by march 1915:03
notmynamesince there was no release between then and the one with ec, we landed the requirement on master15:04
AkshatHey I am facing issue with my swift cluster15:04
Akshatwhen I am loading the cluster...I am getting errors to update container,account server15:04
openstackgerritAlistair Coles proposed openstack/swift: Minor cleanup to EC yield_hashes and gather_ondisk_files  https://review.openstack.org/16894115:08
*** zul has quit IRC15:08
*** zul has joined #openstack-swift15:08
*** Akshat has quit IRC15:08
acolesmattoliverau: cschwede: kota: ^^ cleanups from patch 16518815:09
patchbotacoles: https://review.openstack.org/#/c/165188/15:09
*** Akshat has joined #openstack-swift15:10
*** haomaiwa_ has quit IRC15:18
*** haomaiwa_ has joined #openstack-swift15:18
zaitcevnotmyname: I knew there would be a reason to add PyECLib, just forgot what it was.15:18
*** annegentle has quit IRC15:19
*** annegentle has joined #openstack-swift15:19
*** shakamunyi has joined #openstack-swift15:25
*** chlong has quit IRC15:26
claygjust missed me by like 3 hours15:46
*** haomaiwa_ has quit IRC15:46
claygcschwede: you can't put that on me!15:48
cschwedeclayg: what? why not? it’s your patch, thus you get the kudos15:49
claygcschwede: I think patch 168925 was acctually closer on than patch 16850915:49
patchbotclayg: https://review.openstack.org/#/c/168925/15:49
claygyou mean I get the *blame* when it breaks someone's client - i see what you're doing.15:50
cschwedeclayg: heh, well, i didn’t look at it from that side15:51
claygcschwede: here we'll try that15:52
clayg;)15:52
*** shakamunyi has quit IRC15:52
claygi'm honestly just not working on it - really do think what you had done with the method extraction (maybe in constraints) would be better.15:53
cschwedeclayg: shall i push a new patchset on top of yours? or restore my change?15:54
claygyeah we should keep everything on he same patch - just push over that change id we already have going15:55
*** Akshat has quit IRC15:58
cschwedeclayg: hmm, just trying to cherry-pick my patch on top of yours. actually i’m not sure what to keep, for example commit msg15:59
claygcschwede: i'm pretty sure my commit msg was crap - i exected it to change - was yours any good?16:00
cschwedeclayg: i’m trying to make the best out of both msgs16:01
claygnice - you rock16:01
acolesclayg: peluse: i'm looking at patch 131872 and see self.job['policy'].ts_to_fname in ssync_sender - didn't ts_to_fname go away or did i miss something?16:02
patchbotacoles: https://review.openstack.org/#/c/131872/16:02
acolesline 35216:02
cschwedeclayg: i will submit a new patchset later, leaving for dinner now16:04
*** annegentle has quit IRC16:07
claygcschwede: np, thanks!16:08
*** vinsh has joined #openstack-swift16:09
*** shakamunyi has joined #openstack-swift16:10
*** Akshat has joined #openstack-swift16:13
jordanPhi guys. If you could take a look at https://review.openstack.org/#/c/168990/ (swift-devstack integration issue, w.r.t PyEClib), that would be great :)16:18
jordanP^^ chmouel,16:18
ctennissorry Akshat I don't have any more ideas, it sounds to me like something is misconfigured.16:19
chmoueljoearnold: wouldn't need the full build-essential thing ?16:20
*** Akshat has quit IRC16:22
jordanPchmouel, hummm :)16:23
chmouelcause make is nice but i guess gcc/glibc-devel etc.. would be needed?16:23
jordanPI think make is enough... I can double check that16:24
jordanPchmouel, gcc is already in files/debs/general16:25
jordanPbut I will double check anyway16:25
chmoueljordanP: cool, would be good you can test on a pristine vm16:25
jordanPsure16:26
*** jistr has quit IRC16:44
peluseacoles, I have some catch up reading to do and my head is *killing* me :)  Besides wine still running through my veins, didn't get to sleep til about 3am.  I'm mostly worthless today I think, just FYI16:57
acolespeluse: sounds like you have a had a great weekend!16:57
acolespeluse: i'm writing some unit tests for the ssync_sender changes in patch 131872 fyi16:58
patchbotacoles: https://review.openstack.org/#/c/131872/16:58
*** erlon has joined #openstack-swift16:59
jordanPchmouel, 'make' is enough. I've left a comment on the code review17:05
claygacoles: there's about 10 different tests that will look like test.unit.obj.test_reconstructor.test_reconstruct_fa_(no_errors) - but I won't be writing them till this afternoon17:08
notmynamegood morning (again)17:08
notmynamepeluse: glad you made it back17:08
claygpeluse: when you say you weren't seeing issues I think that just means you weren't testing it enough - that or you're using the isa-l that doesn't seem to exibit the issue - which is also cool!17:08
acolesclayg: ok so if i concentrate on test_ssync_sender.py we don't overlap effort?17:09
claygpeluse: because basically if you want to rebuilt 5 and you have 0, 1, 2, 4 you get back garbage - so it really all just depends on what nodes you turn off17:10
claygacoles: k, makes sense - thanks!17:10
claygacoles: unless you were going to try to get that tombstone cleanup out of that otherwise beautiful bit of work in the _gather_ondisk_file cleanup!17:10
claygk, i'm out of pocket for a bit then i think17:11
peluseclayg, yeah I switched to ISAL a while back...17:12
claygpeluse: good call apparently!17:13
*** G________ has quit IRC17:13
peluseclayg, acoles so what do you guys want me looking at right now?17:13
acolesclayg: heh. i'd love to do that but i figure ssync_sender tests might be a priority - did you see my comment above re "self.job['policy'].ts_to_fname in ssync_sender "17:13
acolesclayg: like, that can't be tested17:14
*** tsg_ has joined #openstack-swift17:16
acolespeluse: i was out of loop myself over weekend, clayg probably has best view on the state of things. everything below 131872 (recon) has landed in that chain17:17
peluseOK cool.  Thinking I'd start wiht patch 16894117:17
patchbotpeluse: https://review.openstack.org/#/c/168941/17:17
notmynamepeluse: the starred patches on the review dashboard are where we are. acoles has one patch. and then there's the reconstructor17:17
notmynameI think we really need to get those landed today17:18
*** Gues_____ has joined #openstack-swift17:19
acolesnotmyname: today which time zone? anyone in hawaii? :P17:22
notmyname:-)17:22
notmynameclayg's time zone is what matters, since he'll be doing the merge to master. but, to be fair, I'm not actually sure clayg follows "time zones" (or anything resembling a normal schedule) ;-)17:23
claygnotmyname: torgomatic need to rebase the multi-rage get last I checkede17:24
swifterdarrellclayg: best accidentally-appropriate typo ever17:25
acoles"multi-rage" "17:25
notmynameclayg: right, but there's still an issue in it17:25
claygthe recon stuff needs more tests i think - but acoles is working on some of them - maybe peluse or I can do some more17:25
notmynameas of right now, I don't think the beta will have multi-range or container sync17:25
pelusehe, clayg said 'recon' and not 'reconstructor'17:26
claygnotmyname: I *think* i'm ready to maybe start pulling out some piecies of feature/ec and see if we can start to play around with the patch chain on ec-review - are you going to get that setup today (is it already?)17:26
claygpeluse: DAMNIT - reconstrcu;lajksdfj - that fucking word sucks - we can't call it recon either17:26
acolespeluse: he's been doing that a lot17:26
claygthis is the most critical issue facing the future of ec right now - we have to rename it to the recoder17:27
chmoueljordanP: cool, will review later on :)17:27
peluse#vote17:27
acolesno, no - object-fixer !! :P17:27
claygobject-do-the-right-thing-button17:27
pelusewe could always being back "the ruggedizer"17:27
acolesNO17:27
peluse:)17:28
notmynamethe hard work, high stress, and lack of sleep have made you all crazy17:28
peluseacoles, nice stuff on the refactor of yield_hashes and gather17:28
acoleslets make the name of the daemon configurable17:29
acolesthat always avoids making a decision17:29
* peluse googles visitor pattern17:29
claygpeluse: *right* - acoles is on his a game17:30
peluseno shit!17:30
acolespeluse: thx but clayg diss'd me leaving the "ugly" tombstone handling so i 'll have to go fix :P17:30
* clayg mostly uses the make-the-crap-i-wrote-last-year-less-annoying-to-me-now pattern17:30
claygacoles: seriously it's like a fart in the middle of bethoven17:31
peluseacoles, you mean the first part of cleanup_ondisk_files()?17:31
acolespeluse: google 'gang of four patterns'17:31
claygnotmyname: awww no container-sync!?  what was wrong with container-sync17:31
pelusethat sounds like it should be rated X17:31
acolespeluse: yeah17:32
claygnotmyname: shit i forgot about the stupid bug with acccount-reaper17:32
claygnotmyname: anyway - what about the ec-review branch?17:32
notmynameclayg: next on my todo for today. on it17:32
acolespeluse: :) when we're done with EC go read their book and your life will change17:32
claygacoles: meh17:32
pelusethat's what I need... I life changing OO book :)17:33
acolesclayg: actually i'm just gonna delete that first piece of cleanup?ondisk and see if any tests fail17:33
clayglol17:34
clayggood start!17:34
peluseacoles, I dopn't really understand the history behind that first part anyway, assumed it was an opmitization for a special case of some kinds17:35
claygpeluse: someone needed to do it - that way seemed least likely to do the wrong thing?17:35
claygok i'm off - see you gusy later17:36
*** annegentle has joined #openstack-swift17:37
*** zhill has joined #openstack-swift17:38
*** silor has quit IRC17:41
*** annegentle has quit IRC17:43
*** annegentle has joined #openstack-swift17:44
*** admin6_ has quit IRC17:44
*** jordanP has quit IRC17:54
*** geaaru has quit IRC18:00
*** Gues_____ has quit IRC18:01
openstackgerritChristian Schwede proposed openstack/swift: Check if REST API version is valid  https://review.openstack.org/16850918:02
cschwedeclayg: ^^ i refactored the patch just a tiny bit18:03
*** tsg_ has quit IRC18:05
*** tsg has joined #openstack-swift18:05
*** greghaynes has quit IRC18:07
*** jrichli has quit IRC18:10
openstackgerritAlistair Coles proposed openstack/swift: Even more cleanup to EC on-disk file cleanup  https://review.openstack.org/16903518:11
acolesclayg: so peluse approved before i could cleanup the cleanup ^^ it wasn't as straightforward as i hoped18:12
peluseis it ever?18:15
*** Gues_____ has joined #openstack-swift18:16
acolespeluse: nope18:19
*** jrichli has joined #openstack-swift18:21
openstackgerritMerged openstack/swift: Minor cleanup to EC yield_hashes and gather_ondisk_files  https://review.openstack.org/16894118:46
openstackgerritChristian Schwede proposed openstack/swift: Check if REST API version is valid  https://review.openstack.org/16850919:17
openstackgerritAlistair Coles proposed openstack/swift: WIP: EC specific ssync_sender fixes and tests  https://review.openstack.org/16905219:18
acolespeluse clayg ^^ WIP back later19:19
pelusek19:19
*** mahatic has quit IRC19:20
*** acoles is now known as acoles_away19:20
tdasilvacschwede, clayg: re 168509, shouldn't the response be a 501? 404 seems strange to me...19:21
*** nikhil|afk has quit IRC19:21
cschwedetdasilva: i think 5xx errors are server errors, but the error is on the client side in this case?19:22
cschwedeactually i’m thinking if 422 is makes sense19:23
notmynamecschwede: ya, 400 or 422 seem reasonable (over 404)19:26
tdasilvacschwede: yeah, either 412 or 422 would be better in my mind, 404 seems deceiving19:26
*** Gues_____ has quit IRC19:26
tdasilvaor 400 like notmyname said19:26
notmynamecschwede: tdasilva: so without listing an account, ... , then swift will currently return 41219:31
notmyname(which I think could be better, but perhaps the consistency is beneficial?19:32
cschwedenotmyname: i was using 412 in my first patchset as well. i don’t know - there are good reasons for 400,412 and 422 imo19:33
cschwedeat least we can agree that 404 is not the best idea ;)19:33
notmynameif I did it all over again, I'd vote 422. but 412 seems more consistent with existing behavior19:34
tdasilvanotmyname: yeah, in that case 412 is returned regardless of version thou, right?19:34
notmynametdasilva: yes19:34
notmynametdasilva: it's 412 if it can't figure out what the request was fo19:34
tdasilvaright19:34
notmynameeg saio/xyzzy/19:34
*** Gues_____ has joined #openstack-swift19:36
tdasilvaI'd vote for 40019:42
*** dencaval has quit IRC19:42
*** teploxoh has joined #openstack-swift19:42
*** annegentle has quit IRC20:04
*** Gues_____ has quit IRC20:11
*** Gues_____ has joined #openstack-swift20:15
*** annegentle has joined #openstack-swift20:25
*** tsg has quit IRC20:31
*** tsg has joined #openstack-swift20:35
*** Gues_____ has quit IRC20:35
*** Gues_____ has joined #openstack-swift20:38
*** annegentle has quit IRC20:41
*** annegentle has joined #openstack-swift20:52
brianclinereading the 1.1 spec, 400 seems to make the most sense.. mostly since it stipulates the request should not be resent without some change/correction and makes no assumption about whether the rest of the request was valid or not20:53
brianclineiirc, 412 preconditions are assumed to be header-based (like when being provided an expected etag for a PUT)20:54
claygare we freaking out!?20:55
brianclinethat said, who actually follows the rfc on this stuff20:55
claygi'm checking out patch 131872 again20:57
patchbotclayg: https://review.openstack.org/#/c/131872/20:57
*** bsdkurt has quit IRC21:00
*** bsdkurt has joined #openstack-swift21:01
openstackgerritMonty Taylor proposed openstack/python-swiftclient: Add socket-level read timeout parameter  https://review.openstack.org/16867321:02
*** tsg has quit IRC21:04
*** acoles_away is now known as acoles21:06
*** rdaly2 has joined #openstack-swift21:07
*** Gues_____ has quit IRC21:09
claygacoles: what are you doing here!?21:11
sweeperlurking imo21:12
sweeperlike everyone else21:12
acolesclayg: writing tests...21:12
notmynameacoles: can you help me grok https://review.openstack.org/#/c/169035/1 ?21:12
notmynameacoles: I' trying to be helpful but feel that I came into that discussion partway through21:13
*** tsg has joined #openstack-swift21:13
notmynameacoles: what's the "single junk in dir that may violate ondisk contract"21:14
acolesnotmyname: ok, so i nearly called that one 'remove the fart from beethoven' cos thats how clayg described the previous cleanup21:14
claygawwwwww we should have waited to merge patch 168941 is acoles was going to keep working on it - my fault for +2ing it I suppose21:14
patchbotclayg: https://review.openstack.org/#/c/168941/21:14
acoles;)21:15
notmynameacoles: ya, I liked that ;-)21:15
acoleslooking21:15
claygacoles: but you didn't remove it - you just added comments21:15
clayg:P21:15
claygacoles: which tests broke when you just pulled it out?21:15
notmynameacoles: I was just trying to figure out the scenario. 'cause I think it needs a test. and I can write it, but I don't understand the "why" yet21:15
vinshacoles: Head back to Colorado and drink some more beer :)21:15
*** Gues_____ has joined #openstack-swift21:16
acolesvinsh: that a helluva way for me to go for beer, but i have a glass of wine by my side ;)21:16
vinshJust fine ;)21:16
claygacoles: I'm pretty sure there's at least one test that specifically validates reclaimed tombstones - but I don't remember anything being to specific about that wierd "there has to be one file in the directory in order to reap too old tombstones" behavior of the current crap21:16
*** rdaly2 has quit IRC21:16
acolesclayg: notmyname there was a test that had a single .meta on the dir iirc. that breaks get_ondisk_files but legacy hash_cleanup_listdir allows it because of the 'if only one file don't even try get_ondisk_files'21:17
acolesclayg: notmyname so i was very careful not to change behavior wrt legacy even though i don't get the legacy behavior, hence the comment, but cleaning up the filename parsing to use our super new parse_ondisk_filename21:19
acoleslike, i think if you had an obj dir with only junk.foo in it, that would just be ignored on master21:20
*** annegentle has quit IRC21:21
acolesnotmyname: clayg: what i *wanted to do* was just call gather_ondisk_files, test the results for a .ts that is older than reclaim_age and if so move it to the obsolete files list, it was sweet, but some tests broke and tbh it doesnt seem a priority to make the code more beautiful :)21:22
acolestry removing the 'if .ts' condition and i expect the same tests will blow up21:23
claygacoles: yeah do what you wanted to do - if there is a stupid test that only works on legacy - then move it to the replicated case of the mixin and rewrite a more reasonable test for the ec case21:26
claygyou don't have to do any of this of course - you're right about it not being the #1 priority21:26
claygacoles: where did you end up on some ssync tests you said?21:26
acolesclayg: totally agree it should be done but i'm focussed on recosntructor and adding thise ssync tests in patch 16905221:27
patchbotacoles: https://review.openstack.org/#/c/169052/21:27
claygredbo: YES!  http://bouk.co/blog/monkey-patching-in-go/21:28
claygacoles: right on21:28
acolesclayg: peluse : so i have a question about the sync_revert case with ssync ...21:29
acolessender starts with a durable and frag archives index 1 and 2, sends FA 2 to the receiver, then wants to cleanup FA2 from local node right?21:30
peluseyes21:31
acolesclayg: peluse : the 'cleanup' should not remove durable, right? cos FA 1 is still on local node, correct?21:31
pelusecurrect, jsut the FA21:31
peluseI'm working on the cleanup stuff right now, its got a few small issues21:32
acolesbut if there is no FA 1 on local node then we *should* cleanup the durable? or can that not happen - no of course it can happen yeas?21:32
pelusewhat?21:32
acolespeluse: is the starting state is that local node has only FA 2 and durable, sends FA 2 to receiver, then cleanup needs to remove the durable??21:33
acoless/is/if/21:33
claygi'm realizing I'm not entirely following the high level flow - I get why a job would have a partition/path and and frag_index, but why does it have a "suffix" key - our jobs should be segregated mainly on the node(s) they're connecting to - which has everything to do with which fi's are in the part - which in turn tells us what kind of job it is and therefore who and how many nodes to connect to21:33
peluseyes21:34
claygwhat does the suffix have to do with it - it should always be suffixES21:34
claygas in - all the suffixes in this part that will meet the critiera for this job (i.e. it has some of these fragment indexes in it)21:34
acolespeluse: was that 'yes' to me or clayg ? :)21:34
peluseacoles to you21:35
peluseclayg, not even sure that's used anywhere, might be left over junk21:35
claygpeluse: oic21:36
*** jamielennox|away is now known as jamielennox21:36
peluseyeah, I'm not seeing it used anywhere....21:36
*** annegentle has joined #openstack-swift21:36
peluserecall this job processor changed just a few times :)21:36
claygpeluse: yeah i don't understand the cardinality of the jobs - these tests that run over the canned and shared crazy set of all kind of objects all up in the setUp is going to be impossible to maintain21:37
clayglike anytime we want to test a new sceanario the most ovbious place to add it is to the shared setup - but then *every* test in the case has to change21:38
claygI'm going to start ripping that testcase apart21:38
peluseclayg, yeah, it turned turn out to be very maintainable.  sorry 'bout that21:39
claygpeluse: s/very/not very/ ?21:40
acolespeluse: ok. cool. i got part way to fixing that and testing in patch 169052, was going to carry on with it now ie. cleaning up where ssync_sender updates removes delete_list items so that durable delete depends on whether there is another frag archive21:40
patchbotacoles: https://review.openstack.org/#/c/169052/21:40
peluseyeah, not... my brain is pretty fried today21:40
claygpeluse: no problem21:40
*** jamielennox is now known as jamielennox|away21:46
*** jamielennox|away is now known as jamielennox21:53
mattoliverauMorning21:54
acolesmattoliverau: hi21:55
mattoliverauacoles your still here! Yay overlap :)21:55
*** teploxoh has quit IRC22:05
*** Gues_____ has quit IRC22:13
*** Gues_____ has joined #openstack-swift22:14
*** annegentle has quit IRC22:19
jrichlimattoliverau acoles: hi!  Yes, acoles is working late!! Ok, I am out ...22:21
*** jrichli has quit IRC22:21
*** tsg has quit IRC22:24
*** tsg has joined #openstack-swift22:31
*** panbalag has quit IRC22:39
*** annegentle has joined #openstack-swift22:41
*** panbalag has joined #openstack-swift22:44
openstackgerritSamuel Merritt proposed openstack/swift: EC: support multiple ranges for GET requests  https://review.openstack.org/16657622:46
brianclinedoes anyone remember (maybe in the last 11-12 months) any bugs/changesets related to json unicode warnings emitted from DatabaseBroker.update_metadata?22:46
notmynamebriancline: ya, something about unicode rings a bell22:47
brianclineif memory serves the ones I saw were ultimately raised from within simplejson22:48
brianclinecame up during some upgrade testing on account/container servers22:48
brianclineI might've been using an older tag.. I'll try against the latest to double-check22:49
notmynamebriancline: I72b322e7513f7da32e8dc75c6bf0e7e016948c88 and Id2ac129828dbdf55b609d839ce4d9d42437ee0a3 and I82359c87a0919d71693e49ecf08e0f1eedc9d18e and I82359c87a0919d71693e49ecf08e0f1eedc9d18e22:49
brianclineand to capture output.. it got lost somewhere in my 5 billion open terminals22:49
brianclineah22:50
notmynamebriancline: those are the gerrit change ids. search for them on review.openstack.org22:50
notmynamebriancline: that's from the last year that has "unicode" in the subject22:50
brianclinenotmyname: aha, this sounds precisely like what I saw22:51
brianclinenotmyname: thanks for grabbing those22:51
brianclinebased on those dates I was definitely on an older tag22:54
*** annegentle has quit IRC22:55
*** panbalag has quit IRC22:55
claygwasn't there something with ipv6 that made us grow an is_local_device function somewhere?23:12
*** tsg has quit IRC23:15
claygnm, i found it - from swift.common.ring.utils import is_local_device23:16
zaitcevyes, ho did it23:20
zaitcevright23:20
*** petertr7 has quit IRC23:21
*** tsg has joined #openstack-swift23:22
*** logan2 has quit IRC23:25
*** mattoliverau has quit IRC23:29
*** mattoliverau has joined #openstack-swift23:29
*** ChanServ sets mode: +v mattoliverau23:30
notmynameFYI https://wiki.openstack.org/wiki/Swift/version_map23:31
*** ho has joined #openstack-swift23:31
*** logan2 has joined #openstack-swift23:33
mattoliverauok, I'm dangerously under caffinated.. think it's time for a coffee run, bbs23:38
acolesmattoliverau: me too!23:38
mattoliverauacoles: your still here, are you attempting to beat the clayg record of lack of sleep?23:39
acolesmattoliverau: no chance :P23:40
*** Nadeem_ has joined #openstack-swift23:43
hogood morning guys!23:46
*** theanalyst has quit IRC23:46
mattoliverauho: Morning23:46
* mattoliverau seems to failing at this coffee thing23:46
homattoliverau: morning!23:47
*** km has joined #openstack-swift23:50
*** theanalyst has joined #openstack-swift23:52
torgomaticso is the K release going to be the last one where we support python 2.6?23:52
*** Tahmina has joined #openstack-swift23:52
notmynametorgomatic: IOW you can stop writing py26 code in about 3 weeks?23:53
torgomaticnotmyname: can I start the long, tedious process of extracting simplejson's tentacles from our codebase23:53
torgomaticwe'll see how many Unicode-related bugs I can uncover as I go23:54
*** jrichli has joined #openstack-swift23:54
notmynamelucid support dies in a few weeks, right? what about cent/rhel? what's reasonable to expect there?23:54
notmynameie LTS distro releases that have/had py2623:54
*** shakamunyi has quit IRC23:55
torgomaticyeah, Lucid has at most until the end of April for support23:56
*** annegentle has joined #openstack-swift23:56
hoWhat is the highest priority review today?  (may be the patch 169035?)23:59
patchbotho: https://review.openstack.org/#/c/169035/23:59

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