Wednesday, 2025-05-28

opendevreviewTim Burke proposed openstack/swift master: ringv2: Use dataclasses  https://review.opendev.org/c/openstack/swift/+/95104900:57
opendevreviewTim Burke proposed openstack/swift master: ringv2: Use dataclasses  https://review.opendev.org/c/openstack/swift/+/95104903:25
timburke_mattoliver, see what you think of ^^^ -- i might squash it in03:27
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: WIP object_versioning: make is_enabled tri-state  https://review.opendev.org/c/openstack/swift/+/95110809:50
opendevreviewShreeya Deshpande proposed openstack/swift master: proxy-logging: Add real-time transfer bytes counters  https://review.opendev.org/c/openstack/swift/+/93091815:21
DHEwell, I can confirm ZFS works... xattrs and all. 16:39
opendevreviewMerged openstack/swift master: Add config option for whether to skip s3_acl-requiring tests  https://review.opendev.org/c/openstack/swift/+/94971618:05
opendevreviewMerged openstack/swift master: CI: run S3 cross-compat tests as part of DSVM jobs  https://review.opendev.org/c/openstack/swift/+/94213318:05
*** timburke_ is now known as timburke20:59
timburke#startmeeting swift21:00
opendevmeetMeeting started Wed May 28 21:00:11 2025 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
opendevmeetThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
mattolivero/21:00
timburkei don't have too many topics, mostly just follow-up from a couple weeks ago21:02
timburkeas usual, the agenda's at21:02
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:02
timburkefirst up21:02
timburke#topic aws-chunked and additional checksums21:03
jianjiano/21:03
timburkewe still need to review & merge checksum validation21:03
timburke#link https://review.opendev.org/c/openstack/swift/+/94407321:03
timburkebut it's been going well since we carried it in prod21:04
timburkewe've even seen clients trying to use crc64nvme, so i'm glad we had that follow-on ready to go21:04
timburke#link https://review.opendev.org/c/openstack/swift/+/94614121:04
jianjian-88 +2061, wow, quite a large patch21:04
acoleso/21:05
mattoliveroh nice, if people use it let's look at getting that landed too!21:05
timburkedecent majority of it should be in test coverage, though, so that's good21:05
acolesare we still waiting for a py version bump to land the checksum validation? something to do with up-reving boto3 for tests??21:05
timburkenope -- i decided to just split the test expectations based on version of boto3 available21:06
acolesok21:06
acolesI'll try to revisit that review then21:06
timburkefwiw, i think that was only needed in test_different_checksum_requested21:07
timburkethere's also a follow-up for s3token to ensure that aws-chunked works even when the secret key didn't come out of cache21:08
timburke#link https://review.opendev.org/c/openstack/swift/+/94967121:08
timburke...which would be nice to have before our next upstream release (not that i'm in a rush for that, but good to mention early)21:09
timburkenext up21:10
timburke#topic swiftclient release21:10
timburkewe had one! 4.8.0 is out and available21:10
timburkeit also dropped support for py36, so we're (slowly) getting closer to openstack's support matrix ;-)21:12
mattoliver\o/21:12
jianjiangreat!21:12
timburkesorry we didn't get more landed (i know there was some hope of getting retries for bytes literals merged)21:13
timburke#link https://review.opendev.org/c/openstack/python-swiftclient/+/91870121:13
timburkebut there's always more releases we can make!21:13
jianjian🙂 will wait for next release then21:13
timburkenext up21:14
timburke#topic conditional PUTs for s3api21:14
timburke#link https://review.opendev.org/c/openstack/swift/+/94968021:14
timburkeit merged! thanks for your help, jianjian!21:14
jianjian\o/21:15
timburkewe've got it out in prod, and our preliminary testing shows it working as we'd hoped21:15
mattolivernice work timburke  and jianjian 21:16
timburke(in particular, we had a user interested in lancedb using swift's s3api as a backend, and jianjian's manual testing showed it working -- still waiting to here back from our users)21:16
timburke#link https://github.com/lancedb/21:16
jianjianyep, also the s3api support of if-none-match: * works well with aws cli and boto3 SDK as well21:17
timburkeall right, last topic from me21:18
timburke#topic MANIFEST.in removal21:18
timburkei merged a change a bit ago because it seemed like this really wasn't necessary anymore21:18
timburke#link https://review.opendev.org/c/openstack/swift/+/94936821:18
timburkei built wheels before and after the patch, and everything seemed right21:19
timburkebut the next time we went to build RPMs for our internal release, they were missing the xml schema files used by s3api!21:20
mattoliveryeah, it seems this is still the way to tell setuptools to include extra files21:20
timburkeas a result, s3api requests that included xml bodies would all fail (multi-deleted, mpu-completions, probably others)21:20
timburkei proposed a revert for it21:21
timburke#link https://review.opendev.org/c/openstack/swift/+/95061521:21
timburkebut i still haven't pinned down where things went wrong -- my assumption is that our build process's old versions of pbr and setuptools were to blame21:22
mattoliverI've managed to fix it downstream in our rpm build but specificalyy including them. But that might not help others. So unless there is another way to specify extra files in setuptools we might need to put that back21:23
timburkeand now that we can actually declare minimum versions of those in pyproject.toml, i think i might prefer to just make sure those minimums are right and keep the MANIFEST.in out21:23
opendevreviewYan Xiao proposed openstack/swift master: Object-server: change labeled timing metrics sample rate for debugging requests  https://review.opendev.org/c/openstack/swift/+/95104221:23
timburkemattoliver, did you explicitly add the files in our spec file, or did you try updating pbr/setuptools? i think clayg tried the latter approach, but ran into other issues because of our old python(/OS?) :-/21:24
mattoliveroh good thinking. Maybe need to play with pbr and setuptools versions then an find the culprit if its just a version then. 21:24
mattoliverI just added the files, I mean the spec already explicitly grabs the man files etc21:25
timburkeyeah, i figured i ought to start with trying to build with our lower-bounds, as they're pretty reasonable: https://github.com/openstack/swift/blob/master/pyproject.toml#L221:27
timburkereleased in '22 and '2321:27
claygyeah, our .spec for setuptools ~41 expected some bootstrap.py script that doesn't exist  ~6421:27
timburkeso i'll plan to try that out in the next day or two and post results in a comment on the revert21:28
mattoliverkk sounds like a plan21:28
mattoliverclayg: oh great. So setuptools spec needs a bunch of updating then. 21:29
timburkebut i wanted to make sure to bring it up in case cschwede_ or anyone else bumps into a similar issue. if it's more than just us, i'm a lot more inclined to merge the revert21:29
mattolivermaybe it's already done in the 3.10 branch21:29
timburkei think it might be21:30
timburkeall right, that's all i've got21:30
timburke#topic open discussion21:30
timburkeanything else we ought to talk about this week?21:30
acolesjust an fyi, I''m ramping back up on feature/mpu work21:30
mattolivernice21:31
acolespicking up where I left off, and pursuing a new approach to reliably detecting obsolete MPUs for orphan cleanup21:31
mattoliverI've been a bit distracted with some downstream work, but I looked at the dataclass ringv2 patch tho. Nice we can start using more modern python concepts (even if its from 3.7) :P  21:32
mattoliverI want to finally push up a rebase of the tracing chain.. otherwise it'll get harder and harder as time goes on. Hopefullly get back to this sooner rather then later.21:33
mattolivermostly got it ready, just need to test it in vsaio to make sure everything is working21:34
timburkeoh yeah, i should take a look at https://github.com/NVIDIA/vagrant-swift-all-in-one/pull/134 ...21:36
mattoliverwoah 2022... really should land this one day, maybe this year will be there year :P 21:38
mattoliverthat vsaio probably needs a rebase too21:38
mattoliveranyway, that's all I've got21:38
mattoliveroh I did remember the meeting last week too, which was nice :P 21:39
timburke🎉21:39
timburkethanks again for leading that meeting slot21:40
timburkeall right, i think i'll call it early then21:41
timburkethank you all for coming, and thank you for working on swift!21:41
timburke#endmeeting21:42
opendevmeetMeeting ended Wed May 28 21:42:02 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:42
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2025/swift.2025-05-28-21.00.html21:42
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2025/swift.2025-05-28-21.00.txt21:42
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2025/swift.2025-05-28-21.00.log.html21:42
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org is temporarily unreachable due to an ongoing issue in the hosting provider where it resides22:08

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!