Skip to content
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

Closed
bedroge opened this issue Mar 9, 2021 · 6 comments
Closed

Add EESSI configuration #54

bedroge opened this issue Mar 9, 2021 · 6 comments

Comments

@bedroge
Copy link

bedroge commented Mar 9, 2021

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 to eessi-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!

@DrDaveD
Copy link
Collaborator

DrDaveD commented Mar 9, 2021

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?

@DrDaveD
Copy link
Collaborator

DrDaveD commented Mar 9, 2021

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 domain.d/eessi-hpc.org.conf and keys/eessi-hpc.org/pilot.eessi-hpc.org.pub.

@jblomer
Copy link
Collaborator

jblomer commented Mar 10, 2021

As discussed yesterday, I'd like to add it to the default repo.

@DrDaveD
Copy link
Collaborator

DrDaveD commented Mar 10, 2021

Ok as also discussed yesterday, when ready Bob will submit it as a pull request against the default branch.

@boegel
Copy link
Contributor

boegel commented Apr 2, 2021

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 default branch in this repo.

@boegel
Copy link
Contributor

boegel commented Nov 17, 2023

done, see #206 + #207, so can be closed

@DrDaveD DrDaveD closed this as completed Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants