[ClusterLabs] VirtualDomain & parallel shutdown
jpokorny at redhat.com
Tue Nov 27 08:35:16 EST 2018
On 27/11/18 12:29 +0200, Klecho wrote:
> Big thanks for the answer, but I in your ways around I don't see a solution
> for the following simple case:
> I have a few VMs (VirtualDomain RA) and just want and to stop a few of them,
> not all.
> While the first VM is shutting down (target-role=stopped), it starts some
> slow update, which could take hours (because of the possible update case,
> stop timeout is very big).
> During these hours of update, no other VM can be stopped at all.
> If this isn't avoidable, this could be a quite big flaw, because it blocks
> basic functionality.
It looks like having transition "leaves", i.e. particular executive
manipulations like stop/start operations, last in order of tens of
minutes and longer is not what's pacemaker design had in mind,
as opposed ot pushing asychronicity to the extreme (at the cost
of complexity of the "orthogonality/non-interference tests",
But the shutdown procedure can be shortcircuited with possible HA
compromises like this:
- put all the VMs you want to stop into an unmananged state
- trigger the shutdown independently of the cluster mananagement
- when they are indeed off (as also indicated by crm_mon if the
monitor operation hasn't been disabled), they can be resurrected
again when suitable (is-managed=true or dropping that property
to designate an equivalent default)
There is a couple of questions, though, like how to make it that
the particular VM won't be shut down in a standard way, which
would trigger the stated problem again (as mentioned, node
shutdown shall be OK). Customizing resource agent to become
an active pacemaker observer/influencer beside a purposed
notification mechanism and customization through attributes
and rules feels terribly flawed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 819 bytes
Desc: not available
More information about the Users