In regard to: Re: [Puppet Users] Re: Module critique, Bai Shen said (at...:
I strongly recommend that you build a native package for SOLR, put it in a
local repository, and ensure it installed via a Puppet Package resource.
Recursive directory management will bite you, especially if there are many
files or large ones, plus using packages is in general a major win. You
can package up your custom SOLR configuration files along with, or manage
just those via File resources as you are now doing; either is fine.
I'll take a look at that. I'm not really familiar with how to build rpms
yet. The tomcat one was built using a file I found online.
With Tomcat WAR files its generally pretty easy. We're actually not
packaging SOLR but I have packaged other WAR files and could provide
an example that you could adapt to SOLR pretty easily.
Our lead developer just finished a SOLR deploy with puppet about a month
ago, I'll see if I can get permission to share his module for you to
compare to. One thing he did that I didn't see on first inspection with
your solr module was he has a define so that we can have multiple solr
"cores". Right now it's all just using file shipping, though. We looked
at templating some of the config but decided that was more advanced than
what we wanted for our first solr roll-out.
Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
--
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.
