Hello EasyBuild experts, currently I am working as intern in a small engineering company which is accessing two clusters for their simulation and viz tasks (one remote cray system, one smaller local Xeon cluster). My task is to examine to what degree EasyBuild can simplify maintaining on both clusters the same software stack, which is mostly open source tools with existing easyconfigs. And I would need some help:
Both clusters come with a highly optimized build environment, including MPI supporting infiniband, BLAS and LAPACK, python with optimized numpy and mpi4py. As far as I can see, all the foss, goolf, etc. toolchains (except for dummy and CrayGNU) want to build their own compilers, MPI libraries, LAPACK, Python etc. modules, but I was told to use the optimized system whereever possible. On the cray, the CrayGNU toolchain seems to support this at least partially. But which toolchain do I choose on the Xeon cluster, which provides all those optimized tools through already existing modules? Can I tweak the goolf toolchain to use the existing system modules? Or do I have to use the dummy toolchain instead? If using the dummy toolchain, do I have to rewrite all involved easyconfig files, or can I take - say the easyconfigs for the goolf toolchain - and somehow replace goolf by dummy at buildtime? I hope, I could make my problem clear. Please help an EasyBuild newbie :) Thank you Gunnar
