Cluster:Modules

From Earlham Cluster Department

(Difference between revisions)
Jump to: navigation, search
(Software build options)
Line 1: Line 1:
-
= Software build options =
+
== Software build options ==
   ARCHPATH=`uname -s`/`/cluster/software/os_release`/`uname -p`
   ARCHPATH=`uname -s`/`/cluster/software/os_release`/`uname -p`
Line 8: Line 8:
** After installation, changed the version from 3.2.6->3.2.7 in the init directory, and /usr/share/Modules to /cluster/software/modules-sw/modules/3.2.7/$ARCHPATH/Modules
** After installation, changed the version from 3.2.6->3.2.7 in the init directory, and /usr/share/Modules to /cluster/software/modules-sw/modules/3.2.7/$ARCHPATH/Modules
* OpenMPI: <code>./configure --prefix=/cluster/software/modules-sw/openmpi/1.3.1/$ARCHPATH && make</code>
* OpenMPI: <code>./configure --prefix=/cluster/software/modules-sw/openmpi/1.3.1/$ARCHPATH && make</code>
 +
 +
== Multiple Repositories ==
 +
 +
<pre>
 +
That's still doable with multiple modules repositories. We can setup
 +
meta-modules that don't actually point you at software but alter how
 +
modules itself behaves. The master meta-module would prepend MODULEPATH
 +
with (say) "/cluster/software/modules" for software that's the same
 +
across all the clusters, and modules-bobsced would prepend MODULEPATH
 +
with "/cluster/bobsced/software/modules". Just like with PATH, the first
 +
hit within a module repository is used. If Perl is only in the master
 +
software repository it'll be grabbed from there, but if OpenMPI is in
 +
both it'll be grabbed from the bobsced repository since it comes before
 +
the master repository.
 +
</pre>

Revision as of 15:45, 5 October 2009

Software build options

  ARCHPATH=`uname -s`/`/cluster/software/os_release`/`uname -p`

Multiple Repositories

That's still doable with multiple modules repositories. We can setup
meta-modules that don't actually point you at software but alter how
modules itself behaves. The master meta-module would prepend MODULEPATH
with (say) "/cluster/software/modules" for software that's the same
across all the clusters, and modules-bobsced would prepend MODULEPATH
with "/cluster/bobsced/software/modules". Just like with PATH, the first
hit within a module repository is used. If Perl is only in the master
software repository it'll be grabbed from there, but if OpenMPI is in
both it'll be grabbed from the bobsced repository since it comes before
the master repository.
Personal tools
Namespaces
Variants
Actions
websites
wiki
this semester
Toolbox