15:01:22 <TheJulia> #startmeeting ironic
15:01:24 <openstack> Meeting started Mon Mar  1 15:01:22 2021 UTC and is due to finish in 60 minutes.  The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:25 <TheJulia> rpittau: it happens
15:01:25 <iurygregory> o/
15:01:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:26 <TheJulia> o/
15:01:28 <openstack> The meeting name has been set to 'ironic'
15:01:28 <rpittau> o/
15:01:30 <ajya> o/
15:01:32 <Qianbiao> o/
15:01:34 <rpioso> \o
15:01:38 <arne_wiebalck> o/
15:01:42 <bdodd> o/
15:01:45 <erbarr> o/
15:01:49 <stendulker> o/
15:01:51 <TheJulia> Our agenda is on the wiki as always.
15:01:56 <TheJulia> #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting
15:02:22 <TheJulia> It doesn't look like there is much to specifically talk about so I suspect today will largely be status updates.
15:02:39 <TheJulia> #topic Announcements / Reminders
15:03:02 <TheJulia> #info This week is ?R-6?, meaning we need to release Sushy/Ironic-lib/metalsmith this week.
15:03:38 <TheJulia> #info Outstanding sushy/ironic-lib patches that are in the gate, so if all goes well we should be able to take care of that tomorrow
15:03:55 <TheJulia> #info Next Week, python client library releases are due.
15:03:55 <rloo> o/
15:04:10 <TheJulia> Does anyone have anything to announce or remind us of this week?
15:04:31 <iurygregory> I've sent the email you asked last week TheJulia http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020774.html =)
15:04:51 <TheJulia> \o/
15:05:02 <iurygregory> I will add a doodle so people can choose slots so I can do the 101 XD
15:05:10 <TheJulia> ++
15:05:26 <TheJulia> Thank you iurygregory
15:05:31 <iurygregory> np!
15:05:39 <TheJulia> \o/ now we can skip action items from the prior week
15:05:56 <iurygregory> <insert happy dance>
15:07:42 <TheJulia> Well, seems like there are no more announcements to be made this week.
15:09:05 <TheJulia> Since we already covered the one action item, I guess we can review status
15:09:17 <TheJulia> #topic Review subteam status reports
15:09:30 <TheJulia> #link https://etherpad.opendev.org/p/IronicWhiteBoard
15:09:44 <TheJulia> Starting at line 297
15:10:28 <TheJulia> it... *looks* like we're good on NVMe support
15:11:10 <rpittau> yeah, changes merged, probably some follow up/docs next but the big part is done
15:11:18 <TheJulia> janders: Question for when your up: Do we need any doc changes. I'm assuming yes.
15:12:17 <TheJulia> arne_wiebalck: I see you +2'ed the node db history change
15:12:36 <TheJulia> arne_wiebalck: does it look like we might be able to make it for some of that work this cycle?
15:12:54 <arne_wiebalck> TheJulia: yes, I had a look earlier
15:13:00 <arne_wiebalck> TheJulia: erm ... :-)
15:13:28 <arne_wiebalck> TheJulia: kaifeng is really doing the work tbh
15:13:43 <TheJulia> Yeah
15:13:48 <TheJulia> I don't think it will make it in Wallaby
15:14:00 <arne_wiebalck> that seems tight, I agree
15:14:19 <TheJulia> Well, a good Xena feature then :)
15:14:24 <arne_wiebalck> so, we keep it out for now?
15:14:29 <arne_wiebalck> I mean the DB change?
15:14:50 <arne_wiebalck> does it make sense to merge it now when all the rest is still in the making?
15:14:57 <TheJulia> I *suspect* it is likely okay it not preferred to get the db change in
15:15:05 <TheJulia> but
15:15:14 <TheJulia> without the whole api surface we don't know how it will all stack yet
15:15:14 <arne_wiebalck> I would think so, too
15:15:27 * TheJulia notes the status for redfish raid
15:15:52 <rloo> ++ please don't merge the DB change w/o the rest :)
15:15:52 <TheJulia> iurygregory: I guess privsep is also moving to xena?
15:16:05 <arne_wiebalck> right, but adding sth non-complete has  a higher risk that we introduce sth we need to change later
15:16:09 <arne_wiebalck> rloo: ++
15:16:24 <TheJulia> yeah
15:16:29 <TheJulia> okay, then we punt it to Xena then
15:16:38 <iurygregory> TheJulia, yeah, rpittau was able to help me a bit (but I don't think we should land only initial support..)
15:16:53 <TheJulia> iurygregory: I concur, noting.
15:17:24 * TheJulia marks the json to yaml stuff as done
15:17:42 <TheJulia> ajya: thank you for the update onc onfig molds
15:18:18 <TheJulia> rpittau: zer0c00l: would review jaming on the anaconda deployment interface make sense?
15:19:11 <arne_wiebalck> TheJulia: ++
15:19:21 <rpittau> TheJulia: probably
15:19:32 * TheJulia adds lazy loading node attributes to ironic-week-prio
15:20:05 <TheJulia> Are we good to move on to priorities for the coming week?
15:20:14 <rpittau> let's
15:20:24 <arne_wiebalck> TheJulia: I was about to propose that, ty.
15:20:55 <TheJulia> #topic Deciding on priorities for the coming week
15:20:59 <arne_wiebalck> Shall we remove lines 571-595?
15:21:07 <arne_wiebalck> Or even to 609?
15:21:10 <TheJulia> #link https://review.opendev.org/q/hashtag:ironic-week-prio+status:open
15:21:48 <openstackgerrit> Merged openstack/sushy master: Follow up TaskMonitor refactor  https://review.opendev.org/c/openstack/sushy/+/777733
15:22:03 <TheJulia> arne_wiebalck: from the whiteboard?
15:22:07 <arne_wiebalck> yep
15:22:19 <iurygregory> we can also filter if the patch has verified +1 =)
15:22:33 <iurygregory> I can paste the link in the whiteboard
15:22:48 <TheJulia> arne_wiebalck: I'm not sure I understand why
15:23:03 <TheJulia> Please keep in mind, i was MIA part of last week and I've been mentally occupied with family stuff as of recent
15:23:24 <arne_wiebalck> TheJulia: The bare metal bit serves no purpose, does it?
15:23:32 <arne_wiebalck> *bare metal SIG
15:23:57 <TheJulia> Ahh, Interesting
15:24:01 <TheJulia> my line numbers were off
15:24:05 <arne_wiebalck> And the redfish profiles is duplicated in the Wallaby priorities.
15:24:18 <TheJulia> Seems reasonable
15:24:28 <TheJulia> If you wouldn't mind, go ahead
15:24:34 <arne_wiebalck> rpioso: any objections?
15:25:31 <rpioso> arne_wiebalck: Nope
15:25:37 * TheJulia removes merged items from the list
15:25:51 <TheJulia> Any new items to add that people are aware of to the review priorites for the week?
15:26:07 <arne_wiebalck> rpioso: I will check one more if we need anything for "historical reasons" :)
15:26:14 <arne_wiebalck> *once
15:26:28 <rpioso> arne_wiebalck: Thank you :-)
15:27:52 <arne_wiebalck> rloo: I updated on the DB loading patch, pls have  a look if that is what you had in mind
15:28:13 <rloo> arne_wiebalck: ++ on my list for today/soon :)
15:28:22 <arne_wiebalck> rloo: ty
15:29:07 <TheJulia> any objections to adding the anaconda deploy stuffs to the priority
15:29:33 <arne_wiebalck> sounds good!
15:33:19 <TheJulia> I've added a few items under new items
15:33:23 <TheJulia> Any objections to these?
15:33:47 <rpittau> should be fine
15:34:51 <TheJulia> Okay, I can add the tag to those
15:34:52 <openstackgerrit> Merged openstack/ironic-lib master: Explicit execute arguments  https://review.opendev.org/c/openstack/ironic-lib/+/777594
15:35:02 <TheJulia> Are we good to proceed?
15:35:05 <iurygregory> ++
15:35:10 <TheJulia> Next up would be Baremetal SIG
15:35:13 <rpittau> onwards!
15:35:24 <TheJulia> #topic Baremetal SIG
15:35:32 <TheJulia> arne_wiebalck: anything to note this week?
15:35:41 <arne_wiebalck> We have iurygregory next week on the "Ironic Prometheus Exporter"
15:35:44 <openstackgerrit> Merged openstack/python-ironicclient master: Add tests for 'baremetal port create' command  https://review.opendev.org/c/openstack/python-ironicclient/+/332880
15:35:51 <TheJulia> Awesome
15:36:06 <arne_wiebalck> And a discussion on PTG input from operators ... maybe :)
15:36:18 <TheJulia> Ohh, Interesting
15:36:29 <TheJulia> Have we started the twitter advertising campaign ?
15:36:44 <arne_wiebalck> I started with a mail today, no twitter yet.
15:36:52 <arne_wiebalck> Maybe we could also ask the foundation?
15:36:58 <TheJulia> okay, I need to dig up the operators group twitter tag
15:37:00 <TheJulia> ++
15:37:01 <iurygregory> without link for zoom in the tweet =)
15:37:06 <TheJulia> That is an awesome idea
15:37:12 <arne_wiebalck> The Large Deployment SIG moved to talks as we do.
15:37:12 <TheJulia> iurygregory: yeah, no tweeting zoom links :(
15:37:22 <TheJulia> I saw that, which they did tweet
15:37:24 <arne_wiebalck> They had 30 participants.
15:37:28 <TheJulia> NICE!
15:37:34 <iurygregory> awesome!
15:37:54 <arne_wiebalck> Quite a good outcome I think
15:38:02 <TheJulia> Well, I guess we can proceed to Open Discussion then :)
15:38:24 <TheJulia> https://twitter.com/osopsmeetup
15:39:01 <TheJulia> #topic Open Discussion
15:39:07 <TheJulia> So what things to discuss?
15:41:23 <rloo> how beautiful are crickets?
15:41:26 <rpittau> not a discussion topic (it could become one though), tinyipa ramdisk in ussuri is broken
15:42:39 <TheJulia> crickets are awesome... sometimes.
15:42:47 <TheJulia> How badly broken are we talking?
15:43:28 <rpittau> the image was rebuild and published using tinycore 11.1, which we don't support in ussuri because the CI is based on bionic (kernel too old)
15:43:38 <openstackgerrit> Merged openstack/sushy master: Initial support for secure boot databases  https://review.opendev.org/c/openstack/sushy/+/773397
15:44:28 <rpittau> that means all the jobs that somehow need to access the ramdisk with chroot won't work
15:44:41 <rpittau> for example ironic-standalone
15:44:46 <iurygregory> can't we pin the image we will use?
15:44:51 <iurygregory> O.o
15:44:52 <rpittau> iurygregory: we do already
15:45:00 <TheJulia> rpittau: because we're building the image?
15:45:07 <TheJulia> in those jobs, i.e. ironic-standalone?
15:45:23 <rpittau> funny enough, if we were building the image we would be fine
15:45:32 <iurygregory> woot?!
15:45:35 <rpittau> the problem is that we download the image and then we chroot into it to modify it
15:45:46 <rpittau> and we download the ussuri one that was rebuilt with 11.1
15:45:53 <TheJulia> rpittau: where do we modify it at?
15:46:06 <rpittau> https://945835ad432887103cff-08f6dc72eccd53018dd797f31cdfe820.ssl.cf1.rackcdn.com/777430/1/check/ironic-standalone/7ab00ea/job-output.txt
15:46:07 <JayF> rpittau: do we need to publish an updated ussuri ramdisk using master IPA-builder?
15:46:17 <rpittau> we access it to modify the configure ssh
15:46:41 <iurygregory> maybe we can ping the job to publish the image to an old IPA-builder...
15:46:49 <iurygregory> override-checkout
15:46:53 <rpittau> JayF: we should not use ipa-builder master, we pinned jobs to 2.2.0 but somehow it got published with something more recent
15:47:01 <iurygregory> O.o
15:47:04 <TheJulia> so that job is building it
15:47:08 <iurygregory> *magic*
15:47:22 <rpittau> what happened is that a change merged on the 28th
15:47:24 <JayF> ah understand, problem is in the other direction
15:47:28 <rpittau> and triggered a rebuild
15:47:40 * JayF wonders if new pip resolver made it not-respect our package limits
15:47:47 <rpittau> I'm not sure is on us to be honest
15:47:55 <TheJulia> oh
15:47:58 <TheJulia> it is adding an ssh key
15:47:59 <TheJulia> ugh
15:48:01 <rpittau> yeah
15:48:08 <TheJulia> Why do we need this?
15:49:07 <rpittau> it's to test if we can access the server, it's a tempest test if I'm not mistaken
15:49:23 <rpittau> but still, the problem is the image publishing with the wrong version
15:49:54 <iurygregory> ironic-python-agent-build-image-tinyipa will publish the image right?
15:50:15 <iurygregory> ops publish-openstack-python-branch-tarball
15:50:36 <rpittau> iurygregory: on our side we publish with ipa-builder
15:50:36 <TheJulia> Maybe instead of downloading, we just let the image build it completely for the job itself? At least to unblock the main ci for ussuri?
15:50:47 <TheJulia> Feels like this quickly becomes a chicken/egg problem
15:50:53 <rpittau> but there's an automated job that publish the images, I think it's on infra side
15:51:22 <iurygregory> on ipa we have     post:
15:51:22 <iurygregory> jobs:
15:51:22 <iurygregory> - ironic-python-agent-build-image-tinyipa
15:51:22 <iurygregory> - ironic-python-agent-build-image-dib-centos8
15:51:28 <JayF> I will echo the concern from rpittau that we not only fix CI; we fix the image for users who may be consuming built IPA images for Ussuri.
15:51:42 <rpittau> JayF: yeah, even if it's tinyipa
15:51:43 <TheJulia> JayF: agree
15:51:59 <JayF> It being TinyIPA is a good point... that actually makes me worry less about it
15:52:12 <JayF> honestly, other than for internal CI use, we'd probably be better off not publishing TinyIPA images at all
15:52:44 <rpittau> JayF: I think there's no choice :)
15:53:26 <TheJulia> Yeah, we need the images published because if we buitl every time we would have a higher failure rate due to some of the clouds due to elongated job times and connections initated.
15:55:18 <TheJulia> so basically we know the build did something wrong when it came time to publish
15:55:21 <rpittau> we can probably see if pinning on the build image jobs work
15:55:27 <TheJulia> but we don't know what exactly until we find the logs?
15:55:41 <JayF> I did want to make one request before open discussion shut down -- https://review.opendev.org/c/openstack/ironic-specs/+/777172 is a spec I've written about removing the need for conductor->IPA communication for the direct driver. I'd appreciate at least one non-VzM core to give it a look over if possible -- I'll be implementing this (downstream) over the next two weeks and would like to
15:55:43 <JayF> make sure what I build will be in the ballpark of an acceptable upstream design
15:55:59 <rpittau> the ipa jobs that iurygregory mentioned are related to master ipa-builder, so pinning them should work
15:56:08 <iurygregory> yep
15:56:24 <TheJulia> pinning on the stable branch correct?
15:56:28 <iurygregory> yes
15:56:31 <TheJulia> sounds like a plan then
15:56:38 <JayF> If master IPA-builder can't build a working image for ussuri, it makes me wonder if that needs to be a repo that starts getting branched like our others.
15:56:47 <TheJulia> sounds like somthing that needs to be double check-ed elsewhere, fwiw
15:56:50 <rpittau> on ipa-builder tag 2.2.0
15:57:03 <TheJulia> I thought we had to code to auto-checkout the right version on branches
15:57:21 <rpittau> not for ipa-builder
15:57:36 <TheJulia> JayF: added to the ironic-week-prio list
15:57:43 <JayF> TheJulia: Thanks!
15:58:38 <iurygregory> branches would be good, tag would also work (we probably need to have documentation with the versions...)
15:58:56 <TheJulia> iurygregory: well, there is central docs for that with releases
15:59:38 <iurygregory> I will try to take a look at it
16:00:04 <TheJulia> okay
16:02:06 <TheJulia> Okay, anything else to discuss today?
16:02:19 <rpittau> I have a patch ready to go for IPA ussuri to pin ipa-builder to 2.2.0, 2 minutes will be up
16:02:36 <iurygregory> rpittau, ack
16:02:42 <TheJulia> okay. Thanks everyone!
16:03:38 * iurygregory brb lunch time
16:04:03 <TheJulia> #endmeeting