<div dir="ltr"><div><span style="font-family:arial,sans-serif;font-size:14px">We minimized the impact of this by creating a small subnet that just had the switch address, host addresses and vrrp address in it.</span><span style="font-family:arial,sans-serif;font-size:14px"><br>
</span></div><div style><font face="arial, sans-serif"><span style="font-size:14px">It seems a feasible solution for us.</span></font></div><div style><font face="arial, sans-serif"><span style="font-size:14px"><br></span></font></div>
<span style="font-family:arial,sans-serif;font-size:14px">>></span><span style="font-family:arial,sans-serif;font-size:14px">We avoided pacemaker in this particular instance because the keepalived setup and configuration was so very simple - only a couple of lines in a config file, and because we didn't need any of the other available HA features.</span><br>
<div><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:14px">Actually this is also the reason we chose keepalived.</span></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2013/6/26 Brent Roskos <span dir="ltr"><<a href="mailto:brent.roskos@solinea.com" target="_blank">brent.roskos@solinea.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I stand corrected. Mostly confused since the keepalived didn't actually need addresses in the multicast IP range. It does use it - as I can see with ifconfig. We minimized the impact of this by creating a small subnet that just had the switch address, host addresses and vrrp address in it. All the chatter was contained within that block.<div>
<br></div><div>We avoided pacemaker in this particular instance because the keepalived setup and configuration was so very simple - only a couple of lines in a config file, and because we didn't need any of the other available HA features.</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div>Brent</div></font></span></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Wed, Jun 26, 2013 at 10:03 AM, Jesse Pretorius <span dir="ltr"><<a href="mailto:jesse.pretorius@gmail.com" target="_blank">jesse.pretorius@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>On 26 June 2013 15:42, Brent Roskos <span dir="ltr"><<a href="mailto:brent.roskos@solinea.com" target="_blank">brent.roskos@solinea.com</a>></span> wrote:<br>
</div><div class="gmail_extra"><div class="gmail_quote"><div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I've also used keepalived for services that did not scale laterally. In this case I put two horizon servers behind an active/passive virtual IP. This was also pretty simple as there was no need to maintain state information in for active passive. That wouldn't work quite as well when capacity thresholds started to become a concern.</div>
<div><br></div><div>Neither of the above required multicast support - which really helps with deployment options.</div></div></blockquote><div><br></div></div><div>*ahem* keepalived most definitely requires multicast support for its vrrp... and it's quite noisy. If there's a way to make it use unicast instead, I'd definitely like to know.</div>
<div><br></div><div>corosync & pacemaker can do a virtual IP failover between as many nodes as you like using unicast instead of multicast.</div></div></div></div>
<br></div></div><div class="im">_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br></div>