15:00:05 #startmeeting ironic 15:00:05 Meeting started Mon Feb 13 15:00:05 2023 UTC and is due to finish in 60 minutes. The chair is iurygregory. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:05 The meeting name has been set to 'ironic' 15:00:07 JayF: sorry about that! 15:00:18 Hello everyone, welcome to our weekly meeting o/ 15:00:32 o/ 15:01:02 who is here today? o/ 15:01:04 o/ 15:01:13 o/ 15:01:42 #topic announcements/reminder 15:02:51 #info feel free to tag patches that need reviews with the hashtag ironic-week-prio 15:03:17 #info OIS Vancouver 2023 Schedule is out! 15:03:26 #link https://vancouver2023.openinfra.dev/a/schedule 15:03:42 No results about the Forum sessions yet 15:04:12 this is all I have for announcements/reminder, does anyone have something that would like to add to it? 15:05:15 ok, moving on 15:05:37 no action items from previous meeting, skipping 15:05:49 #topic Review Ironic CI status & update whiteboard if needed 15:06:15 Did anyone notice something regarding CI that would like to provide an update? 15:07:10 I think it's been smooth 15:07:18 I've had several clean runs for my API changes on master 15:07:31 o/ 15:07:33 I think there might be a few older branches still flakey, but things are pretty good 15:08:15 nothing to report 15:08:26 ack, tks JayF rpittau 15:08:55 #topic 2023.1 Work in progress 15:09:10 #link https://etherpad.opendev.org/p/IronicWorkstreams2023.1 15:09:28 I need to rev the metrics stuff today 15:09:52 sharding is close, I'll get another revision in this morn 15:10:06 reviewing it now 15:10:20 metal3 ci integration is slowly moving forward, but nothing exceptional :/ 15:12:10 I don't think kubajj or dtantsur are around for us to get an update regarding Merging inspector into ironic, but I know there was good progress on it, and saw some updates in patches today 15:12:33 so we should be fine, moving on? 15:12:43 o/ 15:13:24 The first step (adding the inventory API) is almost done. There are just minor follow ups to finish. 15:13:34 awesome 15:13:38 cool! 15:13:46 tks for the update kubajj o/ 15:14:28 no items in RFE review, so skipping 15:14:39 #topic VirtualPDU update 15:15:35 rpittau, any updates you would like to share? 15:15:45 not good ones 15:15:55 * iurygregory hides 15:15:58 rutro 15:16:10 still no news for the patch or the adoption yet 15:16:18 I sent a mail one week ago 15:16:24 going to bump that duringthis week 15:16:55 =( 15:17:55 let us know if there is something we can help with 15:18:23 yesh, thanks, will do 15:18:31 #topic Open discussion 15:18:47 anything we would like to discuss today? 15:19:44 So, we're really, really close to the release. 15:19:50 So I'm curious if anyone would be interested in being able to disable or select focus areas of metrics 15:19:52 If we were an RC-using project, we'd be cutting that soon 15:20:16 ok we have two topics lol 15:20:24 TheJulia: like "application" vs "hardware" metrics? Or something more generic e.g. "all outgoing metric keys must match this regexp" 15:20:36 JayF: I was thinking hardware specifically 15:20:48 Do we know what week is final releases -1 ? 15:21:12 release date is 3/22 15:21:21 R-1 3/13-17 15:21:30 So we have almost exactly a month 15:21:45 Mar 13 - Mar 17 R-1 Final RCs and intermediary releases 15:22:06 3-ish weeks, we will need to release early that week at the latest 15:22:08 Feb 27 - Mar 03 - RC1 15:22:23 We generally don't cut RCs 15:22:23 since at the end of the week they won't actually push the button 15:22:29 right? 15:22:46 let me say, our releases-profile (cycle-with-intermediary) says we don't use RCs 15:23:01 JayF, no we don't cut RC, but this two are normally when we release the stable/ 15:23:13 it is when the angry emails start 15:23:16 ah 15:23:37 and the attempts to force us into doing RC releases if it plays out like it typically does 15:23:42 and when we will get emails with "hey you haven't done a release for x y z" 15:23:42 So I'll say, next meeting, lets make some time and see what's getting in/what isn't 15:23:43 :D 15:23:47 and everyone push to complete their items 15:24:04 I'm especially thinking about the metal3 CI job + autocommit revert 15:24:12 if we miss that this cycle it'll be a huge disappointment IMO 15:24:26 given how far ahead of the curve we already are on sqla2 15:24:27 JayF: you can't imagine how disappointing it is for me :) 15:24:56 rpittau: idk, my imagination is super good at imagining horrible things :| 15:25:00 yeah, which reminds me, I never got an answer from the oslo folk on the error we see :( 15:25:14 there aren't many oslo folk :( 15:25:18 true 15:25:20 might wanna take it to the list? 15:26:21 TheJulia: your metrics question; I think it's useful and interesting 15:26:34 TheJulia: you thinking of trying to sneak that in with the rest of the prom support this cycle? 15:26:48 dunno 15:26:53 my plate feels super full 15:27:36 Makes sense; was just curious 15:27:38 it would be interesting to select if you want metrics of given nodes (like a flag that would provide or not the sensor data) even if is enabled in the conf 15:27:56 That actually makes snese 15:28:04 to just add in the conditional 15:28:04 my main question is, more or less 15:28:13 with the changes we have in place now, prom metrics users get app metrics, right? 15:28:14 regarding selecting "focus areas" are you talking about "I just want fan metrics" 15:28:20 or just "power" ? 15:28:29 can people using prom for hardware metrics opt-out of the new app support or not? 15:28:31 the operator could just choose? 15:28:54 iurygregory: power, there is a push to expose power to end users in some threads of discussion, albeit somewhat abstracted away from the hardware. 15:29:25 JayF: it is all together right now, which means making it selectable/controllable at a high level JustMakesSense^TM 15:29:39 ++ agree 15:29:52 Yeah; I'm mainly wondering if there's an easy "app metrics on/off" toggle we could slip in this cycle 15:30:00 as to not annoy those opers who want hardware but not app metrics 15:30:10 but I mean, metrics are cheap, they can deal with it? lol 15:30:12 likely, since I need to rev the code as it is still wip 15:30:28 * TheJulia glares at the specs repo 15:34:13 dtantsur: reason for no test on https://review.opendev.org/c/openstack/ironic/+/872658 is there is no existing testing of it, it is all mocked out so it would be entirely net new testing, and it wasn't looking like a easy lift when I was looking at it. I can try to look again later this week. 15:34:25 metrics are cheap <- depends on the config they are using XD 15:34:44 dtantsur: btw, I think your right on your second comment, the first I don't think makes much sense given there is no other way for it to transition 15:34:47 iurygregory: I assume that any sane metrics system should make it easyish to filter metrics downstream :) 15:35:03 We're in the age of not understanding the cost or substrate 15:35:16 JUST THROW SOME HARDWARE AT IT /s :D 15:35:17 so..... our definition of sane might not be the same as others 15:35:30 * TheJulia suddenly sees MetricsCloud deployed 15:35:41 * TheJulia sees racks and racks get wheeled into the cluster 15:36:04 Suddenly, it becomes conscious through sheet local gravity 15:37:45 are we good with open discussion? 15:37:53 seems like it :D 15:38:02 ok 15:38:08 thanks everyone! o/ 15:38:20 #endmeeting