I am using external node classifiers that parse information FROM a database (well really a csv file, but it could easily be a database:) in order to build the classifications. This is the opposite of what you are proposing, here its the database that controls how puppet classifies machines, not the other way around.
I am not sure if this would give you the level of detail that you want, but its worth considering. The columns are something like this HOSTNAME;environment;location;department;classification;and others... where classification is a list that related to the puppet files that need to be instantiated. For example: classification could be server,httpd * where server is a classification = includes syslog,nis,autofs,sntp,... * and httpd is a module just as long as it refers to a valid class name that can be passed to puppet. so any changes to the database will cause changes to the effected nodes. /Dan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
