Hi,
For common files that aren't easily grouped I currently manage them is a base
module that everyone gets.
They get their own class or define and are called like so:
class blah {
Include base
base::sysctl {"vm.swappiness": value => 10 }
}
Cheers,
Den
On 21/03/2012, at 4:35, Scott Merrill <[email protected]> wrote:
> How are folks organizing their Puppet modules?
>
> For things that fit the trifecta
> (http://projects.puppetlabs.com/projects/puppet/wiki/Core_Types_Cheat_Sheet/)
> it makes sense (to me) to make them top-level citizens in my
> /etc/puppet/modules directory. This constitute things like Postfix,
> ntp, snmp, and the like.
>
> Moving past these, though, I'm curious how people are organizing
> modules for essentially "standalone" files, i.e. those that don't
> directly associate to a daemon. Things like /etc/sysctl.conf,
> /etc/inittab, shell and profile controls, and the like. This also
> includes miscellaneous services to start or stop when there's no
> attendant config file to require; as well as packages to ensure are
> installed or absent.
>
> What unexpected headaches -- if any -- resulted from your organizational
> choice?
>
> Thanks!
> Scott
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to [email protected].
> 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.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
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.
