Self-Hosted Engine

In Oracle Linux Virtualization Manager, a self-hosted engine is a virtualized environment where the engine runs inside a virtual machine on the hosts in the environment. The virtual machine for the engine is created as part of the host configuration process. And, the engine is installed and configured in parallel to the host configuration.

Since the engine runs as a virtual machine and not on physical hardware, a self-hosted engine requires less physical resources. Additionally, since the engine is configured to be highly available, if the host running the Engine virtual machine goes into maintenance mode or fails unexpectedly the virtual machine is migrated automatically to another host in the environment. A minimum of two self-hosted Engine hosts are required to support the high availability.

You use the oVirt Engine Virtual Appliance to install the engine virtual machine. The appliance is installed during the deployment process; however, you can install the appliance on the host before starting the deployment if required:

# dnf install ovirt-engine-appliance

If you plan to use bonded interfaces for high availability or VLANs to separate different types of traffic (for example, for storage or management connections), you should configure these interfaces before deployment.

If you want to customize the engine virtual machine, you can use a custom cloud-init script with the appliance. You can generate a default cloud-init script during deployment and customize as needed.

To deploy a self-hosted engine, see Self-Hosted Engine Deployment in the Oracle Linux Virtualization Manager: Getting Started Guide.

Note:

To review conceptual information, troubleshooting, and administration tasks, see the oVirt Self-Hosted Engine Guide in oVirt Documentation.