On 12/22/10 04:16, Bart Coninckx wrote:
> All,
>
> I recently jumped from the hb_gui version of SLES10 to the one in SLES11. I
> noticed that the "colocated" and "ordered" properties of a group cannot be
> set
> anymore. Should I assume that the ordering is now determined by the order of
> the
All,
I recently jumped from the hb_gui version of SLES10 to the one in SLES11. I
noticed that the "colocated" and "ordered" properties of a group cannot be set
anymore. Should I assume that the ordering is now determined by the order of
the shown list (and hence the reason of being able to shif
Hi,
I have two nodes rspa and rspa2 (both Centos 5.3 32bits) with the following
packages:
drbd83-8.3.8-1.el5.centos
heartbeat-3.0.3-2.3.el5
pacemaker-1.0.10-1.4.el5
rspa is stopped, and rspa2 has all the resources (IP, FileSystem, Mysql,
Apache and DRBD Master)
When I start heatbeat on rspa, for
On Mon, Dec 20, 2010 at 10:48 PM, Andrew Beekhof wrote:
>
>
> On Mon, Dec 20, 2010 at 10:25 PM, Patrick H. wrote:
>
>> Sent: Sat Nov 13 2010 04:20:56 GMT-0700 (Mountain Standard Time)
>> From: Andrew Beekhof
>> To: The Pacemaker cluster resource manager
>>
>> Subject: Re: [Pacemaker] symmetr
On 21.12.2010 11:08, I wrote:
[...]
like resources getting allocation score
greater then infinity...
native_color: lower allocation score on fo1: 3100
native_color: lower allocation score on fo2: -3
Please ignore this. It was produced by /usr/bin/watch not clearing the
terminal.
(watch -n
Hi there,
I've experimented a bit with pacemaker and as far as I can tell (without
looking
into the source code enough to distinguish a feature from a potential
problem),
the effect of
colocation X-Y : X Y
is (sometimes something) like
"X gets (added) for running together with Y", while Y