This feature (which prob needs some more work) allows the system to keep
track of all of the changes that have occurred and how they relate to puppet
manifest versions.
I am doing the following in a custom report
if report is related to a new puppet code release - log it under that code
release
else if it is related to some unexpected event (prob a user changed a file
or its a manifest bug) -
send an email
determining how puppet reports relate to code versions can be unreliable.
You can only know the code version when the custom report runs and not when
the puppet agent runs. This means that the version that you can capture is
not necessarily correct. This feature takes care of that problem by saving
code version at puppet agent runtime.
Of coarse there are other hackish ways to correlate puppet agent runtimes
with correct versioning, but it would be difficult to argue that they are
better than this implementation.
On Sat, Oct 10, 2009 at 6:19 PM, Carl.caum <carl.c...@gmail.com> wrote:
> I was looking at this option last nigh and perhaps I'm just dense, but
> I'm not sure how it will benefit me. In theory, I know which version I
> have in production/testing/dev by which subversion/git tag I have
> checked out on the master. Am I missing the point? Can someone provide
> an example when this would be useful?
>
>
> On Oct 10, 2009, at 2:29 AM, James Turnbull <ja...@lovedthanlost.net>
> wrote:
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Just thought I'd call the lists attention to a feature that we
> missed documenting for the 0.25.0 release.
>
> A new configuration option, config_version, is now available:
>
> config_version = /usr/local/bin/return_version
>
> The option allows you to specify a command that returns a version
> for the configuration that is being applied to your hosts. The
> command should return a string, such as a version number or name.
>
> Puppet then runs this command at compile time. Each resource is
> marked with the value returned from this command. This value is also
> added to the log instance, serialised and sent along with any report
> generated. This allows you to parse your report output and ascertain
> which configuration version was used to generate the resource.
>
>
> http://reductivelabs.com/trac/puppet/wiki/ReleaseNotes#configuration-versioning
>
> Regards
>
> James Turnbull
>
> - --
> Author of:
> * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
> * Pulling Strings with Puppet (http://tinyurl.com/pupbook)
> * Pro Nagios 2.0 (http://tinyurl.com/pronagios)
> * Hardening Linux (http://tinyurl.com/hardeninglinux)
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - <http://enigmail.mozdev.org/>
> http://enigmail.mozdev.org/
>
> iQEVAwUBStA3tSFa/lDkFHAyAQK2Rwf/ZZ36y+2A3p3Y+fkMPTGHqSF/OxK8rmfr
> gQ9KAgSxdLHQt4+VmE4LKM1HMOmRoIJo7jthFDdp0MRveOxDycJEdKkhSNOHyAsF
> EhlgONMo4T36cBPb1zJSi6yhFkdOSxkn8Q623zRR/P3crUfWMf/xNMzabmCB2zy0
> LKRrW6CzqwPtlSr3ye9Ysiqqpf+rZuRjNgUliqVTfSuBD2PETTGKpHXri2DZ39lB
> /+Qe0fyc+GhN3plobEUpHaadpf9YOtnIpL97RthMDvyHCrQKD3eRHey+C3o0EfZg
> kAcPJb+Y9qJ/ZLK86nhte+5BLwJEwJcvJea2NXtvBqeaDvHqHMveVQ==
> =vSOU
> -----END PGP SIGNATURE-----
>
>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
