[ClusterLabs] Antw: [EXT] faulty business logic

[lejeczek]

On 23/02/2021 07:38, Ulrich Windl wrote:
>>>> 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).
>
Nope, that logic will be faulty - it's: I go with you and 
not the vice versa. If I cannot follow wherever you go then 
tough luck and I do _not_ drag you back some place else.
I think 'stickness' suggested kgaillot should remedy my 
situation.
thanks, L


>> 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/
>
>
>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/