Yoda/Metalnx co-existing with differing security models

[michael-conway]

This captures some issues that were discussed at the 2021 UGM when running Metalnx and Yoda together, and potential conflicts with how security and groups are managed. This captures some of this discussion for further thought.

Yoda-security explained.pdf

• Yoda sets and uses metadata on the iRODS groups that it manages

• groups can be manipulated on iRODS level but care should be taken not to impact the metadata on the groups

• It also supposes that collections are under full control of the Yoda rulesets. To make it work we had to alter the code a bit to not consider collections that were created with the regular irods tools & Metalnx

• intention was to manage only groups named research- grp- vault- hence some prefixed namespace. broader impact might be a bug

• So it is best to use Yoda fully in its own zone. That is the way we may use it in the future should the use case for some match what Yoda offers