Re: [HTCondor-users] Pool PC config: transition from 7.x to 8.0...

[Todd Tannenbaum <tannenba@xxxxxxxxxxx>]

On 9/23/2013 7:29 AM, Stut wrote:
> Hi,
>
> I may want to upgrade from 7.x to 8.0 on Windows pool PCs.
> I wonder what has changed in the (local) configuration.
> I now use following local configuration:
>
> Are these macros still valid in 8.0?
> Which section of the manual can help me out here?

The Version History section of the manual is a pretty exhaustive listing 
of things that have changed.  In addition, note it contains a section of 
incompatibility issues for folks upgrading from the previous stable 
series to the current stable series.

http://research.cs.wisc.edu/htcondor/manual/v8.0/10_Version_History.html

Usually the list of incompatibilities is pretty small - the developers 
invest a lot of time keeping things as backwards compatible as possible.

> How can I let a pool PC occasionally run benchmarks?

Probably your old config will continue to operate the same way with 
benchmarks, as the default value for the various config options will set 
things up to work the same as they did for many years.  During the 
v7.5.x release, the code was changed so the benchmarks run are no longer 
hard-coded but instead can be specified or changed.  Here are the 
relevant settings from the default condor_config:

##  When a machine unclaimed, when should it run benchmarks?
##  LastBenchmark is initialized to 0, so this expression says as soon
##  as we're unclaimed, run the benchmarks.  Thereafter, if we are
##  unclaimed and it has been at least 4 hours since we ran the last
##  benchmarks, run them again.  The startd keeps a weighted average
##  of the benchmark results to provide more accurate values.
##  Note, if you don't want any benchmarks run at all, either comment
##  RunBenchmarks out, or set it to "False".
BenchmarkTimer = (time() - LastBenchmark)
RunBenchmarks : (LastBenchmark == 0 ) || ($(BenchmarkTimer) >= (4 * 
$(HOUR)))
#RunBenchmarks : False

##  When the startd does benchmarks, which set of benchmarks should we
##  run?  The default is the same as pre-7.5.6: MIPS and KFLOPS.
benchmarks_joblist = mips kflops

##  What's the max "load" of all running benchmarks?  With the default
##  (1.01), the startd will run the benchmarks serially.
benchmarks_max_job_load = 1.0

#  MIPS (Dhrystone 2.1) benchmark: load 1.0
benchmarks_mips_executable = $(LIBEXEC)/condor_mips
benchmarks_mips_job_load = 1.0

#  KFLOPS (clinpack) benchmark: load 1.0
benchmarks_kflops_executable = $(LIBEXEC)/condor_kflops
benchmarks_kflops_job_load = 1.0

--
Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of Wisconsin-Madison
Center for High Throughput Computing   Department of Computer Sciences
HTCondor Technical Lead                1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132                  Madison, WI 53706-1685