Re: [HTCondor-users] Help on FLOCK and CCB

[Batsayan Das <batsayan.das@xxxxxxx>]

Thanks for the reply.

Is there and simple guide on  how  " we had flocking set up with several other institutions" ? The manuals are too exhaustive!!
How can I test the flocking setup configuration between pool A and B, before actual deployment?
Can somebody provide sample manager, submitter, executer config files for pool A and B?


Regards,
Batsayan Das
Tata Consultancy Services
Mailto: batsayan.das@xxxxxxx
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________

-----"HTCondor-users" <htcondor-users-bounces@xxxxxxxxxxx> wrote: -----

To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
From: Ben Cotton
Sent by: "HTCondor-users"
Date: 03/05/2014 08:16PM
Subject: Re: [HTCondor-users] Help on FLOCK and CCB

On Wed, Mar 5, 2014 at 5:58 AM, Batsayan Das <batsayan.das@xxxxxxx> wrote:
> how to define a pool?

There's probably a more rigorous definition, but I'd define a pool as
all of the machines that report to the same central manager.

> Whether pool A and pool B can be a private network?

Definitely. When I was at Purdue, we had flocking set up with several
other institutions where at least some of the machines were on private
addresses.

> how one machine in pool A talks to another machine in pool B?
> in there any routing parameters need to be set for this talking?
>

Left to their own devices, the machines will talk directly to each
other. In the case of A flocking to B, the schedd(s) in A will talk
directly to the central manager in B to negotiate, and then to the
execute nodes in B to run jobs. In cases where that's not possible,
you'll need to configure CCB.

> There may be firewalls. Should we use  Condor Connection Brokering (CCB)
> along with FLOCK ?

Maybe. If pools A and B can communicate directly if the firewalls are
removed, then you might prefer to poke the appropriate holes in your
firewalls and configure HTCondor to only use those ports (see sections
3.3.6 and 3.7 of the HTCondor Manual). If some of the hosts are on
private address space, then you'll need to use CCB. As a matter of
personal preference, I like to keep my central managers and schedds on
public space (firewalled as appropriate) and put the execute nodes
behind CCB for this sort of purpose.


Hope this helps!
BC


--
Ben Cotton
main: 888.292.5320

Cycle Computing
Leader in Utility HPC Software

http://www.cyclecomputing.com
twitter: @cyclecomputing
_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you