Wednesday, 2024-03-06

opendevreviewAlistair Coles proposed openstack/swift master: s3api: Support GET/HEAD request with ?partNumber  https://review.opendev.org/c/openstack/swift/+/89458001:32
opendevreviewClay Gerrard proposed openstack/swift master: s3api test for zero byte mpu  https://review.opendev.org/c/openstack/swift/+/91044101:32
opendevreviewMerged openstack/swift stable/2023.1: CI: Remove centos-7 jobs  https://review.opendev.org/c/openstack/swift/+/91091506:04
opendevreviewThomas Goirand proposed openstack/swift master: drive-full-checker  https://review.opendev.org/c/openstack/swift/+/90752308:40
opendevreviewAlistair Coles proposed openstack/swift master: docs: add discussion of content-type metadata  https://review.opendev.org/c/openstack/swift/+/91142511:00
opendevreviewAlistair Coles proposed openstack/swift master: docs: add discussion of content-type metadata  https://review.opendev.org/c/openstack/swift/+/91142511:02
*** clarkb1 is now known as clarkb16:55
opendevreviewAnish Kachinthaya proposed openstack/swift master: add enable open expired in proxy config  https://review.opendev.org/c/openstack/swift/+/90777417:19
opendevreviewAnish Kachinthaya proposed openstack/swift master: add documentation for accessing expired objects  https://review.opendev.org/c/openstack/swift/+/91028617:19
opendevreviewAnish Kachinthaya proposed openstack/swift master: expirer: add per-container grace period  https://review.opendev.org/c/openstack/swift/+/90776217:22
opendevreviewAnish Kachinthaya proposed openstack/swift master: expirer: per account and container grace period  https://review.opendev.org/c/openstack/swift/+/87480618:21
opendevreviewAnish Kachinthaya proposed openstack/swift master: add x-open-expired to access expired objects  https://review.opendev.org/c/openstack/swift/+/87471018:22
kotagood morning20:57
timburke#startmeeting swift21:00
opendevmeetMeeting started Wed Mar  6 21:00:04 2024 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
mattolivero/21:01
timburkeas usual, the agenda's at21:01
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:01
timburkethough i forgot to add the first thing i ought to talk about ;-)21:02
timburke#topic swift release21:02
timburkeit's time to put together a release for caracal!21:02
mattoliverlol21:02
timburkethey need cycle highlights this week, and i can never come up with them unless i'm doing a release21:03
timburkei think we might technically have until next week to make the release, but sooner tends to be better21:03
mattoliverI assume we can use the priority reviews page for patches we want to target to get into the release?21:03
acoleso/ sorry I'm late21:04
timburkeabsolutely!21:04
jianjiano/ me too21:04
mattoliverbut, kk. Try and put my reviewer had on some more this week. 21:04
timburke#link https://wiki.openstack.org/wiki/Swift/PriorityReviews21:04
timburkei need to update it; at least a few of those have merged :D21:04
mattoliverbut thats a good problem to have :) 21:04
timburkeif anyone has other patches to add, please let me know! i should probably kick some of the ones currently listed off until after the release, as they're unlikely to make it (aws-chunked, i'm looking at you)21:06
jianjianfrom patch list, looks like PriorityReviews means patches are almost done and need landing upstream soon21:07
mattolivermaybe we just add a sub heading for non release priority reviews so they don't fall off our radar. 21:07
mattoliverjianjian: yeah, there are so many patches out there. Priority reviews is a way to tell reviewers which are a higher priority for reasons. so when you don't know what to review its a good place to go.21:08
timburkei'll often stuff them into an HTML comment, just to avoid distracting from what matters *this week* ;-)21:08
mattoliveryeah, thats ok too :) 21:08
timburkenext up (and somewhat related)21:08
timburke#topic expirer grace period21:09
timburke#link https://review.opendev.org/c/openstack/swift/+/87480621:09
patch-botpatch 874806 - swift - expirer: per account and container grace period - 12 patch sets21:09
timburke#link https://review.opendev.org/c/openstack/swift/+/87471021:09
patch-botpatch 874710 - swift - add x-open-expired to access expired objects - 30 patch sets21:09
timburkethe follow-ups have been squashed in so we've got just these two patches21:09
mattoliveroh cool! I was about to ask if that had happened!21:09
timburkethere's a pep8 issue on the second, but otherwise i think they're ready for reviews21:10
mattoliverkk!21:10
acolesoh noce, Anish has stacked them in a chain too21:10
timburkebiggest question on my mind (with the release on the horizon) is whether we want to wait for both to be ready before merging the first one21:10
acolesnice*21:10
mattoliverI guess their independent.. but would it be annoying to have a release between the 2? possibly21:12
acolesI think it makes sense, grace period is not much use without being able to access the expired object21:12
mattoliver+121:13
timburkeit may also be somewhat moot -- this week might not be quite enough time21:13
timburkebut i think i *will* add it to the priority reviews page21:13
jianjianmakes sense, +121:13
timburkenext up21:13
timburke#topic aws-chunked21:13
indianwhocodeso/21:13
mattoliverwell lets get some +2/+1s on them, but only land the first when the other is ready.. ie both or nothing?21:14
timburkeπŸ‘21:14
zaitcev"Access expired objects"? Really, guys. Just how far deep the rabbit hole leads?21:14
mattoliverzaitcev: lol, don't ask :P 21:14
timburkei've got the broad strokes of the aws-chunked chain laid out21:15
timburke#link https://review.opendev.org/c/openstack/swift/+/90904921:15
patch-botpatch 909049 - swift - s3api: Improve checksum-mismatch detection - 4 patch sets21:15
timburke#link https://review.opendev.org/c/openstack/swift/+/90980021:15
patch-botpatch 909800 - swift - utils: Add crc32c function - 4 patch sets21:15
timburke#link https://review.opendev.org/c/openstack/swift/+/90980121:16
patch-botpatch 909801 - swift - s3api: Add support for additional checksums - 5 patch sets21:16
timburke#link https://review.opendev.org/c/openstack/swift/+/90980221:16
patch-botpatch 909802 - swift - WIP: s3api: Additional checksums for MPUs - 5 patch sets21:16
timburke#link https://review.opendev.org/c/openstack/swift/+/83675521:16
patch-botpatch 836755 - swift - Add support of Sigv4-streaming - 14 patch sets21:16
mattoliveroh wow, becoming quite a chain!21:16
mattoliveroh and you have a crc32c one now. Nice21:16
indianwhocodesthat sure is a lot!21:17
zaitcevtimburke: re.909049, you see that BaseException.args is absent for me. I added the console log. What version were you at?21:17
zaitcevtimburke: I mean the version of python. Mine was 3.12.21:17
timburkethose middle three might all be able to get squashed into one, but i think they're already reasonably large21:17
mattoliveroh maybe another 3.12 issue maybe?21:18
indianwhocodes^^21:18
zaitcevI suppose I can +2 it as it is and wait until it blows up on py312, and feel smug?21:18
mattoliverlol21:18
timburkezaitcev, .args, or .arg? the snippet you had at https://review.opendev.org/c/openstack/swift/+/909049/4/swift/common/middleware/s3api/s3request.py#873 had .arg, which would be missing21:19
patch-botpatch 909049 - swift - s3api: Improve checksum-mismatch detection - 4 patch sets21:19
zaitcevJust use that str() dammit, what are we even discussing. I'm not inventing a new algorithm for the sharder here.21:19
zaitcevOh21:19
zaitcevHmm.21:19
timburkebut yeah, str() could work fine. i mainly was thinking i'd be explicit about how/where it came from21:20
jianjianon patch "909800: utils: Add crc32c function", is this where the fast isa-l library will be used potentially?21:20
zaitcevNo, no, I was clearly wrong.21:20
timburkejianjian, yup -- isa-l is preferred; if not available, fall back to kernel sockets on py3, or a simple pure-python implementation on py221:22
timburkemy current stumbling block is some seemingly unrelated probe tests failing starting at p 909801 -- i haven't been able to reproduce them locally, and they don't seem to make much sense to me21:23
patch-bothttps://review.opendev.org/c/openstack/swift/+/909801 - swift - s3api: Add support for additional checksums - 5 patch sets21:23
jianjianπŸ‘21:23
timburkethey're all about signals and reload handling, but the patch is only touching things way over in s3api21:24
timburkei'll keep on it, but if anyone has spare cycles to look at it, maybe a fresh set of eyes will see it more quickly21:25
timburke#topic drive-full checker21:25
mattoliveryeah that seems weird, I'll see if it fails for me21:25
timburkei wonder if maybe i need to try under centos 8...21:26
mattoliveroh thats an idea. I do have the centos PR for vsaio floating around. 21:26
timburkei've been reviewing zigo's patch! it's looking fairly good. i probably should have looked at how we (NVIDIA) deal with shutting down rsync earlier, tho :P21:27
mattoliverlet me try and recreate21:27
mattoliverI was hoping I'd trick^Wconvince our SRE to look into it21:27
timburkeoh, boo! i can't even ping csmart directly here ;-)21:28
mattolivercsmart: I can ;) 21:28
csmartπŸ‘‹21:29
mattoliverwow it worked! 21:29
mattoliverπŸ˜†21:29
timburke✨magic✨21:29
timburkeif anyone else wants to take a look, i'm sure zigo would appreciate it21:29
jianjiancsmart, welcome! :-)21:29
mattolivercsmart: I was just says I'm trying to trick SRE into looking at the drive-full patch21:29
timburke#link https://review.opendev.org/c/openstack/swift/+/90752321:30
patch-botpatch 907523 - swift - drive-full-checker - 32 patch sets21:30
csmartSounds good to me!21:30
timburkethanks!21:30
mattolivernice!21:30
acolescsmart: welcome to the party21:30
timburkezaitcev, out of curiosity, how do you guys deal with shutting down rsync when drives start to get full?21:31
timburkemight be good to have more than just the two perspectives on how to deal with it21:31
mattoliver+121:31
zaitcevI don't think we deal with it at all. The field people know that Swift cannot survive a full filesystem.21:32
jianjianbtw, how do your field people define a full FS? what percentage of used?21:33
timburkeinteresting. might be all the more reason to be interested -- there'd be a new cron job you could run to try to defend against it21:33
timburkethe good news is, i trust that csmart wouldn't hold back in criticizing NVIDIA's approach if he disagrees ;-)21:33
zaitcevIn addition, our 2nd day story is fairly weak until OSP 19 or so. It's an upcoming release based on Caracal IIRC, and it uses k8s. Previously, there was no built-in way to monitor or resolve filesystems creeping to full. Just Zabbix and that's it.21:33
zaitcevjianjian: 100% is full. When new files are all created with 0 size.21:34
zaitcevIn legacy Linux we had a root-only reserve, but I suspect rsync defeats it somehow. I see cases where filesystems are totally full.21:35
mattoliversounds like having this checking could be helping redhat too then, thats a win21:36
timburkeall right, next up21:38
timburke#topic part-number support21:38
timburke#link https://review.opendev.org/c/openstack/swift/+/89457021:38
patch-botpatch 894570 - swift - slo: part-number=N query parameter support - 90 patch sets21:38
timburke#link https://review.opendev.org/c/openstack/swift/+/89458021:38
patch-botpatch 894580 - swift - s3api: Support GET/HEAD request with ?partNumber - 99 patch sets21:38
mattoliverwoah 99, just one more indianwhocodes :P 21:39
timburkeindianwhocodes, how's it going? anything we should watch out for as we review?21:39
jianjianzaitcev: wow, you are dealing with 100% full, good to know21:39
mattoliveryeah, ready for a review. Might be nice to get into the release if its ready21:39
jianjianhas to be 99 lol21:39
timburkemattoliver, +121:40
timburkeand that set, i feel pretty good about releasing just the first if that's how far we get21:41
timburkeall right, one last topic i had21:43
timburke#topic drop support for libec<1.421:44
timburke#link https://review.opendev.org/c/openstack/pyeclib/+/83964321:44
patch-botpatch 839643 - pyeclib - Drop support for liberasurecode<1.4.0 - 10 patch sets21:44
timburkeit's been more than seven years since 1.4.0 came out, i think we can feel pretty comfortable doing it21:45
mattoliveryeah, sounds good to me. 21:45
timburkejust wanted to give everyone one last chance to object21:45
timburkei might still wait another month or so before merging, just to avoid it looking like it was supposed to go out in caracal21:46
zaitcevI have no objection. We used to ship with 1.0.9, but that was a very long time ago.21:46
zaitcevBefore the zlib CRC problme, IIRC21:47
timburkeall right, sounds good. i'll self-approve if needed ;-)21:47
timburke#topic open discussion21:47
timburkeanything else we ought to bring up this week?21:47
kotaJust FYI, I'll be at SanJose at GTC week.21:48
mattoliverI have nothing21:48
timburkekota, hurrah! want to try to meet up?21:49
acolestimburke: any progress towards a feature branch for mpu? I have code I want to push somewhere21:49
acolesnobody ever comes to the UK :'(21:49
timburkeacoles, thanks for the nudge! i hadn't done anything with it yet; if you've got code already, i'll try to do that in the next day or two21:49
kotatimburke: maybe, will check free time slot in the week evening. it might be fully busy week.21:49
acolestimburke: thanks, let me know if I can do anything21:50
indianwhocodes@timburke sorry lost connection there21:51
indianwhocodesyes part-num patchg is ready to be merged upstream21:51
timburkeexcellent -- i'll try to take a look this week21:53
indianwhocodeskota will be nice to meet you in-person21:54
kotaindianwhocodes: oh, you'll be at there.21:55
indianwhocodesyes.21:55
mattoliverjianjian:  is in the area too21:56
kotagood to know, let's plan to meet in person21:56
mattoliverWish acoles and I could go to GTC now :( 21:56
timburkei can check in with notmyname, too21:56
kotaawesome21:57
timburkeall right, we're about at time21:58
timburkethank you all for coming, and thank you for working on swift!21:58
timburke#endmeeting21:58
opendevmeetMeeting ended Wed Mar  6 21:58:18 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:58
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2024/swift.2024-03-06-21.00.html21:58
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2024/swift.2024-03-06-21.00.txt21:58
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2024/swift.2024-03-06-21.00.log.html21:58
jianjiankota: will be nice to meet you in person, let me know22:05
opendevreviewThomas Goirand proposed openstack/swift master: drive-full-checker  https://review.opendev.org/c/openstack/swift/+/90752322:52
opendevreviewThomas Goirand proposed openstack/swift master: drive-full-checker  https://review.opendev.org/c/openstack/swift/+/90752323:01

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