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
bqb -> corosync -> pacemaker, then launch
But that'd be a really ugly band aiding and is a very long to start as well.
Note, the libqb/corosync builds are from a signed tarballs, the
pacemaker - from its github tag checked-out as I want to "play" with a
latest builds from trunc.
--
On 06/27/2016 09:28 AM, Bogdan Dobrelya wrote:
> Hello.
> I use this guide [0] to build libqb, corosync, pacemaker
> and test them as pid-space linked docker containers [1].
>
> A Pacemaker builds OK and shows the v1.1.15 runtime, a build-time it
> complains about an unknow
Although it builds, runtime it throws the exit code 17 on me, which I
failed to google / understand from sources. Any help with that, folks?
Thank you!
[0] http://clusterlabs.org/wiki/SourceInstall
[1]
https://github.com/docker/docker/blob/master/docs/reference/run.md#pid-settings---pid
--
t; Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
--
Best regards,
Bogdan Dobrelya,
Irc #bogdando
___
Users mailing list: Users@clusterlabs.or
On 04/26/2016 10:49 AM, Robert Dahlem wrote:
> On 26.04.2016 10:33, Bogdan Dobrelya wrote:
>
>> Is it possible to run several instances of a Corosync/Pacemaker clusters
>> on a node? Can a node be a member of several clusters, so they could put
>> resources the
is.
The former must use STONITH (or a stop policy, if it's only a VIP), as
they don't know how to deal with split-brain, for example.
--
Best regards,
Bogdan Dobrelya,
Irc #bogdando
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org
On 04.02.2016 15:43, Bogdan Dobrelya wrote:
> Hello.
> Regarding the original issue, good news are the resource-agents
> ocf-shellfuncs is no more causing fork bombs to the dummy OCF RA [0]
> after the fix [1] done. The bad news are that "self-forking" monitors
&
-ha.ocf
[3]
https://git.openstack.org/cgit/openstack/fuel-library/tree/files/fuel-ha-utils/ocf/ns_vrouter
On 04.01.2016 17:33, Bogdan Dobrelya wrote:
> On 04.01.2016 17:14, Dejan Muhamedagic wrote:
>> Hi,
>>
>> On Mon, Jan 04, 2016 at 04:52:43PM +0100, Bogdan Dobrelya wrote:
>&
ers@clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
--
Best regards,
Bogdan Dobrelya,
Irc #b
.html
>
> ___
> Users mailing list: Users@clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluste
On 04.01.2016 16:36, Ken Gaillot wrote:
> On 01/04/2016 09:25 AM, Bogdan Dobrelya wrote:
>> On 04.01.2016 15:50, Bogdan Dobrelya wrote:
>>> So far so bad.
>>> I made a dummy OCF script [0] to simulate an example
>>> promote/demote/notify failure mode f
On 04.01.2016 15:50, Bogdan Dobrelya wrote:
> So far so bad.
> I made a dummy OCF script [0] to simulate an example
> promote/demote/notify failure mode for a multistate clone resource which
> is very similar to the one I reported originally. And the test to
> reproduce my case
13 matches
Mail list logo
