Hi,
I'm using puppet with a centralized puppetmaster pushing config to
many client nodes. Most of the configuration files that puppet
manages are static and served via the puppet fileserver (running on
the puppetmaster). I often find myself making changes to a node's
config file, testing those c
On Tuesday 30 Nov 2010 12:58:33 gdb wrote:
> Hi,
>
> I'm using puppet with a centralized puppetmaster pushing config to
> many client nodes. Most of the configuration files that puppet
> manages are static and served via the puppet fileserver (running on
> the puppetmaster). I often find myself
gdb writes:
> I'm using puppet with a centralized puppetmaster pushing config to many
> client nodes. Most of the configuration files that puppet manages are
> static and served via the puppet fileserver (running on the puppetmaster).
> I often find myself making changes to a node's config file,
The issue becomes that while it would offer you a time saver in the
short term, it would give you headaches later with security and as you
try to expand out your puppet infrastructure, which you will have to
do once you reach at the very least 50 hosts. The best solution that I
could offer is you w
