Monday, 2021-05-17

*** trandles has quit IRC00:04
*** janders has quit IRC00:17
*** baha has quit IRC00:17
*** yoctozepto has quit IRC00:17
*** eandersson has quit IRC00:17
*** janders has joined #openstack-ironic00:17
*** eandersson has joined #openstack-ironic00:17
*** baha has joined #openstack-ironic00:17
*** yoctozepto has joined #openstack-ironic00:17
*** ociuhandu has joined #openstack-ironic01:11
*** ociuhandu has quit IRC01:15
*** rh-jlabarre has joined #openstack-ironic01:27
*** paras333 has joined #openstack-ironic01:58
*** paras333 has quit IRC02:02
*** livelace has joined #openstack-ironic02:26
*** rh-jlabarre has quit IRC02:53
*** ricolin has joined #openstack-ironic03:12
*** ricolin has quit IRC03:12
*** ricolin has joined #openstack-ironic03:14
*** livelace has quit IRC03:16
*** akahat is now known as akahat|ruck04:26
*** paras333_ has joined #openstack-ironic04:45
*** paras333_ has quit IRC04:51
*** early has quit IRC05:25
*** early has joined #openstack-ironic05:28
*** logan- has quit IRC06:12
*** logan- has joined #openstack-ironic06:15
timeuwindow page_down06:23
*** k_mouza has joined #openstack-ironic06:26
*** k_mouza has quit IRC06:30
iurygregorygood morning Ironic06:37
*** mkowalski has quit IRC06:43
*** mkowalski has joined #openstack-ironic06:43
*** MahnoorAsghar_ has joined #openstack-ironic06:45
arne_wiebalckGood morning, iurygregory and ironic!06:54
iurygregoryarne_wiebalck, o/06:56
* iurygregory brb need to restart the notebook07:00
*** jawad_axd has joined #openstack-ironic07:05
*** iurygregory has quit IRC07:12
*** paras333 has joined #openstack-ironic07:20
*** iurygregory has joined #openstack-ironic07:21
*** paras333 has quit IRC07:25
*** tosky has joined #openstack-ironic07:32
*** lucasagomes has joined #openstack-ironic07:58
*** dtantsur|afk is now known as dtantsur08:09
dtantsurmorning ironic08:10
*** ociuhandu has joined #openstack-ironic08:13
iurygregorymorning dtantsur08:16
*** ociuhandu has quit IRC08:19
*** ociuhandu has joined #openstack-ironic08:28
jandershey iurygregory arne_wiebalck dtantsur o/08:40
arne_wiebalckgood morning janders dtantsur o/08:41
iurygregoryhey janders o/08:42
*** MahnoorAsghar_ has quit IRC08:47
openstackgerritDmitry Tantsur proposed openstack/ironic-python-agent master: [WIP] Stop accepting duplicated configdrive  https://review.opendev.org/c/openstack/ironic-python-agent/+/79047108:57
*** k_mouza has joined #openstack-ironic09:02
*** derekh has joined #openstack-ironic09:24
*** alexmcleod_ has quit IRC09:27
*** alexmcleod has joined #openstack-ironic09:27
*** dougsz has joined #openstack-ironic09:39
*** ociuhandu has quit IRC09:49
*** MahnoorAsghar__ has joined #openstack-ironic09:52
*** ociuhandu has joined #openstack-ironic10:15
*** ociuhandu has quit IRC10:15
*** ociuhandu has joined #openstack-ironic10:15
*** ociuhandu has quit IRC10:40
*** ociuhandu has joined #openstack-ironic10:43
*** ociuhandu has quit IRC10:44
*** ociuhandu has joined #openstack-ironic10:44
*** ociuhandu has quit IRC10:44
*** ociuhandu has joined #openstack-ironic10:46
*** ociuhandu has quit IRC10:50
*** ociuhandu has joined #openstack-ironic10:51
*** ociuhandu has quit IRC11:04
*** ociuhandu has joined #openstack-ironic11:14
openstackgerritBob Fournier proposed openstack/sushy-tools master: Add support for returning message and attribute registries  https://review.opendev.org/c/openstack/sushy-tools/+/79036111:21
*** ociuhandu has quit IRC11:23
*** paras333_ has joined #openstack-ironic11:24
*** MahnoorAsghar__ has quit IRC11:25
openstackgerritMerged openstack/ironic-lib master: Remove runtime dependency on pbr  https://review.opendev.org/c/openstack/ironic-lib/+/78792211:27
*** paras333_ has quit IRC11:29
timeuwindow page_down11:33
*** timeu has quit IRC11:33
*** timeu has joined #openstack-ironic11:33
*** ociuhandu has joined #openstack-ironic11:35
openstackgerritMerged openstack/ironic master: Add bios_interface to api-ref spec  https://review.opendev.org/c/openstack/ironic/+/79149311:38
openstackgerritMerged openstack/ironic-lib master: setup.cfg: Replace dashes with underscores  https://review.opendev.org/c/openstack/ironic-lib/+/79161911:39
*** ociuhandu has quit IRC11:44
*** yoctozepto has quit IRC11:55
*** rh-jlabarre has joined #openstack-ironic12:14
iurygregoryI've updated the Agenda for the meeting today (removed some items from last meeting)12:16
iurygregoryif anyone has topics feel free to add (the agenda is almost empty)12:16
*** ociuhandu has joined #openstack-ironic12:18
*** tzumainn has joined #openstack-ironic12:19
janderssee you tomorrow Ironic o/12:21
*** ociuhandu has quit IRC12:23
ajyaFor the meeting I added a bug for discussion12:24
*** ociuhandu has joined #openstack-ironic12:27
iurygregoryajya, ack =)12:29
iurygregorybye janders o/12:29
*** yoctozepto has joined #openstack-ironic12:31
*** ociuhandu has quit IRC12:31
*** ociuhandu has joined #openstack-ironic12:33
TheJuliagood morning12:54
iurygregorygood morning TheJulia13:05
dtantsurmorning TheJulia! how is it going?13:07
TheJuliaIt is going, just starting my workday13:07
* dtantsur sighs and looks at https://review.opendev.org/c/openstack/ironic/+/791035 again13:08
*** ociuhandu has quit IRC13:09
* TheJulia tries to wake up the work laptop13:10
* dtantsur uses "horrible mess" in a bug description, which is not a good sign13:10
TheJulia"organic horrible mess"13:10
dtantsurthank you, will fix13:10
TheJuliawhere all well everything was well intentioned13:11
TheJulia"Hi Laptop, Wake up!"13:11
iurygregoryyou can also use wormhole13:11
dtantsuryep, nothing of this has been created maliciously13:11
iurygregoryTheJulia, maybe the corgi or the cat can help :D13:11
dtantsurjust an incoherent growth of our JSON fields over the course of years13:12
iurygregoryouch13:12
iurygregorylet's switch to yaml :D13:12
TheJuliaoh jeeze13:12
dtantsurthis is re kernel_append_params, I showed you on Wed13:12
*** rloo has joined #openstack-ironic13:12
* dtantsur runs away screaming13:12
iurygregorykidding :D13:12
dtantsurwell, with the invention of ansible and k8s, yaml is officially a programming language, soo..13:12
*** ociuhandu has joined #openstack-ironic13:13
iurygregorymakes sense13:14
openstackgerritPierre Riteau proposed openstack/tenks master: Update pip and setuptools before installing requirements  https://review.opendev.org/c/openstack/tenks/+/79175113:15
dtantsurokay, collected my thoughts again https://storyboard.openstack.org/#!/story/200890213:16
*** ociuhandu has quit IRC13:19
*** paras333_ has joined #openstack-ironic13:23
*** jamesdenton has joined #openstack-ironic13:27
*** jamesden_ has quit IRC13:30
*** ociuhandu has joined #openstack-ironic13:31
*** ociuhandu has quit IRC13:38
openstackgerritDmitry Tantsur proposed openstack/ironic master: Clean up kernel_append_params for PXE/iPXE  https://review.opendev.org/c/openstack/ironic/+/79175513:39
*** ociuhandu has joined #openstack-ironic13:39
*** sdanni has joined #openstack-ironic13:43
TheJuliawe need to clean up credentials13:47
dtantsuryep, and credentials too13:49
TheJuliado we have things to review jam upon today?13:50
dtantsurmaybe my user guide changes/additions.. but it may require a thorough reading more than a discussion, so not sure13:51
TheJuliaI wouldn't even know what those changes are yet13:52
TheJuliaLiterally still getting my bearings after being out for a week13:52
dtantsurheh, then probably skipping it is fine13:52
* dtantsur is very sleepy13:52
openstackgerritPierre Riteau proposed openstack/tenks master: Update pip and setuptools before installing requirements  https://review.opendev.org/c/openstack/tenks/+/79175113:53
*** lmcgann has joined #openstack-ironic14:00
openstackgerritDmitry Tantsur proposed openstack/ironic master: Clean up kernel_append_params for PXE/iPXE  https://review.opendev.org/c/openstack/ironic/+/79175514:04
*** ociuhandu has quit IRC14:05
*** ociuhandu has joined #openstack-ironic14:07
*** jamesden_ has joined #openstack-ironic14:10
iurygregoryupstream meeting in 50min14:10
dtantsuriurygregory: who's chairing today in the end, you or me?14:11
* dtantsur doesn't care much14:11
iurygregorydtantsur, I assumed it was me =)14:11
dtantsurcool :)14:11
*** ociuhandu has quit IRC14:12
openstackgerritDmitry Tantsur proposed openstack/ironic master: Clean up kernel_append_params for PXE/iPXE  https://review.opendev.org/c/openstack/ironic/+/79175514:13
*** jamesdenton has quit IRC14:14
openstackgerritDmitry Tantsur proposed openstack/ironic master: Clean up kernel_append_params for Redfish and iLO  https://review.opendev.org/c/openstack/ironic/+/79176114:22
openstackgerritDmitry Tantsur proposed openstack/ironic master: Clean up kernel_append_params for Redfish and iLO  https://review.opendev.org/c/openstack/ironic/+/79176114:23
*** ociuhandu has joined #openstack-ironic14:36
openstackgerritDmitry Tantsur proposed openstack/ironic master: Clean up kernel_append_params for iRMC  https://review.opendev.org/c/openstack/ironic/+/79103514:38
*** ociuhandu has quit IRC14:41
TheJuliaI could also chair, I'm just wrapping up some of the emails I needed to reply to this morning14:42
openstackgerritDmitry Tantsur proposed openstack/ironic master: Clean up kernel_append_params for Redfish and iLO  https://review.opendev.org/c/openstack/ironic/+/79176114:43
openstackgerritDmitry Tantsur proposed openstack/ironic master: Clean up kernel_append_params for iRMC  https://review.opendev.org/c/openstack/ironic/+/79103514:44
*** Qianbiao has joined #openstack-ironic14:45
openstackgerritPierre Riteau proposed openstack/tenks master: Update pip and setuptools before installing requirements  https://review.opendev.org/c/openstack/tenks/+/79175114:58
*** MahnoorAsghar has joined #openstack-ironic14:59
iurygregory#startmeeting ironic15:00
openstackMeeting started Mon May 17 15:00:01 2021 UTC and is due to finish in 60 minutes.  The chair is iurygregory. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: ironic)"15:00
openstackThe meeting name has been set to 'ironic'15:00
iurygregoryo/15:00
dtantsuro/15:00
iurygregoryHello everyone, welcome to our weekly meeting, you can find our agenda in the wiki15:00
iurygregory#link  https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting15:00
iurygregory#topic Announcements/Reminder15:00
*** openstack changes topic to "Announcements/Reminder (Meeting topic: ironic)"15:00
TheJuliao/15:01
bfournieo/15:01
rpioso\o15:01
iurygregoryDoes anyone have anything to announce / reminder us?15:01
rlooo/15:01
dtantsurI think we're slowly approaching the sprint 1 releases15:02
dtantsurin 2 weeks15:02
TheJuliawe are I believe15:02
*** stendulker has joined #openstack-ironic15:02
stendulkero/15:02
iurygregory#info sprint 1 release in 2 weeks15:02
ajyao/15:02
TheJuliaI need to try and crank out performance related patches since it will be a major version bump with the removal of iscsi15:02
erbarro/15:02
iurygregoryyeah that makes sense15:03
iurygregoryshould we move for our next topic?15:03
TheJulia++15:04
iurygregory#topic Review action items from previous meeting15:04
*** openstack changes topic to "Review action items from previous meeting (Meeting topic: ironic)"15:04
iurygregoryI was looking at the logs, we don't have any action item, moving on15:04
iurygregory#topic #Review subteam status reports15:04
*** openstack changes topic to "#Review subteam status reports (Meeting topic: ironic)"15:04
iurygregoryXena themes is not merged yet https://review.opendev.org/c/openstack/ironic-specs/+/78414315:05
dtantsurvery close actually, we may even apply lazy consensus15:05
dtantsur(I think we wanted it on the last meeting?)15:05
iurygregoryaccording to last week meeting, the concensus was that we would merge by EOW15:05
iurygregorydtantsur, yeah15:05
dtantsurSHIP IT!15:05
rloo++15:06
iurygregoryDone!15:06
iurygregoryI will update the ironic board with the information, next week we can have the status, sounds good?15:06
dtantsuryep15:06
rloothx iurygregory!15:06
iurygregory#topic Deciding on priorities for the coming week15:07
*** openstack changes topic to "Deciding on priorities for the coming week (Meeting topic: ironic)"15:07
iurygregoryAnyone has patches that would like to be added to the priorities?15:07
TheJuliathanks iurygregory15:08
dtantsurI have a bunch of new things related to driver refactoring (kernel_append_params this time): https://review.opendev.org/c/openstack/ironic/+/791755 https://review.opendev.org/c/openstack/ironic/+/791761 https://review.opendev.org/c/openstack/ironic/+/79103515:08
dtantsurany objections to adding them? they're not large, just.. annoying?15:08
iurygregorydtantsur, ++ to me it makes sense to have them15:08
TheJuliano objections from me15:09
TheJuliaI'd like to get the db indexes added to the priority list for the week https://review.opendev.org/c/openstack/ironic/+/78862515:09
* dtantsur should probably stop generating more patches now that 1/3 of the weekly priority are his :D15:10
dtantsur++ to indexes15:10
TheJuliaand my patch to cleanup the node santiziation for performance15:10
TheJuliahttps://review.opendev.org/c/openstack/ironic/+/790142 however, it will also need another patch to cleanup objects on selected columns15:10
iurygregoryTheJulia, I think it's ok, the failures seems to be with tests and cover15:10
TheJuliaso it is blocked until I get that patch created/uploaded15:11
TheJuliaiurygregory: yeah, I need to cycle back to them later today, I was MIA all last week15:11
iurygregoryTheJulia, no worries =)15:11
bfournienot sure if its a priority, but would like to get some feedback on new fields in bios api - https://review.opendev.org/c/openstack/ironic/+/78670715:11
iurygregorybfournie, can be a priority without problems I would say15:12
dtantsuryep, the only problem is its size :)15:12
bfourniethanks iurygregory15:12
iurygregorydtantsur, yeah =)15:12
bfournieyeah, size15:12
dtantsuryou could avoid a dependency on sushy (which blocks this patch until a release) by splitting it15:13
dtantsurinto the generic parts and the redfish parts15:13
iurygregoryhumm I think we can release sushy15:13
iurygregorywe already have the support merged15:13
dtantsurah, have we?15:13
iurygregoryI can push today a patch in releases15:13
dtantsurgood, then let's release and replace depends-on with a bump of driver-requirements15:13
bfournieyeah the sushy patch merged15:13
bfourniek, cool15:14
bfourniethanks15:14
iurygregorynp!15:14
iurygregoryanyone have more patches?15:15
iurygregoryor should we move on?15:15
iurygregorymoving on =)15:16
iurygregory#topic Discussion15:17
*** openstack changes topic to "Discussion (Meeting topic: ironic)"15:17
iurygregorywe have one topic added by ajya - Failed to inspect node created with inspect-interface as idrac-redfish15:17
iurygregory#link https://storyboard.openstack.org/#!/story/200890115:17
ajyamysql has changed how it reports duplicate key error by adding table name to key name. This does not work well with oslo.db. There is bug reported in oslo.db, but not fixed yet15:18
ajyaI'm thinking it should be fixed there, but if not possible, add workaround in Ironic. Thoughts? Comments?15:18
dtantsurwe probably rely on this property in a lot of places...15:18
rpiosodtantsur: yep15:18
dtantsurlike, name duplicates, MAC duplicates everywhere.. these all probably raise HTTP 500 now?15:19
dtantsurdo we have any engagement from oslo.db folks already?15:19
ajyanot yet, they're having their weekly meeting now15:19
ajyaI'll raise is there, no response earlier today when I asked15:19
openstackgerritMerged openstack/ironic-specs master: Xena themes  https://review.opendev.org/c/openstack/ironic-specs/+/78414315:19
iurygregorydoesn't seem according to the15:19
iurygregoryhttps://bugs.launchpad.net/oslo.db/+bug/189691615:19
openstackLaunchpad bug 1896916 in oslo.db "duplicate key error for mysql >=8.0.19 are not parsed correctly" [Undecided,New]15:19
rlooI'd be surprised if this is only an issue with ironic15:19
TheJuliaDefinitely needs to be fixed in oslo.db15:20
dtantsurthat being said, I'm surprised we're trying to create ports twice in redfish-idrac inspection15:20
ajyathere is another project that had failing CI and they applied workaround15:20
dtantsursounds like we shouldn't do it on the iDRAC side?15:20
ajyathere is some logic in iDRAC side why it's done15:20
iurygregoryI don't see problem in our CI atm, Dell CI is reporting this?15:20
rpiosoiurygregory: No coverage15:21
ajyano problems in CI, I meant this issue - https://bugs.launchpad.net/tacker/+bug/189686715:21
openstackLaunchpad bug 1896867 in tacker "functional test failures due to unsuccessfully parsed duplicate key error" [Undecided,Fix released] - Assigned to Koichiro Den (koichiroden)15:21
dtantsurajya: if you insist on creating all ports (which I think may be wrong, but okay), you should overwrite _create_ports instead15:21
ajyaand yes, there is no coverage for our case15:21
iurygregorypeople can workaround using other release from mysql also, I'm wondering what is the mysql version we have in requirements15:22
dtantsurtrying to add ports twice is at least sub-optimal15:22
dtantsurI think this particular issue can and should be fixed on our side15:22
rpiosodtantsur: This bug could affect other uses of inspect_utils.create_ports_if_not_exist15:22
TheJuliaBut it also does follow the "fail and fallback model" as opposed to check first reconcile, then create model15:22
rpiosoTheJulia: +115:23
dtantsurrpioso: surely. but it doesn't mean that the iDRAC implementation shouldn't be fixed.15:23
rpiosodtantsur: Not the topic at hand.15:23
dtantsurmmm?15:23
rpiosoAs rloo pointed out, other projects have encountered this, including tacker.15:23
dtantsurthe bug is triggered by calling create_ports_if_not_exist twice. It should not happen.15:23
TheJuliaWe should have consistency in duplicate key errors because the code path all the way to API consumers doing things is impacted15:23
dtantsurI agree that it has to be fixed in oslo.db, but idrac-redfish is also wrong IMO.15:24
dtantsurand the fix is very trivial btw, can be landed much faster than oslo.db15:24
TheJuliaLets delineate the issues, they are two separate things and we could fall into a disagreement of python programming models easily with the driver and the reliance upon the failure and then fallback.15:24
TheJuliain other words, we could bikeshed the driver easily15:24
rpiosoTheJulia: ty15:24
dtantsurwe're not touching these topics15:24
rloois this for a new feature in idrac?15:24
TheJuliarloo: no15:25
dtantsurwe're discussing a very trivial issue: calling the same function twice for no reason15:25
rpiosorloo: No, it's a regression since Focal was introduced.15:25
dtantsurwhich has been fine all the time, but started triggering the mysql regression now15:25
TheJuliaindeed15:25
rlooif you want to backport it, i suspect it'll have to work with older oslo.db. unless oslo.db's fix is backported too.15:25
dtantsurit = ????15:25
rloooh, it is already failing.15:25
rpiosodtantsur: All calls to inspect_utils.create_port_if_not_exist could be affected.15:26
rlooif the code fix is easy as dtantsur sez, would be worth fixing in both places.15:26
dtantsurrpioso: I don't argue with that. Nor does it cancel anything I've said.15:26
rlooor wait for oslo.db to fix.15:26
dtantsurunless I'm missing something.15:26
iurygregorywe should probably talk with oslo folks to see about it15:27
rloodtantsur: that idrac code has merged; guessing you are suggesting an improvement here.15:27
rpiosodtantsur: https://github.com/openstack/ironic/blob/af94a3da1e3f66c70309bbb889c68dfc5bd67e9f/ironic/drivers/modules/inspect_utils.py#L4915:27
rpiosodtantsur: The exception is not caught.15:27
*** ociuhandu has joined #openstack-ironic15:28
rlooSo I think we're done? Someone needs to mention to oslo.db that this affects ironic, it'll be up to them to decide priority etc. and if folks choose to enhance idrac code, that is their choice?15:28
ajyaTalking with oslo now about this issue15:28
rpiosorloo: Sounds workable to me :-)15:28
dtantsurI don't think that fixing bugs is a choice15:28
* dtantsur just makes a patch15:28
rpiosodtantsur: We'll handle it :-)15:29
dtantsurGreat, thanks!15:29
rpiosodtantsur: yw15:29
dtantsurIt boils down to implementing _create_ports instead of inspect_hardware15:29
*** ociuhandu has quit IRC15:30
*** ociuhandu has joined #openstack-ironic15:30
iurygregoryshould we move to our next topic?15:30
dtantsurlikely yes15:31
iurygregory#topic Baremetal SIG15:31
*** openstack changes topic to "Baremetal SIG (Meeting topic: ironic)"15:31
ajyaok, np, so for oslo we will propose a patch as noone else plans to do it, but they seem ok fixing it15:31
iurygregoryarne_wiebalck, do you have anything for the Baremetal SIG?15:31
arne_wiebalckRecord attendance at last week's meeting due to rpioso making publicity, thanks again!15:31
iurygregorynice!15:31
iurygregorytks rpioso =)15:32
arne_wiebalckVideo is already up, thanks stevebaker!15:32
arne_wiebalckThat's it, I think.15:32
iurygregory\o/15:32
iurygregorycool!15:32
iurygregorymoving on15:32
iurygregory#topic RFE review15:32
*** openstack changes topic to "RFE review (Meeting topic: ironic)"15:32
rpiosoarne_wiebalck: Thank you so much for sharing CERN's experience with ironic. Very informative and insightful!15:32
arne_wiebalckrpioso: ty :)15:32
iurygregoryMahnoorAsghar, you added https://storyboard.openstack.org/#!/story/200886615:33
MahnoorAsghariurygregory: Yes; looking for an approval for the RFE15:33
MahnoorAsgharUpdated it now15:33
dtantsurI don't my concerns about it have been addressed15:34
dtantsurI've put a comment re what we previously discussed15:34
MahnoorAsgharLast we discussed this, a vendor passthru implementation was considered favorable15:34
iurygregoryyes15:34
dtantsuryep, just keep in mind that I'll object to including it in metal315:35
TheJuliaarne_wiebalck: out of curiosity, was the video linked to from the ironicbaremetal.org blog?15:35
dtantsurso if you're doing it because of metal3, you may end up in a weird position15:35
arne_wiebalckTheJulia: the blog post with the same topic was15:35
MahnoorAsghardtantsur: Ive changed it to vendor passthru now...let me see your comment15:35
rpiosoDoes Redfish RAID work with vendors other than Dell Technologies?15:36
arne_wiebalckTheJulia: maybe could amend that link to mention the video as well?15:36
*** stendulker has quit IRC15:36
dtantsurrpioso: I'm not sure if anyone has tried15:36
rpiosoDoes the ironic RAID schema support controller and disk IDs?15:37
TheJuliaarne_wiebalck: should enitrely be possible15:37
MahnoorAsgharrpioso: It does, as per the documentation15:37
TheJuliaarne_wiebalck: it is just markdown in a git repo :)15:37
rpiosoCouldn't a default implementation of the originally proposed API addition return empty or a status that indicates it's not supported?15:38
*** MahnoorAsghar has quit IRC15:39
dtantsurshouldn't maybe the driver implementation support simple indexes instead of moving to metal3?15:40
TheJuliarpioso: each raid interface has slightly different requirements and I don't believe the ilo interface has as strict requirements for names/data like the idrac driver does, but it has been a couple years since I last looked at that code/docs so it is a bit difficult to speak to at the moment.15:40
dtantsurif e.g. the iDRAC impelementation allows numbers in addition to string names, it will solve the metal3 problem without most of complications15:41
rpiosodtantsur: The driver IDs indicate where the devices are located in the system. It depends on the system design.15:41
dtantsurright. what I'm suggesting is to move the numbering logic from https://github.com/metal3-io/metal3-docs/pull/148 to the ironic driver15:42
rpiosodtantsur: Redfish schema include ID props.15:42
dtantsurand avoid a new API in ironic completely15:42
dtantsurthen the feature proposed for metal3 will also work for other ironic consumers15:42
rpiosodtantsur: I don't see how the IDs could be made generic.15:42
dtantsurrpioso: exactly the way you're proposing it?15:43
rpiosodtantsur: Even Redfish did not attempt to normalize them.15:43
dtantsurI'm not saying cross-vendor15:43
dtantsurI'm saying: rather than inventing a new API to match numbers to names, accept numbers in your RAID implementation15:43
dtantsurin the physical_drives field (or how is it called?)15:43
dtantsurso pretty much what is proposed for metal3, but do it on ironic level, not in BMO15:44
*** MahnoorAsghar has joined #openstack-ironic15:45
rpiosodtantsur: What would the numbers mean?15:45
dtantsurrpioso: please check the metal3 proposal15:45
dtantsurthey're proposing using numbers instead of names and using the new API to replace numbers with names15:46
*** jawad_axd has quit IRC15:46
MahnoorAsgharMy laptop suddenly died without warning, sorry15:46
rpiosodtantsur:  We could not assure that as new hardware is introduced.15:46
dtantsurokay, then the metal3 proposal should probably drop the conversion bit15:46
*** jawad_axd has joined #openstack-ironic15:46
dtantsurthat being said, I'm okay with https://storyboard.openstack.org/#!/story/200886615:47
dtantsurjust trying to figure out if it's going to be useful for metal3 (seems like no)15:47
rpiosodtantsur: The metal3 proposal to generically number controllers and disks seems misguided to me.15:47
dtantsurrpioso: could you leave a comment there please? you have more information than me.15:47
rpiosodtantsur: 'naive' might be a better choice.15:47
MahnoorAsgharI think its an Airship use case15:47
rpiosodtantsur: We'll see what we can do.15:48
rpiosoRegardless, seems like ironic should provide an API which offers controller and disk IDs since the RAID schema supports that.15:49
dtantsuralso for generic Redfish?15:50
rpiosodtantsur: yep15:50
dtantsurthis is nice. yeah, I agree.15:50
rpiosodtantsur: At least for Dell.15:50
MahnoorAsgharrpioso: +115:51
rpiosoOther vendors are welcome to join to the discussion :)15:51
MahnoorAsgharI was looking into the HP docs; I think stendulkar could shed some light on it?15:51
Qianbiaorpioso may u give a link to the spec you are disgussing about?15:51
rpiosoMahnoorAsghar: Do you have the schema handy?15:52
TheJuliaMahnoorAsghar: he likely could, but I suspect he is asleep at this time. :)15:52
*** jawad_axd has quit IRC15:52
MahnoorAsgharTheJulia: I see15:52
QianbiaoI know you are talking about raid config of metal3 but not clear about which part.15:52
TheJuliaMahnoorAsghar: he is based in India15:52
MahnoorAsgharTheJulia: My neighbour15:53
iurygregoryQianbiao, https://github.com/metal3-io/metal3-docs/pull/148/files15:53
MahnoorAsgharrpioso: Let me try and find it15:53
MahnoorAsgharrpioso: You were talking about the Redfish spec?15:53
rpiosoMahnoorAsghar: schemas15:54
MahnoorAsgharrpioso: okay15:54
iurygregoryhttps://redfish.dmtf.org/redfish/schema_index15:54
iurygregory^ you can probably find in this page15:55
Qianbiaorpioso dtantsur may you have a look at https://docs.openstack.org/ironic/latest/admin/drivers/ibmc.html#backing-physical-disks15:55
Qianbiaois this implementation matches rpioso proposed?15:56
rpiosoThe ID property in https://redfish.dmtf.org/schemas/v1/Storage.v1_10_0.json15:56
Qianbiaoi think we should support drive-id too15:56
MahnoorAsgharQianbiao: The implementation matches the proposal15:57
rpiosos/ID/Id/15:57
iurygregorywe are almost out of time =) 2min15:57
rpiosoSame idea in https://redfish.dmtf.org/schemas/v1/Drive.v1_12_0.json15:58
QianbiaoHmm, i think we should give "id" to vendor.15:58
Qianbiaoiurygregory no worries, we may end the meeting first :)15:58
rpiosoQianbiao: Agree. Those would be returned by the new APIs which the spec originally proposed.15:58
*** bburns has quit IRC15:58
iurygregoryyeah =)15:58
iurygregory#topic Who is going to run the next meeting?15:58
*** openstack changes topic to "Who is going to run the next meeting? (Meeting topic: ironic)"15:58
iurygregoryDo we have any volunteers?15:59
TheJuliaI can15:59
iurygregorytks TheJulia15:59
iurygregory#endmeeting15:59
*** openstack changes topic to "Bare Metal Provisioning | Status: http://bit.ly/ironic-whiteboard | Docs: http://docs.openstack.org/ironic/ | Bugs: https://storyboard.openstack.org/#!/project_group/75 | Contributors are generally present between 6 AM and 12 AM UTC, If we do not answer, please feel free to pose questions to openstack-discuss mailing list."15:59
openstackMeeting ended Mon May 17 15:59:19 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2021/ironic.2021-05-17-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2021/ironic.2021-05-17-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2021/ironic.2021-05-17-15.00.log.html15:59
arne_wiebalckthanks iurygregory16:00
*** bburns has joined #openstack-ironic16:00
Qianbiaorpioso id here can stands any possible fields of a drive. For end user, everything they thinks can identify a drive could be "id".16:00
Qianbiaowhen i implement raid feature, it descripes "drive-id", drive-name, drive serial number, etc..16:01
lmcgannI know the meeting is over but since there was no open discussion I'd like to ask now if anybody has the time to check out our security spec it'd be greatly appreciated: https://review.opendev.org/c/openstack/ironic-specs/+/57671816:02
MahnoorAsgharQianbiao: Which one of these is the disk identifier given by the vendor? I couldn't figure that part out from the DMTF pages16:03
rpiosoQianbiao: The idrac driver supports the name the iDRAC uses to uniquely identify the device, which is referred to as the FQDD (Fully Qualified Device Descriptor).16:03
openstackgerritDmitry Tantsur proposed openstack/ironic-python-agent master: Do not serialize command_params  https://review.opendev.org/c/openstack/ironic-python-agent/+/79179816:03
QianbiaoMahnoorAsghar every drive only has one id indeed.16:04
TheJuliaI feel like I need a giant caffeine IV16:04
MahnoorAsgharTheJulia: Same xD16:04
Qianbiaobut when we handle the logic, drive name (which is unique too) can be an "id" to end user.16:04
MahnoorAsgharQianbiao: Okay...16:05
Qianbiaothe End user does not care about real id, he just knows drive name can identify an unique drive, and which is most friendly to him, so he just use it.16:05
rpiosoQianbiao: The iDRAC Redfish service uses the FQDD as the value of the Redfish resource 'Id' property. FQDDs are unique identifiers in the context of the system being managed.16:06
Qianbiaoibmc use slot id if i am correct.16:06
rpiosoQianbiao: Please see the definition of 'Id' in https://redfish.dmtf.org/schemas/v1/Resource.json.16:07
*** ociuhandu has quit IRC16:08
Qianbiaorpioso the drive id in ibmc looks like "HDDPlaneDisk1"16:09
QianbiaoHDD means hdd slot, 1 means slot number.16:10
QianbiaoI am not professional with ibmc btw, i am just a freelancer ~~16:10
* arne_wiebalck tried fast-track for the first time, in the context of burn-in, *really* nice :)16:11
rpiosoQianbiao: Here's an example iDRAC Id of a RAID controller: RAID.Embedded.1-116:11
TheJuliaarne_wiebalck: \o/16:11
QianbiaoHmm, really quit different.16:11
rpiosoQianbiao: 'Embedded' and 1-1 have meaning.16:11
rpiosoQianbiao: They indicate where it's located in the system.16:12
QianbiaoYes i can guess that.16:12
*** lucasagomes has quit IRC16:12
arne_wiebalckTheJulia: I use a "waiting room" conductor group to do inspection, burn-in and benchmark. This group has fast track enabled, as a requirement from the hardware colleagues. Once confirmed ok, the nodes move to their destination group.16:13
openstackgerritPierre Riteau proposed openstack/tenks master: Update pip and setuptools before installing requirements  https://review.opendev.org/c/openstack/tenks/+/79175116:13
dtantsurwow, cool16:13
TheJuliaarne_wiebalck: please write about this :)16:13
TheJuliasounds super cool :)16:13
Qianbiaorpioso btw, everytime i join weekly meeting, which encourages me to buy some dell stock. :)16:13
openstackgerritPierre Riteau proposed openstack/tenks master: Update pip and setuptools before installing requirements  https://review.opendev.org/c/openstack/tenks/+/79175116:13
rpiosoQianbiao: And here's the ID of a drive controlled by that RAID controller: Disk.Bay.0:Enclosure.Internal.0-1:PCIeExtender.Slot.416:14
Qianbiaoredhat too :), really nice team16:14
TheJulia:)16:14
rpiosoQianbiao: :-) Thank you so much!16:14
arne_wiebalckTheJulia: will do :)16:14
TheJuliaI'd buy stock in CERN if it was a company16:15
arne_wiebalck:-D :-D16:15
rpiosoI consider CERN one of the wonders of the world :-)16:15
Qianbiao:) we can not buy it, we can join it.16:15
TheJuliaThere is part of my brain that is just satisfied by helping improve humanity's knowledge of the universe. It sounds weird I guess.16:16
Qianbiaorpioso almost the same, id identifies the hardware position on mainboard16:16
rpiosoQianbiao: Could be a separate drive enclosure ...16:17
*** jawad_axd has joined #openstack-ironic16:17
Qianbiaoright16:17
rpiosoQianbiao: separate, as in external16:17
rpiosoIt can get complicated.16:18
mraineriI don't think you can deterministcally use "Id" in a manner to describe location or other types of relationships16:18
mraineriWhile I know Dell does that, "Id" is defined as an opaque identifier as a unique value for a member of a collection16:18
TheJuliaI believe the "it can get complicated" case is the same with hpe gear, although I think that is why there is also some of the "these are only hints, we may just focus on attempting to achieve x,y,z without a list of precise drives.16:19
mraineriSome systems might just use a number "Id" as a simple way to manage the keys in the collection16:19
MahnoorAsgharThe purpose is to specify the disks for RAID configuration. As long as the BMCs or Redfish accepts it, its all good16:19
mraineriIf you want to start applying relationships, you need to use properties in the resource designed for that purpose (like how in the Location property there is a ServiceLabel property that reflects some string a user can find on their enclosure)16:20
JayFMahnoorAsghar: I'm not familiar with this specific hardware, but I think the concern is that the "Id" field may not be deterministically numbered across runs16:20
*** Qianbiao has quit IRC16:21
rpiosomraineri: Do you feel a vendor-independent simple numbering scheme could be constructed which would make sense for all system designs from a user perspective?16:21
MahnoorAsgharJayF: Oh I see16:22
rpiosoJayF: It is deterministic for Dell gear.16:22
mrainerirpioso: I think so; we really want to encourage users to rely more on the properties of the resource rather than inferring any real knowledge about the thing based on the value of "Id"16:23
JayFrpioso: nice. Too bad the spec doesn't require that :C16:23
mraineriAll you can really know for sure from "Id" is that you have some unique value that identifies that resource in a collection16:23
TheJuliaThen the "what may change that" may need to be documented as well, just from a standpoint if somebody plugs in a cable between deployments, does it potentially change things around unexpectedly. At least, that would be my operational worry and without documentation I'd likely struggle to understand16:24
mraineriThat is not expected to change over the life of the system16:24
mraineriThere is a "Resource tree stability" clause that recommends things remain static as appropriate across service restarts16:25
mraineriSo, if you come across a URI like "/redfish/v1/Chassis/1/Drives/6", it's very reasonable that the same system will keep reporting that at that URI16:25
TheJuliaas long as there is no physical change I guess16:26
mraineriCorrect16:26
*** alexmcleod has quit IRC16:26
rpiosoTheJulia: To be clear, a drive could be replaced in the system. The new drive's FQDD/Id would be the same as the drive it replaced.16:26
TheJuliak16:28
mraineriI would expect that too16:34
mraineriI would also expect that in the case where the drive was removed, "/redfish/v1/Chassis/1/Drives/6" would still return 200 OK, but the status would indicate the drive is not present16:35
dtantsurHTTP 244 OK NOT FOUND16:35
dtantsur("Task failed successfully")16:36
mraineri:)16:36
rpiosoLOL16:36
dtantsuron this positive note I'm wishing you a great evening16:36
*** dtantsur is now known as dtantsur|afk16:36
mraineriIn all seriousness though, even if a device is not present, there's still good info a user might want to obtain16:37
mraineriLike, slot type, service label indicator, other capabilities of the slot...16:37
openstackgerritMerged openstack/tenks master: Update pip and setuptools before installing requirements  https://review.opendev.org/c/openstack/tenks/+/79175116:37
mraineriWe have a "Special resource situations" clause that helps describe this behavior16:39
* TheJulia blinks at ERROR 24416:41
mraineriDon't worry, we don't count that high in Redfish :D16:42
rpiosoTheJulia: How do our consumers figure out the storage controllers and disks a system has?16:43
*** gyee has joined #openstack-ironic16:44
arne_wiebalckbye everyone o/16:48
rpiosoarne_wiebalck: Good nite! :-)16:48
MahnoorAsghararne_wiebalck: bye o/16:49
*** jawad_axd has quit IRC16:50
MahnoorAsgharThank you guys for the discussion, Im gonna call it a night now16:51
MahnoorAsgharCheers!16:51
rpiosoMahnoorAsghar: Hope you have a nice evening.16:53
*** MahnoorAsghar has quit IRC16:53
*** MahnoorAsghar has joined #openstack-ironic16:54
MahnoorAsgharthanks :D16:54
*** MahnoorAsghar has quit IRC16:54
*** dougsz has quit IRC16:59
*** derekh has quit IRC17:00
iurygregoryenr I only saw this now https://review.opendev.org/c/openstack/releases/+/79074817:03
TheJuliarpioso: inspection data or direct examination. Which kind of leads me mentally to, why do we keep inspection data as-is17:03
iurygregorywe should probably get feedback to see if we are ok or not17:03
TheJuliaYeah, Steve Baker might have feels on this subject17:04
iurygregoryfrom RH perspective I think we are -117:04
iurygregoryI will add him as reviewer =)17:04
TheJuliaI'm ambivalent as it is train, since we can still merge to it17:04
iurygregoryyup17:05
TheJuliabut the direct to EOL may be bad.17:05
iurygregory++17:05
*** k_mouza has quit IRC17:12
*** k_mouza has joined #openstack-ironic17:13
TheJuliaI do think we need need to consider dropping pre-train branches17:17
TheJulialike, EOL them.17:18
*** k_mouza has quit IRC17:18
iurygregorysounds like a plan17:18
iurygregorythis is new to me... "Zuul PTL-Approved +1"17:37
iurygregoryhttps://review.opendev.org/c/openstack/releases/+/79180417:38
iurygregorynvm, it shows the name of Zuul in other patches, I never noticed :D (I was thought it was the name of the PTL/liaison)17:42
*** k_mouza has joined #openstack-ironic17:45
rpiosoTheJulia: Are you aware of any OOB inspection that offers that?17:49
*** k_mouza has quit IRC17:50
*** k_mouza has joined #openstack-ironic17:51
*** k_mouza has quit IRC17:51
*** k_mouza has joined #openstack-ironic17:52
*** rloo has quit IRC17:56
*** rloo has joined #openstack-ironic17:57
*** jawad_axd has joined #openstack-ironic18:01
*** k_mouza has quit IRC18:03
*** jawad_axd has quit IRC18:06
TheJuliarpioso: oob, no18:33
rpiosoTheJulia: Is the in-band data accessible via this API: https://docs.openstack.org/api-ref/baremetal-introspection/#get-introspection-data?18:38
TheJuliaYes, but entirely optional component *and* restricted to system-admin level access18:38
TheJuliawell, system-reader I guess would work18:39
rpiosoTheJulia: And that's the only way we offer to our consumers to identify the storage controllers and disks in a system?18:39
TheJuliaYes. Granted, we never intended for anyone other than a system adminstrator to be setting up such fine grained details on a system for things such as raid where a high level of explicit detail may be required to request something architecturally specific if the driver doesn't support a common/general happy path of configuration18:42
TheJulia"make me a giant raid5 if I don't tell you anything specific limited to the first controller" and the driver just figures it out18:42
TheJuliaNaturally, if someone is doing something highly detailed, they need that level of information to articulate exactly what and how they need it18:43
rpiosoTheJulia: Hrm ... A not uncommon PowerEdge config includes a BOSS controller for the operating system and a PERC controller for all other storage. They're both RAID controllers. How would configuring them be expressed without such explicit detail?19:09
rpiosoTheJulia: Also, btw, BOSS + software RAID controller is a thing.19:10
openstackgerritJulia Kreger proposed openstack/ironic master: Add additional node indexes  https://review.opendev.org/c/openstack/ironic/+/78862519:58
JayFI have seen RAID 10 implemented as the first layer done in PERC, and the second layer done in software (MD)20:04
JayFThis was years and years and years ago and I cannot remember why they did it that way (PERC/5 to really date it)20:04
TheJuliarpioso: Well, I *suspect* boss would be implied as the boot device under most circumstances. Why would anyone do a boss card with a mirror and then software raid though? That just adds to the overall io queue of the OS slowing it down  :\20:49
TheJuliaGranted, operational tools20:49
TheJuliaerr20:49
TheJulianot tools, but requirements can be crazy and varied20:49
openstackgerritJulia Kreger proposed openstack/ironic master: Add additional node indexes  https://review.opendev.org/c/openstack/ironic/+/78862521:28
-openstackstatus- NOTICE: The Zuul service at zuul.opendev.org will be offline for a few minutes (starting now) in order for us to make some needed filesystem changes; if the outage lasts longer than anticipated we'll issue further notices21:32
* TheJulia sighs21:32
* iurygregory time to go sleep, tks Zuul!21:34
*** paras333_ has quit IRC21:37
*** paras333 has joined #openstack-ironic21:38
*** paras333 has quit IRC21:42
*** lmcgann has quit IRC22:10
*** iurygregory has quit IRC22:10
*** iurygregory has joined #openstack-ironic22:19
openstackgerritJulia Kreger proposed openstack/ironic master: Add additional node indexes  https://review.opendev.org/c/openstack/ironic/+/78862522:38
*** uzumaki has joined #openstack-ironic22:45
*** uzumaki has quit IRC22:46
*** uzumaki has joined #openstack-ironic22:47
rpiosoTheJulia: In case you missed it ... A not uncommon PowerEdge config includes a BOSS controller for the operating system and a PERC controller for all other storage. They're both RAID controllers. How would configuring their logical disks be expressed without such explicit detail?23:28
*** k_mouza has joined #openstack-ironic23:34
openstackgerritJulia Kreger proposed openstack/ironic master: Add additional node indexes  https://review.opendev.org/c/openstack/ironic/+/78862523:35
TheJuliarpioso: It is somewhat logical to decide that the drive to be deployed to is the boss card resulting volume, but separate devices would need to be delienated so you'd basically need to know some additional information regardless23:38
rpiosoTheJulia: I'm referring to the RAID logical disk configuration.23:39
TheJuliaI know23:39
TheJuliacontrollers would need to be able to be delineated, then again if that can be done "under the hood" of the driver, maybe that is sufficent23:40
* TheJulia shrugs23:40
rpiosoTheJulia: So the user just knows?23:40
TheJuliaThe API consumer would just have to know today, disks and controllers. if the driver just can't figure it out "under the hood"23:41
rpiosoTheJulia: Perhaps an example target RAID config could help me understand what the driver would be expected to figure out.23:42
*** tosky has quit IRC23:43
*** tzumainn has quit IRC23:44
*** uzumaki has quit IRC23:44
rpiosodtantsur, MahnoorAsghar: I posted a comment to the Metal3 "raid-extension-for-physical-disks-and-controller" spec: https://github.com/metal3-io/metal3-docs/pull/148#pullrequestreview-661495303. Thank you, mraineri, for sharing your experience! I still feel that providing a means of obtaining the IDs from ironic is needed.23:45
TheJuliarpioso: examples 2 and 3 I think: https://docs.openstack.org/ironic/latest/admin/raid.html#examples-for-target-raid-config23:45
rpiosoTheJulia: ty23:47
NobodyCamGood Afternoon Ironic Folks23:49
NobodyCamAny reason we don't emit a node moved to Available event..23:52
*** k_mouza has quit IRC23:57

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