Wednesday, 2022-01-05

opendevreviewTim Burke proposed openstack/swift master: Improve some logging when aborting workers  https://review.opendev.org/c/openstack/swift/+/82343900:12
kotaa happy new year, it's working start day of 2022 to me.01:07
opendevreviewTim Burke proposed openstack/swift master: reconstructor: Abort just the changed policies  https://review.opendev.org/c/openstack/swift/+/82347304:42
acoleskota: happy new year09:34
ozzzo_worktimburke__: How does the 2013 Swift upgrade procedure apply to kolla-ansible? When I go into the containers I can see the swift services running, for example in the swift_account_server container, I see swift-account-server processes running, but the swift-init client doesn't see them:17:52
ozzzo_work(swift-account-server)[swift@sde6-swift1 /]$ swift-init account status No account-server running17:52
timburke__ozzzo_work, i'm not real familiar with kolla, but i'd expect you just need to stop the containers that are running the old version and start containers running the new version18:06
timburke__again, it's the proxies where things will get hairiest -- i'm not sure whether kolla would include the healthcheck middleware in its pipelines or not, and even if it *does*, there's the question of whether your load balancer is configured to check it18:15
ozzzo_workty timburke__ : I'll try asking in the kolla channel about that18:34
kotagood morning20:57
timburke__o/20:57
kotatimburke__: o/20:58
*** timburke__ is now known as timburke20:58
timburke#startmeeting swift21:00
opendevmeetMeeting started Wed Jan  5 21:00:16 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
kotahi21:00
timburkeif memory serves, mattoliver is out this week21:01
timburkeclayg and acoles may or may not be around21:01
kotaoic21:02
claygThanks for the ping!21:02
timburkemaybe it'll work with zaitcev too!? :P21:02
timburkeany way, the agenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:02
timburke#topic object updater fairness21:03
timburkewe ran with a bunch of updater improvements over the holidays, and they seem to be working well!21:03
zaitcevokay, good. Although your cloud is private, isn't it? So the holiday is actually not the peak load for you guys, right?21:04
timburketrue -- i'd say we had a lighter-than-usual load over the holiday21:05
timburkebut still, clearing a billion asyncs is impressive! there was another brief spike of 200-300M asyncs, but my understanding was that we could keep our previous tuning just fine and they cleared within a day or two21:06
timburkethe skips in https://review.opendev.org/c/openstack/swift/+/820962 seemed to do a good job of protecting the container servers21:07
timburkeprobably still a good idea to address the deterministic-hashing issue that clayg spotted before we land it, though21:08
timburke#topic memcache refresh21:09
claygCan someone do that for me?  I’m super duper lazy.21:09
timburkeclayg, i'll try to get to it21:09
claygHahaha I didn’t think that would work!21:10
timburkestuff falling out of memcache is still hurting us, so i'm interested in getting something ship-able21:11
timburkei've got two main efforts: the one for shard ranges is simpler/cheaper: https://review.opendev.org/c/openstack/swift/+/73680221:11
timburkethe one for container info isn't *so* bad: https://review.opendev.org/c/openstack/swift/+/82192121:12
timburkebut it's got a dependency on a refactor: https://review.opendev.org/c/openstack/swift/+/82192021:12
zaitcevJust think that maybe now we could sustain the load from Gnocchi.21:13
zaitcevExcept that Gnocchi is fortunately dead because it was killing Ceph just as well as Swift.21:13
zaitcev(sorry that was about the updater; will try to keep up)21:14
timburkeno worries :)21:14
claygtimburke: those are great!  I’ll dig in more. Can’t wait to see those new stats in prod.21:16
timburkezaitcev, fwiw, you'll definitely want sharded containers ahead of worrying too much about those updater improvements -- and if we can get the set of updating shard ranges to hang around in memcache, the updater improvements may become moot21:16
timburkethe get_container_info refactor has an interesting side-effect: middleware can no longer interfere with the info cached and returned. i don't think it will impact anything, but seems worth calling out21:18
timburke(previously, a left-in-the-pipeline middleware could make a get_container_info call with its local "app" and middleware to the right of it could impact results. with the patch, everybody gets a reference to the actually proxy-server app and uses *that*)21:20
claygModdleware can manipulate memcaxge directly. It’s a “gotcha” at worst.21:22
timburke#topic tempurl signature logging21:23
timburke#link https://bugs.launchpad.net/swift/+bug/168579821:23
timburkemattoliver took a stab at an alternate approach in https://review.opendev.org/c/openstack/swift/+/82258521:23
claygIs Matt driving this?21:24
claygI’d love to see it closed.21:24
timburkewhere we'd stick a new key in the request environment and middlewares could update that with whatever headers/params they want to obscure21:25
timburkei got worried that you could bounce out (due to ratelimit, say) before we get to tempurl, and so the env wouldn't get updated21:26
timburke(and it also bugged me that we had to make the same update *for every request*)21:27
timburkeso i tried an approach similar to register_swift_info in https://review.opendev.org/c/openstack/swift/+/82343221:27
claygLet’s wait and see what Matt thinks then. It looks like mostly code refactoring/quality of life - not correctness.21:29
claygShould we do the obvious fix and iterate on the technical investment?  I think Matt pointed out correctly: we’ll want this the next time we have to obscure something.21:29
timburkesounds good. on the whole, i think i like the approach more than the original patch at https://review.opendev.org/c/openstack/swift/+/817476 -- it became trivial to fix up s3api21:30
timburkethat's everything i've got21:31
claygOIC, we’ll https://review.opendev.org/c/openstack/swift/+/823432 looks pretty thin.21:31
timburke#topic open discussion21:31
timburkewhat else should we talk about this week?21:31
claygOh, but that just builds on Matt’s. You two crack me up.21:32
timburkeclayg, yeah, both matt's patch and mine need tests for the new middleware api21:32
claygSo… we’ll keep waiting on closing the CVE 🤣21:33
timburkeit's been 4 years, what's another? :P21:34
timburkeall right, i think i'll call it then21:36
timburkethank you all for coming, and thank you for working on swift!21:36
timburke#endmeeting21:36
opendevmeetMeeting ended Wed Jan  5 21:36:56 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:36
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2022/swift.2022-01-05-21.00.html21:36
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2022/swift.2022-01-05-21.00.txt21:36
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2022/swift.2022-01-05-21.00.log.html21:36
clayg👍21:37
opendevreviewTim Burke proposed openstack/swift master: reconstructor: Abort just the changed policies  https://review.opendev.org/c/openstack/swift/+/82347323:55

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