Thanks for the reply. Yes, it's a bit confusing. I did end up using the
documentation for Corosync 2.X since that seemed newer, but it also assumed
CentOS/RHEL7 and systemd-based commands. It also incorporates cman, pcsd,
psmisc, and policycoreutils-pythonwhich, which are all new to me. If ther
Thanks for the reply. Yes, it's a bit confusing. I did end up using the
documentation for Corosync 2.X since that seemed newer, but it also assumed
CentOS/RHEL7 and systemd-based commands. It also incorporates cman, pcsd,
psmisc, and policycoreutils-pythonwhich, which are all new to me. If there
On Tue, 2017-08-22 at 19:40 +, Eric Robinson wrote:
> The documentation located here…
>
>
>
> http://clusterlabs.org/doc/
>
>
>
> …is confusing because it offers two combinations:
>
>
>
> Pacemaker 1.0 for Corosync 1.x
>
> Pacemaker 1.1 for Corosync 2.x
>
>
>
> According to th
The documentation located here...
http://clusterlabs.org/doc/
...is confusing because it offers two combinations:
Pacemaker 1.0 for Corosync 1.x
Pacemaker 1.1 for Corosync 2.x
According to the documentation, if you use Corosync 1.x you need Pacemaker 1.0,
but if you use Corosync 2.x then you n
Hello Philipp,
[first of all, I've noticed you are practising a pretty bad habit of
starting a new topic/thread by simply responding to an existing one,
hence distorting the clear thread overview of the exchanges going
on for some of us ... please stop that, there's nothing to be afraid
of going f
On 08/08/17 09:42 -0500, Ken Gaillot wrote:
> On Tue, 2017-08-08 at 10:18 +0200, Ulrich Windl wrote:
> Ken Gaillot schrieb am 07.08.2017 um 22:26 in
> Nachricht
>> <1502137587.5788.83.ca...@redhat.com>:
>>
>> [...]
>>> Unmanaging doesn't stop monitoring a resource, it only prevents start
