On Friday, April 27, 2012 8:28:32 AM UTC-7, Luke Bigum wrote:
>
> What problem are you trying to solve that you think you need Puppet? The
> recommended Puppet way would be to package your binaries and use Puppet
> to enforce new versions of the package. You said your Admins are used to
> just
Ok... Not a small job ;-)
For config files where it's exactly the same on all machines, that's
super easy. It's just stored once on the Puppet Master and file is
managed on all Puppet Agents.
I'm not sure if rdist has some templating system in it for machine
specific config files, but Puppet
On Friday, April 27, 2012 8:11:38 AM UTC-7, Luke Bigum wrote:
>
> Hi Philip,
>
> I've never used rdist before, but I've just checked the man page
> quickly... How many servers have you got that's you've got a 260 MiB and
> 5800 file repository? Is this a raw file count or are some of those
>
Hi Philip,
I've never used rdist before, but I've just checked the man page
quickly... How many servers have you got that's you've got a 260 MiB and
5800 file repository? Is this a raw file count or are some of those
files redundant (like ldap.conf going out to every single server and
being c
We have an existing "management system" of sorts, based on rdist. I'd like
to know the best way to migrate it to using puppet.
Currently, we have a local binaries tree, rdisted out nightly. We also
make use of rdist's extra capability to trigger scripts when and if named
files are updated.
I'
