Wednesday, 2025-07-09

opendevreviewOpenStack Proposal Bot proposed openstack/swift master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/swift/+/95441903:48
opendevreviewLhoussain AIT ASSOU proposed openstack/liberasurecode master: :backend isa_l_rs_vand: generate gen_matrix for libisal When parity is higher than 5, the decoding matrix is not invertible for some combinations of missing data and parity.  https://review.opendev.org/c/openstack/liberasurecode/+/95428509:51
opendevreviewMerged openstack/swift master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/swift/+/95441917:16
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: WIP: use version history to detect orphans  https://review.opendev.org/c/openstack/swift/+/95068917:49
*** vhari_ is now known as vhari19:03
opendevreviewShreeya Deshpande proposed openstack/swift master: proxy-logging: Add real-time transfer bytes counters  https://review.opendev.org/c/openstack/swift/+/93091819:40
opendevreviewShreeya Deshpande proposed openstack/swift master: Provide some s3 helper methods for other middlewares to use.  https://review.opendev.org/c/openstack/swift/+/94079119:40
opendevreviewShreeya Deshpande proposed openstack/swift master: proxy-logging: Add real-time transfer bytes counters  https://review.opendev.org/c/openstack/swift/+/93091819:42
opendevreviewShreeya Deshpande proposed openstack/swift master: Add labeled metrics to s3api  https://review.opendev.org/c/openstack/swift/+/93948119:52
*** timburke__ is now known as timburke20:04
timburke#startmeeting swift21:02
opendevmeetMeeting started Wed Jul  9 21:02:56 2025 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
opendevmeetThe meeting name has been set to 'swift'21:02
timburkewho's here for the swift meeting?21:03
zaitcevo/21:03
zaitcevLooks like it's going to be a short one.21:03
timburkesorry for missing the last couple meetings i was supposed to host21:04
timburkebut i'm here this week! may as well get into it21:04
timburkeas usual, the agenda's at21:04
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:04
timburkefirst up21:04
timburke#topic DCO replaces CLA21:04
timburkei know mattoliver brought this up last week, but in case anyone missed it: we've moved from having everyone sign a contributor license agreement before they can upload patches to requiring that every patch uploaded includes a sign-off for the developer certificate of origin21:06
timburkethis was brought up on the mailing list back in may21:07
timburke#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/A7S24NMKOQZFXRAAEEYQX23S6UF4WML2/21:07
timburkebut only fairly recently started having the gerrit hooks enforce the sign-off21:08
timburke#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/KGEKDH3AKRM3CKQW7SEVVVQFV2X6OCF6/21:08
timburkefor more information (including the text of the dco), see21:08
timburke#link https://docs.openstack.org/contributors/common/dco.html21:08
timburketl;dr: expect to need to add `-s` to your commits and rebases21:10
timburkenext up21:10
timburke#topic October vPTG21:10
timburkedates are set for 10/27-10/3121:10
timburkeregister at21:11
timburke#link https://ptg.openinfra.org/21:11
zaitcevDunno if I can but I'll take a look.21:11
timburkei'll work on getting an etherpad and schedule worked out, but we've got some time still21:11
timburkei'm pretty sure i already responded to express the swift team's interest in participating21:13
timburkeone more fyi21:14
timburke#topic 2026.1 codename21:14
timburkeit's gazpacho21:14
timburke#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/QVZK5PFN233WNDX764B2NZ4W65U27FF4/21:14
timburke(if i'd noticed the poll in time, i would've voted for gazelle, but that's me)21:15
timburkenext up21:15
timburke#topic new liberasurecode backend21:15
timburkethis one came out of left-field for me this week21:16
timburkesomeone apparently has an interest in using proper vandermonde encoding/decoding, such that we avoid the nparity<=4 requirement21:17
timburke#link https://review.opendev.org/c/openstack/liberasurecode/+/95428521:17
timburkeas best i can tell, we ought to be able to do something very similar to what we did for the rs_vand/rs_cauchy split -- just change the way we generate the EC encoding matrix, then let isa-l do its normal thing from there21:18
timburkenote that the patch is not in shape to merge yet -- currently it replaces the encoding matrix entirely (for both isa_l_rs_vand *and* isa_l_rs_cauchy!), with no option to use the old one21:20
zaitcevBut isn't it a perfect superset? So it's only a question of safety, right?21:21
timburke...which would mean that no currently-existing parity fragments would be good anymore21:22
zaitcevOh21:22
timburkebut i think i could see a way to get it to something useful -- we just need to define it as a whole new backend (again, rather like we did when we introduced rs_cauchy)21:23
timburkefwiw, the matrix generation seems to match what other projects do21:23
timburkefor example, https://github.com/tahoe-lafs/zfec/blob/zfec-1.6.0.0/zfec/fec.c#L430-L47921:23
timburkealso, the description at https://en.wikipedia.org/wiki/Reed%E2%80%93Solomon_error_correction#Systematic_encoding_procedure:_The_message_as_an_initial_sequence_of_values21:24
timburkei think the biggest question i've got left is what we'd want to call the thing -- once i've got that, i might go offer some follow-up patch to get things more in the shape i'd expect21:26
timburkeisa_l_rs_vand_inv, maybe? isa_l_rs_vand2?21:26
zaitcevDoes not matter to me tbh.21:28
timburkealright, last item21:29
timburke#topic dsvm devstack gate breakage21:29
timburkemore of an fyi since it's resolved now, but still21:30
timburkewhile i was trying to get better s3api func test coverage, i had us start running the s3 cross-compat tests as part of the dsvm job21:31
timburke#link https://github.com/openstack/swift/commit/38ad3a421:31
timburkeunfortunately, that broke devstack's gate21:31
timburke(i think at some point i knew our job was included for their repo, but i'd forgotten)21:32
timburkethe reason was somewhat sneaky, or maybe it's just that i'm not super-familiar with zuul and cross-project testing21:33
timburketo make our dvsm job test both keystone and tempauth, we configure two test.conf files -- /etc/swift/test.conf (for keystone users) and we update test/sample.conf (for tempauth)21:34
timburkebut the way our roles found the tempauth file was {{ ansible_env.HOME }}/{{ zuul.project.src_dir }}/test/sample.conf21:35
zaitcevStill not seeing why that was bad.21:36
zaitcevI see you added ../swift21:36
timburkewhich works great for our repo, but means we add test/sample.conf files to other repos when they include our job21:36
timburke...which then gets ignored, because the test-running job just says "test/sample.conf" while CWD is the swift repo dir21:37
timburkebut yeah, the solution was to bump back out of the project repo and make sure we go updating the file in the swift repo (ie, the one that will be used when running tests)21:38
timburke#link https://github.com/openstack/swift/commit/e9da48da21:38
jianjianthanks Tim for enabling s3 cross-compat tests as part of the dsvm job21:38
jianjianI wonder if we can also run those tests twice, once for us, once against real s3 😉21:39
jianjianin case some future s3 updates break our cross-compat tests silently 21:40
timburkejianjian, potentially -- i know we can get secrets into .zuul.yaml (we use it to publish to dockerhub), but i forget how. alternatively, we could set up some 3rd party CI for it21:40
timburkeanyway, that's all i've got21:41
timburke#topic open discussion21:41
timburkeanything else we should bring up?21:41
jianjiannot from me21:43
timburkethe cross-compat trouble reminds me i should push a little more on some other improvements there -- we don't actually run with keystone users when we think we do :-/21:43
timburke#link https://review.opendev.org/c/openstack/swift/+/95133921:43
timburkeand i still want to make sure that we call `check_signature` when caching secrets (so keystone users can rely on aws-chunked transfers working)21:44
timburke#link https://review.opendev.org/c/openstack/swift/+/94967121:44
timburkeas a heads-up, i'll be on vacation all next week -- though mattoliver will be running the 0700 meeting anyway21:46
jianjianI think 951339 needs review, I will try to understand those yaml files21:46
jianjiansummer is here, have fun!21:47
timburkethanks -- let me know if you'd like a primer on (my imperfect understanding of) how the zuul stuff works21:48
timburkeall right, i'll call it for this week21:49
timburkethank you all for coming, and thank you for working on swift!21:49
timburke#endmeeting21:49
opendevmeetMeeting ended Wed Jul  9 21:49:40 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:49
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2025/swift.2025-07-09-21.02.html21:49
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2025/swift.2025-07-09-21.02.txt21:49
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2025/swift.2025-07-09-21.02.log.html21:49
timburkeoh, jianjian! i forgot to mention that the test-users change depends on https://review.opendev.org/c/openstack/swift/+/951352 which enables secret caching by default. i've become increasingly convinced that if you're deploying s3api with keystone users, *not* having secret caching enabled basically leaves you with a broken/terrible cluster21:55
timburkethanks for https://github.com/openstack/swift/commit/b0aea936, sorrison!21:56
opendevreviewTim Burke proposed openstack/liberasurecode master: Add new backend for new encoding matrix  https://review.opendev.org/c/openstack/liberasurecode/+/95454923:45

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