15:00:22 <rpittau> #startmeeting ironic
15:00:22 <opendevmeet> Meeting started Mon Oct 25 15:00:22 2021 UTC and is due to finish in 60 minutes.  The chair is rpittau. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:22 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:22 <opendevmeet> The meeting name has been set to 'ironic'
15:00:24 <iurygregory> o/
15:00:25 <TheJulia> o/
15:00:34 <erbarr> o/
15:00:35 <stendulker> o/
15:00:36 <bfournie> o/
15:00:36 <ajya> o/
15:00:38 <arne_wiebalck> o/
15:00:39 <rpittau> Hello everyone! Welcome our weekly meeting!
15:00:43 <rloo> o/
15:00:51 <rpittau> Our agenda can be found on the wiki.
15:00:55 <rpittau> #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting
15:00:56 <ameya49> o/
15:00:59 <Marina> o/
15:01:01 <dtantsur> o/
15:01:28 <rpittau> #topic Announcements / Reminders
15:01:53 <rpittau> the Yoga PTG was last week
15:02:01 <rpittau> #link https://etherpad.opendev.org/p/ironic-yoga-ptg
15:02:33 <rpittau> it looks like it was quite successfull :)
15:03:07 * iurygregory is writing a summary to post on ironicbaremetal.org and send to the ML
15:03:17 <rpittau> great!
15:03:51 <rpioso> o/
15:03:52 <TheJulia> iurygregory: thanks!
15:04:09 <iurygregory> np =)
15:04:20 <opendevreview> Dmitry Tantsur proposed openstack/sushy master: Prepare the ground to use enums instead of strings  https://review.opendev.org/c/openstack/sushy/+/815103
15:04:46 <rpittau> this is the only announcement for today, does anyone have anything else to announce/remind us of ?
15:05:16 <TheJulia> Nothing on my end
15:05:44 <rpittau> alright, moving on!
15:05:57 <rpittau> #topic Review action items from previous meeting
15:06:14 <rpittau> we didn't have any action items from last time
15:06:42 <rpittau> #topic Review subteam status reports
15:06:49 <rpittau> #link https://etherpad.opendev.org/p/IronicWhiteBoard
15:07:06 <iurygregory> I think we can skip ? ^ /me wondering since we need to update for the ones from Yoga
15:07:07 <rpittau> around L62
15:07:12 <TheJulia> I suspect much doesn't make sense on the subteam status report until we've reached forward consensus
15:07:19 <iurygregory> yeah =)
15:07:22 <TheJulia> for cycle priorities
15:07:24 <rpittau> yep
15:07:39 <rpittau> alright, let's move forward then
15:07:55 <rpittau> #topic Deciding on priorities for the coming week
15:08:00 <rpittau> #link https://review.opendev.org/q/status:open+hashtag:ironic-week-prio
15:08:30 <rpittau> I see the yoga themes is there already :)
15:08:39 <iurygregory> yeah I added already :D
15:09:18 <iurygregory> we will talk a bit more about it in open discussion =)
15:09:23 <rpittau> that's probably the highest priority for the week, but I guess we have some space for something more
15:09:39 <dtantsur> https://review.opendev.org/c/openstack/sushy/+/815103 could use some eyes
15:09:53 <dtantsur> unfortunately, I'm still not finished with common constants, but should be soon
15:10:08 <rpittau> added
15:11:21 <rpittau> any other patches to add to the priorities for this week ?
15:11:37 <dtantsur> https://review.opendev.org/c/openstack/ironic-python-agent/+/814771 if possible
15:11:55 <rpittau> sure, added
15:13:01 <rpittau> anything else ?
15:13:41 <rpittau> ok, let's move on
15:13:47 <rpittau> #topic Discussion
15:14:10 <rpittau> iurygregory: do we want to talk now about the Yoga Themes or you want to keep that for the end?
15:14:35 <iurygregory> rpittau, both are ok I would say?
15:14:56 <iurygregory> I added to open discussion because people will need to review the patch =)
15:15:29 <rpittau> ok, I guess we'll need time to have a look there
15:15:40 <rloo> do you want us to review that patch now?
15:16:16 <iurygregory> rloo, nope it will be more a request for review so people can provide feeedback during the next days
15:16:39 <rloo> ok, thx for clarification. (Does it need WIP or does that mean it isn't ready for review?)
15:17:14 <iurygregory> WIP is because we only have a few topics, I will remove after getting some feedback and add more information
15:17:41 <iurygregory> like after we figure out who is interested in which topic etc
15:17:47 <TheJulia> I guess my only concern is storage cleaning enhancement. I don't really remember discussing it during hte ptg and it basically made no progress on consensus building over the past six months
15:17:48 <rloo> 'topics' == 'themes' in the PR?
15:17:55 <rloo> seems like a lot of themes to me :D
15:18:08 <TheJulia> yeah, it is a lot of themes and some of it could be a little more generalized
15:18:15 <iurygregory> TheJulia, it was during the time you were in the TC call =)
15:18:32 <rloo> i think we forgot to get votes on these during the ptg.
15:18:41 <iurygregory> ok, seems like we are talking now :D let's continue
15:18:54 <TheJulia> We kind of realized a long time ago general work themes were better than specific items since sometimes areas shift/change
15:19:04 <iurygregory> I got the list from the https://etherpad.opendev.org/p/ironic-yoga-ptg L655 basically
15:20:18 <iurygregory> the idea is that contributors should vote on topics, provide feedback (we can merge this two topics etc,) (I want to help in this effort)
15:20:32 <TheJulia> Yeah, and often in the past, I've worked to generalize it a little more as defining the areas
15:20:55 <iurygregory> so I can update accordingly to what people said =)
15:20:59 <iurygregory> TheJulia, got it =)
15:22:03 <rloo> fwiw, i'm good with generalized or non-generalized themes, as long as 'we' know what is going on ;)
15:22:48 <rloo> the description of the theme will provide more info. and we can change things during the cycle (as we've done)
15:23:05 <iurygregory> yeah we can have the section with details like we had in xena
15:23:32 <TheJulia> rloo: ++
15:23:54 * rloo wonders if what might be more important is the primary contacts/who will do the work...
15:25:09 <iurygregory> well, they will provide the updates about the status and will be working on the theme
15:25:42 <iurygregory> if is something simple it doesn't have to be a theme or can just be merged with something more generic I would say
15:27:19 <iurygregory> so, as action item for people that are interested please review the Yoga Themes https://review.opendev.org/c/openstack/ironic-specs/+/815308 and provide your feedback :D
15:28:36 <rpittau> we will probably discuss more during the week, after the first reviews :)
15:28:45 <TheJulia> rpittau: ++
15:28:59 <iurygregory> agree =)
15:29:09 <rpittau> we can move forward for now
15:29:16 <rpittau> #topic Baremetal SIG
15:29:22 <rpittau> #link https://etherpad.opendev.org/p/bare-metal-sig
15:29:38 <rpittau> not sure if we have any news, arne_wiebalck ?
15:29:46 <arne_wiebalck> We have meetings since about a year now. I guess it is time to check if we continue, stop, change ...?
15:30:13 <TheJulia> Yeah, and I *think* the consensus was to start a mailing list thread as a retrospective
15:30:48 <iurygregory> I know we had a topic to talk about the SIG in the PTG on Friday but after TheJulia left everybody left the meeting also :D
15:30:55 <arne_wiebalck> heh
15:31:40 <arne_wiebalck> I can send a mail ofc, but since it costs nothing for anyone except for the speakers, I expect noone may care.
15:31:42 <rpioso> arne_wiebalck: I feel we're starting to hit our stride. The turn outs for the past 2 meetings were encouraging.
15:31:55 <arne_wiebalck> rpioso: true
15:32:11 <rpittau> we have the opportunity now
15:32:11 <rpittau> personally I think we should continue, participation was encouraging
15:32:16 <TheJulia> rpioso: good point!
15:32:21 <arne_wiebalck> well, we can continue as long as we have volunteers to present (which was not a problem so far, thanks to all of you!)
15:32:27 <rpioso> arne_wiebalck: Would be a shame to lose that as we hopefully come out of the pandemic.
15:32:31 <TheJulia> I think the difference is we did some active advertising for the last two
15:32:54 <arne_wiebalck> TheJulia: yeah, we were a little more "aggressive" :)
15:33:13 <rloo> 'marketing' arne, 'marketing' :D
15:33:13 * TheJulia imagines an advertising agency for bare metal bears and owls and whatnot :)
15:33:22 <arne_wiebalck> again, the main work is for the speakers and for steve who does the editing
15:33:22 <iurygregory> we didn't have as much operators as we expected, but this is something we can work on I would say =)
15:33:40 <arne_wiebalck> rloo: :-D
15:33:45 <rpittau> owl-bears ? https://en.wikipedia.org/wiki/Owlbear
15:34:06 <dtantsur> :D
15:34:07 <TheJulia> We only tended to get maybe 30% of those who responded or expressed interest… which is statistically pretty good for a community meeting during the work day
15:34:12 <arne_wiebalck> getting more operators to come along to anything is a long standing hard issue, it seems
15:34:33 <arne_wiebalck> the videos have between 100 and 500 views
15:34:38 <rpioso> Any Metal3 operator prospects?
15:34:58 <arne_wiebalck> most popular videos say "Introduction" in it
15:35:03 <iurygregory> yeah, wondering if the large scale sig has meeting with operators also =)
15:35:28 <rpittau> I was going to say if we should maybe extend the invitation to metal3 operators or devs, maybe during the metal3 meeting ?
15:35:46 <rpittau> not sure it was ever mentioned there
15:35:54 <arne_wiebalck> I don't think so.
15:36:14 <arne_wiebalck> a metal3 intro/overview would also be nice :-D
15:36:30 <arne_wiebalck> we still have quite some topics on the list
15:36:52 <arne_wiebalck> but I don't want to bother speakers if they think it is not the best use of their time
15:36:57 <rpioso> The Scientific SIG may be a source of operators, too. Is there a Telecom SIG?
15:37:42 <TheJulia> there is definitely overlap there, but I don't think much beyond verticals exists outside of the scientific folks
15:37:58 <TheJulia> and they largely self-organized in order to address a whole set of issues they had
15:39:09 <arne_wiebalck> I guess the main aspect is commitment from all of you to continue to contribute/prepare presentations.
15:39:43 <iurygregory> arne_wiebalck++
15:41:08 <arne_wiebalck> So, what is the feeling, we try to continue?
15:41:19 <rpittau> in theory next session should be november 9th
15:41:21 <iurygregory> I think so =)
15:41:28 <rpioso> ++...+
15:41:32 <arne_wiebalck> rpittau: yes
15:43:21 <iurygregory> I think we can move to the next topic rpittau =)
15:43:23 <rpittau> we should definitely continue, let's see if we can find a topic/presenter for the next session (not necessarily now)
15:43:29 <rpittau> yep
15:43:35 <arne_wiebalck> ok
15:43:48 <rpittau> #topic RFE review
15:44:05 <rpittau> rpioso: you have a request for an RFE ?
15:44:53 <rpioso> rpittau: Yes, we're proposing [RFE] Enhance Redfish firmware update user experience, https://storyboard.openstack.org/#!/story/2008723.
15:45:48 <TheJulia> I'm a bit concerned by a duality re-use of [redfish]use_swift. If memeory serves we added a new config option in the deploy interfaces for download of assets to the conductor
15:45:58 <rpioso> We added more details, so folks can better understand what's going to change and how.
15:46:47 <TheJulia> We've also had operators explicitly say they need conductors, or they need to be able to define/use their own external endpoint outside of openstack entirely.
15:47:15 <TheJulia> or that the bmc's can't reach anything but the locally attached network, so implication of behavior seems... problematic and possibly complicating for those operators
15:47:31 <dtantsur> I guess the idea is similar though?
15:47:45 <dtantsur> I either can use Swift to send things to the BMC or I can not
15:48:45 <TheJulia> or supply the url to the bmc to download
15:48:53 <rpioso> TheJulia: If I understand the operators need described above, the solution we've proposed should address that, no?
15:49:05 <dtantsur> yeah, so we get to *_download_source again :)
15:49:11 <TheJulia> dtantsur: exactly
15:49:51 <TheJulia> rpioso: no, it actually potentially breaks a case by forcing a download and different location of access
15:50:02 <TheJulia> At least, that is how I'm parsing it
15:50:29 <dtantsur> what does ilo do?
15:50:32 <dtantsur> and irmc?
15:50:41 <TheJulia> I *think* ilo posts the file
15:50:46 <dtantsur> my biggest worry would be creating more inconsistencies
15:50:46 <TheJulia> like contents to the bmc
15:50:49 <dtantsur> ahhh
15:50:51 <TheJulia> but I'd have to check
15:50:51 <dtantsur> well
15:51:04 <TheJulia> brain is at EIUNSUFFCOFFEEEEEEE
15:51:07 <iurygregory> can we update X FW at the same time? Does the BMC have support to do this?
15:51:19 <TheJulia> iurygregory: depends on the bmc
15:51:48 <iurygregory> so iDRAC has support to update multiple FW at once? (I think this would be the case right?)
15:52:31 <rpioso> iurygregory: Yes, it can update multiple FW during 1 reboot (at once, sort of).
15:52:42 <iurygregory> rpioso, got it =)
15:52:46 <dtantsur> it seems like iLO downloads the file locally, yeah
15:53:08 <dtantsur> I guess it may be an argument for re-serving the firmware from the conductor
15:53:56 <sonali_borkar> yes ilo download it locally
15:56:44 <rpioso> https://opendev.org/openstack/ironic/src/commit/5be9edecd3a7e6de905a1eff6621f0227f26b855/ironic/drivers/modules/ilo/management.py#L569
15:57:01 <TheJulia> the feedback generally seems to be that operators don't want the bmc's to be able to talk to anything if they can avoid it
15:58:20 <rpioso> TheJulia: Where do operators prefer the firmware packages be served from?
15:58:23 <TheJulia> I don't remember https://opendev.org/openstack/ironic/src/commit/5be9edecd3a7e6de905a1eff6621f0227f26b855/ironic/drivers/modules/ilo/firmware_processor.py#L162 being this complex
15:58:52 <rpittau> we're almost at the top of the hour, let's wrap up the meeting and we can keep discussing it afterwards?
15:58:54 <TheJulia> rpioso: locally attached https servers on the same network if outbound connections are required
15:59:15 <iurygregory> rpittau,++
15:59:32 <rpittau> we discussed the Yoga Topics already, so we can skip that
15:59:37 <TheJulia> rpioso: naturally, not every operator. Some are willing to allow some specific endpoint access such as the conductor's webserver or swift, but it really varries
15:59:42 <rpittau> last but not least
15:59:42 <rpittau> #topic Who is going to run the next meeting?
15:59:49 <iurygregory> I can run
15:59:54 <rpittau> thanks iurygregory :)
16:00:00 <rpittau> that's all folks!
16:00:03 <dtantsur> TheJulia: if they use virtual media, they already need to allow the conductor
16:00:05 <rpittau> #endmeeting