docs/doc/source/node_management/kubernetes/common_host_tasks/locking-a-host-using-the-cli.rst
Ron Stone f125a8b892 Remove spurious escapes (r8,dsR8)
This change addresses a long-standing issue in rST documentation imported from XML.
That import process added backslash escapes in front of various characters. The three
most common being '(', ')', and '_'.
These instances are removed.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Id43a9337ffcd505ccbdf072d7b29afdb5d2c997e
2023-03-01 11:19:04 +00:00

1.3 KiB

Lock a Host Using the CLI

Locking an unlocked host takes it out of service for configuration and maintenance purposes.

On a controller node, the state transition only succeeds if there are no services running in active mode on the host.

On a worker node (or ), the state transition only succeeds if all currently running containers (hosted applications) on the host can be re-located on alternative worker nodes or Controller. Re-location of containers is initiated automatically by as soon as the state transition is requested. For containers, a live re-location of the container to another host is attempted. A NoExecute taint, as shown below, is applied to the host, causing any containers on that host to be evicted.

services=disabled:NoExecute

Note

On a Simplex system, where re-location of containers is not possible, all running containers are stopped when a host is locked. Other services continue to run.

  • You can lock a host from the controller's command line as follows:

    ~(keystone_admin)$ system host-lock <hostname>