Fields: Access Control Lists (ACLs)
See the associated Access Control Lists (ACLs) resource section for more information on how to use this resource and supported operations.
Additional references
| Type | Value | Additional information |
|---|---|---|
| Permissions resource | acl-rules | Permissions |
| Hooks filename | acl-rules.groovy | Pre- and Post-Processing Hooks |
| Tenant-supported | No | Tenants |
| Distinct query-supported | No | Distinct |
API version 3
This class represents a rule that can be in Moab's access control list (ACL) mechanism.
The basic AclRule information is the object's name and type. The type directly maps to an AclType value. The default mechanism Moab uses to check the ACL for a particular item is if the user or object coming in has ANY of the values in the ACL, then the user or object is given access. If no values match the user or object in question, the user or object is rejected access.
| Field Name | Type | PUT | Description |
|---|---|---|---|
| affinity | AclAffinity | Yes |
Reservation ACLs allow or deny access to reserved resources but they may also be configured to affect a job's affinity for a particular reservation. By default, jobs gravitate toward reservations through a mechanism known as positive affinity. This mechanism allows jobs to run on the most constrained resources leaving other, unreserved resources free for use by other jobs that may not be able to access the reserved resources. Normally this is a desired behavior. However, sometimes, it is desirable to reserve resources for use only as a last resort-using the reserved resources only when there are no other resources available. This last resort behavior is known as negative affinity. |
| comparator | ComparisonOperator | Yes |
The type of comparison to make against the ACL object. |
| type | AclType | Yes |
The type of the object that is being granted (or denied) access. |
| value | String | Yes |
The name of the object that is being granted (or denied) access. |
This enumeration describes the values available for describing how a rule is used in establishing access to an object in Moab. Currently, these ACL affinities are used only for granting access to reservations.
This enumeration is used when Moab needs to compare items. One such use is in Access Control Lists (ACLs).
This enumeration describes the values available for the type of an ACL Rule.
API version 2
This class represents a rule that can be in Moab's access control list (ACL) mechanism.
The basic AclRule information is the object's name and type. The type directly maps to an AclType value. The default mechanism Moab uses to check the ACL for a particular item is if the user or object coming in has ANY of the values in the ACL, then the user or object is given access. If no values match the user or object in question, the user or object is rejected access.
| Field Name | Type | PUT | Description |
|---|---|---|---|
| affinity | AclAffinity | Yes |
Reservation ACLs allow or deny access to reserved resources but they may also be configured to affect a job's affinity for a particular reservation. By default, jobs gravitate toward reservations through a mechanism known as positive affinity. This mechanism allows jobs to run on the most constrained resources leaving other, unreserved resources free for use by other jobs that may not be able to access the reserved resources. Normally this is a desired behavior. However, sometimes, it is desirable to reserve resources for use only as a last resort-using the reserved resources only when there are no other resources available. This last resort behavior is known as negative affinity. |
| comparator | ComparisonOperator | Yes |
The type of comparison to make against the ACL object. |
| type | AclType | Yes |
The type of the object that is being granted (or denied) access. |
| value | String | Yes |
The name of the object that is being granted (or denied) access. |
This enumeration describes the values available for describing how a rule is used in establishing access to an object in Moab. Currently, these ACL affinities are used only for granting access to reservations.
This enumeration is used when Moab needs to compare items. One such use is in Access Control Lists (ACLs).
This enumeration describes the values available for the type of an ACL Rule.
Related Topics