Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] [newb] setting up 2nd machine
- Date: Tue, 26 Jan 2010 11:51:26 -0600
- From: Alan De Smet <adesmet@xxxxxxxxxxx>
- Subject: Re: [Condor-users] [newb] setting up 2nd machine
Neal Becker <ndbecker2@xxxxxxxxx> wrote:
> I've got my first 8-core machine running fine. Setup on fedora 12 from
> condor rpm.
>
> Now I'd like to add a second machine that acts as a compute server. Real
> basic requirements - no parallel stuff.
>
> I've tried reading the docs, but I'm still clueless. What do I need to do?
Based on your description, I'm assuming that your first machine
is running a schedd, a startd, a collector, and a negotiator.
That is, it's an entirely self-contained pool. Given that, your
next steps are:
0. Ensure that the two machines have unrestricted network access
to each other. (Condor can cope with firewalls and NATs, but
that's a more complex question.)
1. Install Condor on the second machine.
2. Configure Condor on the second machine to only run the startd.
(And the master. You always run a master.)
3. Configure Condor on the second machine to report to the
collector on the first machine.
4. Ensure that the first machine is configured to accept writes
from the second machine
5. Ensure that the second machine is configured to accept writes
from the first.
condor_configure/condor_install can probably handle steps 1-3 for
you. You'll want something like:
condor_configure --type=execute --central-manager=first.example.com
--type=execute will set it up to run the startd.
--central-manager=first-machine.com will have it report to the
collector on the first machine. Obviously change
"first.example.com" to the actual name of your first machine.
Steps 4-5 are more complex. The simple option is to set
ALLOW_WRITE=first.example.com,second.example.com
assuming your machines are called first.example.com and
second.example.com. Set that in the configuration files for both
machines. The down side of this is that _anyone_ on first or
second can join in the Condor pool; we're essentially relying on
the machines themselves being secure and the IP addresses not
being hijacked. You can have a much higher level of security,
but it's more complicated.
--
Alan De Smet Condor Project Research
adesmet@xxxxxxxxxxx http://www.cs.wisc.edu/condor/