On 11/24/2012 11:18 AM, Smashed wrote:
I would like to have puppet manage a puppet server, puppet dashboard and
puppet agents. Do you think it would be best to create one puppet module
that does all of these or is it best to break these out into 3 separate
modules (puppet-server, puppet-agent, puppet-dashboard, etc
Also within modules is there any general best practices for organizing
your classes and configuration applications? For example I read in the
Pro Puppet book its usually good to have an install, config and service
class.
It's almost always better to have modules that do as little as
possible. Easier to write, test, and set ordering between them. Also
discrete bits of functionality are far more reusable than large do
everything modules. And you can always create a wrapper class.
class role::puppetserver {
include puppet
include puppetdashboard
include puppetmaster
}
node /^puppetmaster\d+/ inherits basenode {
include role::puppetserver
}
Also don't use hyphens in class names.
http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html#allowed-module-names
Ramin
--
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.
