-
Notifications
You must be signed in to change notification settings - Fork 1
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
Modifying directory structure + drop pilot terminology #217
Modifying directory structure + drop pilot terminology #217
Conversation
Instance
|
Instance
|
Instance
|
72d8ba1
to
41f8bc6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks mostly good. Left a few comments.
I'm a bit uncertain about the changes related to archdetect
. To be on the safe side we would have to build for all architectures we need or at least those that are different from EESSI.
Using x86_64/intel/broadwell subdirectory for software layer (HARDCODED) | ||
Using x86_64/intel/haswell subdirectory for software layer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe (HARDCODED)
was wrong? I think, this is just an example output. So maybe good to check what we get on a client, then use that?
README.md
Outdated
$ source /cvmfs/software.eessi.io/versions/2023.06/init/bash | ||
Found EESSI repo @ /cvmfs/software.eessi.io/versions/2023.06! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit tricky as it is the result of what is in the CVMFS repository. Maybe check what it is now and use that? In case we change the CVMFS repository side, we only need to remember to change it here too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check last two commits, keeping it as /cvmfs/pilot.nessi.no results in failing CI tests.
README.md
Outdated
Prepending /cvmfs/software.eessi.io/versions/2023.06/software/x86_64/intel/haswell/modules/all to $MODULEPATH... | ||
Environment set up to use EESSI (2023.06), have fun! | ||
[EESSI 2023.06] $ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit tricky as it is the result of what is in the CVMFS repository. Maybe check what it is now and use that? In case we change the CVMFS repository side, we only need to remember to change it here too.
init/eessi_defaults
Outdated
export EESSI_CVMFS_REPO="${EESSI_CVMFS_REPO_OVERRIDE:=/cvmfs/software.eessi.io}" | ||
# export EESSI_CVMFS_REPO="${EESSI_CVMFS_REPO_OVERRIDE:=/cvmfs/pilot.nessi.no}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, we need to keep /cvmfs/pilot.nessi.no
here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping /cvmfs/pilot.nessi.no results in failing CI tests, check last two commits.
When changing the README.md only without the init/eessi_defaults file to default, the CI Tests for consistency of README.md fails with :
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets merge it and see if it/what works.
Trying to get closer to EESSI by modifying the directory structure and applying modifications done in PR 387