Hi- can someone briefly explain how the bbproxy stuff works? We have a cluster whose "head node" is accessible, but the cluster nodes are hidden behind that server.
If someone can explain how something like this is set up, that'd be super..
============================================================= (network) [hobbit server] [most of my nodes] [head node] || || [cluster nodes]
Kent C. Brodie - brodie at phys.mcw.edu Department of Physiology Medical College of Wisconsin (414) 456-8590
On Fri, Jul 14, 2006 at 02:18:58PM -0500, Brodie, Kent wrote:
Hi- can someone briefly explain how the bbproxy stuff works? We have a cluster whose "head node" is accessible, but the cluster nodes are hidden behind that server.
If someone can explain how something like this is set up, that'd be super..
============================================================= (network) [hobbit server] [most of my nodes] [head node] || || [cluster nodes]
Since your cluster nodes can talk to the head node, and the head node can talk to the hobbit server, the most simple solution would be to run bbproxy on the head node of the cluster.
Your cluster nodes would then use the head node's bbproxy as their BBDISPLAY server. bbproxy on the head node would be configured to forward messages to the real hobbit server.
Henrik
I'm finishing to centralize the logging of all of our network switch and netapp filers on one server (the machine that also run Hobbit Server) and I want to use logfetch and Hobbit log monitoring functionality to check those log files and create alerts.
Is possible in some way (or in a future version) to start logfetch and report his data as another client without running the entire hobbit client? The ideal setup would be of logfetch running on the hobbit server that check messages files in various directory and report for each file as a different client ...
Someone already used the log monitoring feature in a similar way?
Thanks
Francesco Duranti
participants (3)
-
brodie＠mcw.edu
-
fduranti＠q8.it
-
henrik＠hswn.dk