> So for all lease-holding vms, push the lease to a different storage domain
> (on different
> storage hardware), apply the upgrade and then push the leases back? And that
> can be done
> whilst the VMs are running? Leases must be frequently renewed, so I guess no
> particular
> reason why not.
So for all lease-holding vms, push the lease to a different storage domain (on
different storage hardware), apply the upgrade and then push the leases back?
And that can be done whilst the VMs are running? Leases must be frequently
renewed, so I guess no particular reason why not.
Does that
my current idea of a workaround is to disable storage leases before netapp
upgrades, and re-enable them after upgrades are done. python sdk should make
this fairly easy
(https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/set_vm_lease_storage_domain.py
and
I too am suffering from this. Whilst a proper oVirt-configuration item would be
ideal, the RFE suggests that there is a manual work-around for setting
sanlock's io_timeout, albeit not recommended. Could anyone share what it is?
It seems clear from the sanlock code that io_timeout is the only
So after a little wild discussion with support it boiled down to this BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1705289 which suggests it may be a
good idea to have sanlock io_timeout configureable :)
___
Users mailing list -- users@ovirt.org
To
Hi,
NFS hard mounts should not help with sanlock. It should just kill the VMs
after 60 seconds same as a soft mount.
The sanlock timeout: I asked RedHat support about that in a case for my RHV
environment. They said this should not be changed.
Only thing that came to my mind: disable storage
I know 2 approaches.
1. Use NFS hard mounting option - it will never give error to sanlock and it
will be waiting until NFS is recovered (never tries this one, but in theory
might work)
2. Change the default sanlock timeout (last time I tried that - it didn't work)
. You might need help from
Hi, nope, no storage leases and no fencing at all (because of vlan
separation between mgmt and RAC).
We have own HA fencing mechanism in place, which will trigger action
over API when alarm in monitoring is triggered.
HTH
On 18.04.19 13:12, klaasdem...@gmail.com wrote:
Hi,
are you using
Hi,
are you using ovirt storage leases? You'll need them if you want to
handle a hypervisor completely unresponsive (including fencing actions)
in a HA setting. Those storage leases use sanlock. If you use sanlock a
VM gets killed if the lease is not renewable during a very short
timeframe
Hi,
are you using ovirt storage leases? You'll need them if you want to
handle a hypervisor completely unresponsive (including fencing actions)
in a HA setting. Those storage leases use sanlock. If you use sanlock a
VM gets killed if the lease is not renewable during a very short
timeframe
Hi, we have netapp nfs with ovirt in production and never experienced an
outage during takeover/giveback ..
- the default ovirt mount options should also handle little NFS timeout
11 matches
Mail list logo
