Hej,
We are curious how to maintain architecture-specific EasyBuild trees. We are new to EasyBuild and already have many, many (mostly bioinformatics) tools installed in hand-maintained module and software trees. In our centre, we have clusters running Sandy Bridge EP, Haswell EP, and Broadwell EP. Most of our users are on Broadwell, so we if we compile with -march=native etc., we compile for Broadwell and for Sandy Bridge, which covers it and Haswell. In our standard module tree we manage architecture automatically, keying off a $Cluster variable set by the module system. We handle architectures as if we had modules versioned Tool/Version/Architecture, with the last bit hidden from the user. We have also decided to (mostly) hide our EasyBuild tree from the user, and instead provide access to EasyBuild-built tools using what we are calling alias modules, which we place in our standard module tree. An alias module performs a 'module use' of the easybuild tree and then loads the appropriate EasyBuild-built modules. The large majority of our users do not care about toolchains, etc. Those that do, we will have docs they can consult for working with EasyBuild modules directly. The very large majority of our installed tools do not currently have easyconfigs. We are guessing that our architecture solution with EasyBuild will end up being completely separate EasyBuild trees, accessed using distinct 'module use' paths. The EasyBuild docs point to a 2015 presentation by Pablo Escobar describing an automounter solution which we are definitely not going to implement, but this suggests completely separate trees as well. How is this typically handled by other centres ? Thanks in advance, Douglas — Douglas G. Scofield Evolutionary Biology Centre, Uppsala University douglas.scofi...@ebc.uu.se douglasgscofi...@gmail.com När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/ E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: http://www.uu.se/en/about-uu/data-protection-policy
