Re: [Pacemaker] Making Virtual Domain utilization dynamic

2013-05-01 Thread Michael Schwartzkopff
Am Freitag, 26. April 2013, 22:14:59 schrieb Michael Schwartzkopff: > Hi, > > I picked up my old idea to make resouce utilizations dymanic and wrote the > little patch for VirtualDomain to check CPU utilization every time the > VirtualDomain is monitored: > > --- /usr/lib/ocf/resource.d/heartbeat

Re: [Pacemaker] Two node KVM cluster

2013-05-01 Thread Oriol Mula-Valls
On 01/05/13 06:12, Andrew Beekhof wrote: On 28/04/2013, at 9:19 PM, Oriol Mula-Valls wrote: Hi, I have modified the previous configuration to use sbd fencing. I have also fixed several other issues with the configuration and now when the node reboots seems not to be able to rejoin the clus

Re: [Pacemaker] Clone Resources Individual Configuration per Node

2013-05-01 Thread Andrew Beekhof
On 10/04/2013, at 8:03 AM, Andrew Beekhof wrote: > > On 10/04/2013, at 4:33 AM, Felix Zachlod wrote: > >>> It seems no rule has been selected here and it has fallen back to the >> default. >>> It looks similar on the other node- but some times it seems that the >> script is >>> being called w

Re: [Pacemaker] Pacemaker core dumps

2013-05-01 Thread Andrew Beekhof
On 01/05/2013, at 11:36 PM, Xavier Lashmar wrote: > I'm not sure if anyone has run into this issue but I can't seem to find a > debuginfo package for one of the libraries for CentOS 6.3 with Kernel > 2.6.32-279.9.1el6.x86_64 : libtool-ltdl > > Here's what I get so far from the core dump, but

Re: [Pacemaker] Pacemaker/Corosync on Ubuntu 12.04

2013-05-01 Thread Andrew Beekhof
On 02/05/2013, at 8:21 AM, Andrew Martin wrote: > - Original Message - >> From: "Robert Parsons" >> To: "The Pacemaker cluster resource manager" >> Sent: Wednesday, May 1, 2013 4:03:46 PM >> Subject: [Pacemaker] Pacemaker/Corosync on Ubuntu 12.04 >> >> >> >> We're wanting to build a

Re: [Pacemaker] corosync restarts service when slave node joins the cluster

2013-05-01 Thread Andrew Beekhof
On 01/05/2013, at 11:55 PM, Babu Challa wrote: > Hi Andrew, > > Thanks for the replay. Now I have managed to reproduce the issue. I am > enclosing details here for pacemaker team for their understanding . > Requesting their advice for resolving this issue Update your software. > > Hello P

Re: [Pacemaker] Pacemaker/Corosync on Ubuntu 12.04

2013-05-01 Thread Andrew Martin
- Original Message - > From: "Robert Parsons" > To: "The Pacemaker cluster resource manager" > Sent: Wednesday, May 1, 2013 4:03:46 PM > Subject: [Pacemaker] Pacemaker/Corosync on Ubuntu 12.04 > > > > We're wanting to build a web server farm with approx 18 nodes. We're > aware of scala

[Pacemaker] Pacemaker/Corosync on Ubuntu 12.04

2013-05-01 Thread Robert Parsons
We're wanting to build a web server farm with approx 18 nodes. We're aware of scalability issues with Corosync/Pacemaker but we're also told that it is getting better with newer versions of the software. Ubuntu 12.04 is packaged with corosync 1.4.2 and pacemaker 1.1.6. I imagine that we'll

Re: [Pacemaker] Pcmk migration logic and Libvirt migration behavior

2013-05-01 Thread David Vossel
- Original Message - > From: "Andreas Hofmeister" > To: pacemaker@oss.clusterlabs.org > Sent: Wednesday, May 1, 2013 8:14:20 AM > Subject: [Pacemaker] Pcmk migration logic and Libvirt migration behavior > > Dear All, > > we currently investigate a problem where some Libvirt/KVM VM in a

Re: [Pacemaker] Pacemaker core dumps

2013-05-01 Thread Xavier Lashmar
I'm not sure if anyone has run into this issue but I can't seem to find a debuginfo package for one of the libraries for CentOS 6.3 with Kernel 2.6.32-279.9.1el6.x86_64 : libtool-ltdl Here's what I get so far from the core dump, but I think it's incomplete: ... ... ... Reading symbols from /lib

[Pacemaker] Pcmk migration logic and Libvirt migration behavior

2013-05-01 Thread Andreas Hofmeister
Dear All, we currently investigate a problem where some Libvirt/KVM VM in a pacemaker cluster ends up running on two nodes after being migrated. The problem is triggered when a constraint is inserted that causes the VM to be migrated away from its current node, but then the constraint is rem