[Pacemaker] IP fail over without controlling the services

[David Vossel]

----- Original Message -----
> From: "Dongdong Zhou" <dongdong.zhou at meshdigital.com>
> To: Pacemaker at oss.clusterlabs.org
> Sent: Thursday, July 26, 2012 4:41:36 AM
> Subject: [Pacemaker] IP fail over without controlling the services
> 
> Hi,
> 
> I'm trying to set up IP auto fail over on a two-way master-slave
> MySQL
> replication cluster. What I'm trying to achieve is to only fail over
> the
> IP when there's a problem on the mysqld service. I don't want
> pacemaker
> to control the mysqld service.

Make the mysql resource an un-managed resource... meaning pacemaker won't stop/start it, but it will monitor to see if it is alive or not.  If it fails, your constraints for the IP should work like you expect.

look at the is-managed option at this link.
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-options.html

-- Vossel

> 
> With my current configuration, pacemaker will always keep the service
> running on the active node and the service stopped on the passive
> node.
> 
> Any help would be much appreciated.
> 
> primitive VIP ocf:heartbeat:IPaddr2 \
> 	params ip="109.68.38.75" cidr_netmask="24" \
> 	op monitor interval="30"
> primitive mysqld lsb:mysqld \
> 	op monitor interval="10" timeout="30"
> group mysql mysqld VIP
> property $id="cib-bootstrap-options" \
> 	dc-version="1.1.7-6.el6-148fccfd5985c5590cc601123c6c16e966b85d14" \
> 	cluster-infrastructure="openais" \
> 	expected-quorum-votes="2" \
> 	stonith-enabled="false" \
> 	no-quorum-policy="ignore" \
> 	last-lrm-refresh="1343214667"
> rsc_defaults $id="rsc-options" \
> 	resource-stickiness="100"
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>