I am thinking you would make the ListVolumeStats API call to the SF cluster
from a management server because we know that management servers should have
access to the management network of the SF cluster. I know some KVM hosts might
have access to the management network of the SF cluster that su
Hi Paul, Hi Mike, Hi Syed,
@Paul
> Doesn’t the same problem exist with that? If the agent dies, then the fake
> volume will stop being updated but the VMs would still be running.
Do you mean we don’t know if a machine is running and get an false positive? I
think about if we had only one fake
t: 08 June 2020 17:14
> To: dev@cloudstack.apache.org
> Subject: Re: Managed Storage and HA
>
> My suggestion would be to use a "fake" volume for each host and use that
> to check the activity of a host. The volume can be updated by the agent
> periodi
; -Original Message-
> From: Syed Ahmed
> Sent: 08 June 2020 17:14
> To: dev@cloudstack.apache.org
> Subject: Re: Managed Storage and HA
>
> My suggestion would be to use a "fake" volume for each host and use that
> to check the activity of a host. The volume can
-
From: Syed Ahmed
Sent: 08 June 2020 17:14
To: dev@cloudstack.apache.org
Subject: Re: Managed Storage and HA
My suggestion would be to use a "fake" volume for each host and use that to
check the activity of a host. The volume can be updated by the agent
periodically and then we c
My suggestion would be to use a "fake" volume for each host and use that to
check the activity of a host. The volume can be updated by the agent
periodically and then we can use the above API from the management server
to query the volume activity.
On Tue, Jun 2, 2020 at 1:18 PM Tutkowski, Mike
w
Hi Sven,
You can use the ListVolumeStats API call (I put in an example request and
response below).
Since this goes over the management network, though, it's possible if your
management network is down, but your storage network is up that this call could
fail, but your VMs might still have per
Hi Paul,
Thanks for the answer and help.
Ok. Secondary Storage is no good solution what I understand.
> 1. HAManager
> 2. HighAvailbilityManager
> 3. KVMHAConfig
which of the three should we expand and which one should be active?
@Mike did you know somethings like that if there is a check of
Hi Sven,
I think that there is a piece of the jigsaw that you are missing.
Given that the only thing that we know, is that we can no longer communicate
with the host agent; To avoid split brain/corruption of VMs, CloudStack must
determine if the guests VMs are still running on the host not. T
