[Moabusers] floating licenses and SR's

Brock Palen brockp at umich.edu
Tue Jul 17 12:21:37 MDT 2007


This is the version we have running:

[root at nyx moab-5.1.0-p5]# /usr/local/moab-5.1.0/sbin/moab --about
defaults:   server=:42559  cfgdir=/opt/moab  vardir=/opt/moab
build args: -r
moab server version 5.1.0p4 (snap NA) (rev. 7059M)
Copyright 2000-2007 Cluster Resources, Inc., All Rights Reserved
Moab Workload Manager Version '5.1.0p4' License Information:
   Current License:  Max Procs   = 3538
   Current License:  Valid Until - Sun Jul  6 14:56:22 2008


Looks like we also have p5 installed but its not the active moab.

Brock Palen
Center for Advanced Computing
brockp at umich.edu
(734)936-1985


On Jul 17, 2007, at 2:19 PM, Douglas Wightman wrote:

> Can you send output of "moab --about"?  It  would be useful for us to
> see what revision you are working on.
>
> Thanks,
>
> - Douglas
>
> On Tue, 2007-07-17 at 14:17 -0400, Brock Palen wrote:
>> 5.1.0
>>
>> Client tools are:
>>
>> 5.1.0p3
>>
>> Brock Palen
>> Center for Advanced Computing
>> brockp at umich.edu
>> (734)936-1985
>>
>>
>> On Jul 17, 2007, at 2:04 PM, Douglas Wightman wrote:
>>
>>> This is fixed in later releases.  What version of Moab are you  
>>> using?
>>>
>>> - Douglas
>>>
>>> On Tue, 2007-07-17 at 10:55 -0400, Brock Palen wrote:
>>>> We have a machine that we have a SR defined on it. Like so:
>>>>
>>>> CLASSCFG[bigmem]    QLIST=bigmem  PRIORITY=-50000
>>>> DEFAULT.FEATURES=bigmem
>>>>
>>>> SRCFG[bigmem]   CLASSLIST=bigmem,bigmem_r
>>>> SRCFG[bigmem]   ACCOUNTLIST=cacstaff
>>>> SRCFG[bigmem]   PERIOD=INFINITY
>>>> SRCFG[bigmem]   HOSTLIST=nyx800
>>>> SRCFG[bigmem]   FLAGS=IGNSTATE
>>>>
>>>> We also have software defined like so:
>>>>
>>>> NODECFG[GLOBAL] GRES=stata:10
>>>>
>>>> Is a user submits a job that looks like:
>>>> #!/bin/sh
>>>> #PBS -N makebigdata_bigmem
>>>> #PBS -q bigmem
>>>> #PBS -l  
>>>> nodes=1:ppn=1,walltime=06:00:00,mem=58000mb,software=stata:1
>>>>
>>>> stata -b "do makebigdata_bigmem.do"
>>>>
>>>> The job will never run with the following:
>>>>
>>>> GLOBAL                   rejected: Features
>>>>
>>>> Can we not make a 'default features'  like in the CLASSCFG?  and  
>>>> the
>>>> GLOBAL node then does not have this feature so it will never  
>>>> run?  Is
>>>> there a way around this?
>>>>
>>>> Brock Palen
>>>> Center for Advanced Computing
>>>> brockp at umich.edu
>>>> (734)936-1985
>>>>
>>>>
>>>> _______________________________________________
>>>> moabusers mailing list
>>>> moabusers at supercluster.org
>>>> http://www.supercluster.org/mailman/listinfo/moabusers
>>>
>>>
>>>
>>
>
>
>



More information about the moabusers mailing list