On Wed, 2018-10-24 at 10:21 +0200, Oyvind Albrigtsen wrote:
> ClusterLabs is happy to announce resource-agents v4.2.0.
> Source code is available at:
> https://github.com/ClusterLabs/resource-agents/releases/tag/v4.2.0
>
[snip]
> - ocf.py: new Python library and dev guide
>
I just wanted to
ClusterLabs is happy to announce resource-agents v4.2.0.
Source code is available at:
https://github.com/ClusterLabs/resource-agents/releases/tag/v4.2.0
The most significant enhancements in this release are:
- new resource agents:
- azure-events
- aliyun-vpc-move-ip
- gcp-pd-move
-
>>> "T. Ladd Omar" schrieb am 23.10.2018 um 15:06 in
>>> Nachricht
:
> Hi all, I send this message to get some answers for my questions about
> Pacemaker.
> 1. In order to cleanup start-failed resources automatically, I add
> failure-timeout attribute for resources, however, the common way to
Hello again,
The original script had been posted on VB's forum and it is at Howtos there.
I subscribed, tried to reach the original author but got no response so far.
For me GPL (eg v2) is ok.
Cheers
John
On 5/10/2018 15:00, users-requ...@clusterlabs.org wrote:
Date: Thu, 04 Oct 2018
Hello Friends,
further thought about this situation:
I want to have a cluster service tgtd, on a "primary/second" DRBD, since
the DRBD is only active on the primary node, so the tgtd won't success
on the secondary node.
So should i, or how do config a primary/seconday tgtd service?
Or, which
Hello Dear Andrei Borzenkov,
Thank you very much for your answer. I've check the logs all the time,
but there are nothing helpful , just a bunch of heartbeat messages.
Anyway, i've read the book "Packt - CentOS High Availability" published
in 2015, and got some new ideas, and tried out, the
On 10/24/2018 08:17 AM, Leon Steffens wrote:
> Hi all,
>
> We are trying to set up resource alerts on our Pacemaker 1.1.18
> cluster. When a specific resource gets stopped, we want to trigger an
> alert on a *different* node to the node the resource is running on.
>
> But, it looks like resource
Hi all,
We are trying to set up resource alerts on our Pacemaker 1.1.18 cluster.
When a specific resource gets stopped, we want to trigger an alert on a
*different* node to the node the resource is running on.
But, it looks like resource alerts are only sent to the node the resource
is being
