Most of them are outdated, but provide historical design context.
They are not user documentation and should not be treated as such.
Documentation is available here.
Cluster maintenance scheduling policy
There are situations where it is necessary to limit the amount of newly started virtual machines. For example a maintenance window that only affects some hosts and limits the overall capacity of the cluster.
So we decided to implement a simple scheduling policy that would disallow starting of new virtual machines, while still maintaining the already running ones. This is especially important for highly available VMs.
Owner
- Feature Owner: Martin Sivák
- Email: msivak@redhat.com
Current status
- Available in oVirt 4.1.4 and higher
What it does and does not do
- no user can start new virtual machine
- with the exception of VMs marked as highly available
- migration is not blocked in any way
- balancing is set to Equally balanced
How do I put cluster to maintenance
Select the cluster, click edit and select cluster_maintenance scheduling policy from the dropdown.
How do I quit the maintenance mode
Just edit the cluster again and select any other scheduling policy.
What if I need power saving or equal VM count based maintenance policy?
The functionality is provided by ClusterInMaintenance policy unit so just clone the Power saving scheduling policy and enable the ClusterInMaintenance unit in the clone.
