<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 26 Nov 2013, at 14:05, Robert van Leeuwen <<a href="mailto:Robert.vanLeeuwen@spilgames.com">Robert.vanLeeuwen@spilgames.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div ocsi="0" fpstyle="1" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word;"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;">> Hello,<div style="font-family: 'Times New Roman'; font-size: 16px;"><div>> I've read the documentation about Openstack HA (<a href="http://docs.openstack.org/high-availability-guide/content/index.html" target="_blank">http://docs.openstack.org/high-availability-guide/content/index.html</a>) and I successfully implemented the active/passive model (with corosync/pacemaker) for the two services Keystone and Glance (MySQL HA is based on<br>> Percona-XtraDB multi-master).</div><div>> I'd like to know from the experts, which one is the best (and possibly why) model for HA, between active/passive and active/active, basing on their usage experience (that is for sure longer than mine).</div><br>Hi,<br><br>No so much about active/passive and active/active but maybe helpful:<br>My personal opinion is that I would try to avoid cluster software as much as possible.<br></div></div></div></blockquote><div><br></div><div>Hi Robert,</div><div>do you mean try to NOT use pacemaker/corosync ?</div><div>they say it’s about the best cluster software around… but I understand your point which suggests more simplicity…</div><div><br></div><div>thanks,</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>A.</div><br><blockquote type="cite"><div ocsi="0" fpstyle="1" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word;"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;"><div style="font-family: 'Times New Roman'; font-size: 16px;">They are highly complex pieces of software and you run the chance of creating more issues then you are solving.<br><br>However, some piece will need to be highly available in your setup.<br>I would limit those to as few (and simple) technologies as possible.<br>In our company we already had HA load-balancers (a propriety solution) in house so we decided to use those to also make Openstack HA.<br><br>The only real pain point we have left is the neutron l3 router.<span class="Apple-converted-space"> </span><br>A possible solution would be to use our hardware routers for this (we use VLANs so this is pretty easy to setup/integrate).<br>We will probably go that way in the future.<br>(Currently we have no strict HA requirement for the router yet since all our production traffic to the cloud is going straight from/to the load balancers to the virtual machines without the l3-router in between)<br><br>Cheers,<br>Robert van Leeuwen<br></div></div>_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></div></blockquote></div><br></body></html>