cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Weller <>
Subject Re: Cloudstack High Availability(HA) Testing
Date Mon, 15 May 2017 12:39:40 GMT

By default, ACS will not HA VMs due to a host failure, as ACS assumes the storage could still
be mounted (machine isn't cleanly fenced off). Deleting the host from ACS  should trigger
a failover of the VMs. There's a lot of work in progress to deal with this a lot more gracefully.
A few folks have written out-of-band applications that watch the logs via a queue (e.g. RabbitMQ)
and on host failover use an api call to remove/disable the hosts to force the VMs to be restarted
on another host.

- Si

From: Kurt K <>
Sent: Saturday, May 13, 2017 2:38 AM
Subject: Cloudstack High Availability(HA) Testing

Hi There,

We are in the middle of some confusion regarding Cloustack High
Availability(HA) testing. In our deployment, we have used 2 hypervisor
kvm servers. We have created a VM with HA compute offering in
hypervisor2 server and then we have enabled maintenance mode on
hypervisor2. After that the VM's are online from hypervisor1 server. But
when we bring down the hypervisor2 server forcefully, the Vm's are not
online from hypervisor1 server. We need help/suggestions on this.

We are using below stack versions on all of our servers.

Cloudstack - 4.6.0
CentOS - 7.3

Also both hypervisors are in same cluster.

Please shed some lights to us.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message