Map users into VO's and control their allocations

[juztas]

From Orchestrator - we need to map users to VO groups (Virtual Organizations) and pass VO names back to RMs. Example is:
If Site A is a multi-VO Organization (CMS/ATLAS/OPN/ETC) - there might be a need for a fair resource allocation. The site should be able to know who the requestor is (VO, no need for individual users) and give % of the allocation. E.g.: CMS get's 50%, ATLAS - 40% and anyone else - 10%.
Once this is passed in delta - it is up to RM to identify and accept/deny delta based on resource usage/allocation.

@xi-yang

[xi-yang]

We have organization attribute from registration stored with Keycloak. We can pass that down.

This is not about a single feature but a category of features. What and how do we communicate the user context metadata to the RMs.

Another topic is: how does an RM pass custom provider resource model and information to specific Orchestrators?

We can keep this in the longer term planning.