Closed rptaylor closed 2 years ago
Regarding testing: yes, I update the cvmfs-config.cern.ch repository on the TESTING
tag first. So if you add CVMFS_REPOSITORY_TAG=TESTING
in /etc/cvmfs/config.d/cvmfs-config.cern.ch.local, you get the changes before it goes to production. We leave it in test usually for 1 week. CERN pre-production nodes thus have some time to pick up the changes.
I updated the cvmfs-config TESTING tag just now with the changes from this PR.
@rptaylor Do you only care about this being in the cvmfs default config repository, not osg or egi?
Anyway I'll cherry-pick it to the master branch, because there we keep a superset of the 3 branches.
@jblomer great, thanks! I was away for a couple weeks. I set up the TESTING tag and it seems to work as expected.
@DrDaveD perhaps, it could be useful to OSG/EGI users. We provide a very large general purpose comprehensive software stack, so it likely contains numerous scientific software suites that could be of interest to users in a wide variety of disciplines. https://docs.computecanada.ca/wiki/Available_software I am not sure what sort of software environment is set up on OSG/EGI clusters or if they are intended for general purpose use; anyway you are welcome to use the soft repo.
BTW I recall you made a computecanada branch of this repo, copied from our config repo, but that is somewhat different from what we wanted to have added here.
@jblomer can you let me know when it has graduated to the prod tag? Thanks!
@rptaylor It's available now in prod
Add config and key for Compute Canada soft repo. fix #67
For now that is the only repo to make externally available. The alternative to this way would be to have a config.d/restricted.computecanada.ca file with a URL like http://null.invalid . The connections will be blocked but we also want to prevent external clients from initiating connections for that repo.
Is there a testing procedure for updates to the default config repo branch?