[rabbitmq-discuss] Release of HA + Pacemaker guide
matthew at lshift.net
Mon Apr 26 14:59:38 BST 2010
On Mon, Apr 26, 2010 at 11:48:12PM +1000, Joe Healy wrote:
> Thanks - this is a great guide for ha rabbit.
Good to hear!
> We've been using a similar set up for a couple of months with iscsi instead
> of drdb.
Yup. I was simply using drbd because it's pretty much the lowest common
denominator - (e)nbd would also be possible (over RAID 1), but that's
more fiddly. iscsi / NAS / SAN and such ilk would, I'd expect, give
> Do you need to add resource grouping or colocation to the bunny and ip
> resources to make sure that they move together? Is it important that the ip
> migrates before the bunny starts so that it will listen on the right
Yes and yes:
"crm(ip)# configure primitive ip ocf:heartbeat:IPaddr2 params ip="192.168.50.1" cidr_netmask="24"
crm(ip)# configure colocation bunny_on_ip inf: bunny ip
crm(ip)# configure order bunny_after_ip inf: ip bunny
This should all be looking rather familiar by now. We create the ip
resource, we say that the bunny resource must run on the same node as
the ip resource, and we make sure that the bunny resource is started
after, and stopped before, the ip resource."
These are necessary steps - sure, you could have bunny just listen on
0.0.0.0 which is the default, but if the network i/f isn't there when it
starts then there may be problems. I'm not quite sure what the IPaddr2
script is doing, but it's clearly at least slightly magic - the
interface doesn't show up in the output of ifconfig. In general, I found
things more reliable if the IP address is already there before bunny
More information about the rabbitmq-discuss