[Pacemaker] Active / Active pacemaker configuration advice
Marko Potocnik
marko.potocnik at gmail.com
Thu Nov 25 08:01:45 UTC 2010
I mistyped. Actually I want the service to be controlled by pacemaker, the
service should run on both nodes (hot-standby, I achieved this using
clones), service should be restarted if it fails on any node, IP should move
if service on the same node fails. (and service should be restarted).
On Wed, Nov 24, 2010 at 11:02 PM, Devin Reade <gdr at gno.org> wrote:
> --On Tuesday, November 23, 2010 10:21:04 AM +0100 Marko Potocnik
> <marko.potocnik at gmail.com> wrote:
>
> > I'm using ftp just for test. I want a service to run on both nodes and
> > only IP to move in case a service fails.
> > I don't want to stop / start service if node fails.
>
> You might be able to use the behavior of sshd as a hint on how to
> proceed. In that case, if you have sshd running on both nodes and
> bound to the wildcard address, then you can have the floating IP
> move around under the control of the cluter, but leave sshd starting
> and stopping in the normal fashion (via rc scripts).
>
> To a client, it *looks* like the sshd service moves back and forth
> between the nodes, even though sshd itself is unmanaged.
>
> On the other hand, if sshd binds to a specific IP, this mechanism
> breaks.
>
> (In the particular case of sshd, this only works of course if both
> hosts have the same host key, otherwise the client will get warnings
> about inconsistent server keys.)
>
> Devin
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101125/740137ce/attachment-0002.htm>
More information about the Pacemaker
mailing list