Monday, 2019-07-15

*** baojg has quit IRC00:00
*** baojg has joined #openstack-swift00:00
*** baojg has quit IRC00:00
*** baojg has joined #openstack-swift00:01
*** baojg has quit IRC00:01
*** baojg has joined #openstack-swift00:02
*** baojg has quit IRC00:02
*** baojg has joined #openstack-swift00:02
*** baojg has quit IRC00:03
*** baojg has joined #openstack-swift00:03
*** baojg has quit IRC00:04
*** baojg has joined #openstack-swift00:04
*** baojg has quit IRC00:04
*** baojg has joined #openstack-swift00:05
*** baojg has quit IRC00:05
*** baojg has joined #openstack-swift00:06
*** baojg has quit IRC00:06
*** baojg has joined #openstack-swift00:06
*** baojg has quit IRC00:07
*** baojg has joined #openstack-swift00:07
*** baojg has quit IRC00:08
*** baojg has joined #openstack-swift00:08
*** baojg has quit IRC00:08
*** baojg has joined #openstack-swift00:09
*** baojg has quit IRC00:09
*** baojg has joined #openstack-swift00:10
*** baojg has quit IRC00:10
*** baojg has joined #openstack-swift00:10
*** baojg has quit IRC00:11
*** baojg has joined #openstack-swift00:12
*** baojg has quit IRC00:12
*** baojg has joined #openstack-swift00:13
*** baojg has quit IRC00:13
*** baojg has joined #openstack-swift00:14
*** baojg has quit IRC00:14
*** baojg has joined #openstack-swift00:14
*** baojg has quit IRC00:15
*** baojg has joined #openstack-swift00:15
*** baojg has quit IRC00:16
*** baojg has joined #openstack-swift00:16
*** baojg has quit IRC00:16
*** baojg has joined #openstack-swift00:17
*** baojg has quit IRC00:17
*** baojg has joined #openstack-swift00:18
*** baojg has quit IRC00:18
*** baojg has joined #openstack-swift00:18
*** baojg has quit IRC00:19
*** sasregulus has quit IRC02:05
*** baojg has joined #openstack-swift02:19
*** baojg has quit IRC02:24
*** psachin has joined #openstack-swift03:25
*** baojg has joined #openstack-swift03:44
*** viks___ has joined #openstack-swift04:34
*** new_student1411 has joined #openstack-swift05:02
*** rcernin has quit IRC05:27
*** manuvakery has joined #openstack-swift05:28
*** rcernin has joined #openstack-swift06:44
*** fungi has quit IRC06:50
*** mugsie has quit IRC06:50
*** niceplace_ has quit IRC06:50
*** csmart has quit IRC06:50
*** hoonetorg has quit IRC07:02
*** aluria has joined #openstack-swift07:04
*** niceplace_ has joined #openstack-swift07:16
*** csmart has joined #openstack-swift07:16
*** fungi has joined #openstack-swift07:16
*** mugsie has joined #openstack-swift07:16
*** openstackgerrit has quit IRC07:18
*** hoonetorg has joined #openstack-swift07:19
*** ccamacho has joined #openstack-swift07:38
*** niceplace_ has quit IRC08:26
*** csmart has quit IRC08:26
*** fungi has quit IRC08:27
*** mugsie has quit IRC08:27
*** persia has joined #openstack-swift08:35
*** niceplace has joined #openstack-swift08:36
*** fungi has joined #openstack-swift08:37
*** mugsie has joined #openstack-swift08:37
*** csmart has joined #openstack-swift08:42
*** e0ne has joined #openstack-swift08:45
*** rdejoux has joined #openstack-swift08:52
*** rcernin has quit IRC08:55
*** e0ne has quit IRC09:00
*** e0ne has joined #openstack-swift09:12
*** e0ne has quit IRC09:25
*** baojg has quit IRC11:19
*** tesseract has joined #openstack-swift11:20
*** baojg has joined #openstack-swift11:25
*** pcaruana has joined #openstack-swift11:33
*** psachin has quit IRC11:36
*** baojg has quit IRC11:45
*** baojg has joined #openstack-swift11:45
*** baojg has quit IRC11:46
*** baojg has joined #openstack-swift11:46
*** baojg has quit IRC11:47
*** baojg has joined #openstack-swift11:47
*** baojg has quit IRC11:47
*** baojg has joined #openstack-swift11:48
*** baojg has quit IRC11:48
*** tesseract has quit IRC11:48
*** baojg has joined #openstack-swift11:49
*** baojg has quit IRC11:49
*** baojg has joined #openstack-swift11:49
*** baojg has quit IRC11:50
*** baojg has joined #openstack-swift11:50
*** baojg has quit IRC11:51
*** baojg has joined #openstack-swift11:51
*** tesseract has joined #openstack-swift11:51
*** baojg has quit IRC11:51
*** baojg has joined #openstack-swift11:52
*** baojg has quit IRC11:52
*** baojg has joined #openstack-swift11:53
*** baojg has quit IRC11:53
*** baojg has joined #openstack-swift11:53
*** baojg has quit IRC11:54
*** baojg has joined #openstack-swift11:54
*** baojg has quit IRC11:55
*** baojg has joined #openstack-swift11:55
*** baojg has quit IRC11:55
*** baojg has joined #openstack-swift11:56
*** baojg has quit IRC11:56
*** baojg has joined #openstack-swift11:56
*** baojg has quit IRC11:57
*** baojg has joined #openstack-swift11:57
*** baojg has quit IRC11:58
*** baojg has joined #openstack-swift11:58
*** baojg has quit IRC11:59
*** baojg has joined #openstack-swift11:59
*** baojg has quit IRC11:59
*** baojg has joined #openstack-swift12:00
*** baojg has quit IRC12:00
*** baojg has joined #openstack-swift12:00
*** baojg has quit IRC12:01
*** baojg has joined #openstack-swift12:01
*** baojg has quit IRC12:02
*** baojg has joined #openstack-swift14:02
*** baojg has quit IRC14:07
*** manuvakery has quit IRC14:19
*** new_student1411 has quit IRC14:19
*** baojg has joined #openstack-swift14:20
*** tesseract has quit IRC14:28
*** tesseract has joined #openstack-swift14:30
*** irclogbot_3 has quit IRC14:40
*** irclogbot_1 has joined #openstack-swift14:51
*** sasregulus has joined #openstack-swift14:58
*** tesseract has quit IRC15:02
*** tesseract has joined #openstack-swift15:03
*** gyee has joined #openstack-swift15:31
timburkeDHE, it goes by timestamp. so if the x-timestamps say it went POST-then-PUT, the metadata from the PUT wins. if the timestamps say it went PUT-then-POST, the metadata from the POST wins (but of course, the new *data* will be the same either way)16:08
DHEtimburke: I'm looking at making a custom diskfile implementation, but want to do it right. worried about a race between multiple object servers completing a PUT racing against an incoming POST16:22
DHEmy plan is to avoid the one-directory-per-object current configuration, handling multiple uploads and tombstones in different ways16:23
zigotimburke: Building Swift for Python 3 in Debian Sid, I get a single error: http://paste.openstack.org/show/754397/16:40
zigoAny idea what's that one about? :)16:40
zigoMy /tmp is a normal ext4 filesystem, so it should be fine to use xattr...16:42
zigoTo me, it looks like the if errno.errorcode.get(e.errno) in ('ENOSPC', 'ENOTSUP', 'EOPNOTSUPP'): is missing some values, somehow ...16:44
* zigo is trying to print the value of the exception...16:50
timburkezigo, here, i guess? https://github.com/torvalds/linux/blob/fec88ab0af9706b2201e5daf377c5031c62d11f7/fs/xattr.c#L424-L42617:09
timburkehmm...17:09
zigoSo, ERANGE ?17:10
* zigo is still not finished to prepare a test env17:10
timburkeat least, that's what *my* errno.errorcode[34] says17:11
*** e0ne has joined #openstack-swift17:12
zigoWill try.17:13
*** baojg has quit IRC17:14
*** baojg has joined #openstack-swift17:15
*** baojg has quit IRC17:15
*** baojg has joined #openstack-swift17:15
timburkeso i guess the xattr *name* is too long... but 22 chars doesn't seem *so* long? i wonder where/how XATTR_NAME_MAX gets defined...17:16
*** baojg has quit IRC17:16
timburkeyeah, 255 seems more reasonable: https://github.com/torvalds/linux/blob/851ca779d110f694b5d078bc4af06d3ad37169e8/include/uapi/linux/limits.h#L1517:16
*** baojg has joined #openstack-swift17:16
*** baojg has quit IRC17:17
*** baojg has joined #openstack-swift17:17
*** baojg has quit IRC17:17
*** baojg has joined #openstack-swift17:18
*** baojg has quit IRC17:18
*** baojg has joined #openstack-swift17:19
*** baojg has quit IRC17:19
*** baojg has joined #openstack-swift17:19
timburkethe ext4 code for it looks similar: https://github.com/torvalds/linux/blob/master/fs/ext4/xattr.c#L2317-L231817:19
zigotimburke: This fixes it! :)17:20
zigotimburke: I'll open the patch review soon.17:20
*** baojg has quit IRC17:20
*** baojg has joined #openstack-swift17:20
timburkebut it's so weird! what's the xattr name limit for you??17:20
*** baojg has quit IRC17:21
*** baojg has joined #openstack-swift17:21
zigoOh, what is swift-container-deleter for?17:21
*** baojg has quit IRC17:21
*** baojg has joined #openstack-swift17:22
*** baojg has quit IRC17:22
*** baojg has joined #openstack-swift17:23
*** baojg has quit IRC17:23
*** baojg has joined #openstack-swift17:23
*** baojg has quit IRC17:24
*** baojg has joined #openstack-swift17:24
*** baojg has quit IRC17:25
*** altlogbot_3 has quit IRC17:25
*** baojg has joined #openstack-swift17:25
*** baojg has quit IRC17:25
*** irclogbot_1 has quit IRC17:26
*** baojg has joined #openstack-swift17:26
*** baojg has quit IRC17:26
*** irclogbot_0 has joined #openstack-swift17:29
timburkethere are a few ways to clean up data in swift: you delete a bunch of names one by one, you can send a list of names to the bulk-delete api if that's enabled, or you can mark an entire account as deleted and have the account-reaper clean it up in the background17:31
*** irclogbot_0 has quit IRC17:32
zigotimburke: So, swift-container-deleter is a service that will do this in the background?17:33
timburkenow we've got a fourth way: operators (at the moment; i'm hopeful about turning this into a client-facing api) can delete portions of a single container's namespace. it does listings against the container and queues up deletes for the expirer to process async17:33
timburkenot a service; command line tool. but yeah17:34
timburkei'd like to expand on it in two major ways: first, expose it as a client-facing api. second, make it so you can "reap" a single container -- mark it such that subsequent requests to it will 410, and have a background daemon (replication, maybe?) queue up expirer work to clear it out. once all the data's gone (and some additional amount of time has passed, to ensure async pendings have landed) actually delete the DB17:37
timburkebut this was a good first step17:37
*** irclogbot_1 has joined #openstack-swift17:39
*** altlogbot_1 has joined #openstack-swift17:41
*** tesseract has quit IRC17:45
*** openstackgerrit has joined #openstack-swift17:54
openstackgerritThomas Goirand proposed openstack/swift master: Fix test_parse_get_node_args  https://review.opendev.org/67089417:54
zigoThere you go!17:58
openstackgerritTim Burke proposed openstack/swift master: Authors/changelog for 2.22.0  https://review.opendev.org/66899018:13
claygtimburke: Thiago pointed out that the character check in hardlinks is going to make it difficult to do a hardlink to a manifest: https://review.opendev.org/#/c/633094/12/swift/common/middleware/symlink.py@26618:38
patchbotpatch 633094 - swift - Allow "harder" symlinks - 12 patch sets18:38
claygIn fixing that up I had to allow symlink to peak into 'x-object-sysmeta-slo-etag' (since it's right of slo) - but also remove the double quote from the dis-allowed chars πŸ€”18:39
claygwould it be better to maybe ... strip " and *then* check for disallowed chars?18:39
claygI can't think of a good way to avoid leaking the slo sysmeta name into symlink18:39
*** rdejoux has quit IRC18:49
openstackgerritClay Gerrard proposed openstack/swift master: Allow "harder" symlinks  https://review.opendev.org/63309418:56
zigotimburke: I haven't tested much, but so far, Swift on Pytohn 3 worked for me in Debian. I was able to create a container and an object in it...18:58
timburke\O/18:59
timburkealways good when the sniff-tests pass :-)18:59
zigoI'm uploading to Debian experimental, so that we can process other packages first (swauth and others...)18:59
zigotimburke: You haven't released since Stein, right?18:59
zigotimburke: Is an intermediary release planned before Train?19:00
timburkeclayg, yeah, that kinda sucks... and it'll need the s3 sysmeta variant, too...19:00
timburkezigo, no, we haven't released since stein. yes, we're planning to. real soon, in fact; i was waiting for a few more py3 patches to land, but now i think i'm good to move forward on https://review.opendev.org/#/c/668990/19:01
patchbotpatch 668990 - swift - Authors/changelog for 2.22.0 - 4 patch sets19:01
zigoGood to know!19:02
claygidk, this isn't great - now versoined writes needs to know about slo too so that it can create hard links to manifests19:21
claygmaybe hardlinks to manifests should use the manifest's objects etag... it's in the listing and you can get it with `multipart-manifest=get`19:21
claygas it turns out it's also still in the put_resp when versioned writes gets ahold of it - because slo hasn't clobbered it with the calculated value it stuffed in sysmeta19:22
*** baojg has joined #openstack-swift19:27
*** baojg has quit IRC19:32
claygwell, that may not be quite right -  SLO put response encodes a lot of detail in the response body at the end of the heartbeat19:33
claygthe actual PUT resp of the manifest comes through versioned writes mw, but isn't retruned to the client...19:33
claygI think from a client perspective it's better to let them provide the manifest etag tho... so I guess versioned_writes will just have to learn how to spot a SLO manifest PUT19:34
*** e0ne has quit IRC19:52
*** e0ne has joined #openstack-swift19:53
claygmaybe I'll allow .... both 😬19:58
clayghttps://media0.giphy.com/media/146heXDX89mUgw/source.gif19:58
*** altlogbot_1 has quit IRC20:10
*** altlogbot_0 has joined #openstack-swift20:14
openstackgerritClay Gerrard proposed openstack/swift master: Allow "harder" symlinks  https://review.opendev.org/63309420:20
*** pcaruana has quit IRC20:29
claygjesus, now I'm parsing slo_etag of of container listing etag feilds so that I have it handy for when I do stack pop 😞20:36
*** BjoernT has joined #openstack-swift20:37
*** BjoernT_ has joined #openstack-swift20:41
*** BjoernT has quit IRC20:42
*** persia has left #openstack-swift20:47
openstackgerritClay Gerrard proposed openstack/swift master: WIP: symlink-backed versioned_writes  https://review.opendev.org/63385720:53
*** e0ne has quit IRC21:03
*** e0ne has joined #openstack-swift21:19
*** e0ne has quit IRC21:20
*** e0ne has joined #openstack-swift21:22
*** e0ne has quit IRC21:24
*** e0ne has joined #openstack-swift21:24
*** baojg has joined #openstack-swift21:28
*** baojg has quit IRC21:32
*** e0ne has quit IRC21:39
*** BjoernT_ has quit IRC22:07
timburkeclayg, what would you expect the py2/py3 option to look like in vsaio? `export PYTHON=python2  # or python3`? `export USE_PYTHON3=false  # or true`?22:31
claygUse py3 wfm - probably less work to support?22:34
claygLike if someday something only works in py3 we don’t have to parse the python option πŸ€”22:34
mattoliveraumorning22:53
*** tkajinam has joined #openstack-swift22:59
*** rcernin has joined #openstack-swift23:29
*** baojg has joined #openstack-swift23:29
*** e0ne has joined #openstack-swift23:31
*** baojg has quit IRC23:33
*** e0ne has quit IRC23:36
*** e0ne has joined #openstack-swift23:38
*** e0ne has quit IRC23:42

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