Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:some_examples_of_admission_rules [2017/05/11 15:32]
mvesin [Example 5:]
wiki:some_examples_of_admission_rules [2020/04/07 22:01] (current)
neyron [Example 5: verify correct resources definitions]
Line 138: Line 138:
 </​code>​ </​code>​
  
-==== 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: verify correct resources definitions ====
 +
 +Verify that the ''​oarsub -l [resource request]''​ gives a correct resources definition.
 +
 +OAR resource request hierarchies are implicit in the OAR database, but they can be enforced by an admission rule.
 +
 +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). A GPU never spans several CPUs. The disk property defines special resources to reserve disks on hosts, independently from cpu, gpu and core properties. The license property is yet a completely independent type of resource. ​
 +
 +Any of those resources properties can define a valid hierarchy or resources, for instance:
 +  * ''​oarsub -l switch=2/​core=1''​ → get 2 cores on different switches
 +  * ''​oarsub -l cluster=1/​host=2/​disk=1''​ → get 2 disks of 2 different hosts but on a same cluster
 +  * ''​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 host=1/​disk=1/​core=1''​ → cannot mix disk and core
 +  * ''​oarsub -l switch=1/​cluster=1/​switch=1''​ → obviously wrong
 +
 +==Answer==
 +
 +<code perl>
 +
 +# definition of the valid implicit hierarchies of resources.
 +my %valid_children = (
 +                # both cluster > switch and switch > cluster are relevant
 +                "​cluster" ​ => ["​switch",​ "​cpu",​ "​host",​ "​core",​ "​gpu",​ "​disk"​],​
 +                "​switch" ​  => ["​cluster",​ "​cpu",​ "​host",​ "​core",​ "​gpu",​ "​disk"​],​
 +                "​host" ​    => ["​cpu",​ "​core",​ "​gpu",​ "​disk"​],​
 +                "​cpu" ​     => ["​core",​ "​gpu"​],​
 +                "​gpu" ​     => ["​core"​],​
 +                "​disk" ​    => [],
 +                "​license" ​ => [],
 +                );
 +
 +# nodes is synonym of host
 +my %aliases = (
 +        "​nodes"​ => "​host",​
 +);
 +
 +# valid values are in one of the possible hierarchies
 +my %valid_resources;​
 +foreach my $key (keys %valid_children) {
 +        $valid_resources{$key} = undef;
 +        foreach my $child (@{%valid_children{$key}}) {
 +                $valid_resources{$child} = undef;
 +        }
 +}
 +my @valid_resources = keys %valid_resources;​
 +
 +# test the user's request for possible errors
 +foreach my $mold (@{$ref_resource_list}) { # loop on all moldable resources requests (oarsub -l ... -l ...)
 +        foreach my $r (@{$mold->​[0]}) { # loop on all joint resources requests (oarsub -l ...+...)
 +                my @resources_hierarchy;​
 +                my $parent_resource;​
 +                foreach my $h (@{$r->​{resources}}) { # loop on every resource, look at the resource name only ($h->​{resource}) not the value ($h->​{value})
 +                        if(!grep { $_ eq $h->​{resource} } @valid_resources) {
 +                                die("​[ADMISSION RULE] Error: the requested resources '​$h->​{resource}'​ is not valid, please check your syntax.\n"​);​
 +                        }
 +                        if (!grep { $_ eq $h->​{resource} } @resources_hierarchy) {
 +                                push @resources_hierarchy,​ $h->​{resource};​
 +                        } else {
 +                                # catching the case `oarsub -l /​cluster=a/​switch=b/​cluster=c` or `oarsub -l /​switch=a/​cluster=b/​switch=c`
 +                                push @resources_hierarchy,​ $h->​{resource};​
 +                                die("​[ADMISSION RULE] Error: duplicated resource '​$h->​{resource}'​ in the requested resources hiearchy '"​.join("​ > ", @resources_hierarchy)."'​.\n"​);​
 +                        }
 +                        if (defined($parent_resource)) {
 +                                if (!grep { $_ eq $h->​{resource} } @{$valid_children{$parent_resource}}) {
 +                                        die("​[ADMISSION RULE] Error: the requested resources hierarchy '"​.join("​ > ", @resources_hierarchy)."'​ is not relevant.\n"​);​
 +                                }
 +                        }
 +                        if (exists $aliases{$h->​{resource}}) {
 +                                $parent_resource = $aliases{$h->​{resource}};​
 +                        } else {
 +                                $parent_resource = $h->​{resource};​
 +                        }
 +                }
 +        }
 +}
 +</​code>​
wiki/some_examples_of_admission_rules.1494509578.txt.gz · Last modified: 2017/05/11 15:32 by mvesin
Recent changes RSS feed GNU Free Documentation License 1.3 Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki