Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| condor:installation:network [2011/07/18 14:27] – [Add Local condor User] garrettheath4 | condor:installation:network [2011/07/19 17:57] – [Install Binaries] recompile warning garrettheath4 |
|---|
| Our pool uses a dedicated NAS server with a 2.7TB RAID 5+1 drive configuration to provide faster than normal access times to the data than normal hard drive I/O, especially data reads. | Our pool uses a dedicated NAS server with a 2.7TB RAID 5+1 drive configuration to provide faster than normal access times to the data than normal hard drive I/O, especially data reads. |
| |
| ===== Install Binaries ===== | ===== Add Local condor User ===== |
| | |
| 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 | |
| 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> | |
| | |
| ===== Add Machines to Condor Pool ===== | |
| | |
| FIXME | |
| | |
| ==== 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:\\ | 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:\\ |
| |
| 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'' .)) | 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 ==== | |
| | ===== Install Binaries ===== |
| | |
| | The NAS is used to store all of the program files that Condor needs to run. **Installing these onto the NAS only needs to happen once**, but in order to recompile the binaries onto the ''tesla.cs.wlu.edu'' NAS anyway, run this command in the terminal: |
| | <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 --owner=condor --install --verbose</code> |
| | |
| | ===== Set Machine Variables ===== |
| | |
| | Whenever the ''condor_master'' program opens, the first thing it does is look for the global configuration file. FIXME |
| |
| 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. |
