-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
types: aquilon: add new structure_entitlements in the system parameters #189
Conversation
Can one of the admins verify this patch? |
This depends on #184 |
@hpcugentbot please test this please |
@hpcugentbot please test this please |
@XaF please, could you give a few examples of values assigned to the new structure to illustrate how it is intended to be used? |
@hpcugentbot retest this please |
@XaF we could still do with some documented examples of content/annotations explaining the purpose of these fields. |
A new entitlement system is being added to the Aquilon broker. It will allow to set entitlements of a given type (for instance, 'login' or 'root') and enable them by host, cluster, personality, archetype or Grn/EonID. These new entitlements need to be stored to be picked up by the templates in order to act on them, and this is why the structure_entitlements is being added: we will now have in the structure_system_aquilon structure an "entitlements" dictionary that will use the entitlements type as key, and a structure_entitlements as value. In there, we will find entitlements per-EonID or per-user. In the later case, the user type (also being added to the broker) will also be mentioned (as to, for instance, insure some activities are only being entitled for system users).
Force pushed update to resolve conflict. |
@hpcugentbot retest this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to merge this as is and open and issue to add examples.
A new entitlement system is being added to the Aquilon broker. It will
allow to set entitlements of a given type (for instance, 'login' or
'root') and enable them by host, cluster, personality, archetype or
Grn/EonID.
These new entitlements need to be stored to be picked up by the
templates in order to act on them, and this is why the
structure_entitlements is being added: we will now have in the
structure_system_aquilon structure an "entitlements" dictionary that
will use the entitlements type as key, and a structure_entitlements
as value. In there, we will find entitlements per-EonID or per-user.
In the later case, the user type (also being added to the broker)
will also be mentioned (as to, for instance, insure some activities
are only being entitled for system users).