[ClusterLabs] Antw: [EXT] faulty business logic

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Tue Feb 23 02:38:49 EST 2021


>>> lejeczek <peljasz at yahoo.co.uk> schrieb am 19.02.2021 um 17:40 in Nachricht
<e4ef17ba-c5ac-2045-4084-a76d5a93bf10 at yahoo.co.uk>:
> Hi guys.
> 
> I have a simple cluster with simple constraints:
> 
> Colocation Constraints:
>    check-jupyterhub with openvpn-server (score:INFINITY)
>    secret-dropbox with openvpn-server (score:INFINITY)
> Ticket Constraints:
> 
> no other constraints.
> What puzzles me, and I assume I miss something here, is - 
> when/if resource 'secret-dropbox' fails on a node then 
> cluster relocates, reshuffles everything.
> That is bit bizarre, no?

Actually no: If secret-dropbox failes on one node, it is tried on the other. And to fulfill the colocation contraints, the rest must move also (while possible).

> What is the logic behind that? (and how to tell cluster that 
> 'openvpn-server' is what matters here and if 
> 'secret-dropbox' can't follow then, well, tough luck)
> 
> many thanks, L.
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/ 






More information about the Users mailing list