21:01:34 #startmeeting swift 21:01:34 Meeting started Wed Jul 28 21:01:34 2021 UTC and is due to finish in 60 minutes. The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:34 The meeting name has been set to 'swift' 21:01:44 sorry i'm a little late to get started 21:01:49 who's here for the swift meeting? 21:01:53 timburke: no worries 21:01:56 o/ 21:02:03 o/ 21:03:01 o/ 21:03:14 o7 21:03:48 #topic 2.28.0 release 21:04:03 as kota just pointed out, we've got a new release! 21:04:18 \o/ 21:04:27 there's a lot of great stuff in there; a ton of bug fixes 21:04:49 best swift yet :-) 21:06:12 i should probably poke tdasilva about getting a versioned tag at https://hub.docker.com/r/openstackswift/saio/tags 🤔 21:06:20 i think it's still a manual process atm 21:08:00 Yeah, would be cool to add it to the release pipeline 21:08:36 fwiw, we should be planning on a final xena release around mid-september, so if there's anything you'd really like to get into this cycle, that's the target 21:09:56 Kk 21:09:57 mattoliver, agreed -- i ought to get more familiar with the various zuul pipelines... 21:10:16 #topic PTG 21:10:49 this is actually why i was running behind -- i've at least done half of the team signup, but i still need to reserve some meeting times 21:11:03 o/ 21:11:07 turns out, we're all over the place and scheduling is hard! 21:11:50 Lol, yup 21:11:53 it used to be easier because we'd like all fly on airplanes to get in the same timezone so we could collaborate more effectively - now we just sit at home... alone... forever... 21:12:36 maybe in 2030 after the vaccine for the zeta variant!!! 🤞 21:12:52 :( 21:12:53 clayg and mattoliver if you don't mind, respond on https://doodle.com/poll/a5fx9zy7s3bu72da -- i'll do what i can 21:13:07 😝 21:13:12 Oh yeah of course, sorry will do! 21:13:19 no worries! 21:13:54 so far it looks like the standard meeting time is the one most likely to get us everyone at once, but it's only an hour window each day :-/ 21:14:04 it's hard to get a good sized block 21:14:42 and one more reminder about the call for topics at 21:14:44 #link https://etherpad.opendev.org/p/swift-ptg-yoga 21:15:57 that's all i've got 21:16:34 (sorry, i've been rather distracted lately, so it's been harder than usual for me to keep tabs on things. but the good news is that i've now got a new house!) 21:16:40 #topic open discussion 21:16:51 what else should we bring up this week? 21:17:45 zaitcev, sorry, i haven't gotten around to rebasing https://review.opendev.org/c/openstack/swift/+/787656 (dark-data: Work with sharded containers) yet 21:17:56 Yeah, moving house is distracting, I know, me too! 21:19:16 timburke: I thought I was going to rebase it. I was busy with the S-RBAC unfortunatley. 21:19:31 I was chatting to someone re reconstructor and knowing when I cycle was up on the mailing list, which made me blow the dust off https://review.opendev.org/c/openstack/swift/+/541141 21:20:13 zaitcev, no worries! i saw https://review.opendev.org/c/openstack/swift/+/802138 come across, though i haven't looked at it yet -- i'm guessing that's related? 21:21:15 timburke: Yes, that's it. 21:21:20 mattoliver, i also saw that you've been doing a lot of stuff with request tracing -- how are you feeling about that so far? do we have a sense of how much overhead the changes might have when you *aren't* actively tracing a request? i think there's like an extra function call per middleware, is that right? 21:21:26 And have planned a meeting with nvidias sre guys today to see if sres think my req tracing idea (and patchset) is useful for just crazy. 21:22:43 👍 always a good group to get in touch with. which reminds me, i ought to set up an ops feedback session again and be sure to invite them 21:23:06 Yes and no, there is a conditional. And short circuits to no tracing. But there are calls (if we want extra info) which should basically be a conditional noop if not tracing. 21:23:24 So I think minimal.. but really need to test. 21:24:06 Started out as micro benchmarking timings between middleware. But feels like it could be more useful. 21:25:38 Like I dump the error limited nodes from the proxy it visits which would be nice to know, otherwise the only way to find out is via debug level logging. 21:27:26 Maybe a good topic for ptg ;) 21:28:11 💡 21:28:21 nice -- yeah, it seems like the sort of thing where we might be able to come up with some interesting visualizations if we had the underlying data more readily available 21:28:31 looks like the other thread of work that's seen some iteration this week has been shard-aware reconciler, which had us dusting off policy migration 21:31:18 BTW 21:31:36 The URL for PTG is 404 http://ptg.openstack.org/ptg.html 21:32:00 redirects to https://www.mousehuntgame.com/errors/40x.html 21:32:19 I sense a security issue. I saw these redirects before when someone cracked my blog. 21:32:22 So 21:32:28 maybe my Firefox is cracked 21:32:34 or worse, my laptop OS is 21:32:43 or hopefully it's just the Etherpad 21:33:26 huh. i'm getting a connection timeout. strange 21:34:00 I'm looking at https://etherpad.opendev.org/p/swift-ptg-yoga with a Web Inspector in Firefox 21:34:14 Mine went to the same thing on my phone. 21:34:59 Oh when I went to ptg.os.org/ptg.html 21:35:33 OK. So at least my laptop is not compromised. Whew. 21:35:33 well, i'll take the link off the etherpad until it's resolved 21:35:53 all right -- anything else to bring up? 21:36:01 Well 21:36:05 MinIO 21:36:15 Looks very amusing. 21:37:06 I started with their strange marketing, like this: https://zaitcev.livejournal.com/262821.html 21:37:09 i've still not had a chance to dig into it much. i seem to remember it seeming... a bit rigid 21:37:47 Yeah. 21:38:11 That seems like an amazingly adept one-word description. 21:38:32 I wish we could call Swift "elegant" or something. 21:40:45 all right, i'm gonna call it 21:40:56 thank you all for coming, and thank you for working on swift! 21:40:59 #endmeeting