kota | a happy new year, and good morning | 01:19 |
---|---|---|
kota | it 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 |
kota | let's wake up tomorrow morning for that. | 01:21 |
*** zaitcev is now known as zaitcev|afk | 18:41 | |
*** zaitcev|afk is now known as zaitcev | 19:55 | |
timburke | almost meeting time! | 20:55 |
kota | good morning | 21:00 |
mattoliver | morning | 21:01 |
timburke | #startmeeting swift | 21:01 |
opendevmeet | Meeting 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 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:01 |
opendevmeet | The meeting name has been set to 'swift' | 21:01 |
timburke | who's here for the swift team meeting? | 21:01 |
mattoliver | o/ | 21:01 |
kota | o/ | 21:02 |
acoles | o/ | 21:03 |
timburke | as usual, the agenda's at | 21:03 |
timburke | #link https://wiki.openstack.org/wiki/Meetings/Swift | 21:03 |
timburke | first up | 21:03 |
timburke | #topic PTGs | 21:03 |
timburke | there are two currently scheduled! | 21:04 |
timburke | first will be another vPTG in late March | 21:04 |
timburke | then there will be another in-person one as part of the summit in mid June | 21:05 |
timburke | summit's in Vancouver; early bird pricing for it ends mid-February | 21:05 |
mattoliver | oh nice, I hope I'll be able to go, Vancouver is great | 21:05 |
timburke | my assumption is that i should for sure get things rolling for the vPTG | 21:06 |
acoles | has it been confirmed/announced that the summit will also host a PTG ?- I saw a survey but no confirmation | 21:06 |
timburke | acoles, my understanding is yes, it's confirmed | 21:07 |
timburke | #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031645.html | 21:07 |
timburke | "So, an in-person PTG will take place Wednesday and Thursday! June 14 -15th." | 21:07 |
kota | will the swift room be located there (Vancouver)? | 21:08 |
timburke | if people are going, i'd love to have a room for us | 21:09 |
kota | nice | 21:09 |
timburke | if having a room makes it easier for people to get approval to go, i'd consider going even on my own dime | 21:10 |
timburke | so my homework for next week: | 21:10 |
timburke | 1. get doodle up for vptg times | 21:11 |
timburke | 2. get etherpad up to collect topics | 21:11 |
timburke | 3. talk to employer about going to vancouver | 21:11 |
timburke | speaking of broader openstack things... | 21:12 |
timburke | #topic next release name | 21:12 |
mattoliver | I'm happy to handle the etherpad again if you want | 21:12 |
timburke | that'd be great, thanks mattoliver | 21:13 |
timburke | the coming release is antelope | 21:13 |
timburke | following that will be bobcat! | 21:13 |
timburke | #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031666.html | 21:13 |
timburke | i think i like the animal naming convention we've landed on for the second trip through the alphabet :-) | 21:14 |
acoles | could the 's' release be .... 'swift' :D | 21:14 |
mattoliver | pretty cool were at the 2nd round through the aplhabet. | 21:15 |
mattoliver | should be ;) | 21:15 |
kota | hope it | 21:15 |
kota | OpenStack Swift version Swift. hmm... :D | 21:15 |
timburke | on to patches! there are a handful that have been kicking around for a bit and i wanted to draw attention to them again | 21:16 |
timburke | #topic cleaning up deprecations | 21:17 |
timburke | #link https://review.opendev.org/c/openstack/swift/+/851100 | 21:17 |
mattoliver | cool, I've been away, so a bunch of patch reminders will be greatly appreciated :) | 21:17 |
timburke | we've had py310 unit tests for a bit now | 21:17 |
timburke | and following https://review.opendev.org/c/openstack/swift/+/869600 we've got py310 func tests in the gate | 21:18 |
mattoliver | oh 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 |
timburke | cleaning 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 |
timburke | thanks mattoliver! | 21:19 |
timburke | it should also put us in a better position to support py311 and beyond | 21:20 |
mattoliver | nice | 21:20 |
timburke | speaking of... | 21:20 |
timburke | #topic testing under py311 | 21:20 |
acoles | I'll look at it again | 21:21 |
timburke | i 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 updating | 21:21 |
timburke | #link https://review.opendev.org/c/openstack/swift/+/866051 | 21:21 |
timburke | iirc, unit tests should pass on python 3.11.1 with that | 21:23 |
mattoliver | ok interesting, seems to be just overloading the execute I guess. I'll put it on my list | 21:26 |
timburke | i'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 that | 21:27 |
mattoliver | is there more info on the bug, I guess I can just run py3.11 without this patch and poke around | 21:28 |
timburke | i 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 |
timburke | yeah, i think you'll probably just want to run unit tests and see how they fail. focus on the db/backend tests | 21:29 |
mattoliver | kk | 21:30 |
timburke | #topic own-shard-range epoch reset | 21:31 |
timburke | #link https://review.opendev.org/c/openstack/swift/+/809969 | 21:31 |
mattoliver | oh this is kinda one of mine, busy day for me :P | 21:32 |
timburke | i think i can be the one promising to review it at least :-) | 21:32 |
timburke | just want to keep it on people's radars -- clayg was +2 on it a while back, but then we let is slip into conflict | 21:33 |
timburke | i need to refresh my memory about what (if any) lingering concerns i had | 21:33 |
mattoliver | kk, I'll take a look at the state of it at least. | 21:33 |
mattoliver | me too | 21:33 |
timburke | #topic nested shard range lookups | 21:34 |
timburke | #link https://review.opendev.org/c/openstack/swift/+/863562 | 21:34 |
mattoliver | I think we wanted to maybe update some log lines to they were better. | 21:34 |
mattoliver | otherwise 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 downstream | 21:34 |
mattoliver | oh this one isn't mine! | 21:35 |
mattoliver | yay | 21:35 |
timburke | heh | 21:35 |
mattoliver | is this the flat shard range tree in memcache? | 21:35 |
timburke | yup | 21:35 |
mattoliver | I guess I should just follow the link and stop being lazy | 21:35 |
timburke | we've been doing some profiling in prod recently, and finding the update target keeps showing up as a hot piece of code | 21:36 |
timburke | some 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 recall | 21:37 |
timburke | that's all i've got | 21:39 |
timburke | #topic open discussion | 21:39 |
timburke | anything else we ought to discuss this week? | 21:39 |
acoles | sorry, I have been too distracted to work more on the nested shard lookups | 21:40 |
mattoliver | nah, 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 |
acoles | if anyone can nudge it forwards from WIP, please do | 21:41 |
mattoliver | or just want to play with tracing, also would be useful | 21:41 |
mattoliver | acoles: I'll try to take a look this week. | 21:41 |
acoles | :thum | 21:41 |
acoles | lol 👍 | 21:42 |
mattoliver | it's kinda important, and probably something I understand somewhat, so I should probably review it :) | 21:42 |
mattoliver | I've been playing with a shrink older than patch | 21:42 |
mattoliver | just so we can make some movement on older shard containers that really need a shrink | 21:43 |
mattoliver | got the basic stuff all plumbed and some initial tests, feel like it's working. | 21:43 |
mattoliver | Just so we can start making progress while we still perfect early-active srhinking | 21:44 |
mattoliver | #link https://review.opendev.org/c/openstack/swift/+/867758 | 21:44 |
timburke | nice -- i'll try to take a look | 21:44 |
mattoliver | needs more tests in code and need to build up more confidence in it. | 21:44 |
mattoliver | ta | 21:45 |
timburke | all right, i think i'll call it for this week | 21:46 |
timburke | thank you all for coming, and thank you for working on swift! | 21:46 |
timburke | #endmeeting | 21:46 |
opendevmeet | Meeting ended Wed Jan 11 21:46:53 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:46 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/swift/2023/swift.2023-01-11-21.01.html | 21:46 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/swift/2023/swift.2023-01-11-21.01.txt | 21:46 |
opendevmeet | Log: https://meetings.opendev.org/meetings/swift/2023/swift.2023-01-11-21.01.log.html | 21:46 |
opendevreview | Tim Burke proposed openstack/swift master: Declare py310 support https://review.opendev.org/c/openstack/swift/+/869874 | 21:56 |
opendevreview | Tim Burke proposed openstack/swift master: tests: Remove references to soft_lock https://review.opendev.org/c/openstack/swift/+/869875 | 22:05 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!