Site specific Spack config as used at the University of Lausanne.
Diffusion dcsr-spack-site (master)
Recent Commits
Recent Commits
Commit | Author | Details | Committed | ||||
---|---|---|---|---|---|---|---|
65202a41e414 | Schlyfts | Updated site configuration | Aug 11 2020 | ||||
9b3feb056bb2 | Schlyfts | script for activating python extensions | Apr 2 2020 | ||||
1c75bfd03d97 | Schlyfts | meleze v2 for public consumption | Mar 31 2020 |
README.md
README.md
spack-site
Site specific configuration for SPACK
Inside the configuration directory are the site specific settings for our SPACK instance
These are linked to where they should be in the main SPACK root which allows us to have two seperate repositories
compilers.yaml -> ${SPACK_ROOT}/etc/spack/compilers.yaml config.yaml -> ${SPACK_ROOT}/etc/spack/config.yaml modules.yaml -> ${SPACK_ROOT}/etc/spack/modules.yaml packages.yaml -> ${SPACK_ROOT}/etc/spack/packages.yaml repos.yaml -> ${SPACK_ROOT}/etc/spack/repos.yaml
For the spack environments there are 3 files:
spack.yaml.j2 which is the template for each environment's spack.yaml
meleze.yaml which contains the variables for the template
deploy-env.py which applies the variable to the template and writes the spack.yaml files
If you want to add a new package then do so in the spack.yaml.j2 template
If you need to customise something for an environment then do so in meleze.yaml
c4science · Help