🤔 Problem

Admin workload for managing users and resource pools is too high.

🍴 Appetite

🎯 Solution

Revamp Resource Pool Membership: use authz and allow groups to be attached to resource pools.

Migrate the resource pool membership model to authz: describe a resource pool by its ID and allow users and groups as members. Detail: if we keep to the current access levels, members would have “read” membership which will allow using the resource pool.

We will need to migrate current resource pool members from db to authz.

In the future: attach one (or more) group(s) to newly created resource pools. Tell the group owners that when new users are added to their group, then members have also access to the corresponding resource pool(s).

In the UI, show resource pool access from a group page for members.

To be considered: should we also attach projects to resource pools? Does this fit better into the usage model of projects and compute resources? Should we instead attach projects and not groups?

🚞 User stories / journeys

🐰 Rabbit Holes

Side quests:

• resource pool expiry date (see for example CSCS projects) → prevents accumulation of 100+ resource pools
• membership expiry date → prevents leftover access e.g. for student projects