On 30/03/16 17:09 +0200, Roberto Munoz Gomez wrote:
> I am trying to migrate the bindnetaddr option from corosync.conf to
> cluster.conf but couldn't make it work. I want to use this interface for
> corosync traffic.
>
> inet addr:10.76.125.236 Bcast:10.76.125.239 Mask:255.255.255.240
Looking
I started reading "Pacemaker explained" but as it's so depth I didn't
read that section regarding rules yet. I'll take a look at it and test
it before asking anything again.
Thanks a lot Ken
On Mon, Apr 4, 2016 at 9:26 AM, Ken Gaillot wrote:
> On 04/02/2016 01:16 AM, Jason
On 01/04/16 13:59 +0100, Christine Caulfield wrote:
> I am very pleased to announce the 1.0 release of libqb
>
> [...]
>
> The current release tarball is here:
> https://github.com/ClusterLabs/libqb/releases/download/v1.0/libqb-1.0.tar.gz
One should preferably start at
On 04/02/2016 01:16 AM, Jason Voorhees wrote:
> Hello guys:
>
> I've been recently reading "Pacemaker - Clusters from scratch" and
> working on a CentOS 7 system with pacemaker 1.1.13, corosync-2.3.4 and
> drbd84-utils-8.9.5.
>
> The PDF instructs how to create a DRBD resource that seems to be
>
"Ulrich Windl" writes:
> Actually form my SLES11 SP[1-4] experience, the cluster always
> distributes resources across all available nodes, and only if don't
> want that, I'll have to add constraints. I wonder why that does not
> seem to work for you.
Because
This is true for opt-out clusters. Opt-in cluster only rely on location
constraints.
Regards
Le 4 avr. 2016 08:46, "Ulrich Windl" a
écrit :
> Hi!
>
> Actually form my SLES11 SP[1-4] experience, the cluster always distributes
> resources across all available
Hi!
Actually form my SLES11 SP[1-4] experience, the cluster always distributes
resources across all available nodes, and only if don't want that, I'll have to
add constraints. I wonder why that does not seem to work for you.
Regards,
Ulrich
>>> Ferenc Wágner schrieb am