On 4/6/21 10:23 AM, d tbsky wrote:
Klaus Wenninger
Guess that heavily depends on what you are running inside your VMs.
If the services inside don't need each other or anything provided by
the other cluster-resources (or other way round) or everything is
synchronizing independently from the
Klaus Wenninger
> Guess that heavily depends on what you are running inside your VMs.
> If the services inside don't need each other or anything provided by
> the other cluster-resources (or other way round) or everything is
> synchronizing independently from the cluster ...
> What you could
On 3/31/21 11:11 AM, d tbsky wrote:
Klaus Wenninger
In this case it might be useful not to wait some defined time
hoping startup of the VM would have gone far enough that
the IO load has already decayed enough.
What about a resource that checks for something running
inside the VM that
Klaus Wenninger
> In this case it might be useful not to wait some defined time
> hoping startup of the VM would have gone far enough that
> the IO load has already decayed enough.
> What about a resource that checks for something running
> inside the VM that indicates that startup has completed?
On Mon, Mar 29, 2021 at 10:32 PM Klaus Wenninger
wrote:
> On 3/29/21 8:44 AM, d tbsky wrote:
> > Reid Wahl
> >> An order constraint set with kind=Serialize (which is mentioned in the
> first reply to the thread you linked) seems like the most logical option to
> me. You could serialize a set of
On 3/29/21 8:44 AM, d tbsky wrote:
Reid Wahl
An order constraint set with kind=Serialize (which is mentioned in the first
reply to the thread you linked) seems like the most logical option to me. You
could serialize a set of resource sets, where each inner set contains a
VirtualDomain
Reid Wahl
>
> An order constraint set with kind=Serialize (which is mentioned in the first
> reply to the thread you linked) seems like the most logical option to me. You
> could serialize a set of resource sets, where each inner set contains a
> VirtualDomain resource and an
An order constraint set with kind=Serialize (which is mentioned in the
first reply to the thread you linked) seems like the most logical option to
me. You could serialize a set of resource sets, where each inner set
contains a VirtualDomain resource and an ocf:heartbeat:Delay resource.
5.3.1.
Hi:
since the vm start/stop at once will consume disk IO, I want to
start/stop the vm
one-by-one with delay.
search the email-list I found the discussion
https://oss.clusterlabs.org/pipermail/pacemaker/2013-August/043128.html
now I am testing rhel8 with pacemaker 2.0.4. I wonder if
