[Pacemaker] IP Range Failover with IPaddr2 and clone / globally-unique="true"

Reid, Mike MBReid at thepei.com
Mon Jan 16 14:48:31 EST 2012

Greetings! I am wondering if anyone here might be familiar with managing IP ranges in Pacemaker? (e.g. via ocf:heartbeat:IPaddr2 and clone / globally-unique="true"...I am using Pacemaker v1.0.9)

The reason I ask is because I'm only seeing the first IP address get created and am wondering if perhaps I'm missing something obvious to get the other IPs to show up?

Here's my CIB (It's for a redundant Active/Passive web server):

node MACHINE1 \
        attributes standby="off"
node MACHINE2 \
        attributes standby="off"
primitive resAPACHE ocf:heartbeat:apache \
        params configfile="/usr/local/apache/conf/httpd.conf" \
        op monitor interval="1min" \
        op start interval="0" timeout="40" \
        op stop interval="0" timeout="60"
primitive resDRBD ocf:linbit:drbd \
        params drbd_resource="repdata" \
        op monitor interval="15s"
primitive resFS ocf:heartbeat:Filesystem \
        params device="/dev/drbd/by-res/repdata" directory="/data" fstype="ext4" \
        op monitor interval="120s"
primitive resIP-1 ocf:heartbeat:IPaddr2 \
        params ip="111.22.333.4" nic="eth0"
primitive resIP-2 ocf:heartbeat:IPaddr2 \
        params ip="111.22.333.5" nic="eth0"
primitive resPHP ocf:heartbeat:anything \
        params binfile="/usr/local/sbin/php-fpm" cmdline_options="--fpm-config /usr/local/etc/php-fpm.conf" pidfile="/var/run/php-fpm.pid" \
        op start interval="0" timeout="20" \
        op stop interval="0" timeout="30" \
        op monitor interval="20" \
        meta target-role="Started"
primitive resPROXY ocf:heartbeat:nginx \
        params conffile="/etc/nginx/nginx.conf" \
        op monitor interval="60s" \
        op start interval="0" timeout="40"
primitive resWEBIP ocf:heartbeat:IPaddr2 \
        params ip="33.444.555.6" nic="eth0" cidr_netmask="25"
group web resFS resPHP resAPACHE resPROXY
group webIPs resIP-1 resIP-2
ms msDRBD resDRBD \
        meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true"
clone cloneIP resWEBIP \
        meta globally-unique="true" clone-max="6" clone-node-max="6"
colocation web_ip_range inf: cloneIP msDRBD:Master
colocation web_ips inf: webIPs msDRBD:Master
colocation web_on_drbd inf: web msDRBD:Master
order ordWEB inf: msDRBD:promote web:start
property $id="cib-bootstrap-options" \
        no-quorum-policy="ignore" \
        stonith-enabled="false" \
        expected-quorum-votes="2" \
        dc-version="1.0.9-unknown" \

I was previously using Keepalived, but would prefer to manage the VIP migration via heartbeat/pacemaker, if only I could get the full range of VIPs to show up.

Thanks, Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120116/a87734e0/attachment-0002.html>

More information about the Pacemaker mailing list