On 10/04/2013, at 7:30 PM, Rus Hughes wrote:
> Hi,
>
> I hope I've got the right list, I'm still a little confused about where CMAN
> ends and Pacemaker begins!
Think of CMAN as some extra APIs for corosync.
Anything you would configure in Pacemaker when using corosync is still
configured th
as an update
node vfontopensips1
node vfontopensips2
primitive ClusterIPPres ocf:heartbeat:IPaddr2 \
params ip="10.30.0.176" cidr_netmask="32" \
op monitor interval="5s"
primitive osp ocf:netdev:osp \
params interval="1s" \
op monitor interval="5s" \
meta allow-migrate="true" i
Hi,
I hope I've got the right list, I'm still a little confused about where
CMAN ends and Pacemaker begins! We're using Pacemaker and CMAN on Oracle
6.3 to try and create an active/standby failover pair, but seem to have
some annoying conditions that are making this tricky.
We hae 2 nodes, vfonto
