-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Soft links to latest modules on each platform #1204
Comments
@climbfuji @RatkoVasic-NOAA please check out the paths in the description and add symlinks on any other systems where they might get used. These are all pointing to 1.7.0 (I didn't do Gaea C6 since we didn't deploy 1.7.0 there)
I propose we create an issue with each release to remind ourselves to update these symlinks, and try to update them on the same day across systems to avoid excessive confusion and heartache for developers. Relatedly, I created a wiki page to document all currently supported spack-stack environments on each platform: https://github.com/JCSDA/spack-stack/wiki/Extended-list-of-release-directories If it looks good, we can coordinate dividing up the work, which I predict will be slightly tedious but shouldn't take too long. |
Thanks @AlexanderRichert-NOAA . We should focus on the NOAA/EPIC platforms for the symlinks first - suggest doing S4 next. |
@AlexanderRichert-NOAA I created symbolic links to the latest spack-stack (1.8.0) on 10 tier1 machines.
|
How about you add it to the already closed spack-stack-1.8.0 release task issue (with the list of platforms and a reference to this issue for the location)? I usually take the last releases' task issue to create the next one. |
Actually, let me do this real quick. |
Done. See #1278 (comment) |
That was quick |
I see S4 is missing on this list. Is that needed? |
I don't have access there |
That's why I am asking - JCSDA (@srherbener) or I can do that if it's required |
These directories might work for the S4 symlinks
I vote for |
Makes sense to me, thanks @srherbener. This is also the top-level spack-stack directory, and therefore matches what is done on the other NOAA platforms. |
Let's close this once Steve's done with S4 and after #1335 is merged. |
S4 has a symlink for
|
Thanks @srherbener! I updated the description of the issue (first comment) with the link on S4. |
The idea was raised within EMC to create a symlink, something like
/path/to/spack-stack/latest-modules
, on each platform that would point to the most recent $env/install/modulefiles/Core directory. This would be useful for developers who don't mind updating a bunch of package versions at once, and keeps them from having to update their application modulefiles, at least on develop branches. Let's try this on one or two systems to make sure it works, then it should be as simple as reassigning the symlink with each release.spack-stack-1.8.0:
/contrib/spack-stack/latest-ue-intel/
/contrib/spack-stack/latest-ue-gcc/
/contrib/spack-stack/latest-ue-intel/
/contrib/spack-stack/latest-ue-gcc/
/ncrc/proj/epic/spack-stack/latest-ue-intel/
/ncrc/proj/epic/spack-stack/c6/latest-ue-intel/
/glade/work/epicufsrt/contrib/spack-stack/derecho/latest-ue-intel/
/glade/work/epicufsrt/contrib/spack-stack/derecho/latest-ue-gcc/
/apps/contrib/spack-stack/latest-ue-intel/
/apps/contrib/spack-stack/latest-ue-gcc/
/apps/contrib/spack-stack/latest-ue-intel/
/apps/contrib/spack-stack/latest-ue-gcc/
/contrib/spack-stack-rocky8/latest-ue-intel/
/contrib/spack-stack-rocky8/latest-ue-intel/
/contrib/spack-stack-rocky8/latest-ue-intel/
/data/prod/jedi/spack-stack/latest-ue-intel/
The text was updated successfully, but these errors were encountered: