Hi, I'm in the process of planning a new Puppet infrastructure and had a question regarding the usage of environments. This Puppet implementation requires that there are "plans" applied to each type of machine that it manages. I was thinking of managing each of these plans (ie, "app1-devwebserver", "app1-prodappserver", etc) in separate environments that would contain modules that are specific to the type of machine that is required. In addition, each environment would have a "common" module search path which would contain common/base modules that were to be applied to every type of machine.
While I can see this method working, I'm not sure that it is the most efficient way to handle this. Can anyone offer some advice or suggestions on this design? I was thinking of simplifying the design by not using app-specific environments and using more generic environments for "prod," "dev, "qa," etc, but I think I lose from granularity by doing this. Thanks, Josh -- 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.
