On 11/09/2012 08:49 AM, Cserbák Márton wrote:
> Hi,
>
> I have successfully set up a DRBD+Pacemaker+Xen cluster on two Debian
> servers. Unfortunately, I am facing the same issue as the one
> described in https://bugzilla.redhat.com/show_bug.cgi?id=694492,
> namely, that the CPU features differ on
- Original Message -
> From: "Cal Heldenbrand"
> To: "The Pacemaker cluster resource manager"
> Sent: Friday, November 9, 2012 4:29:05 PM
> Subject: [Pacemaker] Custom event script during master/slave failover?
>
>
> Hi everyone,
>
> I'm playing around with the possibility of using P
On 11/09/2012 04:26 PM, Andrew Beekhof wrote:
> On Fri, Nov 9, 2012 at 4:43 PM, Matthew O'Connor wrote:
>> On 11/08/2012 08:15 PM, Andrew Beekhof wrote:
>>> You're not starting it as a pacemaker resource are you?
>>> CMAN should be doing that as part of the init script (which explains
>>> why its
Hi everyone,
I'm playing around with the possibility of using Pacemaker in a Redis
master/slave cluster. The difficult part of this, is that Redis will not
automatically flip itself from read-only slave mode into master mode. A
client needs to connect to the slave server and run this SLAVEOF NO
- Original Message -
> From: "Andrew Beekhof"
> To: "The Pacemaker cluster resource manager"
> Sent: Friday, November 9, 2012 3:36:10 PM
> Subject: Re: [Pacemaker] Enable remote monitoring
>
> On Sat, Nov 10, 2012 at 6:35 AM, David Vossel
> wrote:
> > - Original Message -
> >>
On Fri, Nov 9, 2012 at 10:25 PM, Lars Marowsky-Bree wrote:
> On 2012-11-09T11:04:15, Andrew Beekhof wrote:
>
>> So I was just explaining the problem and context to David... his
>> comment was "aren't these just unmanaged resources and some
>> constraints?".
>
> They can even be managed - the star
On Sat, Nov 10, 2012 at 6:35 AM, David Vossel wrote:
> - Original Message -
>> From: "Lars Marowsky-Bree"
>> To: "The Pacemaker cluster resource manager"
>> Sent: Friday, November 9, 2012 11:54:16 AM
>> Subject: Re: [Pacemaker] Enable remote monitoring
>>
>> On 2012-11-09T11:46:59, David
On Sat, Nov 10, 2012 at 4:54 AM, Lars Marowsky-Bree wrote:
> On 2012-11-09T11:46:59, David Vossel wrote:
>
>> What if we made something similar to the concept of an "un-managed"
>> resource, in that it is only ever monitored, but treated it like a normal
>> resource. Meaning start/stop could s
On Fri, Nov 9, 2012 at 4:43 PM, Matthew O'Connor wrote:
>
> On 11/08/2012 08:15 PM, Andrew Beekhof wrote:
>> You're not starting it as a pacemaker resource are you?
>> CMAN should be doing that as part of the init script (which explains
>> why its still there until after pacemaker is gone).
> I th
- Original Message -
> From: "Lars Marowsky-Bree"
> To: "The Pacemaker cluster resource manager"
> Sent: Friday, November 9, 2012 11:54:16 AM
> Subject: Re: [Pacemaker] Enable remote monitoring
>
> On 2012-11-09T11:46:59, David Vossel wrote:
>
> > What if we made something similar to t
On 2012-11-09T11:46:59, David Vossel wrote:
> What if we made something similar to the concept of an "un-managed" resource,
> in that it is only ever monitored, but treated it like a normal resource.
> Meaning start/stop could still execute, but start is really just the first
> "monitor" oper
- Original Message -
> From: "Lars Marowsky-Bree"
> To: "The Pacemaker cluster resource manager"
> Sent: Friday, November 9, 2012 5:25:41 AM
> Subject: Re: [Pacemaker] Enable remote monitoring
>
> On 2012-11-09T11:04:15, Andrew Beekhof wrote:
>
> > So I was just explaining the proble
On 2012-11-09T14:06:29, Dejan Muhamedagic wrote:
> > > > Uh? How should this be handled by the RA? Can you elaborate?
> > > For instance, using expect to wait for the login prompt on the
> > > console. Or, if that's possible, employing libvirt to get the
> > > current runlevel. We already discuss
Hi,
On Fri, Nov 09, 2012 at 06:09:18PM +0700, Soni Maula Harriz wrote:
> dear forum,
>
> i use centos 6.3 and configure 2 server with pacemaker and corosync
> (installation via yum)
>
> [root@daksa02 ~]# pacemakerd --version
> Pacemaker 1.1.7-6.el6
> Written by Andrew Beekhof
>
> [root@daksa02
On Fri, Nov 09, 2012 at 12:16:15PM +0100, Lars Marowsky-Bree wrote:
> On 2012-11-08T13:22:34, Dejan Muhamedagic wrote:
>
> > > Uh? How should this be handled by the RA? Can you elaborate?
> > For instance, using expect to wait for the login prompt on the
> > console. Or, if that's possible, emplo
On 2012-11-09T11:04:15, Andrew Beekhof wrote:
> So I was just explaining the problem and context to David... his
> comment was "aren't these just unmanaged resources and some
> constraints?".
They can even be managed - the start would be a "while ! monitor ; sleep
1 ; done" fake, and similar for
On 2012-11-08T13:22:34, Dejan Muhamedagic wrote:
> > Uh? How should this be handled by the RA? Can you elaborate?
> For instance, using expect to wait for the login prompt on the
> console. Or, if that's possible, employing libvirt to get the
> current runlevel. We already discussed this. Your ob
dear forum,
i use centos 6.3 and configure 2 server with pacemaker and corosync
(installation via yum)
[root@daksa02 ~]# pacemakerd --version
Pacemaker 1.1.7-6.el6
Written by Andrew Beekhof
[root@daksa02 ~]# corosync -v
Corosync Cluster Engine, version '1.4.1'
Copyright (c) 2006-2009 Red Hat, In
18 matches
Mail list logo
