[04:16:04] <_joe_> Krenair: I wasn't aware, tbh [08:10:48] hmm that's our globalsign unified cert [08:18:55] <_joe_> yeah I wasn't aware it was OV [09:31:26] mutante: any eta on when puppet on icinga will be enabled [09:31:28] ? [09:36:56] jbond42: I'm tempted to add an sre.experimental. directory for new cookbooks so that it's clear they are not yet production ready because in development. Thoughts? [09:37:16] the reality is that the environment is too complex and in the end cookbooks have to be tested in real life [09:39:29] hi, does this look like a serious problem? https://logstash.wikimedia.org/app/kibana#/doc/logstash-*/logstash-deploy-2020.06.10/mediawiki?id=AXKdluadK6TSR36GW_OI&_g=h@44136fa (Cannot access the database: No working replica DB server: Unknown error (10.64.0.97)) [09:39:35] liw: it is fixed now [09:39:43] ah, that was fast. thank you [09:40:14] marostegui: 5 min [09:40:24] mutante: cool thanks [09:44:06] volans: fyi i do plan to test this before submiting, however i agree more testing will likle bee needed for this book so i think its a good idea. would you have epxperimental/sre/pdus or just experimental/pdus ? also in relation to this change i would need to merge then to another CR to move the files. I really don't want to rebase all this again :) [09:44:37] jbond42: I meant for the future [09:44:50] but yeah, when adding stuff also to the __init__ experimental becomes messy [09:45:10] marostegui: enabled... waiting for a puppet run .. [09:45:12] the other option is a flag that tells the uses a cookbook is still experimental [09:45:13] ahh ok in genral i think its a good idea [09:45:23] mutante: \o/ [09:45:24] maybe asking for confirmation [09:45:29] * volans just thinking out loud [09:46:09] marostegui: it just added checks for db1103 [09:46:21] mutante: excellent, thank you [09:46:28] i think having it under eperimental seems better as its more transparent and easier to notice in a review [09:50:51] jbond42: let me know when we can try to rotate the PDUs keys [10:00:08] XioNoX: i plan to do some testing today or tomorrw just to make sure i havn;t introduced any bugs since last i tested so assuming everything is successfull should be avalible next week [10:03:07] <_joe_> I'm sure the golang designers knew what they were doing, but can someone explain to me why loops in the language are in the form "for k,v := range Struct" and in templates they are "{{ range $k, $v := .Struct }}"? [10:03:18] <_joe_> completely not confusing when writing templates [10:10:25] sadly go templates are confusing, and terribly documented [10:11:28] <_joe_> s/y documented$/e/ [10:12:13] <_joe_> context is I wrote a full template only to realize after the fact I used the go syntax for ranges, more or less :P [10:12:20] ah, lovely [10:12:38] <_joe_> and ofc my eyes could not see the error [10:12:50] <_joe_> I had to go read the docs about the range "pipe" [10:12:57] <_joe_> (yes, those docs are bad) [10:14:17] bet the error message was really helpful, no? :D [10:14:41] <_joe_> too many declarations in command [10:15:05] <_joe_> absolutely helpful, actually, it told me I did mess something up with syntax [10:18:17] s/with syntax/by choosing to use go templates/ ? :) [10:18:44] i think that if someone could actually write good docs for it, it wouldn't be nearly so painful to use [10:19:02] (that wouldn't make it _good_, just.. usable) [10:23:14] <_joe_> kormat: given we're using helm, there isn't much of a choice, really [10:23:23] <_joe_> it's go text/templates to generate yaml files [10:23:31] <_joe_> What could possibly go wrong [10:24:06] is it too late to say "everything"? [10:25:15] <_joe_> depends, I'm so desperate to get away from yaml engineering I opened https://phabricator.wikimedia.org/T254739 [10:25:50] ahh, yes [10:26:05] kormat: https://i.imgflip.com/44mv4k.jpg [10:26:12] :D