search

rucio / containers

Containers for Rucio
Apache License 2.0
9 stars 55 forks source link

fts-cron is not multi-VO capable #177

Open Thysk opened 2 years ago

Thysk commented 2 years ago

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.

bari12 commented 2 years ago

Any update on this?

Thysk commented 2 years ago

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