21:00:30 #startmeeting swift 21:00:30 Meeting started Wed Jan 31 21:00:30 2024 UTC and is due to finish in 60 minutes. The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:30 The meeting name has been set to 'swift' 21:00:38 who's here for the swift team meeting? 21:00:50 o/ 21:01:46 as usual, the agenda's at 21:01:48 #link https://wiki.openstack.org/wiki/Meetings/Swift 21:01:58 first up 21:02:03 #topic swiftclient 21:03:00 there are a few different patches i think are worth having before we have our caracal release later in Feb 21:03:18 #link https://review.opendev.org/c/openstack/python-swiftclient/+/903770 21:03:18 patch 903770 - python-swiftclient - Add transaction id to errors - 4 patch sets 21:04:14 seems good, as transaction ids are so useful, but it looks like acoles still has a few concerns 21:04:31 i must admit, i haven't looked at the latest patchset yet 21:04:54 #link https://review.opendev.org/c/openstack/python-swiftclient/+/848926 21:04:55 patch 848926 - python-swiftclient - shell: Print friendly account byte quotas - 3 patch sets 21:05:59 i think that's ready to go, and it's really nice being able to easily tell what order of magnitude the quota is, rather than needing to count decimal places 21:06:15 and 21:06:18 #link https://review.opendev.org/c/openstack/python-swiftclient/+/907118 21:06:18 patch 907118 - python-swiftclient - WIP: test for invalid segment name - 3 patch sets 21:06:44 which unfortunately is closer to a bug report ;-) 21:08:13 but there's a path-normalization but in swift client that one of our users turned up; a command like `swift upload container/prefix . --use-slo -S ` will work "fine" up until you need to actually make some SLOs 21:09:09 i'll write up a bug report with more details, but it seems to come down to a discrepancy between what swiftclient thinks the (segment) paths should be vs what urllib3 thinks 21:09:49 interesting 21:09:56 it *also* led me to discovering that you can have data in a container that swiftclient can't delete (!) 21:12:23 if you use curl to create an object named `./obj` (so, full url-encoded path might look like `/v1/AUTH_test/container/%2E/obj`), swiftclient tries to delete `obj` instead, even if you're trying to delete the whole bucket 21:13:42 i'll try to get a proper fix up assuming no one else picks it up 21:14:08 #topic part-number support 21:14:39 we still haven't merged any of these yet, though acoles has done some further testing of AWS's behavior 21:14:46 #link https://review.opendev.org/c/openstack/swift/+/906906 21:14:47 patch 906906 - swift - DNM: cross-compat test single-part obj partNumber ... - 1 patch set 21:15:34 unfortunately, indianwhocodes was recently injured, so he might not be able to circle back to the patches for a bit 21:16:23 sorry to hear that 21:16:47 i might wrangle the chain a bit to keep it from stalling out 21:17:09 yeah, we're all hoping him a speedy recovery, too 21:18:25 speaking of s3api support... 21:18:47 #topic aws-chunked support 21:19:31 i actually forgot to put this on the agenda, but we've seen some interest from our users in mountpoint-s3 21:19:36 #link https://github.com/awslabs/mountpoint-s3/ 21:20:18 unfortunately, it uses some features (at the very least, chunked transfers) that s3api doesn't support yet 21:20:45 so we might refresh a patch that tried to add support 21:20:47 #link https://review.opendev.org/c/openstack/swift/+/836755 21:20:48 patch 836755 - swift - Add support of Sigv4-streaming - 8 patch sets 21:21:35 unfortunately it doesn't work out of the box -- but i'm interested in getting it there 21:22:01 and it's always nice to have a ready client to test with :-) 21:22:44 last up 21:22:49 #topic py312 support 21:22:52 sigv4 streaming, wow 21:23:07 oh sorry for the overlapping 21:23:31 no worries :-) 21:23:39 i'd love some reviews on any of these patches 21:23:40 #link https://review.opendev.org/q/project:openstack/swift+topic:py312 21:24:18 that's all i've got 21:24:24 #topic open discussion 21:24:38 anything else we should discuss this week? 21:25:54 not for my side 21:27:00 all right, then i'll let you get on with your morning :-) 21:27:09 thanks timburke! 21:27:10 thanks for coming, and thank you for working on swift! 21:27:14 #endmeeting