21:00:39 <timburke> #startmeeting swift
21:00:39 <opendevmeet> Meeting started Wed Sep 29 21:00:39 2021 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:39 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:39 <opendevmeet> The meeting name has been set to 'swift'
21:00:46 <timburke> who's here for the swift meeting?
21:01:39 <kota> hi
21:01:50 <mattoliver> o/
21:02:02 <acoles> o/
21:02:24 <timburke> as usual, the agenda's at https://wiki.openstack.org/wiki/Meetings/Swift
21:02:58 <timburke> #topic gate
21:03:31 <timburke> the tempest and grenade failures should be resolved now! i seem to recall clayg and acoles noticing them being a problem
21:03:42 <timburke> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-September/025128.html
21:04:11 <timburke> #topic xena release
21:04:20 <timburke> the stable branch has been cut!
21:04:40 <clayg> Woot!
21:04:46 <mattoliver> Nice
21:05:25 <timburke> i'd actually kinda meant to do another release before xena so we wouldn't be shipping code from June, but oh well -- i dropped the ball a bit
21:06:16 <timburke> not the end of the world, of course. 2.28.0 is a great release ;-)
21:06:32 <timburke> #topic ring v2
21:07:04 <timburke> thanks for the review mattoliver! i haven't had a chance to look through them much, but i'll plan on responding this week
21:07:34 <mattoliver> Nps, still have more of the chain to work though, will do that today.
21:08:30 <timburke> #topic root epoch reset
21:09:39 <timburke> it looked like there was a good bit of progress on this, kinda split between...
21:09:44 <timburke> #link https://review.opendev.org/c/openstack/swift/+/807824
21:09:50 <timburke> #link https://review.opendev.org/c/openstack/swift/+/809969
21:10:58 <mattoliver> Yeah, so the situation is we have had an epoch reset in the cluster a few times
21:11:29 <mattoliver> But still can't reproduce without physically breaking it (in a probe test)
21:12:20 <mattoliver> But we know once and own_shard_range is shared it should ALWAYS have an epoch set
21:13:36 <mattoliver> The first patch is one that stops merging a remote own_shard_range with a local if local has an epoch and remote doesn't down in the container broker.
21:14:14 <mattoliver> This "should" fix it.. but hard to know because we still don't know the cause
21:15:25 <mattoliver> The second is one that doesn't do down in the guts of shard merging only on replication. And will block a node without an epoch from replicating to its neighbours
21:15:59 <mattoliver> Not as universal as the first, but will give us better logging and a pause to help diagnose the bug.
21:16:49 <mattoliver> We're thinking about rolling out the second temporarily to catch when/if it happens again so we can track the bugger down.
21:17:00 <timburke> sounds good
21:17:30 <timburke> #topic staticweb + tempurl-with-prefix
21:18:17 <timburke> so this was an idea i had while thinking about how to share something out of my home cluster
21:19:04 <timburke> i wanted to share a set of files, but not require that i send a separate tempurl for each or provide swift creds
21:19:31 <timburke> so i came up with
21:19:33 <timburke> #link https://review.opendev.org/c/openstack/swift/+/810754
21:21:11 <timburke> the core of the change is in staticweb -- basically, do staticweb listings when auth'ed via tempurl and carry the prefix-based tempurl to the links that we build
21:22:45 <timburke> i wanted to get people's thoughts on it, and see how we feel about the increase in privileges (prefix-based tempurl can now do listings -- but only if staticweb is enabled and only within the prefix)
21:23:15 <mattoliver> Oh that's kinda cool. You can share as a list of links and not make the container public readable.
21:23:37 <mattoliver> Need to have a better look and play first though
21:23:51 <timburke> yup :-)
21:24:24 <timburke> and it needs tests -- skimped there, figuring i ought to get a bit more buy-in first
21:25:26 <timburke> anyway, just wanted to raise a bit of attention for it
21:25:32 <timburke> that's all i've got
21:25:41 <timburke> #topic open discussion
21:25:44 <timburke> what else should we bring up this week?
21:27:54 <mattoliver> Ptg not far away, get topics in, or just plan to come and hang with us virtually for a bit
21:28:27 <kota> is the schedule fixed?
21:29:18 <timburke> i believe so, but will double check for next week
21:29:34 <kota> okay
21:32:34 <timburke> all right, i think i'll call it
21:32:45 <timburke> thank you all for coming, and thank you for working on swift!
21:32:48 <timburke> #endmeeting