This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| wiki:some_examples_of_admission_rules [2020/04/07 21:49] – neyron | wiki:some_examples_of_admission_rules [2020/04/07 21:55] – [Example 5: verify correct resources definitions] neyron | ||
|---|---|---|---|
| Line 138: | Line 138: | ||
| </ | </ | ||
| - | ==== Example 4: | + | ==== Example 4: limit access to a queue, based on usernames set in a file ==== |
| - | + | ||
| - | Limit access to a queue, based on usernames set in a file | + | |
| ==Answer== | ==Answer== | ||
| Line 163: | Line 161: | ||
| - | ==== Example 5: ==== | + | ==== Example 5: give a more privilege to the owners of nodes ==== |
| Give a more privilege to the owners of nodes (e.g. people who payed for the nodes) to submit, by restricting others to besteffort jobs: | Give a more privilege to the owners of nodes (e.g. people who payed for the nodes) to submit, by restricting others to besteffort jobs: | ||
| * non-owners compete on the resources according to the scheduling policy of the besteffort queue ; | * non-owners compete on the resources according to the scheduling policy of the besteffort queue ; | ||
| Line 248: | Line 246: | ||
| (There may be some limitations in that property filtering, which could allow malicious users to overcome the usage policy) | (There may be some limitations in that property filtering, which could allow malicious users to overcome the usage policy) | ||
| - | ==== Example 5: ==== | + | ==== Example 5: verify correct resources definitions |
| - | Verify that the < | + | |
| + | Verify that the '' | ||
| OAR resource request hierarchies are implicit in the OAR database, but they can be enforced by an admission rule. | OAR resource request hierarchies are implicit in the OAR database, but they can be enforced by an admission rule. | ||
| Line 255: | Line 254: | ||
| Lets assume that valid resources hierarchies are: | Lets assume that valid resources hierarchies are: | ||
| - | * switch > cluster > host > cpu > gpu > core | + | * '' |
| - | * cluster > switch > host > cpu > gpu > core | + | * '' |
| - | * cluster > switch > host > disk | + | * '' |
| - | * switch > cluster > host > disk | + | * '' |
| - | * license | + | * '' |
| Here both switch > cluster, or cluster > switch can be valid (some clusters spread their nodes on many switches, some clusters share a same switch). Disks are special resources to reserve disks on hosts, independently from cpu, gpu and cores. Licenses are yet a completly independente type of resources. | Here both switch > cluster, or cluster > switch can be valid (some clusters spread their nodes on many switches, some clusters share a same switch). Disks are special resources to reserve disks on hosts, independently from cpu, gpu and cores. Licenses are yet a completly independente type of resources. | ||
| Any of those resources properties can define a valid hierarchy or resources, for instance: | Any of those resources properties can define a valid hierarchy or resources, for instance: | ||
| - | * < | + | * '' |
| - | * < | + | * '' |
| - | * oarsub -l license=1</ | + | * '' |
| But incorrect hierachry should raise an error: | But incorrect hierachry should raise an error: | ||
| - | * oarsub -l gpu=1/ | + | * '' |
| - | * oarsub -l host=1/ | + | * '' |
| + | * '' | ||
| ==Answer== | ==Answer== | ||