[slurm-dev] Re: slurm-dev Re: knl_generic plugin on non-KNL node

2017-10-03 Thread Le Biot, Pierre-Marie
Gamayunov [mailto:vic...@gmail.com] Sent: Thursday, September 21, 2017 3:45 PM To: slurm-dev Subject: [slurm-dev] Re: slurm-dev Re: knl_generic plugin on non-KNL node Hi Pierre-Marie, On Thu, Aug 10, 2017 at 5:27 PM, Le Biot, Pierre-Marie wrote: > >Is there a way do selectively disab

[slurm-dev] Re: slurm-dev Re: knl_generic plugin on non-KNL node

2017-09-21 Thread Victor Gamayunov
Hi Pierre-Marie, On Thu, Aug 10, 2017 at 5:27 PM, Le Biot, Pierre-Marie wrote: > >Is there a way do selectively disable the plugin on non-KNL nodes? > > non-KNL nodes will be assigned dummy features (xyz is mine) but won't be > rebooted when a constraint is specified by a job > > scontrol show

[slurm-dev] slurm-dev Re: knl_generic plugin on non-KNL node

2017-08-10 Thread Le Biot, Pierre-Marie
Hi, On 7/6/2017 2:38 AM, Victor Gamayunov wrote: > >knl_generic plugin on non-KNL node >Hi, > >i have a cluster with a mix of regular Xeon and KNL nodes. I use knl_generic >to switch KNL modes which works very well. >However, there is a side effect on non-KNL nodes: every time I allocate a >no

[slurm-dev] Re: knl_generic plugin on non-KNL node

2017-07-10 Thread Victor Gamayunov
Hi Gilles, On Fri, Jul 7, 2017 at 1:16 AM Gilles Gouaillardet wrote: > in your slurm.conf, you should have a line like this one > NodeName=n[1-4] Feature=knl Sockets=1 CoresPerSocket=68 State=UNKNOWN > at first, make sure your regular Xeon nodes do *not* have the 'knl' feature > I do have that,

[slurm-dev] Re: knl_generic plugin on non-KNL node

2017-07-06 Thread Gilles Gouaillardet
Victor, in your slurm.conf, you should have a line like this one NodeName=n[1-4] Feature=knl Sockets=1 CoresPerSocket=68 State=UNKNOWN at first, make sure your regular Xeon nodes do *not* have the 'knl' feature i guess an other option is not to have the NodeFeaturesPlugins=knl_generic lin