From: Stephan Seitz
Sent: Thursday, October 13, 2016 10:31 AM
To: users@cloudstack.apache.org
Subject: Re: Long downtimes for VMs through automatically triggered storage
migration
>> We turn off HA storage migration, as it doesn't make much sense t
> >
> > What we are still thinking about is the point, if it is principally
> > a
> > good idea to limit CloudStack in its ability to freely and
> > automatically
> > migrate VMs between all cluster nodes. Is setting
> > "enable.ha.storage.migration"=false the intended way to handle a
> > setup
>
See inline.
>What we are still thinking about is the point, if it is principally a
>good idea to limit CloudStack in its ability to freely and automatically
>migrate VMs between all cluster nodes. Is setting
>"enable.ha.storage.migration"=false the intended way t
Hi Simon,
thanks for your swift answer!
Am 12.10.2016 um 15:47 schrieb Simon Weller:
> So if I understand correctly here, you have 2 clusters within a pod and
> you're using cluster level storage (meaning each cluster has it's own primary
> storage).
You are perfectly right.
> There is a glo
Hi Melanie,
So if I understand correctly here, you have 2 clusters within a pod and you're
using cluster level storage (meaning each cluster has it's own primary storage).
There is a global configuration item for preventing CloudStack from attempting
to automatically migrate across primary stor
