Monday, 2015-03-16

*** tsg has joined #openstack-swift00:02
*** aschhabr has joined #openstack-swift00:19
*** tsg has quit IRC00:23
*** aschhabr is now known as achhabra00:24
*** aix has quit IRC00:26
*** aix has joined #openstack-swift00:30
*** kota_ has joined #openstack-swift00:35
openstackgerritKota Tsuyuzaki proposed openstack/swift: Fix the prefix of messages caputured from stderr  https://review.openstack.org/16455201:21
*** lcurtis has joined #openstack-swift01:30
*** achhabra has quit IRC01:45
*** ktsuyuzaki has joined #openstack-swift01:59
*** kota_ has quit IRC02:01
*** kota_ has joined #openstack-swift02:02
*** ho has joined #openstack-swift02:02
*** ktsuyuzaki has quit IRC02:04
*** ktsuyuzaki has joined #openstack-swift02:04
*** kota_ has quit IRC02:06
*** kota_ has joined #openstack-swift02:07
*** ktsuyuzaki has quit IRC02:08
*** ktsuyuzaki has joined #openstack-swift02:09
*** kota_ has quit IRC02:11
*** kota_ has joined #openstack-swift02:14
*** ktsuyuzaki has quit IRC02:15
*** ktsuyuzaki has joined #openstack-swift02:18
*** kota_ has quit IRC02:20
*** kota_ has joined #openstack-swift02:21
*** ktsuyuzaki has quit IRC02:22
*** ktsuyuzaki has joined #openstack-swift02:23
*** kota_ has quit IRC02:25
*** kota_ has joined #openstack-swift02:26
*** ktsuyuzaki has quit IRC02:28
*** ktsuyuza_ has joined #openstack-swift02:28
*** kota_ has quit IRC02:31
*** kota_ has joined #openstack-swift02:31
*** ktsuyuza_ has quit IRC02:33
*** ktsuyuzaki has joined #openstack-swift02:33
*** kota_ has quit IRC02:36
*** kota_ has joined #openstack-swift02:40
*** ktsuyuzaki has quit IRC02:42
*** ktsuyuzaki has joined #openstack-swift02:44
*** kota_ has quit IRC02:46
*** kota_ has joined #openstack-swift02:47
*** ktsuyuzaki has quit IRC02:49
*** ktsuyuzaki has joined #openstack-swift02:51
openstackgerritThiago da Silva proposed openstack/swift: refactor PUT method  https://review.openstack.org/16456102:53
*** kota_ has quit IRC02:53
*** kota_ has joined #openstack-swift02:54
*** ktsuyuzaki has quit IRC02:56
*** ktsuyuzaki has joined #openstack-swift02:57
*** kota_ has quit IRC02:58
*** kota_ has joined #openstack-swift02:59
*** ktsuyuzaki has quit IRC03:01
*** ktsuyuzaki has joined #openstack-swift03:01
*** kota_ has quit IRC03:03
*** kota_ has joined #openstack-swift03:04
*** ktsuyuzaki has quit IRC03:06
*** ktsuyuzaki has joined #openstack-swift03:06
*** kota_ has quit IRC03:08
*** kota_ has joined #openstack-swift03:09
*** ktsuyuzaki has quit IRC03:11
*** ktsuyuzaki has joined #openstack-swift03:11
*** kota_ has quit IRC03:14
*** kota_ has joined #openstack-swift03:14
*** ktsuyuzaki has quit IRC03:16
*** ktsuyuzaki has joined #openstack-swift03:16
*** kota_ has quit IRC03:18
*** kota_ has joined #openstack-swift03:21
*** ktsuyuzaki has quit IRC03:23
*** ktsuyuzaki has joined #openstack-swift03:24
*** kota_ has quit IRC03:25
*** lcurtis has quit IRC03:25
*** kota_ has joined #openstack-swift03:26
*** ktsuyuzaki has quit IRC03:28
*** ktsuyuzaki has joined #openstack-swift03:29
*** kota_ has quit IRC03:30
*** kota_ has joined #openstack-swift03:31
*** ktsuyuzaki has quit IRC03:33
*** ktsuyuzaki has joined #openstack-swift03:36
*** kota_ has quit IRC03:37
*** kota_ has joined #openstack-swift03:38
*** ktsuyuzaki has quit IRC03:40
*** ppai has joined #openstack-swift03:40
*** ktsuyuzaki has joined #openstack-swift03:43
*** kota_ has quit IRC03:45
*** kota_ has joined #openstack-swift03:45
openstackgerritJanie Richling proposed openstack/swift: WIP - Provides a simple skeleton of middleware for encryption feature. - encrypt/decrypt functions and keymaster still stubbed-out - functests fail now because some metadata is being encoded,   and the WSGIContext in the Decrypter is causing issues - mass  https://review.openstack.org/15790703:47
*** ktsuyuzaki has quit IRC03:47
*** ktsuyuzaki has joined #openstack-swift03:48
*** haomaiwang has joined #openstack-swift03:49
*** kota_ has quit IRC03:50
*** kota_ has joined #openstack-swift03:51
*** ktsuyuzaki has quit IRC03:52
*** bkopilov has quit IRC04:39
mattoliverautdasilva: I have had a go at rebasing your versions middleware on the EC branch.. I noticed your new refactor put change, so now rebased it off that. I haven't pushed it over your change (yet) and it might be better if you take a look. https://github.com/matthewoliver/swift/tree/feature/ec04:39
mattoliveraumy EC SAIO is failing to run tests on the current HEAD of the ec branch.. once I figure out whats broken on my sysyem I'll run the unit tests on it.04:41
*** dfg has quit IRC04:48
*** dfg has joined #openstack-swift04:48
*** bkopilov has joined #openstack-swift04:55
*** dfg has quit IRC04:57
*** dfg has joined #openstack-swift04:57
*** dfg has quit IRC05:06
*** dfg has joined #openstack-swift05:06
*** dfg has quit IRC05:15
*** aswadr has joined #openstack-swift05:15
*** dfg has joined #openstack-swift05:15
*** dfg has quit IRC05:24
*** dfg has joined #openstack-swift05:24
*** SkyRocknRoll has joined #openstack-swift05:33
homattoliverau: hello, could you review this (https://review.openstack.org/#/c/138342/10)? If there is no conflict with ec work.05:35
homattoliverau: I have kept a test env for this but it become difficult in near future.05:35
*** sluo_wfh has joined #openstack-swift05:46
openstackgerritPrashanth Pai proposed openstack/swift: Make object creation more atomic in Linux  https://review.openstack.org/16224305:52
*** sluo_wfh has quit IRC05:55
*** kota_ has quit IRC06:05
*** sluo_wfh has joined #openstack-swift06:08
*** dfg has quit IRC06:09
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Imported Translations from Transifex  https://review.openstack.org/16408606:10
*** dfg has joined #openstack-swift06:10
*** ppai has quit IRC06:16
*** nshaikh has joined #openstack-swift06:17
*** dfg has quit IRC06:18
*** dfg has joined #openstack-swift06:18
*** dfg has quit IRC06:26
*** dfg has joined #openstack-swift06:28
*** ppai has joined #openstack-swift06:30
mattoliverauho: I'll take a look, and good afternoon :)06:47
*** pcaruana has quit IRC07:14
*** ppai has quit IRC07:31
*** ppai has joined #openstack-swift07:44
homattoliverau: thanks a lot!08:06
*** rledisez has joined #openstack-swift08:07
*** jordanP has joined #openstack-swift08:09
*** joeljwright has joined #openstack-swift08:18
*** geaaru has joined #openstack-swift08:37
*** ppai has quit IRC08:38
*** nellysmitt has joined #openstack-swift08:40
*** joeljwright has quit IRC08:43
*** joeljwright has joined #openstack-swift08:44
*** jd__ has quit IRC08:50
*** jd__` has joined #openstack-swift08:50
*** ppai has joined #openstack-swift08:50
*** jd__` is now known as jd__08:51
*** NM has joined #openstack-swift09:03
*** NM has quit IRC09:11
*** jistr has joined #openstack-swift09:11
*** NM has joined #openstack-swift09:25
*** NM has quit IRC09:37
*** zackmdavis has quit IRC09:57
*** timburke has quit IRC09:57
*** timburke has joined #openstack-swift09:59
*** zackmdavis has joined #openstack-swift09:59
*** joeljwright1 has joined #openstack-swift10:07
*** joeljwright has quit IRC10:09
*** ho has quit IRC10:24
*** SkyRocknRoll has quit IRC10:34
*** ppai has quit IRC10:41
*** ppai has joined #openstack-swift10:55
*** haomaiwang has quit IRC11:06
*** acoles_away is now known as acoles11:15
*** acoles is now known as acoles_away11:17
*** evanjfraser_ has joined #openstack-swift11:21
*** aix has quit IRC11:21
*** evanjfraser has quit IRC11:22
*** me has joined #openstack-swift11:24
*** me is now known as Guest591611:24
*** acoles_away is now known as acoles11:32
*** NM has joined #openstack-swift11:41
*** joeljwright1 has quit IRC11:54
*** ppai has quit IRC12:00
*** ppai has joined #openstack-swift12:04
*** panbalag has joined #openstack-swift12:11
openstackgerritpaul luse proposed openstack/swift: Merge master to feature/ec  https://review.openstack.org/16466712:18
acolespeluse: you around this early? ^^12:19
peluseacoles, yup, howdy12:19
*** ppai has quit IRC12:19
acolespeluse: good morning - i am just fixing the merge conflict on multi frag index patch12:19
peluseacoles, I thought I had that fixed up for you already, no?12:19
acolespeluse: it failed to merge over weekend - conflicts with the ruggedize to ssync rename12:20
peluseacoles, ahh, OK.  That shouldn't be too bad I don't think.  I didn't look after that one12:21
peluseacoles, clayg got a probe test started for the reconstructor so I'm about to fix an issue there and start building those up12:21
acolespeluse: hmmm, quite a few conflict sites but i'm done12:22
peluseacoles, sorry about that.  Didn't think to circle back since it was really just string replacement12:23
acolespeluse: np. just one of those ones where two lines in a dict changed alongisde each other12:24
acolespeluse: so about the yield_hashes change i put in that gist on Friday...12:25
acolespeluse: i'll stare at it again, but i thought the issue there was that HCL clears out obsolete files but with EC we may have files .data *newer* than .durable that are nt lceaned out but do need to be ignored by yield_hashes12:26
acoless/lceaned/cleaned/12:27
* peluse looking12:27
peluseacoles, ahhh, OK.  Not sure its worth the logic though because it should be very rare when that happens, well at least rare, and when it does...12:29
acolespeluse: ? when it does ssync will puch a newer timestamp to receiver, no?12:30
peluseI don't think its a huge problem but need to think about that scenario just a bit12:30
peluseyes but its not being replciated, its being reconstructed and I think pyeclib will fail12:30
openstackgerritAlistair Coles proposed openstack/swift: Multiple fragment Archive Index Support  https://review.openstack.org/15963712:31
pelusethere swift opaque metadata in the FA and I just kinda assume if we give it a set of FA's and one doesn't belong that it wont build corrupt data and give it back to us but need to check12:32
acolespeluse: hmmm, ic. I guess i imagined a scenario like (quorum -1) .data's get written, so no durable gets written, but enough .data's out there to reconstruct??12:33
acolesor is that by definition a contradiction?12:33
pelusedurable doesn't get written unless there's enough data to reconstruct12:34
acolespeluse: ok.12:34
*** rdaly2 has joined #openstack-swift12:34
pelusebut that will be a good probe test for my todo list!12:34
pelusecuz I'm not sure, maybe it will just explode :)12:35
peluseI've got one fix in the get path on the reconstructor to do and then I'll see how easyily I can add that.  Well, have one other scenario that we drew up in CA that I need to do first but then12:36
acolespeluse: anyway, i really don't like that logic being in yield_hashes !) and i think HCL/GOF is kinda goofy - GOF has *exactly* the info that yield_hashes wants, but HCL then obscures it, and yield_hashes iterates the files again!! I'm pretty confident I can clean all that up without needing the crappy code in that gist.12:38
acolespeluse: heading to lunch. catch u later.12:38
peluseOK, thanks12:44
*** dencaval has joined #openstack-swift12:48
*** joeljwright has joined #openstack-swift12:49
*** openstackgerrit has quit IRC12:50
*** openstackgerrit has joined #openstack-swift12:50
*** fifieldt has joined #openstack-swift12:51
*** aix has joined #openstack-swift13:10
*** silor has joined #openstack-swift13:12
tdasilvamattoliverau: I think your change looks good. You just missed a couple of methods in proxy/controllers/obj.py that can be removed: _listing_iter and _listing_pages_iter13:23
*** mahatic has joined #openstack-swift13:25
*** sandywalsh has joined #openstack-swift13:31
openstackgerritAlistair Coles proposed openstack/swift: Merge 'remotes/origin/master' into feature/crypto  https://review.openstack.org/16470013:45
*** lpabon has joined #openstack-swift13:50
*** o5k has joined #openstack-swift13:51
*** silor has quit IRC13:58
*** jrichli_ has joined #openstack-swift14:12
*** jrichli_ has quit IRC14:17
*** jrichli_ has joined #openstack-swift14:17
*** jrichli_ has quit IRC14:18
*** jrichli has joined #openstack-swift14:18
*** bkopilov has quit IRC14:22
*** bkopilov has joined #openstack-swift14:33
openstackgerritAlistair Coles proposed openstack/swift: Diskfile decides if durable is written based on policy  https://review.openstack.org/16271714:54
*** mahatic has quit IRC14:57
*** nshaikh has quit IRC14:58
*** o5k has quit IRC15:11
*** o5k_ has joined #openstack-swift15:11
*** aswadr has quit IRC15:14
*** david-lyle_afk is now known as david-lyle15:15
*** mahatic has joined #openstack-swift15:24
*** reed has joined #openstack-swift15:26
openstackgerritJiangmiao Gao proposed openstack/swift: Add the missing "file" keyword for print  https://review.openstack.org/16474015:33
*** silor has joined #openstack-swift15:35
openstackgerritAlistair Coles proposed openstack/swift: DiskFile refactoring to per-policy classes  https://review.openstack.org/16224915:39
*** tacotuesday has joined #openstack-swift15:40
tacotuesdayif I have staticweb configured, can I hit the files in my swift container directly from my browser?15:41
acolespeluse: clayg: torgomatic : Paul updated me on discussions you had re diskfile. I had worked this (^^ 162249) up in parallel (just couldn't rebase to feature/ec on Friday) so pushing anyway fwiw15:42
*** o5k_ is now known as o5k15:49
openstackgerritAlistair Coles proposed openstack/swift: DiskFile refactoring to per-policy classes  https://review.openstack.org/16224915:54
*** gyee has joined #openstack-swift15:59
*** openstackgerrit has quit IRC16:11
*** openstackgerrit has joined #openstack-swift16:12
*** aix has quit IRC16:16
openstackgerritMerged openstack/swift: Imported Translations from Transifex  https://review.openstack.org/16408616:23
notmynamegood morning16:24
*** nellysmitt has quit IRC16:30
*** Fin1te has joined #openstack-swift16:35
claygtdasilva: nice, how were you able to get https://review.openstack.org/#/c/164561/1 going w/o the versioned writes work!?16:35
*** sandywalsh has quit IRC16:36
tdasilvaclayg: I just left the old object versioning code there. mattoliverau said he was taking a stab at rebasing obj. versioning patch to ec branch too16:36
claygwhoa! thanks mattoliverau16:37
*** tsg has joined #openstack-swift16:37
tdasilvanotmyname, clayg: now, I did not attempt to rebase patch 159610 yet. I noticed that in the EC branch there are two other controller classes already, so we would need to do work to separate ec code from replica code16:38
patchbottdasilva: https://review.openstack.org/#/c/159610/16:38
tdasilvaor just leave it in the Base class as it is now16:39
*** Nadeem has joined #openstack-swift16:42
claygacoles: i think we're about to run into converging patches again -> https://review.openstack.org/#/c/164380/16:46
acolesclayg: :(16:47
claygacoles: I wanted to see what how little the existing stuff would have to change to allow for a per policy diskfile to get swapped out16:47
claygacoles: no it's good!16:47
claygacoles: last time when we did the policies everywhere stuff it totally worked out!16:48
acolesclayg: oh, so you did the routing part but not yet split out an ECDiskFile16:50
acoles?16:50
claygyeah!16:50
claygI mean I registered it - but haven't implemented any code in there16:50
acolesclayg: oh, ok, i'll upgrade to a :) then16:50
claygalthough I was probably going to have a run at *not* changing any of the existing implementation16:51
claygacoles: like try and what it would look at to leave the existing stuff totally safe and sound and just *add* ec changes under the router16:52
acolesclayg: yeah, i realised over weekend that having an *unchanged* ReplDiskFile would be really attractive to reviewers16:52
claygacoles: mostly just to see where we'd have to split things up - then a real refactor into a common base could even happen after the ec merge16:52
claygacoles: that's my line of thinking16:52
clayglike even if it' menas things aren't as dry as they could be16:53
claygmaybe16:53
claygidk16:53
acolesclayg: i just like OO :|16:53
claygdon't be ashamed16:53
claygi like me a good function here and there - but if the only caller of the function is a method inside the reference implemeantation of a class that you know is an iterface - *maybe* that function might wanna be over-ridden at some point :P16:54
*** openstackgerrit has quit IRC16:54
acolesclayg: tbh i was surpised how simply it all dropped out, and a lot of my line count is commentary16:54
*** openstackgerrit has joined #openstack-swift16:55
claygacoles: ok, so you're probably 'bout done for today - you want me to try to rebase you per-policy diskfile on the router?16:55
claygacoles: or should i leave it to you and work on proxy stuff?16:55
claygacoles: i'm not even sure how long it takes to look at the router and see what it's doing - it seemed strightforward when I hacked it out16:55
acolesclayg: i have an hour or so, just finishing up a tweak on the multi frag patch to keep mattoliverau happy (hi mattoliverau :)16:56
claygacoles: yeah i'm worried about that patch16:56
claygacoles: obviously all that functionality we want16:56
claygacoles: but the implementation was sort of what inspired all the per-policy diskfile discussion - and i'm not sure how much of it survives that refactoring16:56
claygacoles: e.g. is the suffix hash classes16:57
acolesclayg: uhuh. well after peluse got me up to speed earlier i thought we were sticking with the multifrag patch for now and the per-policy-diskfile ideas were on ince16:58
acoless/ince/ice/16:58
claygacoles: I think the hashes/suffix implemenation is a good candiate for OO (it has a state and an interface, which behaviors that are seperate from implemenation) - but again doing that for the EC diskfile doesn't mean the replicated diksfile *has* to change - althought it might *want* to after it sees how obvious it is!16:58
*** nellysmitt has joined #openstack-swift16:58
acolesclayg: have to confess i haven't paid too much attention to the hashes/suffix part yet (sorry)16:59
claygacoles: well... yeah - he needs to make progress on the reconstructor - i'm just saying most of that change get's gobbled by an ECDiskfile16:59
*** Fin1te has quit IRC16:59
acolesclayg: yup16:59
claygoh, i thought that was most of mattoliverau's complaints16:59
acolesclayg: mattoliverau pointed out a possible ValueError I ought to catch when resolving frag index16:59
claygso we can merge it "wrong" and the clean it back up as the policy stuff goes in - or we can leave it as is and try to let paul iterate on the dependent change17:00
acolesstr(fi) could ValueError if there's garbage in the fir17:00
acolesfir??? s/fir/dir/ !!17:00
claygacoles: oh, he also said some stuff about how a bunch of public diskfile functions that manipulate the suffix state should be instance methods - and he's was spot on about that (at least I agreed after having hacked on it)17:01
*** ChanServ changes topic to "Review Dashboard: http://goo.gl/uRzLBX | Overview Dashboard: http://goo.gl/2By1qv | Priority Reviews: https://wiki.openstack.org/wiki/Swift/PriorityReviews | Ideas: https://wiki.openstack.org/wiki/Swift/ideas | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/"17:01
acolesclayg: so far i have kept both up to date i.e. the multi-frag patch works (i believe) and the per-policy stuff is there waitng in the wings17:01
claygbut ultimately I decided no matter how I'd like to clean up the suffix hashes interface I'd rather *review* ad EC diskfile that didn't ess with any of it17:01
acolesclayg: ah, ok, like i said, i need to catch up on the suffix stuff, didn't spot mattoliverau comments there17:02
acoles(well, i spotted but didn;t dwell on them :?)17:02
claygacoles: so the multi-frag change (setting asside suffix stuff) is really all about get_on_disk_files?17:02
claygacoles: ok, well i guess I got hung up on the suffix stuff - so it's good we've got eyes on different things - but I really don't know at what point to merge that change17:03
acolesclayg: for my part, mostly get_on_disk_files, hash_cleanup_listdir, and some cleanup i think17:03
claygacoles: ok ok - right on17:04
acolesclayg: i have one outstanding query in yield_hashes17:04
claygacoles: so in your work on the diskfile stuff did you end up dropping those diskfile functions into the DiskFile class(es)?17:04
acolesclayg: yes pretty much, get_ondisk_files goes into the classes (module unc is still there for unit tests but thats just lack of time on my part to move it out)17:05
*** mahatic has quit IRC17:05
acoleshash_cleanup_listdir just routes through to a class method based on policy (could be refactored, i was 50/50 on that one)17:06
*** mahatic has joined #openstack-swift17:06
claygacoles: no it's fine - no one wants to review all that test churn - unless it's part of a targeted refactor - which shouldn't stand in the way of the EC patches IMHO17:06
acolesclayg: glad to hear that!17:06
claygacoles: so I just change all of the DiskFile(Manager|Writer|Reader) classes to call self.blah_blah instead of the module methods directly by some python tomfollery where I "attach" the module level functions to the class.17:07
claygstrip_self in obj.diskfile17:07
*** dmorita has joined #openstack-swift17:08
claygmeans that I can overwrite the functions with methods in the EC diskfile - but there's no code/test churn in diskfile for the repl policy diskfile17:08
claygnow I just need to figure out what behaviors I acctully need to get into the EC diskfile?17:08
acolesic. clever.17:08
acolesclayg: here's a suggestion...17:09
acolesclayg: i'll rebase my patch on yours. i'll revert to unmodified Repl diskfile and put all the 'new' impl into ECDiskFile17:09
claygacoles: :)17:09
claygit works best when it's your idea ;)17:09
*** rledisez has quit IRC17:09
acolesclayg: then as and when we like the new impl, we roll it into repl diskfile17:10
claygacoles: yeah totally!  but like that maybe doesn't even have to happen as part of the EC review?  maybe?  Like if we say "here let's merge this crazy new stuff and not change any of the old stuff - then after the release we'll go refactoring crazy town everywhere"17:11
acolesclayg: well, i like the idea of knowing that nothing changed with classic diskfile while we get EC landed17:11
claygacoles: yeah at as long as we have those cleanups "in the wings" - we may *want* to not "cleanup" a bunch of critical code paths right before a named openstack release?17:12
claygat least that's my misguided logic17:12
clayganyway - i'd love to see some of the acctual get_on_disk_files and hash_cleanup_listdir changes inside the crazy routed diskfile manager nested class thing I cooked up17:12
acolesclayg: "clean up".almostEquals("f*** up") ??17:12
claygacoles: I mean - that's the joke17:13
acolesclayg: so , are you thinking propose your router patch to master?17:13
clayg"hey this looks like it's just refactoring - what does this patch *do*" - "oh you know, hopefully nothing, theere's probably a few new bugs tho"17:13
claygacoles: if we can prove it out on feature/ec - i think it'd be a good review in the patch chain to master - "here17:14
clayg"here's what we need to change in ReplDiskfile so we can subclass it and override what we mostly only what we need to"17:14
acolesclayg: ok makes sense17:15
clayg"here's where we add in EC diskfile behaviors and notice *nothing changes in the repl diskfile*" (accept what we already changed to make it so we can hide ec specific behaviors in a ec diskfile)17:15
claygi man we *could* probably even get a way with less repl diskfile changes - but it'd mean more duplicated code - like reimplementing all of the methods that call out to module level functions just so we can call instance methods in their place17:16
claygi had convinced myself that it "only* takes three classes to implement a subclass of the existing implementation - but i forgot about the manager - so really it's *4*17:18
acolesclayg: ok, i'll take a crack at that rebase mine on yours with untouched diskfile, and see if i get there before end of day17:18
claygacoles: ok - well i was going to suggest if you wanna take a stab at that tomorrow (my tonight) even - I could work on proxy stuff today - or I can try to carry on your good work in that area - i'll follow your lead17:18
claygjrichli: did notmyname trick you into working on plumbing a non-default policy option through to all the container create methods in functests?17:19
*** erlon has joined #openstack-swift17:19
acolesclayg: ok, well i'll make a start but it may well end up being my tomorrow, hopefully something for you to laugh at on your tuesday morning :D17:19
* notmyname *tricky*tricky*17:19
claygi've also got the container-sync and account-reaper stuff that is pretty cheap17:20
dencavalclayg acoles notmyname Hey core guys,  could you please take a look on bp/sorting-method-storage-policy https://review.openstack.org/#/c/160877/17:20
notmynamedencaval: I'll try to take a look later. but know that most of us are focusing on EC right now. huge amount of work there to get done before kilo17:21
notmynamedencaval: and thanks for working on it! I think it sounds like a really cool idea!17:22
dencavalnotmyname ok, I know you are busy. I hope you have the priority things done soon, thanks17:23
notmynamedencaval: and I just added your patch to the bottom of https://wiki.openstack.org/wiki/Swift/PriorityReviews (because I want to keep an eye on it)17:24
acolesclayg: notmyname : jrichli : re func test and policies - i looked for an easy path to that when i did patch 15920517:24
patchbotacoles: https://review.openstack.org/#/c/159205/17:24
acolesbut didn't see one !17:24
*** o5k_ has joined #openstack-swift17:24
dencavalnotmyname oh pretty nice, thanks17:25
acolesnotmyname: i was wondernig about adding an option to swiftclient to specify 'default' policy for client to use when creating containers. Then just setting the swiftclient env var before running tests?17:26
*** o5k has quit IRC17:26
notmynameacoles: so plumb it through swiftclient instead of the tests themselves? interesting17:26
notmynameit would work17:26
acolesnotmyname: if i'm right, its a *awful* lot simpler and *maintainable*17:27
notmynameand clayg was thinking of an env var for the setting too (but IIRC for the tests instead of swiftclient)17:27
acolesnotmyname: yup. env var. so 'ST_POLICY=banana && ./.functests'17:28
notmynameacoles: ya. at the least, it will be a lot faster to do. jrichli^^17:28
acolesnotmyname: it could actually be a useful feature for swiftclient as well, to have your chosen policy set in env vars17:29
notmynameyup17:29
*** zaitcev has joined #openstack-swift17:29
*** ChanServ sets mode: +v zaitcev17:29
claygacoles: notmyname: ok, well how about we monkey patch swiftclients put_container in the functests *first* and see if it would work?17:34
claygi think in tests.py (the Env tests) it'd be easy enough to patch the "Container" class17:34
claygin the other tests (the retry(method, **kwargs) tests) you'll find that that do their on http thing - so swiftclient just won't help17:35
jrichliacoles: ok, thx.  I will take a look.17:35
openstackgerritMerged openstack/swift: Merge master to feature/ec  https://review.openstack.org/16466717:35
claygi'm heading in' bbiab17:35
openstackgerritMerged openstack/swift: Merge 'remotes/origin/master' into feature/crypto  https://review.openstack.org/16470017:36
acolesjrichli: see wot clayg just said too17:36
jrichliacoles: yes.  I just got back from lunch and am reading the exchange. :-)17:36
acolesclayg: jrichli : oh yeah, not all tests use swiftclient17:37
jrichliclayg: it wasn't a trick :-) but yes, I would like to help.17:39
*** jordanP has quit IRC17:44
*** jistr has quit IRC17:51
openstackgerritAlistair Coles proposed openstack/swift: Multiple fragment Archive Index Support  https://review.openstack.org/15963718:02
*** madgriff_ has joined #openstack-swift18:03
jrichliclayg: checking my understanding: should I look at modifying class Container in swift_test_client.py so that it consumes an ENV var for policy?18:03
openstackgerritAlistair Coles proposed openstack/swift: Multiple fragment Archive Index Support  https://review.openstack.org/15963718:05
acolespeluse: clayg: ^^ think I am done tinkering with this one, apart from fixing anything review uncovers18:06
*** tacotuesday has quit IRC18:06
acolespeluse: i just left the TODO note under yield_hashes as a reminder to revisit18:06
peluseacoles, awesome18:07
peluseclayg, provided it looks good on review are you cool landing it and then refactoring separately?18:08
*** welldannit has joined #openstack-swift18:16
notmynamefunny https://twitter.com/jkmcnk/status/57752369468094054518:18
*** jh_ has joined #openstack-swift18:27
*** Fin1te has joined #openstack-swift18:28
*** jh_ has left #openstack-swift18:28
*** tsg has quit IRC18:35
*** geaaru has quit IRC18:37
jrichliIs he claiming it is crappy code because there is one (ok two) bugs?  At least he is appreciating that things still work18:38
*** welldannit has quit IRC18:38
claygnotmyname: i guess maybe we could land something to fix https://bugs.launchpad.net/swift/+bug/142410818:39
openstackLaunchpad bug 1424108 in OpenStack Object Storage (swift) "KeyError: 'storage_policy_index' in _really_merge_items swift/account/backend.py" [Undecided,New]18:39
claygadding the setdefault thing seems pretty sane18:39
dmsimardcschwede: Just came across https://github.com/enovance/swift-ring-tool18:40
dmsimardcschwede: Nice work but that sounds way too dangerous :p18:40
peluseclayg, FYI got the adjacent + far node tets added to probe and reconstructor updated to work with them... will post soon18:40
claygcschwede: NICE!18:40
claygpeluse: were you able to steal what you needed from the proxy GET path - or did you go the internal client path?18:41
claygpeluse: i'm torn on landing the multi-frag index stuff - i feel like there's good momentum on the per-policy df - what's the downside of just waiting and getting it landed on feature/ec how we're planning on doing the merge to master?18:42
peluseclayg, actually neither... added just a small amount of straightforward error handling and a simple iter chain for 404s.  Will want you to take a look for sure, seemed simpler than either other solution18:42
claygpeluse: NICE!18:43
* clayg loves simple18:43
* clayg not sure if torgomatic believes clayg knows the meaning of the word18:43
peluseclayg, I guess the only downside is that I'm dependent on MFI for recon to work at all.  If you get another solution that I can munge over to as a D then that works too, wouldn't want to wait till the last minute though of course...18:43
notmynamelol18:43
peluseclayg, but I'm on board with that route if that's how you want to go!  Will keep using MFI in the meantime18:44
claygpeluse: +1 you're doing god's work on the reconstructor18:45
* peluse ponders the learning's of working on MFI....18:45
claygpeluse: when you say "recon" you're talking about the reconstructor - not "swift-recon"18:45
peluseyeah, I shouldn't shorten it like that, maybe ECrecon instead18:45
pelusereconstructor is such a long word18:45
claygyeah I dig on it - i was sure somewhere there was a comment about "recon" and I was totally thinking you ment swift-recon18:45
* peluse heads to grab some grub18:46
claygtdasilva: let me know what I can to to help with PUT/versioned_writes/copy on master/feature-ec18:47
tdasilvaclayg: I guess first I'd like to figure out a plan...do we want to move everything to EC branch so that it is easier later to merge back to master18:48
tdasilva?18:48
claygtdasilva: that is *a* plan - is it the *best* plan?  I have no idea :'(18:49
tdasilvaok, well, we have both the refactoring there and versioning is half-way done18:49
tdasilvaI can jump on copy and see if we can make progress on that18:49
claygtdasilva: so you have the PUT method extraction change up against feature/ec with tests passing?18:52
tdasilvaclayg: yes18:52
claygtdasilva: and versioned_writes too!?18:53
claygtdasilva: ok I'll definately review https://review.openstack.org/#/c/164561/18:53
tdasilvaclayg: I tried to make it simple and really just split up the code to small functions18:53
tdasilvano new code added18:53
claygtdasilva: hell yeah!18:53
tdasilvaso it should be simple to code review18:53
tdasilvaclayg: obj. versioning is here: https://github.com/matthewoliver/swift/tree/feature/ec18:54
tdasilvayou will noticed that it's already based on the refactor patch (164561) - thanks to mattoliverau18:55
claygwtg tdasilva and mattoliverau!18:55
claygoh... but he didn't push it to gerrit - weak18:55
clayg:P18:55
tdasilvalol...not yet, but he should be online soon, I just pointed out a couple more methods he can remove and he should be all set18:56
clayghow is "Group-based-policy" an openstack project?  is "Group-based-policy" a *service*????18:56
tdasilvaclayg: could probably use your help with something thou...18:56
claygtdasilva: name it!18:57
tdasilvaclayg: you dropped a comment on obj. versioning about placement of filter in the pipeline (before or after slo/dlo) and that got me thinking about some crazy use cases...unfortunately we don't have have a lot of cross-feature tests, so I think we might need to start thinking about that18:58
*** welldannit has joined #openstack-swift18:59
claygfuuuuuu19:00
claygi think we have *some* cross-feature tests - but not a lot of tests for *versioning* with other features?19:00
tdasilvaclayg: for example: if you version slo manifest and some segments, then receive a multipart-manifest=delete request19:00
claygsounds terrible19:01
tdasilvaclayg: yes, i meant especifically slo/dlo/versioning cross feature, sorry19:01
*** acoles is now known as acoles_away19:01
*** tsg_ has joined #openstack-swift19:03
claygtdasilva: yup - ok well - that's a disaster - so... i guess "help write some tests for dlo/slo * versioning and try to document existing behavior" would be a good starting point19:04
claygso maybe the versioned middleware and copy extraction isn't in the cards in the near?  that's fairly disappointing.  Maybe we'll need to touch base with matt.19:05
tdasilvaclayg: yeah, I think we need to sync19:08
openstackgerritpaul luse proposed openstack/swift: Erasure Code Reconstructor  https://review.openstack.org/13187219:08
openstackgerritpaul luse proposed openstack/swift: Multiple fragment Archive Index Support  https://review.openstack.org/15963719:08
tdasilvanotmyname, clayg: is the current plan to land all the patches there are up for review on ec and merge them to master in two weeks?19:08
openstackgerritThiago da Silva proposed openstack/swift: Refactor server side copy as middleware  https://review.openstack.org/15692319:09
*** mahatic has quit IRC19:12
*** silor1 has joined #openstack-swift19:12
*** silor has quit IRC19:13
*** Fin1te has quit IRC19:14
openstackgerritpaul luse proposed openstack/swift: wip: ec probe test  https://review.openstack.org/16429119:17
notmynametdasilva: ya, like with storage policies there will be refactor to get it into a smaller series of commits and we'll get that as a merge commit again19:18
*** Fin1te has joined #openstack-swift19:21
*** tsg_ has quit IRC19:24
*** tab____ has joined #openstack-swift19:27
*** Fin1te has quit IRC19:28
*** Fin1te has joined #openstack-swift19:30
*** rdaly2 has quit IRC19:32
tdasilvanotmyname: and is kilo RC going to be cut right after? I guess my question is: would we want new work done in master to be merged before tagging RC? trying to figure out if it makes sense to move obj. versioning and copy to ec or just keep working on master19:35
notmynametdasilva: yes, current plan is to cut the RC very soon after the merge finishes. mostly to catch any last thing that needs to land19:38
notmynameeg bugfixes or security issues19:38
tdasilvanotmyname: ok, thanks19:40
notmynametdasilva: if there's a ton of merge conflicts for object versioning, then doing it on ec (or at least the proxy refactors) would more easily allow it to land on master in kilo19:41
*** dmorita has quit IRC19:42
tdasilvanotmyname: agreed...19:43
notmynameand from what peluse/clayg tell me, it would actually help the merge to master anyway since it shows that the proxy is better19:44
claygwell - that's just like my *opinion* man19:45
*** os1 has joined #openstack-swift19:48
os1Hi19:49
os1quick question19:49
os1What's the purpose of account.lock, container.lock, and object.lock in the /var/lock directory?19:49
os1And are they always supposed to be there?19:49
claygwhat the crap?  those must be for recon.19:50
claygwell... s/must/might be/19:51
*** dmorita has joined #openstack-swift19:51
os1Yes, they are for recon.19:53
claygsee!  s/might be/must/ !19:53
os1But why does recon need them, and does anything else need them as well?19:53
claygis it just using them for the read modify write on the recon cache files?19:54
*** nellysmitt has quit IRC19:54
notmynameor for rsync19:55
claygoh... maybe19:55
notmynameI'd expect account.lock to be for rsync. but there are a few other places that swift might drop a ".lock" file19:56
claygnotmyname: yup right there in rsync.conf - doh!19:57
notmynameos1: so that. it's an rsync artifact. ie replication19:57
os1Right - so whether it's for rsync or recon, either way, why do they need those lock files?19:59
*** tsg_ has joined #openstack-swift20:01
openstackgerritMerged openstack/swift: Fix ContainerBroker to use policy-0 in default  https://review.openstack.org/15821920:02
claygos1: well rsync needs them for max connections20:02
claygos1: why do you care?  are they bumming you out somehow?20:03
os1Sometimes they are not installed with the proper unix user permissions.20:06
os1swift-recon outputs errors because of permissions issues to those files.20:06
claygoh really... hrmm... how strange20:06
os1Also, when you said that rsync needs them for max connections, I can see that, but why would a process need a lock file for that?20:07
claygdo you have a traceback - given notmyname's comments i suppose I'm not sure why recon is looking at them - i think it does some locking - but maybe on the swift_recon_path files instead20:07
claygwhy would a process need.... I guess it's ipc - maybe fork-on-connect20:08
peluseclayg, looks like kill_server20:11
pelusewill take out 2 nodes in our EC config (per call) which means I can't really put together the revert test like we talked about since I can't kill just one node at a time20:12
peluseif that makes sense20:12
claygpeluse: oh, takes out one server - but two disks20:14
peluseyeah20:14
claygmaybe if you dig aroud in replica2part2dev until you find *just* the right placement you need?20:15
peluseyeah, I think I'll have to do something like that20:15
os1clayg : Not sure that your explanation completely made sense.20:15
claygother option i 'spose if plumb in something for mount_check so that you can "disable" a disk like it's unmounted or something... maybe...20:15
os1clayg : Regarding the lock.20:15
claygos1: np, just ignore me then20:15
peluseclayg, that might be easier actually.... have to run off to a meeting here soon.  Will keep ya posted.  For a second there I didn't think PUT was working with < parity nodes down!20:16
*** lpabon has quit IRC20:16
clayger... > parity maybe?20:17
clayglike... *more* than :P20:17
claygpeluse: np, keep me posted20:17
peluseyeah, the other way :)20:17
clayglol or s/down/up - there's lots of ways to spell "broke"20:18
os1clayg : What were you trying to suggest with 'fork-on-connect' ?20:19
claygidk, that maybe rsync does have a good reason for exposing the option instead of just... it hates administrators?20:20
madgriff_hey guys, I am trying to serve content from a swift container via a heroku app20:25
madgriff_does anyone have an example of this?20:25
madgriff_or any experience doing such things :)20:25
claygmadgriff_: like cloud files via cdn or just directly out of swift?20:26
*** tsg_ has quit IRC20:26
madgriff_clayg: I have an app that generates static html files and writes them to my swift container for persistent storage. Ive gotten that part down fine, id now like to serve these static files from my application20:27
notmynameeither set the container to public or use a tempurl for time-limited access20:27
claygcan your application do like a "media" url option?  just point it to the public container?20:28
madgriff_clayg: how its set up now (prior to swift) is it writes the html files and stores them locally, and then serves them from the local dir20:28
openstackgerritMerged openstack/swift: Fix the prefix of messages caputured from stderr  https://review.openstack.org/16455220:28
madgriff_clayg: no, I need to serve them, i cant set world readable on my container20:28
claygoic - sor proxy access through the app20:29
madgriff_yes :)20:29
claygthere's lots of "depends how you want to do it" with that setup20:29
claygwell... mostly there's lots of "depends how you want to do auth token management" with that setup20:29
claygonce you have a token - the return resp(body=swiftclient.get_object()) part's always ends up about the same20:30
madgriff_clayg: when I write I set up a swiftclient.Connection20:38
madgriff_clayg: could I follow that same convention with the read20:38
claygnew connection for every request - sure - and make an auth request each time - would work - maybe not the most efficent thing you could do - might depend on how many of these requests you wanna do per second?20:41
*** zhill has joined #openstack-swift20:45
mattoliverauclayg: I didn't want to push to gerrit until I could run tests on it, etc.. And there seems to be pyeclib issues on current EC HEAD.. Tho am sure that probably is just my environment. Haven't had a chance to debug it yet, but wanted tdasilva to have access to the codec while I slept. Surpisingly there weren't too many merge conflicts but only testing with let me know if there is brokenness caused by the rebase (re: obj20:47
mattoliverau versioning)20:47
tdasilvamattoliverau: hi, i had run into some pyeclib issues too, and I had to delete my .tox dir20:48
tdasilvamattoliverau: just FYI...20:48
tdasilvamattoliverau: and also get the latest pyeclib :-)20:49
mattoliverauI thought I had tried that, but will check again. Once done you happy for me to push a new patchet in your name?20:49
tdasilvamattoliverau: sure! thanks for all your help!!20:50
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873620:51
openstackgerritThiago da Silva proposed openstack/swift: Refactor server side copy as middleware  https://review.openstack.org/15692320:58
*** os1 has quit IRC20:59
claygnotmyname: ^ look at that community collaborate!21:02
*** silor1 has quit IRC21:03
notmynamewoot21:08
*** thumpba has joined #openstack-swift21:09
*** tsg has joined #openstack-swift21:10
notmynameI just discovered that OS X autocorrects "defcore" to "deface". I find that humorous.21:10
mattoliverauLol21:12
*** tellesnobrega has quit IRC21:13
*** Fin1te has quit IRC21:17
*** tellesnobrega has joined #openstack-swift21:18
openstackgerritTushar Gohad proposed openstack/swift: Bump PyECLib version to >= 1.0.3  https://review.openstack.org/16487221:19
claygtsg: why not just go for the 1.0.4!?21:19
claygoh... maybe there is no pyeclib 1.0.4 :P21:20
tsgclayg: I had submitted 1.0.3 for global-requirements :)21:20
tsgclayg: need to match that on the swift side21:21
tsgclayg: not sure if can we do 1.0.4 in swift requirements (if yes, I will resubmit) - and yes, there is a pyeclib 1.0.4 :)21:22
tsgclayg: :) looks like you approved - so end of that discussion21:22
swifterdarrelltsg: btw, I successfully got all the pyeclib (and dependency) code packaged and built for Ubuntu Precise, Trusty, and CentOS/RHEL21:23
tsgswifterdarrell: that's awesome!  :)21:23
tsghope the ubuntu uploads last night came handy21:23
swifterdarrelltsg: yup21:23
swifterdarrelltsg: i had to fix a couple things, tho...21:23
*** fbo has quit IRC21:24
tsgswifterdarrell: might be useful to pass those on to zigo21:24
swifterdarrelltsg: let me see if I can get a concise list of things I had to fix21:24
tsg(and me :))21:24
tsgswifterdarrell: that will be great!21:24
*** fbo has joined #openstack-swift21:26
notmynametsg: which means https://review.openstack.org/#/c/164172/ needs to be abandoned, right?21:30
tsgnotmyname: yes - I am assuming using a new branch triggers a new review (and change id)21:31
*** NM has quit IRC21:31
notmynametsg: I guess. why do you need it on master?21:31
tsgnotmyname: jenkins is not happy that feature/ec branch does not exist in the global requirements repo21:32
notmynameoh i see21:32
notmynameand they do have the same change-id21:32
tsghttp://logs.openstack.org/72/164172/1/check/gate-swift-requirements/0ef8713/console.html.gz21:32
notmynamebut yeah, I guess it's (branch, change-id) as the unique pair21:32
* tsg nods21:32
notmynamewhich makes searching for it "fun" https://review.openstack.org/#/q/Ie6e0c1b491017dd5096b14c23b610abc22b03d6a,n,z21:33
tsg:)21:33
notmynameI approved the one for master21:34
tsgnotmyname: thanks21:34
notmynameclayg: dfg is all like "we've got hummingbird and don't want your stinkin' object server" ;-)21:36
dfgha21:36
claygdfg: well the "mess" i was refering to was the pid files - if you don't have a app:object-server section you don't get an object server regardless - right?21:38
claygdfg: but thanks for the explination none-the-less - here I was assuming you were just trying to make something better on the general principle of thing - for some reason I assume you cloud files guys are more altruistic than the rest of us louts21:39
dfgclayg: ya. well we had this problem before hummingbird anyway.21:39
dfgclayg: and I think it is better in general- except for fixing what you had in the comment21:40
dfglike if you don't want to run the auditor21:41
claygwhich part?  about just letting the object-server fail to start because there's no app:object-server section and cleaning up the pid - or trying to somehow add paste config groking to the double-config-parse step so you better implement the coupling?21:41
claygdfg: same thing?  you don't add the audtior section.21:41
claygdfg: I guess i'm confused - it seems like the "problem" was not unwanted servers *starting* - it was their failing to start leaving stale pids around?21:42
dfgwell- the stale pids is def a consequence but i'd rather have them just not start if they are not configured21:42
claygoic - LBYL is better than EAPF in this case for some reason?21:43
dfgthe coding is probably a little messy with the double config parse21:43
dfgbut i didn't think it was a huge deal. if you think its really ugly then i can rty to clean it up some21:43
clayginstead of swift-init all start - could you just run swift-init object-auditor object-replicator object-updater start?21:44
dfgya. we could do that.21:44
claygdfg: well i didn't see "let them try to start and fail" being a huge deal - so I think I was definately misunderstanding your goal.21:45
dfgi just thought that if swift-init had the config and could tell that the server would never run that it could just not try.21:45
claygmy point was only that LBYL in this case could potentially lead to a weird situation with paste were the config file was valid as far as paste was concerned but swift-init was trying to be cleaver and wouldn't try to start the object server because the pipleline:main pointed to app:object instead of app:object-server21:46
dfglike there's this: https://github.com/openstack/swift/commit/0a122c1575fac98693059b0ad3b4386e35b74f6321:46
dfgbut if you use that then you will always get these pids lying around21:47
claygright so the pid cleanup thing seemed like a reasonable thing to fix - no reason to leave the stale pids around once we know the server failed to start - but I didn't see the patch as going after that issue - they could fail to start for other reasons than the config section not listed?21:48
dfgmy point was that if you didn't have a section that you on purpose don't want them to start. as oppsed to an error21:48
claygyeah status code checking could another issue21:49
zaitcevHey, here's an idea: switch to Systemd. It tracks everything 100%, there aren't any stale PIDs, ever.21:49
claygzaitcev: that's a silly idea :)21:49
claygdfg: I think if you say swift-init all start it's somewhat ambiguous if a missing config section is a warning or error - i sure seems that swift object-auditor start with missing object-audtior section would be something closer to an error - not sure21:50
zaitcevwell... We actually tell people only use systemctl start openstack-swift-proxy etc. in RDO, because swift-init proxy-server start  saddles the proxy with wrong SElinux context and thus you must defeat SElinux if you use swift-init.21:50
claygpoor swift-init :'(21:51
*** echevemaster_ has joined #openstack-swift21:52
dfgclayg: ya thats true (about the swift-init object-auditor restart error thing). alright, i'll just drop it then.21:53
claygsorry bro21:53
claygwouldn't mind having a bug to track the cleaning up of stale pid files on failure immediately tho :\21:53
dfgnot a big deal- i didn't spend a lot of time on it. thought it might be a quick fix.21:53
claygi know - nothing is simple - i'm really sorry21:54
madgriff_clayg: thanks for the help earlier btw. Ill start with a connection for each request and then try and find a way to optimize21:56
claygmadgriff_: right on!  let us know how it goes - or write something up something quick on a blog or something if you get a chance.  Thanks!21:56
*** echevemaster_ has quit IRC21:58
dfgnotmyname: i don't think i'm going to do that x-container-response-meta thing. i'm working on just changing static web to look for x-container-meta-cache-control and use it as a default Cache-Control for static web requests. i think it makes sense so far21:58
*** echevemaster has joined #openstack-swift21:58
notmynamedfg: ah22:05
dmsimardHey guys is there a blueprint or something for https://review.openstack.org/#/c/123220/ ? Trying to track down if there's any commits towards that topic.22:05
notmynameso if we do eventually do the x-container-response-meta, then we'll have to deal with conflicts and migrations and always supporting it22:06
notmynamedmsimard: yup. acoles_away and jrichli are the principle people working on it right now (while others focus on EC work). there's a feature/crypto branch for the work22:06
zaitcevdmsimard: spec replaces blueprint as a concep.22:06
dfgwell- thats what i was worried about to begin with. but when you said nobody has ever wanted this- why would it ever get implemented22:07
dfglike- it wasn't really the problem i was trying to solve.22:07
dfgand you already have that problem with CORS22:07
dfgalso- it isn't a problem because if you set it up as. set these headers unless they are already set (which is already a problem you'd have because of custom object headers) then it wouldn't be an issue22:08
dfgi couldn't think of another header that you'd really want to do this with.22:10
* clayg has already giving dfg enough headache for the day so he's not going to mention that it should technically be sysmeta with name translation to avoid user-meta name collision :D22:10
dfgalso there's a good reason to want to have cache control on static web container listings22:10
notmynamedfg: ya. I agree. you're right22:11
dfgclayg: sysmeta was how i was going to do it to begin with :)22:11
dfgbut we already use x-container-meta for static web and CORS- how is this any different?22:11
dmsimardnotmyname: Cool thanks, are you guys aiming for a particular milestone for release ?22:11
claygi guess static web was one of those legacy middlwares that used a bunch of user-meta already :\22:12
notmynamedmsimard: "when it's done"22:12
dmsimardnotmyname: Good answer :)22:12
dfggranted i hate typing out x-container-meta-access-control-allow-origin as the next guy...22:12
dfgbut that's how it goes22:13
*** tab____ has quit IRC22:13
*** welldannit has quit IRC22:13
dfganyway- i think it kinda fits right in there. for now. we'll see what happens to the pr22:13
swifterdarrelltsg: Please see https://gist.github.com/dbishop/692f39d9081414b12699 (feel free to forward to anyone else who could benefit from the feedback)22:13
*** tsg has quit IRC22:17
claygtdasilva: bah the _make_copy_request and _make_copy_context methods are confusing (I know I wrote them)22:19
claygmabye it's just the middleware COPY call backs are confusing22:20
claygtorgomatic: are you sure that somehow gets better if copy is extracted?  I mean slo/dlo will still need to set the copy_hook - it just gets consumed in middleware instead of the ObjectController22:20
torgomaticclayg: if the copy middleware is left of SLO/DLO, then the copy hook goes away22:21
dfgclayg: do you think x-container-meta-cache-control already being set for some unknown reason is an issue? thats the only real problem i didn't like22:27
dfgfigured it would come up in review22:27
tdasilvatorgomatic: yeah, I honestly just spent as much time on that patch to make unit tests pass. will start looking more at code now...22:31
tdasilvaI meant clayg ^^^22:31
tdasilvatorgomatic: left of slo/dlo? I thought it had to be to the right....22:31
torgomatictdasilva: the earlier it goes, the fewer middlewares need to know that COPY is even a thing22:32
tdasilvatorgomatic: mmm...i see...unless it does copies itself...like obj. versioning22:33
torgomatictdasilva: right, but the fact that slo and dlo have this ugly copy-hook thing is a bug, not a feature IMO22:33
torgomaticso put it to the left, and life is good22:33
tdasilvatorgomatic: got it, thanks for the insight. will continue to spend more time on i22:34
tdasilvait22:34
*** panbalag has quit IRC22:42
*** jrichli has quit IRC22:42
*** Nadeem has quit IRC22:44
*** madgriff_ has quit IRC22:55
claygdfg: yeah i mean it'll come up - but mostly just because we have sysmeta and that's a better way to do it now - OTOH, it'd be stupid to make this option do the right thing and leave the rest a mess - so then you'd want to cleanup all the existing options with a compatibility shim and *then* add the new options - which may not be that attractive to you - so you're probably better of just trying to slip in one more piece of sy23:03
claygit won't really make it any harder to cleanup the rest of them later - so you're left with only the pre-existing x-container-meta-cache-control shadowing the new behavior - probably not that likely (FLW)23:04
*** panbalag has joined #openstack-swift23:14
*** gyee has quit IRC23:16
*** lnr has joined #openstack-swift23:33
*** lnr has left #openstack-swift23:33
*** tsg has joined #openstack-swift23:46
*** thumpba has quit IRC23:51
*** tsg has quit IRC23:52
*** NM has joined #openstack-swift23:58
*** ho has joined #openstack-swift23:58

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