Hi Kazu and Matt, Thanks for the pointers. I think the discussion around pacemaker and pacemaker remote seems most promising, esp with Russel's blog post I found after I emailed earlier [1].
Not sure how tooling would be different, but pacemaker, given its use in the controller cluster anyways, seems a more logical choice. Any issues you people think with a canonical distribution instead of RDO? Affan [1] http://blog.russellbryant.net/2015/03/10/the-different-facets-of-openstack-ha/ On Mon, 15 Feb 2016 at 20:59 Matt Fischer <m...@mattfischer.com> wrote: > I believe that either have your customers design their apps to handle > failures or have tools that are reactive to failures. > > Unfortunately like many other private cloud operators we deal a lot with > legacy applications that aren't scaled horizontally or fault tolerant and > so we've built tooling to handle customer notifications (reactive). When we > lose a compute host we generate a notice to customers and then work on > evacuating their instances. For the evac portion nova host-evacuate or > host-evacuate-live work fairly well, although we rarely get a functioning > floating-IP after host-evacuate without other work. > > Getting adoption of heat or other automation tooling to educate customers > is a long process, especially when they're used to VMware where I think > they get the VM HA stuff for "free". > > > On Mon, Feb 15, 2016 at 8:25 AM, Toshikazu Ichikawa < > ichikawa.toshik...@lab.ntt.co.jp> wrote: > >> Hi Affan, >> >> >> >> >> >> I don’t think any components in Liberty provide HA VM support directly. >> >> >> >> However, many works are published and open-sourced, here. >> >> https://etherpad.openstack.org/p/automatic-evacuation >> >> You may find ideas and solutions. >> >> >> >> And, the discussion on this topic is on-going at HA meeting. >> >> https://wiki.openstack.org/wiki/Meetings/HATeamMeeting >> >> >> >> thanks, >> >> Kazu >> >> >> >> *From:* Affan Syed [mailto:affan.syed....@gmail.com] >> *Sent:* Monday, February 15, 2016 12:51 PM >> *To:* openstack-operators@lists.openstack.org >> *Subject:* [Openstack-operators] [nova] VM HA support in trunk >> >> >> >> reposting with the correct tag, hopefully. Would really appreciate some >> pointers. >> >> ---------- Forwarded message --------- >> From: Affan Syed <affan.syed....@gmail.com> >> Date: Sat, 13 Feb 2016 at 15:13 >> Subject: [nova] VM HA support in trunk >> To: <openstack-operators@lists.openstack.org> >> >> >> >> Hi all, >> >> I have been trying to understand if we currently have some VM HA support >> as part of Liberty? >> >> >> >> To be precise, how are host being down due to power failure handled, >> specifically in terms of migrating the VMs but possibly even their >> networking configs (tunnels etc). >> >> >> >> The VM migration like XEN-HA or KVM cluster seem to require 1+1 HA, I >> have read a few places about celiometer+heat templates to launch VMs for an >> N+1 backup scenario, but these all seem like one-off setups. >> >> >> >> >> >> This issue seems to be very much important for legacy enterprises to move >> their "pets" --- not sure if we can simply wish away that mindset! >> >> >> >> Affan >> >> >> >> >> >> _______________________________________________ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >>
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators