RE: current 1.3.1 testing

Rob Hagopian <[email protected]>
Newsgroups gmane.network.up2date.current.devel
Message-ID <F4A736AE282FD511BC28009027CC7C590236BD17@gopostal>
>         Right now, shutting the Apache server down is the only way to
> ensure there aren't issues with cadmin and the server running at the
> same time; we're trying to figure out how to best do some sort of
> process locking now.

The methods used in 1.0.5 to detect a running daemon appear to work well,
they don't translate well over to the python module?


>         There's not really a facility for redundant server built into
> Current, and if there ever is going to be, it's a long way down the
> road.  The best thing to do right now is what you mentioned - 
> mirror the
> server hosts, and make sure the databases on both hosts are updated at
> the same time, then use DNS to initiate a manual failover if 
> necessary.

To be truly (automatically) redundant you can use heartbeat and mon to do
failover, they work fairly well, although it'd probably be useful to develop
a mon module to actually check current's status...
								-Rob
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.