Friday, 2018-01-05

*** jistr has quit IRC00:11
*** jistr has joined #openstack-swift00:16
*** EmilienM has quit IRC00:30
*** tovin07_ has joined #openstack-swift00:43
*** gyee has quit IRC00:49
*** two_tired has joined #openstack-swift01:06
claygtimburke: acoles: be on the lookout for torgomatic ‘s fix for op bug #174137101:23
openstackbug 1741371 in OpenStack Object Storage (swift) "Expiring objects have skewed X-Delete-At values" [Undecided,New] https://launchpad.net/bugs/174137101:23
mattoliveraudid he decide which way he was going to take it? req timestamp or drop x-delete-after?02:06
*** threestrands_ has joined #openstack-swift02:14
*** threestrands_ has quit IRC02:14
*** threestrands_ has joined #openstack-swift02:14
*** awkwardpenguin has joined #openstack-swift02:15
*** awkwardpenguin has quit IRC02:15
*** threestrands has quit IRC02:16
kota_good morning Swift world and a happy new year!02:18
kota_I had been completely off until today.02:19
* kota_ is booting his head02:19
mattoliveraukota_: morning and happy new year!02:22
kota_mattoliverau: happy new year!02:24
kota_it looks like others have started new year work02:25
mattoliverauyeah, but still seems a little quiet. I assume everyones still getting back up to speed :)02:25
kota_mattoliverau: ;)02:33
*** JimCheung has quit IRC02:44
*** links has joined #openstack-swift03:29
*** links has quit IRC03:34
*** links has joined #openstack-swift03:56
*** psachin has joined #openstack-swift04:33
openstackgerritSamuel Merritt proposed openstack/swift master: Fix time skew when using X-Delete-After  https://review.openstack.org/53129004:38
openstackgerritSamuel Merritt proposed openstack/swift master: Ignore directory .stestr  https://review.openstack.org/53129104:41
*** two_tired has quit IRC04:55
*** ianychoi has quit IRC05:52
*** threestrands_ has quit IRC06:13
*** geaaru has quit IRC06:33
*** armaan_ has joined #openstack-swift06:54
*** hseipp has joined #openstack-swift07:39
openstackgerritMerged openstack/swift feature/deep: Set swiftclient log level to WARNING for sharding probe tests  https://review.openstack.org/53090007:52
*** geaaru has joined #openstack-swift08:08
*** tesseract has joined #openstack-swift08:12
*** armaan_ has quit IRC08:15
*** armaan has joined #openstack-swift08:16
*** armaan has quit IRC08:16
*** rcernin has quit IRC08:28
*** armaan has joined #openstack-swift08:31
*** silor has joined #openstack-swift08:51
acolesgood morning09:05
acoleskota_: happy new year!09:05
* acoles imagines kota booting his head and thinks kota must have very flexible joints :)09:06
openstackgerritMatthew Oliver proposed openstack/swift feature/deep: Use _root.db and _shard_db on sharded containers  https://review.openstack.org/53135010:09
mattoliverauacoles: morning10:09
mattoliverauopps already see a commit message typo.. oh well.10:09
acolesmattoliverau: hi, thanks for that ^ and your review comments10:09
mattoliverau^ that is still WIP and I still want to look at adding some more tests. But it's getting late and wanted to push what I had so far10:10
acoles+1 for pushing WIP. have a good weekend10:10
mattoliverauacoles: you too, have a great friday too ;)10:14
acolesmattoliverau: I hope to have something on the shard range state idea soon. TBH, I suspect that eventually we may need both that and some timestamp based analyser to cope with potentially competing sharders. But I think the state base scheme will get to us a tool that can we can start to use in 'controlled' environments.10:15
*** tovin07_ has quit IRC10:18
openstackgerritAlistair Coles proposed openstack/swift feature/deep: fixes for sharding/shrinking races  https://review.openstack.org/52993110:27
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Add includes method to ShardRange  https://review.openstack.org/53090110:27
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Re-introduce shard range updates to root after shard has sharded  https://review.openstack.org/53090210:27
*** szaher has joined #openstack-swift10:54
*** pcaruana has joined #openstack-swift11:02
acolesI'm looking at p 53129011:05
patchbothttps://review.openstack.org/#/c/531290/ - swift - Fix time skew when using X-Delete-After11:05
*** kong has quit IRC12:23
*** hoonetorg has quit IRC12:57
*** silor has quit IRC13:08
*** psachin has quit IRC13:09
*** silor has joined #openstack-swift13:30
*** silor has quit IRC13:32
*** silor has joined #openstack-swift13:35
*** links has quit IRC13:47
*** hseipp has quit IRC13:48
*** hseipp has joined #openstack-swift13:48
*** tonyb has quit IRC13:49
*** tonyb has joined #openstack-swift13:50
*** jistr is now known as jistr|biab13:51
openstackgerritAlistair Coles proposed openstack/swift master: Document that x-delete-after takes precedence over x-delete-at  https://review.openstack.org/53138414:50
*** jistr|biab is now known as jistr15:04
*** hoonetorg has joined #openstack-swift15:10
*** two_tired has joined #openstack-swift15:33
*** two_tired has quit IRC15:41
openstackgerritAlistair Coles proposed openstack/swift master: Tighten up test_check_delete_headers  https://review.openstack.org/53140315:59
openstackgerritAlistair Coles proposed openstack/swift master: Correct 400 response message when x-delete-after is zero  https://review.openstack.org/53140415:59
*** mtreinish has quit IRC16:08
*** mtreinish has joined #openstack-swift16:09
*** openstackstatus has quit IRC16:40
*** openstackstatus has joined #openstack-swift16:42
*** ChanServ sets mode: +v openstackstatus16:42
*** armaan has quit IRC16:57
*** armaan has joined #openstack-swift16:58
timburkegood morning17:02
acolestimburke: o/17:05
*** joeljwright has joined #openstack-swift17:10
*** ChanServ sets mode: +v joeljwright17:10
*** pcaruana has quit IRC17:21
*** hseipp has quit IRC17:26
*** joeljwright has quit IRC17:35
*** JimCheung has joined #openstack-swift17:36
*** early has quit IRC17:42
openstackgerritAlistair Coles proposed openstack/swift master: Use _update_x_timestamp method in object controller DELETE method  https://review.openstack.org/53144717:43
*** early has joined #openstack-swift17:45
openstackgerritAlistair Coles proposed openstack/swift master: Document that x-delete-after takes precedence over x-delete-at  https://review.openstack.org/53138417:45
timburkeacoles: the more i think about this _update_x_timestamp(req) business, the more i feel like it should happen up in the proxy server app (maybe as part of update_request?)17:50
timburke*every* request ends up needing to set it at some point, yeah? may as well centralize that17:51
acolestimburke: heh. I spent while looking for the place in the proxy server where x-timestamp *is* set17:51
acolesthe current *one* place is https://github.com/openstack/swift/blob/5c564e53966b74d6d7589c3505dd33816b3c19f1/swift/proxy/controllers/base.py#L1510-L153417:51
acolesbut the obj PUT path doesn't call that IIRC, so does its own thing17:52
timburke...and meanwhile we've discovered a variety of places where, actually, it'd be kinda nice if it was already set...17:54
timburkei know i've run into that with swift3 before, too17:54
timburkemaybe the One True Place to set X-Timestamp ought to be in gatekeeper, near https://github.com/openstack/swift/blob/2.16.0/swift/common/middleware/gatekeeper.py#L85-L9017:54
acolesI suspect the history behind the special cases is to do with container sync - the comment is a big hint at that17:54
acolesbut yeah it doesn't seem very coherent17:55
timburke...except then we'd still need it in the proxy server for internal clients...17:55
torgomaticsounds like proxy __call__ is the place to do it, and then we can stop worrying17:56
torgomaticI think you guys are right, and the current weirdness is an artifact of how container sync used to be17:56
acolestorgomatic: let's not muddle with it in your x-delete-after patch though...that looks close to being done17:58
torgomaticacoles: agreed17:58
timburkesounds good. proxy __call__ will be good, but i think gatekeeper might also be nice -- then we wouldn't need to carry some of the legacy of https://github.com/openstack/swift3/commit/d8ffe5a into s3api18:02
torgomaticI think I'm going to squash in patch 531403 but leave the other two cleanups to stand on their own unless anyone objects18:02
patchbothttps://review.openstack.org/#/c/531403/ - swift - Tighten up test_check_delete_headers18:02
acolestorgomatic: +1 ^^ that is the only one I felt should be included, the other stuff can follow on18:03
acolestimburke: both? then internal client is happy18:03
timburkeacoles: that's what i was thinking18:03
openstackgerritSamuel Merritt proposed openstack/swift master: Fix time skew when using X-Delete-After  https://review.openstack.org/53129018:15
torgomaticacoles: timburke: there's the patch ^^ with the test fixes included18:17
openstackgerritMerged openstack/swift master: Ignore directory .stestr  https://review.openstack.org/53129118:23
*** armaan has quit IRC18:44
*** armaan has joined #openstack-swift18:47
torgomaticheh, the bug in patch 531290 is slightly more annoying than I thought... if you're running a big EC scheme, say 12+3, you've got 15 fragment archives, each of which could have its own X-Delete-At19:08
patchbothttps://review.openstack.org/#/c/531290/ - swift - Fix time skew when using X-Delete-After19:08
torgomatichowever, only 3 of them update the expirer queue, so 12 of them may end up with X-Delete-At values that aren't reflected in the expirer queue19:09
torgomaticso worst case, you have 3 fragment archives deleted by the expirer and 12 that can't be; they will be cleaned up by the reconstructor, but that's much slower19:10
*** openstack has joined #openstack-swift21:15
*** ChanServ sets mode: +o openstack21:15
torgomaticclayg: that is a very nice property to have21:20
claygyup - wtg ssync!21:20
*** tonyb has quit IRC21:21
*** vinsh has joined #openstack-swift21:25
*** mweshi has joined #openstack-swift21:26
*** mweshi_ has joined #openstack-swift21:39
openstackgerritMerged openstack/swift master: Document that x-delete-after takes precedence over x-delete-at  https://review.openstack.org/53138421:52
timburkeahahaha CORS is such a mess, especially as it interacts with swift... i started looking through the spec and noticed something about "redirect steps"... so i start messing with symlinks, the only place that we currently *can* have redirects sent to the client (as i recall)21:58
timburkei try a cross-domain post to a symlink... and it works! 307, browser follows, 202!21:58
claygtimburke: good find21:59
timburkebut i wasn't actually setting any headers... if i try sending a x-object-meta-* header, i'm no longer on the happy "Simple Cross-Origin Request" path22:00
timburkeso i get my preflight request... which 200s with appropriate headers... so i POST, get back a 307... and then the browser balks: CORS header ‘Access-Control-Allow-Origin’ missing22:03
timburkebecause symlink swallows the proxy-server response and sends back its own22:04
timburkebut even if i *fix* that...22:04
*** mweshi_ has quit IRC22:05
*** mweshi has quit IRC22:05
timburkeall i've done it prevent the warning. i still just see the preflight & POST to the symlink22:05
timburkeand i don't get anything useful in the browser, not even something to tell me "oh, hey, i got a 307"22:06
timburkebecause in the non-simple case, you follow "If the response has an HTTP status code of 301, 302, 303, 307, or 308: Apply the cache and network error steps."22:07
timburkeso, what can we POST and still stay on the happy path?22:09
timburkeContent-Type. but only if it's one of application/x-www-form-urlencoded, multipart/form-data, or text/plain22:09
timburke(also, Accept, Accept-Language, or Content-Language -- but none of those stick to an object)22:11
*** mweshi_ has joined #openstack-swift22:12
*** mweshi has joined #openstack-swift22:13
*** armaan_ has quit IRC22:14
timburkeoh yeah, and /info requests are busted -- no access-control-allow-methods header22:17
*** mweshi has quit IRC22:17
timburkeno, never mind... that parts fine. i messed up my request22:21
timburkebut if you go off the happy path, preflight fails (no allow-origin)22:22
timburkethat's... maybe reasonable? *shrug*22:24
*** mweshi_ has quit IRC22:31
timburkestill not sure what to do for symlink... i guess this is maybe a reason to bring back ?symlink=post ... but how likely is this to really come up? you'd need a pretty full-featured object-store browser that's a web app served from a separate box... but why wouldn't you just put that on your proxies so it scales out with your cluster?22:38
timburkeand we *already* make it difficult to do this sort of thing -- see https://bugs.launchpad.net/swift/+bug/141853022:39
openstackLaunchpad bug 1418530 in OpenStack Object Storage (swift) "TempAuth and CORS is not working" [Low,Confirmed]22:39
timburke(and think about the fact that unless you make the container you're manipulating fully public, you'll necessarily be on the preflight path because of x-auth-token)22:40
*** mweshi has joined #openstack-swift22:47
*** awkwardpenguin has joined #openstack-swift23:02
*** mweshi has quit IRC23:24
*** gyee has quit IRC23:35

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