You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
In current AAD, we have a strong requirement that every vc need a dedicated group, which means resource acl depends on external user/groups. This issue is to decouple them.
Design
Current user/group model:
New user/group model:
From implementation, basically, we will move virutal cluster out of user and into group schema: users belong to some groups, and groups define resource.
In current AAD, we have a strong requirement that every vc need a dedicated group, which means resource acl depends on external user/groups. This issue is to decouple them.
Design
Current user/group model:

New user/group model:

From implementation, basically, we will move virutal cluster out of user and into group schema: users belong to some groups, and groups define resource.
User schema(generated/updated from aad):
virtualCluster: vc1, vc2Group schema(maintained by admin):
groupType: vc/admin/stroageacls: {
virtualClusters: vc1, vc2,
storageConfigs: storageConfig1, storageConfig2,
admin: true/false,
etc
}
Login: only groups with vc access could login.
Items:
update storage logic with new schemaTBDThe text was updated successfully, but these errors were encountered: