- CentOS 6
- Ansible version 2.0.1
Default: /apps
Directory in which to store all EasyBuild and Lmod files.
Easy deployment on a local virtual machine using Vagrant is provided in the vagrant directory.
For some base packages, figure out whether to install with yum or with EasyBuild (e.g., Perl).
How to work around EasyBuild packages where the source tarball downloads are
incorrect (e.g., GCCcore/gmp-6.0.0a.tar.bz2
for which an HTML page is
dowloaded)?
Possible solutions:
- Patch the recipe.
- Download the tarball separately.
- Include the tarball with the playbook.
How to proceed with actually installing EasyBuild packages, preferably driven by other roles? Options:
- Just use tasks like the following:
shell: . {{ easybuild_root }}/modules/modules.bashrc && module load EasyBuild && eb SOME_PACKAGE --robot
- Have a custom
easybuild
Ansible module which wraps this. - Have a
easybuild_packages
variable with a list of packages to be installed by this role. - Similar, but as a separate
easybuild-packages
role which is cheaper to repeatedly include from other roles.
I'm inclined to start with 1 and later choose between 2 and 4.
Preferably the final solution should provide idempotency.
How best to integrate custom EasyBuild configs? As separate role per set of configs? Are these configs stored alongside the 'normal' configs?