Hey;
I'm planning out a module to handle syslog config in my environment. I
know there are modules on puppet forge already but am interested in the
learning opportunity. .
Here's the scenario:
* The syslog config files will all be the same except for forwarders.
* We have three datacenters whose hosts forward to a DC specific collector.
* Production systems and select others also foward to a SIEM
* DMZ systems forward to a third collector in addition to the previous two.
This seems like a template would work well here. Don't know what that
would look like yet but there are plenty of examples on the net. I'm
curious how about hiera interaction - specifically multiple remote
collectors specified.
Here's my hierarchy:
:hierarchy:
- "hosts/%{facts.hostname}"
- "environments/%{facts.environment}"
- "host_env/%{facts.env}"
- "dc/%{facts.dc}"
- "os/%{facts.osfamily}"
- common
in the appropriate dc.yaml file, I'm planning on:
---
dolsyslog::remote: '1.2.3.4'
Similar set up in hosts_env/prd.yaml
---
dolsyslog::remote: '2.3.4.5'
DMZ and specific hosts will be set up in the hosts hieradata directory.
So. long build up to a relatively short question. Can a template be made
to iterate across multiple remotes identified like that? It seems like
it'd be too good to be true but worth the question. If my suspicion is
correct, is there a better way to work this?
Thanks for your time and help.
Doug O'Leary
--
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/5fe212c3-6839-4f74-8580-decd7fed941e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
