On 2/12/10 2:10 AM, Alan Barrett wrote:
Not exactly, but that would probably be acceptable. What actually happens today is that puppetd is not run at all on the client unless an authorised change is known to be ready for deployment; then puppetd is run in --noop mode to verify that the changes it wants to make are as expected; finallly puppetd is run in --no-noop mode.
What happens if a manual change is made outside of the scope of your scheduled Puppet changes? For example, someone tweaks /etc/syslog.conf. Puppet manages it but because you don't run regular noops, how will you know it needs to be changed back? Do plan around the organization (Ops or IT or w/e) not knowing it was changed? Since you don't have regular reports, how do you find out?
-scott -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
