]> git.donarmstrong.com Git - neurodebian.git/commitdiff
Condor to Blend
authorMichael Hanke <michael.hanke@gmail.com>
Mon, 10 Jan 2011 17:11:14 +0000 (12:11 -0500)
committerMichael Hanke <michael.hanke@gmail.com>
Mon, 10 Jan 2011 17:11:14 +0000 (12:11 -0500)
future/blends/condor [new file with mode: 0644]

diff --git a/future/blends/condor b/future/blends/condor
new file mode 100644 (file)
index 0000000..5f1e6eb
--- /dev/null
@@ -0,0 +1,26 @@
+Source: condor
+Tasks: debian-science/distributedcomputing
+Homepage: http://www.cs.wisc.edu/condor
+Responsible: NeuroDebian Team <team@neuro.debian.net>
+Language: C++, Perl
+Author: Condor Team <condor-admin@cs.wisc.edu>
+License: Apache-2.0
+WNPP: 233482
+Published-Title: Condor - A Hunter of Idle Workstations
+Published-Authors: Michael Litzkow, Miron Livny, and Matt Mutka
+Published-In: Proceedings of the 8th International Conference of Distributed Computing Systems, pp. 104-111
+Published-Year: 1988
+Registration: http://www.cs.wisc.edu/condor/downloads-v2/
+Pkg-Description: workload management system
+ Like other full-featured batch systems, Condor provides a job queueing
+ mechanism, scheduling policy, priority scheme, resource monitoring, and
+ resource management. Users submit their serial or parallel jobs to Condor,
+ Condor places them into a queue. It chooses when and where to run the jobs
+ based upon a policy, carefully monitors their progress, and ultimately
+ informs the user upon completion.
+ .
+ Unlike more traditional batch queueing system, Condor can also effectively
+ harness wasted CPU power from otherwise idle desktop workstations. Condor
+ does not require a shared file system across machines - if no shared file
+ system is available, Condor can transfer the job's data files on behalf of
+ the user.