[openstack-dev] [Cinder]Behavior when one cinder-volume service is down

Dulko, Michal michal.dulko at intel.com
Tue Sep 15 15:16:04 UTC 2015


> From: Eduard Matei [mailto:eduard.matei at cloudfounders.com]
> Sent: Tuesday, September 15, 2015 4:54 PM
> 
> Hi,
> 
> Let me see if i got this:
> - running 3 (multiple) c-vols won't automatically give you failover
> - each c-vol is "master" of a certain number of volumes
> -- if the c-vol is "down" then those volumes cannot be managed by another
> c-vol
> 
> What i'm trying to achieve is making sure ANY volume is managed
> (manageable) by WHICHEVER c-vol is running (and gets the call first) - sort of
> A/A - so this means i need to look into Pacemaker and virtual-ips, or i should
> try first the "same name".
> 

I think you should try Pacemaker A/P configuration with same hostname in cinder.conf. That's the only safe option here.

I don't quite understand John's idea of how virtual IP can help with c-vol, as this service only listens on AMQP queue. I think VIP is useful only for running c-api service. 


More information about the OpenStack-dev mailing list