Re: [Linux-ha-dev] [Pacemaker] migration fix for ocf:heartbeat:Xen

2011-09-23 Thread Dejan Muhamedagic
Hi, On Thu, Aug 11, 2011 at 09:07:00PM +, Daugherity, Andrew W wrote: I have discovered that sometimes when migrating a VM, the migration itself will succeed, but the migrate_from call on the target node will fail, as apparently the status hasn't settled down yet. This is more likely to

[Linux-ha-dev] slapd ocf resource agent

2011-09-23 Thread John Keith Hohm
Many thanks to Jeroen and Tomo for starting this. I have taken their versions, incorporated the recommendations from Dejan's review, made a few improvements of my own, and committed to a fork on GitHub: https://github.com/jhohm/resource-agents I'm not sure of your workflow, can I just make a

Re: [Linux-HA] ERROR: glib: Message too long

2011-09-23 Thread Claus Wimmer
Thanks a lot. Somehow I missed this thread. Sounds promising. I'll check it out. Best regards Claus -Ursprüngliche Nachricht- Von: Alexander Bodnarashik boda2...@gmail.com Gesendet: Sep 22, 2011 8:55:32 PM An: General Linux-HA mailing list linux-ha@lists.linux-ha.org Betreff: Re:

Re: [Linux-HA] Problem with creating constraints

2011-09-23 Thread Lars Ellenberg
On Fri, Sep 23, 2011 at 12:39:13PM +1000, Andrew Beekhof wrote: On Wed, Sep 21, 2011 at 7:15 PM, Uwe Weiss u.we...@netz-objekte.de wrote: Hello List, I have a problem in creating a constraint. I hope that someone could help me and give me a hint. I have three resources (A,B,C)

[Linux-HA] Start resource depending on resource(s) outside Pacemakers scope

2011-09-23 Thread Uwe Weiss
Hello list, I would like to start a Resource depending on a mount point which is not handled by pacemaker. I have some resources handled by pacemaker. This resources are stored on Primary/Primary drbd drive. Due to some other resources (outside pacemaker) on this drive I have to start drbd and

[Linux-HA] ldirector - jboss port

2011-09-23 Thread mike
Last year I set up an HA cluster with ldirector pointing to 2 load balanced real servers. We had jboss on the backend listening to the Real IP on port 8080. Initially, we could not get the backend to reply - we kept getting refused connections when we tried going through the VIP. Thanks to