[06:22:08] greetings [08:31:11] morning [09:01:59] I got these guys for review https://gerrit.wikimedia.org/r/c/operations/puppet/+/1332750 https://gerrit.wikimedia.org/r/c/operations/puppet/+/1332751 https://gerrit.wikimedia.org/r/c/operations/puppet/+/1331487 [09:02:09] volans you are exempt ! [09:17:47] <3 too kind of you [09:18:36] you are welcome, the least I can do [09:36:02] can I get a +1 on T435967? [09:36:02] T435967: Quota increase request for project wikispeech - https://phabricator.wikimedia.org/T435967 [09:36:54] and also T436605 [09:36:55] T436605: Quota increase request for project videowiki - https://phabricator.wikimedia.org/T436605 [09:49:57] looking [10:54:41] I'm interested in opinions on this toolforge quota request: T436614 [10:54:42] T436614: Request increased quota for wiki-economics Toolforge tool - https://phabricator.wikimedia.org/T436614 [10:55:42] I think that 16G is the current maximum we allow for pods, so that should be ok. And we don't really have quotas on NFS but we do have recommendations on storage use? [11:29:42] dhinus: no 16G will not schedule in practice [11:33:13] no worker will be practically be empty enough to schedule a pod that eats most of its resources [12:44:11] taavi: ack, I misremembered the value from previous conversation. I see we currently have one tool with "pod_memory: 12" in https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/blob/main/components/maintain-kubeusers/values/tools.yaml [12:46:40] the related task has some discussion on the fact that 12 is already likely to cause scheduling headaches [12:59:11] do we have any guidance for how much NFS storage use is considered acceptable for a tool? (the user above plans to use up to 400G) [13:05:53] we don't have strict guidance except that 400G is considered a lot [13:18:56] thanks, I can write something to that effect in the task. I replied in the task explaining that 16G is not going to work, let's see if they still want the other increases [13:27:00] ^ seems like they do, can anyone add a +1? we can suggest they stay under 200G NFS as that sounds like their real requirement [13:37:49] taavi: lol 'puppet-enc: Allow MEDIUMTEXT worth of Hiera' not on my bingo card [13:57:49] phab question: this T436616 looks like a ticket rather for the specific tool project instead of Toolforge the platform, but a tool project doesn't exist for Not-in-the-Other-Language. what do we usually do in this case? [13:57:50] T436616: Not-in-the-Other-Language fails because PagePileRenderer uses PHP 8.1 syntax on a PHP 7.4 consumer - https://phabricator.wikimedia.org/T436616 [13:58:19] I don't really wanna mark as invalid as to not "lose" track of the request, but I also don't think we can do anything ourselves AFAICT [14:19:34] aputhin: if that user wants to use phab to track tool-specific tasks they can create a tool-not-in-the-other-language tag. I would untag toolforge and tools-platform-team and add other maintainers as cc if there are any. [15:06:44] godog: wasn't on mine either before I went looking why I'm getting a 500 :D [15:07:02] haha! [15:10:18] andrewbogott: that's what I thought sounded like a good "intermediate point", thank you. I see now that I was beaten to the punch and the generic "Tools" project tag was added by someone instead of Toolforge [18:31:59] * dhinus off