We noticed that our puppet reports and our puppet node data stored on our
puppet servers is always written out in the form of the 'node name'. So
when we use a node name like 'prod_webserver' across many webserver
machines, we get a tree of reports and node data like this:
/var/lib/puppet/yaml/node/prod_web.yaml
> /var/lib/puppet/yaml/facts/prod_web.yaml
> /var/lib/puppet/reports/prod_web
> /var/lib/puppet/reports/prod_web/201408130200.yaml
> /var/lib/puppet/reports/prod_web/201408140811.yaml
> /var/lib/puppet/reports/prod_web/201408121328.yaml
> /var/lib/puppet/reports/prod_web/201408130743.yaml
> /var/lib/puppet/reports/prod_web/201408140454.yaml
Where each of those reports likely reflects a compilation run for a
different host... and the facts/node files at the top are getting
constantly re-written as new clients come in.
Is there a way to change the behavior of the data there to be written out
based on the ${::fqdn} of the host (or certname) rather than its node name?
(our client puppet configs ...)
> [main]
> ...
> node_name = facter
> node_name_fact = puppet_node
(a client puppet fact file...)
> puppet_node=prod_web
> puppet_environment=production
> package=frontend=some-version-here
> app_group=us1
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/6d296d23-d317-4f3e-ad6c-338af5be68bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
