starlingx/docs
Code Issues Proposed changes
Files
1c23c1abcaaa591195b9fc667b6dfebb8d817b29
docs/doc/source/node_management/kubernetes/common_host_tasks/swacting-a-master-controller-using-the-cli.rst
Adil ac4d8fea44 Node Management and Distributed cloud Guide updates 
Global Pass Upgrades

Added content from emails attached to ticket and sharepoint

Pacth 01: inputs from email by Greg

Patch 03: Created new section for subcloud group
          updated table 1 shared system configurations

Patch 04: corrected typos (Mary's comments)

Patch 05: solved merged conflict

patch 06: removed broken link

Story: TBD
Task: TBD



Signed-off-by: Adil <mohamed.adilassakkali@windriver.com>
Change-Id: I60b0a40a60a44d30429cd3a4dd8374c16345951a
2021-05-27 16:31:17 -03:00

1.2 KiB
Raw Blame History

Swact Controllers Using the CLI

Swacting initiates a switch of the active/standby roles between two controllers.

Swact is an abbreviated form of the term Switch Active (host). When selected, this option forces the other controller to become the active one in the HA cluster. This means that all active system services on this controller move to standby operation, and that the corresponding services on the other controller become active.

Complete this procedure when you need to lock the currently active controller, or undertake any kind of maintenance procedures; for example, when updating hardware or replacing faulty components.

  • Run the following command from the controller's command line.

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

    If necessary, you can use the --force option to force a swact.

    ~(keystone_admin)$ system host-swact --force <hostname>

    Caution

    The --force option bypasses semantic checks and may cause service failures.