[Pacemaker] What is the best way to find out master node?

2009-12-23 Thread hj lee
Hi, I have two-node cluster with a simple multi-state clone. I am using "crm_mon -1 | grep Masters: | awk '{print $3}' " to find out which node is a master. Is there a better way doing this? I don't like relying on the output of crm_mon command, because the output can change in the future. Thanks

Re: [Pacemaker] How pacemaker handle split brain

2009-12-23 Thread hj lee
On Wed, Dec 16, 2009 at 3:53 AM, Andrew Beekhof wrote: > On Wed, Dec 16, 2009 at 2:24 AM, Javen Wu wrote: > > As per the conversation on IRC, DC election has nothing to do with quorum. > But only the DC that also has quorum is able to fence the unseen nodes > and run resources. > > In two-node c

Re: [Pacemaker] Lustre and Multiple Mount Protection

2009-12-23 Thread Bernd Schubert
On Wednesday 23 December 2009, Dejan Muhamedagic wrote: > Hi, > > On Tue, Dec 22, 2009 at 06:52:34PM +0100, Michael Schwartzkopff wrote: > > Hi, > > > > The Lustre Filesystem uses a feature called Multiple Mount Protection to > > make sure that one device is really only mounted by one node. > > >

Re: [Pacemaker] pacemaker and spanning tree in the network between the nodes

2009-12-23 Thread Dejan Muhamedagic
Hi, On Wed, Dec 23, 2009 at 02:20:32PM +0100, Sebastian Reitenbach wrote: > Hi, > > as said, I updated an other cluster, this time a three node cluster, and I > took some time with one XEN resource configured to test a bit with it. > The XEN resource also had the pingd constraint defined. > > T

Re: [Pacemaker] pacemaker and spanning tree in the network between the nodes

2009-12-23 Thread Sebastian Reitenbach
Hi, as said, I updated an other cluster, this time a three node cluster, and I took some time with one XEN resource configured to test a bit with it. The XEN resource also had the pingd constraint defined. There I observed the following things, see below: On Monday 21 December 2009 12:44:17 pm

Re: [Pacemaker] Xen live migrate if destination IP != uname -n

2009-12-23 Thread Martin Gombač
I did that, but it didn't work. At least i fought it didn't, 'cause i used host command "host ibm1.test.net". Host still resolves to external IP honoring what servers from /etc/resolv.conf have to say. But when pinging the ibm1.test.net and after you told me to use hosts again, now i understan

Re: [Pacemaker] Lustre and Multiple Mount Protection

2009-12-23 Thread Dejan Muhamedagic
Hi, On Tue, Dec 22, 2009 at 06:52:34PM +0100, Michael Schwartzkopff wrote: > Hi, > > The Lustre Filesystem uses a feature called Multiple Mount Protection to make > sure that one device is really only mounted by one node. > > My question now: Is this feature really needed in a pacemaker cluster

Re: [Pacemaker] Xen live migrate if destination IP != uname -n

2009-12-23 Thread Lars Ellenberg
On Wed, Dec 23, 2009 at 09:58:25AM +0100, Martin Gombač wrote: > Hi guys, > > i cannot believe no one else has this problem with Xen OCF live > migration script. > I guess i have to solve it myself. Is there a meta parameter for Xen > resources something like: migrate-target? > I'll try that, i

Re: [Pacemaker] Xen live migrate if destination IP != uname -n

2009-12-23 Thread Martin Gombač
Hi guys, i cannot believe no one else has this problem with Xen OCF live migration script. I guess i have to solve it myself. Is there a meta parameter for Xen resources something like: migrate-target? I'll try that, if not i'll just statically set target_node in Xen OCF. Regards, M. Martin