Red Hat Training

A Red Hat training course is available for Red Hat Virtualization

2.2. Deploying the Self-Hosted Engine Using the Command Line

You can deploy a self-hosted engine from the command line using hosted-engine --deploy to collect the details of your environment.

Note

If necessary, you can still use the non-Ansible script from previous versions of Red Hat Virtualization by running hosted-engine --deploy --noansible.

Prerequisites

  • A fresh installation of Red Hat Virtualization Host or Red Hat Enterprise Linux 7, with the required repositories enabled. See Installing Red Hat Virtualization Host or Enabling the Red Hat Enterprise Linux Host Repositories in the Installation Guide.
  • A fully qualified domain name prepared for your Manager and the host. Forward and reverse lookup records must both be set in the DNS.
  • A directory of at least 5 GB on the host, for the RHV-M Appliance. The deployment process will check if /var/tmp has enough space to extract the appliance files. If not, you can specify a different directory or mount external storage. The VDSM user and KVM group must have read, write, and execute permissions on the directory.
  • Prepared storage for a data storage domain dedicated to the Manager virtual machine. This storage domain is created during the self-hosted engine deployment, and must be at least 74 GiB. Highly available storage is recommended. For more information on preparing storage for your deployment, see the Storage chapter of the Administration Guide.

  • Prepared storage for additional storage domains, as necessary for the size and design of your environment.

    Important

    If you are using iSCSI storage, the self-hosted engine storage domain must use its own iSCSI target. Any additional storage domains must use a different iSCSI target.

    Warning

    Creating additional data storage domains in the same data center as the self-hosted engine storage domain is highly recommended. If you deploy the self-hosted engine in a data center with only one active data storage domain, and that storage domain is corrupted, you will not be able to add new storage domains or remove the corrupted storage domain; you will have to redeploy the self-hosted engine.

Procedure

  1. Install the deployment tool: 

    # yum install ovirt-hosted-engine-setup

  2. Red Hat recommends using the screen window manager to run the script to avoid losing the session in case of network or terminal disruption. Install and start screen: 

    # yum install screen
# screen

  3. Start the deployment script: 

    # hosted-engine --deploy
    Note

    To escape the script at any time, use the Ctrl+D keyboard combination to abort deployment. In the event of session timeout or connection disruption, run screen -d -r to recover the deployment session.

  4. Select Yes to begin the deployment: 

    Continuing will configure this host for serving as hypervisor and create a local VM with a running engine.
The locally running engine will be used to configure a storage domain and create a VM there.
At the end the disk of the local VM will be moved to the shared storage.
Are you sure you want to continue? (Yes, No)[Yes]:

  5. Configure the network. The script detects possible NICs to use as a management bridge for the environment. 

    Please indicate a pingable gateway IP address [X.X.X.X]:
Please indicate a nic to set ovirtmgmt bridge on: (eth1, eth0) [eth1]:

  6. If you want to use a custom appliance for the virtual machine installation, enter the path to the OVA archive. Otherwise, leave this field empty to use the RHV-M Appliance. 

    If you want to deploy with a custom engine appliance image,
please specify the path to the OVA archive you would like to use
(leave it empty to skip, the setup will use rhvm-appliance rpm installing it if missing):

  7. Specify the FQDN for the Manager virtual machine: 

    Please provide the FQDN you would like to use for the engine appliance.
Note: This will be the FQDN of the engine VM you are now going to launch,
it should not point to the base host or to any other existing machine.
Engine VM FQDN:  manager.example.com
Please provide the domain name you would like to use for the engine appliance.
Engine VM domain: [example.com]

  8. Enter the root password for the Manager: 

    Enter root password that will be used for the engine appliance:
Confirm appliance root password:

  9. Enter an SSH public key that will allow you to log in to the Manager as the root user, and specify whether to enable SSH access for the root user: 

    Enter ssh public key for the root user that will be used for the engine appliance (leave it empty to skip):
Do you want to enable ssh access for the root user (yes, no, without-password) [yes]:

  10. Enter the virtual machine’s CPU and memory configuration: 

    Please specify the number of virtual CPUs for the VM (Defaults to appliance OVF value): [4]:
Please specify the memory size of the VM in MB (Defaults to maximum available): [7267]:

  11. Enter a MAC address for the Manager virtual machine, or accept a randomly generated one. If you want to provide the Manager virtual machine with an IP address via DHCP, ensure that you have a valid DHCP reservation for this MAC address. The deployment script will not configure the DHCP server for you. 

    You may specify a unicast MAC address for the VM or accept a randomly generated default [00:16:3e:3d:34:47]:

  12. Enter the virtual machine’s networking details: 

    How should the engine VM network be configured (DHCP, Static)[DHCP]?

    If you specified Static, enter the IP address of the Manager:

    Important

    The static IP address must belong to the same subnet as the host. For example, if the host is in 10.1.1.0/24, the Manager virtual machine’s IP must be in the same subnet range (10.1.1.1-254/24). 

    Please enter the IP address to be used for the engine VM [x.x.x.x]:
Please provide a comma-separated list (max 3) of IP addresses of domain name servers for the engine VM
Engine VM DNS (leave it empty to skip):

  13. Specify whether to add entries for the Manager virtual machine and the base host to the virtual machine’s /etc/hosts file. You must ensure that the host names are resolvable. 

    Add lines for the appliance itself and for this host to /etc/hosts on the engine VM?
Note: ensuring that this host could resolve the engine VM hostname is still up to you (Yes, No)[No]

  14. Provide the name and TCP port number of the SMTP server, the email address used to send email notifications, and a comma-separated list of email addresses to receive these notifications: 

    Please provide the name of the SMTP server through which we will send notifications [localhost]:
Please provide the TCP port number of the SMTP server [25]:
Please provide the email address from which notifications will be sent [root@localhost]:
Please provide a comma-separated list of email addresses which will get notifications [root@localhost]:

  15. Enter a password for the admin@internal user to access the Administration Portal: 

    Enter engine admin password:
Confirm engine admin password:

    The script creates the virtual machine. This can take some time if it needs to install the RHV-M Appliance.

  16. Select the type of storage to use: 

    Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]:

    • For NFS, enter the version, full address and path to the storage, and any mount options: 

      Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]:
Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/nfs
If needed, specify additional mount options for the connection to the hosted-engine storage domain []:

    • For iSCSI, enter the portal details and select a target and LUN from the auto-detected lists. You can only select one iSCSI target during the deployment, but multipathing is supported to connect all portals of the same portal group.

      Note

      To specify more than one iSCSI target, you must enable multipathing before deploying the self-hosted engine. See Red Hat Enterprise Linux DM Multipath for details. There is also a Multipath Helper tool that generates a script to install and configure multipath with different options. 

      Please specify the iSCSI portal IP address:
Please specify the iSCSI portal port [3260]:
Please specify the iSCSI discover user:
Please specify the iSCSI discover password:
Please specify the iSCSI portal login user:
Please specify the iSCSI portal login password:

The following targets have been found:
	[1]	iqn.2017-10.com.redhat.example:he
		TPGT: 1, portals:
			192.168.1.xxx:3260
			192.168.2.xxx:3260
			192.168.3.xxx:3260

Please select a target (1) [1]: 1

The following luns have been found on the requested target:
  [1] 360003ff44dc75adcb5046390a16b4beb   199GiB  MSFT   Virtual HD
      status: free, paths: 1 active

Please select the destination LUN (1) [1]:

    • For Gluster storage, enter the full address and path to the storage, and any mount options:

      Important

      Only replica 3 Gluster storage is supported. Ensure you have the following configuration:

      • In the /etc/glusterfs/glusterd.vol file on all three Gluster servers, set rpc-auth-allow-insecure to on. 

        option rpc-auth-allow-insecure on

      • Configure the volume as follows: 

        gluster volume set _volume_ cluster.quorum-type auto
gluster volume set _volume_ network.ping-timeout 10
gluster volume set _volume_ auth.allow \*
gluster volume set _volume_ group virt
gluster volume set _volume_ storage.owner-uid 36
gluster volume set _volume_ storage.owner-gid 36
gluster volume set _volume_ server.allow-insecure on
      Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/gluster_volume
If needed, specify additional mount options for the connection to the hosted-engine storage domain []:

    • For Fibre Channel, select a LUN from the auto-detected list. The host bus adapters must be configured and connected, and the LUN must not contain any existing data. To reuse an existing LUN, see Reusing LUNs in the Administration Guide. 

      The following luns have been found on the requested target:
[1] 3514f0c5447600351   30GiB   XtremIO XtremApp
		status: used, paths: 2 active

[2] 3514f0c5447600352   30GiB   XtremIO XtremApp
		status: used, paths: 2 active

Please select the destination LUN (1, 2) [1]:

  17. Enter the Manager disk size: 

    Please specify the size of the VM disk in GB: [50]:

    When the deployment completes successfully, one data center, cluster, host, storage domain, and the Manager virtual machine are already running. You can log in to the Administration Portal to add any other resources.

  18. Enable the required repositories on the Manager virtual machine. See Enabling the Red Hat Virtualization Manager Repositories in the Installation Guide.
  19. Optionally, add a directory server using the ovirt-engine-extension-aaa-ldap-setup interactive setup script so you can add additional users to the environment. For more information, see Configuring an External LDAP Provider in the Administration Guide.

The Manager virtual machine, the host running it, and the self-hosted engine storage domain are flagged with a gold crown in the Administration Portal.