Wednesday, 2023-01-11

kotaa happy new year, and good morning01:19
kotait looks like there are a few topics in the last meeting, https://meetings.opendev.org/meetings/swift/2023/swift.2023-01-04-21.00.log.html and the next one includes a lot of things.01:20
kotalet's wake up tomorrow morning for that.01:21
*** zaitcev is now known as zaitcev|afk18:41
*** zaitcev|afk is now known as zaitcev19:55
timburkealmost meeting time!20:55
kotagood morning21:00
mattolivermorning21:01
timburke#startmeeting swift21:01
opendevmeetMeeting started Wed Jan 11 21:01:40 2023 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
opendevmeetThe meeting name has been set to 'swift'21:01
timburkewho's here for the swift team meeting?21:01
mattolivero/21:01
kotao/21:02
acoleso/21:03
timburkeas usual, the agenda's at21:03
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:03
timburkefirst up21:03
timburke#topic PTGs21:03
timburkethere are two currently scheduled!21:04
timburkefirst will be another vPTG in late March21:04
timburkethen there will be another in-person one as part of the summit in mid June21:05
timburkesummit's in Vancouver; early bird pricing for it ends mid-February21:05
mattoliveroh nice, I hope I'll be able to go, Vancouver is great21:05
timburkemy assumption is that i should for sure get things rolling for the vPTG21:06
acoleshas it been confirmed/announced that the summit will also host a PTG ?- I saw a survey but no confirmation21:06
timburkeacoles, my understanding is yes, it's confirmed21:07
timburke#link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031645.html21:07
timburke"So, an in-person PTG will take place Wednesday and Thursday! June 14 -15th."21:07
kotawill the swift room be located there (Vancouver)?21:08
timburkeif people are going, i'd love to have a room for us21:09
kotanice21:09
timburkeif having a room makes it easier for people to get approval to go, i'd consider going even on my own dime21:10
timburkeso my homework for next week:21:10
timburke1. get doodle up for vptg times21:11
timburke2. get etherpad up to collect topics21:11
timburke3. talk to employer about going to vancouver21:11
timburkespeaking of broader openstack things...21:12
timburke#topic next release name21:12
mattoliverI'm happy to handle the etherpad again if you want21:12
timburkethat'd be great, thanks mattoliver21:13
timburkethe coming release is antelope21:13
timburkefollowing that will be bobcat!21:13
timburke#link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031666.html21:13
timburkei think i like the animal naming convention we've landed on for the second trip through the alphabet :-)21:14
acolescould the 's' release be .... 'swift' :D21:14
mattoliverpretty cool were at the 2nd round through the aplhabet. 21:15
mattolivershould be ;)21:15
kotahope it21:15
kotaOpenStack Swift version Swift. hmm... :D21:15
timburkeon to patches! there are a handful that have been kicking around for a bit and i wanted to draw attention to them again21:16
timburke#topic cleaning up deprecations21:17
timburke#link https://review.opendev.org/c/openstack/swift/+/85110021:17
mattolivercool, I've been away, so a bunch of patch reminders will be greatly appreciated :) 21:17
timburkewe've had py310 unit tests for a bit now21:17
timburkeand following https://review.opendev.org/c/openstack/swift/+/869600 we've got py310 func tests in the gate21:18
mattoliveroh I remember this one, it was a follow up, to some of the py310 stuff, So I'll take a look at this today.21:18
timburkecleaning up the deprecation warnings seems desirable in part because we've seen warning emissions lead to longer job times (potentially even causing job timeouts)21:19
timburkethanks mattoliver!21:19
timburkeit should also put us in a better position to support py311 and beyond21:20
mattolivernice21:20
timburkespeaking of...21:20
timburke#topic testing under py31121:20
acolesI'll look at it again21:21
timburkei haven't tried to get a gate job for it up yet, but i *have* at least started running unit tests locally -- and it looks like our sqlite greening will need some updating21:21
timburke#link https://review.opendev.org/c/openstack/swift/+/86605121:21
timburkeiirc, unit tests should pass on python 3.11.1 with that21:23
mattoliverok interesting, seems to be just overloading the execute I guess. I'll put it on my list 21:26
timburkei'm a little concerned about what impact that patch could have on earlier versions of python, though -- as best i can tell, the earlier versions would have Connection.execute eventually call self.cursor().execute, and i'm not entirely sure how things will react if *both* Connection.execute and Cursor.execute have been greened like that21:27
mattoliveris there more info on the bug, I guess I can just run py3.11 without this patch and poke around21:28
timburkei suppose i could be a little more defensive and only add the greened Connection.execute on py311+ ... but that doesn't seem great either...21:29
timburkeyeah, i think you'll probably just want to run unit tests and see how they fail. focus on the db/backend tests21:29
mattoliverkk21:30
timburke#topic own-shard-range epoch reset21:31
timburke#link https://review.opendev.org/c/openstack/swift/+/80996921:31
mattoliveroh this is kinda one of mine, busy day for me :P 21:32
timburkei think i can be the one promising to review it at least :-)21:32
timburkejust want to keep it on people's radars -- clayg was +2 on it a while back, but then we let is slip into conflict21:33
timburkei need to refresh my memory about what (if any) lingering concerns i had21:33
mattoliverkk, I'll take a look at the state of it at least. 21:33
mattoliverme too21:33
timburke#topic nested shard range lookups21:34
timburke#link https://review.opendev.org/c/openstack/swift/+/86356221:34
mattoliverI think we wanted to maybe update some log lines to they were better.21:34
mattoliverotherwise this patch that was suppose to lock the problem down seems to have fixed it as we haven't seen the problem again since carrying this downstream21:34
mattoliveroh this one isn't mine! 21:35
mattoliveryay21:35
timburkeheh21:35
mattoliveris this the flat shard range tree in memcache? 21:35
timburkeyup21:35
mattoliverI guess I should just follow the link and stop being lazy21:35
timburkewe've been doing some profiling in prod recently, and finding the update target keeps showing up as a hot piece of code21:36
timburkesome of that comes from deserializing a bunch of json, some of it's instantiating a bunch of ShardRange objects, some of it seems to be instantiating a bunch of Timestamp objects -- this patch ought to help with all of those as i recall21:37
timburkethat's all i've got21:39
timburke#topic open discussion21:39
timburkeanything else we ought to discuss this week?21:39
acolessorry, I have been too distracted to work more on the nested shard lookups21:40
mattolivernah, I'm still ramping back up after holidays. I have rebased the tracing stuff. So if anyone ever gets bored you can go review and fix my code :P 21:41
acolesif anyone can nudge it forwards from WIP, please do21:41
mattoliveror just want to play with tracing, also would be useful21:41
mattoliveracoles: I'll try to take a look this week. 21:41
acoles:thum21:41
acoleslol 👍21:42
mattoliverit's kinda important, and probably something I understand somewhat, so I should probably review it :) 21:42
mattoliverI've been playing with a shrink older than patch21:42
mattoliverjust so we can make some movement on older shard containers that really need a shrink21:43
mattolivergot the basic stuff all plumbed and some initial tests, feel like it's working.21:43
mattoliverJust so we can start making progress while we still perfect early-active srhinking21:44
mattoliver#link https://review.opendev.org/c/openstack/swift/+/86775821:44
timburkenice -- i'll try to take a look21:44
mattoliverneeds more tests in code and need to build up more confidence in it. 21:44
mattoliverta21:45
timburkeall right, i think i'll call it for this week21:46
timburkethank you all for coming, and thank you for working on swift!21:46
timburke#endmeeting21:46
opendevmeetMeeting ended Wed Jan 11 21:46:53 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:46
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2023/swift.2023-01-11-21.01.html21:46
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2023/swift.2023-01-11-21.01.txt21:46
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2023/swift.2023-01-11-21.01.log.html21:46
opendevreviewTim Burke proposed openstack/swift master: Declare py310 support  https://review.opendev.org/c/openstack/swift/+/86987421:56
opendevreviewTim Burke proposed openstack/swift master: tests: Remove references to soft_lock  https://review.opendev.org/c/openstack/swift/+/86987522:05

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