Monday, 2016-10-31

*** klrmn has joined #openstack-swift00:11
*** jerrygb has quit IRC00:17
*** vint_bra has joined #openstack-swift00:19
*** PsionTheory has joined #openstack-swift00:33
*** vint_bra has quit IRC01:18
*** vinsh has joined #openstack-swift01:20
*** vinsh has quit IRC01:24
*** klrmn has quit IRC02:13
*** PsionTheory has quit IRC02:30
openstackgerritKaren Chan proposed openstack/swift: Mirror X-Trans-Id to X-Openstack-Request-Id  https://review.openstack.org/38735403:02
*** vinsh has joined #openstack-swift03:13
*** jerrygb has joined #openstack-swift03:33
*** jerrygb has quit IRC03:37
openstackgerritPete Zaitcev proposed openstack/swift: Fake GetRing in order to test on systems without Swift  https://review.openstack.org/39170003:38
*** Jeffrey4l has joined #openstack-swift03:44
*** SkyRocknRoll has joined #openstack-swift03:47
kota_hello04:05
kota_back from barcelona04:06
kota_clayg: nice vsaio installs liberasurecode from source. if you finde any problems in the master source, please notify me to fix them.04:07
*** vinsh has quit IRC04:12
*** vinsh has joined #openstack-swift04:16
*** chsc has joined #openstack-swift04:18
*** chsc has joined #openstack-swift04:18
*** jerrygb has joined #openstack-swift04:37
*** chsc has quit IRC04:39
*** links has joined #openstack-swift04:48
*** jerrygb has quit IRC05:04
*** vinsh has quit IRC05:14
*** SkyRocknRoll has quit IRC05:15
*** SkyRocknRoll has joined #openstack-swift05:16
*** SkyRocknRoll has quit IRC05:22
*** nakagawamsa has joined #openstack-swift05:32
*** bkopilov_ has joined #openstack-swift05:45
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix stats calculation in object-reconstructor  https://review.openstack.org/28394605:50
*** chirag has joined #openstack-swift05:58
chiragI have Icehouse version of swift and I want to use it with Keystone Mitaka(v3) and I am facing auth failure issues. Can someone help ??05:59
*** silor has joined #openstack-swift06:11
*** silor1 has joined #openstack-swift06:17
*** silor has quit IRC06:19
*** silor1 is now known as silor06:19
*** vinsh has joined #openstack-swift06:45
*** nakagawamsa has quit IRC06:47
*** vinsh has quit IRC06:50
chirag[Repost]I have Icehouse version of swift and I want to use it with Keystone Mitaka(v3) and I am facing auth failure issues. Can someone help ??06:56
*** jerrygb has joined #openstack-swift07:02
*** jerrygb has quit IRC07:08
*** tesseract has joined #openstack-swift07:11
*** tesseract is now known as Guest5832407:11
openstackgerritChristian Schwede proposed openstack/swift: Respect server type for --md5 check in swift-recon  https://review.openstack.org/24072607:26
kota_chirag: i'm not familiar with the history for keystone auth devel, but it looks keystone v3 with swift has been supported since Juno (past icehouse), https://github.com/openstack/swift/blob/master/CHANGELOG#L74807:28
*** Jeffrey4l has quit IRC07:34
kota_chirag: do you have a chance to try either v2 with Keystone Mitaka or Swift newer than Juno?07:36
chiragHello, unfortunately no I have to do mitaka(v3) with swift icehouse. Is there any way ?07:41
*** LZ has joined #openstack-swift07:46
*** vinsh has joined #openstack-swift07:46
*** LZ has quit IRC07:49
*** sams-gleb has joined #openstack-swift07:56
*** vinsh has quit IRC08:01
*** hseipp has joined #openstack-swift08:37
*** vinsh has joined #openstack-swift08:58
*** vinsh has quit IRC09:02
*** bkopilov has quit IRC09:24
*** bkopilov_ has quit IRC09:24
*** bkopilov_ has joined #openstack-swift09:25
*** bkopilov has joined #openstack-swift09:25
*** chirag has quit IRC09:51
*** vinsh has joined #openstack-swift09:59
*** vinsh has quit IRC10:03
*** eranrom has joined #openstack-swift10:31
*** jerrygb has joined #openstack-swift10:57
*** vinsh has joined #openstack-swift10:59
*** vinsh has quit IRC11:04
*** chlong has joined #openstack-swift11:40
*** cdelatte has joined #openstack-swift11:53
*** vinsh has joined #openstack-swift12:00
*** jerrygb has quit IRC12:01
*** vinsh has quit IRC12:05
*** MVenesio has joined #openstack-swift12:06
*** kei_yama has quit IRC12:08
*** links has quit IRC12:50
*** MVenesio has quit IRC12:51
*** caiobrentano_ has joined #openstack-swift12:56
*** vinsh has joined #openstack-swift13:02
*** jerrygb has joined #openstack-swift13:03
*** jerrygb has quit IRC13:07
*** vinsh has quit IRC13:09
*** jerrygb has joined #openstack-swift13:11
*** jerrygb has quit IRC13:11
*** klamath has joined #openstack-swift13:13
*** klamath has quit IRC13:13
*** klamath has joined #openstack-swift13:14
*** bkopilov_ has quit IRC13:14
*** bkopilov_ has joined #openstack-swift13:15
*** amoralej is now known as amoralej|lunch13:22
*** vint_bra has joined #openstack-swift13:32
*** vinsh has joined #openstack-swift14:04
*** jerrygb has joined #openstack-swift14:08
*** amoralej|lunch is now known as amoralej14:11
*** briancurtin has quit IRC14:19
*** tuan_luong has joined #openstack-swift14:22
*** briancurtin has joined #openstack-swift14:22
*** d0ugal has joined #openstack-swift14:22
*** _JZ_ has joined #openstack-swift14:26
*** jamielennox is now known as jamielennox|away14:34
*** sgundur has joined #openstack-swift14:48
*** sams-gleb has quit IRC14:53
*** sams-gleb has joined #openstack-swift14:54
*** sams-gleb has quit IRC14:58
*** Tuan_ has joined #openstack-swift14:59
*** sgundur has quit IRC15:00
*** tuan_luong has quit IRC15:01
*** jerrygb has quit IRC15:07
*** jerrygb has joined #openstack-swift15:08
*** Tuan_ has quit IRC15:08
*** klrmn has joined #openstack-swift15:09
*** ukaynar has joined #openstack-swift15:12
*** sams-gleb has joined #openstack-swift15:14
*** sgundur has joined #openstack-swift15:22
*** sgundur has quit IRC15:29
*** sgundur has joined #openstack-swift15:30
openstackgerritShashirekha Gundur proposed openstack/swift: Invalidate cached tokens api  https://review.openstack.org/37031915:36
*** StraubTW has joined #openstack-swift15:37
*** chsc has joined #openstack-swift15:37
*** Jeffrey4l has joined #openstack-swift15:38
notmynamegood morning15:39
*** Jeffrey4l has quit IRC15:39
*** Jeffrey4l has joined #openstack-swift15:40
*** Jeffrey4l has quit IRC15:41
*** lcurtis has joined #openstack-swift15:42
*** Jeffrey4l has joined #openstack-swift15:42
*** urth has left #openstack-swift15:42
*** chsc has quit IRC15:48
*** Guest58324 has quit IRC15:56
*** LZ has joined #openstack-swift16:11
*** sgundur has quit IRC16:17
*** sgundur has joined #openstack-swift16:18
*** sgundur has quit IRC16:20
*** sgundur has joined #openstack-swift16:21
*** klrmn has quit IRC16:21
LZHi everyone16:22
LZ Can you recommend me some good online training of swift storage for beginner ?16:24
LZIs there some online course? thanks very much16:24
notmynameLZ: what sort of training? operating it? writing apps for it? understanding the architecture? wanting to contribute?16:24
LZunderstanding the architecture and operating it16:25
*** nikivi has joined #openstack-swift16:26
notmynameLZ: I don't know of anyone who provides training for it like that, but you might try https://www.openstack.org/marketplace/training/f/a/a/swift16:27
notmynamethose are probably pretty strongly coupled to other openstack projects, though16:27
LZOk, I will try it, thanks16:27
notmynameLZ: https://www.swiftstack.com/docs/introduction/openstack_swift.html is a great starting place16:27
notmynameLZ: as is swift.openstack.org16:27
claygmorning!16:28
claygor... Hola!16:28
notmynameclayg: yo!16:28
clayghappy Halloween!16:28
notmynameclayg: do probetests work for you? they seem to pass in the community cluster, so it's likely something on my machine16:28
notmynameclayg: I woke up at 4:07 today. how about you?16:29
clayglast time i was running them was on hummingbird16:29
patchbothummingbird16:29
notmynamelol16:29
claygi'm doing pretty good - i woke up at 7:30 with the kiddos16:29
claygpatchbot: is hummingbird the new docker?  did someone say hummingbird?16:29
LZin prague is 17:30 :-)16:30
claygeverywhere it is 16:27 UTC16:30
* clayg goes to check ntp is running on this machine16:30
LZyes, it is16:30
*** links has joined #openstack-swift16:31
*** chlong has quit IRC16:32
claygntpd[17822]: adjusting local clock by 174.196515s16:34
claygbetter16:34
*** hseipp has quit IRC16:40
timburkegood morning16:41
*** links has quit IRC16:42
tdasilvanotmyname: FWIW, i ran probetests on master a few minutes back and it passed ok for me16:44
notmynametdasilva: thanks16:44
*** sgundur has quit IRC16:48
*** sgundur has joined #openstack-swift16:48
*** tuan_luong has joined #openstack-swift16:51
*** david-lyle has joined #openstack-swift16:51
*** Jeffrey4l has quit IRC16:52
*** sgundur has quit IRC16:53
*** tuan_luong has quit IRC16:54
*** d0ugal has quit IRC16:54
*** d0ugal has joined #openstack-swift16:58
*** d0ugal has quit IRC16:58
*** d0ugal has joined #openstack-swift16:58
*** sgundur has joined #openstack-swift16:58
*** hseipp has joined #openstack-swift16:59
*** chsc has joined #openstack-swift17:01
*** chsc has joined #openstack-swift17:01
*** mvk has quit IRC17:01
openstackgerritJohn Dickinson proposed openstack/swift: Add checksum to object extended attributes  https://review.openstack.org/33632317:05
openstackgerritJohn Dickinson proposed openstack/swift: Add checksum to object extended attributes  https://review.openstack.org/33632317:07
notmyname@torgomatic_ ^17:10
*** klrmn has joined #openstack-swift17:16
*** jordanP has joined #openstack-swift17:19
*** jordanP has joined #openstack-swift17:20
*** hseipp has quit IRC17:21
zaitcevWas there ever an Etherpad for Hummingbird in Barcelona?17:46
zaitcevIt's not in https://etherpad.openstack.org/p/ocata_swift_summit_topics17:46
claygzaitcev: we only really talked about how someone needs to start pushing up some patches to delete some code soon and the layout of the object-server/replicator/repconn17:47
clayggeneral consensus I *think* was that we mostly like the repconn connection on not an "object-server" but it's maybe not great to have it on the replicator either because it's harder to manage/reason about (e.g. "once" mode doesn't even start a repconn listener)17:48
zaitcevokay17:48
claygzaitcev: yeah you're all caught up!17:49
zaitcevBTW, I'm going to add you to review https://review.openstack.org/39170017:49
claygit wasn't a big topic17:49
patchbotpatch 391700 - swift (feature/hummingbird) - Fake GetRing in order to test on systems without S...17:49
clayg^ missed you nadeem hurricanerix17:49
claygzaitcev: awesome sounds good17:49
claygI think i pushed something up like "better error message handling" in some probe test when on-disk rings were missing because of the order that test patches policies and not rings17:50
zaitcevclayg: I see you added multiply policy into replicator, so I started adding them to proxy (put a map[int]Ring inside ProxyDirectClient basically).17:50
claygzaitcev: no that was redbo !17:50
claygzaitcev: don't work on the proxy - delete the proxy!17:51
zaitcevclayg: you did and I put -1 on it so you can circle to it and remove 1 unneded function call17:51
claygoh cool - thanks!17:51
zaitcevhttps://review.openstack.org/#/c/390903/17:51
patchbotpatch 390903 - swift (feature/hummingbird) - Better error messages in go/probe17:51
zaitcevAnyway, I don't even care about policies, I just need something, anything, a place to attach my liberasurecode stub17:52
claygzaitcev: awsome!  learning go via gerrit review while trying to refactor the replicator is going to be so productive!?17:52
zaitcevAnd my existing cluster has 2 policies, so I ended doing policies....17:52
*** sgundur has quit IRC17:52
openstackgerritTim Burke proposed openstack/swift: Treat invalid limit parameters as errors  https://review.openstack.org/29922517:53
openstackgerritTim Burke proposed openstack/swift: Return 400 on bad requests  https://review.openstack.org/39193217:53
notmynametimburke: oh, https://review.openstack.org/#/c/391932/ won't be controversial at all. ;-)18:00
patchbotpatch 391932 - swift - Return 400 on bad requests18:00
*** asettle has joined #openstack-swift18:00
notmynameI'm interested to see what temptest tests do with it18:00
timburkenotmyname: no chance at all :P18:00
timburkei'm telling you, though: a 412 is just wildly inappropriate there18:01
*** LZ has quit IRC18:01
*** sgundur has joined #openstack-swift18:01
claygtimburke: and?18:02
timburkeclayg: i figure not speaking http correctly is probably a bad idea18:03
claygnotmyname: do you have a sense for just how many environments where we currently run unittests are going to skip all of those modules where your doing the xattr check?18:03
*** Harin has joined #openstack-swift18:09
claygtimburke: I feel like I have this discussion with you a lot - I'm not really sure if we disagree or if you keep forgetting18:11
*** jordanP has quit IRC18:11
claygnotmyname: half of me thinks we should let timburke merge some of his api cleans up so he can learn from his mistakes like we have?18:12
claygtimburke: also fwiw - i made the same observation years ago about percondition failed - it *is* very sad that we didn't know http better five years ago18:12
claygi try to watch out for imapproprriate use of http status codes *as much as possible* when reviewing changes to the API going forward - ¡Vive y aprende!18:14
*** Harin has quit IRC18:17
notmynameclayg: with torgomatic_'s patch to stop mocking xattrs, I expect every existing SAIO to break unless they run tests on an xfs partition. my updates mock those out so they skip instead of break. but yeah, I expect every dev box to need to be updated in order to run all the tests (and I'm ok with that)18:20
notmynameclayg: so i'll be making another CI test that has xfs in it. and that will be the "real" one. the tactic I took was to do the simplest thing possible without causing a national crisis18:21
timburkeclayg: "using a 412 to indicate a error condition other than some If-X header did not match is a bit of a mis-use; unless tempest already validates that as the documented error code for a PUT to a version container when the version target does not exist we should consider changing it to a 400 with a better description." -- https://review.openstack.org/#/c/265015/18:24
patchbotpatch 265015 - swift - Autovivify X-Versions-Location container18:24
claygnotmyname: it's a pretty good strategy - you should write that on the change that fixes and rebase torgomatic_'s patch to depend on that18:24
timburkeyou! you were the one that gave me hope!18:24
claygtimburke: and doesn't tempest validate it?18:24
notmynameclayg: yeah, the reason I bundled it in was twofold: the base patch from torgomatic_ is small and the existing stuff without torgomatic_'s patch "works" without my changes (by virtue of not actually testing xattr stuff)18:25
claygtimburke: also if I told you to change an existing error code i was drunk18:25
timburkeno idea. i guess we'll see18:25
notmynameclayg: so it comes down to that I can see going either way, but I thought one patch is simpler than two and combined it's not too big to fit in your head18:25
claygnotmyname: ok, that makes sense18:26
notmynametimburke: there is no hope. we're stuck with our warts18:26
claygnotmyname: i mean - it's reasonable as well - i'm not sure splitting them or keeping them together is acctually *better*18:26
timburkeV2! V2! V2! :P18:26
claygnotmyname: I think your change to the test infrastructure is cirtainly "a bigger deal" than torgomatic_'s patch18:26
claygbut hopefully not "a national crisis" ;)18:27
timburkewe've got enough of those already, thank you18:28
notmynameclayg: I'd prefer to simply edit the image so we have xfs, but I got a *lot* of pushback on that from infra people. along the lines of "dont' do something different than every other project". so, yeah, national crisis (in openstack terms). so my plan is to have one job that skips stuff and another with xfs that tests everything18:28
claygnotmyname: yes, i agree with the strategy - I think it deserves to be on the patch18:31
notmynameclayg: meaning more words in the commit message?18:31
notmynameor a "depends-on" for the CI gate job patch (that I haven't written yet)?18:32
claygnotmyname: yeah something in the commit messsage ... and yeah probably need the CI job ...18:33
notmynameok18:33
claygnotmyname: like I think it's a significant enough change to how swift is tested that it's worth a commit titled "everything you know about unitests is different now"18:33
claygnotmyname: maybe see if anyone else agrees?  torgomatic_ ?18:33
notmynamelooks like the functests failed in the gate (but not in my saio), so there's definitely at least one more patch set18:34
*** ukaynar has quit IRC18:34
claygnotmyname: rock n' roll18:34
torgomatic_I wonder if doing stuff to increase the number of 'S' printed out would help... if I see a test run with hundreds of '.' and one or two 'S', I'm going to assume it's pretty much run the whole thing18:35
claygtimburke: I'm not sure what point I was trying to make on patch 265015 - or what bugs we have that need to be fixed18:35
patchbothttps://review.openstack.org/#/c/265015/ - swift - Autovivify X-Versions-Location container18:35
torgomatic_however, if it's a third 'S', then I can see something's up18:35
torgomatic_(not "third" as in "first, second, third", but as in "one in three of these things is an S")18:36
notmynametorgomatic_: "why can't you people write more code with shared responsibilities?!?"18:36
torgomatic_notmyname: ?18:36
notmynametorgomatic_: sounded like that's what you're advocating ;-)18:36
torgomatic_notmyname: ...no?18:37
notmynametorgomatic_: if we'd only call setting xattrs on more of our tests, we'd get more skips :-)18:37
torgomatic_notmyname: more that skipping the module seems to print one "S" regardless of the number of unit tests run18:37
torgomatic_s/run/in that module/18:37
* torgomatic_ can't brain today18:37
notmynametorgomatic_: ah, right. so if every single test in that module had an S, then it would be better18:37
notmynameI see what you're getting at18:37
torgomatic_notmyname: yep, or at least louder18:38
notmynameno, it was me not following you18:38
*** ukaynar has joined #openstack-swift18:38
notmynamelouder? it's already a capital letter. that's like shouting, man. (...maybe we could do some escape codes for bold?)18:38
notmyname;-)18:38
notmynameyeah, so in a class setup it might be better. I'll look in to that18:39
claygnotmyname: I guess "it's hard to know that we're skipping everything we need to w/o the xattr checksumming change" is a good reason to keep them together18:39
timburkenotmyname: clayg: 14 func test failures on https://review.openstack.org/#/c/391932/ (i suppose i should have run those before submitting), but ZERO tempest failures18:39
patchbotpatch 391932 - swift - Return 400 on bad requests18:39
claygtimburke: does that mean tempest doesn't use versioned containers?18:40
notmynameI'm pretty sure they have some versioning tests in tempest18:40
*** sgundur has quit IRC18:43
timburkehttps://github.com/openstack/tempest/blob/422ded8/tempest/api/object_storage/test_object_version.py#L51-L9518:44
timburkethey only ever test with both containers set up18:45
*** sgundur has joined #openstack-swift18:46
notmynamejrichli has someone at ibm working on swift tests in tempest. might be someone who could make those better, then18:46
* notmyname lunch18:46
*** asettle has quit IRC18:47
*** asettle has joined #openstack-swift18:48
*** asettle has quit IRC18:48
*** asettle has joined #openstack-swift18:48
jrichlinotmyname: that is clu_.  I can see what she has going on18:49
openstackgerritJoel Wright proposed openstack/swift: WIP: Add Preamble and Postamble to SLO and SegmentedIterable  https://review.openstack.org/36537118:49
*** sgundur has quit IRC18:50
claygtimburke: well patch 391932 touches lots of stuff besdies versioned containers - I was looking through the negative tests in temptest and they're kinda sparse - but i'm still surprised they didn't break18:50
patchbothttps://review.openstack.org/#/c/391932/ - swift - Return 400 on bad requests18:50
claygI *suppose* there's probably not that many clients out there doing a bunch of requests they expect to return an error - so maybe this is a special exception18:51
*** asettle has quit IRC18:52
*** asettle has joined #openstack-swift18:52
*** vint_bra has quit IRC19:02
notmynameclayg: it's talk like that which gives timburke hope!19:09
claygnotmyname: you're right - i'm sorry timburke - there is no hope19:10
*** silor has quit IRC19:12
*** vint_bra has joined #openstack-swift19:13
timburkeSo we beat on, boats against the current, borne back ceaselessly into the past.19:15
claygnotmyname: acoles_: so what is alexis handle?19:15
claygbecause I don't know if it's expected, observed or observed, expected?19:15
notmynameclayg: that is a great question. IDK19:18
*** ukaynar has quit IRC19:20
*** sgundur has joined #openstack-swift19:23
*** vint_bra1 has joined #openstack-swift19:25
openstackgerritTim Burke proposed openstack/swift: SLO: Concurrently HEAD segments  https://review.openstack.org/39168219:26
*** vint_bra has quit IRC19:29
*** sgundur has quit IRC19:37
openstackgerritClay Gerrard proposed openstack/swift: Suppress unexpected file warnings for rsync temp files  https://review.openstack.org/39165819:43
openstackgerritClay Gerrard proposed openstack/swift: Include debug message for rsync tempfiles  https://review.openstack.org/39196019:43
*** amoralej is now known as amoralej|off19:46
openstackgerritMerged openstack/python-swiftclient: Correct the example keystone session code imports  https://review.openstack.org/39159119:47
*** sgundur has joined #openstack-swift20:14
*** cdelatte has quit IRC20:17
*** clsacramento has joined #openstack-swift20:24
*** mvk has joined #openstack-swift20:31
*** sgundur has quit IRC20:35
notmynametorgomatic_: "Ran 4866 tests in 70.084s     OK (SKIP=1213)"20:37
notmynamethat should work for you ;-)20:37
*** sgundur has joined #openstack-swift20:37
*** d0ugal has quit IRC20:40
openstackgerritJohn Dickinson proposed openstack/swift: Add checksum to object extended attributes  https://review.openstack.org/33632320:40
*** d0ugal has joined #openstack-swift20:42
claygnotmyname: wait, if the "problem" is just xattr > 4k?  why not put write_metadata's 'xattr_size' kwarg just use a swift.common.constraint and have if fixed to 4k in the environments running tests?20:43
claygor even better - have your code force it dynamically *unless* the environment overrides it?20:44
notmynameclayg: if you're running with default constraints and with /tmp as ext4, then the only thing that breaks are the crypto metadata tests (since those expand the metadata beyond the blocksize limit in ext4)20:46
notmynamethat's where I started, but AFAIK the ext4 limit is blocksize and not 4k (I should check on this) and tempfs is just right out. doesn't work at all20:46
notmynameI've heard a rumor that fedora has /tmp as tempfs20:47
notmynamezaitcev: ^ is that true?20:47
*** jerrygb__ has joined #openstack-swift20:48
notmynameIn the current ext2, ext3, and ext4 filesystem implementations, the20:48
notmyname       total bytes used by the names and values of all of a files extended20:48
notmyname       attributes must fit in a single filesystem block (1024, 2048 or 409620:48
notmyname       bytes, depending on the block size specified when the filesystem was20:48
notmyname       created).20:48
zaitcevnotmyname: http://marc.info/?l=linux-mm&m=146734777402582&w=220:48
notmynamezaitcev: ah yes. I remember that. kernet patch to add xattrs to tempfs20:49
zaitcevnotmyname: oh, you mean ext4. I dunno, sorry. There is some limit, but you can run on ext4. Our biggest and baddest to date Swift at a customer site is on ext4.20:49
*** jerrygb has quit IRC20:49
zaitcevalthough, this was probably still with chaining20:49
notmynamezaitcev: no, I was asking about what /tmp is mounted as in fedora, cent, rhel20:49
notmynamein ubuntu (xenial) it defaults to ext420:50
zaitcevnotmyname: yes, it is mounted as tmpfs20:50
notmynamegot it20:50
zaitcevalso /var/run points to /run, which is also tmpfs20:50
notmynamesame on ubuntu20:50
notmynameok, so I can't simply skiptest on just the crypto ones. gotta skiptest on anything that uses xattrs on tempfiles20:50
notmynameclayg: ^ that's why it can't simply be a constraint check. rhel variants use tempfs where there's zero metadata support20:51
zaitcevor like https://review.openstack.org/#/c/328508/20:51
patchbotpatch 328508 - swift (feature/hummingbird) - Force /var/tmp as the test directory because of xattr20:51
zaitcevsee redbo's comment20:51
notmynameyeah20:52
*** jerrygb__ has quit IRC20:52
notmynamebut I'm guessing you'll still run in to an ext* limit there, right?20:52
zaitcevYes... But we fully support XFS in RHEL 7, so it usually happens when people create a gigantic root on ext4, then run with mount_check=false20:53
zaitcevjust use XFS20:54
notmynameyeah, exactly20:54
zaitcevI moved my $HOME from ext4 to XFS just so I don't have to deal with this anymore with I do ./.unittests20:54
notmynameI'm totally fine with breaking swift dev and test environments where they aren't using xfs. it's what we expect every production deployment to use. there's no (technical) reason I know of to keep trying to make up things to support non-xfs in tests20:56
notmynamebut I may be wrong. I've been wrong many times before, and I'll be wrong again20:57
*** _JZ_ has quit IRC21:02
claygi'm still not sure I fully understand all the justifications here21:03
*** sams-gleb has quit IRC21:03
claygwe have some test environments that are testing on files systems that don't *have* xattrs?  great make a way for the test a) direct all tests to use a filesystem location that *does* have xattr support or b) skip tests if your absolutely unable to provide such a file system (gate my not be able to do that, that's ok by me)21:04
*** sgundur has quit IRC21:04
claygor we have some test environments that are testing on filesystems that can only hold 4K worth of xattrs?  great make it so that tests use less xattrs - operators should have a way limit this already (granting some single digit slop for crypto/etc) - so let's just those tools to enforce the same limits on unittests (which should really not care if the limit is 1K instead of 65K)21:06
*** jamielennox|away is now known as jamielennox21:06
notmynameenvironments where we don't even have xattrs are rhel-based. they have /tmp mounted as tempfs which doesn't support any xattrs at all21:07
notmynameenvs where we have xattrs, but it's limited to 4k, are anything where /tmp is mounted with ext*. this includes the gate images21:08
notmynamewhen I talked to the infra team and qa people about setting up a different job that has xfs in it, they were all for that. but not with us dropping the existing job that doesn't have xfs. so we need a skiptest for that21:10
notmynameone could argue that our unittests shouldn't care what the limit is at all and just work. but then we end us mocking out the xattrs (and just testing the mock) and the same logic gets us to mocking out a whole filesystem21:11
notmynamecurrent state, right now on master, is that we halfway mock out a filesystem for tests21:11
notmynamethis patch drops the half we mock (xattrs) and therefore requires that xattrs are supported on the underlying tempdir21:11
notmynameone option I considered was to set up a new gate image that sets up an xfs partition somewhere and passes it in via an envvar. then our tests use that as the tmpdir and work. this is similar to what zaitcev's golang patch he linked does21:12
notmynameso, sure, that would work21:12
notmynamebut we'd still need the "if the xfs-enabled tmpdir envvar isn't set, raise skiptest", and the plumbing is 95% similar to what i proposed21:13
notmynameso my current plan is to make a gate job template to have /tmp as xfs and then the current stuff works21:14
notmynameI think that's the simplest thing that will work and avoids "swift is being different" and actually tests the new functionality we want in21:14
*** caiobrentano_ has quit IRC21:15
notmynameand, for the record, yes, I think much of this is silly. I'd much prefer to land torgomatic_'s original patch and simply say "yeah, of course it broke. use xfs". but since we can't change the existing job template in CI, we can't do that21:15
notmynamehttp://www.quickmeme.com/img/52/52cfa562021c4c144f132c85c40a1ec19d1e1fedb4dc0764ed06e137d1ae826c.jpg21:16
*** openstackgerrit has quit IRC21:18
*** openstackgerrit has joined #openstack-swift21:19
openstackgerritTim Burke proposed openstack/pyeclib: Avoid segfault when raising exceptions  https://review.openstack.org/38518621:21
openstackgerritClay Gerrard proposed openstack/swift: Remove executable flag from some test modules  https://review.openstack.org/39160621:22
zaitcevMaybe I really should just spend a couple of weeks on tmpfs with xattr. It does not seem that hard, just needs some focus and concentration.21:26
mattoliverauAlmost home, in Sydney, one last flight \o/21:29
claygnotmyname: correct - our tests should not need to write >4K of xattrs on any one inode to know the code they're testing is working correctly21:36
claygnotmyname: correct - our tests should have a way to make all "scatch space" on an external mount point that's been configured for xfs21:36
claygnotmyname: maybe we don't *need* to do either of those things to land torgomatic_'s patch, but if we're going to disable ~1/3 of our tests there we probably *do* need to get this other job that *does* do those tests working in the gate before we land torgomatic_'s patch21:37
torgomatic_clayg: yeah, that's definitely a good idea21:38
clayg... so do you wanna stick a -2 on there or should I?21:38
claygalso... thanks for working on this!  :D21:39
claygwow, so no inprocess fuctests have ever stored xattrs on their files they create - awesome21:41
claygi'm all for getting rid of these mocks21:41
*** nikivi has quit IRC21:50
*** nikivi has joined #openstack-swift21:51
torgomatic_yeah, the mocks are pretty gross21:54
torgomatic_although I'm lazy enough that if there were a good way to fix the mocks, I'd have been tempted to do that21:55
*** jerrygb has joined #openstack-swift21:59
*** jerrygb has quit IRC22:04
*** chlong has joined #openstack-swift22:07
*** nikivi has quit IRC22:10
*** StraubTW has quit IRC22:11
claygdo we mostly pass in the open fd int or do we give it a file object?  i figure if we had the name there'd be some chance... the reuse of fd int's seems liekly to be what bone's the mock?22:18
notmynameclayg: from what torgomatic_ told me, the problem is that we get the inode and the fs number, but the kernel resuses both of those. so we don't have enough info to actually give different xattrs to each call to the mocked out xattr22:32
notmynamewe pass in the fs22:32
notmyname*we pass in the fd22:32
torgomatic_clayg: it's not that, it's that the mock isn't plumbed into unlinking at all. Imagine Test1 makes a file, sets some xattrs, then cleans up the file. Test2 then makes a new file with a different name but happens to get the same inode number (ruh roh), so the new file still mock-has the old xattrs22:32
* notmyname needs to commute. will check in later22:33
*** lcurtis has quit IRC22:40
*** jerrygb has joined #openstack-swift22:42
*** klrmn has quit IRC22:45
*** jerrygb_ has joined #openstack-swift22:45
*** klrmn has joined #openstack-swift22:46
*** jerrygb has quit IRC22:48
*** rvasilets___ has joined #openstack-swift22:52
*** klamath has quit IRC22:52
*** geaaru has quit IRC22:58
*** geaaru has joined #openstack-swift23:00
claygI think it's *likely* to see the reuse of a fd int - and not likely *at all* to see the reuse of a filename - but the reuse of a fd int is a problem yes, specifically because of unlink23:08
clayganyway - when I first saw the mock break down I had assumed a global patch/side-effect on unlink would be reasonable - but again we're back to mapping fname -> fd int and all hell breaks loose23:10
claygoh, wait i see - the fd int gets translated to file system inode through fstat23:11
claygso maybe a global side-effect on unlink to clear the inodes' cache is *insane* - but could also work?23:11
claygdid anyone try it?23:11
*** asettle has quit IRC23:11
*** clsacramento has quit IRC23:25
*** clsacramento has joined #openstack-swift23:26
notmynameclayg: I didn't. not sure if torgomatic_ looked in to it23:28
torgomatic_clayg: no, I didn't try it23:29
torgomatic_clayg: also note that the mock was keyed off inode number, not fd number, but the problem is that sometimes we'd get passed an integer fd, and there's no way to turn that back into a filename23:30
torgomatic_if we had filenames, then we'd just use those and be done with it :|23:30
*** chsc has quit IRC23:30
*** nikivi has joined #openstack-swift23:39
*** geaaru has quit IRC23:40
timburkeclayg: on https://review.openstack.org/#/c/391960/ -- if there's "garbage" in the datadir that we care enough about to get annoyed that our warning is getting skipped... aren't we going to be *even more annoyed* that we're going around *purging* it every 30mins or w/e?23:42
patchbotpatch 391960 - swift - Include debug message for rsync tempfiles23:42
timburkethat line of argument just makes me think we need to tighten our regex. and the second one i offered is still loosey-goosey enough that i can't imagine us changing the filename format enough to accidentally start warning about rsync tempfiles again23:44
timburkeat least, not for another 200+ years23:44
timburkehonestly, i'd worry more about rsync changing their tempfile naming convention more than that23:45
openstackgerritMerged openstack/swift: Remove executable flag from some test modules  https://review.openstack.org/39160623:52
openstackgerritMerged openstack/swift: Suppress unexpected file warnings for rsync temp files  https://review.openstack.org/39165823:53
claygoh that's exciting a bunch of patches are in merge conflict now!23:56
openstackgerritClay Gerrard proposed openstack/swift: Make ECDiskFileReader check fragment metadata  https://review.openstack.org/38765523:57
timburkeclayg: just a sign that things are merging! it's great!23:58

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