15:00:06 #startmeeting ironic 15:00:06 Meeting started Mon Sep 13 15:00:06 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:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:06 The meeting name has been set to 'ironic' 15:00:11 o/ 15:00:11 o/ 15:00:17 o/ 15:00:33 o/ 15:00:36 o/ 15:01:00 Hello everyone, welcome to our weekly meeting 15:01:00 o/ 15:01:02 o/ 15:01:11 o/ 15:01:21 seems like we have enough people so let's get started :D 15:01:29 #topic Announcements/Reminders 15:01:59 #info This week is the R-3 week - we have RC1 for all projects with release-model cycle-with-rc under the ironic 15:02:11 o/ 15:02:34 #info Yoga PTG is in 5 weeks! Don't forget to register and add topics in our etherpad! 15:02:42 #link https://www.eventbrite.com/e/project-teams-gathering-october-2021-tickets-161235669227 15:02:57 #link https://etherpad.opendev.org/p/ironic-yoga-ptg 15:03:49 Does anyone have something to add to our Announcements/Reminders? =) 15:04:42 iurygregory: I guess we need to try and release end of this week or at the latest sometime next week. 15:05:14 Since we typically trail a little after RC1 release as often we devstack changes which can break us at times. 15:05:56 TheJulia, agree, I would say that depending on the project we can wait till next week 15:06:12 sooner obviously better, of course 15:06:45 yeah for most of the projects I think we are in a good shape, ipa-builder we will be able to release this week, we need to take a look at ironic and inspector 15:07:48 moving on 15:08:00 #topic Review action items from previous meeting 15:08:15 skipping since we don't have any Action Item 15:08:26 #topic Review subteam status reports 15:08:33 starting on L60 15:08:55 url? :) 15:09:02 #link https://etherpad.opendev.org/p/IronicWhiteBoard 15:09:12 sorry =) 15:09:17 no worries 15:09:36 I'm going to note db performance done 15:10:00 makes sense to me 15:10:01 I've noticed our periodics are becoming less... efficent, and Dmitry and I chatted about this some last week but it will be a longer term better solution 15:11:35 do we have some data that confirms that is becoming less efficient? (just wondering) =) 15:11:48 knowledge of hundreds of needless extra db queries 15:11:52 based upon the pattern 15:11:57 got it 15:12:32 For example, if we request driver_internal_info from nodes_iter, and then pull a task before making a decision based on d_i_info, then we've triggered more db queries needlessly 15:12:42 when d_i_i had the answer all along 15:12:53 I may look around and try to fix those this week 15:13:02 * TheJulia notes node history 15:13:27 got it, yeah if we have the information handy we don't need to go to the db... 15:15:06 Updated the node event history stuffs 15:15:09 with links! 15:15:15 links++\ 15:15:54 TheJulia: I will replace my name with yours for this item :) 15:16:13 arne_wiebalck: okay :) 15:16:23 or just add TheJulia =) 15:16:46 arne_wiebalck: please feel free to review. I got nobodycam to skim the periodic logic and he +1'ed it based upon his use case and also incorporated his feedback 15:17:03 TheJulia: ok, I will! 15:17:41 are we good to proceed? 15:17:48 yes 15:18:14 #topic Deciding on priorities for the coming week 15:18:19 #link https://review.opendev.org/q/status:open+hashtag:ironic-week-prio 15:18:53 I'd like to get reviews on the events patches this week, it would be a good item to get out there and people can at least use it as soon as the client is out early next cycle 15:18:56 Can these be added to priorities - https://review.opendev.org/c/openstack/ironic/+/808098 https://review.opendev.org/c/openstack/ironic/+/805431 https://review.opendev.org/c/openstack/ironic/+/805428 15:19:06 given that release is close and 2 of them have been open for a while 15:19:40 ajya, ++ make sense to add them I would say 15:20:04 TheJulia, I didn't see any patches for events (maybe I missed) 15:20:21 but I does sound like something we should try to include 15:20:50 iurygregory: node history 15:21:04 oh ok, related to node history! 15:21:15 adding 15:21:28 added 15:22:03 ajya, I think we probably want to backport https://review.opendev.org/c/openstack/ironic/+/805428 right? 15:22:16 can you add a releasenote? 15:22:46 https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/808198 would also be good to land this week 15:23:16 iurygregory: yes to backport and releasenote 15:23:24 TheJulia, ++ I will take a look 15:25:12 hmmm https://review.opendev.org/c/openstack/networking-generic-switch/+/763794 is tagged as a wip 15:25:22 * TheJulia wonders if it is not really 15:25:28 of course, it has also missed the release 15:25:53 TheJulia, well we can hold a bit the ngs release (but we need to do this week) 15:26:24 * iurygregory wondering why the patch is marked as WIP... 15:26:25 oh yeah 15:26:30 it hasn't released yet 15:26:37 that we need to go ahead and get sorted this week 15:26:50 yup, we can still hold ngs, networking-baremetal 15:27:05 yup 15:27:18 it has only had very minor changes since the last release 15:27:25 being networking-baremetal 15:28:31 exactly 15:29:37 later today I will take a look at the non-tagged in patches in our projects and see if there is something we want to include 15:29:48 ++ 15:29:53 should we move on? 15:29:55 yes 15:30:06 #topic Discussion 15:30:25 I have a topic, but I forgot to add to our agenda 15:30:42 Okay 15:31:08 I was talking with the release team since we need the RC for some of our deliverables 15:31:22 should be the neutron tied ones 15:31:54 we have projects like IPE and ironic-ui (that doesn't get a lot of changes) and we are using cycle-with-rc 15:32:14 Because the release team wants to cut a new release regardless of if it changes. 15:32:25 which... artificially increases the version 15:32:27 sadly 15:32:41 What are they proposing? 15:32:46 yes, but they will cut with the major bump, I don't think it makes sense... 15:33:38 Yeah... That has been a point of contention in the past. 15:34:00 yup, I noticed that they asked for the change to RC 15:34:07 https://opendev.org/openstack/releases/commit/7ac3b50659a225846831fec978ecc89041ee459e 15:34:51 for the end user perspective if they check the version they will think we added a bunch of new things that required a Major bump.. 15:34:53 OpenStack's All or Nothing model is *largely* driven to help drive market forces and new versions are part of that, but at the same time they are supposed to also pull in the last release or the next appropriate release. 15:35:15 however, that has changed such where they require a release to be pulled in during a cycle 15:35:26 iurygregory: exactly 15:35:46 iurygregory: and even if we had a release note to the contrary, the perception has been set. 15:35:54 yup! 15:36:19 oh we added this small feature, there is no breaking change in our API (major bump \o/) 15:37:16 yup 15:37:32 As I said, it is really driven to try and play the market with "new version" 15:37:37 so I think we probably need to try to evaluate our projects to cycle-with-intermediary, or maybe see with the release team if we can have a new model (not sure) 15:37:42 Verification of a change to openstack/ironic-inspector master failed: Update parameters for authtoken middleware https://review.opendev.org/c/openstack/ironic-inspector/+/805443 15:37:55 iurygregory: It could be good to discuss 15:38:33 iurygregory: perhaps a ptg session with the release team. I'm sure largely they are driven by the "this is the way it has been documented", and that can be changed if they are willing 15:38:50 TheJulia, yeah I was thinking about that 15:39:05 I will talk with Herve about this 15:39:19 Okay, let me know if there is any way I can help 15:40:00 #action iurygregory to talk with Herve about changing the release of some ironic projects 15:40:05 TheJulia, sure! tks 15:40:19 that's it from my side 15:40:33 onward? 15:40:46 #topic Baremetal SIG 15:40:52 #link https://etherpad.opendev.org/p/bare-metal-sig 15:41:05 arne_wiebalck, do you have something for the Baremetal SIG ? 15:41:07 Lively ops/feedback discussion last week. 15:41:30 There were suggestions to have a 2nd one as we did not really finish. 15:41:51 second one would be good 15:41:51 Maybe it is a good idea to have another one right before the PTG? 15:42:04 I know two firms that just had stuff come up and couldn't make it 15:42:08 arne_wiebalck: ++ 15:42:13 ++ 15:42:13 oh, ok! 15:42:19 How do we find a slot? 15:42:30 Also for TheJulia to join :) 15:42:44 TheJulia: you have a permanent clash with the slot? 15:42:55 arne_wiebalck: yes, OSF board meetings 15:43:05 err 15:43:06 OIF 15:43:13 TheJulia: they picked our slot? :-D 15:43:23 I also know I friend that couldn't join because it was holiday in Brazil 15:43:37 arne_wiebalck: it has always been their slot, just... not every month and sometimes shifted time zone wise. This year threw a wrench into things as we were not able to do in-person 15:44:09 I think maybe a little later would help, at least from some of the feedback from west-coast US operators was that it was just really early for most of them 15:44:32 later, but same day of the week? 15:44:49 could be good 15:45:00 would 2 hrs later be good enough? 15:45:09 yes 15:45:14 that is still acceptable in Europe, I think 15:45:28 well, some of Europe at least 15:45:43 time zones are hard :( 15:45:58 ok, let's try, I will schedule one and we pick up the usual short tutorials after, soounds ok? 15:46:15 ++ 15:46:20 arne_wiebalck, thanks! 15:46:33 cool, that's it from the SIG I believe 15:47:02 #topic RFE review 15:47:08 no topics so skipping 15:47:15 #topic Open discussion 15:48:07 Anyone have anything for our open discussion? 15:49:26 I've got nothing 15:49:34 arne_wiebalck: that sounds good to me 15:49:46 i will be submitting a spec for review soon (once i can figure out how to do so) 15:49:58 I expect we should review jam attestation tomorrow 15:50:15 it's for the redfish power control intermediary 15:50:15 sam_z, feel free to ask here and we can try to help you =) 15:50:24 sam_z: awesome 15:50:29 will do! 15:50:36 TheJulia, ++ for review jam tomorrow 15:50:51 I can drive the jams 15:51:18 I can join without problems I think 15:51:36 so lets go for our last topic 15:51:43 #topic Who is going to run the next meeting? 15:51:57 Do we have any volunteers? 15:53:13 ok, I will run the meeting next week =) 15:53:23 Thanks everyone! 15:53:27 #endmeeting