3 ms·
> don't see why you couldn't use this system for expressing requirements regarding licenses People do just that: http://www.cs.wisc.edu/condor/techpaper/licens
by timf 17y ago
> don't see why you couldn't use this system for expressing requirements regarding licenses
People do just that: http://www.cs.wisc.edu/condor/techpaper/licenses.html http://www.cs.wisc.edu/condor/techpaper/licenses.html
I would not say it is "complex" but ultra flexible. You will not have things working in just one day or anything, but I've set it up without a significant hassle. People have had a lot of ongoing success with Condor in large (and very large) computing environments.
- cabacon 17y agoI'd agree that "length of manual" is a poor heuristic for complexity. Condor is super-customizable, and they document those options pretty extensively. To the direct point, they've even started highlighting the use of condor as "condor cron" in the Open Science Grid to run monitoring applications: http://vdt.cs.wisc.edu/releases/1.10.1/notes/Condor-Cron.html http://vdt.cs.wisc.edu/releases/1.10.1/notes/Condor-Cron.htm... Without that, I'd say it would be a slightly masochistic exercise to take a big system like condor and try to make it a cron replacement; while it clearly has that capability, if that's not one of its use cases, it's going to be a real bear to force it into that configuration. I've been a fringe user of condor before, and it can result in some unfriendly "rejected your job for unknown reasons" situations.