[05:06:04] 10serviceops, 10Parsoid, 10Patch-For-Review: equivalent of scandium on buster? - https://phabricator.wikimedia.org/T268248 (10Dzahn) @jijiki @hnowlan @RLazarus Here's the summary. There is `scandium.eqiad.wmnet` which is a Parsoid test server that is like an appserver and on stretch. And then there is `tes... [05:08:49] 10serviceops, 10Parsoid, 10Patch-For-Review: equivalent of scandium on buster? - https://phabricator.wikimedia.org/T268248 (10Dzahn) This ticket should have a better title but the point is it is about scandium and testreduce and not about the prod parsoid appservers and upgrading them. That should be another... [05:11:23] 10serviceops, 10Parsoid, 10Patch-For-Review: equivalent of scandium on buster? (upgrading parsoid testing servers) - https://phabricator.wikimedia.org/T268248 (10Dzahn) [05:11:57] 10serviceops, 10Parsoid, 10Patch-For-Review: equivalent of scandium on buster? (upgrading parsoid testing servers) - https://phabricator.wikimedia.org/T268248 (10Dzahn) [05:12:01] 10serviceops, 10Operations, 10Release-Engineering-Team-TODO, 10Patch-For-Review, 10Release-Engineering-Team (Deployment services): Upgrade MediaWiki appservers to Debian Buster (debian 10) - https://phabricator.wikimedia.org/T245757 (10Dzahn) [09:48:58] 10serviceops, 10Graphoid, 10Operations, 10MW-1.35-notes (1.35.0-wmf.34; 2020-05-26), 10Platform Engineering (Icebox): Undeploy graphoid - https://phabricator.wikimedia.org/T242855 (10hashar) What is the status of the decommissioning of #graphoid ? The reason I ask is that CI still has to maintain images... [10:48:50] 10serviceops, 10Graphoid, 10Operations, 10MW-1.35-notes (1.35.0-wmf.34; 2020-05-26), 10Platform Engineering (Icebox): Undeploy graphoid - https://phabricator.wikimedia.org/T242855 (10akosiaris) >>! In T242855#6636185, @hashar wrote: > What is the status of the decommissioning of #graphoid ? As far as I... [10:49:49] akosiaris: merci! :] [10:52:07] hashar: de rien! [11:04:33] o/ Hey all! At the last tech conf (or whatever) I talked with one of you about wmde / wikibase having a namespace in the main docker registry. Few questions 1) is that still okay? 2) what are the requirements for images that are there? [11:04:56] I remember at the time I was told that we could bu things there that didn't necessarily use the wmf base images, does that still hold true? [11:05:20] And are there requirements for where these images are built, like, must be WMF CI? or can we be more flexible in our own namespace? [11:28:00] * apergos peeks in, interested in the answers also [11:31:15] not a 100%, but my understanding is that (with very rare exceptions) we want to only allow images build ourselves to be pushed to the registry [11:33:11] Is there some list of / documented reasons for that and also notes on the restrictions? [11:33:33] If they are too much we will likely just end up using some other docker registry [11:36:11] Not that I know of, sorry. My reasoning comes from the fact that we try to limit what is allowed to be run in the kubernetes clusters by only allowing docker images from our registry to be run...but that ofc. would also include CI images etc. so that might be more like a weak limitation [11:36:35] akosiaris can maybe shed some light if there are some hard rules... [11:46:57] Indeed and I 100% agree that you shouldnt run these images in prod k8s clusters :) from my vauge memory that is what the namespaces may have been useful for [11:47:00] 10serviceops, 10MW-on-K8s, 10Operations, 10TechCom-RFC, and 2 others: RFC: PHP microservice for containerized shell execution - https://phabricator.wikimedia.org/T260330 (10dr0ptp4kt) @tstarling, I was wondering if you could please weigh in on my questions above? In the context of Wikifunctions one though... [11:47:14] yes, this is mostly the same case as releng images, that we shouldnt run in prod [12:02:42] 10serviceops, 10Operations, 10Performance-Team, 10Patch-For-Review, and 2 others: Reduce read pressure on mc* servers by adding a machine-local Memcached instance (on-host memcached) - https://phabricator.wikimedia.org/T244340 (10Addshore) > Some keys are super hot - take for instance `WANCache:v:global:Ca... [12:04:35] indeed, but I don't think we're currently limiting any furter that "allow just our registry" [12:05:29] Is the best place for this to continue a phab ticket? (perhaps I'll wait until the end of the day and see if other people want to chime in here otherwise make one) [12:08:26] 10serviceops, 10Performance-Team, 10User-jijiki: Run latest Thumbor on Docker with Buster + Python 3 - https://phabricator.wikimedia.org/T267327 (10Aklapper) [12:08:28] A task would be good to keep the discussion more permanent in any case! [12:09:38] Feeld like we should def. come up with something to write down at the end :) [12:10:34] *feels [12:18:53] * addshore will defintly copy the logs to the phab ticket nonetheless [12:21:59] thanks! [12:55:13] We have the same set of questions about releases.wikimedia.org too, are there guidelines on what can and can't be there? [12:55:20] or is that in someone elses realm? [12:57:51] addshore: I don't have a recollection of that discussion tbh, maybe you had it with Giuseppe. That being said, if there is a sufficient good reason we could discuss it. But no we don't have guidelines cause it was never designed to be service for anyone else. Even releng images are essentially piggybacking on it without a guideline or anything [12:58:01] regarding releases you want release engineering :-) [13:07:52] I definitely remember Giuseppe being in the room, I dont recall who else, I may even be able to dig up some notes :P [13:11:23] I think it was in or around this session https://phabricator.wikimedia.org/T234644#5661914 but I dont see anything in the notes [15:07:36] 10serviceops, 10Release-Engineering-Team, 10Security, 10cloud-services-team (Kanban): Implement SSH CA (certificate authority) for host keys? - https://phabricator.wikimedia.org/T268344 (10LarsWirzenius) [15:14:50] 10serviceops, 10Operations, 10Traffic, 10Patch-For-Review, 10Platform Team Workboards (Green): MW REST API should be routed to api_appserver MW cluster - https://phabricator.wikimedia.org/T268043 (10herron) p:05Triage→03Medium [23:45:16] 10serviceops, 10Operations, 10Release-Engineering-Team-TODO, 10Patch-For-Review, 10Release-Engineering-Team (Deployment services): Upgrade MediaWiki appservers to Debian Buster (debian 10) - https://phabricator.wikimedia.org/T245757 (10Dzahn) [23:47:55] 10serviceops, 10Operations, 10Release-Engineering-Team-TODO, 10Patch-For-Review, 10Release-Engineering-Team (Deployment services): Upgrade MediaWiki appservers to Debian Buster (debian 10) - https://phabricator.wikimedia.org/T245757 (10Dzahn) [23:49:35] 10serviceops, 10Operations, 10Release-Engineering-Team-TODO, 10Patch-For-Review, 10Release-Engineering-Team (Deployment services): Upgrade MediaWiki appservers to Debian Buster (debian 10) - https://phabricator.wikimedia.org/T245757 (10Dzahn)