-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add EESSI configuration #54
Comments
Yes we would want to rename it to esssi-hpc.org.pub. @jblomer do you want to put this in the default config repo or leave it only for egi? |
I'm not sure exactly how the rpm is generated, but downloading it and running it through rpm2cpio was the easiest way I found to get |
As discussed yesterday, I'd like to add it to the default repo. |
Ok as also discussed yesterday, when ready Bob will submit it as a pull request against the default branch. |
We briefly discussed this during our EESSI monthly meeting yesterday. @bedroge will look into creating a new master key and adopt the use of yubikeys to store it safely. Once that is done, we will look into the pull request to add the new public key and corresponding configuration to the |
Hi @DrDaveD,
As you suggested on the CVMFS forum (https://cernvm-forum.cern.ch/t/best-practices-for-client-configuration-packages-without-config-repo/47/9), I'm opening this issue as a request to include the EESSI configuration in one of the cvmfs-config repos. (EGI?).
The latest configuration packages (rpm/deb/tar) for the EESSI repositories can be found at:
https://github.com/EESSI/filesystem-layer/releases/tag/v0.3.0
Note that it currently still includes some more keys, partly due to legacy reasons (old cvmfs-config repo) and because of an issue with the Ansible role that we use to configure our servers. However, for this purpose it should be sufficient to only include the
pilot.eessi-hpc.org.pub
key (and perhaps rename it toeessi-hpc.org.pub
?). For future repos, we will make use of the master/pub key of this repo.If you need any more information, please let me know!
The text was updated successfully, but these errors were encountered: