Mon Apr 14 06:36:51 PDT 2008
- Previous message: [Slony1-general] Re: Small tool to make Slony management easier
- Next message: [Slony1-general] Re: Small tool to make Slony management easier
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In response to Dane Miller <dane at greatschools.net>: > Bill Moran wrote: > > Each of our DB servers has multiple IP addresses and firewall policies > > dictate who can talk to who. For example, two DB servers in the same > > data center will talk directly to each other on their DB IPs, whereas > > a DB server in another facility will have to go through two firewalls > > and connect to another DB's management IP. In somewhat less abstract > > terms, if I have 3 servers: > > db0 - datacenter 1 > > db1 - datacenter 1 > > db2 - datacenter 2 > > > > If I execute slonik commands from db1, it will use the hostname > > db0-db to connect to db0, but db2 will use the hostname db0-mgmnt. > > Clever. Thanks for the info, this helped my understanding a lot. Out > of curiosity, couldn't you also tunnel the inter-datacenter db traffic > and add some routes down the tunnel to simplify slony config paths? Sure, but that would make our firewall rules more complex. It's a tradeoff. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran at collaborativefusion.com Phone: 412-422-3463x4023
- Previous message: [Slony1-general] Re: Small tool to make Slony management easier
- Next message: [Slony1-general] Re: Small tool to make Slony management easier
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list