Monday, 2024-01-22

tkajinamit seems unit tests of sushy-tools are broken because of recent change in Werkzeug https://github.com/pallets/werkzeug/commit/eef696b15c5e9fc20ed718f6685a3f21f2fbc3b8#diff-ff3c479edefad986d2fe6fe7ead575a46b086e3bbcf0ccc86d85efc4a4c63c79R2201:33
tkajinamwondering if we can just update unit tests to expect 415, or we should fix the logic so that it returns 400, if the different code breaks something01:34
opendevreviewTakashi Kajinami proposed openstack/sushy-tools master: Fix broken unit tests with Werkzeug>=2.3.0  https://review.opendev.org/c/openstack/sushy-tools/+/90623001:40
tkajinamprobably this is the correct approach01:41
opendevreviewTakashi Kajinami proposed openstack/sushy-tools master: Fix broken unit tests with Werkzeug>=2.3.0  https://review.opendev.org/c/openstack/sushy-tools/+/90623007:35
opendevreviewTakashi Kajinami proposed openstack/sushy-tools master: Fix broken unit tests with Werkzeug>=2.3.0  https://review.opendev.org/c/openstack/sushy-tools/+/90623007:36
opendevreviewTakashi Kajinami proposed openstack/sushy-tools master: Remove translation sections from setup.cfg  https://review.opendev.org/c/openstack/sushy-tools/+/90621707:36
opendevreviewTakashi Kajinami proposed openstack/sushy-tools master: Add Python 3.10 and 3.11 to supported versions  https://review.opendev.org/c/openstack/sushy-tools/+/90621607:36
opendevreviewTakashi Kajinami proposed openstack/sushy-tools master: Improving nova search filter  https://review.opendev.org/c/openstack/sushy-tools/+/89613007:38
rpittaugood morning ironic! o/07:48
opendevreviewDmitry Tantsur proposed openstack/ironic stable/2023.2: Don't create a hardlink to a symlink when handling file:// URLs  https://review.opendev.org/c/openstack/ironic/+/90613208:32
opendevreviewDmitry Tantsur proposed openstack/ironic stable/2023.1: Don't create a hardlink to a symlink when handling file:// URLs  https://review.opendev.org/c/openstack/ironic/+/90613308:32
iurygregorygood morning Ironic10:37
dtantsurtkajinam: I wonder if the sushy library is affected (i.e. it does not send content-type)10:46
tkajinamdtantsur, the failure in sushy-tempest-uefi-redfish-vmedia is unrelated and seems the job is trying to reach a broken node in infra. I'm discussing it in #opendev now10:48
dtantsurk thanks for looking into it10:48
tkajinamor is there any failures I've not yet noticed ?10:48
opendevreviewTakashi Kajinami proposed openstack/ironic master: Stop using a specific mirror in infra  https://review.opendev.org/c/openstack/ironic/+/90625610:57
opendevreviewTakashi Kajinami proposed openstack/ironic master: wip: Attempt to use CI mirror  https://review.opendev.org/c/openstack/ironic/+/90625711:03
tkajinamdtantsur, seems like ^^^11:05
tkajinamI'll check if I can complete that shell hack to use infra mirror after dinner11:05
opendevreviewMerged openstack/sushy-tools master: Fix broken unit tests with Werkzeug>=2.3.0  https://review.opendev.org/c/openstack/sushy-tools/+/90623011:07
opendevreviewRiccardo Pittau proposed openstack/bifrost master: Collect lshw output in json format  https://review.opendev.org/c/openstack/bifrost/+/89040811:42
opendevreviewMerged openstack/ironic-python-agent master: Add support for reporting CPU socket number  https://review.opendev.org/c/openstack/ironic-python-agent/+/90064211:52
iurygregorydtantsur, looking at your comments from https://review.opendev.org/c/openstack/ironic/+/903379/, I've moved from e.message to e  (https://review.opendev.org/c/openstack/ironic/+/903379/5/ironic/drivers/modules/redfish/utils.py) but I'm puzzled why the log is showing the error as MissingAttributeError('The attribute UpdateService is missing from the resource redfish/v1') instead of just 'The attribute UpdateService is missing from the 12:08
iurygregoryresource redfish/v1'  12:08
dtantsuriurygregory: because you're checking it before the logging engine has applied str() on it. This is fine.12:09
iurygregoryaha!12:09
iurygregoryI was going crazy here 12:09
dtantsurFYI https://bugs.launchpad.net/ironic/+bug/2050054 (the linuxefi problem)12:09
* iurygregory needs more coffee12:09
iurygregorya new bug and I need to update my statistics from the last week lol12:10
iurygregorydtantsur, second question https://review.opendev.org/c/openstack/ironic/+/903379/5/ironic/drivers/modules/redfish/firmware_utils.py if I understood correct you said we have something like redfish/common.py,  but I couldn't find any in `ironic/common/` or `ironic/drivers/modules/redfish/` , it's ok to just create one under driver or in common? 12:16
opendevreviewMerged openstack/ironic-inspector stable/2023.1: Fix RBAC access for service/admin user access  https://review.opendev.org/c/openstack/ironic-inspector/+/90612312:20
opendevreviewVerification of a change to openstack/sushy stable/2023.2 failed: Handle a different related properties for missing TransferProtocolType  https://review.opendev.org/c/openstack/sushy/+/90574012:40
opendevreviewMerged openstack/ironic-python-agent-builder stable/wallaby: CI: specify Debian version explicitly  https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/90612112:50
opendevreviewMerged openstack/ironic-python-agent-builder stable/wallaby: Drop TripleO job  https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/90583512:50
tkajinamfyi.. docs job in master is broken because of https://bugs.launchpad.net/nova/+bug/2050090 ... I'm trying to downgrade pillow as a short term fix12:51
tkajinamso do not recheck12:51
iurygregorytks for the heads-up tkajinam !12:55
tkajinamfun moment after mass u-c bump :-)12:58
opendevreviewTakashi Kajinami proposed openstack/ironic master: Stop using a specific mirror in infra  https://review.opendev.org/c/openstack/ironic/+/90625613:12
rpittautkajinam: consider that we have in the plan to drop blockdiag13:13
rpittauthe issue with pillow is already known13:15
rpittautkajinam: at the moment we're looking at plantuml13:15
rpittauI actually wonder why the version was updated13:16
rpittautkajinam: https://bugs.launchpad.net/ironic/+bug/202634513:17
rpittaugoing to pin again to 9.5.013:17
tkajinamrpittau, ahh, ok so there is a bug already. I'll mark mine as duplicate13:24
rpittautkajinam: it's ok13:24
rpittauI marked mine as you were faster13:24
tkajinamah, yes13:25
tkajinambut I was talking about the bug I reported today... let me mark it as duplicate13:25
tkajinamclosed https://bugs.launchpad.net/nova/+bug/2050090 ( which I created today) as duplicate of https://bugs.launchpad.net/nova/+bug/202634513:28
rpittauright, thanks13:32
tkajinamrpittau, thank you, too13:33
tkajinamrpittau, looks like designate decided to use graphviz . I have no good view to tell which one is better, but I hope we don't pull too many tools13:34
tkajinamhttps://review.opendev.org/c/openstack/designate/+/88936913:35
rpittautkajinam: yeah plantuml is based on graphviz, problem is for us graphviz is not enough13:36
rpittaubecause we also make use of seqdiag13:37
rpittaulet's say that plantuml is more user-friendly :)13:37
tkajinamah, ok13:38
tkajinamthanks for the clarification and it sounds very reasonable to me13:38
rpittauno problem!13:38
rpittauhopefully I'l get to it soon :/13:38
tkajinamif we get an establish pattern, it may help the other projects. I see octavia has seqdiag and they had to disable it but can utilize the same approach, I hope13:44
rpittauwell I did some testing some months ago with plantuml, that's why I proposed that13:45
rpittauI need to retrieve the patch and propose it, just need to find the time for that!13:45
TheJuliagood morning13:46
iurygregorygood morning TheJulia =)14:08
dtantsuriurygregory: my bad, it's called utils https://opendev.org/openstack/ironic/src/branch/master/ironic/drivers/modules/redfish/utils.py14:39
iurygregorydtantsur, ack, tks!14:40
k_romanenkoHi! 14:56
TheJuliagreetomgs!14:57
k_romanenkoLong time no see 14:57
dtantsuro/14:58
TheJuliawell, that should be greetings, but apparently I cannot type, still.14:59
rpittauI took that as a mix between "greetings" and "oh my goodness"15:00
iurygregoryyou need more coffee TheJulia =)15:00
JayF#startmeeting ironic15:01
opendevmeetMeeting started Mon Jan 22 15:01:25 2024 UTC and is due to finish in 60 minutes.  The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'ironic'15:01
JayFGood morning everyone o/15:01
iurygregoryo/15:01
dtantsuro/15:01
TheJuliao/15:01
masgharo/15:01
JayF#topic Announcement/Reminder15:01
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:01
JayFNo action items from previous meeting; skipping that agenda item.15:02
JayF#topic Caracal Release Schedule15:02
rpittauo/15:02
JayFIt is R-10, no notable deadlines, but 10 weeks left :)15:02
JayF#link https://releases.openstack.org/caracal/schedule.html15:02
JayF#topic Potential BM SIG/Ironic meetup at CERN around June 6, 202415:03
JayFI will be at OpenInfra Days at CERN on June 6.15:03
dtantsurIs there a nice link with the info for ^^^?15:03
JayFSo will a handful of other Ironic contributors15:03
JayFWe are looking to see if there is enough interest to schedule a thing, likely on the 5th15:03
JayFIf so, it'll become official likely this week or next (I just got my travel approved on Friday)15:03
dtantsurI'm interested in theory, but cannot commit until I figure out.. many things15:04
TheJuliaI went looking last week, and it seems like not much has been published yet15:04
JayFThere is almost zero details published about the OIF Days, and the BM SIG meetup is in the "Jay and others think it's a cool idea" stage15:04
rpittauvery interested too, it's quite close for me to get to Geneve15:04
dtantsurOnce official, I can ask for budget (and consider if I can self-sponsor if I get a no (likely))15:05
JayFbut Arne asked me to check w/the community for general interest before we put too much effort into an Ironic meetup, specifically15:05
rpittaulikewise15:05
iurygregoryI'm not even considering based on the prices I saw =(15:05
rpittau:/15:05
JayFSo it sounds like "general interest but major logistical concerns"15:06
JayFI'll pass on the strong desire for more documentation about the OIF Days :)15:06
TheJuliaI'm unsure I'll be able to, trying to bring some clarity to my schedule for the year but it is going slow15:07
JayF90% of my orgs travel planning is done a the top of the year, which makes it good for events with this timing, but less good if something pops up in late 2024 :)15:07
JayFEither way, I think this topic is exhausted?15:07
JayF#topic Review Ironic CI Status15:08
JayFI had a separate topic for this, but will bring it up now instead since it's mostly-resolved15:08
JayFInspector docs jobs are broken on latest eventlet15:09
rpittauis that for eventlet or because of the uc update?15:09
JayFit was removed from upper-constraints in requirements project due to minor breakages across openstack and it being late in the cycle15:09
JayFI am talking specifically about eventlet, other breakages (I assume someone tried pillow again based on backlog?) I don't know details about15:09
JayFbut we will have to find some kind of solution in eventlet or sphinx autodoc to make things happy if we want to continue to be able to autodoc once we get new eventlet15:10
rpittauack15:10
JayFas of now, I'm working w/infra to get us experimental queue CI tempest/unit test/doc jobs that run against master eventlet so we can easily test15:10
JayFComments about this or other things to note? 15:10
JayFMoving on.15:12
JayF#topic Bug Deputy15:12
JayFThanks to iurygregory for volunteering to be the bug deputy.15:12
JayF#info Summary: -11 bugs, -2 wishlist items, -2 new, -9 in progress, -1 critical, -2 high.15:12
JayFAny comments iurygregory? Anyone want to volunteer to pick it up for this week?15:12
iurygregoryyw =)15:12
iurygregoryI forgot to update today, seems like we got a new bug =)15:13
JayFzarro boogs found :D 15:13
rpittauI think I can handle this week considering the great job done by iurygregory :)15:13
JayF#action rpittau is the bug deputy for this week15:13
iurygregorytks rpittau =)15:14
rpittau:)15:14
JayF#topic RFE Review15:14
JayF#link https://bugs.launchpad.net/ironic/+bug/204991315:14
JayFdtantsur proposed this on Decomposing out-of-band inspection15:15
dtantsurYeah. It's honestly somewhat less scary than it sounds :)15:15
dtantsurThe tl;dr is that I want to move oob (!) inspection to the default path15:16
dtantsurso that we virtually always have access to MAC addresses or CPU architecture (at least as far as Redfish is concerned)15:16
JayFI think my biggest issue with the RFE is that the top line of what it's accomplishing is not super clear (in the bug ticket itself). Right now, we can only do IB or OOB inspection, not both or a combination(?)15:17
* JayF suspects that this issue is based in his lack of inspection knowledge15:17
TheJuliaI think part of it is filling in some of the information gaps to create a easier user experience15:18
JayFWell, an easier user experience *for redfish users* 15:19
TheJuliasome paramters we have logic built around is just no longer required15:19
TheJuliaI think oob is already prior art in some other interfaces, fwiw, and IPMI is expected to have rough edges for those who continue to use it15:19
* JayF notes there's almost no way he's a "no" to this RFE, but is just talking through it to understand more15:19
dtantsurmy view is a bit biased because IPMI is going extinct in my world :)15:20
JayFWell that's part of why I'm asking the questions this way15:21
dtantsurJayF: we cannot officially do a combination of ib and oob15:21
JayFI know the Metal3 lens is redfish tinted :D 15:21
dtantsurBUT15:21
dtantsurthe inspector/agent interface actually is a hybrid interface - see my explanation in the RFE15:21
TheJuliasomewhat similar, only the most die-hard IPMI fans seem to continue to do new deployments with it15:21
dtantsurwe also need to keep in mind that for many consumers ironic today is what they deploy in a year15:22
TheJuliaor two, so  yeah15:22
dtantsur(does not apply to metal3, but we're indeed wearing fishy glasses)15:22
JayFShould we have an end goal (that this would be a step towards) of in-band inspection becoming "baked in" in a sense, too?15:23
TheJuliaI'm not sure there is truly value to forcing it in process wise, but if we can get the data as part of other processes its not a big deal15:23
dtantsurI'm pondering that.. I guess there may be some sense into re-running oob inspection in some cases? Like, installing a new NIC?15:24
JayFInspection has always been shaped a little differently than other things in-band, is all I'm thinking. If it could look more like other step-based flows, that'd be neat, but I suspect there are reasons I'm not thinking of that wouldn't be possible/desirable (even beyond the "not enough hours in the day).15:24
dtantsurInspection is kinda step-based - the hooks are very similar - but only in terms of processing data15:26
dtantsur"not enough hours" is always a critical problem tbh15:26
JayFyeah15:27
JayFEither way, I think I'm OK with this. I'm a little skeptical about doing it without a spec, but I suspect the diff is smaller than I realize and my skepticism is just ... lack of knowledge about inspection moreso than any meaningful concern.15:27
dtantsurheh, I even wrote the RFE in rst format in case you ask for a spec :D15:28
dtantsurit won't match very well into the template though15:28
JayFLet me put it this way, if I'm an Ironic operator, I'm not sure I understand what that RFE is doing.15:29
JayFAnd maybe in a world where we primarily communicate about new features via docs and release notes that is OK?15:30
dtantsurI can write a spec. In this case, I agree that the proposal is not exactly obvious unless you (like me) have spent months pondering it15:30
JayFI am saying ^ that is the problem I would like solved, I don't care if it's a fresh para at the top of an RFE, a spec, or interpretive dance :D 15:31
JayF*paragraph15:31
JayFbut unless there are objections I am A-OK with approving it since I trust you to do that :D 15:32
dtantsurSo folks, to spec or not to spec? :)15:32
TheJuliaspec might be good, tbh15:33
JayFAlright, spec it is.15:33
rpittaueither way honestly15:33
TheJuliaI kind of understand what your going after though, so I'm a bit easier to convince15:33
dtantsurOkay, I'll do it. The RFE text is half of the spec already.15:33
JayFI'd say like, a thin spec :)15:33
TheJuliaMany None or N/A lines :)15:33
dtantsuroh yeah :D15:33
JayF#agreed https://bugs.launchpad.net/ironic/+bug/2049913 needs to have a spec15:33
JayF#topic Open Discussion15:34
JayFI have one thing for here to start15:34
JayFblockdiag! 15:34
JayFBauzas made a suggestion in #openstack-nova I think we should execute on: https://bugs.launchpad.net/tacker/+bug/2026345/comments/11 15:34
rpittauyeah, we need to burn it down with seqdiag15:34
JayFunless there are moving parts I'm not aware of15:35
TheJuliaOne item in my mind is the priorities for the cycle, I suspect some of the items we put on there haven't made progress, or might be a review away. Others just haven't been started. We should likely revisit/discuss explicitly15:35
rpittauthat suggestion may work for blockdiag, but not sure about seqdiag15:35
rpittauI mean we could svg too for sequence diagrams15:35
rpittauI can put something together with plantuml in the next week, but we can even remove entirely the dependencies and just use pure images15:36
TheJuliaSome of the sequenec diagrams seem overkill at this point for our documentation15:36
TheJulia*or* haven't changed/updated/evolved in *ages*15:36
TheJuliawhich makes me wonder "is it really needed" and "does it continue to bring value"15:37
JayFAnd/or are less useful.15:37
rpittauthe other solution would be remove the sequence diagrams and convert blockdiag to graphviz15:37
rpittauwhich is what other projects are doing15:37
JayFThe seqdiag is my favorite, but I know many other folks don't like them and it's outta date15:37
JayFso I don't object if we wanna pull them 15:37
TheJuliaI'm thinking the ilo docs used to have tons of them, and it *really* wasn't needed in the end because it was painting a picture beyond the driver interface15:38
rpittaumost of the seq diags are in the ilo docs indeed15:38
JayFwe have a good one for agent deploy flow15:38
JayFthat's outdated but can be useful15:38
JayFI still use that when onboarding folks to how IPA works; but that's the only diagram in our docs I've used in years outside of the state machine15:39
JayFand like I said, it's significantly bitrotted and so I'm still +1 to dumping it 15:39
masgharIf any diagrams can still help newcomers, can we try to update them instead of removing them? 15:40
TheJuliaI think this is a thing we need to look at on a case by case basis15:41
JayFI'd rephrase that to a question pointed at you; you have recently been a newcomer: what diagrams have helped you?15:41
TheJuliaand discussing it to a conclusion during a meeting might not be viable15:41
JayFAnd that can be a good input to the discussion.15:41
masgharThe state machine so far :D I havent looked at the IPA diagram you mentioned though15:41
masgharPerhaps all the diagrams cant be discussed in the meeting alone, like Julia said15:42
TheJuliahttps://docs.openstack.org/ironic/latest/admin/drivers/ilo.html#id6 :)15:42
JayF++ I agree, but we will need to take action at some point15:42
dtantsuryeah, losing the state machine will be undesirable15:42
rpittaumasghar: that's not seqdiag though, it's a png15:43
rpittauor I'm confusing the file :)15:43
TheJuliastate machine has to be regenerated when we make changes (which is *often* also forgotten)15:43
masgharAh, so only the seqdiag ones are in consideration?15:43
rpittaufor the migration yes15:44
masgharrpittau: okay15:44
JayFTheJulia: is that code for "nobody check it for SERVICING"15:44
TheJuliaJayF: that had a python2 only dependency for SVG generation, yes15:44
rpittaumasghar: but your point makes total sense, if there is anything useful we should definitely migrate and update it15:45
TheJuliawhich is why it is now a PNG15:45
JayFegad15:45
* TheJulia gets some glue and applies it to jamesdenton__'s irc client15:45
JayFand makes a strong argument against "just punt it to offline" because that is an end state that's unpleasant for that15:45
jamesdenton__:|15:45
TheJuliajamesdenton__: sorry, your not allowed to leave us ;)15:45
jamesdenton__am i bouncing?15:45
TheJuliajamesdenton__: It seems that way15:46
TheJuliajamesdenton__ meet jamesdenton_ 15:46
JayFabout every 5-10 minutes :D 15:46
jamesdenton__had a pretty major storm overnight and some power outages... things settling down15:46
jamesdenton__yeah, i think znc is going nuts15:46
JayFSo sounds like the summary is: the state of generated diagrams in our docs is generally bad, not just the parts that are blocking u-c bumps, and should probably be a larger topic which involves retiring a large number of them.15:47
JayFI might try to nerd-snipe some of my friends in other communities to find us a replacement library ;) 15:47
rpittauispers plantuml15:47
rpittauargh15:47
* rpittau whispers plantuml15:47
TheJuliagoing back to the sequence diagrams, I think it might make sense to make sure some lower level details are covered elsewhere in our docs in terms of mechanics, but I think the diagrams in the ilo driver can be dropped15:48
JayF++15:48
rpittausounds good15:49
TheJuliamasghar: as one of our newer members, would you like to take a look at that? I can, but I may make some assumptions on what actually is documented clearly15:49
rpittauI can prepare an example patch to show plantuml15:49
JayFthat sounds great15:49
masgharI can! I will ask many many questions though :D15:50
TheJuliamasghar: that is fine :)15:50
masgharThanks rpittau!15:50
opendevreviewIury Gregory Melo Ferreira proposed openstack/ironic master: RedfishFirmwareInterface - Unit Tests & More logs  https://review.opendev.org/c/openstack/ironic/+/90337915:50
rpittaumasghar: questions welcome :)15:50
TheJuliarpittau: is this in regards to the sequence diagrams?15:50
rpittauyes15:50
TheJuliaokay15:50
masgharAlright then, I will start with the ilo diagrams15:50
TheJuliaperfect15:51
JayFAnything else we need to chat about in Open Discussion? :)15:51
TheJuliaI brought up our published priorities15:51
k_romanenkoI have some  little questions 15:52
TheJuliak_romanenko: for our open discussion section of our meeting?15:52
k_romanenkoI guess so.  Since I left Mirantis I have a batch of incomplete Ironic-related changes on review. 15:53
k_romanenkoOver last years I completed two of them. So far there are some changes pending. Here are questions related:15:53
JayFTheJulia: I suggest we encourage, here and on ML, people review that and take a dedicated agenda item next meeting to go over priorities, is that good for you?15:53
JayFTheJulia: that way we don't spend time here looking over it sync in meeting?15:53
TheJuliaJayF: fair, in the past I would have just told folks "update the whiteboard"15:54
TheJuliak_romanenko: okay15:54
JayFIn this case, the whiteboard is the attached bugs, which has the same effect here15:54
JayFbut I think a zoomed out view is valuable15:54
k_romanenko1. Is ML2 Neutron Events Fail Fast feature still actual? 2. Are Ironic_tempest_plugin tests still necessary? 3. Are the functional tests for ironicclient OSC plugin still needed?15:54
k_romanenkoIf yes all three, then I will continue on those topic. I just have some time. 15:55
JayFIf you have links to the reviews those questions are contextually related to that'd be useful too :D 15:55
TheJulia1) Neutron events processing work stalled, basically the issue was "how to pause/resume" where we need to in way that is non-breaking15:55
k_romanenkoML2 Fail Fast: https://review.opendev.org/c/openstack/ironic/+/37001615:55
TheJulia2) Depends, for api contract stuffs yes, if you have specific questions happy to look/discuss after the meeting.15:56
TheJulia3) I have no idea :)15:56
k_romanenkoTempest plugin, here I renewed the patch already https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/90607815:56
JayFI hashtagged 906078 for you with ironic-week-prio15:57
TheJuliaso I think the original stance was not to do negative testing in tempest, because largely those items should already be covered in overall unit tests. That being said, at a glance I suspect your additional tests make sense15:57
k_romanenkoironicclient OSC plugin tests like this: https://review.opendev.org/c/openstack/python-ironicclient/+/38249615:57
TheJuliaI just approved that one15:59
k_romanenkoThank you 15:59
k_romanenkoOk, then I will put aside the ML2 stuff and continue updating points 2 and 3. 16:00
JayFAnd just in time; because we're at time for the meeting.16:00
JayFThank you so much everyone16:00
JayFand welcome back k_romanenko o/16:00
JayF#endmeeting16:00
opendevmeetMeeting ended Mon Jan 22 16:00:56 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/ironic/2024/ironic.2024-01-22-15.01.html16:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/ironic/2024/ironic.2024-01-22-15.01.txt16:00
opendevmeetLog:            https://meetings.opendev.org/meetings/ironic/2024/ironic.2024-01-22-15.01.log.html16:00
k_romanenkoIt was nice to see all the same people after so long time. 16:05
JayFIt's nice in some ways :) Wish there were more new people to see, too16:05
TheJuliaWow, it feels weird that it is overcast and raining here....16:10
JayFTheJulia: *laughs in PNW* https://usercontent.irccloud-cdn.com/file/BxVIlqK6/rain-rain-rain-rain-rain.png16:11
TheJuliaI was like "why is it still dark in the office"16:12
TheJuliawe're really not equipped for tons of rain here16:12
JayFTheJulia: literally yesterday we went to the hockey game, left around 3pm, it was grey and miserable from the rain and it just being ... here ... we come home around 8-ish and it's almost *brighter* because even though it's darker, the grey is lifted16:12
JayFyeah, I know it's not directly comparable in terms of like, life-impact, but I hate the constant grey :/16:12
TheJulia:(16:13
TheJuliaYeah, it can get old16:13
JayFyeah but the flip side is we get beautiful, clear, mild summers16:13
clarkbI've found the most important thing is to not let the rain win. Its raining? we're still walking to school, or going on that hike, or fishing, etc16:15
clarkbthe last week has been bad bceause its actually been unsafe to be outside more than the cold/wet16:15
rpittaugood night! o/16:58
JayFo/16:59
masgharI need rain-repellant glasses tbh17:10
TheJuliaI'll just stay in doors when it is raining, then again living in a desert, flooding is the other concern when it is raining like it is right now.17:15
masgharHopefully there's no flooding 17:16
TheJuliait is almost guaranteed with nearby mountains.17:17
masgharOh dear17:17
masgharStay safe Julia!17:18
opendevreviewDmitry Tantsur proposed openstack/ironic master: Account for nodes with the same BMC hostname in inspection lookup  https://review.opendev.org/c/openstack/ironic/+/90630817:26
TheJuliamasghar: eh, so far okay, just one of the nearby roads appears to be flooding out for now18:37
TheJuliaJayF: I replied on https://review.opendev.org/c/openstack/ironic/+/902009 18:37
TheJuliaI'm not sure the concern you have is the item to go into depth in there, given what you cited are not cases where the policy in ironic comes into play.  Now, if other services changed default enforcement and ironic's config was out of date with the wrong role, then that would be problematic, but it is also something we're largely blind to18:39
JayFI think some nonzero amount of this is operator FUD that I've been fielding around this when billboarding Ironic's automatic_lessee support18:39
JayFthere's a lot of fear around running mixed setups which I thought was justified to some level, but it sounds like it's potentially not18:40
TheJuliaFUD how so?18:40
TheJulialike, normal "it is different, everything is going to break" or specific concerns?18:40
JayFor the "all cloud operator supplied by by config" in your comment is hiding complexity18:41
JayFTheJulia: I have had professional openstack deploy-y type of people say they can't enable new-style RBAC on any openstack services until *all* openstack services in a deployment supports them18:41
TheJulia... that is so wrong it is not even funny18:41
* TheJulia gets out a sad panda18:41
JayFTheJulia: I do not personally hold this opinion, but my comment there was meant to reflect that we might have FUD to fight against here18:41
* TheJulia ponders re-framing18:42
JayFit's not exactly (well, not ONLY) our job to do so, but it impacts us greatly so it seems prudent of us to frame this as best as we can18:42
TheJuliaYeah, I think with that in mind, I can reframe it a little to help with the FUD type concerns18:43
TheJuliaWould it be awful to explicitly call out "concerns over need for other services to support RBAC..." ?18:46
JayFWhy not just say it directly that: "It's our belief that this should be safe to enable even if you may be using openstack services which do not yet support RBAC scope (whatever the right glossary term is here)" and ask people to file bugs / let us know if it's not true?18:47
TheJuliasomething in the middle maybe18:48
* TheJulia looks out window, sees dark sky, goes and makes more coffee18:48
opendevreviewDmitry Tantsur proposed openstack/ironic master: Flip require_managed_boot to True for the new agent inspection  https://review.opendev.org/c/openstack/ironic/+/90631418:54
opendevreviewJulia Kreger proposed openstack/ironic master: Disable legacy RBAC policy by default.  https://review.opendev.org/c/openstack/ironic/+/90200919:11
TheJuliaJayF: take a look at ^ and lmk19:12
JayFBasically exactly what I wanted, a strong statement with specific caveats or no strong statement19:13
JayFA++ would converse again19:13
TheJuliasigh: 'ImageDraw' object has no attribute 'textsize'19:15
TheJuliamasghar: our docs builds are broken now too :(19:16
TheJuliado we want to block on the docs job for now?19:39
JayFwhat is the change that broke it?19:42
JayFthe charting stuff is a "fix it now" thing or something else?19:43
TheJuliawell, you liked to the bug filed against another project during the meeting :)19:49
TheJuliaI figured it was a "we should", but didn't realize we were broken19:49
JayFtbh I got the impression from backlog (read at like, t+15m from waking up, so maybe it was a misread) that u-c was going to be reverted for that19:50
JayFwhich is why I'm asking19:50
opendevreviewJulia Kreger proposed openstack/ironic-inspector master: Change policy to enforce only new policy  https://review.opendev.org/c/openstack/ironic-inspector/+/90511920:00
TheJuliaJayF: ahh, okay, no idea20:06
JayFhttps://review.opendev.org/c/openstack/requirements/+/90626220:07
JayFalthough I'll note, nova has fixed their build20:07
dkingdtantsur: M3 folks: I was wanting to get thoughts on adding some useful endpoints for the Ironic liveness probe for the BMO deployment. Is there any reason why that would be a bad thing?20:13
JayFCan you be explicit about what you mean by that?20:15
dkingJayF: Currently, the liveness probe for Ironic just calls 'http://127.0.0.1:6385'. That makes sure that the container is running, but too often I find that works while something useful, like 'http://127.0.0.1:6385/v1/nodes/' would fail, for instance if there is a problem connecting to the db.20:17
JayFah, so you're talking specifically about stuff in the operator, understood20:18
JayFthanks for the clarification20:18
JayFI wasn't sure if you were saying Ironic should add e.g. a /v1/healthcheck endpoint20:18
JayFlike used to be popular a few years back20:18
dkingyeah, really just the k8s deployment file for BMO.20:18
TheJuliawell, technically the healthcheck is there, the problem is it doesn't trigger anything in the backend20:18
dkingThat might be useful, but personally, I think just hitting /v1/nodes/ should be fine since that catches the issues.20:19
TheJuliaso if the db is roasting over a nice fire, only a node list will really give a clue to that20:19
TheJuliait still won't poll the backend, fwiw20:19
dkingOh, if there is a healthcheck, I think it really should include a backend request.20:19
JayFhitting /v1/nodes is also punishing your database for no good reason, really :)20:20
dkingIn my experience, I've had issues where the db itself is fine but for various reasons Ironic needs to restart to be able to connect to it. I don't think it's the same issue each time.20:20
dkingFair. But if it can't handle one extra hit, it's probably too fragile anyway. 20:21
JayFDepends on what your value of limit= is, how aggro your healthchecking is, and a few other things.... but the point is, there are lower-cost ways to validate :D20:21
TheJuliaYour not loading 100k nodes into your deployment... right?20:21
dkingI suppose that over time that really adds up, but maybe it's worth it to catch Ironic not being able to work. 20:22
JayFyeah, exactly ^ :D 20:22
dkingOkay. So, what's a better way to do that?20:22
dkingI suppose the client could report when there's a timeout.20:23
JayFIf you're looking for a single config for a single environment, and not a universal solution20:23
JayFI would be tempted to say "get a specific node" but that gets HILARIOUS when that node goes EOL20:23
JayFprobably GET /v1/conductors20:23
JayFI think that's the endpoint?20:23
dkingYeah, I wouldn't rely on any specific node. 20:24
JayFbecause you could then actually check to see if conductors are happy if you wanted to go a step further from that20:24
JayFthat is going to pull from the DB, confirm, with latency, that rabbit is happy20:24
JayFand not make your DB server work too hard in the process20:24
dkingCurrently, we already are checking state fairly regularly. I think it's BMO doing it. I don't know why something didn't yell from that.20:24
dkingOkay, that might work.20:25
dkingI don't see/v1/conductors20:26
JayFhttps://docs.openstack.org/api-ref/baremetal/#conductors-conductors20:26
TheJuliaJayF: well, no rabbit in  metal3 20:26
JayFah, valid20:26
JayFbut BMO is not only metal3, I think?20:27
JayFdepending on which BMO(?) I think dmitry has one that's not only for metal3 now20:27
JayFbut tbh I still haven't sorted all the glossary terms from that side of the community20:27
dkingOh, right, I needed to add the X-OpenStack-Ironic-API-Version header. But that means that if we added that to the probe, we would need to add the header as well.20:28
TheJuliawell, Bare Metal Operator for driving interactions with ironic != other operators doing just software setup at a high level, but the latter seems to be much more "problem/case" specific20:28
dkingEven if the results are empty, they still have to hit the DB, right, and maybe any other resources?20:29
TheJuliait does a select against the conductors table20:29
JayFin the RMQ case, that table would be updated with metadata if the conductor wasn't checking in20:30
JayFI don't think that happens in the json-rpc case20:30
TheJuliait still occurs, but it journals it to the db20:31
TheJuliaI'm not sure if we actually bother to keep it up to date in metal3's single process context20:31
dkingSo, currently, changing the liveness probe to something like `curl -sSf -H "X-OpenStack-Ironic-API-Version: 1.49" 'http://127.0.0.1:6385/v1/conductors/'` would seem to be a useful improvement?20:34
JayFI do not have enough context on metal3 as a whole to say that; but I would say it is a better test of "is Ironic likely to do a thing" than a query on `/`20:34
dkingOkay. I think that helps.20:36
dkingSo, what's up with /v1/heartbeat/?20:36
dkingAs in, if it doesn't check db connections, etc., why not?20:36
JayFThat is an internal endpoint used for the *ironic-python-agent* to heartbeat (report in, we would NOT call it heartbeat today I suspect) to Ironic.20:36
JayF> A /heartbeat method is exposed at the root of the REST API. This is used as a callback from within the ironic-python-agent ramdisk, so that an active ramdisk may periodically contact the Bare Metal service and provide the current URL at which to contact the agent.20:37
JayFfrom https://docs.openstack.org/api-ref/baremetal/#utility20:37
dkingOH, right. I got my head into the containers and forgot about the real stuff.20:38
JayFNo problem Neo, we all get distracted by the red dress sometimes :D 20:38
dkingIs there a similar endpoint on Inspector that would be good? I suppose that `/v1/rules` is still best as `/v1/introspection` could be much larger.20:41
JayFI don't know for inspector.20:41
iurygregoryseems like vmedia job is broken becuase it can't connect to the mirror https://zuul.opendev.org/t/openstack/build/68b9f6721c024cdc8b5e50c75af3853f20:46
JayFthey were talking about that in #opendev20:47
JayFjust being weirded out that it was hitting the mirror directly I think20:47
iurygregoryyeah, we have an attempt to fix it via https://review.opendev.org/c/openstack/ironic/+/90625620:47
TheJuliawe can temp disable and re-enable 20:48
JayFhttps://review.opendev.org/c/openstack/ironic/+/90625620:48
JayFis the fix20:48
iurygregoryyeah20:48
JayFit looks good to me except for the docs being broken20:48
JayFwhich has a u-c revert that is pending a second core review20:48
iurygregorystandalone failed 20:48
iurygregoryhttps://zuul.opendev.org/t/openstack/build/de9d82545d0d44c69b4135f6a290ac6920:48
JayFyou should dig into that separately I suspect, as the changed code does not impact standalone, right?20:49
iurygregorymaybe just a random failure =)20:49
JayFwell not random anymore, an Ironic expert just looked at it20:49
iurygregoryI don't think it does based on what I saw20:49
JayFsounds like it'll get identified and figured out ;)20:49
iurygregory:D hopefully!20:49
JayF(you know I'm talking about you, right :P)20:49
JayFlol20:50
iurygregoryI had this feeling lol20:50
iurygregory=D20:50
dtantsurdking: keep in mind that both conductors and nodes endpoints are authenticated. This is a potential problem for healthchecks.21:33
TheJuliabrraaaaiiinsss21:47
JayFpillow downgrade is in the gate22:21
iurygregory\o/22:30
TheJuliaAwesome22:34
JayFhttps://review.opendev.org/c/openstack/ironic/+/906256 is almost certinly going to need another recheck23:01
JayFb/c it got rechecked while pillow was still upgraded23:02
JayFso if you see it's failed, please bump it and remember only one core approval needed to fix the gate23:02
iurygregoryJayF, the change got +1 from zuul =)23:54
iurygregory+2W23:54
opendevreviewJulia Kreger proposed openstack/ironic-specs master: WIP/DNM: Document to discuss vmedia issue/fix options  https://review.opendev.org/c/openstack/ironic-specs/+/90632423:54
JayFstarted at > 2024-01-22 21:59:5723:54
JayFThank you queue?23:55
JayFlol23:55
JayFoh, other landed at 1:18(?)23:55
JayFthat must have hit my inbox late23:55
JayFinteresting23:55
iurygregorymagic23:59

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