Monday, 2022-12-12

vanougood morning ironic01:56
opendevreviewVanou Ishii proposed openstack/ironic master: [iRMC] indentify BMC firmware version  https://review.opendev.org/c/openstack/ironic/+/86507403:31
opendevreviewVanou Ishii proposed openstack/ironic master: [iRMC] Handle IPMI incompatibility in iRMC S6 2.x  https://review.opendev.org/c/openstack/ironic/+/86507503:31
opendevreviewVanou Ishii proposed openstack/ironic master: [iRMC] indentify BMC firmware version  https://review.opendev.org/c/openstack/ironic/+/86507403:34
opendevreviewVanou Ishii proposed openstack/ironic master: [iRMC] Handle IPMI incompatibility in iRMC S6 2.x  https://review.opendev.org/c/openstack/ironic/+/86507503:34
rpittaugood morning ironic! o/08:12
opendevreviewRiccardo Pittau proposed openstack/ironic bugfix/20.2: Align iRMC driver with Ironic's default boot_mode  https://review.opendev.org/c/openstack/ironic/+/86678009:32
kubajjGood morning Ironic!09:39
*** dmellado_ is now known as dmellado10:39
rpittauplease when someone has a moment vheck https://review.opendev.org/c/openstack/ironic/+/866780 thanks!11:17
opendevreviewRiccardo Pittau proposed openstack/sushy stable/zed: Handle proper code_status in unit test  https://review.opendev.org/c/openstack/sushy/+/86720911:26
opendevreviewRiccardo Pittau proposed openstack/sushy stable/zed: Handle proper code_status in unit test  https://review.opendev.org/c/openstack/sushy/+/86720911:27
TheJuliagood morning13:32
opendevreviewJulia Kreger proposed openstack/ironic master: Add doc for lsblk: /dev/nvme0n1p2: not a block device  https://review.opendev.org/c/openstack/ironic/+/86722814:05
opendevreviewKirill proposed openstack/ironic-specs master: new spec: support of vnc console.  https://review.opendev.org/c/openstack/ironic-specs/+/86653714:29
TheJuliaKirill_: thanks for the formatting fix14:31
TheJuliaKirill_: +2'ed, a couple nit's. At a high level I grok what your doing, I don't think there is any impact since your functionally going to be adding another service which supports the novnc interface so the nova-compute service can return a working proxy url14:37
Kirill_so if +2, which steps are next - should we move it to unimplemented and i can start do it?) 14:40
TheJuliayou'll need another +2 to merge it14:55
JayFGood morning15:01
JayF#startmeeting ironic15:01
opendevmeetMeeting started Mon Dec 12 15:01:52 2022 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
TheJuliao/15:01
iurygregoryo/15:01
dtantsuro/15:02
matfechnero/15:02
hjensaso/15:02
JayF#topic Announcements/Reminder15:02
ajyao/15:02
rlooo/15:02
JayFStanding reminder to tag your patches that are ready-for-review with hashtag ironic-week-prio15:02
JayFand to review hashtagged changes as well15:02
JayFReminder also that meetings are cancelled 12/26 and 1/2 to allow folks to celebrate the holiday15:03
JayF#topic Action items from previous meeting15:03
rpittaup15:04
rpittaup/15:04
rpittauo/15:04
rpittauargh...15:04
JayFI did push that MR up to add an ironic-releases group; will be getting that populated with folks and getting things in place to retire old bugfix branches.15:04
JayFI'm thinking it might be wise to wait until Jan 2023 to activate on that? Does anyone have a strong opinion?15:04
Kirill_o/15:04
JayFI guess nobody cares about timing on that then?15:06
JayFrpittau: I also had you listed as having an action to remove centos8 jobs from bifrost/IPE wallaby15:06
JayFI think I saw that patch come through?15:06
rpittauJayF: that's done15:07
iurygregoryI don't think we are in a hurry to retire them, or are we?15:07
TheJuliajayf: no opinion from my point of view15:07
opendevreviewMark Goddard proposed openstack/ironic-python-agent stable/yoga: Warn when smartctl not found  https://review.opendev.org/c/openstack/ironic-python-agent/+/86715915:07
opendevreviewMark Goddard proposed openstack/ironic-python-agent stable/xena: Warn when smartctl not found  https://review.opendev.org/c/openstack/ironic-python-agent/+/86716015:07
opendevreviewMark Goddard proposed openstack/ironic-python-agent stable/wallaby: Warn when smartctl not found  https://review.opendev.org/c/openstack/ironic-python-agent/+/86716115:07
iurygregorywe can have a deadline but it can probably wait till begin of 202315:07
JayFiurygregory: the only real driving factors are that it's confusing when backporting stuff, and that the olld bugfix branches are all showing up in zuul-config-errors15:07
iurygregoryJayF, I see15:07
JayFYeah; I'm thinking I'll get all the commands lined up, sent to the list to review15:07
JayFand then execute after holiday15:08
JayFI just don't want someone to get broken christmas week :) 15:08
TheJulia++15:08
JayFaight it looks like we successfully did the things15:08
JayF#action JayF to document steps needed to retire bugfix branches; and schedule it to happen sometimes post-holiday (2023)15:08
JayFNext up15:08
JayF#topic 2023.1 WIP15:08
JayFShards workflow is actively blocked on reviews at this point15:09
JayFplease help us get the spec landed in ironic side so we can start landing db /api code15:09
JayFI'll make sure to put a review on 860731 for SQLA 2.0+inspector15:10
JayF#link https://etherpad.opendev.org/p/IronicWorkstreams2023.115:10
TheJulia++15:10
JayFMoving on15:11
JayFthere are no RFEs for review, skipping that15:11
JayF#topic Open Discussion15:11
JayFAnything for open discussion today?15:11
TheJuliaI'm happy to get on a call and walk through ether the shard spec or the inspector sqlalchemy stuffs15:11
JayFI'd be happy to participate in such a review jam15:11
JayFsuch jam, wow15:11
rpittauis anyone looking at the ironic weekly priorities recently?15:12
rpittauhttps://review.opendev.org/q/hashtag:ironic-week-prio+status:open15:12
rpittauwe have a lot still under review since november15:12
dtantsurTheJulia: I'm looking through the sqla stuffs right now15:12
rloo(I hope to go through the shard spec one more time today, if i have outstanding questions will ping TheJulia and/or JayF)15:12
JayFI've been trying to get the metrics bits done for reviews rpittau, I think they are incredibly down across the board15:13
JayFrpittau: I'll personally make sure to make a pass; but I am concerned overall review capacity in the project is diminished right now for reaosns I can't see/understand15:13
JayFI think we might have fallen into the trap where people are reviewing things they have comments for but not putting a lot of approval +1/+2s on stuff too, but I am not sure15:13
JayFEither way I noticed that too rpittau and would appreciate if cores across the project worked to get things landed15:14
rpittauJayF: I'll have a look this week15:14
JayFthanks for bringing it up :D15:15
rpittau:)15:15
JayFAlright, is there anything else for Open Discussion? 15:16
JayFIf not we can give folks a nice 40 minutes+ back :D15:16
TheJuliasounds good to me15:17
JayF#endmeeting ironic15:18
opendevmeetMeeting ended Mon Dec 12 15:18:00 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:18
opendevmeetMinutes:        https://meetings.opendev.org/meetings/ironic/2022/ironic.2022-12-12-15.01.html15:18
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/ironic/2022/ironic.2022-12-12-15.01.txt15:18
opendevmeetLog:            https://meetings.opendev.org/meetings/ironic/2022/ironic.2022-12-12-15.01.log.html15:18
Kirill_Hi, can someone help to review: https://review.opendev.org/c/openstack/ironic-specs/+/866537. TheJulia has already done it, need someone more))15:18
TheJuliaI was just going to mention that!15:18
Kirill_oh)))thanks15:18
rlooTheJulia: qq, does this need a reno? https://review.opendev.org/c/openstack/ironic/+/86693315:18
TheJuliaIt is a fairly quick read, semi-vague because it is primarily forklifting a service from nova and implementing an ironic version, the existing console specs should cover the API interaction with ironic, fwiw.15:19
TheJuliarloo: likely does, it is not explicitly required to backport, fwiw15:19
TheJuliaI can add one real quick15:19
rlooTheJulia: ok, ping me when it is ready. going to look at shard spec now...15:19
opendevreviewJulia Kreger proposed openstack/ironic master: Catch any exception for Cleaning  https://review.opendev.org/c/openstack/ironic/+/86693315:22
TheJuliarloo: ^^^ done15:22
rloothx TheJulia! JayF if you want to approve ^^15:23
JayFI hate it when they update under me LOL15:23
JayF+2a15:23
TheJuliaAnyone object if I single core workflow a networking-generic-switch submitted driver15:34
* dtantsur does not15:36
dtantsuranyone knows why this failed? https://zuul.opendev.org/t/openstack/build/3eb1359f5b5d422c91b77c8615c57c2515:36
JayFthat was the tox version update15:39
JayFit broke a lot of stuff all the way around15:39
JayFif that's not a recent result; recheck and it should pass15:39
JayFif it's a recent result then they probably didn't land the fix yet :| 15:40
rpittauI think all the fixes landed15:40
rpittauhttps://review.opendev.org/q/I9a138af94dedc0d8ce5a0d519d75779415d3c30b15:41
JayFnice15:41
* TheJulia needs a very large cup of coffee15:52
rlooJayF, TheJulia I've commented on https://review.opendev.org/c/openstack/ironic-specs/+/861803/19. Over to you. Is anyone else going to review?15:59
JayFarne_wiebalck had comments on it at some point; I hope someone else will review too15:59
JayFas we said in the meeting; there's just not a lot of folks reviewing16:00
rloothe overall 'shard' idea is fine. So I'm good with a MVP, V1 that provides the basic plumbing. It just isn't clear to me how to bootstrap this with the consumer. the consumer cannot 'self delineate' if it doesn't have any input so I am scratching my head there.16:01
TheJuliaI'm on a quick call at the moment16:02
rlooLMK if you would like to meet to discuss.16:02
rloo(am avail most of today)16:02
JayFI think the answer to that will just be documentation16:03
JayFe.g. "run a lot of node update calls to set a shard"16:03
JayFwe don't touch on migration much in the ironic spec though, that is fair16:04
JayFit is mentioned in the nova spec; but not the pieces you're asking about I think16:04
rlooi can envision manual stuff to do this. but not automated stuff.16:04
JayFYeah; I am not sold on automated shard setting16:04
JayFwhich is part of why I wanted it scoped out of the first spec16:04
rlooi think automated might make sense, but need more details to work the kinks out.16:05
JayFyeah; I'm not even pointing brainpower at that16:05
JayFuntil the whole more-manual story is done16:05
rlooand yes, it would be easier if this spec did not attempt to do anything automated.16:05
JayFit doesn't16:05
JayFif it says it does it's accidental and leftover :) 16:05
rloothere is a stretch goal or something.16:06
JayFyeah, just as sorta a visioning thing "this may be a next step"16:06
JayFI can tell you I'm not taking that step until ironic+nova pieces are done and talking :D 16:06
rloothat isn't a stretch goal... so it should be reworded... anyway, that's why we're discussing this :)16:07
JayFI'd be OK with completely removing it from the spec if it's a point of contention16:07
JayFand just leave it for future()16:07
rlooi have to read/review the spac as it is worded... 16:07
*** hjensas is now known as hjensas|out16:11
*** jamesdenton_ is now known as jamesdenton16:12
TheJuliaokay, off that call16:14
TheJuliaAhh, yeah, so the idea is it becomes opt-in, and they can through node-update calls16:15
TheJuliaI *think* one thing that might make migration "easy" moving forward, which is not clearly defined in Nova yet, but should likely come about likely in the next cycle a concept to possibly just "evacuate the entire compute node", but would be much automated, but slower in a sense. :\16:19
JayFI'm trying to push off that higher level logic for now16:19
JayFI want us to have node-update working, GET /v1/shard, and that about it for this spec16:20
TheJuliaYeah, I think it will come somehow16:20
JayFthen plug in the nova stuff16:20
JayFthen after that, we can evaluate if we want ironic magic, nova magic, or some combinatino16:20
JayFbut for now, I just want foundations in place for nova driver to jump off from16:20
TheJulia++16:20
TheJuliabuild the foundation, let the next level evolve from there16:21
TheJuliaand those next levels might be so stupidly simple we won't need much in the way of process to go "oh yeah, that makes sense"16:21
TheJuliathe challenge is... the foundation is a bit the Doctor's Tardis.16:21
JayFso if I read rloo's comments here correctly, it might be useful to just remove that stretch commentary altogether from the spec16:22
JayFand just be direct about what we're doing and let the magic follow later16:22
TheJuliaMaybe change the heading to "future ideas out of immediate scope"16:22
rlooi can comment on the spec itself if that would help you. 16:22
JayFI question the value of having possible ideas in a doc that will live even if those ideas don't get implemented? idk16:22
JayFI see both sides16:22
JayFit's good to have it written down but it's also good to only document that which is getting changed16:23
rlooi'm ok with possible future ideas or whatever.16:23
TheJuliawe're good at loosing ideas and oinly half implementing others at times16:23
TheJuliaso the line is kind of hard to draw16:23
rlooi'm not ok with high level stuff that this spec is supposed to describe )16:23
rloowe've done this before. had several specs to get some feature done.16:24
TheJuliarloo: what high level stuff specifically?16:24
rloothe automated stuff for example.16:24
TheJuliaso we can strip it all out16:25
rlooi'll comment in the spec. give me a few min.16:25
TheJuliaone of the really negative feedbacks we got on resource_class is the lack of auto-setting16:25
TheJuliasince this is sort of similar, it is entirely for a consumer16:26
TheJuliaalso.. humans didn't quite know what to set because placement was a mystery for most mortals16:26
JayFthe exception here is that small scale users of ironic arguably won't need to set shard16:28
JayFwhich is separate from resource_class16:28
JayFin fact; part of why I'm slightly skeptical about too much magic is that I think folks need to have an operational understanding of how/why they are sharding, rather than just letting it be magic16:29
TheJuliaThis is a good point, we just need to make sure we actually write enough details about how theory relates to practice16:29
JayFwe have to coordinate between devops (to setup computes to manage the shards) and ironic API; just like with something like networking that requires external state be reflected in our api16:29
TheJuliaso they can grok and apply16:29
TheJuliaI think the challenge is a number of medium shops run highly automated pipelines these days16:30
JayFlike, with my ops hat on16:30
TheJuliai.e. plug in rack and walk away while everything gets added/setup/enrolled/etc16:30
JayFI would've never, ever opted into any automatically-set-shard magic16:30
JayFif anything; I might would've wanted a feature to allow a cap set to count(nodes) per shard, and fail a create if there's "no room"16:31
JayFbecause I would want the "create a new shard" logic at a higher level, in the automation itself16:31
TheJuliaYeah, I guess that does play into your own business proceses and how you want to do things16:31
JayFyeah, I am so far from sold the automated stuff would be a win but I mostly didn't have this conversation because it was in the "maybe eventually" space16:32
JayFand I'm happy to have those conversations on the maybe-eventually time frame lol16:32
TheJuliaI think there are users who would love/appreicate it, but it is really not a complex feature in the end to have it as an opt in thing16:32
TheJuliaat some point down the road16:32
JayFyeah, I think it will look like a minor next step16:33
TheJuliayeah16:33
JayFif we did the foundational work -- including operational docs -- well16:33
TheJuliayup16:33
JayFif it doesn't seem like a minor next step, we should reconsider :D 16:33
TheJulia++16:33
TheJuliaWhich relates back to the overall effort to make it easier to contribute to OpenStack16:34
rloook JayF TheJulia. i commented in the spec, the sections to maybe reword or whatever. i think i had a few? other questions in that spec.  I think that we can discuss with arne later if he isn't avail now. the basic sharding won't preclude him using the same value for conductor group as for shard value...16:38
JayFI think the biggest piece we failed to comm for arne_wiebalck's original comment was how the scaling is different16:38
JayFIronic scales higher than all these other tools which are designed to scale to about the size of a hypervisor16:39
JayFso we use a shard so we can emulate that size (hypervisor) without having to sacrifice our own backend scaling freedom16:39
TheJuliaThat is a good way of putting it16:39
rloo(ping me if you have questions, i'm sticking my head downstream)16:39
TheJuliaI'm going to check one thing and I'll crack it back open16:39
TheJuliaApparently someone is putting a telephone pole in my yard.... o O (wut?)16:40
JayFTheJulia: Ironically, we'd be at about the same scale, conductor:compute:networking-agent, if we never made an agent driver and everyhing was still iscsi'd ;) 16:40
TheJuliadepending on the rollover frequency, yeah16:44
opendevreviewMerged openstack/ironic master: Fixes anaconda deploy for PXE boot  https://review.opendev.org/c/openstack/ironic/+/86005516:58
rpittaugood night! o/17:11
opendevreviewJulia Kreger proposed openstack/ironic-specs master: Add a shard key  https://review.opendev.org/c/openstack/ironic-specs/+/86180317:27
TheJuliarloo: hopefully that clears things up17:37
rloothx TheJulia! Will look in the next hour or so.17:38
opendevreviewMerged openstack/networking-generic-switch master: Add support for Dell OS10  https://review.opendev.org/c/openstack/networking-generic-switch/+/86006717:44
opendevreviewMerged openstack/sushy stable/zed: Handle a different error code for missing TransferProtocolType  https://review.opendev.org/c/openstack/sushy/+/86689917:46
opendevreviewMerged openstack/sushy stable/yoga: Handle a different error code for missing TransferProtocolType  https://review.opendev.org/c/openstack/sushy/+/86690117:58
opendevreviewJulia Kreger proposed openstack/ironic-specs master: Add a shard key  https://review.opendev.org/c/openstack/ironic-specs/+/86180318:36
opendevreviewJulia Kreger proposed openstack/ironic-specs master: Add a shard key  https://review.opendev.org/c/openstack/ironic-specs/+/86180318:41
TheJuliarloo: okay, there it should go18:41
TheJuliawell, be good18:41
rloo+2 TheJulia Thanks for all the updates!18:44
JayFarne_wiebalck: if you have further comments on the shard key spec; please make them. Otherwise I'm going to land it, probably sometime this week19:29
-opendevstatus- NOTICE: Gerrit will be unavailable for a short time as it is upgraded to the 3.6 release19:59
JayFTheJulia: if you wanna update https://review.opendev.org/c/openstack/ironic-inspector/+/860731 I will be a quick re-review; up to you if you wanna follow-up or update inline20:00
TheJuliaoh... hmm20:09
TheJuliagerrit upgrade20:09
* TheJulia determines gerrit cookies won't work for that20:09
opendevreviewMerged openstack/ironic master: [grenade] Explicitly enable Neutron ML2/OVS services in the CI job  https://review.opendev.org/c/openstack/ironic/+/86699321:25
TheJuliaJayF: I can do a follow-up tomorrow21:47
JayFaight21:48
opendevreviewMerged openstack/ironic master: Fix unit tests for Python 3.11  https://review.opendev.org/c/openstack/ironic/+/86686121:49
opendevreviewYusuke Okada proposed openstack/ironic stable/zed: Change boot_interface order of iRMC driver  https://review.opendev.org/c/openstack/ironic/+/86599822:41

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