Wednesday, 2025-08-06

opendevreviewMerged openstack/liberasurecode master: Make sure alg_sig_handle->tbl1_l is defined  https://review.opendev.org/c/openstack/liberasurecode/+/95621401:58
opendevreviewAlistair Coles proposed openstack/swift master: s3api: func test MPU requests with x-delete-at  https://review.opendev.org/c/openstack/swift/+/95664509:42
opendevreviewTim Burke proposed openstack/pyeclib master: Improve error message when using closed ECDriver instances  https://review.opendev.org/c/openstack/pyeclib/+/95660915:56
opendevreviewTim Burke proposed openstack/pyeclib master: Prep for type annotations  https://review.opendev.org/c/openstack/pyeclib/+/95661015:56
opendevreviewTim Burke proposed openstack/pyeclib master: Add type annotations  https://review.opendev.org/c/openstack/pyeclib/+/95661115:56
opendevreviewTim Burke proposed openstack/pyeclib master: Re-org code so we can ship the new pyi file for the c extension  https://review.opendev.org/c/openstack/pyeclib/+/95661215:56
opendevreviewClay Gerrard proposed openstack/swift master: Fix another way mw may encouter invalid swift paths  https://review.opendev.org/c/openstack/swift/+/95673019:54
opendevreviewShreeya Deshpande proposed openstack/swift master: proxy-logging: Add real-time transfer bytes counters  https://review.opendev.org/c/openstack/swift/+/93091820:54
*** timburke_ is now known as timburke20:59
timburke#startmeeting swift21:00
opendevmeetMeeting started Wed Aug  6 21:00:06 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
timburkesorry i skipped the meeting a couple weeks ago -- i think i just got busy and forgot21:02
timburkethanks for keeping the rhythm going for the 0700 meeting, though, mattoliver!21:02
timburkeas usual, the agenda's at21:02
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:02
mattoliverNps, it happens21:02
timburkefirst up21:02
timburke#topic vPTG21:03
timburkejust another quick reminder on the vPTG in a couple months21:03
timburkei think i'll keep the topic there at least until i actually get an etherpad up to gather topics ;-)21:03
timburkenext up21:04
timburke#topic ring v221:04
timburkethe big hairy new-format patch landed!21:04
timburkethanks mattoliver and clayg for reviewing it21:04
timburkenow we get to do the even-more-interesting bits ;-)21:05
mattoliverYeah, I decided to take advantage of the clay +2 and comments. And decided to land it and figured anything else can be follow ups21:05
mattoliver+10021:05
timburkethere were a couple rough edges that i wouldn't have minded smoothing out -- but at the same time, i'm not sure i could have without breaking our prod clusters that were already using it :-(21:06
timburkeor at least, not easily21:06
mattoliverSorry if I jumped the gun a little then21:07
timburkeeh, no worries. i was feeling stuck -- at least now, the path forward if i want to fix them is more clear (do the tricky thing, so i don't break other people's clusters, too)21:07
timburkenext up21:08
timburke#topic new backend for liberasurecode21:08
timburkethe libec change is looking good21:08
timburke#link https://review.opendev.org/c/openstack/liberasurecode/+/95428521:08
mattoliverjust the name 21:08
timburkeand i haven't heard anyone offer better names for it -- if that continues to be the case, i'm inclined to merge it by the end of the week21:09
mattoliveryeah, fair enough, sounds like a good plan21:09
timburkethere's also a corresponding patch for pyeclib to support it21:09
mattoliverI'll keep my naming thinking hat on21:09
timburke#link https://review.opendev.org/c/openstack/pyeclib/+/95610921:10
opendevreviewMerged openstack/swift master: crypto: Fix traceback on non-utf8, non-swift paths  https://review.opendev.org/c/openstack/swift/+/95362321:10
timburke(needs a little more, but on the whole i've been pleased by how simple it is to add new backends there)21:11
timburkenext up21:11
timburke#topic type hinting in pyeclib21:12
timburkeso while i was poking around in pyeclib, and exchanging review comments about how swift now has some (not-checked) type hints in it, i got to thinking about how we'd want to go about using and enforcing type hints, and thought pyeclib would be a decent place to start21:13
mattoliverWell it's a smaller codebase so could be a good place to start and test I guess21:14
timburkeyup: it's small, self-contained, has no dependencies...21:15
timburkeso i spent a day or so trying it out, eventually landing on a chain that ends with21:15
timburke#link https://review.opendev.org/c/openstack/pyeclib/+/95661221:15
mattoliverkk, will take a look21:16
timburkethere were definitely a few bugs caught as a result! i tried to structure the chain so we have the functional changes in the fron, then a patch that just adds annotations, then a patch to fix up packaging21:17
timburkefirst two patches are definitely ready to take a look at; last two still need a little work, though21:17
mattoliverkk21:18
timburkebut getting a pyi file at the end of it all that describes the interface for pyeclib_c (the C extension) was pretty nice!21:18
timburkeas i got in there, i realized there was a decent bit of cruft, though, which brings me to...21:19
timburke#topic removing dead interfaces from pyeclib21:20
timburkewe've got some weird warts in pyeclib. there's an ECStripingDriver that basically tries to mimic RAID 0, and an ECNullDriver that i guess was used for benchmarking?21:21
mattoliveryeah, I assumed the null driver was for something like that21:22
timburkei suspect both of them were added to demonstrate the library_import_str interface for ECDriver -- they're certainly the only known users of it21:23
timburkebut the striping driver doesn't even work with ECDriver! stripes require m=0, while ECDriver requires m>021:23
timburkeand then check_metadata seems weird -- it requires that you pass in *all* of the frags (data and parity)21:25
timburkei kinda want to just rip all of that out21:25
timburkeand probably do a v2 bump for the library21:25
timburkewanted to start shopping the idea, and get input on whether i ought to try to start emitting deprecation warnings about it now21:26
mattoliverright, so one doesn't work and the other is clearly a noop. so yeah they're obviously not used. 21:27
timburkei mean, i guess someone could try to instantiate the striping guy directly -- but i don't know why anyone would want it, since it can only harm durability21:28
mattoliverI guess one could, I wonder if there is a git entry with info when it was added. ..but I don't see a harm  in a dep warning. Seems like as good time as any.21:30
timburke👍21:31
timburkeok, one last-minute topic21:31
timburke#topic releases21:32
timburkei'm inclined to do libec and pyeclib releases shortly after getting the new backend patches merged21:32
timburkeand i also started putting together release notes for a swift release (though a few more things have merged since i last updated it)21:33
timburke#link https://review.opendev.org/c/openstack/swift/+/95633321:33
timburkei'll be out next week, so if i don't get to them this week, it might be more like two ;-)21:34
mattoliverdefinitely!21:34
timburkebut i'd appreciate eyes on the release notes if anyone has a chance21:34
timburkethat's all i've got21:34
mattoliverdo we want to merge your ringv2 followup before the swift release? 21:34
mattoliverI'll definitely give it a read. 21:35
timburkemaybe? see what you think. part of it makes things more brittle (by blowing up on unrecognized checksums) which might complicate things a little. but clayg seemed to like the idea, i think?21:36
timburke#topic open discussion21:36
timburkeanything else we should bring up this week?21:37
mattoliverI had a patch to add a past2timestamp structure in with the history table stuff... but instead am thinking about just moving the past_past_moves and past_part_moves_epoch in, which basically give a similar answer.. except to the hour grainulatity for older part moves. 21:38
mattoliverthe hour granularity might be good enough 🤷 Plus it moves an existing builder structure into the ring.21:39
mattoliverAnyway, just playing for now. I see how it shakes out21:40
timburkenice -- yeah, i was thinking i should take a look at the state of the history patch and think about where we want to go with it21:40
timburkeoh yeah, i got the gate passing for those backports of the aws-chunked/validate-checksums-on-upload work: https://review.opendev.org/q/project:openstack/swift+branch:stable/2025.1+is:open21:41
mattoliveryeah, that'll be great if you get the chance. Now's the time to change things on it. 21:41
mattoliverIt does feel weird, orig wrote it so long ago it feels like a different me, so keep playing with it to see if there are other possible improvements. I'd also like to go revisit the reconstructor changes to see if they still make sense. 21:42
timburkehow do we feel about those stable patches? it might be stretching the scope for stable a little, but zigo indicated it'd be nice to have21:42
timburkemattoliver, yeah, i know that feeling21:43
mattoliveryeah, I'd say it might be stretching a little. but the fact that it fixes boto based clients and because zigo  wants it, I say let's backport em ;) 21:44
zigoYeah, as more and more software relly on the aws-chunked, it is a pain especialy because of boto indeed.21:45
timburkeall right, i'll look at getting that merged then, and add a stable release to the list of things i oughta get out there ;-)21:46
zigoIf backported, there's a chance I can push it as a Debian Stable proposed update, otherwise no hope until Debian 14 (hint: Debian 13 is to be released this week-end).21:47
mattolivernice, then let's get it in ;) thanks for getting them together timburke 21:47
timburkesounds good -- thanks for keeping us aware of downstream impacts, zigo!21:48
zigo2 more years without proper S3 support does not feel nice...21:48
timburkeall right, i think i'll call the meeting a little early, let matt get an extra ten minutes in his morning21:48
timburkethank you all for coming, and thank you for working on swift!21:48
timburke#endmeeting21:49
opendevmeetMeeting ended Wed Aug  6 21:49:01 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:49
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2025/swift.2025-08-06-21.00.html21:49
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2025/swift.2025-08-06-21.00.txt21:49
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2025/swift.2025-08-06-21.00.log.html21:49
mattoliverthanks timburke, now I can go get breakfast :) 21:49
opendevreviewMerged openstack/swift stable/2025.1: s3request: refactor to introduce SigChecker classes  https://review.opendev.org/c/openstack/swift/+/95619123:12
opendevreviewMerged openstack/swift stable/2025.1: s3request: refactor error handling while reading input  https://review.opendev.org/c/openstack/swift/+/95620023:12
opendevreviewMerged openstack/swift stable/2025.1: Add support of Sigv4-streaming  https://review.opendev.org/c/openstack/swift/+/95619223:12
opendevreviewMerged openstack/swift stable/2025.1: utils: Add CRCHasher and crc32c implementation  https://review.opendev.org/c/openstack/swift/+/95619323:12
opendevreviewMerged openstack/swift stable/2025.1: s3api: Validate additional checksums on upload  https://review.opendev.org/c/openstack/swift/+/95619423:13
opendevreviewMerged openstack/swift stable/2025.1: s3api: Add support for crc64nvme checksum calculation  https://review.opendev.org/c/openstack/swift/+/95619523:13

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