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