Skip to content

Retiring a KVM host

Retire takes an active host of a cluster out of service: its VMs are moved to the other hosts, it leaves OpenNebula, the server is shut down and the host is marked retired. Super admins retire hosts.

Before you start

  • The host is active and in a cluster, and another host of that cluster is enabled.
  • Every VM on the host is running or powered off, and each fits on one other enabled host of the cluster.
  • The host's iLO answers.

Starting the run

  1. Open the site in Infrastructure, tab Hosts, select the host and press Retire. A page opens that reads OpenNebula.
  2. When the host has local storage, the page lists in red what is deleted with no way to restore it: the datastores on that storage, the images in them, and every VM with a disk there (on any host). These VMs cannot be moved off it.
  3. Tick the deletion (when there is anything to delete) and type the host's name.

What the run does

The run is shown step by step on the host:

Step What happens
R0 Checks: the host is in OpenNebula and in its cluster, another host of the cluster is enabled, every VM is running or powered off and fits on one other enabled host, the iLO answers, the local storage is what was confirmed and no other platform's datastore uses it. Nothing changes if a check fails.
R1 The host is disabled in OpenNebula.
R1a The confirmed VMs on the local storage are deleted, each read again just before; a VM no longer there stops the run.
R2 The other VMs are moved one at a time to the enabled host with the most free memory: running ones live, powered-off ones cold. The run stops at the first VM that does not move.
R3 No VM is left on the host.
R3a, R3b The images and then the datastores on the local storage are deleted.
R4 The host is deleted from OpenNebula.
R5 The server is shut down through its iLO (forced after 10 minutes), only while the host is not in OpenNebula again and no datastore uses its storage.
R6 The host is marked retired, its storage retired and its local datastore records removed.

When a step fails

A failed run is continued with Resume (from the failed step) or given up with Abandon. Once a run has begun deleting, only its own Resume continues it; the host shows what it was confirmed to delete.

The last run folds under its heading in the host's details, open while it runs or after it failed. Its log shows only what the steps do not, such as each VM moved.

All the details: Portal reference, Deploying and retiring hosts.