Re: [Pacemaker] Node recover causes resource to migrate

2013-07-30 Thread Andrew Beekhof
On 25/07/2013, at 9:22 PM, Jacobo García wrote: > Hello, > > As suggested I'm trying to add the nodes via corosync-objctl. > > My current config file is this one: > https://gist.github.com/therobot/4327cd0a2598d1d6bb93 using 5001 as the > nodeid on the second node. > > Then I try to add th

Re: [Pacemaker] Node recover causes resource to migrate

2013-07-25 Thread Jacobo García
Hello, As suggested I'm trying to add the nodes via corosync-objctl. My current config file is this one: https://gist.github.com/therobot/4327cd0a2598d1d6bb93 using 5001 as the nodeid on the second node. Then I try to add the nodes with the following commands: corosync-objctl -n totem.interface

Re: [Pacemaker] Node recover causes resource to migrate

2013-07-24 Thread Andrew Beekhof
On 24/07/2013, at 10:09 PM, Lars Marowsky-Bree wrote: > On 2013-07-24T21:40:40, Andrew Beekhof wrote: > >>> Statically assigned nodeids? >> Wouldn't hurt, but you still need to bring down the still-active node to get >> it to talk to the new node. >> Which sucks > > Hm. But ... corosync/pac

Re: [Pacemaker] Node recover causes resource to migrate

2013-07-24 Thread Lars Marowsky-Bree
On 2013-07-24T21:40:40, Andrew Beekhof wrote: > > Statically assigned nodeids? > Wouldn't hurt, but you still need to bring down the still-active node to get > it to talk to the new node. > Which sucks Hm. But ... corosync/pacemaker ought to identify the node via the nodeid. If it comes back w

Re: [Pacemaker] Node recover causes resource to migrate

2013-07-24 Thread Andrew Beekhof
On 24/07/2013, at 7:26 PM, Lars Marowsky-Bree wrote: > On 2013-07-24T09:00:23, Andrew Beekhof wrote: > >>> 4. Node A is back with a different internal ip address. >> >> This is your basic problem. >> >> I don't believe there is any cluster software that is designed to support >> this sort o

Re: [Pacemaker] Node recover causes resource to migrate

2013-07-24 Thread Jacobo García
Thanks for your answers. Is it possible to configure corosync/pacemaker in this scenario so if a node goes down instead of bringing the node back I can build a new one and add it to the cluster? Building new nodes is almost "free" for me. Also, what's the difference between bringing a new node fro

Re: [Pacemaker] Node recover causes resource to migrate

2013-07-24 Thread Lars Marowsky-Bree
On 2013-07-24T09:00:23, Andrew Beekhof wrote: > > 4. Node A is back with a different internal ip address. > > This is your basic problem. > > I don't believe there is any cluster software that is designed to support > this sort of scenario. > Even at the corosync level, it has no knowledge tha

Re: [Pacemaker] Node recover causes resource to migrate

2013-07-23 Thread Andrew Beekhof
On 23/07/2013, at 2:20 AM, Jacobo García wrote: > Hello, > > I'm trying the debug the following scenario: > > My cluster setup is two AWS instances providing an elastic ip as an HA > resource. I have written a custom resource script for managing that, the > script passes all the tests specif

[Pacemaker] Node recover causes resource to migrate

2013-07-22 Thread Jacobo García
Hello, I'm trying the debug the following scenario: My cluster setup is two AWS instances providing an elastic ip as an HA resource. I have written a custom resource script for managing that, the script passes all the tests specified in ocf-tester. It behaves properly in other test scenarios. In