Friday, 2019-07-19

*** mahatic has quit IRC00:37
*** tomha has joined #openstack-swift00:39
*** tomha has quit IRC00:43
*** BjoernT has joined #openstack-swift00:57
*** BjoernT has quit IRC00:58
*** gyee has quit IRC01:00
*** BjoernT has joined #openstack-swift01:17
*** BjoernT has quit IRC01:24
*** mahatic has joined #openstack-swift01:35
*** ChanServ sets mode: +v mahatic01:35
*** tkajinam has quit IRC02:21
*** tkajinam has joined #openstack-swift02:21
*** psachin has joined #openstack-swift03:37
*** pcaruana has joined #openstack-swift04:37
*** new_student1411 has joined #openstack-swift04:55
*** tkajinam has quit IRC05:01
*** mrjk_ has joined #openstack-swift05:46
*** jistr has quit IRC05:47
*** jistr has joined #openstack-swift05:48
*** rdejoux has quit IRC05:49
*** mrjk has quit IRC05:49
*** tkajinam has joined #openstack-swift05:55
*** rcernin has quit IRC06:02
*** hoonetorg has quit IRC06:39
*** hoonetorg has joined #openstack-swift06:56
*** rdejoux has joined #openstack-swift07:10
*** baojg has quit IRC07:35
*** baojg has joined #openstack-swift07:36
*** baojg has quit IRC07:39
*** baojg has joined #openstack-swift07:41
*** baojg has quit IRC07:43
*** baojg has joined #openstack-swift07:44
*** ccamacho has joined #openstack-swift08:04
*** zaitcev_ has joined #openstack-swift08:54
*** ChanServ sets mode: +v zaitcev_08:54
*** zaitcev has quit IRC08:57
*** tkajinam has quit IRC09:05
*** zaitcev__ has joined #openstack-swift09:08
*** ChanServ sets mode: +v zaitcev__09:08
*** zaitcev_ has quit IRC09:12
*** e0ne has joined #openstack-swift09:48
*** e0ne has quit IRC10:06
*** dsariel has joined #openstack-swift11:14
*** dsariel has quit IRC11:15
*** tdasilva has joined #openstack-swift11:32
*** ChanServ sets mode: +v tdasilva11:32
*** tesseract has joined #openstack-swift11:33
*** tdasilva_ has joined #openstack-swift12:29
*** ChanServ sets mode: +v tdasilva_12:29
*** tdasilva has quit IRC12:32
*** zaitcev__ has quit IRC12:51
*** zaitcev__ has joined #openstack-swift13:03
*** ChanServ sets mode: +v zaitcev__13:03
*** dsariel has joined #openstack-swift13:10
*** dsariel has quit IRC13:25
*** zaitcev_ has joined #openstack-swift13:34
*** ChanServ sets mode: +v zaitcev_13:34
*** zaitcev__ has quit IRC13:37
*** tdasilva_ is now known as tdasilva13:43
*** e0ne has joined #openstack-swift14:12
*** baojg has quit IRC14:27
*** zaitcev_ has quit IRC14:42
*** zaitcev_ has joined #openstack-swift14:58
*** ChanServ sets mode: +v zaitcev_14:58
*** baojg has joined #openstack-swift15:16
*** e0ne has quit IRC15:29
openstackgerritClay Gerrard proposed openstack/swift master: symlink-backed versioned_writes  https://review.opendev.org/63385715:49
*** pcaruana has quit IRC15:49
claygtdasilva: timburke: ok, i'm going to try and rework the hardlinks patch so that hardlinks to SLOs use the manifest etag and hope that simplifies somethings?15:50
tdasilvaclayg: ack...currently going through p 63385715:51
patchbothttps://review.opendev.org/#/c/633857/ - swift - symlink-backed versioned_writes - 6 patch sets15:51
*** new_student1411 has quit IRC15:56
*** gyee has joined #openstack-swift15:58
*** baojg has quit IRC16:15
*** tdasilva has quit IRC16:56
*** tdasilva has joined #openstack-swift16:56
*** ChanServ sets mode: +v tdasilva16:56
*** tdasilva_ has joined #openstack-swift17:13
*** ChanServ sets mode: +v tdasilva_17:13
*** tdasilva has quit IRC17:15
*** tesseract has quit IRC17:24
*** tdasilva_ has quit IRC17:37
*** tdasilva_ has joined #openstack-swift17:37
*** ChanServ sets mode: +v tdasilva_17:37
tdasilva_clayg: the question on versioning and object expiration is an interesting one. I'm not sure we have added tests for this before...one idea (similar behavior to s3) would be to disallow expiration headers to objects in versioned containers??17:40
openstackgerritMerged openstack/swift master: py3: Bring functional/test_object.py under test; add func-ec-py37 job  https://review.opendev.org/64589517:44
timburkeclayg, tdasilva_ i wonder how well it'd work to ensure that expiration headers only make it to the link and not the real data... it'd be a break from pre-link behavior, but i think in a good way?17:57
timburkewow... do we really *never* check the status when we refetch the manifest at https://github.com/openstack/swift/blob/2.21.0/swift/common/middleware/slo.py#L817-L821 ?18:00
timburkethe non-atomic bits of swift suck...18:00
*** thiago__ has joined #openstack-swift18:00
*** ChanServ sets mode: +v thiago__18:00
*** thiago__ is now known as tdasilva18:01
timburkeotoh, i don't really want to plumb *more* slo logic into the object server, so...18:01
*** tdasilva_ has quit IRC18:03
clayg@tdasilva yes, i'm not clear on expiration behavior when versions are involved - I assumed the version would get uploaded and set to expire (potentially causing the link to 404 after expiration, or still be valid if it's already pointing to a newer version)18:05
claygI think it gets easier if we're able to move toward bucket policies18:05
tdasilvaclayg: how so?18:06
clayg@timburke just expiring the link seems reasonable from a data protection stand point - and also seems like it'd potentially still be useful once we can apply a bucket policy to cleanup the old versions...18:07
clayg@tdasilva well just cause we can stop trying to set which object expires when when they're uploaded and instead you just set the policy on the bucket!18:07
timburkeclayg, it *does* mean that versioned_writes should be in the expirer pipeline, though -- i'm not sure that we currently recommend that? but it'd certainly be useful to have that delete marker in there in case there was a re-upload18:13
claygi'm pretty sure we recommend that you do NOT put versioned_writes in your expirer pipeline - there was a bug on this not that long ago IIRC18:14
tdasilvaso in the case of supporting versioning with s3api, would we block users from using expiration to conform with aws s3?18:15
clayg@timburke I think it'd be pretty wild if expirer triggered stack based action18:16
tdasilvaassuming we also have bucket policy in the future18:16
claygtdasilva: I think it's a safe assumption we'll have some solution to bucket policy compatibility in the future18:16
timburkeclayg, on the policies thing... and you could have separate policies for the primary vs the main... i think i like that idea! well... *if* we get some sort of exemption for "currently-pointed-at version" (or should it be "most-recent"? 🤔)18:17
claygtdasilva: I think we'll continue to try and make s3api emulation/compatibility as near-as-possible translation of aws s3 when swift has the requisite underlying compatible capabilities (even to the extent of disallowing combining features that work together in swift because they don't in s3; sure)18:18
timburkeswift-ring-builder --help18:19
timburkeRing Builder file does not exist: --help 😞18:19
claygtimburke: tdasilva: we need to narrow the actionable design - we're talking about "how versioning works today" "how it should work after symlinks" "how it should work with bucket policies" "how it should work when with s3api + bucket policies" that's alot to figure out at the same time18:20
timburkemeanwhile, the actual help spans ~350 lines, which is a fair bit of reading...18:20
claygwe could *just* figure out how s3api + bucket policies should work (because that's "as near as possible to how they work in aws s3) - then try and work backwards from there?18:21
claygtimburke: lp bug #1553030 maybe?18:22
openstackLaunchpad bug 1553030 in OpenStack Object Storage (swift) "Change optparse to argparse, optparse is Deprecated since python version 2.7" [Undecided,In progress] https://launchpad.net/bugs/1553030 - Assigned to dharmendra (dharmendra-kushwaha)18:22
timburke👍, at least in part18:23
timburkemaybe entirely? the subcommand handling in argparse is actually pretty nice...18:24
tdasilvaclayg: I think it might be worth looking at the end goal so that we don't end up having to bend the code later to conform with a new requirement18:24
tdasilvaclayg: i guess i'm just thinking that it would be weird if swift allows one thing and s3 does sort of the opposite18:30
timburke^^^ definitely true. to design the swift thing, we need to figure out the superset of the s3 thing that still makes sense in swift18:31
*** psachin has quit IRC19:20
*** tdasilva has quit IRC20:06
*** tdasilva has joined #openstack-swift20:06
*** ChanServ sets mode: +v tdasilva20:06
openstackgerritClay Gerrard proposed openstack/swift master: Allow "harder" symlinks  https://review.opendev.org/63309420:44
clayghrmm... ubuntu-bionic | ERROR: unknown environment 'func-ec-py3'20:45
*** e0ne has joined #openstack-swift20:51
*** e0ne has quit IRC20:57
*** zaitcev_ is now known as zaitcev22:02
zaitcevtimburke: did you try to run functests against py3?22:02
zaitcevyour posted reviews implied that you did22:03
zaitcevsorry, brb22:07
*** baojg has joined #openstack-swift22:18
*** baojg has quit IRC22:22
zaitcevSo, anyway. According to tcpdump, account server does not send a reply, but just closes the connection. But it logs a success. So..... maybe a flush is missing somewhere, but it worked fine on py2.22:27
*** gyee has quit IRC22:34
*** gyee has joined #openstack-swift22:57
*** takamatsu has quit IRC23:31
timburkezaitcev, what version of eventlet are you using?23:52
timburkethat'd be my first guess, anyway23:52
zaitcevpython3-eventlet-0.24.1-3.fc30.noarch23:58
zaitcevshould be fine23:58

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