Self-Hosted Engine Prerequisites

In addition to the Requirements and Scalability Limits, you must satisfy the following prerequisites before deploying a self-hosted engine.

  • A minimum of two (2) KVM hosts and no more than seven (7).

  • A fully-qualified domain name for the engine and host with forward and reverse lookup records set in the DNS.

  • A directory of at least 5 GB on the host for the oVirt Engine Appliance. During the deployment process the /var/tmp directory is checked to see if it has enough space to extract the appliance files. If the /var/tmp directory doesn't have enough space, you can specify a different directory or mount external storage.

    Note:

    The VDSM user and KVM group must have read, write, and execute permissions on the directory.

  • Prepared storage of at least 74 GB to be used as a data storage domain dedicated to the engine virtual machine. The data storage domain is created during the self-hosted engine deployment.

    If you're using iSCSI storage, don't use the same iSCSI target for the self-hosted engine storage domain and any other storage domains.

    Caution:

    When you have a data center with only one active data storage domain and that domain gets corrupted, you're unable to add new data storage domains or remove the corrupted data storage domain. If you have deployed the self-hosted engine in such a data center and its data storage domain gets corrupted, you must redeploy the self-hosted engine.

  • Ensure that the host you're using to deploy a self-hosted engine can access yum.oracle.com.