starlingx/docs
Code Issues Proposed changes
Files
f01c69c1e43da9e36764e9a70c17183a9f7a5f48
docs/doc/source/node_management/kubernetes/common_host_tasks/locking-a-host-using-the-cli.rst
Stone 0d7d14b0c2 File structure reorg 
Changed names of kubernetes and openstack subdirs, and reorganized index files
for consistency with other docs.

Signed-off-by: Stone <ronald.stone@windriver.com>
Change-Id: I234dd88e500f12e7c68b0e8bc5b68ca6e0875aba
2021-02-22 13:04:19 -05:00

1.3 KiB
Raw Blame History

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>