openSUSE admin

2017-05-08 #opensuse-admin Heroes Meeting

[20:02:37] <Ada_Lovelace> Or let's start.

[20:02:58] <pjessen> yup

[20:03:10] <Ada_Lovelace> At first: Questions from the community

[20:03:40] <Ada_Lovelace> Have we got new people with questions?

[20:03:53] <pjessen> is this a general item or just in case ?

[20:04:03] <Ada_Lovelace> just in case

[20:04:19] <Ada_Lovelace> and "questions" in general item

[20:04:54] <pjessen> okay. Then perhaps we ought to start with a listing of whos is attending.

[20:05:32] * cboltz hides once more

[20:05:37] <pjessen> just raise your hand and say "Im here"

[20:05:49] * tampakrap

[20:06:45] <Ada_Lovelace> Then to the second item: status reports about everything (see ticket #17272 / March meeting for a list)

[20:06:47] <kl_eisbaer1> I'm here

[20:06:55] <Ada_Lovelace> Lars :)

[20:07:11] <Ada_Lovelace> Hi!

[20:07:14] <kl_eisbaer1> you really miss me? Wonderful ;-)

[20:07:31] <kl_eisbaer1> looks like I broke not too much ;-)

[20:07:38] <pjessen> it was getting a bit lonely here

[20:07:40] <Ada_Lovelace> I was surprised, that you were inactive.

[20:08:26] <kl_eisbaer1> sometimes even I fell inactive

[20:08:34] <kl_eisbaer1> status report?

[20:08:41] <Ada_Lovelace> Yes.

[20:08:48] <kl_eisbaer1> connect.o.o - anyone with news about that beast ?

[20:09:08] <Ada_Lovelace> It lives like it is...?

[20:09:32] <kl_eisbaer1> DNS: up and running (which allowed us to add IPv6 very quickly :-)

[20:09:42] <kl_eisbaer1> Monitoring and status page

[20:09:44] <pjessen> good stuff!

[20:10:02] <Ada_Lovelace> I added an additional item for Icinga.

[20:10:15] <kl_eisbaer1> pjessen: I'm looking forward to the openVPN machine, so next time I can leave the solving completely up to you

[20:10:37] <kl_eisbaer1> Ada_Lovelace: where?

[20:10:38] <Ada_Lovelace> We spoke about using Salt Stack for checks.

[20:10:55] <Ada_Lovelace> On our list for today.

[20:11:05] <pjessen> haha, what have i committed to?

[20:11:15] <Ada_Lovelace> https://progress.opensuse.org/issues/18456

[20:12:11] <Ada_Lovelace> Additional to that Lars and I created a wiki page: https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/Monitoring

[20:12:30] <kl_eisbaer1> Ada_Lovelace: you know that this needs still developement?

[20:12:54] <Ada_Lovelace> What do other admins say about using zeromq in combination with SaltStack, API and Icinga?

[20:13:04] <kl_eisbaer1> Ada_Lovelace: so I would leave the "Using salt for monitoring" out for now - until you implemented the missing features in Salt and Icinga

[20:13:06] <kl_eisbaer1> :-)

[20:13:16] <Ada_Lovelace> Yes, but why not the meaning?

[20:13:37] <Ada_Lovelace> or opinion ^^

[20:13:38] <kl_eisbaer1> Ada_Lovelace: fine with me - go ahead :-)

[20:14:32] <Ada_Lovelace> Nothing? Thhen we would try it. ^^

[20:15:18] <Ada_Lovelace> kl_eisbaer1: Anything about the status page additional to that?

[20:16:11] <tampakrap> if you need help with salt let me know as always

[20:16:18] <kl_eisbaer1> I am currently working on an update to the next version - but need to figure out how to package all the additional vendor php packages comming in via the composer requires

[20:16:24] <Ada_Lovelace> Yes. Thanks!

[20:17:28] <kl_eisbaer1> more=

[20:17:30] <kl_eisbaer1> ?

[20:17:31] <cboltz> kl_eisbaer1: I already had some fun with composer when packaging the MediaWiki extensions

[20:17:41] <kl_eisbaer1> cboltz: so where are your packages?

[20:17:49] <cboltz> home:cboltz:infra

[20:18:05] <cboltz> feel free to steal my script ;-)

[20:18:07] <kl_eisbaer1> cboltz: ok, thanks. I will have a look

[20:18:42] <cboltz> (actually, with more users, maybe we should split it into generic script + config file instead of carrying 10 slightly modified copies)

[20:19:09] <kl_eisbaer1> cboltz: which package contains "your script" ?

[20:19:57] <kl_eisbaer1> is there any documentation/script for openSUSE that helps packaging https://packagist.org/ ?

[20:19:58] <cboltz> for example mediawiki_1_27-Elastica and mediawiki_1_27-GitHub

[20:20:20] * kl_eisbaer1 might need to ask on #opensuse-packaging ;-)

[20:21:21] <kl_eisbaer1> more?

[20:21:42] <cboltz> a small bugreport: when I click on "Monitoring page" instead of the "Monitor openSUSE" button on http://monitor.opensuse.org/ a layer with broken content pops up

[20:22:56] <cboltz> I doubt we need that layer for additional information, so making everything a link to /icinga/ is probably the easiest solution

[20:24:05] <kl_eisbaer1> cboltz: that "welcome" page was (as always) just a quick hack from me to show what we have

[20:24:35] <kl_eisbaer1> cboltz: IMHO we might discuss about a "project"(?) below github.com/opensuse/ to store simple pages like that

[20:25:22] <kl_eisbaer1> at the moment, that page is just in a local git repo

[20:26:11] <cboltz> I'd vote for one repo per page/domain, in this case the ideal name would be monitor.opensuse.org (or monitor.o.o if you want a shorter name)

[20:26:29] <kl_eisbaer1> cboltz: ok, fine with me

[20:26:35] <cboltz> simple pages change rarely, and that name makes it easier to find it again ;-)

[20:28:31] <pjessen> next item?

[20:29:20] <kl_eisbaer1> ticket triage ?

[20:30:34] <Ada_Lovelace> Max wanted to do a lot for the conference and not tickets.

[20:30:41] <kl_eisbaer1> One note about the monitor.o.o - I just noticed that we have https://github.com/orgs/openSUSE/teams/opensuse-admin-tools already

[20:31:19] <Ada_Lovelace> What is to do there after the last year with the conference in the same location and other events with great internet access?

[20:31:36] <kl_eisbaer1> Ada_Lovelace: ask Max

[20:31:59] <Ada_Lovelace> Ok

[20:32:07] <Ada_Lovelace> I was surprised...

[20:32:23] <kl_eisbaer1> Ada_Lovelace: you are not alone ...

[20:32:56] <cboltz> mmaher_: are you near your keyboard, or is only your computer online? ;-)

[20:32:58] <Ada_Lovelace> I'll write him.

[20:33:18] <kl_eisbaer1> cboltz: should we create a "openSUSE heroes" team there or is it ok if we use the openSUSE-admin team ?

[20:34:17] <cboltz> I don't care about the name on github too much, so use whatever is easier ;-)

[20:35:09] <kl_eisbaer1> cboltz: ok - I'll take this as action item to prepare something for the next meeting

[20:35:29] <kl_eisbaer1> Next status report?

[20:35:33] <kl_eisbaer1> => new wiki

[20:35:56] <cboltz> well, I'm still waiting for the auth proxy

[20:36:14] <cboltz> kl_eisbaer1: did you have some time to work on it already?

[20:36:29] <kl_eisbaer1> nope - as I said: I would prefer to have openVPN first

[20:36:57] <cboltz> I *love* dependency chains...

[20:37:00] <tampakrap> yes, openvpn is high priority task now that we also have freeipa

[20:37:03] <kl_eisbaer1> cboltz: if you want to use ldap-auth, this might be a bit easier, but even that is nothing I would do in a minute (firewalling, etc. needs to be done there)

[20:37:22] <pjessen> just checking - have I promised something? I've been busy with openVPN in the business anyway.

[20:37:47] <pjessen> wrt openVPN

[20:38:05] <cboltz> kl_eisbaer1: sounds like I should look at openID again - I'll need to modify the extension to enforce the username, but maybe it isn't too hard

[20:38:39] <kl_eisbaer1> cboltz: so you will become a mediawiki extension author - what a surprise ;-)

[20:39:23] <kl_eisbaer1> pjessen: I guess tampakrap will take you on his list of openVPN contacts ;-)

[20:39:25] <cboltz> I hope that I'll only become a one-time patch contributor ;-)

[20:39:41] <kl_eisbaer1> btw: Salt / Gitlab - any news here ?

[20:39:45] <cboltz> BTW: did I already mention http://en.test.opensuse.org/Map_test ?

[20:40:12] <tampakrap> pjessen: I'll contact you via mail on this topic on monday or tuesday to set up a separate hands-on meeting

[20:40:23] <tampakrap> gitlab and salt are two different topics

[20:40:25] <kl_eisbaer1> cboltz: you might want to start to document your work on progress.o.o ?

[20:40:38] <tampakrap> gitlab news: it is fully integrated now with freeipa auth yey!

[20:40:39] <pjessen> okay, sounds good.

[20:41:19] <cboltz> kl_eisbaer1: that's on my TODO list, but in some cases I prefer to wait until I know which way we go before documenting it

[20:41:22] <tampakrap> non-suse people can not access the freeipa instance yet to reset their passwords, so either I send them a password via encrypted mail or you wait until we have the openvpn in place

[20:41:45] <kl_eisbaer1> cboltz: that does not really work regarding "release often, release early", right?

[20:42:04] <kl_eisbaer1> cboltz: because in that case nobody can jump in and help if you have no documentation

[20:42:15] <tampakrap> regarding salt: we have new NTP servers set up by Rudi and me managed fully in salt

[20:42:22] <Ada_Lovelace> We have got different extensions which need old packages...

[20:42:28] <kl_eisbaer1> cboltz: you might get also some additional testers/contributors by making some "marketing"

[20:42:49] <tampakrap> they are running sle and are managed by the suse salt master, I will "upgrade" them to leap and move them to the opensuse salt

[20:42:57] <cboltz> now we are back at the dependency chain

[20:43:09] <cboltz> I need the authentification running because testing makes sense

[20:43:29] <tampakrap> second news regarding salt: powerdns for slave nameserver is fully in salt, chip.o.o is our slave DNS server set up by darix and me

[20:43:34] <cboltz> (the current way of "find and use the 'lost password' link is slightly insane ;-)

[20:43:39] <kl_eisbaer1> cboltz: ...and if you would document the dependency chains in our admin-wiki, we might know better how to help you ;-)

[20:43:47] <tampakrap> and right now I am working on rsyslog clients, then will work on rsyslog server

[20:44:12] <cboltz> ;-)

[20:45:03] <tampakrap> rsyslog and powerdns formulas already got full opensuse support as well

[20:45:07] <cboltz> about salt - I wrote a role for AppArmor: https://gitlab.opensuse.org/infra/salt/merge_requests/10

[20:45:48] <cboltz> it might become a formula later

[20:46:21] <tampakrap> yes, we need to work on this as well

[20:46:31] <tampakrap> I want also to extract profile/zypper to a formula

[20:46:48] <cboltz> as soon as it gets merged, all salt-managed machines will get the default profiles (from apparmor-profiles package)

[20:46:55] <cboltz> and you can easily add your own profiles

[20:47:30] <kl_eisbaer1> +1 from me

[20:47:34] <tampakrap> there are already apparmor profiles running on some machines, should we import them also to salt before we merge that one?

[20:47:58] <kl_eisbaer1> tampakrap: release early, release often, I would say...

[20:48:10] <cboltz> we can import them whenever we have time - my salt code won't destroy anything ;-)

[20:48:23] <tampakrap> cool

[20:48:27] <kl_eisbaer1> I do not see where the commit can break something that was not broken from the beginning

[20:48:29] <tampakrap> also https://gitlab.opensuse.org/infra/salt/merge_requests/11 this got merged a few mins ago

[20:49:04] <tampakrap> no, I mean if the commit will cause salt to overwrite apparmor profiles that are in the machines set up manually

[20:49:44] <kl_eisbaer1> tampakrap: sorry, but how? Can you point me to the command that is doing this ?

[20:49:53] <cboltz> the current version will install the apparmor-profiles package which might *in theory* overwrite something

[20:50:25] <cboltz> but the profiles in that packages are installed on nearly every openSUSE system in the default install, so I'm sure they won't break anything

[20:51:11] <kl_eisbaer1> IMHO the files are already marked as %config(noreplace) - so I do not see anything that might break because of a package that should be installed on productive machines anyway

[20:51:45] <cboltz> indeed

[20:52:09] <pjessen> guys, you're digressing. The agenda says "naming pattern for VMs".

[20:52:22] <kl_eisbaer1> tampakrap: what about accepting it tomorrow - and we will have a close look at the nodes during the day ?

[20:52:41] <kl_eisbaer1> pjessen: correct

[20:52:53] <kl_eisbaer1> I guess that topic comes from tampakrap, right?

[20:53:29] <kl_eisbaer1> tampakrap: ?

[20:53:32] <Ada_Lovelace> I thought we had this topic some months ago on the mailing list...

[20:53:50] <tampakrap> kl_eisbaer1: regarding the overwrite - the scenario is: I have written a file by hand, then I use file.managed in salt and overwrite the content

[20:54:14] <tampakrap> regarding accepting it tomorrow, I was hoping that we can finish it with cboltz today

[20:54:20] <tampakrap> there are a few comments I need to make there

[20:54:36] <tampakrap> so cboltz if you got time after the meeting we can do it

[20:54:41] <cboltz> tampakrap: right now, there isn't any custom AppArmor profile in salt yet, "just" the framework to handle them

[20:54:52] <tampakrap> okay

[20:55:01] <kl_eisbaer1> tampakrap: regarding "accepting it today" - in that case you need to take care of the machines on your own, as I need to go to sleep after the meeting ;-)

[20:55:07] <tampakrap> I understood it, wanted to make sure only that this scenario happens

[20:55:27] <kl_eisbaer1> tampakrap: VM naming scheme ?

[20:55:29] <tampakrap> good point, so we can finish the code today and deploy only in a couple of machines

[20:55:38] <tampakrap> and finish the deployment tomorrow

[20:55:58] <tampakrap> so naming scheme

[20:56:44] <tampakrap> first the domain: it will be either $location.infra.o.o or just infra.o.o - I personally believe we don't really need the location on the FQDN of the machine

[20:56:53] <tampakrap> it is marked as a grain

[20:57:16] <tampakrap> makes sense?

[20:57:17] <pjessen> agree, location is superlfuous.

[20:57:27] <cboltz> indeed, good point

[20:57:50] <Ada_Lovelace> It depends on whether we want to have geo clustering in the future.

[20:58:12] <Ada_Lovelace> If no, then yes (own experience). ;)

[20:58:19] <kl_eisbaer1> Ada_Lovelace: I don't think that we need it for the infra.o.o domain

[20:58:34] <pjessen> geo clustering happens behind tho scenes.

[20:58:36] <tampakrap> we don't

[20:58:49] <kl_eisbaer1> so $machine.infra.o.o ?

[20:58:55] <tampakrap> the infra.o.o will be obvious behind the VPN, and on each machine's `hostname -f`

[20:58:55] <Ada_Lovelace> yes

[20:59:02] <tampakrap> and also an A record

[20:59:08] <tampakrap> also behind the openvpn

[20:59:31] <pjessen> right

[20:59:50] <tampakrap> so since the location will not be on the domain, this means that the hostname has to be unique on each machine

[21:00:05] <tampakrap> regarding the naming pattern of the hostnames, flame on :)

[21:00:20] <Ada_Lovelace> next topic

[21:00:38] <pjessen> hostnames: two syllable names, in english, french or german.

[21:01:01] <Ada_Lovelace> french?

[21:01:10] <kl_eisbaer1> pjessen: fine with me

[21:01:14] <cboltz> I'd vote for boring, numbered hostnames like "wiki1"

[21:01:29] <Ada_Lovelace> +1

[21:01:38] <pjessen> cboltz: please no.

[21:01:49] <Ada_Lovelace> so you can know for what something is...

[21:01:50] <kl_eisbaer1> cboltz: in that case I vote for plain chinese hostnames ;-)

[21:02:20] <cboltz> let me warn you that I like crazy ideas ;-))

[21:02:22] <pjessen> known names that people generally know - I had trouble with baloo ....

[21:02:56] <kl_eisbaer1> 维客.infra.opensuse.org

[21:03:06] <tampakrap> the problem with the cartoon names comes because: 1) we don't define the roles in salt on ALL machines 2) we don't create automatically a cname based on the role

[21:03:17] <kl_eisbaer1> looks at least interesting - and will increase the need for better monitor resolutions for me ;-)

[21:03:24] <pjessen> hostname != service names - "wiki1" is good as CNAME to <whatever hostbame>

[21:03:43] <tampakrap> so if baloo had a role 'lists' on salt, and it would create automatically your CNAME, and maybe also add it in the motd and/or in the bash shell like baloo (lists) $

[21:03:53] <tampakrap> then whatever name we pick will be problematic :)

[21:04:06] <pjessen> problem with cartoon names - they're not unviersally known. Gaston Lagaffe anyone?

[21:04:24] <tampakrap> there is a specific list on where to pick those names

[21:05:06] <pjessen> anyway, two syllables is good and memorable. London, Dresden, Airbus - plenty to be found.

[21:05:43] <cboltz> IMHO the problem with cartoon names or two syllables is that they don't give you an idea what the host does

[21:06:19] <pjessen> true, but add a service name for that.

[21:06:20] <cboltz> so I'd really prefer the boring "wiki1" way - even if we have "wiki 125" one day ;-)

[21:06:24] <tampakrap> exactly my point, so unless we don't set up roles and take advantage of them, pick whatever you want. the result will be confusing

[21:06:45] <kl_eisbaer1> cboltz: correct. But you should be able to use the alias to log in to the machine (ssh wiki1 will log you in to boing for example)

[21:07:10] <Ada_Lovelace> cboltz: The funniest story about hostnames in my work experience is the word "Wurstbrot" in the work documentation for HR. :)

[21:07:19] <kl_eisbaer1> my main concern about those hostnames is more the PS1 output and the serial console naming

[21:07:26] <Ada_Lovelace> And Wurstbrot was a hostname.

[21:07:49] <cboltz> sounds like a bad company for vegetarians ;-)

[21:08:05] <kl_eisbaer1> Ada_Lovelace: can easily be topped: ismirwurscht.suse.de still exists ;-)

[21:08:20] <pjessen> hahaha

[21:08:58] <kl_eisbaer1> but I guess tampakrap wants a solution today for the hostnames, right ?

[21:09:02] <pjessen> bahnhof.suse.de ?

[21:09:04] <cboltz> sounds like the perfect solution for the *.infra.opensuse.org hostnames - ismirwurscht, mirdochegal etc. ;-)

[21:09:17] <kl_eisbaer1> Host bahnhof.suse.de not found: 3(NXDOMAIN)

[21:09:38] <pjessen> see, good one for a hostname - two syllables

[21:09:49] <kl_eisbaer1> but: "senil.suse.de has address 192.168.1.129"

[21:10:04] <tampakrap> not really :)

[21:10:13] <kl_eisbaer1> ...and debil exists, too ;-)

[21:10:24] <Ada_Lovelace> Enough with funny hostnames...

[21:10:31] <Ada_Lovelace> Next topic

[21:10:32] <tampakrap> I would prefer that someone works on populating the roles to motd and/or PS1

[21:10:38] <pjessen> where is the emoticon for ROFLAO

[21:11:19] <kl_eisbaer1> tampakrap: but what happens if a host has more than one role ?

[21:11:57] <pjessen> two CNAMES pointing to the same host?

[21:12:02] <tampakrap> it will have the roles comma separated in the PS1

[21:12:12] <kl_eisbaer1> :D

[21:12:25] <tampakrap> also, this host is candidate for splitting the service to another host

[21:12:38] <kl_eisbaer1> root@mailinglists,ircbot,webserver ~#

[21:13:21] <kl_eisbaer1> ...so we need to think about which role is worth to become mentioned in "PS1"

[21:13:32] <tampakrap> root@funnyname (lists, ircbot, webserver) ~#

[21:13:59] <kl_eisbaer1> ...in that case, we can use whatever name the admin of the machine prefers, right?

[21:14:13] <Ada_Lovelace> seems ;-)

[21:14:15] <tampakrap> sure

[21:14:21] <tampakrap> that's also a possibility

[21:14:22] <kl_eisbaer1> we just need to watch that the role line does not become too long for the serial console

[21:14:37] <pjessen> actually, that sounds good.

[21:14:57] <cboltz> kl_eisbaer1: whatever role(s) is/are listed in pillar/id/* (which also means roles included in one of that roles won't get listed)

[21:15:40] <kl_eisbaer1> I guess, we should start with that and evaluate next year if it paid out

[21:16:25] <tampakrap> agreed

[21:16:36] <kl_eisbaer1> pjessen, Ada_Lovelace, cboltz ?

[21:16:48] <Ada_Lovelace> agreed

[21:16:48] <cboltz> agreed

[21:16:52] <pjessen> agreed

[21:17:13] <kl_eisbaer1> next topic. "Support other Open Source communities"

[21:17:26] <pjessen> yeah, I was wondering about that one

[21:17:28] <kl_eisbaer1> I wrote something about this in the ticket already

[21:17:42] <kl_eisbaer1> while SUSE lists https://www.suse.com/company/open-source/

[21:17:56] <kl_eisbaer1> openSUSE just has: http://suse.github.io/

[21:18:00] <Ada_Lovelace> Why not, if we have got capacities available.

[21:18:18] <pjessen> Ada: that is exactly the question.

[21:18:29] <kl_eisbaer1> so I was wondering if we could not check if we want to support - for example - the NTP pool with a machine or other projects

[21:18:38] <Ada_Lovelace> I would say, yes.

[21:19:04] <kl_eisbaer1> I would say: technically, we have capacity - but not admin / aka time wise

[21:19:07] <cboltz> I agree that we can and should do it, but a) someone has to do it ;-) and b) it should not stop us from getting our own stuff done

[21:19:38] <pjessen> I would say yes, no question about it, but it has to be up to the admin.

[21:19:39] <kl_eisbaer1> but we should mention it somewhere, if we can do it

[21:20:09] <kl_eisbaer1> keyserver.o.o is one example: I am maintaining it anyway, so getting it added to the public pool was a low brainer

[21:20:11] <Ada_Lovelace> How about, technical yes, but communities need own volunteers?

[21:20:41] <kl_eisbaer1> Ada_Lovelace: agreed

[21:20:56] <kl_eisbaer1> I just wanted to mentoin two points:

[21:21:14] <kl_eisbaer1> a) openSUSE likes to support, if community needs it

[21:21:27] <pjessen> if we, as the openUSE community have resources to spare, we should offer them, as we can

[21:21:30] <kl_eisbaer1> b) openSUSE has an own interest not to waste resources ;-)

[21:21:45] <pjessen> (b) very important

[21:21:54] <tampakrap> totally support the idea, let's do it

[21:22:24] <kl_eisbaer1> ...and do not forget to talk about it ;-)

[21:22:35] <Ada_Lovelace> ;)

[21:22:35] <kl_eisbaer1> but I guess that's all about this topic at the moment

[21:22:48] <Ada_Lovelace> Theo can talk about it at the oSC.

[21:22:59] <tampakrap> you are in my mind

[21:23:14] <pjessen> any immedciate candidates ?

[21:23:46] <tampakrap> our NTP servers could be

[21:23:54] <tampakrap> they need public IP and public domain

[21:24:09] <pjessen> and protection

[21:24:28] <kl_eisbaer1> ...a lot of protection, as they would open direct access to the infra.o.o network ...

[21:25:00] <tampakrap> true

[21:25:18] <darix> do NOT use our internal instances for the pool

[21:25:23] <pjessen> ntp is another favourite of mine, been running a stratus 1 mirror for ten years. (from dcf77)

[21:26:04] <kl_eisbaer1> pjessen: /me is wondering what interesting stuff you are NOT doing ;-)

[21:26:23] <kl_eisbaer1> but I guess we leave the topic for now and switch to the next one?

[21:26:30] <kl_eisbaer1> Ideas / plans for the Heroes workshop at oSC17

[21:27:15] <darix> beer lots of beer?

[21:27:17] <kl_eisbaer1> who added this ?

[21:27:31] <cboltz> I added it

[21:27:37] <Ada_Lovelace> You as the organisator?

[21:28:01] <kl_eisbaer1> darix: "malt beer"?

[21:28:12] <kl_eisbaer1> Ada_Lovelace: no, that's why I'm asking...

[21:28:19] <darix> mate beer

[21:28:21] <kl_eisbaer1> cboltz: so please start :-)

[21:28:30] <cboltz> the basic question is: do we want to have a pure workshop with discussions and hands-on, or do we want to have some lightning talks?

[21:28:31] <pjessen> osc17 is in Nürnberg / home ?

[21:28:35] <kl_eisbaer1> darix: .oO :D

[21:28:50] <kl_eisbaer1> pjessen: yes. same location as last year

[21:28:55] <Ada_Lovelace> I would bring some fellow students with me. ;)

[21:29:09] <kl_eisbaer1> Ada_Lovelace: to the workshop ?

[21:29:23] <Ada_Lovelace> Why not? They should learn. ^^

[21:29:30] <pjessen> I'll have to think about a little road-trip

[21:29:40] <kl_eisbaer1> pjessen: definitively !!!!!!!!!!

[21:29:50] <cboltz> I have to admit that the reason for asking is a bit selfish - Sarah and I had proposed a talk which didn't fit into the overly crowded schedule, so we might have some topics for lightning talks

[21:29:53] <kl_eisbaer1> pjessen: you know about the "travel support programm" ?

[21:29:58] <Ada_Lovelace> We have to restructure our Linux laboratory in the next semester.

[21:30:41] <pjessen> yeah, maybe I can file my petrol-receipts :-)

[21:30:46] <kl_eisbaer1> Ada_Lovelace: ...and what has "restructuring the Linux laboratory" to do with a workshop that was planned to sit together and work (for example) on wiki / openID / freeIPA and other stuff ?

[21:31:00] <kl_eisbaer1> pjessen: ...and your Hotel...

[21:31:30] <Ada_Lovelace> We will do something like that,too. And they can see how we are doing that in the community.

[21:31:49] <kl_eisbaer1> Ada_Lovelace: my original plan was to have a small room with people who want to work together on different topics (4 eyes coding)

[21:32:15] <Ada_Lovelace> Ok. I thought about bringing them to us...

[21:32:56] <kl_eisbaer1> I you bring a huge amount of people, I need to reconsider the original plan

[21:33:15] <Ada_Lovelace> Not such a large number.

[21:33:17] <kl_eisbaer1> ...and that would mean that we probably do not end up in "getting things done" - but more in "talking about things"

[21:33:40] <kl_eisbaer1> that's not a big deal - but this would, from my pow, the consequence

[21:33:53] <Ada_Lovelace> Then I let them in other talks...

[21:34:19] <kl_eisbaer1> while I'm happy to share knowledge and also to give some presentations (if needed), I would vote to use the time together to get things done instead

[21:34:49] <Ada_Lovelace> Agreed

[21:35:03] <kl_eisbaer1> I -as example - want to learn from tampakrap how I could test my Salt changes on my nodes before I submit them to git

[21:35:32] <kl_eisbaer1> ...and we might want to get the new wiki stuff online together

[21:35:50] <kl_eisbaer1> saltifying more machines is another "topic"

[21:35:58] <Ada_Lovelace> That would be great! :)

[21:35:58] <kl_eisbaer1> so - to make it short:

[21:36:02] <tampakrap> services, not machines

[21:36:15] <kl_eisbaer1> there is not really a full, public schedule for this "workshop"

[21:36:40] <kl_eisbaer1> as I wanted to do something similar we did during Christmas

[21:36:52] <kl_eisbaer1> but this time the other way around: less talking, more coding ;-)

[21:37:32] <tampakrap> talk is cheap, show me the code

[21:37:33] <kl_eisbaer1> there will definitively some learning - and some guys will also be asked to put their console on a screen

[21:37:57] <kl_eisbaer1> but I want to use the workshop to "work" (and not to talk about shopping ;-)

[21:38:43] <kl_eisbaer1> Ada_Lovelace, cboltz: I hope that makes my original idea a bit more clear ?

[21:38:51] <Ada_Lovelace> Yes.

[21:38:51] <cboltz> yes, it does

[21:39:02] <kl_eisbaer1> sorry if the description in the event page was not so clear

[21:39:27] <kl_eisbaer1> does it make sense to everyone ?

[21:39:30] <Ada_Lovelace> But that sounds like more than the planned time. ;)

[21:39:53] <kl_eisbaer1> I asked for 3 days and got 3 hours ... ;-)

[21:39:57] <pjessen> next item - "mirror status - 31 open tickets "

[21:40:53] <pjessen> I added this - mostly a little egotistical. One of my guys set up to mirror for Switzerland, but it's been waiting

[21:41:02] <cboltz> kl_eisbaer1: talking about the workshop description: can you please add wine as another option? I don't like beer ;-)

[21:41:17] <kl_eisbaer1> cboltz: only if you bring something with you

[21:41:19] <pjessen> schnapps?

[21:41:35] <kl_eisbaer1> pjessen: I guess switzerland has more to give ;-)

[21:41:55] <kl_eisbaer1> pjessen: but schnapps might be a good "starter" :-)

[21:42:29] <cboltz> kl_eisbaer1: should be possible, but I can't promise that it will be cooled as it should be (I doubt Z-Bau will let me use their fridge)

[21:42:31] <kl_eisbaer1> pjessen: I asume that most tickets are currently stalled because Max is busy with preparing the oSC17. Is this correct, Ada_Lovelace?

[21:42:58] <Ada_Lovelace> It seems.

[21:43:08] <cboltz> it looks like *everybody* who could handle mirror tickets is busy

[21:43:20] <Ada_Lovelace> I'll ask what he is doing.

[21:43:39] <pjessen> Yes, I think so too. I don't want to push anyone, but mirroing has become very public lately

[21:43:54] <Ada_Lovelace> I'll say it.

[21:44:41] <pjessen> Can I help out with mirrroing?

[21:45:00] <tampakrap> not yet unfortunately

[21:45:05] <pjessen> insert 'r'

[21:45:17] <tampakrap> the important service is still behind the suse network

[21:45:38] <pjessen> okay, just offering. Let me know if I can help.

[21:46:00] <kl_eisbaer1> pjessen: IMHO it would be more helpful if someone can finish the work on mirrorpinky, so admins would be able to administrate their mirror servers on their own

[21:46:14] <tampakrap> that as well yes

[21:46:30] <kl_eisbaer1> https://github.com/openSUSE/mirrorpinky

[21:46:38] <darix> tampakrap: that one you can move tonight. just needs ram

[21:46:49] <pjessen> that sounds really cool, but it's news ro me. mirrorpinky?

[21:47:18] <kl_eisbaer1> pjessen: "A self management frontend for the mirrorbrain.org database"

[21:47:42] <darix> pjessen: mirrorpinky and mirrorbrain

[21:48:12] <pjessen> I'll have a look - the more we can offload to the mirror the better

[21:49:07] <kl_eisbaer1> pjessen: right. If you find someone with some Rails-skills, that would be perfect

[21:49:59] <pjessen> rails ... umm, not sure. not my cup of tea.

[21:50:21] <kl_eisbaer1> ...at the end, when everything is stored in the database, we "just" need some commandline scripts to adapt the settings (like writting the "host allow" line in the rsyncd.conf for example)

[21:51:14] <kl_eisbaer1> that way adding/deleting/editing a mirror could be done by any admin himself (once he has registered for an openSUSE account)

[21:52:30] <kl_eisbaer1> pjessen: anything more about this topic?

[21:52:56] <pjessen> I guess we're just short on resources, so wait and see.

[21:53:23] <kl_eisbaer1> ok

[21:53:48] <kl_eisbaer1> so the only topic left is "Salt Stack for Icinga Checks with ZeroMQ", added by Ada_Lovelace

[21:54:00] <kl_eisbaer1> but I guess we skip this as she left already

[21:55:44] <kl_eisbaer1> ending meeting ?

[21:55:57] <tampakrap> yes!

[21:56:15] <cboltz> yes

[21:56:23] <tampakrap> last thing I wanted to say: long live openSUSE Leap 15!

[21:57:08] <pjessen> see you guys later

[21:57:15] <cboltz> I expect a lifetime of at least 3 years - and then we'll have Leap 16 ;-)

[21:57:17] <kl_eisbaer1> bye!

[21:57:24] <pjessen> ciao

[21:57:34] <kl_eisbaer1> cboltz: voting for 21!