Daniel Dehennin writes:
> Hello,
>
[...]
> I only manage to have my VM as corosync member like others when default
> the route is on the same interface as my multicast traffic.
Here are some corosync informations:
On one working host:
root@nebula3:~# corosync-quorumtool
Quorum inform
Hello,
I'm trying to setup a pacemaker/corosync on Ubuntu Trusty to access a
SAN to use with OpenNebula[1]:
- pacemaker .1.10+git20130802-1ubuntu2.1
- corosync 2.3.3-1ubuntu1
I have a dedicated VLAN for cluster communications.
Each bare metal node have a dedicated interface eth0 on that VLAN, 3
