-
Notifications
You must be signed in to change notification settings - Fork 42
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
Proposal for a single rucio chart with complete reproducible deployment of rucio #217
base: 228-unified-rucio-helm-charts
Are you sure you want to change the base?
Proposal for a single rucio chart with complete reproducible deployment of rucio #217
Conversation
Hey @volodymyrss, I am not able to access the link to the talk ( probably due to access restrictions). Could you please highlight what are the global variables you'd use that are accessible to all the sub-charts? |
Hi @maany , thanks for having a look on this draft proposal! Please see updated link, it should work.
For example, database configuration and rucio version. Please have a look here of our integrated chart we use : https://gitlab.cta-observatory.org/cta-computing/dpps/bdms/bdms/-/tree/main/chart (this one with test values) |
We will merge this branch into |
@volodymyrss please can you rebase / fix conflicts and I will merge this branch into the |
Related to #228
We decided to split this PR into multiple smaller PRs. This PR will be just a reordering of charts.
Original comment below.
The principle agreed with @bari12 on Rucio-Dirac workshop, but not the technical details of the chart implementation.
In CTAO we made a chart of our Bulk Data Management System (BDMS) including as subcharts rucio charts, optional dependencies charts, and adding jobs for bootstrap and configure. See a talk.
This would require several changes ported to upstream rucio chart:
rucio-server
,rucio-demons
, etc charts to be subcharts ofrucio
chart.Please let me know if this set of changes makes sense!
The PR is started as a draft, just starting to move.