What you're looking at is called fault tolerance in other hypervisors.

As far as i know, ovirt doesn't implement such solution.

But if your system doesn't support failure recovery done by high availability options, you should take in account to revise your application architecture if you want to keep running on ovirt.

Luca

Il 10 feb 2018 8:31 AM, "Ranjith P" <ranjithspr13@yahoo.com> ha scritto:
Hi,

>>Who's shutting down the hypervisor? (Or perhaps it is shutdown externally, due to overheating or otherwise?)

We need a continuous availability of VM's in our production setup. If the hypervisor goes down due to any hardware failure or work load then VM's above hypervisor will reboot and started on available hypervisors. This is normally happening but it disrupting VM's. Can you suggest a solution in this case? Can we achieve this challenge using glusterfs?

Thanks & Regards
Ranjith


On Sat, Feb 10, 2018 at 2:07 AM, Yaniv Kaul


On Fri, Feb 9, 2018 at 9:25 PM, ranjithspr13@yahoo.com <ranjithspr13@yahoo.com> wrote:
Hi,
Anyone can suggest how to setup VM Live migration (without restart vm) while Hypervisor goes down in ovirt?

I think there are two parts to achieving this:
1. Have a script that migrates VMs off a specific host. This should be easy to write using the Python/Ruby/Java SDK, Ansible or using REST directly.
2. Having this script run as a service when a host shuts down, in the right order - well before libvirt and VDSM shut down, and would be fast enough not to be terminated by systemd.
This is a bit more challenging.

Who's shutting down the hypervisor? (Or perhaps it is shutdown externally, due to overheating or otherwise?)
Y.
 
Using glusterfs is it possible? Then how?

Thanks & Regards
Ranjith

Sent from Yahoo Mail on Android

______________________________ _________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/ mailman/listinfo/users




_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users