Chapter 8. Installing Additional Hosts to a Self-Hosted Environment

Adding additional hosts to a self-hosted environment is similar to deploying the original self-hosted engine host, but the procedure is simplified, because the script detects the environment. By running the hosted-engine script on the new host, the shared storage domain is detected and the host can be used as a failover host to host the Manager virtual machine when required. You can also attach regular hosts, which are not configured using the hosted-engine script, to a self-hosted engine environment; however, they cannot be used to host the Manager virtual machine. It is highly recommended to have at least two hosted-engine configured hosts to ensure the Manager virtual machine is highly available.

Prerequisites

  • For a RHEL-based self-hosted engine environment, you must have prepared a freshly installed Red Hat Enterprise Linux system on a physical host, and subscribed the host to the required entitlements. See Section 3.1, “Subscribing to the Required Entitlements” for more information on subscriptions.
  • For a RHEV-H-based self-hosted engine environment, you must have prepared a freshly installed RHEV-H on a physical host. Ensure that at least one network card is configured and that SSH password authentication has been enabled from the Security screen.

Procedure 8.1. Adding an Additional Self-Hosted Engine Host

  1. Starting the hosted-engine Script

    • For a RHEL-based self-hosted engine host, install the ovirt-hosted-engine-setup package, and run the deployment command: 
      # yum install ovirt-hosted-engine-setup
      # hosted-engine --deploy
    • For a RHEV-H-based self-hosted engine host, in the text user interface, select the Hosted Engine screen, and select < Deploy Hosted Engine >. Select < Add this host to an existing group >, and select < OK >.

  2. Configuring Storage

    Select the type of storage to use. 
    During customization use CTRL-D to abort.
Please specify the storage you would like to use (iscsi, nfs3, nfs4)[nfs3]:
    • For NFS storage types, specify the full address, using either the FQDN or IP address, and path name of the shared storage domain. 
      Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/nfs
    • For iSCSI, specify the iSCSI portal IP address, port, user name and password, and select a target name from the auto-detected list: 
      Please specify the iSCSI portal IP address:           
Please specify the iSCSI portal port [3260]:           
Please specify the iSCSI portal user:           
Please specify the iSCSI portal password:
Please specify the target name (auto-detected values) [default]:

  3. Detecting the Self-Hosted Engine

    The hosted-engine script detects that the shared storage is being used and asks if this is an additional host setup. You are then prompted for the host ID, which must be an integer not already assigned to an additional host in the environment. 
    The specified storage location already contains a data domain. Is this an additional host setup (Yes, No)[Yes]? 
[ INFO  ] Installing on additional host
Please specify the Host ID [Must be integer, default: 2]:

  4. Configuring the System

    The hosted-engine script uses the answer file generated by the original hosted-engine setup. To achieve this, the script requires the FQDN or IP address and the password of the root user of that host so as to access and secure-copy the answer file to the additional host. 
    [WARNING] A configuration file must be supplied to deploy Hosted Engine on an additional host.
The answer file may be fetched from the first host using scp.
If you do not want to download it automatically you can abort the setup answering no to the following question.
Do you want to scp the answer file from the first host? (Yes, No)[Yes]:       
Please provide the FQDN or IP of the first host:           
Enter 'root' user password for host Host-HE1.example.com: 
[ INFO  ] Answer file successfully downloaded

  5. Configuring the Hosted Engine

    Specify the name for the additional host to be identified in the Red Hat Enterprise Virtualization environment, and the password for the admin@internal user. 
    Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_2]:           
Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: 
Confirm 'admin@internal' user password:

  6. Configuration Preview

    Before proceeding, the hosted-engine script displays the configuration values you have entered, and prompts for confirmation to proceed with these values. 
    Bridge interface                   : eth1
Engine FQDN                        : HostedEngine-VM.example.com
Bridge name                        : rhevm
SSH daemon port                    : 22
Firewall manager                   : iptables
Gateway address                    : X.X.X.X
Host name for web application      : hosted_engine_2
Host ID                            : 2
Image size GB                      : 25
Storage connection                 : storage.example.com:/hosted_engine/nfs
Console type                       : vnc
Memory size MB                     : 4096
MAC address                        : 00:16:3e:05:95:50
Boot type                          : disk
Number of CPUs                     : 2
CPU Type                           : model_Penryn
         
Please confirm installation settings (Yes, No)[Yes]:
After confirmation, the script completes installation of the host and adds it to the environment.