On 24/05/11 11:24, Felix Frank wrote:
On 05/16/2011 09:14 PM, Jonathan Gazeley wrote:
We have configured puppet to manage its own puppet.conf on clients, and
to ensure that puppetd is running on all hosts.
Hi,
maybe I'm being dense, but this doesn't address the original issue, does it?
If you manage to deploy an utterly broken config, puppet won't be able
to get itself back up to speed because it cannot start anymore.
Am I missing something here?
No, you are correct. If I deploy a garbage config, it will break the
puppet clients. But the benefit is that I can easily deploy a modified
puppet config to many clients if we need to add extra config parameters
in future.
I can mitigate the risk by carefully testing the new puppet.conf on an
isolated dev machine.
Cheers,
Jonathan
Cheers,
Felix
--
----------------------------
Jonathan Gazeley
Network Specialist
Residential & Mobile IT
IT Services
University of Bristol
----------------------------
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
