<div dir="ltr"><p class="">Talking about modules and build systems, take a look at Easybuild:</p>
<p class=""><a href="http://hpcugent.github.io/easybuild/">http://hpcugent.github.io/easybuild/</a></p>
<p class=""> </p>
<p class="">This is not a direct answer to the original poster's
question - which has been admirably dealt with in previous answers.</p></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 May 2015 at 23:22, Michael Gutteridge <span dir="ltr"><<a href="mailto:michael.gutteridge@gmail.com" target="_blank">michael.gutteridge@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:monospace">I'll plus-one your two-cents there.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">We're using an NFS mounted application file system where we have requested tools- it's organized by tool name and version. Modules has been an absolute revelation for keeping things sensible when maintaining multiple versions of software.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">We do use Puppet for managing the nodes themselves, including the versions of system software that are installed (/usr and below). Fair warning: Puppet is fairly dependent on packaging for deploying software. There are add-on modules that allow installation from tarballs... those do a pretty good job, but I haven't used them extensively.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">What you may look into at the same time is build management and automation for your unbundled tools. We don't have anything at the moment and I'm *really* not looking forward to the next OS upgrade.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Best</div><span class="HOEnZb"><font color="#888888"><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Michael</div><div class="gmail_default" style="font-family:monospace"><br></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 26, 2015 at 2:56 PM, Chris Dagdigian <span dir="ltr"><<a href="mailto:dag@sonsorol.org" target="_blank">dag@sonsorol.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Environment Modules (<a href="http://modules.sourceforge.net/" target="_blank">http://modules.sourceforge.net/</a>) or the more modern derivatives are pretty darn universal in cluster environments where a shared filesystem can be used to host an application/tools tree. Do one install and one module file and it's instantly available across the cluster. Does a great job of allowing you to host and offer many different versions/permutations of the same application.<br>
<br>
After that you get less universal and odder more DIY setups. Some groups will roll software into custom .rpm, .pkg or .deb packages depending on their OS and will do all of their custom/internal software as binary packages hosted on a central app repository server. Lots of hacks involving passwordless SSH scripts run on remote nodes to replicate files or dump/unpack a tarball representing a tool.<br>
<br>
And finally the cool DevOps kids are using Puppet, Chef, SaltStack, Ansible, Cfengine, etc. configuration management / orchestration toolkits -- those are often overkill for simple software installs but they *excel* at maintaining and managing configuration states across many different systems. If your entire cluster is Puppetized one could easily come up with a puppet-based method for installing or managing the installation of software<br>
<br>
My $.02 of course<div><div><br>
<br>
<br>
<br>
Trevor Gale wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello all,<br>
<br>
I was wondering what solutions other use for easy software installation across clusters. Is there any method that is generally accepted to be the most effective for making sure that all the software is consistent across each node?<br>
<br>
Thanks,<br>
Trevor<br>
___________<br>
</blockquote>
<br>
_______________________________________________<br>
Beowulf mailing list, <a href="mailto:Beowulf@beowulf.org" target="_blank">Beowulf@beowulf.org</a> sponsored by Penguin Computing<br>
To change your subscription (digest mode or unsubscribe) visit <a href="http://www.beowulf.org/mailman/listinfo/beowulf" target="_blank">http://www.beowulf.org/mailman/listinfo/beowulf</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Beowulf mailing list, <a href="mailto:Beowulf@beowulf.org">Beowulf@beowulf.org</a> sponsored by Penguin Computing<br>
To change your subscription (digest mode or unsubscribe) visit <a href="http://www.beowulf.org/mailman/listinfo/beowulf" target="_blank">http://www.beowulf.org/mailman/listinfo/beowulf</a><br>
<br></blockquote></div><br></div>