15:01:23 #startmeeting ironic 15:01:23 Meeting started Mon Feb 3 15:01:23 2025 UTC and is due to finish in 60 minutes. The chair is rpittau. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:23 The meeting name has been set to 'ironic' 15:01:28 Hello everyone! 15:01:32 Welcome to our weekly meeting! 15:01:36 The meeting agenda can be found here: 15:01:42 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_February_03.2C_2025 15:01:45 o/ 15:01:50 o/ 15:02:12 o/ 15:02:25 o/ 15:03:08 * cid o/ on mobile 15:03:12 o/ 15:04:05 nice attendance today :) 15:04:11 #topic Announcements/Reminders 15:04:26 Standing reminder to review patches tagged ironic-week-prio and to hashtag any patches ready for review with ironic-week-prio: 15:04:26 #https://tinyurl.com/ironic-weekly-prio-dash 15:04:31 #link https://tinyurl.com/ironic-weekly-prio-dash 15:04:45 lot of patches are on their way to be merged 15:04:56 looks ok 15:05:22 So speaking of patches... I want to ask 15:05:24 we still have 2 specs there that need attention 15:05:36 #link https://review.opendev.org/c/openstack/ironic-specs/+/933620 15:05:45 #link https://review.opendev.org/c/openstack/ironic-specs/+/938526 15:05:51 yes cardoe? 15:06:01 I've got the sushy pyupgrade patch. It's got a bunch of +2's... just wondering how people feel about it. Because my next question is gonna be... how do people feel about just using Python's Black spec. 15:06:06 933620 was revised this morning for two nits, just needs some +2 love :) 15:06:21 TheJulia: cool, I'll have a look after the meetnig 15:06:35 If we just take Black as it comes, we can enable auto-formatting in pre-commit (and in your editors) and not have to worry about style editing / etc and have the tools do it for us. 15:08:00 is it this patch? https://review.opendev.org/c/openstack/sushy/+/934916 15:08:28 Yes. 15:08:30 Merged openstack/ironic master: doc: fix typo and slight wording order for networking https://review.opendev.org/c/openstack/ironic/+/940558 15:08:35 I remember black was not fully pep8 compatible? 15:08:43 black is pep8 compatible. 15:08:45 that's also waht I remember 15:08:48 ok 15:08:51 pep8 is just ambiguous 15:08:55 Oh, they fixed it? Good. 15:09:13 No, no, it was something very explicitly incompatible. I just cannot remember what. 15:09:22 As in: black formatted code would fail a pep8 check. 15:09:27 I have the same memory, but it was some time ago 15:09:35 yeah, they could have changed it 15:10:09 "Black is a PEP 8 compliant opinionated formatter" 15:10:17 yeah, it's a different stance from the one they had back in the days 15:10:18 oh well, I don't have anything particularly against it 15:10:41 o/ 15:10:43 I guess the only question is, have other projects done the same 15:10:43 I personally find some of the things these formatters do annoying, but I'll follow the pack 15:10:49 TheJulia: right 15:10:52 dtantsur: samesies 15:10:55 TheJulia: openstacksdk was at least moving towards it 15:11:27 I don't have an opinion as to what style is used, I am plus one to using auto formatters. And as a bonus, I'm sure that black style format will likely be supported by my IDE 15:11:34 * dtantsur hopes it's easy to setup vim in a way that uses per-repo formatters.. 15:11:54 just a point that sometimes format style between python versions is incompatible 15:12:01 dtantsur: samesies, again :) 15:12:09 :) 15:12:28 rpittau: yeah, we'd need to be able to tell it to use the formatting compatible with the oldest supported version 15:12:33 yep 15:12:43 it was a problem in the past, not sure how much of a problem it is nowadays 15:12:46 do we want to give it some more time to think about it ? 15:12:59 So the reason I ask is that we'd just get freebie formatting without having to fight a style checker. 15:13:35 rpittau: sure thing. I just want to make it easier for everyone to contribute and collaborate and if automation can take a tedious thing off the table then it might be a plus. 15:13:59 Honestly, the pre-commit stuff has done a large amount of progress toward that direction 15:14:26 Cause ruff can fix a lot of issues without people needing to manually fix stuff but it can only do it enabling its formatter, which only supports black right now. 15:14:44 Literally the only 2 config knobs they have is line length and if you want strings to be single quote or double quote. 15:14:55 ... We should get back on track 15:14:58 * dtantsur is horrified by the potential diff 15:15:13 alright, let's give it some more time and we'll go back to it 15:15:15 TheJulia: yes. sorry. 15:15:53 next one is 15:15:54 I'd say let's commit to reviewing the bootable containers and graphical console spec this week? 15:15:54 2025.1 Epoxy Release Schedule 15:16:06 #link https://releases.openstack.org/epoxy/schedule.html 15:16:17 8 weeks to go! 15:16:43 and this week PTL nomination period starts February 5 15:17:16 left the announcement for the next PTG 15:17:16 Flamingo PTG will take place place April 7-11, 2025! 15:17:29 related to the schedule: 15:17:29 new bugfix branches cut is happening this week 15:17:52 anything else to announce/remind ? 15:18:35 KubeCon and the PTG back-to-back, OMG 15:18:40 yep.... 15:19:01 we don't have planned discussion topics today 15:19:05 any open topic? 15:19:34 Please take time to review inspector rules; it's extremely close and I'd like to close that chapter 15:19:54 cid and I can do a demo/group review session if it'd be helpful 15:20:11 JayF: thanks for the heads up, will do! 15:20:20 ++ 15:20:23 Also another small announcement: Next week Satoshi will be joining GR-OSS as an MLH fellow; focusing on a hardware manager to run steps from a container. 15:20:38 Also, later in the week, I could possibly do a bootable containers demo. Thursday or Friday if anyone is interested 15:20:40 JayF: is that in ironic week prio list ? 15:20:58 rpittau: I believe so but not 100% sure; I'll double check 15:21:01 ok 15:21:03 I wrote up https://etherpad.opendev.org/p/ironic-cardoe-inspect-hooks-and-rules and https://gist.github.com/cardoe/82ca7d2a33ae963dbe30f2b43ac13f64 which was my thought around using inspector hooks and rules and I'd love to get cid's feedback. I'm all for a a demo/review session. 15:21:10 (Definitely interested in both demos) 15:21:15 TheJulia: +1 I'm in for a demo of bootable containers too 15:21:26 yep +1 to bootc demo 15:21:35 both sound quite interesting 15:21:56 * dtantsur +1 to both 15:22:14 not sure if I will be around on Friday, so I vote for Thursday :D 15:22:21 Okay, should be possible 15:22:37 How about Thursday for both? assuming cid has availability 15:22:49 * JayF can set it aside overall as a review day 15:22:56 ++ 15:23:03 we can do one this week and the other next week ? 15:23:19 cardoe, I had already taken a look, I will do well to give some feedback. 15:23:23 maybe just not everyone needs to go to both? 15:23:32 I don't wanna ask cid to wait more on inspector rules 15:23:48 sure 15:23:50 JayF: Can ya help me figure out why codespell doesn't seem to run on ironic-specs? https://review.opendev.org/c/openstack/ironic-specs/+/938526 I see rpittau's making review comments for spelling issues. :/ 15:24:06 will look cardoe 15:24:07 I’ll be available on Thursday or Friday +++ 15:24:13 alright, anything else to discuss today? 15:24:26 cardoe: may just need a rebase fwiw 15:24:38 Steve Baker proposed openstack/ironic-specs master: Graphical Console Support https://review.opendev.org/c/openstack/ironic-specs/+/938526 15:24:53 I rebased it. 15:25:13 thank you everyone! 15:25:14 #endmeeting