Hello everyone,
We have a bit of a predicament at my work and I am hoping the knowledge of this mailing list can help out! I shall explain what we have / need and hopefully there shall be a solution :)
We currently have 3 data centres, and would like a hobbit server in each. Our design is to have all servers in one data centre communicating with the hobbit within that data centre. We would then want the hobbit servers to communicate between each other to share the knowledge of the tests so each hobbit has a full view of all 3 data centres.
I have currently configured each hobbit to have knowledge of the others by changing BBDISP to 0.0.0.0 and BBDISPLAYS to the 3 hobbit server IP's. I have then configured all our clients to talk only to the the hobbit within the local data centre.
So far I have observed that any server side test replicates fine across all hobbits, however it seems for any client side scripts that are run, that only the hobbit the client reports to will get the data and wont share it with the other two. We don't want to have to configure each client to talk to all 3 hobbits as this will increase the network chatter.
Hopefully I've explained that well enough, does this make sense and is there a way around it?
Many thanks in advance for your time, James.
How are your client side scripts talking to the server. (eg using bb data?)
David Peters
+61 2 63913565 +61 4 17863572
This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.
Hi David,
Our client scripts use the standard:
$BB $BBDISP "status $MACHINE.$TEST $COLOUR date
$MSG
"
call to send the message out to the server. Within the config file on each client we have clients in data centre A configured to send data to Hobbit A, clients in data centre B to send data to hobbit B, and clients in data centre C to send to hobbit C.
Thanks, James ----- Original Message ----- From: david.peters at dpi.nsw.gov.au To: hobbit at hswn.dk Sent: Thursday, July 02, 2009 1:19 AM Subject: Re: [hobbit] Multiple Hobbit server clusters
How are your client side scripts talking to the server. (eg using bb data?)
David Peters
+61 2 63913565 +61 4 17863572
This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.
You might want to take a look at the bbproxy man page: http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html
<http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html>I haven't used it myself, but I'm sure others here have.
If you have the option of setting up a private network between the 3 hobbit servers, you ought to be able to push the bbproxy output over it, thereby keeping all the hobbit traffic off your main network. Or I could be all wet
- I have no idea if that would work... :)
Ralph Mitchell
On Wed, Jul 1, 2009 at 2:42 PM, James <j.sansford at ntlworld.com> wrote:
Hello everyone,
We have a bit of a predicament at my work and I am hoping the knowledge of this mailing list can help out! I shall explain what we have / need and hopefully there shall be a solution :)
We currently have 3 data centres, and would like a hobbit server in each. Our design is to have all servers in one data centre communicating with the hobbit within that data centre. We would then want the hobbit servers to communicate between each other to share the knowledge of the tests so each hobbit has a full view of all 3 data centres.
I have currently configured each hobbit to have knowledge of the others by changing BBDISP to 0.0.0.0 and BBDISPLAYS to the 3 hobbit server IP's. I have then configured all our clients to talk only to the the hobbit within the local data centre.
So far I have observed that any server side test replicates fine across all hobbits, however it seems for any client side scripts that are run, that only the hobbit the client reports to will get the data and wont share it with the other two. We don't want to have to configure each client to talk to all 3 hobbits as this will increase the network chatter.
Hopefully I've explained that well enough, does this make sense and is there a way around it?
Many thanks in advance for your time, James.
Try http://xymon.com/hobbit/help/manpages/man8/bbproxy.8.html
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
"When you have eliminated the impossible, that which remains, however improbable, must be the truth." --- Sir Arthur Conan Doyle
On Thu, Jul 2, 2009 at 2:28 AM, Ralph Mitchell <ralphmitchell at gmail.com>wrote:
You might want to take a look at the bbproxy man page: http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html
<http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html>I haven't used it myself, but I'm sure others here have.
If you have the option of setting up a private network between the 3 hobbit servers, you ought to be able to push the bbproxy output over it, thereby keeping all the hobbit traffic off your main network. Or I could be all wet
- I have no idea if that would work... :)
Ralph Mitchell
On Wed, Jul 1, 2009 at 2:42 PM, James <j.sansford at ntlworld.com> wrote:
Hello everyone,
We have a bit of a predicament at my work and I am hoping the knowledge of this mailing list can help out! I shall explain what we have / need and hopefully there shall be a solution :)
We currently have 3 data centres, and would like a hobbit server in each. Our design is to have all servers in one data centre communicating with the hobbit within that data centre. We would then want the hobbit servers to communicate between each other to share the knowledge of the tests so each hobbit has a full view of all 3 data centres.
I have currently configured each hobbit to have knowledge of the others by changing BBDISP to 0.0.0.0 and BBDISPLAYS to the 3 hobbit server IP's. I have then configured all our clients to talk only to the the hobbit within the local data centre.
So far I have observed that any server side test replicates fine across all hobbits, however it seems for any client side scripts that are run, that only the hobbit the client reports to will get the data and wont share it with the other two. We don't want to have to configure each client to talk to all 3 hobbits as this will increase the network chatter.
Hopefully I've explained that well enough, does this make sense and is there a way around it?
Many thanks in advance for your time, James.
Oops... :) Ralph
On Thu, Jul 2, 2009 at 1:34 AM, Josh Luthman <josh at imaginenetworksllc.com>wrote:
Try http://xymon.com/hobbit/help/manpages/man8/bbproxy.8.html
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
"When you have eliminated the impossible, that which remains, however improbable, must be the truth." --- Sir Arthur Conan Doyle
On Thu, Jul 2, 2009 at 2:28 AM, Ralph Mitchell <ralphmitchell at gmail.com>wrote:
You might want to take a look at the bbproxy man page: http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html
<http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html>I haven't used it myself, but I'm sure others here have.
If you have the option of setting up a private network between the 3 hobbit servers, you ought to be able to push the bbproxy output over it, thereby keeping all the hobbit traffic off your main network. Or I could be all wet - I have no idea if that would work... :)
Ralph Mitchell
On Wed, Jul 1, 2009 at 2:42 PM, James <j.sansford at ntlworld.com> wrote:
Hello everyone,
We have a bit of a predicament at my work and I am hoping the knowledge of this mailing list can help out! I shall explain what we have / need and hopefully there shall be a solution :)
We currently have 3 data centres, and would like a hobbit server in each. Our design is to have all servers in one data centre communicating with the hobbit within that data centre. We would then want the hobbit servers to communicate between each other to share the knowledge of the tests so each hobbit has a full view of all 3 data centres.
I have currently configured each hobbit to have knowledge of the others by changing BBDISP to 0.0.0.0 and BBDISPLAYS to the 3 hobbit server IP's. I have then configured all our clients to talk only to the the hobbit within the local data centre.
So far I have observed that any server side test replicates fine across all hobbits, however it seems for any client side scripts that are run, that only the hobbit the client reports to will get the data and wont share it with the other two. We don't want to have to configure each client to talk to all 3 hobbits as this will increase the network chatter.
Hopefully I've explained that well enough, does this make sense and is there a way around it?
Many thanks in advance for your time, James.
It's OK, that makes me useful =)
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
"When you have eliminated the impossible, that which remains, however improbable, must be the truth." --- Sir Arthur Conan Doyle
On Thu, Jul 2, 2009 at 2:40 AM, Ralph Mitchell <ralphmitchell at gmail.com>wrote:
Oops... :) Ralph
On Thu, Jul 2, 2009 at 1:34 AM, Josh Luthman <josh at imaginenetworksllc.com>wrote:
Try http://xymon.com/hobbit/help/manpages/man8/bbproxy.8.html
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
"When you have eliminated the impossible, that which remains, however improbable, must be the truth." --- Sir Arthur Conan Doyle
On Thu, Jul 2, 2009 at 2:28 AM, Ralph Mitchell <ralphmitchell at gmail.com>wrote:
You might want to take a look at the bbproxy man page: http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html
<http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html>I haven't used it myself, but I'm sure others here have.
If you have the option of setting up a private network between the 3 hobbit servers, you ought to be able to push the bbproxy output over it, thereby keeping all the hobbit traffic off your main network. Or I could be all wet - I have no idea if that would work... :)
Ralph Mitchell
On Wed, Jul 1, 2009 at 2:42 PM, James <j.sansford at ntlworld.com> wrote:
Hello everyone,
We have a bit of a predicament at my work and I am hoping the knowledge of this mailing list can help out! I shall explain what we have / need and hopefully there shall be a solution :)
We currently have 3 data centres, and would like a hobbit server in each. Our design is to have all servers in one data centre communicating with the hobbit within that data centre. We would then want the hobbit servers to communicate between each other to share the knowledge of the tests so each hobbit has a full view of all 3 data centres.
I have currently configured each hobbit to have knowledge of the others by changing BBDISP to 0.0.0.0 and BBDISPLAYS to the 3 hobbit server IP's. I have then configured all our clients to talk only to the the hobbit within the local data centre.
So far I have observed that any server side test replicates fine across all hobbits, however it seems for any client side scripts that are run, that only the hobbit the client reports to will get the data and wont share it with the other two. We don't want to have to configure each client to talk to all 3 hobbits as this will increase the network chatter.
Hopefully I've explained that well enough, does this make sense and is there a way around it?
Many thanks in advance for your time, James.
Oooh, interesting. Although I'm not entirely sure this is what I need.
The reason why we wish to have a hobbit (sorry, xymon..I'm still used to the old name!) in each data centre is in case our inter-data centre links go down.
For example, currently we only have a xymon server at site B. If the link between A and B went down, we would suddenly have no visibility of any clients in site A. Therefore we wish to have xymon servers in site A, B and C monitoring local clients to that data centre. The issue is that we do not want to have to view 3 separate xymon server pages to see the status overall, hence why I wan't all three to communicate to each other. So Xymon A can send A results to B and C, Xymon B can send B results to A and C etc.
Is this possible? I can't immediately see a way to do this with a proxy, as it just seems to be adding another layer, that would still have to send out results to all 3 xymons (so brings me back to the original situation of having each client send to all 3 xymons anyway, which is something we don't really want to do).
Or have I mis-interpreted the use of the proxy?
Ta! James
---- Ralph Mitchell <ralphmitchell at gmail.com> wrote:
You might want to take a look at the bbproxy man page: http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html
<http://192.168.1.50/xymon/help/manpages/man8/bbproxy.8.html>I haven't used it myself, but I'm sure others here have.
If you have the option of setting up a private network between the 3 hobbit servers, you ought to be able to push the bbproxy output over it, thereby keeping all the hobbit traffic off your main network. Or I could be all wet
- I have no idea if that would work... :)
Ralph Mitchell
On Wed, Jul 1, 2009 at 2:42 PM, James <j.sansford at ntlworld.com> wrote:
Hello everyone,
We have a bit of a predicament at my work and I am hoping the knowledge of this mailing list can help out! I shall explain what we have / need and hopefully there shall be a solution :)
We currently have 3 data centres, and would like a hobbit server in each. Our design is to have all servers in one data centre communicating with the hobbit within that data centre. We would then want the hobbit servers to communicate between each other to share the knowledge of the tests so each hobbit has a full view of all 3 data centres.
I have currently configured each hobbit to have knowledge of the others by changing BBDISP to 0.0.0.0 and BBDISPLAYS to the 3 hobbit server IP's. I have then configured all our clients to talk only to the the hobbit within the local data centre.
So far I have observed that any server side test replicates fine across all hobbits, however it seems for any client side scripts that are run, that only the hobbit the client reports to will get the data and wont share it with the other two. We don't want to have to configure each client to talk to all 3 hobbits as this will increase the network chatter.
Hopefully I've explained that well enough, does this make sense and is there a way around it?
Many thanks in advance for your time, James.
j.sansford at ntlworld.com wrote:
Oooh, interesting. Although I'm not entirely sure this is what I need.
The reason why we wish to have a hobbit (sorry, xymon..I'm still used to the old name!) in each data centre is in case our inter-data centre links go down.
For example, currently we only have a xymon server at site B. If the link between A and B went down, we would suddenly have no visibility of any clients in site A. Therefore we wish to have xymon servers in site A, B and C monitoring local clients to that data centre. The issue is that we do not want to have to view 3 separate xymon server pages to see the status overall, hence why I wan't all three to communicate to each other. So Xymon A can send A results to B and C, Xymon B can send B results to A and C etc.
Is this possible? I can't immediately see a way to do this with a proxy, as it just seems to be adding another layer, that would still have to send out results to all 3 xymons (so brings me back to the original situation of having each client send to all 3 xymons anyway, which is something we don't really want to do).
Depending on how many servers you can have in your hobbit cluster, you could try something like this:
Have a BBPROXY server in each data center. This will also be a network tester for just that data center. You can set this up using the BBLOCATION tag in hobbitserver.cfg file. You then separate off your BBDISPLAY servers. You could have 2 in different datacenters. You then get you proxy (and network testers) to update the 2 display servers and all your clients to update both display servers. This will require 5 servers.
Now obviously you will need to come up with some sort of failover between the 2 display servers. You could use Load Balancing (100 0 ratio) or some sort of DNS failover.
Cheers
Iain
Or have I mis-interpreted the use of the proxy?
Ta! James
participants (5)
-
david.peters@dpi.nsw.gov.au
-
iain@shihad.org
-
j.sansford@ntlworld.com
-
josh@imaginenetworksllc.com
-
ralphmitchell@gmail.com