07:06:02 <mattoliver> #startmeeting swift
07:06:02 <opendevmeet> Meeting started Wed Jul 30 07:06:02 2025 UTC and is due to finish in 60 minutes.  The chair is mattoliver. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:06:02 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
07:06:02 <opendevmeet> The meeting name has been set to 'swift'
07:06:39 <mattoliver> Agenda as always (which is currently not updated) is at:
07:06:46 <mattoliver> #link https://wiki.openstack.org/wiki/Meetings/Swift
07:06:59 <mattoliver> #topic Bug triage
07:07:17 <mattoliver> cschwede: sorry to keep probing you on this every 2 weeks :P
07:07:50 <mattoliver> It's alot of work and I think last time we talked about slowing down if you need to catch your breath (and we all should be helping you).
07:08:18 <cschwede> No problem :) No updated bugs this time, but was wondering if we need a different approach at all. Eg. closing bugs > X years old or sth similar.
07:08:45 <cschwede> Quite a few bugs need a good amount of time to check if they are still valid
07:09:09 <mattoliver> oh maybe :hmm:
07:09:42 <mattoliver> Nice project for any new swift devs who want to get their swift feet wet.
07:09:52 <cschwede> I mean - if they are open for eg 5+ years, they are likely not important at all?
07:09:53 <mattoliver> ie, checking bugs.
07:10:00 <mattoliver> lol, true
07:10:39 <mattoliver> maybe we should get some metrics on our bugs. I mean maybe even 10years would get rid of alot :P
07:10:40 <cschwede> We don't want to scare new devs immediately away, do we? ;)
07:11:37 <cschwede> Indeed. Maybe we simply start with a generous time (5/10 years), close them and have a look at the impact.
07:11:51 <mattoliver> True. I know when I've picked bugs for newbies to work on, I somestimes start with "maybe check if its still valid". But telling them to go check all bugs would be too much
07:12:01 <mattoliver> Yeah +1
07:13:37 <acoles> is it easy to list the bugs filtered by age? perhaps we should try to at least scan the subject lines in case there are any that are obviously still valid?
07:13:41 <mattoliver> I'll let timburke__ and others who'll async have a say too. But I think it sounds reasonable.
07:14:10 <acoles> I'm thinking more of the bugs that are written more as a wish for future enhancement than an immediate code problem
07:14:52 <mattoliver> yeah, some of the low hanging fruit "feature requests" like bugs are still nice to have.
07:15:39 <cschwede> Maybe exclude wishlist bugs then? Quickly looking at the oldest bugs: https://bugs.launchpad.net/swift/+bugs?orderby=datecreated&start=0
07:16:15 <mattoliver> #link https://bugs.launchpad.net/swift/+bugs?orderby=datecreated&start=0
07:17:49 <cschwede> Maybe it's a good topic for another PTG discussion ;)
07:19:03 <mattoliver> kk. I think closing old bugs should be OK. But maybe a scan of the subjects at least would be useful. And yeah maybe keeping all wishlist makes sense.
07:19:37 <acoles> how can we see a list of in-use tags? (the first is a wishlist but is it wishlist, wish_list or ...)
07:20:27 <acoles> oh there is autocomplete for existing tags
07:20:44 <acoles> so *is* there a wishlist tag?
07:21:13 <mattoliver> there is things in wishlist importance
07:21:37 <acoles> aha, thanks mattoliver
07:21:42 <mattoliver> maybe its time to hit up the launchpad api and do some magic.
07:22:20 <cschwede> and a "low-hanging-fruit" tag, useful for new devs
07:22:56 <acoles> another idea might be to tag anything we look at and decide to keep with '2025' or similar, then cull anything > 5 years without '2025'
07:22:59 <mattoliver> Let's wait to see what the timburke__ and co think. But I'll do an initial parse and try and point out (only from a very high level look) at things that we might want to save of anything older then 5years are we'll start there?
07:23:15 <acoles> +1
07:23:45 <mattoliver> kk, let's move on then
07:23:53 <mattoliver> thanks cschwede !
07:24:06 <mattoliver> #topic eventlet removal POC update
07:24:30 <mattoliver> cschwede: any time to play with this yet?
07:24:49 <acoles> some bugs impact more projects than swift but seem very stale e.g. https://bugs.launchpad.net/swift/+bug/1179009 but s
07:25:01 <cschwede> Yes! Currently working on getting some tests passing for my object server POC. Another new deep rabbit hole!
07:25:23 <acoles> oops sorry, we've  moved on
07:27:36 <mattoliver> lol, yup, but we're really thankful for you to at least take the initial leap :P
07:29:00 <mattoliver> lol acoles that one is incomplete everywhere it seems and 12 years old
07:29:24 <mattoliver> Anyway thanks again cschwede
07:29:57 <mattoliver> Speaking of potential PTG topics...
07:30:02 <mattoliver> #topic October vPTG
07:30:17 <mattoliver> Just a reminder there is another PTG coming up in october.
07:30:24 <mattoliver> Oct 27-31
07:30:35 <mattoliver> #link https://ptg.openinfra.org/
07:31:09 <mattoliver> Seeing as we already have a topic, maybe I should go make an etherpad for it so we can start gathering ideas eariler this time :)
07:32:09 <mattoliver> that's just an info one really
07:32:36 <mattoliver> We talked about the isa-l stuff last meeting. So probably don't have to re-hash that.
07:33:10 <mattoliver> Might was well talk ringv2 while I'm neck deep into it. :P
07:33:16 <mattoliver> #ringv2
07:33:21 <mattoliver> #topic ringv2
07:33:47 <mattoliver> I had a good chat to clayg this morning (my time) about the current state of the main patch.
07:34:07 <mattoliver> #link https://review.opendev.org/c/openstack/swift/+/834261
07:35:09 <mattoliver> There are some refactors in how we'll maintain the ring reader/writer classes. But nothing major format wise that needs to change
07:35:39 <mattoliver> So I think we're very close to landing what we have and leave the rest to follow ups
07:35:55 <acoles> exciting
07:37:12 <mattoliver> I have been working deeper in the chain to give us the old primary/history table in the ring, which I think we all want to improve reconstructor and replication smarts.
07:38:08 <mattoliver> Anyway.. we have been running it in prod with no issues, so there are no worries with the current implementation.
07:38:33 <mattoliver> I think that's all I have for today, sorry for not being more organised
07:38:34 <mattoliver> so
07:38:36 <mattoliver> #topic open discussion
07:39:22 <mattoliver> acoles: I might have got nerdsniped on your more deterministic shard finding stuff. And testing some things out.
07:40:25 <mattoliver> got some very basic code that I plan to test on some large containers because I want to make sure it's fast enough in regards to sqlite and hitting indexes etc.
07:40:55 <mattoliver> not convinced either way yet.. and didn't get much of a chance to play too much today. Got distracted with ringv2
07:41:33 <acoles> ok, I did think of some potential flaws but it'd be interesting to see how you go. I don't think I'll find time to explore it much for a while
07:42:26 <mattoliver> yeah, I have some flaws already, but let's see. Initial shard on a container would be the hardest, when we have defined upper and lower boundries I think it might work better.
07:43:26 <mattoliver> Also it tends to leave with more smaller shards, so less efficient in sizing.. but maybe thats ok. So long as it picks right, I don't mind if things need to shrink (once that's working better).
07:44:40 <mattoliver> I've got code for the initial shard being just out of chr bounds to my middle namespace function seems to work quite well. BUT I think it'll come down to IO speed of sqlite to be honest to see how feasible it all is.
07:45:28 <mattoliver> Anyway, that's all I got
07:46:43 <mattoliver> cschwede: I did see you found an account_quite recurrsion error, nice and scary find :P
07:47:04 <mattoliver> #link https://review.opendev.org/c/openstack/swift/+/955866
07:47:22 <mattoliver> And it's already merged thanks to acoles and timburke__
07:47:41 <cschwede> Yes, I was a bit surprised too. This was actually found when writing some new tempest tests by our new QE team member
07:47:46 <mattoliver> Anything else to bring up?
07:47:54 <mattoliver> lol
07:48:53 <acoles> not from me
07:50:10 <mattoliver> Cool, thank I'm going to go make dinner for the fam.
07:50:20 <mattoliver> Thanks for coming and thanks for working on swift
07:50:22 <mattoliver> #endmeeting