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

Copy from /cvmfs or from eospublic? #40

Open
katilp opened this issue Nov 18, 2022 · 0 comments
Open

Copy from /cvmfs or from eospublic? #40

katilp opened this issue Nov 18, 2022 · 0 comments

Comments

@katilp
Copy link
Owner

katilp commented Nov 18, 2022

The cvmfs mount was originally needed because the image did not have condition data access and the dbs were not on eospublic as they are now (/eos/opendata/cms/conddb/selection-for-containers/).

When running on 2011 files in November 2022, the cvmfs was unstable made the workflow fail so the db cp was updated to copy from eospublic. Now the access is mixed, i.e. the original base is taken from cvmfs but the database copy is from eospublic.

Clean this up. In principle, a cvmfs mount is not needed, but the cvmfs access has the advantage of not being restricted to OD condition data.

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

1 participant