----- Original Message ----- > From: "R. I. Pienaar" <[email protected]> > To: "mcollective-users" <[email protected]> > Sent: Wednesday, 16 November, 2016 17:05:21 > Subject: Re: [mcollective-users] choria and puppet defaults
> ----- Original Message ----- >> From: "R. I. Pienaar" <[email protected]> >> To: "mcollective-users" <[email protected]> >> Sent: Wednesday, 16 November, 2016 16:08:27 >> Subject: Re: [mcollective-users] choria and puppet defaults > >> ----- Original Message ----- >>> From: "Thomas Müller" <[email protected]> >>> To: "mcollective-users" <[email protected]> >>> Sent: Wednesday, 16 November, 2016 12:41:42 >>> Subject: [mcollective-users] choria and puppet defaults >> >>> hi >>> >>> (second try, first post seems to be vanished somewhere) >>> >>> Just recently learned about the mcollective-choria. Very interesting! >>> Actually the longish deployment guide was bit scaring. :-) >>> >>> Really neat idea about presetting sane defaults. I can see some issue with >>> installations i've seen. many of them do not use default paths for >>> puppet.conf -> agent -> server and ssldir. The hardcoded defaults would not >>> match with this configuration. >> >> Choria is for AIO Puppet 4, it configures it accordingly. Puppet plugin had >> wrong defaults, I've fixed those so it works with AIO by default. > > Ah your other mail was a bit clearer, I am not against making them > configurable > and would accept a PR, parsing puppet.conf correctly is reasonably expensive > via the Puppet libraries but can be done. > > You can open a issue if you like at the choria project There's actually an existing issue for this https://github.com/ripienaar/mcollective-choria/issues/55 I'll comment there -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
