15:00:00 #startmeeting ironic 15:00:00 Meeting started Mon Sep 19 15:00:00 2022 UTC and is due to finish in 60 minutes. The chair is iurygregory. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:00 The meeting name has been set to 'ironic' 15:00:05 o/ 15:00:13 o/ 15:00:23 hello ironicers, welcome to our weekly meeting 15:00:42 o/ 15:01:08 o/ 15:01:20 o/ 15:01:33 o/ 15:01:35 you can find our agenda in the wiki page 15:01:40 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 15:02:00 #topic Announcements / Reminder 15:02:15 we have the result for the doodle \o/ 15:02:35 #info Check PTG Topics - doodle result Tomorrow Sep 20 at 16 UTC 15:03:08 I will send the information in the ML today (I can also send a calendar invite for those who need one =) ) 15:04:00 please ping me here or send me a dm if you want the calendar invite 15:04:14 #info Zed release by EOW 15:04:37 @lecris[m]: https://www.supermicro.com/products/archive/motherboard/x9drt-hf <-- doublecheck that is right 15:05:10 we will focus on Ironic, ironic-python-agent, inspector and bifrost this week 15:05:22 Maybe, saw 3.3 is available 15:06:08 iurygregory: if you need any help doing release work, lmk -- I should learn some of this 15:06:34 JayF, sure =) 15:07:00 does anyone have something that would like to add to our Announcements / Reminder ? 15:08:10 has everyone voted? 15:08:18 at least, elegeble for voting for PTL/TC? 15:09:12 Voting closes in 7 hours, give or take, yeah? 15:09:22 yup 15:09:28 great question, I heard a few people voted, other had problems to vote because they didn't have OSF membership etc 15:10:01 * TheJulia raises an eyebrow 15:10:15 we can circle back to that I guess 15:10:21 I thought it would close earlier lol 15:10:28 yeah 15:11:48 #topic Review subteam status reports 15:12:33 we probably don't have a lot, but would to check the SQLAlchemy 2.0 15:12:39 #link https://etherpad.opendev.org/p/IronicWhiteBoard 15:13:00 I do not know how to run the bug subteam report; it's been ages since it's been properly updated. I did start going through the backlog. ~20 tickets triaged; 5 marked as merged/triaged, 9 closed invalid, rest either left alone or labelled as triage 15:13:13 I'm pretty sure at this pace I'm going to eventually get through the backlog, it just is slow work 15:13:28 Anyone who has done this kind of triage against storyboard who wants to give me advice on how to be more efficient, please reach out 15:14:11 not sure how to make more efficient I find it better than jira :D 15:14:44 I don't, and I dislike jira, but hey that's life :P 15:14:53 yes! 15:16:05 Are there any volunteers for sqlalchemy stuffs on ironic-inspector ? 15:16:21 I can help with that 15:16:27 Am I also able to edit the white board? (line 152 says WIP, but the change has been merged) 15:16:36 everyone is 15:16:47 kubajj, yeah, everyone can update =) 15:18:26 I think we can move on 15:19:58 #topic Deciding on priorities for the coming week 15:20:29 our focus for this week is important patches for ironic, inspector, ipa, bifrost that we want to include in the Zed release 15:20:30 I... think I can mark the RBAC stuffs as basically minus more tempest tests 15:20:53 https://review.opendev.org/c/openstack/bifrost/+/858099 is a fix for the last failing bifrost job 15:20:56 err, basically done 15:21:34 ok now I understand =), I was a bit lost with the minus 15:21:35 I don't know how important it is, but this one passed zuul after dtantsur changed the grenade test https://review.opendev.org/c/openstack/ironic-inspector/+/853304 15:21:39 tks TheJulia 15:22:28 kubajj: I gave that #ironic-week-prio and a +2 15:22:42 thanks JayF 15:23:25 wouldn't mind https://review.opendev.org/c/openstack/ironic/+/855872 getting in Zed - it's already in the prio list 15:25:07 https://review.opendev.org/c/openstack/ironic/+/852694 <-- would be nice as well 15:25:46 ajya, ack 15:25:54 TheJulia, ok 15:29:31 ok, moving on 15:29:40 #topic Baremetal SIG 15:29:52 wondering if we have any updates for it 15:29:59 JayF, tks for sending the email 15:30:12 I spoke with some of the devrel experts downstream here at GR-OSS, but didn't get much actionable feedback :| 15:30:45 One thing that was said, that I think we should consider -- is asking cores/contributors of Ironic to give a short talk on a new/lesser known feature when we don't have an external presentation 15:30:59 which I think is a decent idea; except that putting more work on contributors is probably unreasonable 15:31:32 We've also done that unless we want to do presentation on super minor things 15:31:47 then again... each cycle brings new things 15:31:48 it would be interesting, I think we did some presentations on this style... 15:32:02 bluntly, the presentation is just the honey to get folks in ... the real value is in discussion and getting folks in one place 15:32:15 but AIUI there's been little interest in attending a SIG without a talk so... 15:33:11 I've had some people tell me it is an issue of a lack of a standing meeting invite 15:33:57 and where we *have* gotten invites sent out to end operators, we've tended to have far better participation 15:34:02 hummm 15:34:24 I am onboard to create and maintain such an invite, but I have no idea who to initially populate it with 15:34:45 cores, if it is on google, we can all edit it with a google account 15:34:54 yeah 15:34:56 and invite more people *insert evil laugh here* 15:35:05 I wouldn't mind doing this 15:35:38 granted... the meetings system does icals... but that requires people to go find, and be willing to just add to their own calendar 15:35:42 a few... extra steps 15:35:42 It occurs to me both my emails are on weird TLDs (personal = .cc, work = .io) so maybe someone with a three digit TLD should own it anyway lol 15:36:34 I could create something, but I think we should discuss time/day 15:36:55 One of us should reply to the on-list thread with a doodle and the outcome of this conversation 15:37:03 my limiting factor has been the use of the 2nd or third tuesday in the month which collides with higher level meetings 15:37:34 I can create the doodle and answer in the thread JayF 15:37:59 ack, thank you 15:38:11 and we could do some sort presentations based upon added features, I think 15:38:18 at least from this past cycle 15:38:25 wondering if google would be the best thing to use, but we can discuss this after the meeting probably 15:39:23 also since at the PTG we will have operators it would be good to raise this during the PTG (I think) 15:39:57 that's actually a really good idea, and not far away 15:40:06 maybe worth just tabling the actual scheduling until post-PTG 15:41:49 more thoughts on it? 15:44:21 ok, let's do this =) 15:44:24 moving on 15:44:35 #topic RFE review 15:44:47 JayF, you added a topic =) 15:44:58 I mean, I'm "up" theoretically, but this is one of the bugs I ran across in triage 15:45:09 it's a reasonable RFE, we should probably do it, I'm +1 but wanted to put it thru the process 15:46:07 https://storyboard.openstack.org/#!/story/2009872 optionally turn machines off after cleaning failure 15:47:11 Are there any comments or disagreements? If I don't hear any I'm going to make this as RFE-approved. It's a reasonable request, and it's smart to make it configurable so if there's any harm in powering off after some failures (e.g. firmware failure), it'll have been done by a non-default config 15:47:46 that seems like a bug as well 15:47:52 in that the clean fault should be cleared out upon start 15:48:10 what they are describing is behavior where it does not 15:48:17 oh, interesting, I missed that nuance 15:48:33 I'll put that comment there and split the RFE from the bug part, and ask for more details on the bug piece 15:48:37 ++ 15:48:44 we might have quietly already fixed that without realizing that 15:48:48 but worth double checking 15:48:52 and fixing if not 15:49:04 ++ 15:49:07 I think it makes sense to allow operators to say "turn off even if it failed" 15:49:26 but we just need a giant warning "if you've bricked things, not our fault" 15:49:46 We can do that by conveying "why we leave power on" 15:49:51 in the event of a failure 15:50:12 Oh yeah, absolutely 15:50:28 yeah, we don't want to receive the blame :D 15:50:37 I'll split off an RFE, marked approved, for that feature and I've already asked the user in that ticket for more details on the bug 15:50:49 you both know I wouldn't implement this in any kind of dangerous way, I'm a hardware-chicken lol 15:51:02 tks JayF 15:51:49 #topic Open discussion 15:51:50 Dmitry Tantsur proposed openstack/bifrost stable/yoga: Do not install grub2 and shim on the host system https://review.opendev.org/c/openstack/bifrost/+/858391 15:52:03 does anyone have something that would like to discuss? 15:52:17 iurygregory: I've already felt horrible once when someone bricked a bunch of SSDs :( I'm just glad we were able to help them get them recovered 15:52:37 I had a thought of something semi-important, then it ran away 15:52:50 I think it is standing next to the coffee maker demanding MOAR COFFEEEEEEE 15:52:50 oh .-. 15:53:00 coffee \o/ 15:53:39 * iurygregory is happy because he bought more coffee capsules to use in the machine :D 15:53:46 Not to discuss, but I just wanted to let you know that now I have officially started my 4th year project and I will be working on the Integration of inspector into ironic https://storyboard.openstack.org/#!/story/2010275 15:53:56 \o/ 15:54:00 kubajj, \o/ nice 15:54:04 Nice to hear it kubajj, it'll be nice to have you staying around \o/ 15:55:04 So probably expect me asking couple of questions about inspector soon 😄 15:55:23 as long as you have a comically large magnifying glass while you ask them :P 15:55:24 I'm all yours, you can blame me for most of its misdesign :D 15:55:50 Thanks 15:56:06 kubajj: awesome! 15:56:11 kubajj: \o/ 15:56:44 kubajj: if you want to solve data model stuffs first, sqlalchemy 2.0 compatability is fun! :) 15:56:57 * TheJulia should actually look at that this week 15:56:59 "fun" 15:57:02 "fun" 15:57:04 :D 15:57:04 heh 15:57:07 Can you blame me?! 15:57:25 I think I heard some evil laugh 15:57:30 We can even complain to Mr Corgi about your behavior 15:57:32 :D 15:57:41 dtantsur, lol 15:57:48 TheJulia: I need to complete the first step in the storyboard first as I defined it as a minimal objective for the project. 15:59:05 dtantsur: mr corgi is presently glaring at me... But I think he wants to go for a alk 15:59:06 walk 15:59:16 corgi wins 15:59:23 always 15:59:31 thanks everyone o/ 16:00:00 #endmeeting