Issue #2986 has been updated by Luke Kanies.
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. ---------------------------------------- Feature #2986: Added support for facter facts and node attributes http://projects.puppetlabs.com/issues/2986 Author: James Turnbull Status: Needs more information Priority: Normal Assigned to: Category: Target version: Keywords: facter fact node database DSL Branch: Affected URL: Components: 1) store facter/custom node attributes in the dashboard 2) add DSL language to search and interact with this data -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
