[ClusterLabs] Antw: [EXT] Removing a resource without stopping it

Klaus Wenninger kwenning at redhat.com
Mon Jan 31 15:02:21 EST 2022

On Mon, Jan 31, 2022 at 2:43 PM Jehan-Guillaume de Rorthais <jgdr at dalibo.com>

> On Mon, 31 Jan 2022 08:49:44 +0100
> Klaus Wenninger <kwenning at redhat.com> wrote:
> ...
> > Depending on the environment it might make sense to think about
> > having the manual migration-step controlled by the cluster(s) using
> > booth. Just thinking - not a specialist on that topic ...
> Could you elaborate a bit on this?
> Boothd allows to start/stop a ressource in the cluster currently owning the
> associated ticket. In this regard, this could help to stop the resource on
> one
> side and start it on the other one.
> However, as far as I know, there's no action like migrate-to/migrate-from
> that
> could be executed across multiple clusters to deal with the migration steps
> between both clusters... or does it?
Guess I hadn't thought that far. 'controlled' above is probably not the
wording. 'safeguard' may be the better one. Was mainly thinking of a
that would prevent the initial cluster from starting the vm again if
goes wrong with the sequence of actions described.
But of course the idea of using booth to actively trigger a migration sounds
appealing and generally useful.
Maybe something to put on the wishlist ;-)

> ++
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20220131/9d999780/attachment.htm>

More information about the Users mailing list