Wout wrote: > On Oct 8, 10:38 am, David Schmitt <da...@dasz.at> wrote: >> While it may be quite an initial implementation hump, it will probably >> save you many headaches down the line if you look into using an external >> node classifier. There you can maintain your system's and architecture's >> information in a format of your choosing and prepare the data for >> puppet's consumption on a need-to-know basis. >> >> See the wiki for more >> information:http://reductivelabs.com/trac/puppet/wiki/ExternalNodes > > Thanks for the fast reply :) Creating a shell script to produce a YAML > output with (only) the information that node needs looks very > interesting. Too bad you cannot define resources for a specific node, > but I do not think this will be necessary in my setup.
This is a common "problem" with external nodes, but that can mostly be worked around by including the hostname as class and using that to include manual overrides. If you need even more dynamic stuff, get Volcane's extlookup() function: http://nephilim.ml.org/~rip/puppet/extlookup.rb Regards, DavidS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
