Puppet » Puppet Dashboard

Let’s start with a question, if you have 500 nodes, how do you automatically create a nagios configuration file for these hosts? What about a munin configuration file? How do you have this regenerated as you spin up new hosts?

Everything as a Resource? (EaaR)

I wanted to search through all of my known hosts for different metadata, such as being tagged as a certain server, and return an object with information about these hosts. Then iterate this object to create a configuration file via a template.

Bryan McLellan wrote:

Let’s start with a question, if you have 500 nodes, how do you automatically create a nagios configuration file for these hosts? What about a munin configuration file? How do you have this regenerated as you spin up new hosts?

Everything as a Resource? (EaaR)

I wanted to search through all of my known hosts for different metadata, such as being tagged as a certain server, and return an object with information about these hosts. Then iterate this object to create a configuration file via a template.

Yeah, it’s much more ‘everything as a resource’ – at least, that’s the philosophy we’re trying to work with, rather than just encouraging what amounts to database queries to fill in templates. It’s fantastically difficult to know what data is affecting what host if you just do the queries, but it’s reasonable to come up with a plan for managing dependencies if you stick to export/collect.