Re: [Netdisco] netdisco read-only server

[Ben C. <ben...@gm...>]

Folks,

Slony has worked very well for netdisco. I created a replication set with
all tables EXCEPT the following:

# Netdisco tables not replicated:
#   admin
#   device_port_log
#   device_port_ssid
#   device_port_wireless
#   log
#   process
#   sessions
#   user_log

This setup allows one server to do all contact with devices, while the other
server can still allow users and log their activity. You *could* replicate
the device_ tables but we don't use the wireless functionality and it's a
little more complicated to replicate tables without primary keys.

There was some work to understand slony and configure it, but the thing I
like about this is no changes were made to the netdisco install (expect by
slony - these are reversible). Even better I didn't have to start with an
identical database as slony just truncates the tables before syncing.

If anyone wants a copy of the slony scripts I created for netdisco let me
know.

B


On Tue, Jan 11, 2011 at 8:31 AM, Ben Carbery <ben...@gm...> wrote:

> Hi,
> I've discovered what looks like a good alternative to altering the netdisco
> install in any way. The slony replication system for postgres can handle
> replicating only certain tables. I hope that by leaving out log, user_log,
> process, sessions from the replication set (so these tables remain writable)
> netdisco should be kept happy.
> I have slony up and running on a test database and it looks like it can
> handle a heavy load such as when running a macsuck on the network. I will
> update the list with how it goes.
> cheers,
> B
>
>