Red Hat Training
A Red Hat training course is available for Red Hat Virtualization
Chapter 1. Introduction
A self-hosted engine is a virtualized environment in which the Red Hat Virtualization Manager, or engine, runs on a virtual machine on the hosts managed by that Manager. The virtual machine is created as part of the host configuration, and the Manager is installed and configured in parallel to the host configuration process. The primary benefit of the self-hosted engine is that it requires less hardware to deploy an instance of Red Hat Virtualization as the Manager runs as a virtual machine, not on physical hardware. Additionally, the Manager is configured to be highly available. If the host running the Manager virtual machine goes into maintenance mode, or fails unexpectedly, the virtual machine is migrated automatically to another host in the environment. Hosts that can run the Manager virtual machine are referred to as self-hosted engine nodes. At least two self-hosted engine nodes are required to support the high availability feature.
For the Manager virtual machine installation, a RHV-M Virtual Appliance is provided. Manually installing the Manager virtual machine is not supported. To customize the Manager virtual machine, you can use a custom cloud-init script with the appliance. Creating custom cloud-init scripts is currently outside the scope of this documentation. A default cloud-init script can be generated during the deployment.
Table 1.1. Supported OS versions to Deploy Self-Hosted Engine
|
System Type
|
Supported Versions
|
|---|---|
|
Red Hat Enterprise Linux host
|
7.2 or later
|
|
Red Hat Virtualization Host
|
7.2 or later
|
|
HostedEngine-VM (Manager)
|
7
|
For hardware requirements, see Hypervisor Requirements in the Installation Guide.
Important
It is important to synchronize the system clocks of the hosts, Manager, and other servers in the environment to avoid potential timing or authentication issues. To do this, configure the Network Time Protocol (NTP) on each system to synchronize with the same NTP server.
The following diagram illustrates the self-hosted engine deployment workflow:
