[ClusterLabs] Help required for N+1 redundancy setup

[Nikhil Utane]

Thanks to you Ken for giving all the pointers.
Yes, I can use service start/stop which should be a lot simpler. Thanks
again. :)

On Tue, Dec 22, 2015 at 9:29 PM, Ken Gaillot <kgaillot at redhat.com> wrote:

> On 12/22/2015 12:17 AM, Nikhil Utane wrote:
> > I have prepared a write-up explaining my requirements and current
> solution
> > that I am proposing based on my understanding so far.
> > Kindly let me know if what I am proposing is good or there is a better
> way
> > to achieve the same.
> >
> >
> https://drive.google.com/file/d/0B0zPvL-Tp-JSTEJpcUFTanhsNzQ/view?usp=sharing
> >
> > Let me know if you face any issue in accessing the above link. Thanks.
>
> This looks great. Very well thought-out.
>
> One comment:
>
> "8. In the event of any failover, the standby node will get notified
> through an event and it will execute a script that will read the
> configuration specific to the node that went down (again using
> crm_attribute) and become active."
>
> It may not be necessary to use the notifications for this. Pacemaker
> will call your resource agent with the "start" action on the standby
> node, after ensuring it is stopped on the previous node. Hopefully the
> resource agent's start action has (or can have, with configuration
> options) all the information you need.
>
> If you do end up needing notifications, be aware that the feature will
> be disabled by default in the 1.1.14 release, because changes in syntax
> are expected in further development. You can define a compile-time
> constant to enable them.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20151222/082dde31/attachment.htm>