Differences

This shows you the differences between two versions of the page.

--- wiki:some_examples_of_admission_rules [2020/04/07 21:51] – neyron
+++ wiki:some_examples_of_admission_rules [2020/04/07 21:54] – [Example 5: verify correct resources definitions] neyron
@@ Line 254: / Line 254: @@
 Lets assume that valid resources hierarchies are:
-  * switch > cluster > host > cpu > gpu > core
+  * ''switch > cluster > host > cpu > gpu > core''
-  * cluster > switch > host > cpu > gpu > core
+  * ''cluster > switch > host > cpu > gpu > core''
-  * cluster > switch > host > disk
+  * ''cluster > switch > host > disk''
-  * switch > cluster > host > disk
+  * ''switch > cluster > host > disk''
-  * license
+  * ''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.
 Any of those resources properties can define a valid hierarchy or resources, for instance:
-  * <code>oarsub -l switch=2/core=1</code> → get 2 cores on different switches
+  * ''oarsub -l switch=2/core=1'' → get 2 cores on different switches
-  * <code>oarsub -l cluster=1/host=2/disk=1</code> → get 2 disks of 2 different hosts but on a same cluster
+  * ''oarsub -l cluster=1/host=2/disk=1'' → get 2 disks of 2 different hosts but on a same cluster
-  * oarsub -l license=1</code> → get 1 license
+  * ''oarsub -l license=1'' → get 1 license
 But incorrect hierachry should raise an error:
-  * oarsub -l gpu=1/host=2 → cannot get 2 hosts for a same gpu
+  * ''oarsub -l gpu=1/host=2'' → cannot get 2 hosts for a same gpu
-  * oarsub -l host=1/disk=1/core=1 → cannot mix disk and core
+  * ''oarsub -l host=1/disk=1/core=1'' → cannot mix disk and core
+  * ''oarsub -l switch=1/cluster=1/switch=1'' → obviously wrong
 ==Answer==