Hi Ken,
On 2/26/20 7:30 AM, Ken Gaillot wrote:
The use case is a large organization with few cluster experts and many
junior system administrators who reboot hosts for OS updates during
planned maintenance windows, without any knowledge of what the host
does. The cluster runs services that have
On February 26, 2020 12:30:24 AM GMT+02:00, Ken Gaillot
wrote:
>Hi all,
>
>We are a couple of months away from starting the release cycle for
>Pacemaker 2.0.4. I'll highlight some new features between now and then.
>
>First we have shutdown locks. This is a narrow use case that I don't
>expect a
Hi all,
We are a couple of months away from starting the release cycle for
Pacemaker 2.0.4. I'll highlight some new features between now and then.
First we have shutdown locks. This is a narrow use case that I don't
expect a lot of interest in, but it helps give pacemaker feature parity
with prop
On 25/02/20 15:59 +0100, Oyvind Albrigtsen wrote:
ClusterLabs is happy to announce fence-agents v1.0.0.
Correction: fence-virt
The source code is available at:
https://github.com/ClusterLabs/fence-virt/releases/tag/v1.0.0
The most significant enhancements in this release are:
- bugfixes and e
ClusterLabs is happy to announce fence-agents v1.0.0.
The source code is available at:
https://github.com/ClusterLabs/fence-virt/releases/tag/v1.0.0
The most significant enhancements in this release are:
- bugfixes and enhancements:
- build: try to detect initscripts directory
- fence_virtd: a
Dear users,
I have facing one strange issue on active active HA configuration. when any
resource failed ,pacemaker is moving to another server and pcs status
showing as per below.
Cluster_eno4 (ocf::heartbeat:IPaddr2): Stopped testsrv1
Cluster_eno1 (ocf::heartbeat:IPaddr2): Stopp
