VMEvict
From The FluidVM Wiki
VMEvict is a feature that will let you quickly bring take a node down for maintenance by live migrating all virtual servers hosted on it using FluidVM's HotMigrate technology. VMEvict will randomly find compute nodes with resource to migrate virtual servers into. If you have more than one potential destination compute nodes, they might all be used.
Factors affecting VMEvict
Resource availability
First of all, there need to be other compute nodes with enough resources in them to accept the exodus of virtual serves from the node on which VMEvict is invoked.
Use of local storage
Secondly, FluidVM will not perform a VMEvict on a compute node even if there is a single virtual server that is using local storage. Virtual servers using the ISO Store are exempt from this rule. If you need to migrate all OpenVZ virtual servers based on local storage to another compute node, then use the mass management feature you can access via the VMSearch pane in the Virtual Cockpit.
VMProtect
If you are running important services on a compute node and do not want to increase load on it by accepting migrations from VMEvict or otherwise, you can protect the node with the VMProtect option. Nodes with this flag set to on, will not participate in VMEvict.
How to initiate VMEvict
VMEvict can be initiated in 2 different ways. On the tree, you can right click on a compute node. This will display a context menu. Select VMEvict from there.
You can also access the VMEvict option via the Home pane of compute nodes. Depending on whether the underlying virtualization technology supports HotMigrate or not, this feature will or will not be available.
