Re: [ClusterLabs] STONITH not communicated back to initiator until token expires

2017-04-26 Thread Chris Walker
Just to close the loop on this issue, discussions with Redhat have confirmed that this behavior is as designed, that all membership changes must first be realized by the Corosync layer. So the full trajectory of a STONITH action in response to, for example, a failed stop operation looks like:

[ClusterLabs] IPaddr2 cloning inside containers

2017-04-26 Thread Ken Gaillot
FYI, I stumbled across a report of a suspected kernel issue breaking iptables clusterip inside containers: https://github.com/lxc/lxd/issues/2773 ocf:heartbeat:IPaddr2 uses clusterip when cloned. I'm guessing no one's tried something like that yet, but this is a note of caution to anyone

Re: [ClusterLabs] Problem with clone ClusterIP

2017-04-26 Thread Ken Gaillot
On 04/26/2017 02:45 AM, Bratislav Petkovic wrote: > Tahank you, > > > > We use the Cisco Nexus 7000 switches, they support Multicast MAC. > > It is possible that something is not configured correctly. > > In this environment working IBM PowerHA SystemMirror 7.1 (use Multicast) > without

[ClusterLabs] Antw: Re: Problem with clone ClusterIP

2017-04-26 Thread Ulrich Windl
>>> Ken Gaillot schrieb am 25.04.2017 um 17:38 in >>> Nachricht : > On 04/25/2017 09:32 AM, Bratislav Petkovic wrote: >> I want to make active/active cluster with two physical servers. >> >> On the servers are installed: