15:00:16 #startmeeting ironic 15:00:16 Meeting started Mon Jun 27 15:00:16 2022 UTC and is due to finish in 60 minutes. The chair is iurygregory. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:16 The meeting name has been set to 'ironic' 15:00:22 o/ 15:00:24 Hello everyone o/ 15:00:25 o/ 15:00:27 \o 15:00:32 welcome to our weekly meeting :D 15:01:03 o/ 15:01:13 o/ 15:01:21 we don't have a big agenda, so it will probably be a quick meeting (and we don't have quorum it seems =) ) 15:01:41 you can find the agenda in the wiki 15:01:43 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 15:01:55 #topic Announcements / Reminder 15:02:13 #info ML thread - Thoughts on closing some branches 15:02:19 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-June/029274.html 15:02:50 today I've sent this email to the ML, feel free to provide feedback =) 15:02:56 sounds good to me 15:02:59 I 15:03:09 I'm planing in open the request next monday 15:03:16 k 15:03:21 if no objections on the ML 15:03:26 I may have patches that would need to be abandoned, that is fine 15:03:57 we can try to get them merged I would say I will make a list of open patches in all branches 15:04:11 not sure if CI will help (it will depend on the branch) 15:04:41 Does anyone have anything that would like to add to Announcements / Reminder ? 15:04:57 uhh 15:05:44 Likely worth mentioning we're having a lot of issues with CI. In particular emulated VM performance which we have some "fixes" for, as well as issues with NetworkManager on centos9 not honoring dhcp properly. 15:06:15 o/ 15:06:28 CI at least for master was in a better shape after your patches TheJulia (so I didn't mention) 15:06:59 re cs9 I wasn't aware of that, I will add to the etherpad in case is not there yet 15:07:27 iurygregory: go ahead and add it please 15:07:33 will do =) 15:07:33 it is the conenctivity issues from what I can tell 15:07:53 I'm trying to get more info out of it but all the tricks dont' seem to work, so I might have to reproduce locally or something 15:08:08 actually, I should just ask infra to hold a job 15:08:14 ack 15:08:26 * TheJulia will do that after the meeting 15:09:43 ok, moving on 15:10:24 we don't have action items, skipping 15:10:39 #topic Review subteam status reports 15:10:56 #link https://etherpad.opendev.org/p/IronicWhiteBoard 15:11:08 starting on L75 15:12:03 Merged openstack/ironic bugfix/20.2: CI: Add iweb to the use tinyipa on list https://review.opendev.org/c/openstack/ironic/+/847661 15:12:29 \o/ 15:13:01 *magic* 15:13:02 :D 15:15:15 not much to add in the status, I think we can move on 15:16:36 #topic Deciding on priorities for the coming week 15:16:47 #link https://review.opendev.org/q/status:open+hashtag:ironic-week-prio 15:17:12 I'd kind of like https://review.opendev.org/c/openstack/ironic-python-agent/+/839084 to get some eyes 15:17:28 but it is not high on my priority list (in other words, I just want to get it off my plate) 15:18:40 np from me 15:18:57 I've added some patches to fix CI in our bugfix/20.2 for ironic 15:19:10 iurygregory: ack 15:19:34 since we need to get jobs running on it 15:19:58 and we also need https://review.opendev.org/c/openstack/ironic/+/847657 15:20:07 hopefully CI will be happy :D 15:20:58 it's already a backport so I added to the list =) 15:22:04 anyone have more patches that needs review? I know we have some patches that needs attention already (but since CI was in a bad shape we had to fix it first) 15:22:47 I think I added a couple already 15:22:54 mainly Ci fixes 15:23:01 rpittau, tks! 15:23:30 oh yeah I will add one more as it's just missing approval https://review.opendev.org/c/openstack/ironic-python-agent/+/775391 15:24:02 done, thanks 15:24:43 fixed ;) 15:25:00 ok, moving on o/ 15:25:03 ah thanks! :) 15:25:07 #topic Baremetal SIG 15:25:20 arne is not around today 15:25:31 TheJulia, do you have something for the SIG? 15:25:47 I don't *really*, at least that I've not had a chance to talk with arne_wiebalck about 15:26:03 I migh thave a lead on a talk or three or this fall, maybe starting in August 15:26:20 nice =) 15:26:47 skipping RFE review since we don't have any in the agenda 15:26:53 #topic Open discussion 15:27:01 do we have something we would like to discuss? 15:27:08 I guess I have two items 15:27:20 go ahead =) 15:27:48 The first, with the RBAC work, there was the direction change from the TC on that admin is actually project scoped but system admin sort of level access 15:27:53 but we don't have that encoded in our policies 15:28:15 and I'm curious if anyone would object if we did that, *and* captured the project ID so all resources they create are inherently "owned" outright 15:28:33 its kind of another slice of access/usage, but could save us some headache 15:28:48 At least in the OpenStack context 15:29:48 any concerns/objections? 15:30:05 after reading "could save us some headache" I'm +1 to it 15:30:15 k 15:30:25 no objections, that does make sense IMHO 15:30:26 did they update the docs or something about this change in RBAC? 15:30:39 iurygregory: passed an updating resolution 15:30:44 after we did our work 15:30:52 TheJulia, got it 15:31:36 and since is a TC decision (only if we have very strong objections we wouldn't do that I would say...) 15:32:04 So, other thought which comes to mind. Have we considered kind of re-visioning our position in the OpenStack ecosystem? I'm starting to wonder if being at such a lower layer means we might be better suited to kind of "pull a zuul"... 15:32:21 ofc it will be good to hear the thoughts from operators etc (maybe arne_wiebalck since they are moving with RBAC if I recall) 15:32:23 iurygregory: well, tc decisions are basically non-binding, fwiw 15:32:47 they are recommendations with potential threat of non-compliance of being booted from openstack 15:33:32 Going back to vision, I guess it is time to revisit overall 15:34:26 re-vision ++ from, I was planning in write an email about this (since we will probably need to reach out our contributors ) 15:34:43 Re, the change, that is a good point, I wonder how it would impact arne_wiebalck’s environment 15:35:51 I think we should hold several discussions, say over the next two months to try and see where we have consensus as to where we’re at and where we’re going 15:36:01 ++ 15:37:16 probably bring up in the next meeting (see if we have more folks that would engage in the discussion) 15:37:33 ++ 15:37:34 and after that maybe start a thread in the openstack-discuss 15:38:11 ++ 15:38:13 sounds good to me 15:39:17 cool 15:40:22 I think that's all for open discussion right TheJulia ? 15:40:34 yup, all from me 15:40:41 ok o/ 15:41:04 #topic Who is going to run the next meeting? 15:41:34 Do we have any volunteer? 15:42:32 I will run the next meeting o/ 15:42:36 Thanks everyone! 15:42:51 #endmeeting