Monday, 2024-08-19

opendevreviewMahnoor Asghar proposed openstack/ironic master: Add unit test to ensure full node object is not logged  https://review.opendev.org/c/openstack/ironic/+/92648710:39
iurygregorygood morning Ironic10:50
cardoeJayF: https://review.opendev.org/c/openstack/python-ironicclient/+/924895 is good btw13:30
cardoedang rebase was for real as we had touched the same lines of code. :/13:30
JayFcid: re: cardoe's change, we persist disable_ramdisk for runbooks inside the runbook, yeah? So I wonder if cardoe's change needs to ensure steps/disable_ramdisk and runbook are mutually exclusive14:52
JayFwdyt?14:52
* JayF put that comment on the change, will remove it if wrong14:54
cidJayF, cardoe: Exactly, I think it should be invalid to pass in a runbook and disable_ramdisk at the same time.14:54
cardoeAs in I should figure out how to hide that option if you're passing --runbook?14:55
JayFI think cid has it setup now wehre if you did14:55
cardoeWhelp. Back to the editor14:55
JayFclean --runbook blah --clean-steps {} it'll error14:55
JayFsaying you can only provide one or the other14:55
cardoeokay I can do that.14:56
cardoeAs far as the Python 3.12 support stuff... I'm getting nada from the requirements upstream folks.14:56
JayFthere's like one person14:57
JayFand they are doing release activities as well14:57
JayFI know that doesn't make it less annoying, but the only way to fix it long term is to get that team more resources14:59
* JayF is working on it as he gets more of his ironic work handed over14:59
JayFMeeting in a minute here though :) 14:59
JayF#startmeeting Ironic15:00
opendevmeetMeeting started Mon Aug 19 15:00:31 2024 UTC and is due to finish in 60 minutes.  The chair is JayF. 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
JayFHello everyone and welcome to the Ironic weekly meeting15:00
JayFAs always we hold meetings under the OpenInfra Code of Conduct at https://openinfra.dev/legal/code-of-conduct15:01
JayF#topic Roll Call15:01
JayFo/15:01
cido/15:01
JayFAs is somewhat obvious, I'm running the meeting this morning as Riccardo is out. Going to give a minute or three to see if we can manage quorum.15:01
masgharo/15:01
JayFI don't think there are any decision points looking at today's agenda, so I'm going to move on and get our usual things on the record :)15:02
JayF#topic Announcements/Reminders15:02
JayF#info Standing reminder to review patches tagged ironic-week-prio and to hashtag any patches ready for review with ironic-week-prio: https://tinyurl.com/ironic-weekly-prio-dash15:02
JayFThis is especially important as the milestone 3 is coming up at the end of August. This is the feature freeze observed by most Ironic projects (but not generally by Ironic). This means we should especially prioritize reviews that touch other OpenStack projects.15:03
JayF#info 2024.2 Dalmatian Release Schedule https://releases.openstack.org/dalmatian/schedule.html 15:03
JayFPTL nomination period is currently open. Riccardo is currently the only nominee for Ironic PTL; thanks for his volunteering for another term.15:04
JayF#info  the next OpenInfra PTG which will take place October 21-25, 2024 virtually! Registration is now open! https://ptg.openinfra.dev/ 15:04
JayFThe ironic team has been registered, and people with topics or who want to start gathering context/researching for discussion topics should look at the etherpad:15:05
JayF#topic https://etherpad.opendev.org/p/ironic-ptg-october-202415:05
JayFI know this may be the first PTG for some of our new contributors, so just a piece of advice: much of the useful PTG discussion happens beforehand, in the etherpad, while folks have time to do research.15:05
JayFThat concludes announcements/reminders from the agenda15:06
JayF#topic Review Ironic CI Status15:06
JayFSeems OK to me? I've not seen too much trouble, I had a patch pushed yesterday pass CI.15:06
cidGenerally okay. Yeah!15:06
JayFGood stuff, thanks for the report!15:07
JayFNo discussion topics for this week, skipping15:07
JayF#topic Bug Deputy Updates15:07
JayFI believe cid was bug deputy, anything interesting to report?15:07
cidNothing much. It was a silent week. 2 New bugs15:07
JayFSounds good. 15:08
JayFDoes someone want to volunteer to take it this week?15:08
JayFI anticipate a busy week or I'd take my turn :)15:08
cidI don't mind still! Unless there's anybody else15:08
masgharI will be out for 2 days this week, but I can take next week15:09
JayF#info cid and masghar will group up on bug deputization this week :)15:09
JayFNow you have to cooperate, it's in the agenda, can't hashtag-undo that :P 15:09
masgharSounds good :)15:09
JayFThere are no RFEs up for review, skipping that agenda item.15:09
JayF#topic Open Discussion15:10
cidIs there an equivalent tag to ironic-week-prio for other projects in OpenStack?15:10
JayFeach project has their own way of doing it, more or less15:10
JayFmany have a "Review-Priority" +1/-1 but usually ask that to be restricted to cores15:10
JayFe.g. for Nova, I know they track feature status in etherpads and meetings15:10
JayFand you usally have a champion15:10
JayFso if I need reviews I go edit that etherpad, show up in the meeting, or ask the core champion15:11
cidThat's indeed different from Ironic's15:11
JayFYeah, and the reality is, there are not many projects with so many cores you need a "system" beyond "just ask $person"15:11
cidWell, I have the runbook support patch up in openstack-sdk. I will just ask!15:12
JayFYeah, #openstack-sdks is a good place for that15:12
JayFbut they'll often wait for ironic cores15:12
JayFbut they'll often wait for ironic cores/15:13
cidTo review it first?15:13
JayFYou may want to #ironic-week-prio it so we can look too15:13
cidOk, great!15:13
* cid adds tag15:13
JayFOn a different note: adamcarthur5 and GR-OSS in general are working on enhancing gophercloud/openstack-exporter for prometheus support. If anyone has a specific use case/question/interest/etc feel free to reach out to me or him.15:13
JayF^^^ (for ironic)15:14
JayFAny other items for open discussion?15:14
JayFAlright, I'm going to close up the meeting. Thanks for coming o/15:16
JayF#endmeeting15:16
opendevmeetMeeting ended Mon Aug 19 15:16:10 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:16
opendevmeetMinutes:        https://meetings.opendev.org/meetings/ironic/2024/ironic.2024-08-19-15.00.html15:16
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/ironic/2024/ironic.2024-08-19-15.00.txt15:16
opendevmeetLog:            https://meetings.opendev.org/meetings/ironic/2024/ironic.2024-08-19-15.00.log.html15:16
kubajjo/15:18
JayF\o15:22
JayFcid: kubajj was going to help us with stress-ng gpu stuff15:22
JayFcid: CID, meet Kuba, Kuba is slowly-becoming-veteran of Ironic, I think he's now worked in some capacity at the three ironic pillars (RH, GR, and now CERN) :D 15:23
cidOh, Hey kubajj!15:23
kubajjJayF: msavchen picked it up instead, but the same team15:24
JayFkubajj: meet CID, he's working for GR-OSS on various Ironic things including trying to get support for upstream GPU burn-in as mentioned in my email15:24
kubajjcid: hi o/15:24
JayFYou're multiplying!15:24
JayFActually I probably met msavchen in Geneva, I bet, but don't have the IRC<>Face mapping setup in my brain lol15:24
kubajjJayF: it's Maryna, she's our Ironic expert (alongside Jose, but I was hired to replace her as her program finishes in September15:25
JayFoh, of course15:25
JayFI think I know her more via her patches than via conversations tbh15:26
kubajjJayF: sad I missed you at CERN by just a month or so :/15:26
msavchenhello hello, yes, I was there on Openinnfra event15:27
JayFHey, it won't be the last chance, I hope.15:27
msavchenHope so:)15:28
opendevreviewJay Faulkner proposed openstack/ironic-python-agent master: [doc] Clarify Step return values  https://review.opendev.org/c/openstack/ironic-python-agent/+/92654615:34
opendevreviewJay Faulkner proposed openstack/ironic-python-agent master: [doc] Clarify Step return values  https://review.opendev.org/c/openstack/ironic-python-agent/+/92654615:35
opendevreviewJay Faulkner proposed openstack/ironic-python-agent master: [doc] Clarify Step return values  https://review.opendev.org/c/openstack/ironic-python-agent/+/92654615:35
cardoeSo I'm looking at argparse. You can't have a mutually_exclusive_group that has an argument or another group15:37
cardoeChanged in version 3.11: Calling add_argument_group() or add_mutually_exclusive_group() on a mutually exclusive group is deprecated. These features were never supported and do not always work correctly. The functions exist on the API by accident through inheritance and will be removed in the future.15:38
cardoeCause that's how I see this working. Mutually Exclusive Group of ("runbook" OR "clean-steps && "disable-ramdisk")15:38
JayFI wonder if we can check late in the code15:42
JayFif both are set -> manually kaboom15:42
JayFor alternatively, just find out that it returns an API error that doesn't require a decoder ring and I'll revise my comment15:43
JayFe.g. if you do clean --runbook X --disable-ramdisk True # if it just runs the runbook that is bad; if it returns a 400: Give me a runbook OR a disable_ramdisk/steps15:43
JayFthen that's more OK :)15:43
JayFmainly just trying to avoid a case where someone passes --disable-ramdisk=true and  ironic ignores it and/or they get an impenetrable error15:44
cidcardoe: Unless I did not understand your last message,  you will not need to call `add_argument_group`, just including `disable_ramdisk` with `add_argument` is what you need.15:54
cardoeYeah that's fair. I'll play with it. I gotta now stand up one that has runbooks in it.15:55
cardoecid: Where am I adding "disable_ramdisk" too? Which group?15:55
cardoeCause you created a mutually_exclusive_group which means in that group only 1 can be specified. "clean_steps" OR "runbook"15:56
cardoeI can't add "disable_ramdisk" to that cause that's an optional for "clean_steps"15:56
cidOh, I see what you mean now.15:56
JayFI'd totally suggest just going the route of seeing how the API complains about it15:56
cidYou will have to manually validate that15:56
JayFand I'll note the local API setup I espouse in my youtube video, and is documented, is probably enough for this problem15:56
JayFso you shouldn't need a full devstack to determine the behavior if our logging is good enough15:57
cardoeSo I've got kind and k3s locally that run ironic. I just haven't gotten around to building my own containers.15:57
cardoeI'm consuming loki built containers so they're on stable versions.15:57
cidRight! I think adding the check at the API level is probablly sufficient15:57
JayFrunbooks hasn't made it into Ironic releases yet at all, fwiw, even bugfix ones15:58
*** dking is now known as Guest88616:09
JayFDo we have any working examples of firmware interface being used to update firmwares on ilo?16:37
TheJuliavia ilo itself, or redfish?16:39
JayFvia the new redfish interface16:39
JayFI mean: via IRONIC'S IMPLEMENTATION of the new redfish interface16:41
TheJulia@iurygregory ^16:44
iurygregoryJayF, I can provide some examples later, I'm in hurry right now, I need to go to my girlfriend's cousin's funeral16:51
*** Guest886 is now known as dking16:57
TheJuliaiurygregory: please ensure some of those examples go into docs. And condolences.17:09
dkingTheJulia: It might be a bit late in the day for folks, but regarding the fact that there's no current introspection, is there some way that I could see something from the `data` object from a collector in the `node` object passed on clean/deploy steps? Perhaps some internal way to set some data?18:54
TheJuliahmmmmmmmmm18:55
TheJuliadking: I don't think so off hand, but it seems like it could be added to the task for it to be optionally loaded in19:02
TheJuliabut I don't remember how the data and all gets precisely handled on the newest code19:02
cido/19:28
iurygregoryTheJulia, sure, I will push a patch19:40
JayFWe'll need a final release of Ironic libraries before the end of the week, FWIW. I assume release managers have been on that20:14
JayFiurygregory: my condolances, and zero rush on the ask -- Mainly we were curious about the idea of "components" given it appears from their end-user-hp-tooling perspective they mostly just run one command and it gets $stuff. I think they might be operating at a slightly higher abstraction layer and I'm trying to piece together what they need ... on a timeline of like "over the next couple months"20:15
iurygregoryJayF, the idea is for us to be able to keep track in our DB, the redfish call itself is just a SimpleUpdate Action with a given url for the firmware (but in the redfish spec there is something about Targets where you could specify the resource that would be updated, but atm no vendors have this working from what I've tested - Dell&HPE)20:31
JayFaha so *in practice* it's generally one package20:32
JayFand that's just a label for future use or for operators with interesting hardware20:32
iurygregorycorrect20:33
iurygregorysince we have plans to expand the "components" front 20:33
iurygregoryallowing NIC for example20:33
opendevreviewJay Faulkner proposed openstack/ironic master: Support Automatic Lessee from instance metadata  https://review.opendev.org/c/openstack/ironic/+/92488720:41
opendevreviewcid proposed openstack/ironic master: [WIP] Add inspection rules  https://review.opendev.org/c/openstack/ironic/+/91830322:35
opendevreviewcid proposed openstack/ironic master: [WIP] Add inspection rules  https://review.opendev.org/c/openstack/ironic/+/91830322:49

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