[08:59:57] greetings [09:01:13] an update on the discord call we mentioned yesterday: we've been asked to not advertise outside of discord for this one, limiting our ability to reach active tool maintainers (we're not sure which ones are active on Discord) :( [09:03:01] as an alternative, so we still get a chance to present push-to-deploy and alerting system, we've thought of using the same presentation structure / discussion during our next monthly meeting - we would advertise it via IRC and cloud list [09:03:48] any concerns with using the monthly for this? we can also come up with an alternative ad-hoc google meet for the same purpose, but the monthly sounds like a established opportunity [09:17:16] aputhin: I still am not a huge fan of re-purposing the toolforge monthly from the current format which is designed for the people working on the platform itself [09:25:38] yeah I get that / remember that argument, which is what made me want to double check xD [09:26:01] part of me is concerned we haven't been able to use the monthly to full effect since it's mostly WMCS teams participating (at least since I joined, not sure how it was before) [09:27:31] we can also discuss a separate format / space to connect to tool maintainers. OTOH leveraging the monthly invites maintainers to get more involved on platform decisions [09:28:03] I don't have a strong opinion / push hear. would love input from everyone on the matter (missed the chance to discuss this on our weekly yesterday :D) [09:28:23] hear -> here* [09:33:49] tbh the attendee set was mostly similar beforehand. though before we had two separate teams and/or before we had attention from actual product people, that was the space where we actually planned and discussed what we wanted to do next and how we were going to do it. now those discussions seem to be happening somewhere in the internal meetings of [09:33:49] the two teams, I guess I am just partially missing the old status quo there :/ [10:24:08] I'm considering to disable tun/tap outside of ganeti* and cloudvirt* to reduce our attackable footprint: could anyone please check some time next week if anything in cloud VPS uses this and then update https://phabricator.wikimedia.org/T438459 ? [11:59:18] taavi: ^ would you be ok to audit tun/tap as part of clinic duty? if not that's fine too I'll take it [12:05:02] godog: d.caro is clinic duty as of yesterday, I guess the topic was not updated yet? [12:05:18] doh! my bad I didn't check the pad /o\ [12:05:50] ok I'll make a note to check next week [15:46:36] dhinus: fwiw T401715 is starting to be something that should be looked sooner than later, now that 7.4 is out of debian security support [15:46:36] T401715: Remove or replace "default" web service image - https://phabricator.wikimedia.org/T401715 [15:47:30] taavi: agree, I'll push it in the next tools-platform triage [15:48:45] thanks! [15:58:38] I saw the toolsdb alert only now, I'm not sure if it's mixnmatch again or another tool, I opened T438504 [15:58:38] T438504: [toolsdb] 2026-08-18 Transaction History Length growing too much - https://phabricator.wikimedia.org/T438504