Monday, 2024-09-23

rpittaugood morning ironic! o/07:32
timeuHi all, 08:13
timeuwhat's the difference esp_image and bootloader setting in the ironic.conf ? I know that the bootloader setting on the baremetal node and the global setting in the ironic.conf is used for UEFI booting. What does the esp_image do ? 08:14
dtantsurtimeu: I'm equally puzzled why we ended up with two names, these seem to be the same thing..10:56
dtantsurif you have a minute, file a bug. This is something we should sort out.10:57
opendevreviewDmitry Tantsur proposed openstack/ironic-tempest-plugin master: Check inspection data and abortion in the standalone tests  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/92792811:26
timeu@dtantsur: Thanks, will create an issue. 11:37
timeu@dtantsur: Created an issue: https://bugs.launchpad.net/ironic/+bug/208171911:53
opendevreviewcid proposed openstack/ironic master: [WIP] Add inspection rules  https://review.opendev.org/c/openstack/ironic/+/91830312:04
TheJuliagood morning12:58
TheJuliarpittau: replied to https://bugs.launchpad.net/ironic/+bug/2081305 with a thought which might enable us further13:02
rpittauTheJulia: good morning! I read it, thanks, I think it would make sense to change the default to "linux"13:41
rpittauI was actually looking at the configuration in CS9 and I think the "linuxefi" entry was just a way to distinguish from legacy that was introduced in older CentOS, and that now just points to "linux" as EFI/secure boot should work with that natively now, at least starting from GRUB 2.0613:41
rpittaulinuxefi was kept for backward compatibility13:41
TheJulia2.06 was also like 2-3 years ago if memory serves13:42
TheJuliaso, should be good to move in forward looking terms on the master branch13:42
rpittauyeah, the current version in CS9 is indeed 2.0613:43
TheJuliaof course, crossing distrbutions, the version doesn't mean much13:44
TheJuliagrub fragmentation is totally a thing13:44
rpittauyep, right13:45
rpittauat least for ubuntu and centos we should be good13:45
TheJuliayup13:46
TheJuliaIt might make sense to change in our latest stable branch as well13:50
TheJuliasince given how recent, that is a functional defect13:50
rpittauok, I think I can start having a look at that this week13:52
TheJuliaok14:07
opendevreviewDmitry Tantsur proposed openstack/ironic master: [WIP] Refactoring: get rid of AgentDeployMixin  https://review.opendev.org/c/openstack/ironic/+/93020314:13
dtantsur4 mixins are driving me nuts, hence ^^^14:16
rpittau#startmeeting ironic15:00
opendevmeetMeeting started Mon Sep 23 15:00:10 2024 UTC and is due to finish in 60 minutes.  The chair is rpittau. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'ironic'15:00
masgharo/15:00
TheJuliao/15:00
rpittauhello everyone! 15:00
rpittauWelcome to our weekly meeting!15:01
rpittauThe meeting agenda can be found here:15:01
rpittauhttps://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_September_23.2C_202415:01
rpittaugoing to give a minute or two for people to show up15:01
JayFo/15:02
JayFwelcome back rpittau 15:02
rpittauthanks :)15:02
rpittaualright let's start, not a lot of things today, mostly announcements15:03
rpittau#topic Announcements/Reminders15:03
cido/15:03
rpittauStanding reminder to review patches tagged ironic-week-prio and to hashtag any patches ready for review with ironic-week-prio:15:03
rpittau#link https://tinyurl.com/ironic-weekly-prio-dash15:03
rpittaulooks like we have some outstanding patches there but the situation seems ok15:04
rpittau2024.2 Dalmatian Release Schedule15:05
rpittau#link  https://releases.openstack.org/dalmatian/schedule.html15:05
rpittau1 week left to the official release!15:05
rpittauall ironic projects have been released!15:05
rpittauthank everyone!15:05
cardoeSo I don't actually know how to tag other people's patches with the weekly prio15:06
rpittaucardoe: you need to add the ironic-week-prio tag15:06
cardoeThere's a handful of docs updates that Jay and Julia have made that I think would be good for us to get over the finish line for the release.15:06
cardoeMy guess is the docs usually get the most eyeballs around a release.15:06
rpittaucardoe: there's an Hashtags field15:06
opendevreviewMerged openstack/ironic master: Fix typo in parameter description  https://review.opendev.org/c/openstack/ironic/+/93012115:07
opendevreviewMerged openstack/ironic master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/ironic/+/93010015:07
JayFcardoe: release is already done, fwiw, so those are locked in. We could backport if meaningful15:07
cardoeWell it'll update the "latest" docs which is what users will likely look at.15:07
JayFcardoe: obviously anything landed goes in /latest/, but for the dalmation-specific urls, we have to backport if desired15:08
cardoeSince looking at specific versions of docs is hard.15:08
TheJuliaDocs backports are easy/low cost as well15:08
cardoeWhere can I add the weekly tag? https://usercontent.irccloud-cdn.com/file/yLmY2fng/image.png15:08
JayFTheJulia: ++ that is basically the direction I was going15:08
rpittaucardoe: you need to click on Show All15:09
JayFcardoe: show all in top left, that'll expose hashtag, then add it15:09
rpittauthen you'll see the Hashtags field15:09
JayFcardoe: if you don't have access as a non-core, we can fix the acl15:09
JayFbut I *think* we already fixed it15:09
rpittauI think that's open for everyone15:09
cardoeI can't edit it https://usercontent.irccloud-cdn.com/file/SRsQFq7D/image.png15:09
TheJuliaI think it is restricted to cores *and* creators15:09
rpittauok, I remember wrong15:10
cardoeI know I'm derailing. So I apologize.15:10
rpittauthen a core will have to do that15:10
rpittaumoving back to the meeting :)15:10
dtantsurwe might need a group like "ironic-trusted-contributors"15:10
TheJuliano worries15:10
cardoeJust saying I'm willing to help triage the patch queue for you guys.15:10
rpittau#info the next OpenInfra PTG which will take place October 21-25, 2024 virtually!15:11
rpittaudon't forget to register!15:11
rpittau#link https://ptg.openinfra.dev/15:11
rpittauIronic team has been registered!15:11
rpittauAdd your name and topics to the etherpad 15:11
rpittau#link  https://etherpad.opendev.org/p/ironic-ptg-october-202415:11
JayFhonestly I'm just +1 to putting that access behind "any logged in user" until/unless we have evidence it's being abused15:11
JayFwe don't have to lock every door :D 15:11
rpittauJayF: I thought it was already like that, but to be honest I'd rather keep some margin of control to avoid any abuse15:12
JayFWhat abuse? There's not a slew of low-quality patches invading our priority queue :)15:12
JayFmaybe someone setting hashtag:buy-my-crapdotcom15:12
rpittauhashtags are not project-related15:12
rpittauany patch can be added potentially15:13
rpittauthat's an easy way to clog a board15:13
JayFI would embrace the problem of too many patches to review in the queue :D 15:13
TheJuliaAnyway PTG!15:14
rpittauyep15:14
rpittau#topic PTG time slots and planning15:14
rpittauso I've reviewd the etherpad of the PTG topics and it loks like we have quite a fwe15:15
rpittauI was thinking to go like last time15:15
TheJuliawhich was?15:15
rpittau3 days, 2-3 hours per day, plus potentially 1-2 cross-sessions and/or APAC-friendly senssion15:15
JayFI'd suggest we make sure to do a round trip about *when* to have those PTG sessions again, I know we have contributors from more varied parts of the world now 15:16
TheJuliaseems reasonable, but we likely need to look at the time windows and if topics exceed time windows we have for 2-3 hours a day, then we need to try to avoid compressing the window for topics15:16
JayFI'd rather book more time than we need and get it back than vice-versa15:16
rpittauyep, we can go for 4 hours, or even add 1 more day15:17
JayFwe do also at least have one desired cross-team session w/neutron15:17
rpittauI was planning to send a mail to see if there's anyone interested in an APAC-friendly session15:17
rpittauand yes about the cross session I was mainly thinkgin about neutron15:18
rpittauanyone wants to check with neutron people for a feasible time/day?15:19
TheJuliaI don't think they have established a schedule15:20
TheJuliaso we likely need to begin time windowing15:20
TheJuliaand then reach out from there15:20
rpittauyeah, I'd like to start booking our time slots first anyway15:20
TheJuliaso PTL ballpark estimate on existing topics15:21
rpittauyep15:21
TheJuliaand then begin reserve based upon that, with some author outreach15:22
rpittauyes15:22
rpittauI'll have that done hopefully this week15:22
TheJuliaok15:24
opendevreviewDmitry Tantsur proposed openstack/ironic master: Refactoring: get rid of AgentDeployMixin  https://review.opendev.org/c/openstack/ironic/+/93020315:24
rpittauI've added a caracal retrospective topic at the very top15:24
TheJuliaJayF: separate from meeting, if there is interesting in graphical consoles on your end in read-only mode as well, then maybe it might be worth while to have a separate graphical consoles session. I'm super hesitant and I think that might be a good middle ground, but read-only is likely more complicated.15:25
JayFTheJulia: *literally* my only requirement is "some way to see the output from the console without allowing access to put things on the console"15:25
JayFtext/graphical, I don't care15:25
TheJuliahmmmm15:25
TheJuliaInteresting15:25
JayFimagine a world where you need upgraded security access to touch the console of a machine with sensitive data on it; but just seeing the output from IPA trying to clean it is allowed15:26
JayFIronic being the arbiter of that access would allow operators to show their security teams that risk does not exist15:26
JayF(since Ironic already has root on bmcs, basically)15:27
TheJuliaYeah, true15:27
masgharThat makes sense15:27
rpittauanything else for the PTG?15:28
rpittaumoving on then!15:29
rpittau#topic Bug Deputy Updates15:29
rpittauanything worth mentioning on the bugs side?15:29
cidNothing, 4 new bugs15:30
rpittaucool, thanks cid :)15:30
rpittauI can take over bug deputy for this week15:31
rpittauI don't see any new RFE to discuss15:31
cidrpittau: alright. Ty!15:31
rpittauanything more to discuss for today?15:32
rpittaunp cid :)15:32
rpittauthanks to you15:32
rpittaualright15:33
rpittauI'll end up just announcing that apparently I will be PTL for the epoxy cycle too, and then we'll see! :D15:33
rpittauthanks everyone!15:33
rpittau#endmeeting15:33
opendevmeetMeeting ended Mon Sep 23 15:33:45 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:33
opendevmeetMinutes:        https://meetings.opendev.org/meetings/ironic/2024/ironic.2024-09-23-15.00.html15:33
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/ironic/2024/ironic.2024-09-23-15.00.txt15:33
opendevmeetLog:            https://meetings.opendev.org/meetings/ironic/2024/ironic.2024-09-23-15.00.log.html15:33
TheJuliaOut of curiosity, has anyone done any sort of competitive analysis recently?15:44
JayFNo. Honestly I probably should though, given how my role downstream can crossover into project manager-y stuff15:46
TheJuliaMine as well at times, which caused me to ask because I'm adding yet another new topic to the etherpad15:48
TheJulia(for the ptg)15:48
JayFhonestly if nothing else, having an idea where we draw the lines vs other softwares would be nice15:54
JayFbecause I think that's a key difference: Ironic is more laser-focused on lifecycle+OS deployment15:54
JayFbut many other things in this space are about full end-to-end workload management, and getting *a specific configuration* running15:55
TheJuliaThis is true15:55
TheJuliamaybe less about specific configuraiton, but more about specific type of workload15:57
TheJuliafor example, slurm15:57
TheJuliaI suspect we've been slightly allergic to such in the past too15:58
TheJulia(not slurm specifically, but slurm is an example specific workload solution, and we've generally been slightly allergic to workload integrations15:59
JayFI'm not saying we should *change* where our lines are drawn15:59
JayFbut when talking about Ironic vs other tools, beingl ike "Ironic + [this tool] can give a $thing-like experience" would be nice to have in the quiver16:00
TheJuliaThat [this tool] in my mind could also just be a driver or a playbook as a driver16:00
TheJuliaas well, so maximum value is delivered overall16:01
TheJuliaor to *enable* maximum value, I guess16:01
TheJuliaeveryone has different value perceptions16:01
TheJuliaand that is okay, just it is what is16:01
JayFI have hesitance about that kinda thing existing in Ironic16:01
JayFbut mainly in a sense of "should that live in Ironic or somewhere else"16:01
JayFnot in a if it's a good idea, just in-tree vs having stuff pluggable 16:02
JayFI think there's a reasonable path to consider where we try to make Ironic more friendly with external integration points16:02
JayFlike the OCI image is a push in this direction IMO16:02
JayFsomething like a hardware manager to run a step in a container16:02
JayFthese pieces which allow you to adapt to existing infrastructure with less pain16:02
TheJuliaWell, there are many different paths, some enable lots of clean further integrations16:03
TheJuliaWe all make complexity trade-offs16:03
rpittaugood night! o/16:07
TheJuliaI think we need to also be very clear at what problems we're seeking to solve, and we need to be mindful that the world will continue to evolve in some areas and evolution there is needful. If we get into a pattern of "well they can just do x", and that may be painful or workflow brudonsome, they may look for other options inherently because perceptions are different. I guess what I'm suspecting is that "table stakes" may 16:09
TheJuliachange/evolve, and we should be mindful of *that* aspect. Saying we'll solve it with more scaffolding and without the actual meet to the table stakes introduces risk as well, and the only way we can really be mindful fo that anyhow is to have a good grasp of what the table stakes are when evaluating the ecosystem.16:09
opendevreviewDmitry Tantsur proposed openstack/ironic master: Add disable_power_off field to the node model  https://review.opendev.org/c/openstack/ironic/+/93022916:22
opendevreviewVerification of a change to openstack/bifrost stable/2024.2 failed: Update .gitreview for stable/2024.2  https://review.opendev.org/c/openstack/bifrost/+/93003117:13
JayFYeah I think the heart of what you're getting at is something that Dave kept saying during the doc audit: we love to talk about the various things that could be possible but don't always do a good job of giving a direct path to do specific things17:38
TheJuliaAgreed17:45

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