Re: [ClusterLabs] VirtualDomain and Resource_is_Too_Active ?? - problem/error

2019-06-03 Thread Jan Pokorný
On 03/06/19 13:39 +0200, Jan Pokorný wrote: > Yes, there are at least two issues in ocf:heartbeat:VirtualDomain: > > 1/ dealing with user input derived value, in an unchecked manner, while >such value can be an empty string or may contain spaces >(for the latter, see also I've raised back

[ClusterLabs] announcement: schedule for resource-agents release 4.3.0

2019-06-03 Thread Oyvind Albrigtsen
Hi, This is a tentative schedule for resource-agents v4.3.0: 4.3.0-rc1: June 14. 4.3.0: June 21. I've modified the corresponding milestones at https://github.com/ClusterLabs/resource-agents/milestones If there's anything you think should be part of the release please open an issue, a pull reque

Re: [ClusterLabs] VirtualDomain and Resource_is_Too_Active ?? - problem/error

2019-06-03 Thread Jan Pokorný
On 29/05/19 09:29 -0500, Ken Gaillot wrote: > On Wed, 2019-05-29 at 11:42 +0100, lejeczek wrote: >> I doing something which I believe is fairly simple, namely: >> >> $ pcs resource create HA-work9-win10-kvm VirtualDomain \ >> hypervisor="qemu:///system" \ >> config="/0-ALL.SYSDATA/QEMU_VMs/HA-

[ClusterLabs] Antw: Inconclusive recap for bonding (balance-rr) vs. HA (Was: why is node fenced ?)

2019-06-03 Thread Ulrich Windl
Hi! A rather good summary I think, specifically the notes on link failure detection and timeouts. One problem is that corosync reacts very (too?) fast on communication dropouts, while link failure monitoring (and recovery) measures are typically much slower. We also fell into that pit years ago: