The deb package installs the condor config method, and the deb package condorconfig
I. deb package installation of condor Method
Download it by yourselfCondor-8.2.6-287355-ubuntu_14.04_amd64.deb. I also downloadedLibmpich2-3_1.4.1-4.2_amd64.debPackage. This is a dependency package required by condor. If apt-get cannot solve this problem, install it on your own. I have created a condor user and added it to sudoers. The following operations are all performed under condor.
Install the deb package
$Sudo dpkg-I condor-8.2.6-287355-ubuntu_14.04_amd64.deb
At this time, it is usually prompted that many dependent packages are not installed, don't worry, and solve it slowly
$Sudo apt-get update
$Sudo apt-get install-f
$Sudo dpkg-I libmpich2-3_1.4.1-4.2_amd64.deb
$Sudo apt-get sysv-rc-conf
$Sudo sysv-rc-conf condor on
$Sudo service condor on
Ii. condor cluster configuration method
Here, my manager is10.1.1.25This function only submits tasks and does not execute them.
Slave1 is10.1.1.253. Slave2 is10.1.1.196, The function is the same as slave1.
Database is10.1.1.160, Slave interacts with storage to operate databases.
1. First, let's look at the master configuration. The configuration file is/Etc/condor/condor_configHere, I only give
It must be noted that the CONDOR_HOST parameter is followed by the manager address. DAEMON_LIST
2. slave Configuration
Well, now I want to explain DAEMON_LIST. This is the condor process of the local machine. The processes of machines with different roles are different.
Central Management host (executable)
DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD, STARTD
Central Management host (submit only but not execute)
DAEMON_LIST = COLLECTOR, MASTER, NEGOTIATOR, SCHEDD
Job submission host
DAEMON_LIST = MASTER, SCHEDD
Job execution host
DAEMON_LIST = MASTER, STARTD
Use DAEMON_LIST after modification
$Sudo service condor restart
Restart condor and use
$Pstree | grep condor
You can view the condor processes on the local machine. On the manager, you can see
On slave, you can see
After submitting a job with condor_submit, you can see it in the log file
The job is submitted by 10.1.1.25 and executed by 10.1.1.196. The configuration is correct.
Reprinted please indicate the source