On 6 Dec 2010, at 3:52 AM, Craig Dunn wrote:
> Reading the latest best practices for 2.6.x I see that it recommends generic
> classes for server model types to be put in /etc/puppet/services. Sounds a
> sensible idea but I can't seem to find much more information on this and
> services/ doesn't seem to be in the default search path for classes. Does it
> have to be specifically imported?
If you have a separate services/ directory for site modules (or any other
directory of extra modules you want to use) -- then you must add it to your
Puppetmaster's modulepath. Once your modulepath is set correctly, however,
Puppet's autoloader will find modules in your services/ directory as easily as
those in your modules/ directory; no special imports are required in your
manifests.
> Does anyone have any example snippets of this in use?
You should just need something like this in your Puppetmaster's puppet.conf:
[master]
modulepath =
$confdir/modules:$confdir/services:/usr/share/puppet/modules
That would insert $confdir/services into the middle of the default modulepath,
if you were previously using the default. (You may also want to parameterize
on the $environment fact, &c.)
Incidentally, we (the Stanford University Libraries) adopted this
modules/services distinction from the other, larger Puppet deployment here at
Stanford, and it's worked very well for us.
--
Ian Ward Comfort <icomf...@stanford.edu>
Systems Team Lead, Academic Computing Services, Stanford University
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
