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

fts-cron is not multi-VO capable #177

Open
Thysk opened this issue Feb 1, 2022 · 2 comments
Open

fts-cron is not multi-VO capable #177

Thysk opened this issue Feb 1, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request Multi-VO

Comments

@Thysk
Copy link

Thysk commented Feb 1, 2022

FTS-cron takes the arguments of one VO and one VOMS/role, this doesn't allow for multi-VO setups which require multi-VOs and multiple voms

Adding a check for multi-vo=true in many of the proxy generations, and delegations.
Rucio can then look at the locations specified in the config for the proxy.
The difficulty is then locating the certs and keys for the proxies.

Is there a standardised place to place these? /opr/rucio/keys/, /opt/rucio/certs/
or for multi-VO should I specify a location within multi-VO?

I think the difficulty would then be to generate all the proxies and delegations as needed for continuous access. But this could be appended to the renew_fts_proxy.sh rather than override, so if many VOs were specified the script would be longer.

@Thysk Thysk added enhancement New feature or request Multi-VO labels Feb 1, 2022
@Thysk Thysk self-assigned this Feb 1, 2022
@bari12
Copy link
Member

bari12 commented May 20, 2022

Any update on this?

@Thysk
Copy link
Author

Thysk commented May 25, 2022

Ah sorry, no. Had a quick look and I havent done anything here yet,

Need to figure out how to get a list of VOs, and generate the voms-proxy against the VO, and then deligate to the FTS as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Multi-VO
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants