Wednesday, 2022-11-09

opendevreviewJianjian Huo proposed openstack/swift master: Proxy: add metrics related to error limiter.  https://review.opendev.org/c/openstack/swift/+/86344604:39
opendevreviewJianjian Huo proposed openstack/swift master: Proxy: add metrics related to error limiter.  https://review.opendev.org/c/openstack/swift/+/86344605:34
opendevreviewJianjian Huo proposed openstack/swift master: sharding: avoid transient overlaps while auditing.  https://review.opendev.org/c/openstack/swift/+/86408807:14
timburke#startmeeting swift21:00
opendevmeetMeeting started Wed Nov  9 21:00:08 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 team meeting?21:00
mattolivero/21:00
mattoliver(looks like I just made it in time)21:00
timburkesorry to have skipped out on so many meetings -- but i did at least update the agenda today!21:01
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:01
timburkei only have a couple topics, so let's get started21:02
timburke#topic broken func tests21:02
timburkerecently there was a fix for a CPython CVE21:03
timburke#link https://github.com/python/cpython/issues/8738921:03
kotasorry, late a bit21:03
timburkethat's been working its way through backports21:03
timburke#link https://python-security.readthedocs.io/vuln/http-server-redirection.html21:03
mattoliverahh that explains the // patch I saw pop up21:04
timburkethe fix made it so urls like http://swift.example.com//v1/AUTH_test (which used to 400) would get translated to http://swift.example.com/v1/AUTH_test before they get to us21:05
timburkewhich doesn't seem so bad -- but when you have something like domain_remap, it can change the object name for a url like http://container.account.swift.example.com//object21:06
timburkei've written up a bug for them21:07
timburke#link https://github.com/python/cpython/issues/9922021:07
timburkeand a patch for us21:08
timburke#link https://review.opendev.org/c/openstack/swift/+/86344121:08
timburkewe first saw the issue with some non-voting centos9/fips func tests, but since they were non-voting the investigation wasn't really prioritized21:09
timburkerecently, though, it started affecting our rolling upgrade jobs -- and since there's no fixing old proxy code, i had to just make them non-voting for now21:10
timburke#link https://review.opendev.org/c/openstack/swift/+/86392921:10
timburkeif anyone has time to review the fix, that'd be much appreciated! once we have a fix landed, i'll propose backports, too21:11
timburkeany questions or comments?21:12
mattoliverI'll put it on my list. Although I've been really distracted these last few weeks. But will try to get to them in the next day or 2. 21:12
timburkethanks21:12
timburkenot that i really *want* to maintain a new library, but eventually i feel like we'll kind of have to just write our own request parser :-(21:14
timburkespeaking of cpython...21:14
timburke#topic testing under py31021:14
timburkewe're getting closer and closer to testing on py310!21:14
timburkethe pytest is nearly passing21:15
timburke#link https://review.opendev.org/c/openstack/swift/+/85109921:15
timburke"the pytest patch" i mean21:15
mattoliverlol, yeah, it's been harder then expected to just work. 21:16
timburkethe only remaining issue is the requirements-check21:16
mattolivermostly due to requirement versions etc21:16
timburkeso i proposed a patch to add pytest-cov to requirements21:16
timburke#link https://review.opendev.org/c/openstack/requirements/+/863581/21:16
timburkeand fortunately, once those land, it looks like py310 unit tests already pass21:18
timburke#link https://review.opendev.org/c/openstack/swift/+/85094721:18
mattoliveroh nice!21:18
timburkeso we're getting there! next, i might try to switch our func (or even probe) tests to jammy21:19
mattoliveroh good idea. 21:20
timburkethat's all i've got21:20
timburke#topic open discussion21:20
timburkewhat else should we discuss this week?21:20
mattoliverI've been looking at Al's shard ranges from root final patch. Looking good. Think I'm almost happy it wont break things. But will solve some brittleness21:21
mattoliverI also talked to clay briefly about ring v2. And we wants me to revisit the builder into ring stuff.21:22
timburkenice -- am i right to think that acoles's patch you're talking about is https://review.opendev.org/c/openstack/swift/+/852905 ?21:23
mattoliverI said probably needs some disucssions esp with timburke regarding my serialzation classes stuff. So I think I have him onboard with landing the first few patches. 21:23
mattoliveryup that's it21:23
mattoliverthen looping back to get ringbulder classes after21:24
timburkei definitely like the idea of having some movement on that chain :-)21:25
mattoliverthe default will be v1 rings, so if need be we can wait a bit if we want to include more bits into it (before reworking our downstream controller). 21:25
mattoliveryeah +121:25
mattoliverSo I plan, if I'm not pulled into any more fires, to prioritize re-reviewing those first 2 and getting them landed21:26
timburke👍21:26
mattoliverI also reworked the Otel tracing chain to support an Otel Collector. 21:27
mattoliverso not just jaeger21:27
mattoliverAs we have movement on wanting to test that at work. 21:27
timburkenice21:27
mattoliver#link https://review.opendev.org/c/openstack/swift/+/85755921:28
timburkeoh! i also have a patch to improve wsgi server start-up time when you configure a bunch of workers21:28
timburke#link https://review.opendev.org/c/openstack/swift/+/86284321:28
mattoliverAnd I sometimes do wonder if I should convince someone in testing out the sharded pending files patch.21:28
mattoliveroh nice one!21:28
mattolivergreat, I have notices a "reload" can take a while. I assume this would speed that up too?21:29
mattoliverthough that might be caused by finishing old requests.21:29
timburkeyep -- i saw a reload that took ~70s come down to ~15s21:30
mattoliver\o/21:30
mattoliverthat's awesome! 21:30
timburkereload should just wait for the new workers to come up; old workers can continue running21:30
mattoliverThe reload stuff is awesome btw! 21:31
mattoliverwe used it a bunch in a new mcrouter rollout. And it's freakin cool!21:31
timburkenice!21:32
timburkeoh! speaking of old workers -- i added a configurable timeout following a reload to start stopping workers more forcefully21:33
timburke#link https://review.opendev.org/c/openstack/swift/+/78903521:33
timburkethat patch started out just being about quieting some log messages, but i really like having that extra state on hand21:33
mattolivernice21:34
mattoliverI mean maybe they're dealing with a long running request.. but nice to have a hammer21:34
timburkeyeah... 2hr might be a little short for the default, i suppose...21:35
mattoliverwho knows, that's one of those hard things to pick21:37
mattoliverhow long is a peice of string. 21:37
timburkeas much as anything, i just want to give ops a way that they can be *sure* no old workers are running with stale configs21:37
mattoliver2hrs seems like a ok starting point. and we can extend from there21:37
mattoliver+121:38
mattoliverThat's all I have for the moment21:39
timburkeall right, i think i'll call it21:39
timburkethank you for coming, and thank you for working on swift!21:39
timburke#endmeeting21:39
opendevmeetMeeting ended Wed Nov  9 21:39:40 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:39
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2022/swift.2022-11-09-21.00.html21:39
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2022/swift.2022-11-09-21.00.txt21:39
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2022/swift.2022-11-09-21.00.log.html21:39

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