Re: [Condor-devel] Is Redefining OpSys a Good Idea?

[Matthew Farrellee <matt@xxxxxxxxxx>]

First, re can -

LOCAL_CONFIG_FILE = /home/matt/DWA_LSB.sh|
Requirements = TARGET.DWA_LSB_Version =?= MY.DWA_LSB_Version
SUBMIT_EXPRS = DWA_LSB_Version, DWA_LSB_Id, DWA_LSB_Release, Requirements

$ echo 'cmd=/bin/sleep\nargs=1d\nqueue' | condor_submit
Submitting job(s).
1 job(s) submitted to cluster 1637.

$ condor_q -l | grep DWA
AutoClusterAttrs = 
"JobUniverse,LastCheckpointPlatform,NumCkpts,DWA_LSB_Version,FileSystemDomain,DiskUsage,ImageSize,RequestMemory,Requirements,NiceUser,ConcurrencyLimits"
DWA_LSB_Release = 13
DWA_LSB_Id = "Fedora"
DWA_LSB_Version = ":core-4.0-amd64:core-4.0-noarch"
Requirements = ( TARGET.DWA_LSB_Version =?= MY.DWA_LSB_Version ) && ( 
TARGET.Arch == "X86_64" ) && ( TARGET.OpSys == "LINUX" ) && ( 
TARGET.Disk >= DiskUsage ) && ( ( TARGET.Memory * 1024 ) >= ImageSize ) 
&& ( ( RequestMemory * 1024 ) >= ImageSize ) && ( 
TARGET.FileSystemDomain == MY.FileSystemDomain )

But, use a LOCAL_CONFIG_DIR and drop the system type into it, don't use 
LOCAL_CONFIG_DIR=script| syntax, or if you must, scope it to TOOL. The 
script is generating information that is a property of the system. Maybe 
use rc.local.

Second, re should -

It surely depends on your pool use cases. I would provide the data and 
maybe a thin layer specific user groups can take advantage of for their 
applications. Requirements is a heavy hammer vs Rank when you do not 
know the application is problematic.

There is a non-technical issue here in how applications are managed and 
pooled OSes are provided. The major Linux distributions these days 
provide a stable stream with will defined break points. Condor provides 
$$ options for executable selection.

Best,


matt

On 09/13/2011 02:20 PM, Douglas Thain wrote:
> All -
>
> I love static linking, application virtualization, and apple pie, but
> any solution that requires the user to take some positive action is
> unlikely to work in practice  :(
>
> Defining OpSys to be much more specific (RHEL6 as opposed to LINUX)
> makes it more likely that the user will get a machine compatible with
> the submitting machine when they follow a simple hello world example.
> The experts will figure out how to make the requirements expression
> longer when they need to.
>
> I'll add some thoughts to the wiki page to that effect...
>
> My $.02 -
>
> Doug
>
>
>
> On Tue, Sep 13, 2011 at 2:13 PM, Todd Tannenbaum<tannenba@xxxxxxxxxxx>  wrote:
> > > > Is OpSys hard coded anywhere that would prevent this from working?
> >
> > IIRC, OpSys is not hard-coded and can be over-ridden in condor_config.
> >
> > However, please take a look at the below URL Nick sent - it describes the
> > changes to OpSys and friends we propose doing in the very near future. We
> > would love folks (Todd has images of Doug and Ian's big brains in his head)
> > to leave a comment on the ticket saying if you think the proposal will leave
> > things in a better or worse state, and/or any additional thoughts/edits.
> >   Open source is a community effort, yada yada....
> >
> > Thanks,
> > Todd
> >
> > > > Does anyone have a better solution to dealing with the Linux mess?
> > >
> > > See https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2366
> > >
> > > -Nick
> >
> >
> > --
> > Todd Tannenbaum                       University of Wisconsin-Madison
> > Center for High Throughput Computing  Department of Computer Sciences
> > tannenba@xxxxxxxxxxx                  1210 W. Dayton St. Rm #4257
> > Phone: (608) 263-7132                 Madison, WI 53706-1685
> _______________________________________________
> Condor-devel mailing list
> Condor-devel@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-devel