Wednesday, 2023-02-08

kotagood morning20:55
mattolivermorning21:00
indianwhocodesafternoon21:02
acoleso/21:02
acoleskota: good to have you back in the channel!21:03
kotaacoles: thanks!21:04
timburkesorry to be so late!21:06
timburke#startmeeting swift21:06
opendevmeetMeeting started Wed Feb  8 21:06:34 2023 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:06
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:06
opendevmeetThe meeting name has been set to 'swift'21:06
timburkewho's here for the swift meeting?21:06
kotao/21:06
mattolivero/21:06
indianwhocodeso/21:07
timburkei've been a bit distracted by hardware issues, so i haven't update the agenda21:08
mattolivernps, hows your laptop going?21:08
timburkebut it couldn't hurt to close the loop on the s3api CVE21:08
timburkemattoliver, still dead-ish, but at least now i've got my desktop booting off the old hard drive -- feels much more like my work computer than before (when i was trying to do everything off my personal OS installs)21:10
timburke#topic s3api CVE21:10
opendevreviewASHWIN A NAIR proposed openstack/swift master: proxy-server exception logging shows replication_ip/port  https://review.opendev.org/c/openstack/swift/+/86086621:11
timburkejust to close this out -- a tag is now up (2.28.1) for stable/xena21:11
mattolivercool21:11
timburkesince that's the last non-extended-maintenance branch, no more tags are expected21:11
timburkeall the backports have landed (iirc that was already true last week, but never hurts to reiterate)21:12
mattoliverSo now no excuse, update your clusters peoples :) 21:12
kotagreat21:12
indianwhocodesdone already :wink21:13
mattoliverThanks for getting that all backported timburke 21:13
acoles+121:13
timburke...and that's all there is to it! CVE resolved!21:13
mattoliver\o/21:14
timburke#topic March vPTG21:14
timburkeagain, the etherpad to collect topics is up21:14
timburke#link https://etherpad.opendev.org/p/swift-ptg-bobcat21:14
timburkeand acoles has already added some to it :-)21:14
mattolivernice! I'm still to dump whatever I can think of there... I'll try and get to that before next meeting21:15
indianwhocodessame here, wanna have something more precisefirst21:15
timburkei still need to add ring v2, and maybe a link to an ideas-style doc21:15
timburkenever hurts to add a placeholder, though, and fill in more info as you get there :D21:16
mattoliverIf ring v2 isn't there when I get to adding some topics I'll add it, but you can always update it21:17
timburke👍21:17
indianwhocodesimo, the last etherpad link is useful too, ref: https://etherpad.opendev.org/p/swift-ptg-antelope21:17
mattoliver(as I go through open patches from days old)21:17
mattoliverwhat, you mean those are stil things :P 21:17
timburkei still haven't gotten to the time-slots poll, sorry -- seems likely that we'll settle on similar slots to the last few vPTGs21:18
timburkeoh yeah, if anybody's looking for even *older* etherpads, there's also https://wiki.openstack.org/wiki/Swift/Etherpads21:18
mattoliverI've already added our news one to that21:19
mattoliver*new ones21:19
timburkei noticed someone had done it -- thanks mattoliver!21:20
indianwhocodesThanks Tim, only found the ops doc now, seems very relevant!21:20
timburkethat's all i've got right now -- who's got topics they'd like to bring up?21:20
timburke#topic open discussion21:20
mattoliveryeah, ops feedback is always really useful for thinking about pain points and future work21:21
mattoliverI've been working on some more stuck shard ranges21:21
mattoliverIt's a weird edgecase. but something like21:21
mattoliver#link https://review.opendev.org/c/openstack/swift/+/87285221:21
mattolivershould stop them from getting into failing a sharding_enabled check and get to the audit code to pull in new shard ranges from root.21:22
indianwhocodesbeen working on how i could increase the delay in between when the object is marked for expiry and when the expirer actually issues the delete21:23
indianwhocodesby been working (I mean just started)21:23
mattoliverThe other fix was to add a db_state check in sharding_Enabled, but that would mean an extra directory listing check on every broker the sharder looks at (all of them). So this approach is a noop (well no extra io checks)21:23
mattoliverindianwhocodes: lol, and cool21:24
indianwhocodesAlso if there is a way or an API we can introduce to recover expired data if the data they put under was incorrect21:24
mattoliverwhy would we increase the delay between expiry deletes? is there a bug?21:25
mattoliveroh I think you just answered that question21:25
mattolivercan't you just put new or remove the expiry metadata, so a post?21:25
indianwhocodesya something like that21:26
mattoliveror do you mean post delete21:26
timburkecan have things like a client that wants to extend the expiry, but there's a bunch of failures and they exhaust their retries21:26
indianwhocodes"x-delete-at:" -XPOST21:26
indianwhocodesbut does it really work ? because i tired doing it and a head on the object still worked!21:27
indianwhocodesneeds further investigation21:27
timburkepretty sure indianwhocodes is looking to introduce a recovery option in between the x-delete-at lapsing and the expirer actually laying down a tombstone21:27
indianwhocodesyup21:27
indianwhocodesmany possible scenarios need to explain it better too, lol21:28
mattoliverok, so a POST after the x-delete-at date, the obj server would consider it already deleted21:28
mattolivereven if it isn't, i guess21:28
indianwhocodesya!21:28
mattoliverand it's a recover from that POV. 21:28
mattoliverI get it! 21:28
mattoliverwell, you'd need to know it was in that state, maybe some kind of force. Or allow posts with x-delete-at's through the obj server barrier, the obj server is already looking at the x-delete-at date set on the object.. .21:30
timburkeso down in the diskfile, we check for past-expiry -- and the object-server will 404 any POST to avoid exactly this scenario21:30
mattoliveranyway we can take this offline21:30
timburke#link https://github.com/openstack/swift/blob/2.31.0/swift/obj/diskfile.py#L2736-L275021:30
mattoliveryeah21:30
timburkebut we could plumb in some (likely reseller-admin-gated) header to twiddle _open_expired21:31
mattoliveryeah ok, I look forward to reviewing some options. Ping me if we want to chat more21:32
timburkemattoliver, the sharding patch looks pretty clean -- did we already audit for other sharding-related sysmeta we should also add?21:32
mattoliverGood thinking, let me double check, just in case before we land anything21:33
timburkecleave context meta, maybe?21:35
mattoliverOh only other thing of note, I've been looking into otel metrics again, so going to have aplay with the api some in some downstream tests here at work, and I hope to turn that learning into how we'd go about things in Swift... just a heads up, and probably a topic for the ptg21:35
indianwhocodesexciting!21:35
timburkenice!21:35
timburkeas a heads-up, it's openstack election season again -- i'll try to get my self-nomination up by friday21:36
kotanice, and thanks for continuing it21:37
mattoliverYeah timburke for PTL!21:37
timburkeall right, i'll let y'all go then21:38
timburkethanks for coming, and thank you for working on swift!21:39
timburke#endmeeting21:39
opendevmeetMeeting ended Wed Feb  8 21:39:10 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:39
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2023/swift.2023-02-08-21.06.html21:39
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2023/swift.2023-02-08-21.06.txt21:39
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2023/swift.2023-02-08-21.06.log.html21:39
opendevreviewTim Burke proposed openstack/swift master: Don't clear x-container-sysmeta-sharding on delete_db  https://review.opendev.org/c/openstack/swift/+/87285222:23

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