-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Been there and this is not the way to do it. What you did is enable host HA and out-of-band management, not VM HA, and host HA, to my knowledge, does not work as it's intended. What you want is for the VMs to start on a different host in case of failure of the original host. For that, you need to have the offering with HA and a nfs primary storage in disabled mode named HA, a simple folder with this name shared via nfs. That's all. You'll see that in the event of host failure, being it power related, network, etc., the vms that are on that host and are HA enabled will power up on other hosts after some time - no idea where to configure these timings, for me the HA process starts well after 10-12 minutes after the host failure. |
Beta Was this translation helpful? Give feedback.
-
We run into the same situation and did not understand HA in Cloudstack correctly, too. It is really hard for CS to be sure that a host is really down. There are so many situations where the management server is unable to connect to the host, but all VMs are still running. If CS no is trying to start the VMs on other hosts it will end in a mess.
Even if possible, we are not going to automate this. We want control over this and one big reason is that we also run SDS (linstor) on all hosts and so it will impact our primary storage, too. Hope that helps! |
Beta Was this translation helpful? Give feedback.
-
@tdtmusic2 @sbrueseke |
Beta Was this translation helpful? Give feedback.
@tdtmusic2 @sbrueseke
Hi, I found something in code, maybe it can resolve this issue.
#10026