Expand scope to include how software is provisioned?

mikecroucher / HPC_schedulers

Which schedulers are the most popular on current HPC systems?

14 stars 9 forks source link

Expand scope to include how software is provisioned? #4

Open willfurnass opened 4 years ago

willfurnass commented 4 years ago

Could expand schema to include:

how centrally-provided software built and provisioned ('artisan' builds, EasyBuild, Spack, Alces, Nix, container registry, conda)
how software loaded (Environment Modules, Lmod, spack load/spack environments, conda environments, containery thing pull/run/exec, CVMFS)

mikecroucher commented 4 years ago

It's a good idea but how easy is it to get such info from public information?

takluyver commented 4 years ago

I've only got experience of one HPC cluster, but in that one, it's not possible to answer these as clearly as with the scheduling system. Different bits of software are managed in different ways, and in some cases by different groups of people.

willfurnass commented 4 years ago

Yes, probably difficult to get info on this. The answers would be interesting though.