Skip to content
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

Explore environment chaining on HPCs to integrate with default modules #1119

Open
climbfuji opened this issue May 17, 2024 · 0 comments
Open
Assignees
Labels
INFRA JEDI Infrastructure NAVY United States Naval Research Lab NOAA-EMC OAR-EPIC NOAA Oceanic and Atmospheric Research and Earth Prediction Innovation Center

Comments

@climbfuji
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Here is an email from CISL to users of Derecho/Casper:

Did You Know: Adding your own modules with Spack
May 17, 2024
On both Casper and Derecho, CISL uses the Spack package manager to install compilers and software libraries for you to use. You are probably familiar with these software packages from using our modules system. However, you may not know that you can also augment our software stack with your own package installs using Spack. It provides the concept of “chained installations”, in which there is a downstream instance of Spack (i.e. yours) that can use packages from an upstream instance (the CISL software stack) as dependencies.To make it easier to set up such a downstream, CISL provides a utility called spack-downstream, which will create a copy of Spack in your work directory and configure it to interact with our upstream version. Spack supports thousands of software packages, and the best part is that any package you install can show up alongside our software packages as a module. Check out our Spack documentation to get started using this new capability!

Describe the solution you'd like
We should check if we can make use of this functionality (and do something similar on other systems where the sysadmins use spack) to simplify integrating with the software stack provided by the system administrators.

Additional context
n/a

@climbfuji climbfuji self-assigned this May 17, 2024
@climbfuji climbfuji added INFRA JEDI Infrastructure NOAA-EMC OAR-EPIC NOAA Oceanic and Atmospheric Research and Earth Prediction Innovation Center NAVY United States Naval Research Lab labels May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
INFRA JEDI Infrastructure NAVY United States Naval Research Lab NOAA-EMC OAR-EPIC NOAA Oceanic and Atmospheric Research and Earth Prediction Innovation Center
Projects
None yet
Development

No branches or pull requests

1 participant