Dde, nicely done! Looking forward to playing with this when I get back.
digimer
On 2018-04-30 07:16 PM, Ken Gaillot wrote:
Source code for the third release candidate for Pacemaker version
2.0.0 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.0-r
Some of this has been mentioned before, but to collect it all in one
location, here is information of particular interest to distribution
packagers and users who build Pacemaker themselves:
* Should you stay on the 1.1 series or move to 2.0? See the following
list of factors to consider,
Source code for the third release candidate for Pacemaker version
2.0.0 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.0-r
c3
The main feature of this release is renaming all the Pacemaker daemons
to help make the documentation and logs easier to follow:
Hi!
Thanks for the prompt response.
Due to the RedHat version, I can't use shared storage. I'm using
timer-based watchdog with stonith-watchdog-timeout set to 5 seconds.
On Sun, 29 Apr 2018 at 05:37, Digimer wrote:
> Ah, ok, now I get it.
>
> So node 2 should wait until
I am pleased to announce the second testing (Alpha 3) release of
Corosync 3.0 (codename Camelback) available immediately from our website at
http://build.clusterlabs.org/corosync/releases/ as corosync-2.99.2.
You can also download RPMs for various distributions from CI
On 04/30/2018 08:51 AM, Christine Caulfield wrote:
> On 29/04/18 13:22, Andrei Borzenkov wrote:
>> 29.04.2018 04:19, Wei Shan пишет:
>>> Hi,
>>>
>>> I'm using Redhat Cluster Suite 7with watchdog timer based fence agent. I
>>> understand this is a really bad setup but this is what the end-user
On 29/04/18 13:22, Andrei Borzenkov wrote:
> 29.04.2018 04:19, Wei Shan пишет:
>> Hi,
>>
>> I'm using Redhat Cluster Suite 7with watchdog timer based fence agent. I
>> understand this is a really bad setup but this is what the end-user wants.
>>
>> ATB => auto_tie_breaker
>>
>> "When the