Node Cordoning and Uncordoning

Node cordoning is the process of marking compute nodes as unschedulable, preventing new workflows from being placed on them. This is commonly used during maintenance, node upgrades, or when preparing to remove nodes from the cluster.

Changes to compute node scheduling require that a fuzzball context is set up and authorized.

$ fuzzball context create <context_name> <api_url> <oidc_server_url> <oidc_client_id>

$ fuzzball context login -u <admin_username> -p '<admin_password>'

The fuzzball node cordon command marks one or more compute nodes as unschedulable.

$ fuzzball node cordon <node-id>

Example:

$ fuzzball node cordon node-worker-01

$ fuzzball node cordon --all

Alternative syntax:

$ fuzzball node cordon -a

The fuzzball node uncordon command marks one or more compute nodes as schedulable again.

$ fuzzball node uncordon <node-id>

Example:

$ fuzzball node uncordon node-worker-01

$ fuzzball node uncordon --all

Alternative syntax:

$ fuzzball node uncordon -a