Wednesday, 2022-02-02

opendevreviewMatthew Oliver proposed openstack/swift master: ring: Introduce a V2 format (PTG edition)  https://review.opendev.org/c/openstack/swift/+/82727603:40
opendevreviewMatthew Oliver proposed openstack/swift master: container-updater: no incoming syncs no account update  https://review.opendev.org/c/openstack/swift/+/81183306:08
zaitcevI received a winter storm robocall17:20
zaitcevMy and clayg may lose power tomorrow17:20
zaitcevI don't think I'll have pipe burst. I have way more propane for heating than last year. But work will probably stop.17:21
mattoliver:( stay safe both of you! 20:10
timburke_almost meeting time!20:57
*** timburke_ is now known as timburke20:57
kotasorry, this week is too busy to me so let me absent today, I'll check the meeting log later20:58
timburkeno worries kota! have a good week20:58
kotathx timburke20:58
seongsoochogood morning!20:59
timburke#startmeeting swift21:00
opendevmeetMeeting started Wed Feb  2 21:00:10 2022 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
opendevmeetThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
seongsoochoo/21:00
mattolivero/21:00
acoleso/21:01
timburkeas usual, thhe agenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:02
timburkefirst up21:02
timburke#topic PTG21:02
timburkeregistration is open!21:02
timburke#link https://openinfra-ptg.eventbrite.com/21:02
timburkewith luck, this'll be our last virtual one!21:03
timburkedates are April 4-821:03
mattoliverTime to work on all the last ptg items before the next :p 21:03
timburke...yeah, i should go through those aaction items again...21:04
timburkebut first21:04
timburke#topic 2.29.0 release21:05
timburkei want to get a release out!21:05
timburkechangelog updates are up at21:05
timburke#link https://review.opendev.org/c/openstack/swift/+/826947https://review.opendev.org/c/openstack/swift/+/82694721:05
timburke#undo21:05
opendevmeetRemoving item from minutes: #link https://review.opendev.org/c/openstack/swift/+/826947https://review.opendev.org/c/openstack/swift/+/82694721:05
timburke#link https://review.opendev.org/c/openstack/swift/+/82694721:05
timburkeit's going to be a great release!21:06
mattoliverNice21:06
seongsoocho🎉 21:06
timburkeif you've got any other work in flight, let's try to get it landed; i'll update the changelog as needed21:07
acolestimburke: do we have any outstanding patches we'd like to include before release?21:07
acolesoh, ok :)21:07
timburkethere were a few i was thinking of; i put them on the priority reviews page21:08
timburke#link https://wiki.openstack.org/wiki/Swift/PriorityReviews21:08
mattoliverIs everything on the priority list done? I should just go check21:08
timburkehttps://review.opendev.org/c/openstack/swift/+/822585 - Trim sensitive information in the logs (CVE-2017-8761)21:08
timburkehttps://review.opendev.org/c/openstack/swift/+/813715 - s3api: Fix multipart upload listings21:08
timburkehttps://review.opendev.org/c/openstack/swift/+/826326 - proxy-server: add stats for backend shard_listing requests21:08
timburkethough they're all a *little* hairy21:08
timburkemaybe i'll rearrange my agenda a little ;-)21:09
timburke#topic tempurl signatures in logs21:09
timburkeso i think the solution at https://review.opendev.org/c/openstack/swift/+/822585 is coming along nicely -- though some functions are probably in the wrong place21:10
timburkemattoliver took a stab at pulling them out to a new module in https://review.opendev.org/c/openstack/swift/+/82569421:10
timburkeit creates a decent bit of churn, though, since it's re-homing register_swift_info as well21:11
mattoliverIf people like the move then it can get squashed down into the first. 21:12
timburkei wanted to get people's opinion on that -- should we go ahead and squash that down?21:12
acolesI have a preference to keep the behavioural change and the code relocation in separate patches, to make review easier21:12
mattoliverSo leave them as 2 and as they are? Or the other way around? Move then behaviour change?21:13
mattoliverThe move was also because the new sensitive registers stuff was in the wrong place 21:14
acolesI don't want to create work for anyone but maybe move existing first then make change and add new functions makes most sense???21:14
mattoliverKk, if everyone else agrees I'll swap em :) 21:15
timburkemattoliver, do you want  to do that, or should i?21:16
mattoliverI'll do it21:16
acolesthanks mattoliver 21:16
timburke👍 thanks21:16
timburke#topic multipart upload listings21:17
timburke#link https://review.opendev.org/c/openstack/swift/+/81371521:17
timburkei know we've been running with this in prod for a while, but i'm pretty sure i spotted a bug i'd like to fix before landing21:18
timburkei'll work on re-spinning that this afternoon (tests will probably be the time-consuming part)21:18
timburke#topic proxy-server stats21:19
timburke#link https://review.opendev.org/c/openstack/swift/+/826326 adds some stats for listing shard ranges that mirror stuff we've already got for updating21:19
timburkebut when i put it on the reviews page i think i didn't realize it had some pre-reqs21:20
timburkein particular, https://review.opendev.org/c/openstack/swift/+/824608 - Fix statsd prefix mutation in proxy controllers21:21
timburkethe more i dig into it, the more it seems ripe for a yak-shave21:23
timburkeand i'm a little worried we're currently adding more hair :-/21:23
mattoliverIs the yak changing the metric from what the patch is doing? Because if not maybe we land it to fix then yak-shave follow up? 21:26
timburkeacoles, should i just grin and bear it? can you help me feel better about the logger class hierarchies?21:26
acoleslooking21:27
timburkei think what i *really* want is to pull the statsd client off the logger. start passing around both a statsd client *and* a logger everywhere we currently just have a logger, and have some separate statsd-client wrapper to handle the prefixing of stats21:28
timburkehaving both a PrefixLoggerAdapter and a MetricsPrefixLoggerAdapter feels weird. and i'm a little worried about the thread_locals stuff (though maybe it's unwarranted)21:29
acolesre. the conflation of logging and stasd, I also scratched my head at that but I don't think I can justify spending time on unravelling it21:31
acolesre. the LogAdapter inheritances, at first glance I'm not sure I see the problem - each adapter wraps another so doesn't need to inherit the other's behaviours21:32
acolesthere is an assumption that the wrapped logger is a utils.LogAdapter (i.e. has stasd functions and thread locals)21:33
timburkethe fact that we've got a LogAdapter that's a sibling of our SwiftLogAdapter felt weird to me. pre-existing behavior, but still...21:34
acoleson patchset 5 I got feedback that nudged me towards the separate MetricsPrefixLoggerAdapter21:36
mattoliverPassing around a statsd client too does sound a bunch of work. I kinda like we can statsd and log from the same client, but we do have adapters all over the place.. but I guess that's what the adapter  pattern does, add functionality. 21:39
acolesmaybe utils.LogAdapter could inherit from utils.SwiftLoggerAdapter and lose the stasd delegate stuff?? IDK, I'd need to study with fresh eyes21:39
timburkeok, one other thing that bugged me: the idea of the patch seems to be that `set_statsd_prefix` (or maybe it's the statsd client's `set_prefix`?) is inherently undesireable -- if you're going to set a prefix, it ought to be via a wrapper, it'll be set in __init__, and you shouldn't need to touch it again. but then we still have (and use!) the other interfaces -- we're just more careful about how/when we do it21:39
timburkei kinda want to just get rid of the dangerous interface21:40
acolesI agree, but not in this patch :)21:40
timburkegrin and bear it, got it! 👍21:41
acolesand, note that elsewhere we are considering introducing the same pattern to set proxy-server backend user agent (i.e. mutate attribute after init)21:41
acoleslooking for that patch...21:41
acoleshttps://review.opendev.org/c/openstack/swift/+/81938721:42
mattoliverUntil we can trick(convince) someone to go fix it all ;) 21:42
timburkeall right, enough of me whining about code purity21:42
mattoliverLol21:42
timburke#topic updater fairness21:42
timburkewe've landed a bunch of patches related to this; i think the only outstanding item is the deferral queue21:42
timburke#link https://review.opendev.org/c/openstack/swift/+/82173621:43
acolestimburke: I'm with you on the purity, just feeling more pragmatic :D21:43
mattoliverWe should write it down as a bug/tech debt to fix up, so 1, we remember and 2, others can find it to work on it21:43
timburkeacoles, i just wanted to check in on how the deferal queue is going -- i think i saw some fix ups recently?21:45
timburkeeh, i should just go review the patch ;-)21:46
timburke#topic memcache refreshing21:46
acolesthere was a little churn triggered by your query about the stats - actually, I've not had chance to catch up with you on that. I left a long comment, and fixed a related thing, but otherwise left it as is ... pending you pointing out my folly21:47
acolesI should add some comment in the patch perhaps about how to count things21:47
timburkecool -- i'll be sure to review it21:47
timburkethe shard-range patch has landed now, and the reemoval of pipeline_property is making its way through the gate21:48
timburkei wanted to check if anyone thinkgs they'll have time to look at the account/container info patch: https://review.opendev.org/c/openstack/swift/+/82192121:48
mattoliverI'll put it on my todo 21:52
timburkethanks mattoliver21:52
timburkethat's all i had for this week21:52
timburke#topic open discussion21:52
timburkeanything else we ought to bring up?21:52
mattoliverI pushed up a ptg version of serialisation v2. But gzip seek might not be supported in py221:53
acolesthanks for shepherding everything timburke, there's been lots going on ! 21:53
mattoliverSo I left some questions in the review. 21:53
mattoliverMaybe make it py3 only... anyway, maybe something to bring up next meeting. 21:54
timburkeoh yeah, thanks mattoliver! i'd been meaning to loop back to that21:54
mattoliverNo stress, lots going on21:55
mattoliverWould like to progress that hair the so we can benefit from last primaries ;) 21:55
mattoliver*chain 21:55
acolestimburke said yoga is the end of the road for py2 🥳21:55
mattoliverNo idea why phone change that to hair. 21:56
timburkeexactly! anything to make "emergency rebalance" mode less common will be *great*21:56
mattoliverYeah, it'll make things much simpler.21:56
acolesI'd like to progress my hair ;)21:56
mattoliverLol21:56
timburkeacoles, i know the feeling ;-)21:56
timburkeall right21:57
timburkethank you all for coming, annd thank you for working on swift!21:57
timburke#endmeeting21:57
opendevmeetMeeting ended Wed Feb  2 21:57:22 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:57
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2022/swift.2022-02-02-21.00.html21:57
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2022/swift.2022-02-02-21.00.txt21:57
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2022/swift.2022-02-02-21.00.log.html21:57

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