2017-12-05T00:03:53 *** cboltz has quit IRC 2017-12-05T00:26:11 *** Son_Goku has quit IRC 2017-12-05T00:29:13 *** Son_Goku has joined #opensuse-admin 2017-12-05T00:30:06 *** Son_Goku has quit IRC 2017-12-05T00:37:42 *** jdsn has quit IRC 2017-12-05T00:38:10 *** jdsn has joined #opensuse-admin 2017-12-05T00:39:19 *** Son_Goku has joined #opensuse-admin 2017-12-05T02:00:02 *** Son_Goku has quit IRC 2017-12-05T02:05:30 *** plinnell has quit IRC 2017-12-05T02:08:59 *** plinnell has joined #opensuse-admin 2017-12-05T02:08:59 *** plinnell has joined #opensuse-admin 2017-12-05T02:44:13 *** a-865-kx has quit IRC 2017-12-05T02:45:56 *** Son_Goku has joined #opensuse-admin 2017-12-05T03:05:12 *** a-865-kx has joined #opensuse-admin 2017-12-05T03:30:29 *** okurz has quit IRC 2017-12-05T03:31:51 *** okurz has joined #opensuse-admin 2017-12-05T04:48:47 *** nicolasbock has quit IRC 2017-12-05T05:00:33 *** plinnell has quit IRC 2017-12-05T05:02:27 *** Son_Goku has quit IRC 2017-12-05T05:04:06 *** plinnell has joined #opensuse-admin 2017-12-05T07:20:37 *** tigerfoot has quit IRC 2017-12-05T07:49:09 *** asmorodskyi has joined #opensuse-admin 2017-12-05T08:06:11 *** cthugha has quit IRC 2017-12-05T08:06:32 *** cthugha has joined #opensuse-admin 2017-12-05T08:16:28 *** tigerfoot has joined #opensuse-admin 2017-12-05T09:48:09 *** kl_eisbaer has joined #opensuse-admin 2017-12-05T09:48:09 *** kl_eisbaer has joined #opensuse-admin 2017-12-05T10:07:48 *** fvogt has joined #opensuse-admin 2017-12-05T10:08:22 *** tigerfoot has quit IRC 2017-12-05T10:08:35 *** tigerfoot has joined #opensuse-admin 2017-12-05T10:15:11 *** tigerfoot has quit IRC 2017-12-05T10:24:09 *** tigerfoot has joined #opensuse-admin 2017-12-05T10:50:42 *** cthugha is now known as ldevulder 2017-12-05T11:12:28 *** Son_Goku has joined #opensuse-admin 2017-12-05T11:13:17 *** cboltz has joined #opensuse-admin 2017-12-05T11:28:08 *** Son_Goku has quit IRC 2017-12-05T11:32:14 *** deneb_alpha has joined #opensuse-admin 2017-12-05T11:32:14 *** deneb_alpha has joined #opensuse-admin 2017-12-05T11:45:12 *** Son_Goku has joined #opensuse-admin 2017-12-05T11:56:16 *** Son_Goku has quit IRC 2017-12-05T12:03:21 *** nicolasbock has joined #opensuse-admin 2017-12-05T12:15:38 *** Son_Goku has joined #opensuse-admin 2017-12-05T12:49:03 *** cboltz has quit IRC 2017-12-05T12:52:28 kl_eisbaer: hi :) 2017-12-05T13:00:57 *** fvogt has quit IRC 2017-12-05T15:22:27 *** asmorodskyi has quit IRC 2017-12-05T15:22:53 *** asmorodskyi has joined #opensuse-admin 2017-12-05T15:37:40 *** Son_Goku has quit IRC 2017-12-05T16:02:01 *** mcaj has quit IRC 2017-12-05T16:06:54 *** cboltz has joined #opensuse-admin 2017-12-05T16:30:25 PROBLEM: SSH on mirrordb1.infra.opensuse.org - Server answer: ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=mirrordb1.infra.opensuse.org&service=SSH 2017-12-05T16:30:34 PROBLEM: NRPE on mirrordb1.infra.opensuse.org - CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=mirrordb1.infra.opensuse.org&service=NRPE 2017-12-05T16:32:48 *** kl_eisbaer has quit IRC 2017-12-05T16:38:02 *** tigerfoot has quit IRC 2017-12-05T16:39:07 *** tigerfoot has joined #opensuse-admin 2017-12-05T16:40:25 RECOVERY: SSH on mirrordb1.infra.opensuse.org - SSH OK - OpenSSH_7.2 (protocol 2.0) ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=mirrordb1.infra.opensuse.org&service=SSH 2017-12-05T16:40:26 RECOVERY: NRPE on mirrordb1.infra.opensuse.org - NRPE v3.1.1 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=mirrordb1.infra.opensuse.org&service=NRPE 2017-12-05T16:42:52 tampakrap: I'm just looking at !128 2017-12-05T16:43:37 your init.sls changes would mean to put the contacts file on every minion - but I'd guess we only need it on monitor.infra.o.o 2017-12-05T16:45:52 it's on the profile 2017-12-05T16:46:16 ah the profile is included by every machine 2017-12-05T16:46:22 I'll fix it 2017-12-05T16:49:09 cboltz: fixed 2017-12-05T16:50:23 *** fvogt has joined #opensuse-admin 2017-12-05T16:55:26 :-) 2017-12-05T17:01:38 PROBLEM: HTTP rsync.o.o on widehat.opensuse.org - CRITICAL - Socket timeout after 10 seconds ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=widehat.opensuse.org&service=HTTP%20rsync.o.o 2017-12-05T17:16:28 cboltz: mind giving it a test as well please? 2017-12-05T17:21:28 RECOVERY: HTTP rsync.o.o on widehat.opensuse.org - HTTP OK: HTTP/1.1 200 OK - 1217 bytes in 0.175 second response time ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=widehat.opensuse.org&service=HTTP%20rsync.o.o 2017-12-05T17:22:37 *** kl_eisbaer has joined #opensuse-admin 2017-12-05T17:52:44 cboltz: https://gitlab.infra.opensuse.org/infra/salt/merge_requests/120 I'm thinking of going back to using roles for ntp2 and ntp3, opinion? 2017-12-05T17:53:12 I am using it to get the bindaddress value and to exclude the other ntp servers 2017-12-05T17:57:46 *** tigerfoot has quit IRC 2017-12-05T18:00:33 *** deneb_alpha has quit IRC 2017-12-05T18:02:17 what about setting a grain with the last part of the IP: ntp_bind_address: 102 2017-12-05T18:02:32 and then using that in pillar/role/ntp.sls? 2017-12-05T18:04:25 I also considered to read the machine's IP addresses which salt already provides in the grains, but - anna and elsa have some more IPs ;-) 2017-12-05T18:10:50 oh, the most boring (but also more flexible) solution would be to add the two - bindaddress lines to pillar/id/{anna,elsa} 2017-12-05T18:19:05 cboltz: I did it with some jinja, give it a refresh please 2017-12-05T18:28:04 looks good :-) 2017-12-05T18:28:27 filtering for 192.168.x.y IPs is obvious 2017-12-05T18:29:19 but maybe you should add a comment why you filter out IPs that end with .4 - you probably know it now, but other people who read that (or even yourself in a year) might just scratch their head ;-) 2017-12-05T18:29:40 okay 2017-12-05T18:30:27 oh, and merge !129 which should improve the test result color ;-) 2017-12-05T18:31:42 okay both done 2017-12-05T18:31:48 ah no I need to rebase 2017-12-05T18:45:45 *** mmaher_home has joined #opensuse-admin 2017-12-05T18:59:45 do you use KDE for a DE? 2017-12-05T19:02:54 katnip: yes, one of my machines is running KDE. Why are you asking ? 2017-12-05T19:03:26 just curious what you all use for this is all 2017-12-05T19:03:41 meeting time! 2017-12-05T19:04:02 hello 2017-12-05T19:04:09 katnip: whatever is useful and provides links to a) a Mailer b) a Browser and c) a Console ;-) 2017-12-05T19:04:19 huhu 2017-12-05T19:04:26 gotcha :) 2017-12-05T19:04:27 all KDE here. 2017-12-05T19:04:32 same 2017-12-05T19:05:34 so let's start? 2017-12-05T19:05:36 cboltz: around? 2017-12-05T19:05:42 yes 2017-12-05T19:05:56 hi 2017-12-05T19:06:06 hi 2017-12-05T19:06:41 cboltz: wanna moderate? 2017-12-05T19:06:55 no problem ;-) 2017-12-05T19:07:18 let's start with questions from the community 2017-12-05T19:07:23 does someone have a question? 2017-12-05T19:09:13 apparently not 2017-12-05T19:09:22 doesn't look so, so let's continue with 2017-12-05T19:09:25 using deprecated service as default haproxy answer (like https://crashdb.opensuse.org/) ? 2017-12-05T19:10:05 this is my current idea to "announce" to users that a service is no longer available 2017-12-05T19:10:26 something we might use for whatever webservice we discontinue next :-) 2017-12-05T19:10:36 this is the default backend? 2017-12-05T19:10:45 tampakrap: no, not the default one 2017-12-05T19:10:59 good, +1 from me then 2017-12-05T19:11:01 IMHO it's much better and more informative than a plain 404 page :-) so +1 from me 2017-12-05T19:11:12 My current idea is to show this page just for services we had in the past but no longer (like crashdb or apparmor) 2017-12-05T19:11:14 how long to keep it? 2017-12-05T19:11:27 tampakrap: good question 2017-12-05T19:11:32 6 moths is fine? 2017-12-05T19:11:32 IMHO a year should be enough 2017-12-05T19:11:40 but that includes that we track it.... 2017-12-05T19:11:49 ...and afterward remove it from the DNS and from haprox 2017-12-05T19:11:50 y 2017-12-05T19:12:17 Just one note: the page get's delivered via haproxy directly - so we don't need any special service for it 2017-12-05T19:12:25 I'd argue that subdomains and that page are cheap - just keep it forever ;-) 2017-12-05T19:12:41 there is one little problem, tough: there is a size limit for it 2017-12-05T19:13:25 I am very, very close with the page to the size limit (so even one or two more words might be too much) 2017-12-05T19:14:00 in case we get over the size limit, haproxy would not show anything (and also does not log anything, which was very "interesting to debug" in the beginning) 2017-12-05T19:14:12 so I hope the explanation there is enough 2017-12-05T19:14:28 yep it's perfect 2017-12-05T19:14:55 ok, so "one step closer to the 'deprecation of services' SLA" ;-) 2017-12-05T19:15:13 yep 2017-12-05T19:15:24 if anyone has a better idea/layout, feel free to contact me 2017-12-05T19:15:33 other than that: that's it for the topic at the moment 2017-12-05T19:15:58 there's one small issue - there's a small grey artefact below the geeko 2017-12-05T19:16:10 kl_eisbaer: I'll send you a fixed image later 2017-12-05T19:16:33 cboltz: just send me an update 2017-12-05T19:16:41 merci 2017-12-05T19:17:04 ok, so let's continue with the next topic: how to proceed with redmine, connect and icc? 2017-12-05T19:17:27 ...and conference ... ;-) 2017-12-05T19:17:36 ...and svn ... 2017-12-05T19:17:38 ...and ... 2017-12-05T19:17:40 I added icc, can we move it to the group of crashdb and gallery please? 2017-12-05T19:17:52 conference is wip, new machine is dale.i.o.o already given to the admins 2017-12-05T19:18:02 oh, fine :-) 2017-12-05T19:18:16 I'd say 3 months (that is before the next osc) 2017-12-05T19:18:35 no objections from my side against icc 2017-12-05T19:19:02 svn is in the suse-dmz right? 2017-12-05T19:19:02 IMHO we should think about a meeting once a year to discuss the services we want to take down 2017-12-05T19:19:15 tampakrap: at the moment, yes. I contacted jdsn already and provided svn2 for him 2017-12-05T19:19:29 he just did not find any time yet to work on it 2017-12-05T19:19:39 I lost you, to work on what? 2017-12-05T19:19:55 svn2 is the hostname of the suse-dmz machine that provides svn.o.o and kernel.o.o/kernel.suse.com 2017-12-05T19:19:57 jsdn, the current maintainer of svn, needs to work on svn2 - the new machine 2017-12-05T19:20:21 oh, sorry. Than it was the other way around and the new one is svn while the old one is svn2 ;-) 2017-12-05T19:20:45 ah yes now I remember we talked about this again 2017-12-05T19:20:53 so the new svn machine is sle12 right? 2017-12-05T19:20:57 or leap? 2017-12-05T19:21:04 leap 42.3 - as always 2017-12-05T19:21:16 okay, so why drop it then? 2017-12-05T19:21:19 maybe we can get rid of svn.opensuse.org at all 2017-12-05T19:21:23 ahhh 2017-12-05T19:21:27 now I get you 2017-12-05T19:21:44 so I could send a mail to -factory and -project if anybody is still using it 2017-12-05T19:21:56 if not, it is going away in let's say 3 months, sounds good? 2017-12-05T19:22:02 I could write a blog post as well 2017-12-05T19:22:17 maybe check the access logs? 2017-12-05T19:22:21 tampakrap: you can do it maybe easier in the first run: just check the public repos and their last committer 2017-12-05T19:22:27 it seems some of the SVN repos are still used 2017-12-05T19:22:35 opensuse-doc had the last commit 8 weeks ago 2017-12-05T19:22:57 jip - but maybe we can convince Karl to use github :-) 2017-12-05T19:23:22 opensuse-i18n also had a commit 2 months ago - funnily also by Karl ;-) 2017-12-05T19:23:32 and apparently it is the only one 2017-12-05T19:23:46 translations are migrated to git already 2017-12-05T19:23:54 so maybe talking with him is enough - for the public repos 2017-12-05T19:24:04 I did not check if there are any hidden repos, yet 2017-12-05T19:24:41 okay I'll do it 2017-12-05T19:24:47 jip: there are some 2017-12-05T19:24:54 but all of them are very, very old... 2017-12-05T19:25:05 thanks tampakrap 2017-12-05T19:25:15 *** asmorodskyi_ has joined #opensuse-admin 2017-12-05T19:26:07 One question, still: should we schedule a meeting during OSC (?) where we decide about discontinued services ? 2017-12-05T19:26:48 yes please 2017-12-05T19:27:36 redmine is also on my list to update to sle12, it will take time though, so any help will be welcome 2017-12-05T19:28:00 I am working on the new voting system that the board requested with high priority these days 2017-12-05T19:28:06 *** asmorodskyi has quit IRC 2017-12-05T19:28:06 tampakrap: what about next week ? 2017-12-05T19:28:47 sure, assuming I finish the voting system first 2017-12-05T19:29:00 tampakrap: no problem, I have enough other tasks ;-) 2017-12-05T19:29:12 tampakrap: just ping me, if you need help 2017-12-05T19:29:47 https://progress.opensuse.org/issues/28902 filed this for svn.o.o 2017-12-05T19:30:28 ok, thanks. I guess that is it for the deprecated or "to be moved" services ? 2017-12-05T19:30:38 connect.o.o I assume the agreement is still to drop it as soon as we have the new voting system I am working on with scarabeus, and as soon as we have the new mailing system from heinlein right? 2017-12-05T19:31:08 I don't know, sorry 2017-12-05T19:31:17 I just had the old task in progress to handle connect.o.o 2017-12-05T19:31:30 so I started to work on a elgg package and reserved a machine for it 2017-12-05T19:31:32 looking at the salt master, the only remaining sle11 machines are the narwals, which could go to salt directly and replace them all with leap 2017-12-05T19:31:47 boosters ? 2017-12-05T19:31:54 boosters is connect 2017-12-05T19:31:55 community? 2017-12-05T19:32:02 and also community that I don't know what is doing tbh 2017-12-05T19:32:03 pontifex ;-) 2017-12-05T19:32:46 community is running some vhosts like counter.o.o or the IRC bot 2017-12-05T19:32:58 it's a mix of accounts and services 2017-12-05T19:33:37 ah and osc-collab (not in salt), the maintainers also have been given a leap machine to move it almost a year ago 2017-12-05T19:33:48 so I suppose it is time to send them a mail and put a deadline on them 2017-12-05T19:33:58 tampakrap: jip, totally agreed 2017-12-05T19:34:24 we really can't maintain sle11 any more, especially when 15 is knocking our door 2017-12-05T19:34:29 tampakrap: just one question: did you contact any of the maintainers of events.o.o already ? 2017-12-05T19:34:38 yes, henne 2017-12-05T19:34:43 ah, ok. 2017-12-05T19:34:59 JFYI: this machine is already broken 2017-12-05T19:35:07 I know 2017-12-05T19:35:13 ok 2017-12-05T19:35:37 I guess we can finish this topic, than ? 2017-12-05T19:35:41 yes 2017-12-05T19:36:08 " Priorisation of TODOs " can IMHO be skipped, too. 2017-12-05T19:36:08 ok, so next topic - Priorisation of TODOs 2017-12-05T19:36:33 ok, then let's continue with 2017-12-05T19:36:35 was my topic before I filled the others :-) 2017-12-05T19:36:39 use of https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Machines and the pages behind 2017-12-05T19:36:53 Jip - more or less something FYI only 2017-12-05T19:37:06 have a look at http://paste.opensuse.org/372359e3 2017-12-05T19:37:28 that's how I'd put the "standardized" parts into salt (pillar/id/) 2017-12-05T19:37:30 cboltz: nice :-) 2017-12-05T19:38:02 this would mean that we can get rid of most pages you created ;-) 2017-12-05T19:38:03 So we might extend the machine starting page with a link to that general Saltyfied list 2017-12-05T19:38:07 kl_eisbaer: /root/bin/generate_redmine_wiki.sh can you commit that script to the salt repo as well please? we have the bin/ directory with such tools 2017-12-05T19:38:11 cboltz: nope, not really 2017-12-05T19:38:18 the content is still useful, just moved to salt 2017-12-05T19:38:19 tampakrap: of course 2017-12-05T19:38:50 cboltz: I see the wiki pages more for "problem solvers" and people, who work on a machine only if Salt is broken ;-) 2017-12-05T19:39:12 wiki page is always useful to have, yes 2017-12-05T19:39:15 cboltz: ...or how would you implement something like for https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Monitorinfraopensuseorg 2017-12-05T19:39:16 I'd argue that everybody should have a checkout of the salt repo at hand ;-) 2017-12-05T19:39:19 for example ? 2017-12-05T19:39:53 The monitoring already links to the special wiki pages for each machine, btw. 2017-12-05T19:40:01 cboltz: my suse-it colleagues might need to work on one of those machines and they might not have vpn or salt handy unfurtunately 2017-12-05T19:40:22 so having the info in a place that doesn't require vpn is always nice 2017-12-05T19:40:29 we could solve that by having a checkout of the salt repo on a webserver 2017-12-05T19:40:41 but I don't want to have the information duplicated at salt and wiki 2017-12-05T19:40:49 so - while I really appreciate to have most informations in Salt, sometimes it's just handy to give admins some old, ugly text files at hand to start with their job 2017-12-05T19:41:04 as long as it is generated/automated, I don't mind having it duplicate 2017-12-05T19:41:08 +1 2017-12-05T19:41:17 to bother 2017-12-05T19:41:19 both 2017-12-05T19:41:30 pjessen: +1 for cboltz or +1 for tampakrap ? 2017-12-05T19:41:47 you and tampa 2017-12-05T19:41:50 kl_eisbaer: for the additonal information (like on the Monitorinfraopensuseorg page), we can (and should) still use wiki pages, but 2017-12-05T19:42:13 - those pages could have a more readable name (for example just "Monitor" or "Monitoring") 2017-12-05T19:42:27 - several machines can link to the same page 2017-12-05T19:42:42 cboltz: the problem is, that I want to have a documentation link for every machine that is monitored 2017-12-05T19:43:09 if there is a more general information provided, someone could always create additional pages and link to them 2017-12-05T19:43:13 see https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Olafinfraopensuseorg as examle 2017-12-05T19:43:45 but using Salt to collect some basic information of the machine is very cool and helpful 2017-12-05T19:44:21 just think about : 2017-12-05T19:44:29 Admin notices a problem with a machine on https://monitor.opensuse.org/icinga/ 2017-12-05T19:44:52 Now he just needs to click on the "Extra host notes" (the folder icon beside the host name) 2017-12-05T19:45:22 and he get's redirected to the wiki page of the machine - where he hopefully finds all useful information on how to debug/fix or getting help 2017-12-05T19:45:58 sounds good 2017-12-05T19:46:01 nice integration ;-) 2017-12-05T19:46:13 but - we could also get this by serving pillar/id/$machine ;-) 2017-12-05T19:46:15 most of the current wiki pages of the machines just contain "useless" information that could obviosly also provided by salt, yes 2017-12-05T19:46:29 (or a formatted version of those files) 2017-12-05T19:47:04 but I hope that the administrators of the machine understand that people, who want to fix their wiki server will have other problems than to search in Salt for the information ;-) 2017-12-05T19:47:06 kl_eisbaer: https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Sarabiinfraopensuseorg (as an example) this page is wrong, I edit it via the script or I can edit hte wiki page directly? 2017-12-05T19:47:33 cboltz: but if you don't want to use it, feel free to ignore it. I know that I sometimes are very happy to have such information at hand 2017-12-05T19:47:48 tampakrap: the machine pages should be edited by hand 2017-12-05T19:48:03 cool 2017-12-05T19:48:06 just the overview page is created by the script - as I did not want to miss a machine that is monitored 2017-12-05T19:48:16 perfect 2017-12-05T19:48:49 ...and the monitoring is still not correct, as we miss most of the machines in Provo 2017-12-05T19:48:54 but that's another topic 2017-12-05T19:49:39 For it was just important to point out that there is now a direct connection between a monitored machine and some documentation of the machine 2017-12-05T19:50:07 if the specific wiki page is used or not is something I like to leaf up to the admin of the machine 2017-12-05T19:50:09 RECOVERY: MySQL WSREP recv on galera1.infra.opensuse.org - OK wsrep_local_recv_queue_avg = 0.195652 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=galera1.infra.opensuse.org&service=MySQL%20WSREP%20recv 2017-12-05T19:50:25 ^ juhu, backup job done ;-) (sorry) 2017-12-05T19:50:28 yep got it 2017-12-05T19:50:32 one problem we have with this way that we split information across multiple places 2017-12-05T19:50:51 cboltz: you might be right - but I would leave that up to the maintainer of the machine 2017-12-05T19:51:01 I would prefer to have the info on ldap instead of salt tbh, and populate specific info on salt 2017-12-05T19:51:10 cboltz: or you provide me a similar way to easily create/update and provide the documentation in Salt 2017-12-05T19:51:10 instead of keeping salt as the central point of such data 2017-12-05T19:51:52 I already tried to find out how much information we could store in Freeipa - but there is IMHO not really much possible 2017-12-05T19:52:28 location, arch, OS-Version, MAC address, host group and certificates are ...... Information that could also be stored in Salt. Here is where I agree with cboltz 2017-12-05T19:53:02 but that does not tell me why (for example) a memcached is running on the machine or what other service is using it and how 2017-12-05T19:53:21 I agree as well with that, I am talking about data like cnames and responsible people 2017-12-05T19:53:35 tampakrap: ah, yes. 2017-12-05T19:53:40 they could be in ldap, populated automatically in salt (and even better in salt-mine) 2017-12-05T19:53:58 tampakrap: https://freeipa.infra.opensuse.org/ipa/ui/#/e/host/search 2017-12-05T19:54:01 then we can generate monitoring data and wiki pages from salt-mine 2017-12-05T19:54:10 => I already started to use it ;-) 2017-12-05T19:54:15 if you agree with the pillar/id/ additions in http://paste.opensuse.org/372359e3 _and_ agree that we should _move_ (not duplicate) the information to salt, I'm probably able to come up with a script that creates nice HTML pages for each machine you could link from the monitoring 2017-12-05T19:54:21 for example, the host groups 2017-12-05T19:54:44 the "documentation:" part can still link to the wiki, but those links should be role-specific, not machine-specific IMHO 2017-12-05T19:54:45 I created "apache_servers, nginx_servers" ....and combined them in ... "web-servers" 2017-12-05T19:55:30 So now, if you click on the web-servers host group and check the "Indirect Membership", you get all our web servers, regardless if they are running nginx or apache 2017-12-05T19:55:52 so the host groups can be populated as roles in salt 2017-12-05T19:55:57 ...and btw: if you add a new host in the host group, freeipa automatically created the DNS entries for you 2017-12-05T19:56:04 tampakrap: jip, exactly 2017-12-05T19:56:12 perfect, I like 2017-12-05T19:56:47 hopefully freeipa can create the sudoers rules so we can get rid of them from salt 2017-12-05T19:56:53 ...and other services like the monitoring (for service and hostgroups) or salt could use this information from ldap 2017-12-05T19:57:10 tampakrap: https://freeipa.infra.opensuse.org/ipa/ui/#/e/sudorule/search 2017-12-05T19:58:02 so:yes - you can create sudoers via freeipa - you just need to think about groups and the normal organizational stuff 2017-12-05T19:58:28 got it 2017-12-05T19:59:05 btw: I already created a "machine" user group that has a lower requirement on password changes 2017-12-05T19:59:26 so users in that group don't need to change their password too often 2017-12-05T20:00:03 * cboltz wonders if he's the only one who doesn't want to spread things over several places (yes, that's a vote against using freeipa for things we could do in salt ;-) 2017-12-05T20:00:03 but I guess we can skip the freeipa tutorial to another meeting ;-) 2017-12-05T20:00:23 cboltz: you know KISS ? 2017-12-05T20:00:36 I filed also https://gitlab.infra.opensuse.org/infra/salt/merge_requests/127 and https://gitlab.infra.opensuse.org/infra/salt/merge_requests/128 to generate the monitoring contacts from the ldap users and from the salt roles 2017-12-05T20:00:37 my favourite principle 2017-12-05T20:00:39 take the best tool for a job - and let the other tools make use of it 2017-12-05T20:01:19 cboltz: using Salt for everything is like going into your wine garden with a truck ... 2017-12-05T20:01:25 I know KISS - but IMHO keeping everything at one place is part of it (unless the additional tool is _really_ worth it) 2017-12-05T20:01:53 cboltz: redundance is sometimes needed - but what you should keep in mind the the authority 2017-12-05T20:02:38 there is one authoritative service - the other might have duplicated data, but they need to keep in sync with the authority 2017-12-05T20:03:21 at the moment, neither Salt, nor Freeipa nor any other service knows everything about the network, the services, their users and admins 2017-12-05T20:03:44 but if you wisely combine all of them, you get a very, very good picture 2017-12-05T20:04:08 PROBLEM: MySQL WSREP recv on galera1.infra.opensuse.org - CRIT wsrep_local_recv_queue_avg = 1.875776 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=galera1.infra.opensuse.org&service=MySQL%20WSREP%20recv 2017-12-05T20:04:15 in the end, it's just a question how you present that information to the user in the end 2017-12-05T20:05:24 ...and for me, this sometimes means: "clicky bunty wins" ;-) 2017-12-05T20:07:05 more questions/remarks? 2017-12-05T20:07:16 I don't think we come to a conclusion here today 2017-12-05T20:07:28 I get your point, but would still prefer to have things at one place unless there are very good reasons for a separate place 2017-12-05T20:07:43 cboltz: agreed 2017-12-05T20:07:48 I could even create HTML pages for each machine from pillar/id/* if we decide to use that way ;-) 2017-12-05T20:08:01 so you'd have something you can link from the monitoring 2017-12-05T20:08:23 and those pages could include links to additional wiki pages with more information 2017-12-05T20:08:29 at the moment, my reason is that I want important information about a host at a single page - available via a link from the monitoring. And this information should be easily editable and extensible 2017-12-05T20:08:32 cboltz: I'd suggest to invest some time on salt-mine instead of pillar/id/* 2017-12-05T20:09:05 cboltz: fine with me - I just did what my time permits 2017-12-05T20:09:18 cboltz: if you have better solutions, feel free - I will not object 2017-12-05T20:09:35 *** tigerfoot has joined #opensuse-admin 2017-12-05T20:09:35 cboltz: at the moment, it's just me using these pages anyway 2017-12-05T20:09:40 then the machines will know also data about each other, eg monitoring will know all the IPs of all the machines, the web servers will know the hostnames of their database servers, the haproxy servers will know the IPs of their webservers etc 2017-12-05T20:10:25 cboltz: I'm just building "my infrastructure" as easy as possible - for me. 2017-12-05T20:10:35 I have a feeling that we have different opinions what is a "better solution" ;-) 2017-12-05T20:10:43 there's nothing wrong with that 2017-12-05T20:10:47 cboltz: feel free to convince me that your solution is as good and you got me ;-) 2017-12-05T20:11:14 so before I spend time to move your wiki content to salt, I'd like to know that we'll go that way ;-) 2017-12-05T20:11:29 cboltz: I just hope that "my" solution gives you a good idea what I want to achieve 2017-12-05T20:11:39 (I'll of course provide one or two examples so that you can see what I'm going to do) 2017-12-05T20:11:51 cboltz: yes, please 2017-12-05T20:12:01 I'm looking forward to it, too 2017-12-05T20:12:07 yes, you basically want 2017-12-05T20:12:17 cboltz: at least you should now have an idea what I expect from it ? 2017-12-05T20:12:31 yes 2017-12-05T20:12:42 If I need to update a wiki page or a text file is not relevant for me 2017-12-05T20:12:52 btw: can I include pictures in salt? 2017-12-05T20:13:15 => just joking - I know ASCII art :-) 2017-12-05T20:13:24 base64 2017-12-05T20:13:30 hm. 2017-12-05T20:13:31 lol 2017-12-05T20:13:49 I was thinking about some basic UML or schema graphics 2017-12-05T20:14:02 seriously: good question for salt itsself (I'd say just "git add picture.jpg"), but for the rendered page adding an tag is probably easy 2017-12-05T20:14:11 like [ server1 ] ---speaks with ---> [server2] 2017-12-05T20:14:48 jip, if we can collect - if needed - such pictures somewhere in git and just point to them, I guess this should work 2017-12-05T20:15:37 my solution can (and probably will) still include links to the wiki or $whatever_makes_sense - but those wiki pages will be service-specific (think of a pagename like "monitoring") instead of machine-specific 2017-12-05T20:15:56 ok - fine with me 2017-12-05T20:16:47 Next topic ? 2017-12-05T20:17:23 no objections ;-) 2017-12-05T20:17:28 *** Ada_Lovelace has joined #opensuse-admin 2017-12-05T20:17:41 next topic is the offsite meeting 2017-12-05T20:17:50 hi Sarah! 2017-12-05T20:17:56 Hi 2017-12-05T20:18:06 are we having one before the conference or we are going straight for the conf? 2017-12-05T20:18:16 I have forgotten the time... 2017-12-05T20:18:46 I'd prefer a meeting before the conference 2017-12-05T20:19:04 at the conference, everybody is busy enough, so we won't get too many things done 2017-12-05T20:19:05 Last month we spoke about February. 2017-12-05T20:19:42 jip, I agree 2017-12-05T20:20:04 feb is fine 2017-12-05T20:20:07 this time I would love to see some "work groups" - getting things done 2017-12-05T20:20:30 ...and than we can present that outcome during the conference :-) 2017-12-05T20:20:32 the funny thing is that my only free weekend in February is Feb 17/18 - the other weekends I'm already busy with various other stuff 2017-12-05T20:20:49 so we're going for nuremberg at feb? 2017-12-05T20:21:07 tampakrap: what about Prague ? 2017-12-05T20:21:23 sure, prague it is! 2017-12-05T20:21:26 any preferences, anyone ? 2017-12-05T20:22:03 depends if we want to optimize travel or if we want to switch locations ;-) 2017-12-05T20:22:07 I can't promise - 17/18 is right in the middle of Sportferien 2017-12-05T20:22:39 cboltz: Insheim ? 2017-12-05T20:23:12 I'm not sure if my parents would like that idea ;-) 2017-12-05T20:23:18 pjessen: I guess you will have the longest travel of us - so what would be your preferred date and location ? 2017-12-05T20:23:47 otherwise we go for 3-4 march 2017-12-05T20:24:21 it shouldn't depend on me, but 24/25 would be better. 3/4 March is also good 2017-12-05T20:24:54 cboltz, Ada_Lovelace ? 3/4 March ? 2017-12-05T20:25:09 3/4 March is ok for me 2017-12-05T20:25:25 3/4 March is also ok for me 2017-12-05T20:25:55 nice! 2017-12-05T20:25:56 location ? 2017-12-05T20:26:38 Per didn't join us before. He should say what he like (his home or Prague). ;-) 2017-12-05T20:27:11 I have to decline arranging anything for ZH, too many things going. My personal favourite would be Nuernberg 2017-12-05T20:27:25 ok, fine with me 2017-12-05T20:27:36 No long way for me... 2017-12-05T20:27:50 If everyone agrees, I will clarify the location in Nuremberg for the 3/4 of March 2017-12-05T20:28:03 i'm a fish out of water here 2017-12-05T20:28:07 ...and also ask for travel and lodging support 2017-12-05T20:28:28 I agree but I would say let's give pjessen some time to change his mind so we can have it in prague this time :P 2017-12-05T20:28:28 katnip: want to join ? :-) 2017-12-05T20:28:41 im in the US :/ 2017-12-05T20:28:43 tampakrap: you are free to bring enough beer with you 2017-12-05T20:28:57 katnip: that's an argument, not a problem ;-) 2017-12-05T20:29:35 kl_eisbaer: i seriously don't think it would work out :/ 2017-12-05T20:29:56 katnip: if you don't want to jump into a train or boat, we could easily start a video conf or chat for you 2017-12-05T20:30:06 s/train/plane/ 2017-12-05T20:30:24 * cboltz already wondered when oversea trains were invented 2017-12-05T20:30:28 now that we have some servers under our control in the US ..... 2017-12-05T20:30:32 the chat would work or maybe video 2017-12-05T20:30:37 eurotunnel? 2017-12-05T20:30:44 cboltz: I'm just ahead of time :-) 2017-12-05T20:30:57 pjessen: that's undersea ;-) 2017-12-05T20:31:00 katnip: cool - putting you on the list :-) 2017-12-05T20:31:12 ok :) 2017-12-05T20:32:00 ah, details. 2017-12-05T20:32:31 oversea trains = railway bridges ? oka\y, getting too silly 2017-12-05T20:33:41 next topic ? 2017-12-05T20:33:48 yes 2017-12-05T20:33:54 status reports about everything 2017-12-05T20:34:43 I'll go first 2017-12-05T20:34:48 salt has tests!!!!! 2017-12-05T20:34:57 * tampakrap claps loud 2017-12-05T20:35:33 https://gitlab.infra.opensuse.org/infra/salt/pipelines/585/builds 2017-12-05T20:35:34 related: http://paste.opensuse.org/15812913 ;-) 2017-12-05T20:36:34 so, during hackweek I worked on validation / syntax checking, there are a bunch of hacks introduced since upstream doesn't have the proper tooling 2017-12-05T20:36:50 special thanks to cboltz for having the strong nerves to review my code 2017-12-05T20:37:31 ... and to tampakrap for not killing me after some evil reviews ;-) 2017-12-05T20:37:33 we validate that pillar/id/*.sls has all the necessary data and that they are correct, we check that pillar/role/*.sls are actually assigned roles 2017-12-05T20:37:55 and an overall show_highstate which is a quick way to render the overall code 2017-12-05T20:38:00 and perform syntax checking 2017-12-05T20:38:18 so, we don't have actual functionality tests, but at least we have progress 2017-12-05T20:38:42 also we have a deployment job, that runs only for the production branch and tells the master to pull the new code 2017-12-05T20:38:45 that's it 2017-12-05T20:39:07 wow, that's awesome! :D 2017-12-05T20:39:24 tampakrap: can you please make a posting out of it? 2017-12-05T20:39:25 on a related note: https://gitlab.infra.opensuse.org/infra/salt/merge_requests I have open MRs for chrony and for generating the contact cfgs, feel free to review 2017-12-05T20:39:34 that really looks like cool stuff 2017-12-05T20:39:43 kl_eisbaer: you're on my mind, I wanted to tell it to the team meeting first :) 2017-12-05T20:39:51 :D 2017-12-05T20:40:24 I'll continue with another salt topic ;-) 2017-12-05T20:40:28 I worked on doing the monitoring setup (client side) with salt 2017-12-05T20:40:30 so if you want to add a check to /etc/nrpe.d/ or need to add a package to the zypper whitelist, you can now do it by adding some pillar data in salt 2017-12-05T20:41:09 while doing that, I also cleaned up the package whitelist a lot (thanks to Theo for helping with that) 2017-12-05T20:41:10 cboltz: I don't like that the data are in salt, can we move it to ldap please? HAHAHA okay I'll stop now 2017-12-05T20:41:41 tampakrap: I'll happily review your merge request ;-) 2017-12-05T20:43:25 as soon as someone answers my questions in https://gitlab.infra.opensuse.org/infra/salt/issues/3 and https://gitlab.infra.opensuse.org/infra/salt/issues/3 I'll also add the package list and the /etc/nrpe.d/ checks of all machines to salt 2017-12-05T20:43:38 s/3/2/ in the first link 2017-12-05T20:44:08 RECOVERY: MySQL WSREP recv on galera1.infra.opensuse.org - OK wsrep_local_recv_queue_avg = 0.000000 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=galera1.infra.opensuse.org&service=MySQL%20WSREP%20recv 2017-12-05T20:44:20 okay but please move these tickets to the progress-admin, the gitlab issue tracker was supposed to redirect to progress (until upstream broke it) 2017-12-05T20:44:30 so I'll close the ticketing system there completely 2017-12-05T20:45:24 I'd hope for a quick answer so that we can close them without needing to move them ;-) 2017-12-05T20:46:20 fair enough 2017-12-05T20:46:25 cboltz: let's discuss this tomorrow 2017-12-05T20:46:42 ok 2017-12-05T20:46:52 the good thing is: the monitoring will instantly know if something breaks ;-) 2017-12-05T20:47:45 salt won't remove any packages or /etc/nrpe.d/ checks, so in theory nothing can break ;-) 2017-12-05T20:47:54 we'll see if practise disagrees 2017-12-05T20:48:39 I've another status report .... https://progress.opensuse.org/news/63 2017-12-05T20:49:04 I hope to finish the migration of pontifex - aka download.o.o - on thursday, finally 2017-12-05T20:49:34 Guys, I have to go - no status to report, really. I have reserved 3/4 March in my calendar. 2017-12-05T20:49:54 at the moment, I'm still fighting with "knapsack" modules and the database (esp. repmgr), but I've still good hope to finish this until tomorrow night 2017-12-05T20:50:03 pjessen: thank you for your time! 2017-12-05T20:50:19 pjessen: any objections to become MX master ? 2017-12-05T20:50:31 MX master? 2017-12-05T20:50:44 pjessen: topic "own MX for openSUSE ? " 2017-12-05T20:50:57 Sure, I'll be happy to look after that. 2017-12-05T20:51:04 I guess it's time to isolate the master MX from SUSE-IT and bring it under our control 2017-12-05T20:51:23 agreed, but... 2017-12-05T20:51:36 it might be a forwarding of list traffic to baloo and the other stuff to Heinlein in the end 2017-12-05T20:51:59 It's what I do professionally anyway, so ... 2017-12-05T20:52:02 but this way we can get rid of the ping - pong with SUSE-IT regarding the redirects 2017-12-05T20:52:15 I was thinking about the other way round, so that Heinlein {c,w}ould do the spam filtering 2017-12-05T20:52:22 ...and I talked already with Christian, who has no objections. 2017-12-05T20:52:34 ah so we can get rid of the shuttle net from baloo right? 2017-12-05T20:52:38 So the only thing that we need to clarify is a) if we want and b) if legal agrees 2017-12-05T20:52:53 tampakrap: yes, right 2017-12-05T20:52:59 Heinlein is doing something... 2017-12-05T20:53:18 He has tested something with my opensuse.org alias... 2017-12-05T20:53:18 cboltz: in this case we need to figure out how Heinlein forwards the other stuff back to us 2017-12-05T20:53:26 mmaher_home: do you have any news from Heinlein? 2017-12-05T20:54:09 cboltz: the technical person wants to contact me this week. thats the last status i have. 2017-12-05T20:54:09 pjessen: but I don't want to stop you - let's move this discussion to the mailing list ? 2017-12-05T20:54:45 2 weeks ago I received notifications by mailbox.org admin. 2017-12-05T20:54:58 thanks, that would be great. Let's resume on the mailing list tomorrow. 2017-12-05T20:55:27 A bit early still, but Merry Christmas to everone. 2017-12-05T20:55:32 I should change my password which doesn't exist. 2017-12-05T20:56:29 pjessen: Merry Christmas to you :) 2017-12-05T20:57:04 pjessen: bye, merry early christmas! 2017-12-05T20:57:24 *** pjessen has quit IRC 2017-12-05T20:57:32 *** asmorodskyi_ has quit IRC 2017-12-05T20:57:38 so after mixing topics a bit - does someone have another status report? 2017-12-05T20:58:34 heroes tickets are low as never before, yeah 2017-12-05T20:59:40 I've seen that you handled quite some mirror and monitoring tickets in the last days - thanks for that! 2017-12-05T21:00:24 cboltz: I hope to become two-digit until new year :-) 2017-12-05T21:00:52 I'm afraid I have to disagree with "as low as never before" - we were down to ~130 in March IIRC 2017-12-05T21:01:23 but I completely agree that going in the two-digit range would be very nice 2017-12-05T21:01:29 now I see 129 new tickets 2017-12-05T21:02:03 but anyway, I guess we just have two topics left? 2017-12-05T21:02:04 strange, I see 158 open tickets 2017-12-05T21:02:15 right 2017-12-05T21:02:26 cboltz: I guess "open" in redmine includes "feedback" and other tickets 2017-12-05T21:02:48 next meeting - Jan 2nd, or move it to Jan 9th? 2017-12-05T21:02:58 I vote to the 9th 2017-12-05T21:03:24 *** Son_Goku has joined #opensuse-admin 2017-12-05T21:03:32 I'm fine with both 2017-12-05T21:03:43 I'm also fine with both 2017-12-05T21:04:36 so let's make it 9th since lars can't on 2 2017-12-05T21:04:45 thanks! 2017-12-05T21:04:46 I'm fine with both. 2017-12-05T21:05:10 ok, so the next meeting will be on Jan 9th 2017-12-05T21:05:27 we already discussed the "own MX for openSUSE" topic 2017-12-05T21:05:39 1400 EST ? jan 9th ? 2017-12-05T21:05:42 wait a min 2017-12-05T21:06:00 kl_eisbaer: the MX will also be relay? 2017-12-05T21:06:14 or the relay will still be the haproxy servers? 2017-12-05T21:06:14 tampakrap: depends on us - or Heinlein 2017-12-05T21:06:24 ah yes I forgot heinlein 2017-12-05T21:06:27 tampakrap: from my pow, it should become an own machine 2017-12-05T21:06:55 so separate pair for MX, separate pair for relay (away from haproxy)? 2017-12-05T21:07:03 (ignoring heinlein for now) 2017-12-05T21:07:06 We will have some fun how we should handle SPAM and Virus tagging, as the german law is very strict in this 2017-12-05T21:07:21 tampakrap: right 2017-12-05T21:07:31 oh, that's easier than you might think 2017-12-05T21:07:48 completely forget about tagging, and reject the mails instead 2017-12-05T21:07:52 tampakrap: maybe we should think about having mx1 in Nuremberg (or Prague?) and mx2 in Provo ? 2017-12-05T21:08:06 cboltz: yes - and no 2017-12-05T21:08:15 the important thing is to do the reject on the MX, so that the sending server gets a 5xx instead of a 200 to log 2017-12-05T21:08:24 but I would rely on Per here, as he has the knowledge we might simple use :-) 2017-12-05T21:08:36 this also means the sending server has to create the bounce mail, so we won't create backscatter 2017-12-05T21:08:59 ...and of course on you, cboltz :-) 2017-12-05T21:09:01 okay 2017-12-05T21:09:17 tampakrap: so we have the two admins for a possible MX already 2017-12-05T21:09:32 perfect 2017-12-05T21:09:46 BTW: that's what Peer Heinlein recommends for years, and since he's an expert on mail servers _and_ studied the legal stuff, I trust him on this ;-) 2017-12-05T21:09:58 I'm just not sure if we can have this (incl. the own mailboxes from Heinlein) as Christmas present for our users 2017-12-05T21:10:33 for my it's just the question: who wants to drive this ? 2017-12-05T21:10:36 *** nicolasbock has quit IRC 2017-12-05T21:11:56 I told you, he is working on it... 2017-12-05T21:12:36 Ada_Lovelace: who is "he" ? 2017-12-05T21:12:43 Should I forward such a email to you? 2017-12-05T21:12:52 A admin by Heinlein. 2017-12-05T21:13:10 Ada_Lovelace: ah, ok. So the board already decided that Heinlein takes over our MX ? 2017-12-05T21:13:18 I received emails by mailbox.org, that my mailbox has changes. 2017-12-05T21:13:38 I should change my password for adalovelace@opensuse.org. 2017-12-05T21:14:08 Yes. 2017-12-05T21:14:39 ah, ok. Because than we can forget the discussion/topic about hosting our own MX 2017-12-05T21:14:39 I don't know what Max said to Per. 2017-12-05T21:14:58 the board didn't talk about the technical details (at least in the last year), but IMHO it would make sense if they do the MX 2017-12-05T21:15:00 sounds like some interesting setup 2017-12-05T21:15:51 Well, theoretical question, but what if people decide that their account/mail should not be given out to others ? 2017-12-05T21:15:59 That's a discussion between Max and Per. 2017-12-05T21:16:24 *at the moment* 2017-12-05T21:16:37 is the mail simply an alias? 2017-12-05T21:16:38 wow. Congratulations, mmaher_home, for your legal exam ;-) - I hope you have enough money in your pocket ;-) 2017-12-05T21:16:42 we asked if we can either have the forward option or creation of a mailbox inbox. still no answer 2017-12-05T21:17:02 Most email aliases are MX forwards. What will be given away? 2017-12-05T21:17:24 Ada_Lovelace: user data - and might it be only the login / user names 2017-12-05T21:18:01 Enough that someone at Heinlein would know that user X is an openSUSE member 2017-12-05T21:18:05 *** Son_Goku has quit IRC 2017-12-05T21:18:16 even if this user never want to get a mailbox at mailbox.org 2017-12-05T21:18:57 but luckily I'm not an expert in this area, so I might have a bit to much paranoia here 2017-12-05T21:19:19 that's why I'm relying on board and legal decisions for such stuff 2017-12-05T21:20:14 same for the DNS, btw. But luckily we don't need to think about user data here ;-) 2017-12-05T21:21:17 so moving to the last topic then? 2017-12-05T21:21:23 IMHO yes. 2017-12-05T21:21:31 yes 2017-12-05T21:21:31 Then you aren't allowed to host openSUSE systems at any hosting providers, because databases have user data. 2017-12-05T21:21:59 I just wanted to ask if anybody would disagree if I ask legal to take over the primary NS for the opensuse.org domain 2017-12-05T21:22:32 no objections, that's one shuttle net address less :) 2017-12-05T21:22:53 Ada_Lovelace: again: I'm not an expert - but I see a difference between hosting servers (and getting them maintained by openSUSE people) or directly providing data to other providers that contains user information 2017-12-05T21:23:40 the only thing I have in the DNS case: we should IMHO think about running a 3rd DNS machine somewhere else 2017-12-05T21:23:49 kl_eisbaer: right, but actually we already give that data to a company - SUSE ;-) 2017-12-05T21:24:07 cboltz: yes, and everybody agreed during account creation that this is ok 2017-12-05T21:24:21 ...and everybody need to agree again if you give the data to another company 2017-12-05T21:24:31 *** Son_Goku has joined #opensuse-admin 2017-12-05T21:24:54 but again: that's just my personal understanding and I'm no lawyer 2017-12-05T21:25:04 so I'm fine with whatever the board decides 2017-12-05T21:25:12 *** Son_Goku has quit IRC 2017-12-05T21:25:28 feel free to talk to legal and/or to Richard about this ;-) 2017-12-05T21:25:35 Per is lawyer, too. 2017-12-05T21:25:36 The good thing, if we run our own DNS would be: we could provide Geo-based DNS :-)) 2017-12-05T21:26:20 again: I don't want to object here - I was just surprised that this topic is already in that state where Heinlein checks the setup 2017-12-05T21:26:55 I'm happy that something goes forward here - so go ahead and drive it :-) 2017-12-05T21:26:55 regarding the third dns server, that's a big blocker 2017-12-05T21:27:31 yes / no - it depends. We have of course enough free IPs to host it either in Nuermberg or Provo 2017-12-05T21:27:49 and I'm sure we will find enough "DNS masters" who will include our domain as slave 2017-12-05T21:28:03 true 2017-12-05T21:28:17 but if we want to go further (the Geo-Based thing), we should not take this too easy 2017-12-05T21:28:45 IMHO starting with a basis setup with 2 servers in NUE and 2 in Provo should be totally ok 2017-12-05T21:29:28 once we are able to run a "useful" amount of services also in Provo (like wiki, download.o.o. or such), we should think about the geo-base DNS again and enroll that 2017-12-05T21:29:50 as it would improve the availability and usability for our users, especially in the US 2017-12-05T21:29:53 we need to make the vpn in provo first and figure out how to bridge the vpn servers 2017-12-05T21:29:59 ...and maybe even Asia 2017-12-05T21:30:01 right? 2017-12-05T21:30:22 tampakrap: yes, this is meanwhile one of the hottest topics for me after the download.o.o switch 2017-12-05T21:30:58 tampakrap: if scar would open a VPN tunnel to the machines in Provo, it could route the "default gateway" traffic already 2017-12-05T21:31:17 tampakrap: only the machines with more than one interface need to get an additional routing entry for the Provo network range 2017-12-05T21:31:36 okay 2017-12-05T21:32:50 DNS servers can be everywhere on the world and can communicat together the. 2017-12-05T21:32:59 ok - any other questions? 2017-12-05T21:33:07 *communicate together then* 2017-12-05T21:33:19 Ada_Lovelace: I would even say: they *should* be everywhere in the world :-) 2017-12-05T21:33:50 ...and establishing DNSSec is also a good idea, IMHO ;_) 2017-12-05T21:34:04 I know colleages who wanted to have their own DNS servers so for HA. 2017-12-05T21:38:30 any other points ? 2017-12-05T21:38:34 kl_eisbaer: willl you setup all those DNS servers manually, or will you use salt from the beginning this time? ;-) 2017-12-05T21:38:57 cboltz: I doubt I will have enough time for this 2017-12-05T21:39:03 hint: seeing that you want at least 4 servers, salt is probably faster 2017-12-05T21:39:47 cboltz: on the other way: DNS is really easy 2017-12-05T21:40:15 as freeipa will stay as master, all the other will get their information from freeipa anyway 2017-12-05T21:40:52 cboltz: ...and in this case Salt can't be faster than a "dd" of a golden image ;-p 2017-12-05T21:41:18 the dns config of chip is already in salt btw 2017-12-05T21:41:28 if you have to copy that image to Provo, things might be different ;-) 2017-12-05T21:41:29 cboltz: ...and you might think about other admins who will just include the opensuse.org domain as additional slave zone 2017-12-05T21:42:08 I'm not sure if they would give your salt master access to their servers if you are speaking about two zones only 2017-12-05T21:42:16 ah, autsch! 2017-12-05T21:42:28 found an important bug in my thinking :-/ 2017-12-05T21:42:45 ;-) 2017-12-05T21:42:47 at least in Nuremberg, the reverse zone is a problem 2017-12-05T21:43:06 ah yes 2017-12-05T21:43:08 something I need to clarify with MF-IT 2017-12-05T21:43:51 so in worst case reverse lookups would still need the MF DNS servers? 2017-12-05T21:44:05 cboltz: ...and that is something that will not work 2017-12-05T21:44:28 ...but I'm sure we will find a solution 2017-12-05T21:44:29 silly question - why not? 2017-12-05T21:45:04 my understanding is that having separate DNS servers for the reverse lookup shouldn't be a problem 2017-12-05T21:45:28 yeah - but it does not help with the separation 2017-12-05T21:45:52 if I still need to open ticket after ticket for every single IP, that simply just boring 2017-12-05T21:46:07 I have to leave you. Tomorrow is university. 2017-12-05T21:46:26 Ada_Lovelace: have a lot of fun there :-) 2017-12-05T21:46:28 Ada_Lovelace: have a nice evening 2017-12-05T21:46:29 Bye. Until next meeting. 2017-12-05T21:46:34 bye 2017-12-05T21:46:45 *** Ada_Lovelace has quit IRC 2017-12-05T21:46:53 let me start the discussion with MF-IT how we can solve that finally. 2017-12-05T21:47:21 I get your point and agree that the perfect solution would be to also handle the reverse lookups ourself 2017-12-05T21:48:04 but even if this doesn't work, handling the forward DNS (aka what people use 99,9% of the time) would be a big step forward 2017-12-05T21:48:32 cboltz: depends - I'm not sure if this will work for geo-based DNS 2017-12-05T21:48:44 ...and for implementing DNSSec this does also not really help 2017-12-05T21:49:22 but anyway - I'll take that with me for now 2017-12-05T21:49:36 at least it's good to hear that nobody has objections against it 2017-12-05T21:50:50 I'm quite sure nobody wants to depend on MF-IT if it can be avoided ;-) 2017-12-05T21:51:03 ok - anything left to discuss ? 2017-12-05T21:51:52 nothing from me 2017-12-05T21:52:02 nope, we can discuss further with merge requests https://gitlab.infra.opensuse.org/infra/salt/merge_requests :) 2017-12-05T21:52:23 ok - in this ^^ case it's time for me to leave ;-) 2017-12-05T21:52:40 have a good night! 2017-12-05T21:52:45 good night! 2017-12-05T21:52:48 see ya 2017-12-05T21:52:49 good night! 2017-12-05T21:52:54 *** kl_eisbaer has left #opensuse-admin 2017-12-05T21:53:00 and thanks everybody for staying so long! 2017-12-05T21:53:10 np 2017-12-05T21:53:43 *** mmaher_home has quit IRC 2017-12-05T22:02:52 paperwork (uploading the meeting log and creating a ticket for the January meeting) done 2017-12-05T22:12:37 you're the man 2017-12-05T22:12:54 do you link those to the wiki page as well btw? 2017-12-05T22:15:17 never do something manually that you get for free ;-) 2017-12-05T22:15:19 https://progress.opensuse.org/projects/opensuse-admin/issues?query_id=36 2017-12-05T22:16:50 okay can you include that link to the wiki then please? 2017-12-05T22:18:23 it's already on https://en.opensuse.org/openSUSE:Heroes/Meetings 2017-12-05T22:19:02 but maybe repeating it in the "Past Meetings" section would be a good idea 2017-12-05T22:19:44 I'll also drop the list of past meetings, with the exception of the offsite meeting 2016 because we don't have that in progress 2017-12-05T22:20:33 yep makes sense 2017-12-05T22:36:22 tampakrap: in !128 you wrote "all roles are added on the tests" 2017-12-05T22:36:48 maybe you misunderstood me - I was thinking about adding the roles in test_show_highstate.sh 2017-12-05T22:37:46 cboltz: I didn't misunderstood you, that's exactly what I meant 2017-12-05T22:38:03 the problem is that show_highstate doesn't validate if the function is correct 2017-12-05T22:38:30 so I *assume* it renders it as correct 2017-12-05T22:38:50 but maybe I am wrong and our testing has a bug that I don't see 2017-12-05T22:39:45 see https://gitlab.infra.opensuse.org/infra/salt/blob/production/bin/prepare_test_show_highstate_env.sh#L41 2017-12-05T22:40:12 in the previous line we get all roles and we put them in /etc/salt/grains 2017-12-05T22:41:10 ah, you managed to confuse me - I only noticed write_grains in test_show_highstate.sh, and didn't find anything about roles there 2017-12-05T22:51:15 cboltz: I'm running the tests locally, in /etc/salt/grains I do see all the roles including the monitoring role 2017-12-05T22:51:55 and I'm pretty sure it works fine because before the tests were green, I had some syntax errors that were properly caught by show_highstate 2017-12-05T22:52:19 so my assumption is probably valid, it doesn't check if the state function exists 2017-12-05T22:53:15 indeed, I tried with "file.exi" locally and it happily prints out the "exi" in show_highstate :-( 2017-12-05T22:54:24 by the way, when running them locally I get this 2017-12-05T22:54:26 [ERROR ] Rendering exception occurred: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'has_key' 2017-12-05T22:54:28 [CRITICAL] Rendering SLS 'base:profile.apparmor.profiles' failed: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'has_key' 2017-12-05T22:54:30 [ERROR ] Rendering exception occurred: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'iteritems' 2017-12-05T22:54:32 [CRITICAL] Rendering SLS 'base:zypper.config' failed: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'iteritems' 2017-12-05T22:54:34 [ERROR ] Rendering exception occurred: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'iteritems' 2017-12-05T22:54:36 [CRITICAL] Rendering SLS 'base:zypper.packages' failed: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'iteritems' 2017-12-05T22:54:38 [ERROR ] Rendering exception occurred: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'has_key' 2017-12-05T22:54:40 [CRITICAL] Rendering SLS 'base:zypper.repositories' failed: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'has_key' 2017-12-05T22:56:25 strange[tm] 2017-12-05T22:56:42 I don't see those errors when running show_highstate for one of my test VMs 2017-12-05T22:57:02 I'm on tumbleweed if it makes any difference 2017-12-05T22:57:26 I have the saltmaster on tumbleweed, and the VMs are 42.3 2017-12-05T22:58:11 (I'm using "salt $minion state.show_highstate", not salt-call) 2017-12-05T23:07:43 something changed in jinja and iteritems() is not valid any more? 2017-12-05T23:09:23 no idea - but I can't imagine such a change would be intentional 2017-12-05T23:10:14 I replaced iteritems() with items() in zypper formula and I got rid of the iteritems erros 2017-12-05T23:10:18 but the has_key ones remain 2017-12-05T23:11:20 https://stackoverflow.com/questions/27740153/check-if-key-exists-in-a-python-dict-in-jinja2-templates 2017-12-05T23:11:29 https://github.com/saltstack-formulas/vmbuilder-formula/issues/3 2017-12-05T23:11:32 this says in a comment that hasKey is deprecated and we should use in instead 2017-12-05T23:11:55 ha issue found 2017-12-05T23:12:00 salt is python3 in tumbleweed 2017-12-05T23:12:33 yes, I noticed that 2017-12-05T23:12:46 but never thought that we might need to run 2to3 on our salt code :-/ 2017-12-05T23:13:21 there is a possibility that even in leap salt will go to python3 2017-12-05T23:13:25 so better to fix those issues now 2017-12-05T23:13:50 no objections ;-) 2017-12-05T23:14:16 dhcpd-formula uses has_key() a lot 2017-12-05T23:14:47 I also see it in profile/apparmor/ and profile/wiki/ 2017-12-05T23:15:20 iteritems() is used in some formulas - grep yourself ;-) 2017-12-05T23:16:04 I'm fixing the ones that the testsuite hits for now 2017-12-05T23:16:37 I'll handle profile/apparmor (already done) and profile/wiki 2017-12-05T23:18:22 I'm doing them as well :/ 2017-12-05T23:18:53 I have both finished now, and already tested ;-) 2017-12-05T23:19:35 http://paste.opensuse.org/52345265 can you test this as well please? 2017-12-05T23:19:45 at least show_highstate is clean now 2017-12-05T23:21:35 *** fvogt has quit IRC 2017-12-05T23:24:07 you surprise me - why paste.o.o instead of a merge request? 2017-12-05T23:24:42 I can't, it's my github repo 2017-12-05T23:24:50 ah I could do a branch 2017-12-05T23:25:00 I'm stupid yes 2017-12-05T23:25:12 no problem, I can patch from paste.o.o 2017-12-05T23:25:32 https://gitlab.infra.opensuse.org/infra/salt/merge_requests/130 should fix has_key() in profile/* 2017-12-05T23:26:34 https://github.com/tampakrap/zypper-formula/pull/1 2017-12-05T23:28:18 interestingly the diff fails to apply on the zypper-formula from gitlab 2017-12-05T23:28:32 maybe it's out of sync with your github repo? 2017-12-05T23:29:51 now it's in sync 2017-12-05T23:31:06 highstate on my wiki test VM didn't change anything 2017-12-05T23:31:22 so your changes are ok 2017-12-05T23:32:37 aboe[m]: can we move https://github.com/tampakrap/zypper-formula to saltstack-formulas namespace? 2017-12-05T23:33:11 merged 2017-12-05T23:58:39 cboltz: on !127 I don't understand about the function you propose me to introduce 2017-12-05T23:59:12 I use this try except twice, but once I am loading the yaml and the second I am using the read_file_skip_jinja function 2017-12-05T23:59:19 I am not sure how I can unify them