21:01:31 <timburke_> #startmeeting swift
21:01:31 <opendevmeet> Meeting started Wed Mar  9 21:01:31 2022 UTC and is due to finish in 60 minutes.  The chair is timburke_. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:31 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:31 <opendevmeet> The meeting name has been set to 'swift'
21:01:40 <timburke_> who's here for the swift meeting?
21:01:55 <mattoliver> o/
21:02:23 <kota> o/
21:02:26 <acoles> o/
21:03:02 <timburke_> as usual, the agenda's at https://wiki.openstack.org/wiki/Meetings/Swift
21:03:07 <timburke_> #topic PTG
21:03:18 <timburke_> i finally got the etherpad started!
21:03:25 <timburke_> #link https://etherpad.opendev.org/p/swift-ptg-zed
21:04:06 <timburke_> thanks everybody, for responding to the doodle poll -- i'll work on getting time slots booked later today
21:04:51 <timburke_> are there any questions or comments on the PTG? it's less than a month away, now!
21:06:09 <timburke_> all right.
21:06:27 <timburke_> #topic sha1 signatures
21:07:42 <timburke_> afaranha has been trying to get a fips-mode tempest job passing, and some swift tests are currently failing
21:08:23 <timburke_> because the tempest swift tests cover tempurls, and only use sha1 signatures
21:08:55 <timburke_> which aren't secure enough to be used in fips-mode
21:09:09 <timburke_> there's a tempest change to address that: https://review.opendev.org/c/openstack/tempest/+/832771
21:09:36 <timburke_> but i'd also like to deprecate sha1 signatures in tempurl: https://review.opendev.org/c/openstack/swift/+/525771
21:11:04 <timburke_> now that it's got a dependency on the tempest change, that mostly ready to go... except for some odd test failures in the dsvm jobs. i'll look into those more
21:11:29 <timburke_> i know we *also* use sha1 signatures in formpost: https://bugs.launchpad.net/swift/+bug/1794601
21:11:52 <mattoliver> oh
21:12:06 <timburke_> anybody know of any other places we ought to update to use (or at least allow) sha256/sha512 sigs?
21:13:30 <mattoliver> nothing straight off the top of my head
21:14:02 <timburke_> oh! admin /info requests
21:15:36 <mattoliver> container sync realms
21:16:57 <timburke_> good catch
21:17:09 <timburke_> anyone available to champion updating formpost, the info controller, or container sync realms?
21:17:32 <timburke_> or at least writing up the bugs for the latter two?
21:18:23 <mattoliver> I'll have a go
21:18:53 <timburke_> thanks mattoliver!
21:19:48 <timburke_> that's all i've got
21:19:55 <timburke_> #topic open discussion
21:20:04 <timburke_> what else should we talk about this week?
21:21:19 <acoles> does any one know how these s3api doc files are used https://github.com/openstack/swift/tree/master/doc/s3api ?
21:21:36 <acoles> kota: ^^ do you remember?
21:22:16 <acoles> they seem to define schema for s3api requests but I can't see how they are built into docs (if at all)
21:22:19 <kota> at least rnc is used for generating assertion files for response xml
21:22:43 <timburke_> and the conf files in https://github.com/openstack/swift/tree/master/doc/s3api/conf are used when we run the swift-tox-func-s3api-ceph-s3tests-tempauth jobs
21:23:10 <kota> on the conf files, I'm not sure on my memory but it looks like to pass ceph-s3-tests
21:23:24 <timburke_> kota, can you refresh my memory on the difference between those and https://github.com/openstack/swift/tree/master/swift/common/middleware/s3api/schema ?
21:23:25 <kota> oh, timburke_ is sure on that.
21:23:29 <acoles> but we have rng files here for the request validation I think https://github.com/openstack/swift/tree/master/swift/common/middleware/s3api/schema
21:24:09 <kota> i think the rnc is human readable rather than schema xml so at that time, I wanted to keep the original source of the xml
21:24:31 <kota> if we decided to maintain xml directly, we don't have to keep the rnc files
21:25:06 <kota> ah... maybe rng, i meant
21:25:58 <timburke_> do you remember what tool converts between the two? it'd probably be good to confirm that they're actually the definitions...
21:26:37 <timburke_> actually the *same* definitions, i mean
21:27:05 <kota> let me take it as my homework, probably I discussed it on the review (the patch is proposed another one, IIRC). So i can look for that
21:27:21 <acoles> thanks kota !
21:27:23 <timburke_> thanks kota
21:27:27 <kota> np
21:29:24 <mattoliver> I have a few chains lingering (v2 serialisation, global error limitting, ACTIVATING and CLEAVING states to the shading state machine, etc.) but maybe rather then disccuss here and now I'll add them to the PTG etherpad :)
21:30:08 <timburke_> 👍 i keep meaning to keep pushing on the ring v2 stuff
21:30:29 <mattoliver> I know, nps. busy times :)
21:30:39 <acoles> mattoliver: I am (slowly) reloading the ACTIVATING and CLEAVING states stuff
21:30:47 <acoles> into my brain
21:30:58 <mattoliver> lol, great! yeah it's a long reload
21:31:15 <mattoliver> took me a while as well :)
21:31:49 <mattoliver> having full confidence and getting shrinking "done" would be awesome
21:32:43 <timburke_> i think i'll try to cut a 2.29.1 as the final yoga release -- and be sure to call out how it'll be the final py2-supporting release
21:32:57 <mattoliver> \o/
21:33:12 <kota> awesome!
21:33:43 <timburke_> or, final py2-supporting stable branch, anyway
21:36:01 <timburke_> all right, i think i'll call it
21:36:12 <timburke_> thank you all for coming, and thank you for working on swift!
21:36:16 <timburke_> #endmeeting