2.3. Deploying the Self-Hosted Engine
hosted-engine --deployor the Cockpit user interface, you are asked a series of questions to configure the host and Manager virtual machine. The fields in the deployment script are pre-populated with a default answer if one is available; change or enter your answers as necessary.
Procedure 2.4. Deloying the Self-hosted Engine
Beginning DeploymentSelectto begin the deployment.
During customization use CTRL-D to abort. Continuing will configure this host for serving as hypervisor and create a VM where you have to install the engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]:
Downloading the RHV-M Virtual ApplianceIf you have not manually downloaded the RHV-M Virtual Appliance, you can download and install it during deployment. Selectto download the appliance.
The oVirt engine appliance is now required to deploy hosted-engine. You could get oVirt engine appliance installing ovirt-engine-appliance rpm. Do you want to install ovirt-engine-appliance rpm? (Yes, No) [Yes]:
Configuring StorageSelect the type of storage to use.
Please specify the storage you would like to use (glusterfs, iscsi, fc, 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. You can only select one iSCSI target during the deployment.
Please specify the iSCSI portal IP address: Please specify the iSCSI portal port : Please specify the iSCSI portal user: Please specify the iSCSI portal password: Please specify the target name (auto-detected values) [default]:
- For Gluster storage, specify the full address, using either the FQDN or IP address, and path name of the shared storage domain.
ImportantOnly replica 3 Gluster storage is supported. Ensure the following configuration has been made:
- In the
/etc/glusterfs/glusterd.volfile on all three Gluster servers, set
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
- For Fibre Channel, the host bus adapters must be configured and connected, and the
hosted-enginescript will auto-detect the LUNs available. The LUNs must not contain any existing data.
The following luns have been found on the requested target:  3514f0c5447600351 30GiB XtremIO XtremApp status: used, paths: 2 active  3514f0c5447600352 30GiB XtremIO XtremApp status: used, paths: 2 active Please select the destination LUN (1, 2) :
Configuring the NetworkThe deployment detects possible network interface controllers (NICs) to use as a management bridge for the environment.
iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]:
Please indicate a nic to set ovirtmgmt bridge on: (eth1, eth0) [eth1]:
Please indicate a pingable gateway IP address [X.X.X.X]:
Configuring the Virtual MachineThe script will automatically detect the RHV-M Virtual Appliances available; select the appropriate appliance.
The following appliance have been found on your system:  - The oVirt Engine Appliance image (OVA)  - Directly select an OVA file Please select an appliance (1, 2) :Select theor console type to connect to the virtual machine.
Please specify the console type you would like to use to connect to the VM (vnc, spice) [vnc]:Specify
Yesif you want cloud-init to perform the initial configuration of the Manager virtual machine. Specify for cloud-init to performs tasks like setting the root password, configuring networking, configuring the host name, injecting an answers file for
engine-setupto use, and running
engine-setupon boot. Optionally, select if you have an existing cloud-init script to take care of more sophisticated functions of cloud-init.
Would you like to use cloud-init to customize the appliance on the first boot (Yes, No)[Yes]?
Would you like to generate on-fly a cloud-init ISO image (of no-cloud type) or do you have an existing one (Generate, Existing)[Generate]?
NoteFor more information on cloud-init, see https://cloudinit.readthedocs.org/en/latest/.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: (leave it empty to skip): manager.example.comSpecify the domain name to use for the Manager if different from the default.
Please provide the domain name you would like to use for the engine appliance. Engine VM domain: [domain.example.com]Specify whether to automatically execute
engine-setupwhen the Manager first boots, and to restart the Manager virtual machine as a monitored service.
ImportantIf you select No you still have the option of running
engine-setup --accept-defaultsto automatically accept all questions that have default answers. This option should be used with caution and only if you are familiar with engine-setup.
Automatically execute engine-setup on the engine appliance on first boot (Yes, No)[Yes]?
Automatically restart the engine VM as a monitored service after engine-setup (Yes, No)[Yes]?Enter the root password for the Manager.
Enter root password that will be used for the engine appliance (leave it empty to skip): p@ssw0rd
Confirm appliance root password: p@ssw0rdEnter an SSH public key that will allow you to later 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): ssh-rsa AAAAB3NzaBlyc2EAAAADAQABAAABAQDN79V0/3Y3R0iyoCvu7fbw0Mtggm7tHb76yMA4asmU2DBk7ql3AguTNAK9p7Hkc1FANjXGvAZh2vBk+OFN51F/mqe4mgWM1CrpJcsM5ouReT+HkJpMb2f8tU14ZGVRuB/JYfwzsXhs6Jx6Nhh810yqlduTODRDhR9tOtvmtv4cb5VoJhlpppsQOkVxGfB7fPRVucw5PMAUJDwFsOqvtqjuvbGniMYvSZwhv7Nw5Su8WOpMnyr3WfUfDdIAWli5rk4hBHWRZC4zbRsZK03V8wua3PZE0sX3iNvJy4g/s5ynwLytTz7zPXjdyTsYm7BMX8IDhariXY10cYso+fIfjyjf email@example.com
Do you want to enable ssh access for the root user (yes, no, without-password) [yes]:Specify the Manager disk size and memory size.
Please specify the size of the VM disk in GB: :
Please specify the memory size of the VM in MB (Defaults to appliance OVF value): :Specify the CPU type to be used by the Manager and the number of virtual CPUs to use.
The following CPU types are supported by this host: - model_SandyBridge: Intel SandyBridge Family - model_Westmere: Intel Westmere Family - model_Nehalem: Intel Nehalem Family - model_Penryn: Intel Penryn Family - model_Conroe: Intel Conroe Family Please specify the CPU type to be used by the VM [model_SandyBridge]:
Please specify the number of virtual CPUs for the VM [Defaults to appliance OVF value: 4]:Specify a MAC address for the Manager virtual machine, or accept a randomly generated one. The MAC address can be used to update your DHCP and DNS server before installing the operating system on the virtual machine. If you want to provide the Manager virtual machine with an IP address via DHCP, ensure that you have a valid DHCP reservation for that MAC address. The deployment script will not configure the DHCP server for you.
You may specify a MAC address for the VM or accept a randomly generated default [00:16:3e:77:b2:a4]:Specify the networking details of the virtual machine.
How should the engine VM network be configured (DHCP, Static)[DHCP]?If you specified Static, enter the IP address of the Manager.
ImportantThe 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 (10.1.1.1-254/24).
Please enter the IP address to be used for the engine VM [10.x.x.x]:
Please provide a comma-separated list (max3) of IP addresses of domain name servers for the engine VM Engine VM DNS (leave it empty to skip):
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]
Configuring the Self-hosted EngineSpecify a password for the
admin@internaluser to access the Administration Portal. 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.
Enter engine admin password: p@ssw0rd
Confirm engine admin password: p@ssw0rd
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 :
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]:
Configuration PreviewBefore proceeding, the configuration values entered are displayed, and prompts for confirmation to proceed with these values.
Please confirm installation settings (Yes, No)[Yes]: YesThe deployment creates the Manager virtual machine, starts the
ovirt-engineand high availability services, and connects the host and shared storage domain to the Manager virtual machine.When the
hosted-enginedeployment completes successfully, the Red Hat Virtualization Manager is configured and running on your host. The Manager has already configured the data center, cluster, host, the Manager virtual machine, and a shared storage domain dedicated to the Manager virtual machine.
ImportantLog in as the admin@internal user to continue configuring the Manager and add further resources. You must create another data domain for the data center to be initialized to host regular virtual machine data, and for the Manager virtual machine to be visible. See Storage in the Administration Guide for different storage options and on how to add a data storage domain.Link your Red Hat Virtualization Manager to a directory server so you can add additional users to the environment. Red Hat Virtualization supports many directory server types; for example, Red Hat Directory Server (RHDS), Red Hat Identity Management (IdM), Active Directory, and many other types. Add a directory server to your environment using the
ovirt-engine-extension-aaa-ldap-setupinteractive setup script. For more information, see Configuring an External LDAP Provider in the Administration Guide.The answers you gave during configuration are saved to a file to help with disaster recovery. If a destination is not specified using the
--generate-answer=<file>argument, the answer file is generated at
Subscribing to the Required EntitlementsSubscribe the Manager virtual machine to the required entitlements. See Subscribing to the Required Entitlements in the Installation Guide for more information.