Hi, Thanks for your contributions. We discussed the approaches and decided on a simple symlink.
Having /etc/easybuild.d as a symbolic link to a location visible to the entire cluster. EasyBuild still believes /etc/easybuild.d/config.cfg is the config file. Best wishes Joachim On 13 Sep 2016, at 04:32, Jack Perdue <[email protected]<mailto:[email protected]>> wrote: BTW... I had to research an EB "config.cfg" file... that was new to me.... learned a new eb command line option. :) [j-perdue@ada2 ~]$ ml EasyBuild [j-perdue@ada2 ~]$ ml EasyBuild-ada [j-perdue@ada2 ~]$ eb --show-default-configfiles Default list of configuration files: [with $XDG_CONFIG_HOME: (not set), $XDG_CONFIG_DIRS: (not set)] * user-level: ${XDG_CONFIG_HOME:-$HOME/.config}/easybuild/config.cfg -> /home/j-perdue/.config/easybuild/config.cfg => not found * system-level: ${XDG_CONFIG_DIRS:-/etc}/easybuild.d/*.cfg -> {/etc}/easybuild.d/*.cfg => (no matches) Default list of existing configuration files (0): (none) [j-perdue@ada2 ~]$ env | grep EASYBUILD | sort EASYBUILD_BUILDPATH=/tmp/easybuild EASYBUILD_DEPRECATED=2.0 EASYBUILD_MODULES_TOOL=Lmod EASYBUILD_PREFIX=/software/easybuild EASYBUILD_REPOSITORYPATH=/software/easybuild/ebfiles_repo/ada EASYBUILD_ROBOT=/software/easybuild/ebfiles_repo_cleaned/ada EASYBUILD_SOURCEPATH=/software/easybuild/sources EBDEVELEASYBUILD=/software/easybuild/software/EasyBuild/2.8.2/easybuild/EasyBuild-2.8.2-easybuild-devel EBROOTEASYBUILD=/software/easybuild/software/EasyBuild/2.8.2 EBVERSIONEASYBUILD=2.8.2 __LMOD_STACK_EASYBUILD_BUILDPATH=L3RtcC9lYXN5YnVpbGQ= __LMOD_STACK_EASYBUILD_DEPRECATED=Mi4w __LMOD_STACK_EASYBUILD_MODULES_TOOL=TG1vZA== __LMOD_STACK_EASYBUILD_PREFIX=L3NvZnR3YXJlL2Vhc3lidWlsZA== __LMOD_STACK_EASYBUILD_REPOSITORYPATH=L3NvZnR3YXJlL2Vhc3lidWlsZC9lYmZpbGVzX3JlcG8vYWRh __LMOD_STACK_EASYBUILD_ROBOT=L3NvZnR3YXJlL2Vhc3lidWlsZC9lYmZpbGVzX3JlcG9fY2xlYW5lZC9hZGE= __LMOD_STACK_EASYBUILD_SOURCEPATH=L3NvZnR3YXJlL2Vhc3lidWlsZC9zb3VyY2Vz Jack Perdue Lead Systems Administrator High Performance Research Computing TAMU Division of Research [email protected]<mailto:[email protected]> http://hprc.tamu.edu HPRC Helpdesk: [email protected]<mailto:[email protected]> On 09/12/2016 01:25 PM, Jack Perdue wrote: The latter is the approach we take. ml EasyBuild # load stock EB modules then ml EasyBuild-ada # to build on/for Ivy Bridge nodes or ml EasyBuild-ada-Westmere # to build on/for Westmere nodes or ml EasyBuild-curie # to build on P7 nodes (this has its own P7 compile of EB) with each having its own EASYBUILD_* settings (primarily _INSTALLDIR, _REPOSITORYPATH and ROBOTPATH). jack On 09/12/2016 12:56 PM, Martin wrote: We are rolling out a central /etc/profile.d/... file that exports the relevant EASYBUILD_ variables. Out method of choice is currently puppet but we are thinking about taking the intermediate of building a SiteEB module that does this (so "ml load SiteEB" instead of "ml load EasyBuild"). That way we decouple the upstream installation from our own site settings On Mon, Sep 12, 2016 at 7:19 PM Åke Sandgren <[email protected]<mailto:[email protected]> <mailto:[email protected]>> wrote: Why not keep /etc/easybuild.d/ in sync on all systems? On 09/12/2016 06:19 PM, Joachim Hein wrote: > Hi, > > The EasyBuild configuration file lives on a local disc of our > frontend /etc/easybuild.d/config.cfg hence EB is broken on any other > part of the cluster (e.g. building on a compute node). I am aware > of http://easybuild.readthedocs.io/en/latest/Configuration.html#configuration-file-s <https://urldefense.proofpoint.com/v2/url?u=http-3A__easybuild.readthedocs.io_en_latest_Configuration.html-23configuration-2Dfile-2Ds&d=CwMFaQ&c=ODFT-G5SujMiGrKuoJJjVg&r=yuyoBkmTkIQPbv1BTF9U27ww5Lm7GhsMmWcQG9gmjbA&m=Y_NNis7GVIp_e7hV3npDq4Lr6iwZa3SBudImyPdjryY&s=G8Mng7i3L_TiYsEhPXKwgzDfY4lOvOBNf2BD4-dJwAY&e=> and > currently $EASYBUILD_CONFIGFILES seems the way forward. However setting > that as a system default in every account seems polluting to me. A > natural place seems the EasyBuild module and I could hack it into there. > However with the frequent upgrades to EB, I would need to remember to > hack the newly builded module each time. > > Since many here are operating multimode clusters, this must be a > frequent issue. How are others handling this? > > Thanks and best wishes > Joachim > -- Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden Internet: [email protected] <mailto:[email protected]> Phone: +46 90 7866134 Fax: +46 90-580 14 Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hpc2n.umu.se&d=CwMFaQ&c=ODFT-G5SujMiGrKuoJJjVg&r=yuyoBkmTkIQPbv1BTF9U27ww5Lm7GhsMmWcQG9gmjbA&m=Y_NNis7GVIp_e7hV3npDq4Lr6iwZa3SBudImyPdjryY&s=-Vt9JMuIFrztszzhOTIk2ZVo8DFkVrNhDX5owscvPwQ&e=> -- -- http://www.xing.com/profile/Martin_Marcher http://www.linkedin.com/in/martinmarcher Mobil: +43 / 660 / 62 45 103 UID: ATU68801424
