[00:42:07] 10serviceops, 10Release Pipeline (Blubber), 10Release-Engineering-Team (Backlog): Base Blubber policy file for CI - https://phabricator.wikimedia.org/T215319 (10greg) [00:43:15] 10serviceops, 10DBA, 10Phabricator, 10Release-Engineering-Team (Backlog), and 2 others: Improve privilege separation for phabricator's config files and mysql credentials - https://phabricator.wikimedia.org/T146055 (10greg) [07:41:23] 10serviceops, 10Citoid: JSTOR is blocking citoid IPs - https://phabricator.wikimedia.org/T216456 (10Joe) @Mvolz this means we can reconfigure citoid to use both proxies? [09:13:06] how to make the "notes_url" parameter of monitoring::service (and related classes) required for all new code that is being added, without having to set it for all existing code at the same time [09:13:30] or should i just start adding it to all existing checks and then it can become required [09:16:14] <_joe_> mutante: I fear the best way to do what you want [09:16:27] <_joe_> is to add a check in our puppet-lint plugins [09:16:44] do i figure out how to make jenkins-bot vote -1 if a certain parameter is not set? [09:16:47] ah, yea [09:18:16] or i could add a default URL to all existing code.. a wikitech page that says "fix me" :P [09:19:47] <_joe_> lol, I don't think that's a great idea [09:20:36] <_joe_> but maybe less effort [09:32:44] uhm.. fatal: remote error: operations/puppet-lint-wmf_styleguide-check unavailable [09:33:02] that's what i should read though, right. that is referenced in Gemfile [09:41:31] _joe_: where do i clone the puppet-lint-wmf_styleguide-check ? is that unexpected that it's "fatal.. not available"? [09:41:41] or my typo in the name.. hmm [09:41:55] <_joe_> mutante: adding that check will not be trivial at all [09:42:07] hmm, ok [09:42:14] <_joe_> i just realized we never went to do such a check and it's a nightmare to do [09:42:41] <_joe_> a tragedy of parsing puppet-lint tokens [09:42:47] <_joe_> so, go the other way :P [09:42:49] ok, i will consider the alternatives then and start to add URLs to existing code to start [09:42:56] alright. tx [09:43:17] <_joe_> we can later add a check for that specific url [10:49:50] i will use Phabricator workboard URLs as notes_url where it matches and i don't have a better one. Works for quite a few misc things [12:26:33] 10serviceops, 10Core Platform Team (Multi-DC (TEC1)), 10Core Platform Team Backlog (Next), 10Kubernetes, and 2 others: Deployment strategy for the session storage application. - https://phabricator.wikimedia.org/T217650 (10Joe) p:05Triage→03Normal [12:28:17] 10serviceops, 10Core Platform Team (Multi-DC (TEC1)), 10Core Platform Team Backlog (Next), 10Kubernetes, and 2 others: Deployment strategy for the session storage application. - https://phabricator.wikimedia.org/T217650 (10Joe) a:05Eevans→03None [12:29:52] 10serviceops, 10Core Platform Team (Multi-DC (TEC1)), 10Core Platform Team Backlog (Next), 10Kubernetes, and 2 others: Deployment strategy for the session storage application. - https://phabricator.wikimedia.org/T217650 (10akosiaris) a:03Eevans [12:32:15] 10serviceops, 10TechCom-RFC: RfC: Standards for external services in the Wikimedia infrastructure. - https://phabricator.wikimedia.org/T208524 (10Joe) [12:32:21] 10serviceops, 10Core Platform Team (Multi-DC (TEC1)), 10Core Platform Team Backlog (Next), 10Kubernetes, and 2 others: Deployment strategy for the session storage application. - https://phabricator.wikimedia.org/T217650 (10akosiaris) Definitely the 2nd as far as I am concerned. * we add a more generic "pr... [12:32:47] 10serviceops, 10TechCom-RFC: RfC: Standards for external services in the Wikimedia infrastructure. - https://phabricator.wikimedia.org/T208524 (10Joe) >>! In T208524#4987398, @jijiki wrote: >> **Production deployment** >> >> Have backups if the service stores any data > > May be we could add "and a res... [12:40:20] 10serviceops, 10TechCom-RFC: RfC: Standards for external services in the Wikimedia infrastructure. - https://phabricator.wikimedia.org/T208524 (10Joe) [12:42:03] 10serviceops, 10TechCom-RFC: RfC: Standards for external services in the Wikimedia infrastructure. - https://phabricator.wikimedia.org/T208524 (10Joe) >>! In T208524#4987487, @akosiaris wrote: > I would suggest the following change of wording to 2 different sentences > > * Be able to perform requests to a sp... [14:32:46] 10serviceops, 10Scap, 10Patch-For-Review, 10Release-Engineering-Team (Kanban): Scap: server_groups regression - https://phabricator.wikimedia.org/T217597 (10Joe) [14:32:49] 10serviceops, 10Scap, 10Release-Engineering-Team (Kanban): Deploy scap 3.9.2-1 - https://phabricator.wikimedia.org/T217611 (10Joe) 05Open→03Resolved [14:34:24] !log Rump up citoid traffic from k8s to 25% on codfw - T213194 [14:34:33] FFS [14:36:36] akosiaris: you ok if I --set resources.replicas=20 ? [14:37:06] <_joe_> ottomata: why do you need 20 replicas? [14:37:16] https://phabricator.wikimedia.org/T214080#4999866 [14:37:24] ottomata: nope. I am ok though if you change it in the /srv/scap-helm/eventgate/eventgate-analytics-{eqiad,codfw}-values.yaml files and apply that with -f :P [14:37:30] Ah great. [14:37:47] _joe_: it makes sense for the amount of req/s [14:37:49] <_joe_> ottomata: oh so you're using eventgate! [14:38:02] <_joe_> akosiaris: yeah that's what I wanted to understand [14:38:13] that's the quarter goal! its working in beta now (with your cool docker::service too) handling api-request events [14:38:36] (btw, I might make a yq .deb someday soon, would be nice to scap-helm ... get | yq .resources [14:39:14] <_joe_> ottomata: you realize you have root and you can build and upload such a package, right? [14:39:15] <_joe_> :D [14:39:25] exactly "I" might... [14:39:32] :) [14:39:44] <_joe_> yeah, I meant, jfdi [14:40:17] <_joe_> did they preserve the ugly syntax from jq? [14:40:19] indeed! right after I jfdallthatotherstufftoo! [14:40:23] ya its just a wrapper [14:55:23] niiiice! 20 replicas looking good. I could make a single ab -c1000 do around 6375 msgs/sec, then was limited by single node ab. [15:54:06] 10serviceops, 10Scap, 10Patch-For-Review, 10Release-Engineering-Team (Kanban): Scap: server_groups regression - https://phabricator.wikimedia.org/T217597 (10thcipriani) 05Open→03Resolved Now that 3.9.2-1 is everywhere, this should be resolved. [17:27:01] 10serviceops, 10Core Platform Team (Multi-DC (TEC1)), 10Core Platform Team Backlog (Next), 10Kubernetes, and 2 others: Deployment strategy for the session storage application. - https://phabricator.wikimedia.org/T217650 (10Eevans) For my part, I'm Good with either approach; I really like the idea of not ha...