[HTCondor-devel] Dan, quick question re shared port server


Date: Thu, 17 Jan 2013 17:26:48 -0600
From: Todd Tannenbaum <tannenba@xxxxxxxxxxx>
Subject: [HTCondor-devel] Dan, quick question re shared port server
Hi Dan -

When using the shared port server on the central manager (collector machine), things get a little complicated. Users either need to 1. open up two ports on their firewall for the central manager (one for the collector, one for the shared_port), or 2. open just one port on their firewall for the shared_port, but then they need to edit CONDOR_HOST everywhere on all nodes (including flocking), and also intuitive things like "condor_status -pool hostname.com" will not work as it used to.

Could we do better? The simple idea (credit: zmiller) is if the shared_port sees a malformed request (e.g. a stream that does not begin w/ a proper daemon name), the shared_port would send it to the collector by default if a collector is registered. The hope is this heuristic would enable us to run the shared_port on port 9618 everywhere including the central manager, and yet no need to modify CONDOR_HOST etc. We wanna have our cake and eat it as well.

Possible? Crazy? If you think it is reasonable/possible, we'll make a ticket.

thanks
Todd

--
Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of Wisconsin-Madison
Center for High Throughput Computing   Department of Computer Sciences
HTCondor Technical Lead                1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132                  Madison, WI 53706-1685
[← Prev in Thread] Current Thread [Next in Thread→]