Hi Jon,
Don't worry, TBH I'm dubious about those claiming to have VM-HA working when a
host crashes (but doesn't restart).
I'll check in with the guys that set values for host-ha when testing, to see
which ones they change and what they set them to.
paul.an...@shapeblue.com
www.shapeblue.com
Rohit / Paul
Thanks again for answering.
I am a Cisco guy with an ex Unix background but no virtualisation experience
and I can honestly say I have never felt this stupid before
I have Cloudstack working but failover is killing me.
When you say VM HA relies on the host telling CS the VM
Jon,
In the VM's compute offering, make sure that HA is ticked/enabled. Then use
that HA-enabled VM offering while deploying a VM. Around testing - it depends
how you're crashing. In case of KVM, you can try to cause host crash (example:
echo c > /proc/sysrq-trigger) and see if HA-enabled VMs
I'm afraid that is not a host crash. When shutting down the guest OS, the
CloudStack agent on the host is still able to report to the management server
that the VM has stopped.
This is my point. VM-HA relies on the management sever communication with the
host agent.
Kind regards,
Paul Angus
Hi Jon and Angus,
I did not shutdown the VMs as Yiping Zhang said, but I have confirmed this
and discussed earlier in the users list that my HA-enabled VMs got started
on another suitable available host in the cluster even when I didn't have
IPMI-enabled hardware and did no configuration for OOBM
Hi Andrija,
first of all thanks for your reply. I have now testet the setup on a Ubuntu
Xenial. Same issu with Default VPC Offering. Redundant VPC offering works also
without any problems. Same as on CentOS.
See delow the debug log (censored public Ips):
2018-05-23 12:58:05,161 INFO
Hi Ben,
interesting parts seems to be:
2018-05-23 12:59:47,213 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-5:null) (logid:ef8b353e) getting broadcast uri for
pif enp8s0f0.233 and bridge brenp8s0f0-233
2018-05-23 12:59:47,213 DEBUG
I can say for fact that VM's using a HA enabled service offering will be
restarted by CS on another host, assuming there are enough capacity/resources
in the cluster, when their original host crashes, regardless that host comes
back or not.
The simplest way to test VM HA feature with a VM
Jon,
As Rohit says, it is very important to understand the difference between VM HA
and host HA.
VM HA relies on the HOST telling CloudStack that the VM is down on order for
CloudStack start it again (wherever that ends up being).
Any sequence of events that ends up with VM HA restarting the VM