<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>All<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I was wondering whether my current understanding of HA in Quantum is currently correct or not as there does seem to be a little confusion. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>From what I understand, the Quantum Service, DHCP and L3 agents are all supported through Pacemaker RA’s or using the native messaging in Openstack Grizzly. Using the Grizzly Quantum messaging heartbeats, the Quantum service will keep deploying configurations until a point in time the agents are not responding. When this occurs it will look to deploy configurations on other available Network nodes running the agents. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>However, the bit I am really fuzzy about it as follows. What happens if the network node completely fails? How would I recover the current networking configuration from the failed network node and re-deploy it on a working network node automatically? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I also see from reading multiple sources, that it would be possible to deploy the same configuration to multiple network nodes at the same time using the Quantum API, but it isn’t supported currently through the normal GUI API calls so it would be an enhancement or a separate orchestration step.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If possible, would someone be able to point me in the right direction of how I can provide full HA Quantum based services for not only new configurations, but how I would re-deploy and recover configurations from a failed network node. I’m looking at this from an SLA perspective as well – is it possible to achieve failover between two active network nodes?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks in advance to the great community out there.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Jon<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>