On Fri, Nov 7, 2014 at 4:35 AM, Giulio Fidente <gfidente@xxxxxxxxxx> wrote: > The architecture we're considering is as follows: > > keepalived > haproxy > ceph-mon > > where haproxy and ceph-mon are always up on all openstack 'controller' nodes > (also running cinder) and keepalived is taking care of managing a virtual ip > hosted on one of those For Ceph, you almost certainly don't need to use keepalived or haproxy as all Ceph clients will fail over to the full set of monitor IPs (you need a way of distributing those IPs to the cluster - chef/puppet/ansible/etc/etc can handle that). Having keepalived/haproxy in the loop for ceph-mon is one more thing that could break. We do run cinder services behind the controller/headnodes nodes via keepalived/haproxy - the "trick" such as it is for Ceph is to set all the hostnames in cinder to being the same and it works okay. See: https://github.com/bloomberg/chef-bcpc/blob/master/cookbooks/bcpc/templates/default/cinder.conf.erb We haven't seen any issues in an active/active configuration; though there are some MySQL schema deadlocks that aren't necessarily related to Ceph sitting in Cinder. Cheers. -- justin -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
