[09:39:40] what's up with the 'toolforge office hours' section of the next monthly meeting? didn't we agree when that came up some time ago that if we're doing that, it should be in a separate meeting? [09:41:08] it's about gathering some info on "is there interest on doing it?" not doing it right away [09:41:15] (as far as I understand the email) [09:41:44] that email is on cloud-announce, not on cloud-admin [09:42:08] yep, [09:42:30] I think the idea was to send a reminder to cloud-announce that the monthly meeting exists [09:43:34] (koml.a/aputhin might have more details on the intention) [09:43:34] why? [09:45:12] I'm not sure, I would welcome more community involvement from time to time though, not saying that the monthly is the best place, but better than nothing I guess [09:45:23] i mean, we've discussed this all relatively recently and ended up not doing that, so having that overturned in the only meeting in a while i'm not able to attend is a strange way to do it in my mind [09:46:57] what do you mean with "the only meeting in a while I'm not able to attend"? [09:49:12] it seems to have been discussed during https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Monthly_meeting/2026-06-30 when i was on holiday [09:53:26] oh yep, maybe we could have some more process around how to make those decisions to avoid missing input [09:57:22] your concern is that it's being asked again if it's useful to have the office hours? (hopefully with some community input) or that it was sent to cloud-announce that in the next monthly that would be discussed? [09:57:27] (or both, or none xd) [09:58:21] my concern is that i don't want to re-purpose the monthly meeting because it's so useful as is :) [09:59:36] (as in, everyone attending more or less has the big picture context of what's going on on the development side so we can get detailed there, but publishing its existence widely to those who don't already follow the development channels might change that) [10:01:16] I think that it was not the intention to change the meeting, but let's make sure (again) during the meeting and remind that if we do office hours, it should not affect the monthly [10:01:39] (that is, +1 from me on keeping them separated) [10:02:12] isn't the mail that just went on cloud-announce doing that already? [10:04:09] I don't interpret it like that, though now that you mention it I see how it can be. If we create the office hours (that I think would be good), we can always redirect users there, or irc/email for support and such [10:05:40] We should clarify though at the beginning of the next meeting what it is for and what it is not, just to make sure expectations are set [10:06:35] (and probably rephrase the wiki text to avoid any confusion and redirect people to the right channels) [10:26:02] wdyt about https://wikitech.wikimedia.org/w/index.php?title=Portal:Toolforge/Admin/Monthly_meeting&diff=prev&oldid=2439772 ? [10:49:32] Lgtm, though I would lean to keep the meet link there, I have no strong opinion [10:51:27] * dcaro lunch [10:52:49] fair enough, done [11:32:51] we're not repurposing anything and no decision was made. that's a "topic" for the monthly. it was raised on the last meeting as "are we interested in doing that?" and then we decided we don't have enough input from the community (since there's not enough of them attending the monthly when we discuss this) [11:34:43] the diff makes sense. +1 to clarify we're not holding office hours next week, just intend to discuss the possibility of establishing some [14:33:20] i am taking down metricsinfra-prometheus-2 and replacing it with a trixie instance, apologies in advance for any possible accidental alerts [14:39:52] ^ack (just saw the alerts) [15:15:27] fun side quest: cloudinfra internal puppetserver hadn't been updating for a while thanks to a permission issue due to a labs/private commit done as root, alerting was also broken so https://gerrit.wikimedia.org/r/c/operations/puppet/+/1313982 fixes it [15:16:09] might have been me? Didn't we have an alias or something for that? [15:16:22] `pgit` is the alias, yep [15:16:52] iirc there's a git hook that stops commit attempts, but even a `git add` can write in .git which is what probably happened here [15:16:54] and it's not setup to be git as an alias? [15:17:07] (as in, git being the alias for pgit) [15:18:12] not sure [15:18:51] I might be misremembering (maybe it was said, but not agreed or never done) [15:19:08] I regret ever thinking that it was a good idea to try to do this with a service user and not root. We've been chasing edge cases for years. [15:19:16] xd [15:19:26] sudo w! [15:34:09] ok, that's the new prometheus box online I think. apart from a few pontoon stacks that probably have their puppet rebases broken as usual it seems to be mostly able to reach everything [15:34:39] 🎉 [16:23:04] note to self: wmcs-prepare-cinder-volume takes a while to format a 100G volume [16:23:38] does it zero it out or something? [16:23:56] Discarding device blocks: 4718592/26214400 [16:23:57] i guess? [16:35:02] I did use it on a 4TB volume and I don't remember it taking _that_ long, but I don't remember exactly, maybe a couple minutes? I might misremember. [16:35:15] it was also a high-iops volume, not sure if it makes a difference [17:36:04] * dcaro off [17:36:06] cya tomorrow!