On 11/08/2012 10:49 AM, James Fellows wrote:

For me, the benefit of the header is being able to immediately tell
whether the file has been modified by someone or something since the
last puppet run (by comparing the header to the last modified
timestamp on the file).

You can already do that with puppet noop run:

# puppet agent -t --noop

which won't modify system but only announce what changes will be applied on the next "real" agent run. If you find your file in the list of resources that puppet wants to (re)appy, you can be certain that someone has messed around that resource. When it was done can be seen by filesystem timestamps.

If, on the other hand, puppet was the last who modified that file and you want to know when, again you can use the filesystem timestamps.

Now, the only corner case in which I can see potential use of that kind of header is if someone changed manifests on your master, and puppet now wants to modify the file - which was last modified also by puppet. But if you use some kind of VCS for keeping track of your manifests, you could know even that.


Would others find it useful?  If so I could raise a feature request
for it to open a formal discussion, and (one day, maybe!) fork and
contribute to the code.

That kind of header IMHO only brings one thing to the table - and that is fancy look :) Other than that I find it pretty much useless.

But then again I don't mind useless as long as it doesn't do performance penalties. But this does impose additional strain on both the master (catalog compilation time increase) and the agents (run time increase). And management software should be as non-intrusive as possible. I want puppet, zabbix, ossec and other management related agents to consume as little resources as possible...


--
Jakov Sosic
www.srce.unizg.hr

--
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.

Reply via email to