15:00:35 #startmeeting oslo 15:00:35 Courtesy ping for bnemec, smcginnis, moguimar, johnsom, stephenfin, bcafarel, kgiusti, jungleboyj 15:00:35 #link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting 15:00:36 Meeting started Mon Sep 21 15:00:35 2020 UTC and is due to finish in 60 minutes. The chair is bnemec. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:39 The meeting name has been set to 'oslo' 15:00:44 o/ 15:00:45 o/ 15:00:47 o/ 15:00:53 o/ 15:01:55 o/ 15:03:43 #topic Red flags for/from liaisons 15:03:50 none from Barbican 15:04:21 I don't see Jay yet - none from Cinder that I'm aware of. 15:04:23 Hopefully everything is quiet. I don't think we released anything last week. 15:04:40 Hopefully it will be quiet for a few weeks yet. 15:04:52 :) 15:05:00 Nothing from Octavia 15:05:00 * bnemec crosses fingers 15:06:25 #topic Releases 15:06:32 As I mentioned, not much going on here either. 15:06:50 If all goes well we won't have to release victoria between now and when it ships. 15:07:57 #topic Action items from last meeting 15:08:02 "bnemec send ptg planning email" 15:08:04 Done 15:08:11 "backport https://review.opendev.org/#/c/719876/" 15:08:30 Also done 15:08:41 "Switch oslo.utils to wallaby test template" 15:08:50 I believe smcginnis took care of that. Thanks! 15:09:25 That's it for action items. 15:09:29 #topic PTG/Forum Planning 15:09:35 #link https://etherpad.opendev.org/p/oslo-wallaby-topics 15:10:15 bnemec: We should have that template updated now every time we branch. 15:10:20 Just a reminder that the etherpad is out there. If there's anything we should discuss "face-to-face" then please add it to the list. 15:10:48 smcginnis: Yeah, IIRC you said it didn't happen this time because we didn't get the victoria one merged in time. 15:11:02 Ah, right! 15:11:31 Which was because of a legitimate breakage, so hopefully not a regular occurrence. :-) 15:11:43 (fingers crossed) 15:13:01 On the etherpad there's already a retrospective topic, so please fill that in with any thoughts you have on how the cycle went. 15:13:56 At some point we should probably discuss whether we want to do a project update too. 15:14:03 However, that kind of leads me into the next topic... 15:14:08 #topic PTL election season 15:14:33 Once again, I don't intend to continue as PTL. 15:15:03 Especially as of late, my non-OpenStack responsibilities have been sucking up a lot of time. That situation will probably get worse as time goes on. 15:15:49 I'm still not planning to disappear completely or anything, but it would be good to have someone leading Oslo that is a little more in touch with what's going on. 15:16:34 So, if you're interested in the position, start preparing your nomination email now. :-) 15:18:17 #topic Weekly Wayward Review 15:18:38 #link https://review.opendev.org/#/c/725938/ 15:19:31 hberaud: This is one of yours. I left a few comments that would be nice to address before merging. 15:19:44 bnemec: ack I'll take a look, thanks 15:20:05 Particularly the copyright and option name one. 15:20:14 ack 15:20:33 hberaud: Thanks, I'll WIP it for now. 15:20:42 ok 15:20:53 #link https://review.opendev.org/#/c/746723/ 15:21:40 if some of you could take a look to this one too ^^^ 15:21:41 I added myself to the reviewers 15:21:54 Crud, I never came back to that, did I? 15:22:20 bnemec: yes 15:24:11 Hervé Beraud proposed openstack/oslo.config master: Allow HostAddressOpt to accept undercore - RFC1033 https://review.opendev.org/746723 15:24:11 Okay, I'll take a look at that when we're done here. 15:24:23 thanks 15:25:52 #topic Open discussion 15:26:03 That's it for the agenda. Anything else to discuss this week? 15:26:04 we need tributes to review pre-commit patches 15:26:23 https://review.opendev.org/#/q/topic:oslo-pre-commit+(status:open+OR+status:merged) 15:26:51 my inbox is full of those, and more than half of them are ready to go 15:27:06 thanks for the hard work there hberaud o/ 15:27:29 thanks, my pleasure 15:28:16 I need to re-take a look to some of these 15:28:25 whose in failure 15:28:44 #action merge pre-commit patches 15:28:48 all -2 are gone 15:29:03 so it means that all have been updated to our last proposal of pre-commits 15:29:07 s/whose/those/ 15:29:26 so now we just need to please the gate god 15:29:52 * hberaud start to slaughter a chicken 15:30:14 This is the second time in a week that someone has offered chickens to the ci gods. :-) 15:30:25 xD 15:30:25 poor chickens 15:30:34 Fair warning: I don't think it worked last time. :-P 15:31:01 you broke my dreams 15:31:08 you should sacrifice an empty floppy disk 15:31:49 my laptop even doesn't have CDROM reader 15:32:12 if it doesn't work, a floppy disk that hasn't been backed up yet 15:32:29 lol 15:32:31 lol 15:32:47 Floppies were such a terrible storage medium. 15:33:24 I used to cross my fingers everytime I was copying something out of them 15:33:34 back to the PC 15:33:34 hahaha 15:34:07 I was like 12-ish 15:34:26 :) 15:34:32 last milenium 15:34:46 I have a bit of a question, if open discussion is extra-open now :D. o/ for those who don't know me, I've worked on Ironic for a while and manage it at Verizon Media. 15:35:01 o/ JayF 15:35:05 JayF: o/ 15:35:32 o/ 15:35:54 I was going to file an RFE about getting support for SAN-name checking in the ssl socket wrapper in oslo.service -- primary use case: requiring client certificates with specific SAN names for clients connecting to the Ironic Python Agent (which uses oslo.service wsgi server) 15:36:44 Just curious if that held any general interest for you all, or if anyone is likely to vehemently oppose it. Barring any objections, I'd expect to put up an RFE soon and work on it sometime soon (think weeks, not days). 15:36:48 what happens right now if you try a SAN-name? 15:36:55 seems a good things 15:37:13 SAN name is just a field in a client cert 15:37:25 today; oslo.service supports ensuring that cert is signed by a specific CA 15:37:46 but there's no way to say "signed by the CA, and SAN is 'my-trusted-server.example.com'" 15:38:08 I see 15:38:32 sounds ok 15:38:44 count me in for reviews 15:39:19 +1 15:39:25 Thanks! Like I said, no promise on timeline -- but it's something I wanted to ensure there was general interest in upstream, and will do that code here. All part of a project to enhance TLS server support in IPA. 15:39:49 I will admit I don't entirely understand what you gain from checking that, but I'm no security expert so I wouldn't block it if there's a need. 15:40:14 So let me give you a concrete example: we have a corporate-wide certificate issuing system 15:40:28 currently, we have IPA checking that it has any-valid-cert from that system 15:40:45 instead, we want to limit it to any-valid-cert /that an Ironic Conductor would hold/ 15:40:59 it's essentially imparting some authorization logic on what's primarily used for only authentication today 15:41:35 IPA's API is generally minimally or unauthenticated, so adding this is a helpful security addition; especially for deployers who are not using dedicated provisioning/cleaning networks in Ironic to isolate nodes when the agent is running. 15:41:47 Ah, I think I see. It's the combination of the cert being valid and the name being correct, not one or the other. 15:42:15 You couldn't spoof an invalid SAN because you wouldn't have access to the cert issuing system. 15:42:18 Exactly. 15:42:27 I don't think it can hurt 15:42:44 I suspect the use case for it, with IPA at least, is minimal, but I could see other users of oslo.service seeing a benefit 15:42:51 Yeah, that sounds totally reasonable to add. 15:43:02 and frankly, it's just nicer to contribute stuff like that upstream so I don't have to hold a patched library forever :D 15:43:11 :) 15:43:18 +1000 15:44:12 We don't want people to feel the need to have downstream forks of stuff. 15:44:48 Sounds like we're all in agreement on this. 15:44:53 Anything else before we call it a meeting? 15:45:02 nope 15:46:18 Thanks! I'll be sure to link the relevant story (you all use storyboard, I presume?) and code as it gets written in here for review. And feel free to ping if you ever have an Ironic question :) 15:46:46 JayF: We don't use storyboard. We're still on launchpad. 15:46:56 ack, I can do that 15:47:37 I'd probably advocate for just a wishlist bug, unless there ends up being significant design needed. 15:48:13 that's what my plan was, this should be straightforward enough to not need a spec, at least by ironic standards 15:48:27 Agreed. 15:50:34 Okay, looks like we're done. 15:50:40 Thanks for joining, everyone! 15:50:43 bnemec: Thans 15:50:44 #endmeeting