Hello all,
I've been meaning to address the implementation of "reload" in Pacemaker
for a while now, and I think the next release will be a good time, as it
seems to be coming up more frequently.
In the current implementation, Pacemaker considers a resource parameter
"reloadable" if the resource
I am pleased to announce the latest release of Corosync
2.4.0 available immediately from our website at
http://build.clusterlabs.org/corosync/releases/.
This release is mostly about long awaited QDevice feature and few rather
small fixes.
Qdevice is complete rewrite of old cman qdisk using
On 06/30/2016 09:18 AM, Jan Friesse wrote:
> Hi Li,
>
>> Hi all,
>> I compiled latest version of corosync and found its init script
>> is not LSB compliance. When I check stopped corosync service status
>> with cmd "service corosync status" (on centos 6 without systemd), it
>> returns "1"
On Thu, Jun 30, 2016 at 01:27:25PM +0200, Tomas Jelinek wrote:
> It seems eventmachine can be safely dropped as all tests passed without it.
Great, thanks for confirming.
--
Valentin
___
Users mailing list: Users@clusterlabs.org
On 06/30/2016 11:16 AM, Bogdan Dobrelya wrote:
> Hello.
> I'm building the libqb -> corosync -> pacemaker and commit each as a
> separate docker container layer. Then I run the latter and spawn a
> corosync with a simple config, then a pacemaker instance.
>
> The issue is, that when I just run
Hello.
I'm building the libqb -> corosync -> pacemaker and commit each as a
separate docker container layer. Then I run the latter and spawn a
corosync with a simple config, then a pacemaker instance.
The issue is, that when I just run processes, the pacemaker complains
it has an ipc issues
