Re: [ClusterLabs] Help required for N+1 redundancy setup

Thanks Ken for the detailed response. I suppose I could even use some of the pcs/crm CLI commands then. Cheers. On Wed, Mar 16, 2016 at 8:27 PM, Ken Gaillot wrote: > On 03/16/2016 05:22 AM, Nikhil Utane wrote: > > I see following info gets updated in CIB. Can I use this or

Re: [ClusterLabs] Help required for N+1 redundancy setup

On 03/16/2016 05:22 AM, Nikhil Utane wrote: > I see following info gets updated in CIB. Can I use this or there is better > way? > > crm-debug-origin="peer_update_callback" join="*down*" expected="member"> in_ccm/crmd/join reflect the current state of the node (as known by the partition that

Re: [ClusterLabs] Help required for N+1 redundancy setup

I see following info gets updated in CIB. Can I use this or there is better way? On Wed, Mar 16, 2016 at 12:40 PM, Nikhil Utane wrote: > Hi Ken, > > Sorry about the long delay. This activity was de-focussed but now it's > back on track. > > One part of question

Re: [ClusterLabs] Help required for N+1 redundancy setup

Hi Ken, Sorry about the long delay. This activity was de-focussed but now it's back on track. One part of question that is still not answered is on the newly active node, how to find out which was the node that went down? Anything that gets updated in the status section that can be read and

Re: [ClusterLabs] Help required for N+1 redundancy setup

On 01/08/2016 11:13 AM, Nikhil Utane wrote: >> I think stickiness will do what you want here. Set a stickiness higher >> than the original node's preference, and the resource will want to stay >> where it is. > > Not sure I understand this. Stickiness will ensure that resources don't > move back

Re: [ClusterLabs] Help required for N+1 redundancy setup

Would like to validate my final config. As I mentioned earlier, I will be having (upto) 5 active servers and 1 standby server. The standby server should take up the role of active that went down. Each active has some unique configuration that needs to be preserved. 1) So I will create total 5

Re: [ClusterLabs] Help required for N+1 redundancy setup

On 01/08/2016 06:55 AM, Nikhil Utane wrote: > Would like to validate my final config. > > As I mentioned earlier, I will be having (upto) 5 active servers and 1 > standby server. > The standby server should take up the role of active that went down. Each > active has some unique configuration

[ClusterLabs] Help required for N+1 redundancy setup

Hi Can anybody tell be ,how to configure corosync pacemaker with crmsh for active -active and N+1redundancy setup for kamailio. Thanks Rishin Disclaimer: This

Re: [ClusterLabs] Help required for N+1 redundancy setup

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 wrote: > On 12/22/2015 12:17 AM, Nikhil Utane wrote: > > I have prepared a write-up explaining my

Re: [ClusterLabs] Help required for N+1 redundancy setup

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.

Re: [ClusterLabs] Help required for N+1 redundancy setup

On 12/03/2015 05:23 AM, Nikhil Utane wrote: > Ken, > > One more question, if i have to propagate configuration changes between the > nodes then is cpg (closed process group) the right way? > For e.g. > Active Node1 has config A=1, B=2 > Active Node2 has config A=3, B=4 > Standby Node needs to

Re: [ClusterLabs] Help required for N+1 redundancy setup

On 12/01/2015 05:31 AM, Nikhil Utane wrote: > Hi, > > I am evaluating whether it is feasible to use Pacemaker + Corosync to add > support for clustering/redundancy into our product. Most definitely > Our objectives: > 1) Support N+1 redundancy. i,e. N Active and (up to) 1 Standby. You can do

[ClusterLabs] Help required for N+1 redundancy setup

Hi, I am evaluating whether it is feasible to use Pacemaker + Corosync to add support for clustering/redundancy into our product. Our objectives: 1) Support N+1 redundancy. i,e. N Active and (up to) 1 Standby. 2) Each node has some different configuration parameters. 3) Whenever any active node