What does "cordoned" means?

[kelson42]

I'm puzzled by the word itself and its meaning in the context of the Zimfarm

[elfkuzco]

It means the owner doesn't want their worker to run tasks anymore (#1408)

[benoit74]

It allows to make the distinction between "disabled" (where Zimfarm admins do not want to run tasks on the worker anymore) and "cordoned" (where worker owner doesn't want to run tasks anymore).

"cordoned" setting is also useful when a worker in enrolled on multiple Zimfarm because the "cordoned" setting is stored in worker config file so it automatically applies to all Zimfarms where "disabled" is a setting stored in Zimfarm DB so this has to be done in all Zimfarms.

"cordoned" word has been borrowed from k8s which use the same word for the same intent (disable a k8s node from getting new pods scheduled to run).

[benoit74]

Note it is also documented in the documentation: https://github.com/openzim/zimfarm/tree/main/worker#using-the-cordoned-environment-variable

[kelson42]

Almost any action can be done by many people with many roles. We don't use new word each time depending who requested it.

To me, and most Zimfarm usets, it is just too complicated/subtle. Why not just say: the worker is "paused" and write - where it relevant - by whom (nickname and/or role)?

[benoit74]

And how do we decide who can undo what has been done by someone? We have no way ATM to say that.

Problem was: Zimfarm admins decides to pause a worker, how do we unsure Zimfarm owner cannot un-pause it? Or the opposite: Zimfarm owner decide to pause worker, how do we unsure Zimfarm admin cannot decide to unpause it?

Using two very distinct settings with two very distinct names was the leaniest path. Zimfarm owners do not need to know about Zimfarm admin setting. Zimfarm admins are not that many and should be able to cope with two distinct settings.