Update README, containers, CI for software.eessi.io #163
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
bedroge
changed the title
trz42
requested changes
Nov 25, 2023
There was a problem hiding this comment.
Looks good. One curl command to (test) access a file in the new EESSI stack (software.eessi.io) via the Norwegian Stratum-1 doesn't work. Likely a configuration issue on that Stratum-1. Maybe it could be replaces with another Stratum-1 (or temporarily removed/commented).
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.
Replaced all paths / names of the old
pilot.eessi-hpc.orgrepo to the newsoftware.eessi.iorepo, and removed "pilot" in any references to "pilot stack" (also in container image names). Also bumped some versions of tools used in the containers (CVMFS, AWSCLI).TODO: don't install the EESSI CVMFS configuration package, but instead check if the repo can be accessed usingcvmfs-config-default; this cannot be done though, as the EESSI configuration is not part of it yet (probably as of Monday).The containers now include the new EESSI CVMFS configuration package that has the configuration for both the old and new domain.