14:02:24 #startmeeting cloudkitty 14:02:24 Meeting started Mon Oct 13 14:02:24 2025 UTC and is due to finish in 60 minutes. The chair is rafaelweingartner. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:24 The meeting name has been set to 'cloudkitty' 14:02:30 Hello guys! 14:02:35 Roll count 14:02:39 \o 14:05:41 o/ 14:07:11 nice to see you here 14:10:17 Let's start 14:10:19 #topic vPTG 14:10:31 everything seems to be ready, room is booked, date is scheduled 14:10:44 I also already create an initial scratch for the etherpad 14:10:59 I will then amend with some more information about releases and information 14:12:34 Monday at 14UTC? 14:13:04 *Monday October 27* 14:13:11 yes 14:13:27 that is how we normally do it, in our usual meeting time, right? 14:13:35 Yes 14:15:38 is that timeslot fine? 14:15:42 or do we need some change? 14:15:57 as nobody mentioned anything before, I just maintained the usual that we use 14:16:24 It's OK for me for 30 minutes. I might need to leave after that but Matt should be around for one hour. 14:16:48 I see 14:16:52 I guess that would be fine 14:20:19 let's move on. If needed we can adjust the day and timeslot 14:20:21 let me know 14:21:22 #Target reviews 14:21:46 #link https://review.opendev.org/c/openstack/cloudkitty/+/963621, this one is an important one I guess 14:21:49 to fix our pipelines 14:21:55 can you guys review it 14:22:01 and approve if you think that one is fine to be merged 14:23:06 Done 14:23:58 awesome! 14:23:59 thanks 14:26:14 if everything is fine there, I guess we could merge it 14:27:15 Gerrit issue, my vote didn't post 14:27:27 Merging now 14:28:06 thanks! 14:28:46 then, we have this one #link https://review.opendev.org/c/openstack/cloudkitty/+/960374, which I also think we can merge 14:31:15 I executed a recheck in this one #link https://review.opendev.org/c/openstack/cloudkitty/+/950542 14:34:21 Just a note on recheck, the community has been asked to avoid "bare rechecks", i.e. rechecks without a reason 14:37:20 yes, but I just did it because the patch that is going to fix is going to be merged 14:38:02 you, now, we always should add a reson? 14:38:05 I mean, a written one? 14:38:12 that is my understanding 14:38:40 like recheck opendev.org 404 14:38:50 (just making something up) 14:39:09 it would help to group issues by reason 14:39:09 I don't always do a thorough investigation of the issue, but at least which job failed, and ideally why 14:39:33 I see 14:39:53 I will do that next time then 14:40:31 The request not to do bare rechecks comes up about once every year 14:40:55 :) 14:40:56 yes 14:40:57 I have see 14:41:00 seen* 14:44:20 Any thoughts on https://review.opendev.org/c/openstack/cloudkitty/+/961609 ? It helps spreading out requests to the loki storage, where the query window is smaller than 30 days, i.e. you can not search for data for a whole month 14:45:01 some deployments try to limit the search window to a couple of days or a week, which is of course problematic for cloudkitty 14:47:46 Left a comment to address 14:48:04 thank you! 14:48:14 Will get it addressed asap 14:48:44 thanks! 14:50:05 Then, #link https://review.opendev.org/c/openstack/cloudkitty/+/953827, it would be interesting to get some feedback here as well 14:52:32 Still not too keen on the eval(). I have to think about it. 14:52:51 ok 14:53:01 I wait for you to mature 14:53:09 but this is somethign common that we use in other systems 14:53:22 remember, it is a config on the server side done by the operator 14:55:35 Yes, I understand. 14:59:25 Do you guys have something else to add to the meeting? 14:59:38 we still have 10min, and the other patches I guess we can discuss in our next meeting 15:00:56 I have to leave for another meeting 15:03:25 ok 15:03:27 thanks! 15:04:00 thank you all for participating. Have a nice week! 15:04:07 #endmeeting 15:04:11 #endmeeting 15:04:18 #endmeeting