<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">></span><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">> Hello,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">> I am thinking about using the keystone as an authentication system but I am afraid about failures which can affect all the cluster. In fact if the keystone server dies then our full cluster will stop. It would be better if we could use
HA with the keystone. Then if > our primary keystone server dies we have to elect a new primary keystoe server. Are there some tools which can be used in HA deployment?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">> Any piece of advice will be valuable<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">IMHO: get a proper ha load-balancer solution, make sure you install at least 2 of all APIS and load-balance in active-active mode<o:p></o:p></p>
<p class="MsoNormal">The OpenStack APIs are stateless so you can run multiple servers at the same time as long as they can connect to the same database backend.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The load-balancer is usable for all APIs, you can use it as the HA-IP for mysql and can also be used to offload SSL so you just have one place to configure your certificates.<o:p></o:p></p>
<p class="MsoNormal">(for galera, make use of a “sorry-server” and not active-active load-balancing for writes)<b><o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The great thing about a load-balancer is that you remove all HA complexity out of the OpenStack setup.<o:p></o:p></p>
<p class="MsoNormal">In my personal opinion the pacemaker setups can function OK but pacemaker is a complex piece of software and it is not unlikely to cause downtime either to misconfiguration or inexperienced people operating it.<o:p></o:p></p>
<p class="MsoNormal">Especially if pacemaker is also starting/stopping mysql/rabbit/openstack services and not only moving around a few IPs.<o:p></o:p></p>
<p class="MsoNormal">If you are going the pacemaker way make sure you play around with it quite a bit and do failure tests so you are comfortable with the commands and know what to look for when things go wrong.<o:p></o:p></p>
<p class="MsoNormal">Do not forget: any other people operating the pacemaker cluster will need that knowledge and a 2 node cluster is not a real cluster (split-brains).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal">Robert van Leeuwen<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>