21:03:34 #startmeeting swift 21:03:34 Meeting started Wed Jun 15 21:03:34 2022 UTC and is due to finish in 60 minutes. The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:03:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:03:34 The meeting name has been set to 'swift' 21:03:43 who's here for the swift meeting? 21:06:10 o/ 21:06:13 hi, i'm late 21:06:41 acoles is on vacation 21:06:44 heh -- i was just about to propose cancelling for lack of interest/new topics ;-) 21:07:21 main thing i wanted to bring up was around the sha1 deprecation stuff 21:07:28 #topic sha1 deprecation 21:07:38 Well a short one is OK too :) 21:07:56 i'd appreciate some reviews on https://review.opendev.org/c/openstack/python-swiftclient/+/845157 to add support for sha256/sha512 tempurls to the client 21:07:57 +1 21:09:09 mattoliver, i pushed up some revisions to https://review.opendev.org/c/openstack/swift/+/838434 to add sha256/sha512 support server-side for formpost -- if it looks good to you, let's go ahead and merge it 21:09:53 and i took acoles's idea to make the tempurl deprecation a little softer and wrote up https://review.opendev.org/c/openstack/swift/+/845862 21:10:36 basically, the idea is to keep sha1 support by default for now, but warn about it when clients use it 21:10:58 kk, thanks, I'll loop back to it todat 21:11:01 *today 21:11:24 thanks! 21:11:39 I did take a quick look the other day and was a great refactor and change, so thanks! 21:11:40 to make the tempurl warnings not *so* overwhelming, just log the first time a client uses it per-worker 21:12:13 though that could still get to be a lot, depending on how often you reload your proxies 21:12:47 sure, but better, and if people don't want the noise, stop using sha1 :) 21:13:26 true 21:13:40 you can disable the warning on client usage by explicitly configuring sha1 -- but it'll go back to warning you during process start-up instead 21:15:49 i'm still torn about whether it's a good path forward -- we (nvidia) have already had our firedrill about it, so it doesn't buy us anything -- and it puts the eventual dropping of sha1 support that much further off 21:17:15 but if we want to slow down the deprecation, now's the time to do it -- and i'd like to tag a release sometime in the next month or so, so... what do we think? should i pursue it further and write up some tests around it? 21:17:28 at least it is a path, and lack of support in the client probably means its a good idea 21:18:46 true -- which reminds me that i ought to go review https://review.opendev.org/c/openstack/python-swiftclient/+/833954 to move formpost to the client ;-) 21:21:49 all right, i'll get some tests together 21:21:57 oh yeah, I should confirm I have base64 support there 21:22:51 we could probably rebase it off the tempurl patch and share some code 21:23:05 i figured i'd probably do that as part of my review ;-) 21:23:43 true. whoever gets to it first ;) 21:25:08 all right 21:25:14 #topic backend ratelimiting 21:25:30 mattoliver, did i see you reworked some patches around this? 21:26:27 Well it was refactoring the error_limiting code, mostly rebasing it. 21:27:52 seperating the error_limiting into a class where we can configure the count and period was something that has come up again, I think related 21:28:12 and I already had a patch for that. 21:28:44 nice 21:29:43 all right -- i think that's all i've got 21:29:52 #topic open discussion 21:30:02 anything else we ought to bring up this week? 21:30:28 nope 21:30:52 all right -- i'll let you guys get breakfast then ;-) 21:31:00 thank you for coming, and thank you for working on swift! 21:31:04 #endmeeting