Hi Chris,
We have configured puppet to manage its own puppet.conf on clients, and
to ensure that puppetd is running on all hosts. However it does not
manage puppet.conf on the puppetmaster, so if we accidentally mess up
the config, we won't break the puppetmaster.
The hostname of the puppetmaster is hard-coded, in our case. Can anyone
think of a better way of identifying the puppetmaster, so our manifests
will run anywhere, if we decide to make a different machine the
puppetmaster?
Cheers,
Jonathan
----------------------------
Jonathan Gazeley
Systems Support Specialist
ResNet | Wireless & VPN Team
IT Services
University of Bristol
----------------------------
On 05/16/2011 05:09 PM, Chris Phillips wrote:
Hi,
Is there a general feel on whether puppet should look after its own
client configuration files and service status? I'd not foresee problems
about a "service ensure enabled" for puppetd and a file object for the
puppet.conf but clearly wouldn't want to risk locking ourselves out of
the clients from a bad config file being sent down etc.
Thanks
Chris
--
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.
--
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.
