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.

Sign up for GitHub

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

Jump to bottom

Make sure all reporting now using code from a common directory i.e. datacentre processing or another shared directory? (Steve 29/11/2022) #25

Open
SteveDonegan opened this issue Nov 29, 2022 · 2 comments
Open

Make sure all reporting now using code from a common directory i.e. datacentre processing or another shared directory? (Steve 29/11/2022) #25

SteveDonegan opened this issue Nov 29, 2022 · 2 comments

Comments

@SteveDonegan
Copy link
Contributor

Should we actually make a new playbook that deals solely with installation of reporting - so can use that to update on all rather than running the main dhus install playbook?
@SteveDonegan
Copy link
Contributor Author

CEntralise reporting and mirror archive code on hub BE machines (i.e. reporting, NRT etc)

@SteveDonegan
Copy link
Contributor Author

NOTE that py code for sentinel find etc IS centralised on /datacentre/processing3 - other code is installed on root disks i.e. /usr/local/srh_install//ceda_relay_hub/management_scripts/python/dhus/report_publication_delay.py - need to centralise this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SteveDonegan