| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| condor:installation:network [2011/07/15 19:10] – [Set Machine Variables] added chown garrettheath4 | condor:installation:network [2011/07/18 18:01] – [Install Binaries] added owner=condor garrettheath4 |
|---|
| In order to install the binaries onto the ''tesla.cs.wlu.edu'' NAS, run this command in the terminal: | In order to install the binaries onto the ''tesla.cs.wlu.edu'' NAS, run this command in the terminal: |
| <code bash>cd /mnt/config/src/fedora64 | <code bash>cd /mnt/config/src/fedora64 |
| sudo ./condor_configure --type=manager,submit,execute --central-manager=john.cs.wlu.edu --local-dir=/mnt/config/hosts/_default --install-dir=/mnt/config/release/x86_64_rhap_5 --install --verbose</code> | sudo ./condor_configure --type=manager,submit,execute --central-manager=john.cs.wlu.edu --local-dir=/mnt/config/hosts/_default --install-dir=/mnt/config/release/x86_64_rhap_5 --owner=condor --install --verbose</code> |
| |
| ===== Add Machines to Condor Pool ===== | ===== Add Machines to Condor Pool ===== |
| FIXME | FIXME |
| |
| ===== Set Machine Variables ===== | ==== Add Local condor User ==== |
| | |
| | In order for daemons to run correctly and for permissions to be properly set, a local ''condor'' user must be present on all members of the Condor pool. The following must be set for the ''condor'' users:\\ |
| | condor UID = 1344 |
| | condor GID = 1610 |
| | |
| | First, check to see if the ''condor'' user exists on the machine. Do this by running: |
| | <code bash>cat /etc/passwd | grep ^condor:</code> |
| | **If you get a match**, first reset its settings in case the user wasn't created correctly. |
| | <code bash>sudo groupmod -g 1610 condor |
| | sudo usermod -c "Owner of Condor Daemons" -d "/var/lib/condor" -m -u 1344 -g condor -s "/sbin/nologin" -L condor</code> |
| | :!: If you get a message that says that the directory ''/var/lib/condor'' already exists, run this command next: |
| | <code bash>sudo chown -R condor:condor /var/lib/condor</code> |
| | |
| | **If you do not get a match**, you need to manually add the user. To do this, run: |
| | <code bash>sudo groupadd -g 1610 condor |
| | sudo useradd -c "Owner of Condor Daemons" -d "/var/lib/condor" -m -u 1344 -g condor -s "/sbin/nologin" condor |
| | sudo usermod -L condor</code> |
| | |
| | Just to be sure, do <code bash>ls -al /var/lib/condor</code> and verify that the entry "''.''" is owned by ''condor'' and is a part of the ''condor'' group. If not, you probably have a conflicting UID or GID and will have to set it manually. Set it to one that is not being used by the local user system or by the network and then set the ''CONDOR_IDS'' variable in that individual host's Condor local configuration file((A host's individual configuration file is located at ''/mnt/config/hosts/<HOSTNAME>/config/condor_config.local'' .)) |
| | ==== Set Machine Variables ==== |
| |
| The problem with putting as much of Condor on the NAS is that this introduces a lot of NFS traffic onto the network, especially when Condor jobs are running. Having the user executables stored centrally on the NAS will cause all of the computers to be almost constantly reading from the NAS when the executables are opened and run. | The problem with putting as much of Condor on the NAS is that this introduces a lot of NFS traffic onto the network, especially when Condor jobs are running. Having the user executables stored centrally on the NAS will cause all of the computers to be almost constantly reading from the NAS when the executables are opened and run. |
| In order to do this, we need to create certain directories on every machine that are owned by the (local) ''condor'' user. These directories will serve as the playground for condor jobs when they are executing on a machine. To do this, we need to create such directories and then tell Condor where they are and what to do with them. | In order to do this, we need to create certain directories on every machine that are owned by the (local) ''condor'' user. These directories will serve as the playground for condor jobs when they are executing on a machine. To do this, we need to create such directories and then tell Condor where they are and what to do with them. |
| |
| <code bash>sudo mkdir -p /var/lib/condor/execute | <code bash>sudo mkdir /var/lib/condor/execute |
| sudo chown -R condor:condor /var/lib/condor | sudo chown -R condor:condor /var/lib/condor/execute |
| sudo chmod -R 755 /var/lib/condor</code> | sudo chmod -R 755 /var/lib/condor/execute</code> |
