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:52] – [Example 5: verify correct resources definitions] neyron | wiki:some_examples_of_admission_rules [2020/04/07 21:55] – [Example 5: verify correct resources definitions] neyron | ||
|---|---|---|---|
| Line 248: | Line 248: | ||
| ==== Example 5: verify correct resources definitions ==== | ==== 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 254: | 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: | ||
| - | * < | + | * '' |
| - | * → get 2 cores on different switches | + | * '' |
| - | * < | + | * '' |
| - | * → get 2 disks of 2 different hosts but on a same cluster | + | |
| - | * < | + | |
| - | * → get 1 license | + | |
| But incorrect hierachry should raise an error: | But incorrect hierachry should raise an error: | ||
| - | * oarsub -l gpu=1/ | + | * '' |
| - | * → cannot get 2 hosts for a same gpu | + | * '' |
| - | * oarsub -l host=1/ | + | * '' |
| - | * → cannot mix disk and core | + | |
| ==Answer== | ==Answer== | ||