So we've got "resources". And "classes" and "nodes" and "defines" and "modules" and "plugins" and "templates". And I'm not sure I've got them all, by any means. Classes are singletons.
I'm working on managing a batch of identical servers. The obvious thing, it seems to me, is to define a *thingy* (technical term meaning I want to not misuse any of the specifically meaningful terms above) which encapsulates exactly what I want these identical servers to do (presumably using lots of modules and things from elsewhere), and then associate the *thingy* with the list of nodes I want to be like that. Is this the propperly Puppetish best-practices approach? (It's a small batch, 2 at the moment, unlikely to exceed a dozen ever; they're actually *virtual* servers). And, if that is the right general approach -- what flavor of *thingy* should I be writing there? Is that a define, or a class, or a module, or what? Or is it best (since they're really truly supposed to be identical) to skip the container and just import or define everything I want directly in the node, using the multiple titles syntax to create a batch of identical nodes? (And I've got my test node connecting to my puppet server and doing the trivial stuff from the "simplest recipe" correctly, and I'm moving on to bigger and better things! Thanks for all the help in stage one.) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
