Decommission a Node

Before removing a node from an active VM Squared cluster it is recommended to decommission it first. This step allows any active VMs to be live migrated from the node and any data to be safely migrated before the node is powered down.

If a node is removed from the cluster without first decommissioning the same steps can be used to remove it from the list of active hosts.

Warning

Decommissioning a node from a VM Squared cluster is not reversible. To add the node back requires a new installation.

Assumptions

  • User has added SSH key to the Cluster SSH Authorized Keys outlined in Dashboard Console

Decommission a node

To decommission a node the user must log into the Dashboard Console. From the dashboard console type decom-node and follow the prompts.

Decommissioning a node may take a while as all data has to be migrated to other nodes in the cluster.

The example below illustrates selecting si-overlapped-4 to be decommissioned and the typical output.

VMsquared:vmsquared\dashboard> decom-node
Available hosts:
0) Exit
1) si-overlapped-1
2) si-overlapped-2
3) si-overlapped-3
4) si-overlapped-4
#? 4
Selected host: si-overlapped-4
IPs: fdb2:32f8:9806::4
Static: true
Compute: true
Storage: true
Status: Down
Compute host: si-overlapped-4 is down.
Storage host is down.
si-overlapped-4
OSDs to Remove IDs: osd.3
Flushing OSDs.........  NOTE:  This May Take A While
OSD Decommission initiated.
Removing OSDs 3
removed item id 3 name 'osd.3' from crush map
updated
stop down osd.3.
marked out osd.3.
removed osd.3
VMsquared:vmsquared\dashboard>

Once the process has completed the node can be safely powered off and removed from the cluster.