Detect Perlmutter nodes and set corresponding Globus endpoint #246
Conversation
This file contains 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
lukaszlacinski
force-pushed
the
lukaszlacinski/globus/nersc
branch
from
688961e to
149eefc
Compare
lukaszlacinski
force-pushed
the
lukaszlacinski/globus/nersc
branch
from
149eefc to
cc54251
Compare
|
Thanks @lukaszlacinski for implementing this. The unit tests pass on Perlmutter. Merging. |
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.
NERSC Perlmutter nodes do not have an FQDN set properly. It means that
socket.getfqdn()and regex cannot be used to determine what machine zstash is run on and set a corresponding Globus endpoint UUID. This PR adds another detection method that relies on$NERSC_HOSTenvironment variable that is set on NERSC machines. If the variable is set to"Perlmutter"or "unknown", a Perlmutter Globus endpoint will be used for the machine zstash executed on.