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

caches.json should come from CVMFS #43

Open
djw8605 opened this issue Jan 12, 2017 · 5 comments
Open

caches.json should come from CVMFS #43

djw8605 opened this issue Jan 12, 2017 · 5 comments

Comments

@djw8605
Copy link
Member

djw8605 commented Jan 12, 2017

Rather than having caches.json come from a release, it should come from somewhere on CVMFS, so we can update if a Cache is consistently down.

@djw8605
Copy link
Member Author

djw8605 commented Jan 12, 2017

stashcp should look several places for caches.json, including a special directory in CVMFS, and the release directory...

@matyasselmeci
Copy link
Contributor

/cvmfs/stash.osgstorage.org/caches.json? If we're OK with that, it should be a one-line change.

@djw8605
Copy link
Member Author

djw8605 commented Oct 1, 2019

Sure. Where on the priority chain should it go?

@matyasselmeci
Copy link
Contributor

I think just behind os.path.join(prefix, "etc/stashcache/caches.json") so the admin can still override it.

BTW I just noticed

cache_files.insert(0, resource_string(__name__, 'caches.json'))

That needs to be an append, not an insert, because we need to make the resource file the least important.

@matyasselmeci
Copy link
Contributor

Never mind, I see the PR.

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

2 participants