Hi Lele - <br><br>On the OpenStack mailing list there was a post about network and high availability, but specifically this Etherpad at <a href="http://etherpad.openstack.org/making-nova-components-ha">http://etherpad.openstack.org/making-nova-components-ha</a> is the only area where people are putting in their ideas for how to make OpenStack HA. <br>
<br>Hope this helps, feel free to continue the discussion.<br>Anne <br><br>Dear All,<br>
<br>
We (NTT PF Lab) will be discussing on how we can support HA of
nova-network component tomorrow at 4:00 P.M.<br>
Actually Edward would be driving this session for his blueprint <a href="https://blueprints.launchpad.net/nova/+spec/making-nova-components-ha" target="_blank">https://blueprints.launchpad.net/nova/+spec/making-nova-components-ha</a>
and we have requested Edward to reserve some time slot for us so that
we can explain what we did to achieve HA of nova-network service
(Active/Standby) using heartbeat (Linux-HA).<br>
<br>
Please refer to the attached document which gives you more information
about the POC, the problems we encountered and how did we resolve those
problems.<br>
<br>
We have created etherpad at <a href="http://etherpad.openstack.org/making-nova-components-ha" target="_blank">http://etherpad.openstack.org/making-nova-components-ha</a>.
Your feedback/suggestions are welcome.<br>
<br>
See you all tomorrow at 4:00 P.M.<br>
<br>
Thanks and Best Regards,<br>
<font color="#888888">Tushar Patil.<br>
</font><br>______________________________<div id=":2mt">_________________<br>
Mailing list: <a href="https://launchpad.net/%7Eopenstack" 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/%7Eopenstack" 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></div><br><div style="margin: 2em 0pt;" name="sig_d4a6b6619e"><div style="padding: 5px; font-size: 11px; color: rgb(102, 102, 102); font-family: sans-serif;">
<strong>Anne Gentle</strong>
<br>
<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a><br>
<div style="font-size: 10px;">
<a href="http://justwriteclick.com/" target="_blank">my blog</a> |
<a href="http://xmlpress.net/publications/conversation-community/" target="_blank">my book</a> |
<a href="http://www.linkedin.com/in/annegentle" target="_blank"><span>LinkedIn</span></a> | <a href="http://del.icio.us/annegentle" target="_blank">Delicious</a> |
<a href="http://twitter.com/annegentle" target="_blank">Twitter</a>
</div></div></div><div class="gmail_quote">On Wed, May 18, 2011 at 7:42 AM, Leandro Reox <span dir="ltr"><<a href="mailto:leandro.reox@gmail.com">leandro.reox@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
List, <div><br></div><div>How do you guys manage HA and Live migration in case of harware failure in Openstack ? , i read that there is no way to manage this in a native way, but products like pacemaker + virtualdomain can do that . So i want to know your opinions for a fully HA environment over Openstack. <br>
<br>Best regards<br><br>Lele</div>
<br>_______________________________________________<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" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br>