Wednesday, 2025-06-04

mattoliverafternoon/morning07:01
*** cschwede_ is now known as cschwede07:01
mattoliverAnyone here for the 0700 swift meeting?07:02
mattoliverwell maybe I should start it first :P07:02
cschwedeo/07:02
mattoliver#startmeeting swift07:02
opendevmeetMeeting started Wed Jun  4 07:02:58 2025 UTC and is due to finish in 60 minutes.  The chair is mattoliver. Information about MeetBot at http://wiki.debian.org/MeetBot.07:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:02
opendevmeetThe meeting name has been set to 'swift'07:02
mattoliverhey cschwede 07:03
cschwedeHello mattoliver!07:03
mattoliverAs usual the agenda is at:07:03
mattoliver#link https://wiki.openstack.org/wiki/Meetings/Swift07:03
cschwedeI don't have much news on #1 (bug triage) and #2 (eventlet), been on PTO07:03
mattoliverI did update it, but most topics are really just quick updates07:04
mattoliverfair enough, this might be a quick one then 07:04
mattoliverSo we'll skip the first to topics but instead all hope cschwede had a PTO :) 07:05
mattoliver*two topics07:05
mattoliver#topic SO_TIMESTAMP/SO_TIMESTAMPING patch07:05
mattoliverNot to much on this really, but if I keep it in, it reminds me I need to work on it :P 07:05
mattoliver#link https://review.opendev.org/c/openstack/swift/+/94410307:06
cschwedeI think I can give that one a try on my side this week as well, if that helps07:06
mattoliverQuickly looking at it, it's stuck on me it seems :P 07:07
mattoliverbut yeah, your feed back would be great!07:07
mattoliverEsp with the extra timeout I have in there. I had to do it, but is it worth is.. I think so, but happy to be wrong.07:07
mattoliver#topic ringv207:08
cschwedeI think this will be a very helpful feature for larger deployments to track things down07:08
cschwedeWell, both actually (timestamps+ringv2) ;)07:08
mattoliverWe've just enabled it in all of our prod clusters, and working great. We haven't crossed to the bigger dev_id bridge yet, but that'll probably be at the end of the month.. so will let everyone know how it goes07:09
cschwedeSounds great actually!07:10
mattolivertimburke just squashed a patch into it to go from using named tuples to dataclases.. so finally getting to use more modern py3 things (even if it was introduced in py3.7 :P)07:10
mattoliveryeah, we'd tested it a bunch, even forced a rebuild of a wider dev_id ring and deployed it to a few racks just to check and make sure memory usage and everything else was working as expected in prod. 07:11
mattoliverAll went great, so nvidia is now running it07:12
mattoliveroh the link07:12
mattoliver#link https://review.opendev.org/c/openstack/swift/+/83426107:12
cschwededid you notice any big difference in memory usage at all?07:12
mattoliveronly what was expected.. but was a little less then expected.. we basically add 2 bytes for dev id in the replica2part2dev. so 2 * 2^partpower * replicas was back of the napkin.07:14
mattoliverSo should be worse in EC (more replicas) and when each worker of a services auto-reload the ring (after it's forked at startup). 07:15
mattoliverSo initially they can all share the loaded ring. Then memory usage goese up a little as you replace the ring on a node.07:16
mattoliverBut I feel like it was less then I expected.. so went fine for us. I can find some numbers and pop then in IRC if people are interested.07:16
cschwedeno worries, i was just curious. and less than expected sounds good!07:17
mattoliver#topic aws-chunked07:17
mattoliver#link https://review.opendev.org/c/openstack/swift/+/94407307:18
mattoliverI think this is ready for reviews again. And we need to land this before the next swift release, because it'll actually allow us to support the extra algorithms given to us :P 07:19
mattoliverie, so we can actually check the crc checksums. 07:19
mattoliverI started looking, so I need to finish reviewing it.07:19
mattoliverNo much else for that topic07:20
mattoliver#topic swiftclient release07:20
mattoliverWell it was released07:20
mattoliverThat's basically that update :P 07:20
cschwede\o/07:20
mattoliverLast 2 topics I just added not long ago. 07:21
mattoliver#topic Coop tokens07:21
mattoliver#link https://review.opendev.org/c/openstack/swift/+/90896907:21
mattoliverWe've been carrying this and running it in prod for like a year or so, and it's awesome. 07:21
mattoliverWe talked about it at the last PTG07:21
mattoliverjianjian has been cleaning it up and getting it ready to actually merge. And I think we should. 07:22
cschwedeWell, if you run it like a year in prod, it sounds pretty good, no?07:22
mattoliveryeah, exactly 07:23
mattolivercant ask for more testing :P 07:23
cschwederight :)07:23
mattoliverAs it currently stands it helps shard range caches and stops a thundering herd problem. So everyone should benefit if they run sharding.. but we probably could move it to more caching areas. 07:24
mattoliverbasically just wan't to shout it out to everyone, to give kudos to jian and say we need to review it. (mostly talking to myself there).07:25
mattoliverLast topic on the agenda I have, is basically because of Tims comments in channel earlier07:26
mattoliver#topic Move to pyproject07:26
mattoliver#link https://review.opendev.org/c/openstack/pyeclib/+/94754307:26
mattoliverTim's been testing stuff on a mac for some reason. And things can't currently build. 07:27
mattoliverTo quote tim above: "we should maybe think about merging that pyproject.toml pyeclib change -- wheel building on OS X is currently busted (at least for me) and in such a way that setup.py doesn't even realize it's running on a mac07:27
mattoliverthat particular part seems to trace back to platform.platform() returning something like "macOS-..." instead of "Darwin-..."07:27
mattoliverbut even addressing that, our existing setup.py doesn't seem to properly respect CFLAGS/LDFLAGS, so it couldn't find my custom libec install location. the switch to pyproject.toml (and with it, getting out of setuptools' way a bit) fixed that, though!"07:27
mattoliverNot sure how that comes out, but there it is :P 07:28
* cschwede looking at this right now07:28
mattoliver There is still a setup.py so things on older systems should still build fine so long as there is a new enough setuptools. 07:29
mattoliverI guess I could go double check this on some old systems I'm still building for. 07:29
mattoliverCough centos7 cough07:29
cschwedeyou added the s3api xml files manually in your .spec, right?07:29
mattoliverYeah, I did to get around the other issue.07:30
mattoliveralthough maybe we should think about landed the MANIFEST revert change07:30
mattoliverThough I think later setuptools probably does the right thing, so maybe not.07:31
mattoliverBut put it into our spec file, as it doesn't hurt to make sure the files are there. 07:31
cschwederight07:32
mattoliverIt's getting too late to me to play with it today. But I'll attempt a build on our centos7 env with the pyproject change tomorrow and put the results as a comment.07:32
mattoliverok, so according to the pyproject.toml we need `setuptools>=74.1` 07:33
mattoliverSo thats what we need to check. or also put in requirements maybe 🤷07:34
mattoliveroh that's pyeclib I have there... is that the one he means. 07:35
mattoliveryup it was, good07:35
mattoliverAnyway, that's all I got07:35
mattoliver#topic open discussion07:35
mattoliverAnything else to bring up this meeting?07:36
cschwedeNot from my side, thx mattoliver for all the updates!07:36
mattoliverKK, might close the meeting then! 07:36
mattoliverThanks from coming and thanks for working on swift!07:36
mattoliver#endmeeting07:36
opendevmeetMeeting ended Wed Jun  4 07:36:52 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:36
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2025/swift.2025-06-04-07.02.html07:36
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2025/swift.2025-06-04-07.02.txt07:36
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2025/swift.2025-06-04-07.02.log.html07:36
mattolivercschwede: we've had 2 new aussie people start in SRE here, and one of them says they know you from redhat (where they came from)07:37
mattoliverBrendan Shephard, worked on triple0 and heat. 07:39
mattoliverAnyway, he said you were awesome, and I couldn't agree more ;)07:39
mattoliverTime to go make dinner for the fam. o/07:39
cschwedeOh wow, that sounds nice :D Please say Hello to Brendan from me o/07:39
cschwedeThanks mattoliver :D Enjoy your dinner!07:40
opendevreviewShreeya Deshpande proposed openstack/swift master: Add SubsetMap  https://review.opendev.org/c/openstack/swift/+/94367614:52
opendevreviewShreeya Deshpande proposed openstack/swift master: proxy-logging: Add real-time transfer bytes counters  https://review.opendev.org/c/openstack/swift/+/93091815:10
opendevreviewTim Burke proposed openstack/pyeclib master: Fix memory leak  https://review.opendev.org/c/openstack/pyeclib/+/93182217:30
opendevreviewTim Burke proposed openstack/pyeclib master: Simplify error handling in pyeclib_c_get_segment_info  https://review.opendev.org/c/openstack/pyeclib/+/95179617:38
opendevreviewTim Burke proposed openstack/pyeclib master: Remove ancient Travis CI config  https://review.opendev.org/c/openstack/pyeclib/+/95179717:42
opendevreviewTim Burke proposed openstack/pyeclib master: Clean out some old cent7/cent8 setup  https://review.opendev.org/c/openstack/pyeclib/+/95179917:47
opendevreviewAlistair Coles proposed openstack/swift master: sq: proxy logging test fixups  https://review.opendev.org/c/openstack/swift/+/95180018:10
opendevreviewTim Burke proposed openstack/pyeclib master: Simplify error handling in pyeclib_c_get_segment_info  https://review.opendev.org/c/openstack/pyeclib/+/95179621:39
opendevreviewMerged openstack/pyeclib master: Remove ancient Travis CI config  https://review.opendev.org/c/openstack/pyeclib/+/95179722:36
opendevreviewMerged openstack/pyeclib master: Simplify error handling in pyeclib_c_get_segment_info  https://review.opendev.org/c/openstack/pyeclib/+/95179623:20

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