----- 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.


> What about querying puppet.conf for paths? Or using Puppet.settings from
> the puppet gem? Maybe this could be implemented with a "defaults provider"
> thing like puppet types/providers do to prevent a hard dependency with
> puppet. But I'm really no export in this area. :-)

yes, its possible, but with AIO there's only so many things to consider so
it does just work.

-- 

--- 
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.

Reply via email to