On Tue, 2017-11-21 at 12:58 +0200, Euronas Support wrote:
> Thanks for the answer Ken,
> The constraints are:
>
> colocation vmgi_with_filesystem1 inf: vmgi filesystem1
> colocation vmgi_with_libvirtd inf: vmgi cl_libvirtd
> order vmgi_after_filesystem1 inf: filesystem1 vmgi
> order
Thanks for the answer Ken,
The constraints are:
colocation vmgi_with_filesystem1 inf: vmgi filesystem1
colocation vmgi_with_libvirtd inf: vmgi cl_libvirtd
order vmgi_after_filesystem1 inf: filesystem1 vmgi
order vmgi_after_libvirtd inf: cl_libvirtd vmgi
On 20.11.2017 16:44:00 Ken Gaillot wrote:
On Fri, 2017-11-10 at 11:15 +0200, Klecho wrote:
> Hi List,
>
> I have a VM, which is constraint dependant on its storage resource.
>
> When the storage resource goes down, I'm observing the following:
>
> (pacemaker 1.1.16 & corosync 2.4.2)
>
> Nov 10 10:04:36 [1202] NODE-2pengine:
Hi List,
I have a VM, which is constraint dependant on its storage resource.
When the storage resource goes down, I'm observing the following:
(pacemaker 1.1.16 & corosync 2.4.2)
Nov 10 10:04:36 [1202] NODE-2pengine: info: LogActions:
Leave vm_lomem1 (Started NODE-2)