[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Dynamic Pool Configuration

Hi Rajesh,

Thank you for your reply and the pointers. It sure helped. However, I think in a grid infrastructure and assuming that a particular node will report to many central managers, it is hard to envision *all* the values for CONDOR_HOST beforehand. In other words, if a node comes alive, it should be dynamically inducted into a condor pool based on some heuristics (e.g., locality), as opposed to hardwiring the condor control manager that it will report to.

I am not sure if my point makes sense here. Please let me know your views.


On 7/7/05, Rajesh Rajamani <raj@xxxxxxxxxx> wrote:
> Imagine I have a condor pool of 50 machines which are monitored/managed
> by some "parent node". Based upon the status of these 50 nodes, the jobs
> are submitted to them.

When you say "monitored/managed", do you mean the Condor system or a
third-party management software?  I'm assuming it is the former.  Check
for information about the Central Manager

> Now, think of a new node (51st machine) that has been provisioned by
> some resource allocator. This node was not a part of the original condor
> pool. In other words, originally the "parent node" is not aware of this
> new node. My question is -- how do I make the parent node aware of the
> fact that a new machine has arrived (and it needs to be included in the
> pool and can be used for job execution, monitoring etc.) ?

Resources report to the collector, which then works with the negotiator
to schedule jobs.  All you need to do is use the proper value for
CONDOR_HOST in the config file of the new "node".  See for details.

Rajesh Rajamani
Senior Member of Technical Staff
Direct : +1.408.321.9000
Fax    : +1.408.321.9030
Mobile : +1.650.218.9131

Optena Corporation
2860 Zanker Road, Suite 201
San Jose, CA 95134

This electronic transmission (and any attached documents) contains
information from Optena Corporation and is for the sole use of the
individual or entity it is addressed to. If you receive this message in
error, please notify me and destroy the attached message (and all
attached documents) immediately.