On Sat, Jun 18, 2011 at 1:29 AM, Bruce Bushby <bruce.bus...@gmail.com>wrote:
> Hello > > I'm new to large scale puppet deployment and was hoping the list could > offer some pointers on "module layout" > > My initial "layout" was motivated by a need to "harden" our Linux > systems. I grouped the various hardening configs into: > > Kernel > OS > Network > Shell > Files > Application > > I'm hoping I can create the same module structure within puppet. In my experience, these module categories are too broad and it will make maintenance difficult. You don't want to get too fine-grained with your modules, but if you keep things this broad, you'll end up having lots of complicated relationships like Class[os::foo] -> Class[files::foo] I made this mistake on a large deployment and regretted it. -- 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.
