Easyconfig that can extend EESSI#371
Conversation
|
Instance
|
|
Module name could be something like |
|
It's not very intuitive for the end user, I'm thinking |
|
Here are the differences between what the module gives and what the Everything as expected here (I have already removed |
|
I'd like to see this one move forward soon. Is there anything more it needs? I can start taking it into "production" locally right now to test things out unless that's already been done. |
Updates by the bot instance
|
I've used it quite a bit myself, but someone else giving it a go could yield valuable feedback. |
| easybuild_installpath = string.gsub(os.getenv("EESSI_SOFTWARE_PATH"), 'versions', 'host_injections') | ||
| else | ||
| -- Would have liked to use os.getenv("EESSI_CVMFS_REPO") here but the hypen needs to be escaped | ||
| easybuild_installpath = string.gsub(os.getenv("EESSI_SOFTWARE_PATH"), "/cvmfs/pilot.eessi%-hpc.org", pathJoin(os.getenv("HOME"), "eessi")) |
There was a problem hiding this comment.
I see a future where this could benefit from the same thing we do for EasyBuild, i.e. going through a list of env vars to use as the base, i.e. HOME, PROJECT, etc. I.e. the envvars-user-modules config option
There was a problem hiding this comment.
The benefit of the current setup is that we can configure EESSI to automatically expose the modules. Thinking about it though, it may be more interesting to do this in a more dynamic way inside the module itself...but the downside of this is you would have to always load the module to see the installed modules.
|
There is a potential problem here, we have an easybuild.cfg setup with various settings, among them we use HMNS. There may be a need to be more careful in overriding more things in this module... |
Updates by the bot instance
|
|
Anyway, initial testing of this is successful. EESSI extended in my $HOME with Wannier90 :-) |
Updates by the bot instance
|
|
@akesandgren Don't you want to wait until the dust settles on this? I can update the PR today to target the production branch. I also need to figure out what to do about the hook, it is a moving target so can't really be part of the installation |
|
Nah, I'm just playing around and figuring out how to use this. |
Updates by the bot instance
|
ocaisa
changed the base branch from
2023.06-pilot.eessi-hpc.org
to
2023.06-software.eessi.io
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
trz42
added
bot:deploy
trz42
left a comment
trz42
left a comment
There was a problem hiding this comment.
Finally! Yeah! Yippieeeeeee 🥳
…1-foss-2022b
{2023.06}[foss/2022b] bokeh V3.2.1
7 participants
The idea would be to add this to (it's own?) easystack file, it will be found as it is in the same directory (as well the "sources" since they are just the hook). It currently requires write permissions to the
host_injectionsdirectory as this allows us to automatically make the modules visible.The name may be a bit suspect, as I would like to have
EESSIas a module for different EESSI versions.