First class network stack support #256
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bcumming
commented
Aug 18, 2025
| @@ -87,7 +87,7 @@ def main(): | |||
| ) | |||
| return 0 | |||
| except Exception as e: | |||
| root_logger.debug(traceback.format_exc()) | |||
| root_logger.info(traceback.format_exc()) | |||
There was a problem hiding this comment.
Instead of pushing Python stack traces to the logs, just dump them on the screen given that most users know something about the internals of stackinator.
albestro
reviewed
Aug 19, 2025
Co-authored-by: Alberto Invernizzi <[email protected]>
RMeli
reviewed
Aug 20, 2025
| - spec: [email protected] fabrics=cxi,rxm,tcp | ||
| prefix: /opt/cray/libfabric/1.22.0/ | ||
| version: ["git.v2.2.0=main"] | ||
| require: fabrics=cxi,rxm,tcp |
There was a problem hiding this comment.
This is just an example, but do you need lnx for OpenMPI?
There was a problem hiding this comment.
I don't know - I am copying off what @biddisco provided.
We can update the examples, and the configuration in the network.yaml files, separately from this work (which focuses on the infrastructure).
Co-authored-by: Rocco Meli <[email protected]>
Co-authored-by: Rocco Meli <[email protected]>
albestro
approved these changes
Aug 21, 2025
RMeli
approved these changes
Aug 21, 2025
This was referenced Aug 21, 2025
bcumming
added a commit
to eth-cscs/alps-cluster-config
that referenced
this pull request
Aug 21, 2025
Add `network.yaml` files to the cluster configurations, to support building OpenMPI and low-level network libraries. The stackinator work that uses `network.yaml` was merged: eth-cscs/stackinator#256 Note that the definitions of libfabric, etc, are currently pinned to commits on `main`/`master` of the source repositories, which isn't ideal - but with this feature we can start using concrete versions when it is possible.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The method for adding MPI and tuning the networking libarary stack has been simplified.
There are two components that define the network stack.
The first is the new
networkfield inenvironments.yamlthat replaces the oldmpifield.The user provides a
specfor the MPI distribution they want (currently cray-mpich and openmpi are supported), and an optional list of specs for dependencies (e.g. libfabric):The other half is the new
network.yamlfile in the system configuration, that provides a default list ofspecsfor each MPI distribution, and apackages.yamldescription of the default / required variants and options for cray-mpich, openmpi, libfabric, etc.For example, using this approach, the
+cudavariant can be set as a default on a GH200 cluster, and disabled on a CPU-only system.Based off #210.