This is really question for pacemaker list, so CCing. Regards, Honza > Hi, > > I would like Corosync to manage Radius in an active/active > configuration but I don't know how I should add this, so was wondering > if somebody could point me in the right direction. > > Thanks and kind regards, > Soph. > > -- Details -- > > So far I have this, > # crm configure show > node centos6-radius0-kawazu > node centos6-radius1-yetti > primitive failover-ip ocf:heartbeat:IPaddr \ > params ip="192.168.10.200" \ > op monitor interval="2s" > property $id="cib-bootstrap-options" \ > dc-version="1.1.10-14.el6_5.2-368c726" \ > cluster-infrastructure="classic openais (with plugin)" \ > expected-quorum-votes="2" \ > stonith-enabled="false" \ > no-quorum-policy="ignore" > > And wondered if I should add this: > # crm configure primitive RADIUS lsb:radiusd op monitor interval="5s" > timeout="20s" start-delay="0s" > If I could add ocf:heartbeat then may be better, but I read this mayn't > work when raddb forked. ( Reference : > http://oss.clusterlabs.org/pipermail/pacemaker/2012-April/013790.html ) > > If not then how should I configure this? > > My O/S is CentOS 6. > > -- End -- > _______________________________________________ > discuss mailing list > discuss@xxxxxxxxxxxx > http://lists.corosync.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss