Internal VO handling - overview

stfc / rucio

Rucio - Scientific Data Management

http://rucio.cern.ch

Apache License 2.0

0 stars 0 forks source link

Closed elichad closed 3 years ago

elichad commented 4 years ago

Adding VO handling to the Rucio code, not including user/admin interaction with VOs.

Pass VO into InternalAccount, InternalScope, and rse_id creation. Functions should return VO-specific output where necessary.

These changes will form the first PR against the main Rucio fork. (Individual issues to be listed below.)

elichad commented 4 years ago

Design notes:

If two VOs are using the same (physical) RSE, the RSE will have a seperate rse_id for each VO in Rucio.
If one user is part of two VOs, they will have a separate account for each VO, and a separate identity for each account – i.e. identities are VO-specific.
Auditor, Automatix and Sonar are single-VO only, the latter two because they use the Client classes which are single-VO. Refactoring these daemons to be multi-VO and not use the client is low priority.