RHEL9 upgrade: first commit includes - #879
Conversation
arswalid
commented
Jul 13, 2026
- Main changes OS CPE SLURM etc...
- access information
- module structure
- envs
- toolchains
- CPE
- known issues and FAQs
- Main changes OS CPE SLURM etc... - access information - module structure - envs - toolchains - CPE - known issues and FAQs
|
This PR looks good to me - no specific comments. This will be a helpful starting point for users as they onboard onto the RHEL9 nodes. |
There was a problem hiding this comment.
@arswalid and @mselensky I didn't go through all of this but noticing a lot of formatting issues, etc. Can you please go through and verify that the heading capitalization, code highlighting, other formatting is consistent, that it's using NLR instead of NREL, and proofread?
|
|
||
| - On RHEL 8, applications were installed under `/nopt/nrel/apps/`. A new directory, `/nopt/nlr/apps`, has been created for this transition. | ||
| - Slurm for RHEL 9 is installed under `/nopt/slurm/latest` instead of `/nopt/slurm/current`. | ||
| - The latest FastX server is running on `kd7.hpc.nrel.gov` and can be accessed with the FastX client or at <https://kd7.hpc.nrel.gov>. |
There was a problem hiding this comment.
| - The latest FastX server is running on `kd7.hpc.nrel.gov` and can be accessed with the FastX client or at <https://kd7.hpc.nrel.gov>. | |
| - The latest FastX server is running on `kd7.hpc.nlr.gov` and can be accessed with the FastX client or at <https://kd7.hpc.nlr.gov>. |
| - On RHEL 8, applications were installed under `/nopt/nrel/apps/`. A new directory, `/nopt/nlr/apps`, has been created for this transition. | ||
| - Slurm for RHEL 9 is installed under `/nopt/slurm/latest` instead of `/nopt/slurm/current`. | ||
| - The latest FastX server is running on `kd7.hpc.nrel.gov` and can be accessed with the FastX client or at <https://kd7.hpc.nrel.gov>. | ||
| - Access to RHEL 9 login and compute nodes is restricted. Reach out to `hpc-help@nlr.gov` to get started on the newer software stack. |
There was a problem hiding this comment.
| - Access to RHEL 9 login and compute nodes is restricted. Reach out to `hpc-help@nlr.gov` to get started on the newer software stack. | |
| - Access to RHEL 9 login and compute nodes is restricted. Reach out to [hpc-help@nlr.gov](mailto:hpc-help@nlr.gov) to get started on the newer software stack. |
| @@ -0,0 +1,68 @@ | |||
| # Accessing Kestrel RHEL9 | |||
|
|
|||
| ## login Nodes | |||
There was a problem hiding this comment.
| ## login Nodes | |
| ## Login Nodes |
|
|
||
| ## login Nodes | ||
| Use the following login nodes to access upgraded RHEL 9 resources: | ||
|
|
There was a problem hiding this comment.
hostnames all need to use nlr instead of nrel
| - GPU login node: `kl5.hpc.nrel.gov` | ||
| - DAV node: `kd7.hpc.nrel.gov` | ||
|
|
||
| ## ssh steps |
There was a problem hiding this comment.
| ## ssh steps | |
| ## SSH Steps |
| - DAV node: `kd7.hpc.nrel.gov` | ||
|
|
||
| ## ssh steps | ||
| 1. SSH to one of the login nodes listed above. |
There was a problem hiding this comment.
The numbers aren't rendering correctly in markdown, they are all showing as "1."
|
|
||
| ## Known Issues | ||
|
|
||
| - `openmpi` 5 works only with `mpirun` because Slurm is configured without PMIx. |
There was a problem hiding this comment.
| - `openmpi` 5 works only with `mpirun` because Slurm is configured without PMIx. | |
| - `openmpi5` works only with `mpirun` because Slurm is configured without PMIx. |
| ## Known Issues | ||
|
|
||
| - `openmpi` 5 works only with `mpirun` because Slurm is configured without PMIx. | ||
| - `mpiifx` previously failed because of missing path definitions. This should be fixed; report if it still fails. |
There was a problem hiding this comment.
how should users report this?
|
|
||
| ### I cannot find the module I need. | ||
|
|
||
| Use `module spider ModuleName` first to verify availability. If it still cannot be found, email `hpc-ticket` and the Apps team will follow up. |
There was a problem hiding this comment.
| Use `module spider ModuleName` first to verify availability. If it still cannot be found, email `hpc-ticket` and the Apps team will follow up. | |
| Use `module spider <ModuleName>` first to verify availability. If it still cannot be found, email `hpc-ticket` and the Apps team will follow up. |
|
|
||
| ### I need to mix and match compilers and libraries/MPI. How can I do that? | ||
|
|
||
| Modules do not support arbitrary mix-and-match combinations. For example, if `oneapi` is loaded, only software compiled with oneAPI is shown. For custom stacks, use Spack and contact `hpc-ticket` to be matched with a Spack expert. |
There was a problem hiding this comment.
please fix the email and use mailto like the rest of the codebase
| @@ -0,0 +1,26 @@ | |||
| # Getting Started | |||
|
|
|||
There was a problem hiding this comment.
Since this the section heading page it might be nice to have a little intro/summary about the upgrade and why were are doing that. Could you write that @mselensky ?
|
@yandthj thanks for catching those typos + good idea on the intro - let me know what you think! |