Wednesday, 2022-08-03

opendevreviewTim Burke proposed openstack/swift master: Stop using unicode literals in docs conf.py  https://review.opendev.org/c/openstack/swift/+/85181800:01
opendevreviewTim Burke proposed openstack/swift master: s3api: Be more consistent about CompleteMultipartUpload logging  https://review.opendev.org/c/openstack/swift/+/85159800:34
opendevreviewMerged openstack/swift master: Stop using unicode literals in docs conf.py  https://review.opendev.org/c/openstack/swift/+/85181801:50
opendevreviewOpenStack Proposal Bot proposed openstack/swift master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/swift/+/85194903:55
opendevreviewMerged openstack/swift master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/swift/+/85194904:36
opendevreviewMatthew Oliver proposed openstack/swift master: Sharding: No stat updates before CLEAVED state  https://review.opendev.org/c/openstack/swift/+/83781107:38
opendevreviewMatthew Oliver proposed openstack/swift master: WIP: sharding: Block moving to CLEAVED if cleaved rows < expected  https://review.opendev.org/c/openstack/swift/+/84397307:42
*** lifeless_ is now known as lifeless13:51
opendevreviewTim Burke proposed openstack/swift master: Add an option to stop locking in our SysLogHandler  https://review.opendev.org/c/openstack/swift/+/84023216:04
opendevreviewTim Burke proposed openstack/swift master: proxy: Add a chance to skip memcache for get_*_info calls  https://review.opendev.org/c/openstack/swift/+/85095418:18
acolestimburke__: sorry, I need to skip today's meeting20:45
timburke__acoles, no worries20:46
*** timburke__ is now known as timburke20:46
timburkeonly just updated the agenda -- there's not a lot i wanted to bring up, anyway20:49
mattoliverMorning21:00
kotamorning21:00
timburke#startmeeting swift21:00
opendevmeetMeeting started Wed Aug  3 21:00:45 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:01
mattolivero/21:02
timburkeas usual, the agenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:02
timburke#topic sha1 deprecations21:02
timburketempurl and formpost patches have now all merged, and i abandoned the client backport21:02
timburkei think the only thing left is to do the same dance for /info admin calls21:03
timburke#link https://review.opendev.org/c/openstack/swift/+/85078721:03
timburkeshould take care of it, just needs review21:03
mattoliverI'll take a look at that today21:04
timburkethanks!21:04
timburke#topic ring v221:04
timburkei finally goaded clayg into reviewing the head of the chain21:05
timburke#link https://review.opendev.org/c/openstack/swift/+/83426121:05
timburkei'll try to keep on him to make sure it's to his liking :-)21:06
mattoliverCool21:06
timburkeand i should also rebase some of the later patches in the chain21:06
claygi mean, if you think my feedback like "swift-ring-builder write_ring --format=v2 should write a v2 ring" is un-reasonable... ;)21:07
mattoliverLol, what kinda cli interface is that 😜 21:07
mattoliverYou hot to do it while standing on your head.. obviously 21:08
claygyeah, I think I still have a bunch of work to do to give a serious review - what are the parts you think need the most testing or validation?  any design choices you're still un-easy about?21:08
timburkeclayg, that was great! mattoliver and i have been so in the weeds on it (and through so many rebases and restarts) that we missed that kind of sniff test21:09
claygi remember I didn't understand some of the scary doc-strings in the internal bits of the ring.io module 🤔21:09
timburkei did my best to wrap it up so no one else would *have* to understand it ;-)21:10
timburkei suppose one thing i haven't spot-checked is deserialization speed -- i remember at some point in investigating the history of ring formats, that was part of what drove us away from pickles21:10
timburke#topic backend rate-limiting21:13
timburkei think we're still bogged down with other things and haven't gotten around to testing the patch in prod21:13
timburkebut wanted to give others a chance to correct me if i'm wrong :-)21:14
claygmaybe we could prioritize that - since we're waiting on new rev of the no-lock-logging patch 21:14
timburkei already pushed up a new one for that -- and i'm going to take a look at making the related eventlet toggle per-fileno instead of global21:15
timburke(long and short of that is we tried https://review.opendev.org/c/openstack/swift/+/840232 on some real hardware, which then started tripping https://github.com/eventlet/eventlet/blob/master/eventlet/hubs/hub.py#L176 since we were no longer suppressing it at https://github.com/openstack/swift/blob/master/swift/common/utils.py#L6196 )21:18
timburkethough i like prioritizing the backend ratelimiting patch, too -- and it seems like we could probably re-use some of the workload generation for testing both patches21:19
timburkeall right -- one more last-minute topic21:20
timburke#topic 2.30.0 release21:21
timburkei'm getting some release notes together! i wanted to do this last week, but didn't get around to it. hopefully by friday there'll be a changelog patch up21:21
timburkethat's all i've got21:21
timburke#topic open discussion21:22
timburkewhat else should we talk about this week?21:22
zaitcevI've got nothing.21:23
clayg@timburke i don't understand why the no-lock-logging setup triggers the warning tho - who's waiting on to read what now?21:23
timburkeclayg, it was complaining about *writes*, not reads. the escape hatch is poorly named21:24
timburkethe trouble was that we had multiple greenthreads trying to write to the logging socket at the same time21:25
timburkewhich is exactly what the patch expected to have happen; the theory is that because of us using UDP, that should be fine21:26
claygreally?  at the *same* time?!  can you really get a /dev/log to raise EAGAIN... maybe...21:27
timburkei was surprised, too -- but i still think it's going to be handled as intended21:28
timburkei'm going to be out camping next week -- would anyone like to chair the meeting, or should we just cancel and meet the following week?21:29
mattoliverDepends if we have anything to talk about. How about we tentively cancel. And I'll chair and let people know if anything changes :) 21:30
timburke👍21:30
mattoliverBut I suspect canceling is fine21:30
mattoliverEnjoy your camping :) 21:30
kotaenjoy21:31
clayg🏕️21:31
timburkeall right, i think i'll call it early then21:31
timburkethank you all for coming, and thank you for working on swift!21:32
timburke#endmeeting21:32
opendevmeetMeeting ended Wed Aug  3 21:32:09 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:32
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2022/swift.2022-08-03-21.00.html21:32
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2022/swift.2022-08-03-21.00.txt21:32
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2022/swift.2022-08-03-21.00.log.html21:32

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