Self-Hosted Engine Guide

Procedure 2.1. Setting Up Self-Hosted Engine on RHEV-H

1. Click Deploy Hosted Engine.
   

   View larger image

   
2. Specify the Red Hat Enterprise Virtualization Manager virtual machine installation method. To install using the RHEV-M Virtual Appliance, enter the URL to the appliance. For example: http://file.domain.com/rhevm-appliance.ova. This is the recommended Manager installation method. Click Deploy, and click Close.
   Alternatively, select PXE Boot Engine VM if PXE installation is the desired installation method.
3. Click OK to start the hosted-engine deployment script. Press Enter to confirm to continue.
   

   View larger image

   

4. 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 (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]:

   Copy to Clipboard Toggle word wrap
   • 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

     Copy to Clipboard Toggle word wrap
   • 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 [3260]:
     Please specify the iSCSI portal user:
     Please specify the iSCSI portal password:
     Please specify the target name (auto-detected values) [default]:

     Copy to Clipboard Toggle word wrap
   • For Gluster storage, specify the full address, using either the FQDN or IP address, and path name of the shared storage domain.

     Important

     Only replica 3 Gluster storage is supported. Ensure the following configuration has been made:

     • 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

       Copy to Clipboard Toggle word wrap
     • 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

       Copy to Clipboard Toggle word wrap

     Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/gluster_volume

     Copy to Clipboard Toggle word wrap
   • For Fibre Channel, the host bus adapters must be configured and connected, and the hosted-engine script will auto-detect the LUNs available. The LUNs must not contain any existing data.

     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]:

     Copy to Clipboard Toggle word wrap
   Choose the storage domain and storage data center names to be used in the environment.

   [ INFO  ] Installing on first host
   Please provide storage domain name. [hosted_storage]:
   Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI.Please enter local datacenter name [hosted_datacenter]:

   Copy to Clipboard Toggle word wrap

5. Configuring the Network

   The script detects possible network interface controllers (NICs) to use as a management bridge for the environment. It then checks your firewall configuration and offers to modify it for console (SPICE or VNC) access.

   Note

   Configuring a bonded and vlan-tagged network interface as the management bridge is currently not supported. To work around this issue, see https://access.redhat.com/solutions/1417783 for more information.

   Please indicate a nic to set rhevm bridge on: (eth1, eth0) [eth1]:
   iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: Yes
   Please indicate a pingable gateway IP address [X.X.X.X]:

   Copy to Clipboard Toggle word wrap

6. Configuring the Virtual Machine

   The script creates a virtual machine to be configured as the Red Hat Enterprise Virtualization Manager.

   Note

   If you want to manually install the Manager virtual machine, see Appendix A, Manually Installing the Manager Operating System to complete the self-hosted engine setup. Using the appliance eases the workflow, because user interaction with the Manager virtual machine is not required. Manual installation allows you to take full control of the installation.

   [ INFO ] Checking OVF archive content (could take a few minutes depending on archive size)
   [ INFO ] Checking OVF XML content (could take a few minutes depending on archive size)
            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 no-cloud ISO image
            or do you have an existing one(Generate, Existing)[Generate]? Generate
            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.com
            Automatically execute engine-setup on the engine appliance on first boot (Yes, No)[Yes]? Yes
            Automatically restart the engine VM as a monitored service after engine-setup (Yes, No)[Yes]? Yes
            Please provide the domain name you would like to use for the engine appliance.
            Engine VM domain: [example.com]
            Enter root password that will be used for the engine appliance (leave it empty to skip): p@ssw0rd
            Confirm appliance root password: p@ssw0rd
            How should the engine VM network be configured (DHCP, Static)[DHCP]? Static
            Please enter the IP address to be used for the engine VM: 192.168.x.x
   [ INFO ] The engine VM will be configured to use 192.168.x.x/24
            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] Yes
            Please specify an alias for the Hosted Engine image [hosted_engine]:
            The following CPU types are supported by this host:
                   - model_Penryn: Intel Penryn Family
                   - model_Conroe: Intel Conroe Family
            Please specify the CPU type to be used by the VM [model_Penryn]:
            Please specify the number of virtual CPUs for the VM [Defaults to appliance OVF value: 4]:
            You may specify a MAC address for the VM or accept a randomly generated default [00:16:3e:77:b2:a4]:
            Please specify the console type you would like to use to connect to the VM (vnc, spice) [vnc]: vnc

   Copy to Clipboard Toggle word wrap

7. Configuring the Hosted Engine

   Specify a name for the hypervisor to be identified in the Red Hat Enterprise Virtualization environment, and the password for the admin@internal user to access the Administration Portal. Provide the FQDN for the Manager virtual machine.

   Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_1]:
   Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: p@ssw0rd
   Confirm 'admin@internal' user 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 [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]:

   Copy to Clipboard Toggle word wrap

8. Configuration Preview

   Before proceeding, the hosted-engine script displays the configuration values you have entered, and prompts for confirmation to proceed with these values.

9. Creating the Manager Virtual Machine

   The script creates the Manager virtual machine, starts the ovirt-engine and high availability services, and connects the hypervisor host and shared storage domain to the Manager virtual machine.

   You can now connect to the VM with the following command:
   	/usr/bin/remote-viewer vnc://localhost:5900
   Use temporary password "3042QHpX" to connect to vnc console.
   Please note that in order to use remote-viewer you need to be able to run graphical applications.
   This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding).
   Otherwise you can run the command from a terminal in your preferred desktop environment.
   If you cannot run graphical applications you can connect to the graphic console from another host or connect to the serial console using the following command:
   socat UNIX-CONNECT:/var/run/ovirt-vmconsole-console/fabbea5a-1989-411f-8ed7-7abe0917fc66.sock,user=ovirt-vmconsole STDIO,raw,echo=0,escape=1
   
   If you need to reboot the VM you will need to start it manually using the command:
   hosted-engine --vm-start
   You can then set a temporary password using the command:
   hosted-engine --add-console-password
   [ INFO ] Running engine-setup on the appliance
   ...
   [ INFO ] Engine-setup successfully completed
   [ INFO ] Engine is still unreachable
   [ INFO ] Engine is still unreachable, waiting...
   [ INFO ] Engine replied: DB Up!Welcome to Health Status!
   [ INFO ] Connecting to the Engine
            Enter the name of the cluster to which you want to add the host (Default) [Default]:
   [ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes... [ INFO  ] Still waiting for VDSM host to become operational...
   [ INFO  ] The VDSM Host is now operational
   [ INFO  ] Shutting down the engine VM
   [ INFO  ] Enabling and starting HA services
   [ INFO  ] Saving hosted-engine configuration on the shared storage domain
             Hosted Engine successfully set up
   [ INFO  ] Stage: Clean up
   [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-2015xx.conf'
   [ INFO  ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
   [ INFO  ] Stage: Pre-termination
   [ INFO  ] Stage: Termination
   
   [screen is terminating]
   Hit <Return> to return to the TUI

   Copy to Clipboard Toggle word wrap

Procedure 3.1. Subscribing to Required Entitlements Using Subscription Manager

1. Register your system with the Content Delivery Network, entering your Customer Portal Username and Password when prompted:

   # subscription-manager register

   Copy to Clipboard Toggle word wrap
2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.

   # subscription-manager list --available

   Copy to Clipboard Toggle word wrap
3. Use the pool identifiers located in the previous step to attach the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization entitlements to the system:

   # subscription-manager attach --pool=poolid

   Copy to Clipboard Toggle word wrap
4. Disable all existing repositories:

   # subscription-manager repos --disable=*

   Copy to Clipboard Toggle word wrap
5. Enable the required repositories for Red Hat Enterprise Linux 7:

   # subscription-manager repos --enable=rhel-7-server-rpms
   # subscription-manager repos --enable=rhel-7-server-rhev-mgmt-agent-rpms
   

   Copy to Clipboard Toggle word wrap
6. Ensure that all packages currently installed are up to date:

   # yum update

   Copy to Clipboard Toggle word wrap

   Note

   Reboot the machine if any kernel related packages have been updated.

Procedure 3.2. Installing the Self-Hosted Engine

1. Install the self-hosted engine packages:

   # yum install ovirt-hosted-engine-setup

   Copy to Clipboard Toggle word wrap
2. Optionally install the RHEV-M Virtual Appliance package if you intend to use the appliance for the Manager virtual machine installation:

   # yum install rhevm-appliance

   Copy to Clipboard Toggle word wrap
   You can also use a CD-ROM, disk, or PXE installation media for the Manager operating system installation. The physical CD-ROM drive is not supported.

Procedure 3.3. Configuring a RHEL-based Self-Hosted Engine

1. Initiating Hosted Engine Deployment

   Run the hosted-engine script. To escape the script at any time, use the CTRL+D keyboard combination to abort deployment. It is recommended to use the screen window manager to run the script to avoid losing the session in case of network or terminal disruption. If not already installed, install the screen package, which is available in the standard Red Hat Enterprise Linux repository.

   # yum install screen

   Copy to Clipboard Toggle word wrap

   # screen

   Copy to Clipboard Toggle word wrap

   # hosted-engine --deploy

   Copy to Clipboard Toggle word wrap

   Note

   In the event of session timeout or connection disruption, run screen -d -r to recover the hosted-engine deployment session.

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 (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]:

   Copy to Clipboard Toggle word wrap
   • 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

     Copy to Clipboard Toggle word wrap
   • 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 [3260]:           
     Please specify the iSCSI portal user:           
     Please specify the iSCSI portal password:
     Please specify the target name (auto-detected values) [default]:

     Copy to Clipboard Toggle word wrap
   • For Gluster storage, specify the full address, using either the FQDN or IP address, and path name of the shared storage domain.

     Important

     Only replica 3 Gluster storage is supported. Ensure the following configuration has been made:

     • 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

       Copy to Clipboard Toggle word wrap
     • 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

       Copy to Clipboard Toggle word wrap

     Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/gluster_volume

     Copy to Clipboard Toggle word wrap
   • For Fibre Channel, the host bus adapters must be configured and connected, and the hosted-engine script will auto-detect the LUNs available. The LUNs must not contain any existing data.

     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]:

     Copy to Clipboard Toggle word wrap
   Choose the storage domain and storage data center names to be used in the environment.

   [ INFO  ] Installing on first host
   Please provide storage domain name. [hosted_storage]: 
   Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI.Please enter local datacenter name [hosted_datacenter]:

   Copy to Clipboard Toggle word wrap

3. Configuring the Network

   The script detects possible network interface controllers (NICs) to use as a management bridge for the environment. It then checks your firewall configuration and offers to modify it for console (SPICE or VNC) access.

   Note

   Configuring a bonded and vlan-tagged network interface as the management bridge is currently not supported. To work around this issue, see https://access.redhat.com/solutions/1417783 for more information.

   Please indicate a nic to set rhevm bridge on: (eth1, eth0) [eth1]:
   iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: Yes
   Please indicate a pingable gateway IP address [X.X.X.X]:

   Copy to Clipboard Toggle word wrap

4. Configuring the Virtual Machine

   Note

   If you want to manually install the Manager virtual machine, see Appendix A, Manually Installing the Manager Operating System to complete the self-hosted engine setup. Using the appliance eases the workflow, because user interaction with the Manager virtual machine is not required. Manual installation allows you to take full control of the installation.
   Select disk for the boot device type, and the script will automatically detect the RHEV-M Appliances available. Specify the memory size.

            Please specify the device to boot the VM from (cdrom, disk, pxe) [disk]: 
   [ INFO ] Detecting available oVirt engine appliances
            The following appliance have been found on your system:
                  [1] - The oVirt Engine Appliance image (OVA)
                  [2] - Directly select an OVA file
            Please select an appliance (1, 2) [1]:
   [ INFO ] Checking OVF archive content (could take a few minutes depending on archive size)
   	       Please specify the memory size of the appliance in MB (Defaults to OVF value: 16384):

   Copy to Clipboard Toggle word wrap
   Specify Yes if you want cloud-init to take care of the initial configuration of the Manager virtual machine. Specify Generate for cloud-init to take care of tasks like setting the root password, configuring networking, configuring the host name, injecting an answers file for engine-setup to use, and running engine-setup on boot. Optionally, select Existing if you have an existing cloud-init script to take care of more sophisticated functions of cloud-init. Specify the FQDN for the Manager virtual machine. Specify a MAC address for the HostedEngine-VM, or accept a randomly generated one. The MAC address can be used to update your DHCP and DNS server prior to installing the operating system on the virtual machine.

   Note

   For more information on cloud-init, see https://cloudinit.readthedocs.org/en/latest/.

   Would you like to use cloud-init to customize the appliance on the first boot (Yes, No)[Yes]? Yes
   Would you like to generate on-fly a cloud-init no-cloud ISO image or do you have an existing one(Generate, Existing)[Generate]? Generate
   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.com
   Automatically execute engine-setup on the engine appliance on first boot (Yes, No)[Yes]? Yes
   Automatically restart the engine VM as a monitored service after engine-setup (Yes, No)[Yes]? Yes
   Please provide the domain name you would like to use for the engine appliance.
   Engine VM domain: [example.com]
   Enter root password that will be used for the engine appliance (leave it empty to skip): p@ssw0rd
   Confirm appliance root password: p@ssw0rd
   How should the engine VM network be configured (DHCP, Static)[DHCP]? Static
   Please enter the IP address to be used for the engine VM: 192.168.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] Yes
   Please specify an alias for the Hosted Engine image [hosted_engine]:
   The following CPU types are supported by this host:
       - model_Penryn: Intel Penryn Family
       - model_Conroe: Intel Conroe Family
   Please specify the CPU type to be used by the VM [model_Penryn]: 
   Please specify the number of virtual CPUs for the VM [Defaults to appliance OVF value: 4]: 
   You may specify a MAC address for the VM or accept a randomly generated default [00:16:3e:77:b2:a4]: 
   Please specify the console type you would like to use to connect to the VM (vnc, spice) [vnc]: vnc

   Copy to Clipboard Toggle word wrap

5. Configuring the Hosted Engine

   Specify a name for hypervisor host to be identified in the Administration Portal, and the password for the admin@internal user 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 the name which will be used to identify this host inside the Administrator Portal [hosted_engine_1]:
   Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: p@ssw0rd
   Confirm 'admin@internal' user 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 [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]:

   Copy to Clipboard Toggle word wrap

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.

7. Creating the Manager Virtual Machine

   The script creates the Manager virtual machine, starts the ovirt-engine and high availability services, and connects the hypervisor host and shared storage domain to the Manager virtual machine.

   You can now connect to the VM with the following command:
   	/usr/bin/remote-viewer vnc://localhost:5900
   Use temporary password "3042QHpX" to connect to vnc console.
   Please note that in order to use remote-viewer you need to be able to run graphical applications.
   This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding).
   Otherwise you can run the command from a terminal in your preferred desktop environment.
   If you cannot run graphical applications you can connect to the graphic console from another host or connect to the serial console using the following command:
   socat UNIX-CONNECT:/var/run/ovirt-vmconsole-console/fabbea5a-1989-411f-8ed7-7abe0917fc66.sock,user=ovirt-vmconsole STDIO,raw,echo=0,escape=1
   
   If you need to reboot the VM you will need to start it manually using the command:
   hosted-engine --vm-start
   You can then set a temporary password using the command:
   hosted-engine --add-console-password
   [ INFO ] Running engine-setup on the appliance
   ...
   [ INFO ] Engine-setup successfully completed
   [ INFO ] Engine is still unreachable
   [ INFO ] Engine is still unreachable, waiting...
   [ INFO ] Engine replied: DB Up!Welcome to Health Status!
   [ INFO ] Connecting to the Engine
            Enter the name of the cluster to which you want to add the host (Default) [Default]:
   [ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes... [ INFO  ] Still waiting for VDSM host to become operational...
   [ INFO  ] The VDSM Host is now operational      
   [ INFO  ] Shutting down the engine VM
   [ INFO  ] Enabling and starting HA services
   [ INFO  ] Saving hosted-engine configuration on the shared storage domain
             Hosted Engine successfully set up
   [ INFO  ] Stage: Clean up
   [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-2015xx.conf'
   [ INFO  ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
   [ INFO  ] Stage: Pre-termination
   [ INFO  ] Stage: Termination

   Copy to Clipboard Toggle word wrap

Procedure 4.1. Troubleshooting the Manager Virtual Machine

1. Check the status of the Manager virtual machine by running hosted-engine --vm-status.

   Note

   Any changes made to the Manager virtual machine will take about 20 seconds before they are reflected in the status command output.

   If the Manager virtual machine is up and running as normal, you will see the following output:

   --== Host 1 status ==--
   
   Status up-to-date              : True
   Hostname                       : hypervisor.example.com
   Host ID                        : 1
   Engine status                  : {"health": "good", "vm": "up", "detail": "up"}
   Score                          : 3400
   stopped                        : False
   Local maintenance              : False
   crc32                          : 99e57eba
   Host timestamp                 : 248542

   Copy to Clipboard Toggle word wrap
2. If the health is bad or the vm is down, enable the global maintenance mode so that the hosts are no longer managed by the HA services.
   • In the Administration Portal, right-click the engine virtual machine, and select Enable Global HA Maintenance.
   • You can also set the maintenance mode from the command line:

     # hosted-engine --set-maintenance --mode=global

     Copy to Clipboard Toggle word wrap
3. If the Manager virtual machine is down, start the Manager virtual machine. If the virtual machine is up, skip this step.

   # hosted-engine ---vm-start

   Copy to Clipboard Toggle word wrap
4. Set the console password:

   # hosted-engine --add-console-password

   Copy to Clipboard Toggle word wrap
5. Connect to the console. When prompted, enter the password set in the previous step. For more console options, see https://access.redhat.com/solutions/2221461.

   # hosted-engine --console

   Copy to Clipboard Toggle word wrap
6. Determine why the Manager virtual machine is down or in a bad health state. Check /var/log/messages and /var/log/ovirt-engine/engine.log. After fixing the issue, reboot the Manager virtual machine.
7. Log in to the Manager virtual machine as root and verfiy that the ovirt-engine service is up and running:

   # service ovirt-engine status

   Copy to Clipboard Toggle word wrap
8. After ensuring the Manager virtual machine is up and running, close the console session and disable the maintenance mode to enable the HA services again:

   # hosted-engine --set-maintenance --mode=none

   Copy to Clipboard Toggle word wrap

Procedure 5.1. Migrating to a Self-Hosted Environment

1. Initiating a Self-Hosted Engine Deployment

   Note

   If your original installation was version 3.5 or earlier, and the current name of the management network is rhevm, you must modify the answer file prior to running hosted-engine --deploy. For more information, see https://access.redhat.com/solutions/2292861.
   Run the hosted-engine script. To escape the script at any time, use the CTRL+D keyboard combination to abort deployment. It is recommended to use the screen window manager to run the script to avoid losing the session in case of network or terminal disruption. If not already installed, install the screen package, which is available in the standard Red Hat Enterprise Linux repository.

   # yum install screen

   Copy to Clipboard Toggle word wrap

   # screen

   Copy to Clipboard Toggle word wrap

   # hosted-engine --deploy

   Copy to Clipboard Toggle word wrap

   Note

   In the event of session timeout or connection disruption, run screen -d -r to recover the hosted-engine deployment session.

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 (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]:

   Copy to Clipboard Toggle word wrap
   • 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

     Copy to Clipboard Toggle word wrap
   • 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 [3260]:           
     Please specify the iSCSI portal user:           
     Please specify the iSCSI portal password:
     Please specify the target name (auto-detected values) [default]:

     Copy to Clipboard Toggle word wrap
   • For Gluster storage, specify the full address, using either the FQDN or IP address, and path name of the shared storage domain.

     Important

     Only replica 3 Gluster storage is supported. Ensure the following configuration has been made:

     • 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

       Copy to Clipboard Toggle word wrap
     • 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

       Copy to Clipboard Toggle word wrap

     Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/gluster_volume

     Copy to Clipboard Toggle word wrap
   • For Fibre Channel, the host bus adapters must be configured and connected, and the hosted-engine script will auto-detect the LUNs available. The LUNs must not contain any existing data.

     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]:

     Copy to Clipboard Toggle word wrap
   Choose the storage domain and storage data center names to be used in the environment.

   [ INFO  ] Installing on first host
   Please provide storage domain name. [hosted_storage]: 
   Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI.Please enter local datacenter name [hosted_datacenter]:

   Copy to Clipboard Toggle word wrap

3. Configuring the Network

   The script detects possible network interface controllers (NICs) to use as a management bridge for the environment. It then checks your firewall configuration and offers to modify it for console (SPICE or VNC) access HostedEngine-VM. Provide a pingable gateway IP address, to be used by the ovirt-ha-agent to help determine a host's suitability for running HostedEngine-VM.

   Please indicate a nic to set rhevm bridge on: (eth1, eth0) [eth1]:
   iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: 
   Please indicate a pingable gateway IP address [X.X.X.X]:

   Copy to Clipboard Toggle word wrap

4. Configuring the Virtual Machine

   The script creates a virtual machine to be configured as the Red Hat Enterprise Virtualization Manager, referred to in this procedure as HostedEngine-VM. Specify the boot device and, if applicable, the path name of the installation media, the CPU type, the number of virtual CPUs, and the disk size. Specify a MAC address for the HostedEngine-VM, or accept a randomly generated one. The MAC address can be used to update your DHCP server prior to installing the operating system on the virtual machine. Specify memory size and console connection type for the creation of HostedEngine-VM.

   Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]: 
   The following CPU types are supported by this host:
             - model_Penryn: Intel Penryn Family
             - model_Conroe: Intel Conroe Family
   Please specify the CPU type to be used by the VM [model_Penryn]: 
   Please specify the number of virtual CPUs for the VM [Defaults to minimum requirement: 2]: 
   Please specify the disk size of the VM in GB [Defaults to minimum requirement: 25]: 
   You may specify a MAC address for the VM or accept a randomly generated default [00:16:3e:77:b2:a4]: 
   Please specify the memory size of the VM in MB [Defaults to minimum requirement: 4096]: 
   Please specify the console type you want to use to connect to the VM (vnc, spice) [vnc]:

   Copy to Clipboard Toggle word wrap

5. Configuring the Self-Hosted Engine

   Specify the name for Host-HE1 to be identified in the Red Hat Enterprise Virtualization environment, and the password for the admin@internal user to access the Administration Portal. Provide the FQDN for HostedEngine-VM; this procedure uses the FQDN manager.example.com. Finally, 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.

   Important

   The FQDN provided for the engine must be the same FQDN provided for the BareMetal-Manager.

   Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_1]: Host-HE1
   Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: 
   Confirm 'admin@internal' user password: 
   Please provide the FQDN for the engine you want to use. This needs to match the FQDN that you will use for the engine installation within the VM: manager.example.com
   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]:

   Copy to Clipboard Toggle word wrap

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                        : manager.example.com
   Bridge name                        : rhevm
   SSH daemon port                    : 22
   Firewall manager                   : iptables
   Gateway address                    : X.X.X.X
   Host name for web application      : Host-HE1
   Host ID                            : 1
   Image size GB                      : 25
   Storage connection                 : storage.example.com:/hosted_engine/nfs
   Console type                       : vnc
   Memory size MB                     : 4096
   MAC address                        : 00:16:3e:77:b2:a4
   Boot type                          : pxe
   Number of CPUs                     : 2
   CPU Type                           : model_Penryn
   
   Please confirm installation settings (Yes, No)[No]:

   Copy to Clipboard Toggle word wrap

7. Creating HostedEngine-VM

   The script creates the virtual machine to be configured as HostedEngine-VM and provides connection details. You must install an operating system on HostedEngine-VM before the hosted-engine script can proceed on Host-HE1.

   [ INFO  ] Stage: Transaction setup
   ...
   [ INFO  ] Creating VM
   You can now connect to the VM with the following command:
   	/usr/bin/remote-viewer vnc://localhost:5900
   Use temporary password "5379skAb" to connect to vnc console.
   Please note that in order to use remote-viewer you need to be able to run graphical applications.
   This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding).
   Otherwise you can run the command from a terminal in your preferred desktop environment.
   If you cannot run graphical applications you can connect to the graphic console from another host or connect to the console using the following command:
   virsh -c qemu+tls://Test/system console HostedEngine
   If you need to reboot the VM you will need to start it manually using the command:
   hosted-engine --vm-start
   You can then set a temporary password using the command:
   hosted-engine --add-console-password
   The VM has been started.  Install the OS and shut down or reboot it.  To continue please make a selection:
            
             (1) Continue setup - VM installation is complete
             (2) Reboot the VM and restart installation
             (3) Abort setup
             (4) Destroy VM and abort setup
            
             (1, 2, 3, 4)[1]:

   Copy to Clipboard Toggle word wrap
   Connect to the virtual machine using the VNC protocol with the following command. Replace FQDN wit the fully qualified domain name or the IP address of the self-hosted engine host.

   /usr/bin/remote-viewer vnc://FQDN:5900

   Copy to Clipboard Toggle word wrap

8. Installing the Virtual Machine Operating System

   Connect to HostedEngine-VM, the virtual machine created by the hosted-engine script, and install a Red Hat Enterprise Linux 6.7 operating system.

9. Synchronizing the Host and the Virtual Machine

   Return to Host-HE1 and continue the hosted-engine deployment script by selecting option 1:

   (1) Continue setup - VM installation is complete

   Copy to Clipboard Toggle word wrap

10. Installing the Manager

    Connect to HostedEngine-VM, and subscribe to the appropriate Red Hat Enterprise Virtualization Manager repositories. See Subscribing to the Required Entitlements in the Installation Guide.
    Ensure that the most up-to-date versions of all installed packages are in use, and install the rhevm packages.

    # yum update

    Copy to Clipboard Toggle word wrap

    # yum install rhevm

    Copy to Clipboard Toggle word wrap

11. Disabling BareMetal-Manager

    Connect to BareMetal-Manager, the Manager of your established Red Hat Enterprise Virtualization environment, and stop the engine and prevent it from running.

    # service ovirt-engine stop
    # chkconfig ovirt-engine off

    Copy to Clipboard Toggle word wrap

    Note

    Though stopping BareMetal-Manager from running is not obligatory, it is recommended as it ensures no changes will be made to the environment after the backup has been created. Additionally, it prevents BareMetal-Manager and HostedEngine-VM from simultaneously managing existing resources.

12. Updating DNS

    Update your DNS so that the FQDN of the Red Hat Enterprise Virtualization environment correlates to the IP address of HostedEngine-VM and the FQDN previously provided when configuring the hosted-engine deployment script on Host-HE1. In this procedure, FQDN was set as manager.example.com because in a migrated hosted-engine setup, the FQDN provided for the engine must be identical to that given in the engine setup of the original engine.

13. Creating a Backup of BareMetal-Manager

    1. Ensure that the management network (ovirtmgmt)is configured as a VM network prior to performing the backup. For more information on configuring networks, see Explanation of Settings and Controls in the New Logical Network and Edit Logical Network Windows in the Administration Guide.
    2. Connect to BareMetal-Manager and run the engine-backup command with the --mode=backup, --file=FILE, and --log=LogFILE parameters to specify the backup mode, the name of the backup file created and used for the backup, and the name of the log file to be created to store the backup log.

       # engine-backup --mode=backup --file=FILE --log=LogFILE

       Copy to Clipboard Toggle word wrap

14. Copying the Backup File to HostedEngine-VM

    On BareMetal-Manager, secure copy the backup file to HostedEngine-VM. In the following example, [manager.example.com] is the FQDN for HostedEngine-VM, and /backup/ is any designated folder or path. If the designated folder or path does not exist, you must connect to HostedEngine-VM and create it before secure copying the backup from BareMetal-Manager.

    # scp -p FILE LogFILE manager.example.com:/backup/

    Copy to Clipboard Toggle word wrap

15. Restoring the Backup File on HostedEngine-VM

    Use the engine-backup tool to restore a complete backup. If you configured the BareMetal-Manager database(s) manually during engine-setup, follow the instructions at Section 7.2.3, “Restoring the Self-Hosted Engine Manager Manually” to restore the backup environment manually.
    • If you are only restoring the Manager, run:

      # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --restore-permissions

      Copy to Clipboard Toggle word wrap
    • If you are restoring the Manager, Reports, and Data Warehouse, run:

      # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --provision-dwh-db --provision-reports-db --restore-permissions

      Copy to Clipboard Toggle word wrap
    If successful, the following output displays:

    You should now run engine-setup.
    Done.

    Copy to Clipboard Toggle word wrap

16. Configuring HostedEngine-VM

    Configure the restored Manager virtual machine. This process identifies the existing configuration settings and database content. Confirm the settings. Upon completion, the setup provides an SSH fingerprint and an internal Certificate Authority hash.

    # engine-setup

    Copy to Clipboard Toggle word wrap

    [ INFO  ] Stage: Initializing
    [ INFO  ] Stage: Environment setup
    Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
    Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140304075238.log
    Version: otopi-1.1.2 (otopi-1.1.2-1.el6ev)
    [ INFO  ] Stage: Environment packages setup
    [ INFO  ] Yum Downloading: rhel-65-zstream/primary_db 2.8 M(70%)
    [ INFO  ] Stage: Programs detection
    [ INFO  ] Stage: Environment setup
    [ INFO  ] Stage: Environment customization
             
              --== PACKAGES ==--
             
    [ INFO  ] Checking for product updates...
    [ INFO  ] No product updates found
             
              --== NETWORK CONFIGURATION ==--
             
    Setup can automatically configure the firewall on this system.
    Note: automatic configuration of the firewall may overwrite current settings.
    Do you want Setup to configure the firewall? (Yes, No) [Yes]: 
    [ INFO  ] iptables will be configured as firewall manager.
             
              --== DATABASE CONFIGURATION ==--
             
             
              --== OVIRT ENGINE CONFIGURATION ==--
             
             
              --== PKI CONFIGURATION ==--
             
             
              --== APACHE CONFIGURATION ==--
             
             
              --== SYSTEM CONFIGURATION ==--
             
             
              --== END OF CONFIGURATION ==--
             
    [ INFO  ] Stage: Setup validation
    [ INFO  ] Cleaning stale zombie tasks
             
              --== CONFIGURATION PREVIEW ==--
             
              Default SAN wipe after delete           : False
              Firewall manager                        : iptables
              Update Firewall                         : True
              Host FQDN                               : manager.example.com
              Engine database secured connection      : False
              Engine database host                    : X.X.X.X
              Engine database user name               : engine
              Engine database name                    : engine
              Engine database port                    : 5432
              Engine database host name validation    : False
              Engine installation                     : True
              PKI organization                        : example.com
              NFS mount point                         : /var/lib/exports/iso
              Configure VMConsole Proxy               : True
              Engine Host FQDN                        : manager.example.com
              Configure WebSocket Proxy               : True
             
              Please confirm installation settings (OK, Cancel) [OK]:

    Copy to Clipboard Toggle word wrap

17. Synchronizing the Host and the Manager

    Return to Host-HE1 and continue the hosted-engine deployment script by selecting option 1:

    (1) Continue setup - engine installation is complete

    Copy to Clipboard Toggle word wrap

    [ INFO  ] Engine replied: DB Up!Welcome to Health Status!
    [ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
    [ INFO  ] Still waiting for VDSM host to become operational...
    [ INFO  ] The VDSM Host is now operational
              Please shutdown the VM allowing the system to launch it as a monitored service.
              The system will wait until the VM is down.

    Copy to Clipboard Toggle word wrap

18. Shutting Down HostedEngine-VM

    Shutdown HostedEngine-VM.

    # shutdown -h now

    Copy to Clipboard Toggle word wrap

19. Setup Confirmation

    Return to Host-HE1 to confirm it has detected that HostedEngine-VM is down.

    [ INFO  ] Enabling and starting HA services
              Hosted Engine successfully set up
    [ INFO  ] Stage: Clean up
    [ INFO  ] Stage: Pre-termination
    [ INFO  ] Stage: Termination

    Copy to Clipboard Toggle word wrap

Procedure 5.2. Migrating to a Self-Hosted Environment using the RHEV-M Virtual Appliance

1. Initiating a Self-Hosted Engine Deployment

   Run the hosted-engine script. To escape the script at any time, use the CTRL+D keyboard combination to abort deployment. It is recommended to use the screen window manager to run the script to avoid losing the session in case of network or terminal disruption. If not already installed, install the screen package, which is available in the standard Red Hat Enterprise Linux repository.

   # yum install screen

   Copy to Clipboard Toggle word wrap

   # screen

   Copy to Clipboard Toggle word wrap

   # hosted-engine --deploy

   Copy to Clipboard Toggle word wrap

   Note

   In the event of session timeout or connection disruption, run screen -d -r to recover the hosted-engine deployment session.

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 (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]:

   Copy to Clipboard Toggle word wrap
   • 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

     Copy to Clipboard Toggle word wrap
   • 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 [3260]:           
     Please specify the iSCSI portal user:           
     Please specify the iSCSI portal password:
     Please specify the target name (auto-detected values) [default]:

     Copy to Clipboard Toggle word wrap
   • For Gluster storage, specify the full address, using either the FQDN or IP address, and path name of the shared storage domain.

     Important

     Only replica 3 Gluster storage is supported. Ensure the following configuration has been made:

     • 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

       Copy to Clipboard Toggle word wrap
     • 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

       Copy to Clipboard Toggle word wrap

     Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/gluster_volume

     Copy to Clipboard Toggle word wrap
   • For Fibre Channel, the host bus adapters must be configured and connected, and the hosted-engine script will auto-detect the LUNs available. The LUNs must not contain any existing data.

     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]:

     Copy to Clipboard Toggle word wrap

3. Configuring the Network

   The script detects possible network interface controllers (NICs) to use as a management bridge for the environment. It then checks your firewall configuration and offers to modify it for console (SPICE or VNC) access HostedEngine-VM. Provide a pingable gateway IP address, to be used by the ovirt-ha-agent to help determine a host's suitability for running HostedEngine-VM.

   Please indicate a nic to set rhevm bridge on: (eth1, eth0) [eth1]:
   iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: 
   Please indicate a pingable gateway IP address [X.X.X.X]:

   Copy to Clipboard Toggle word wrap

4. Configuring the Virtual Machine

   The script creates a virtual machine to be configured as the Red Hat Enterprise Virtualization Manager, referred to in this procedure as HostedEngine-VM. Select disk for the boot device type, and the script will automatically detect the RHEV-M Appliances available. Select an appliance.

            Please specify the device to boot the VM from (choose disk for the oVirt engine appliance) (cdrom, disk, pxe) [disk]: 
   [ INFO ] Detecting available oVirt engine appliances
            The following appliance have been found on your system:
                  [1] - The RHEV-M Appliance image (OVA)
                  [2] - Directly select an OVA file
            Please select an appliance (1, 2) [1]:
   [ INFO ] Verifying its sha1sum
   [ INFO ] Checking OVF archive content (could take a few minutes depending on archive size)

   Copy to Clipboard Toggle word wrap
   Specify Yes if you want cloud-init to take care of the initial configuration of the Manager virtual machine. Specify Generate for cloud-init to take care of tasks like setting the root password, configuring networking, and configuring the host name. Optionally, select Existing if you have an existing cloud-init script to take care of more sophisticated functions of cloud-init. Specify the FQDN for the Manager virtual machine. This must be the same FQDN provided for the BareMetal-Manager.

   Note

   For more information on cloud-init, see https://cloudinit.readthedocs.org/en/latest/.

   Would you like to use cloud-init to customize the appliance on the first boot (Yes, No)[Yes]? Yes
   Would you like to generate on-fly a cloud-init no-cloud ISO image or do you have an existing one(Generate, Existing)[Generate]? Generate
   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.com

   Copy to Clipboard Toggle word wrap
   You must answer No to the following question so that you can restore the BareMetal-Manager backup file on HostedEngine-VM before running engine-setup.

   Automatically execute engine-setup on the engine appliance on first boot (Yes, No)[Yes]? No

   Copy to Clipboard Toggle word wrap
   Configure the Manager domain name, root password, networking, hardware, and console access details.

   Please provide the domain name you would like to use for the engine appliance.
   Engine VM domain: [example.com]
   Enter root password that will be used for the engine appliance (leave it empty to skip): p@ssw0rd
   Confirm appliance root password: p@ssw0rd
   How should the engine VM network be configured (DHCP, Static)[DHCP]? Static
   Please enter the IP address to be used for the engine VM: 192.168.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] Yes
   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: 2]: 
   You may specify a unicast MAC address for the VM or accept a randomly generated default [00:16:3e:77:b2:a4]: 
   Please specify the memory size of the VM in MB [Defaults to appliance OVF value: 4096]:
   Please specify the console type you would like to use to connect to the VM (vnc, spice) [vnc]: vnc

   Copy to Clipboard Toggle word wrap

5. Configuring the Self-Hosted Engine

   Specify the name for Host-HE1 to be identified in the Red Hat Enterprise Virtualization environment, and the password for the admin@internal user to access the Administration Portal. Finally, 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 the name which will be used to identify this host inside the Administrator Portal [hosted_engine_1]: Host-HE1
   Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: 
   Confirm 'admin@internal' user password: 
   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]:

   Copy to Clipboard Toggle word wrap

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                      : manager.example.com
   Bridge name                      : ovirtmgmt
   Host address                     : host.example.com
   SSH daemon port                  : 22
   Firewall manager                 : iptables
   Gateway address                  : X.X.X.X
   Host name for web application    : Host-HE1
   Host ID                          : 1
   Image size GB                    : 50
   Storage connection               : storage.example.com:/hosted_engine/nfs
   Console type                     : vnc
   Memory size MB                   : 4096
   MAC address                      : 00:16:3e:77:b2:a4
   Boot type                        : pxe
   Number of CPUs                   : 2
   CPU Type                         : model_SandyBridge
   
   Please confirm installation settings (Yes, No)[Yes]:

   Copy to Clipboard Toggle word wrap

7. Creating HostedEngine-VM

   The script creates the virtual machine to be configured as HostedEngine-VM and provides connection details. You must manually run engine-setup after restoring the backup file on HostedEngine-VM before the hosted-engine script can proceed on Host-HE1.

   [ INFO  ] Stage: Transaction setup
   ...
   [ INFO  ] Creating VM
             You can now connect to the VM with the following command:
                     /bin/remote-viewer vnc://localhost:5900
             Use temporary password "3463VnKn" to connect to vnc console.
             Please note that in order to use remote-viewer you need to be able to run graphical applications.
             This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding).
             Otherwise you can run the command from a terminal in your preferred desktop environment.
             If you cannot run graphical applications you can connect to the graphic console from another host or connect to the serial console using the following command:
             socat UNIX-CONNECT:/var/run/ovirt-vmconsole-console/8f74b589-8c6f-4a32-9adf-6e615b69de07.sock,user=ovirt-vmconsole STDIO,raw,echo=0,escape=1
             Please ensure that your Guest OS is properly configured to support serial console according to your distro documentation.
             Follow http://www.ovirt.org/Serial_Console_Setup#I_need_to_access_the_console_the_old_way for more info.
             If you need to reboot the VM you will need to start it manually using the command:
             hosted-engine --vm-start
             You can then set a temporary password using the command:
             hosted-engine --add-console-password
             Please install and setup the engine in the VM.
             You may also be interested in subscribing to "agent" RHN/Satellite channel and installing rhevm-guest-agent-common package in the VM.
           
           
             The VM has been rebooted.
             To continue please install oVirt-Engine in the VM
             (Follow http://www.ovirt.org/Quick_Start_Guide for more info).
           
             Make a selection from the options below:
             (1) Continue setup - oVirt-Engine installation is ready and ovirt-engine service is up
             (2) Abort setup
             (3) Power off and restart the VM
             (4) Destroy VM and abort setup
           
             (1, 2, 3, 4)[1]:

   Copy to Clipboard Toggle word wrap
   Connect to the virtual machine using the VNC protocol with the following command. Replace FQDN with the fully qualified domain name or the IP address of the self-hosted engine host.

   # /bin/remote-viewer vnc://FQDN:5900

   Copy to Clipboard Toggle word wrap

8. Enabling SSH on HostedEngine-VM

   SSH password authentication is not enabled by default on the RHEV-M Virtual Appliance. Connect to HostedEngine-VM via VNC and enable SSH password authentication so that you can access the virtual machine via SSH later to restore the BareMetal-Manager backup file and configure the new Manager. Verify that the sshd service is running. Edit /etc/ssh/sshd_config and change the following two options to yes:

   [...]
   PermitRootLogin yes       
   [...]
   PasswordAuthentication yes

   Copy to Clipboard Toggle word wrap
   Restart the sshd service for the changes to take effect.

   # service sshd restart

   Copy to Clipboard Toggle word wrap

9. Disabling BareMetal-Manager

   Connect to BareMetal-Manager, the Manager of your established Red Hat Enterprise Virtualization environment, and stop the engine and prevent it from running.

   # service ovirt-engine stop
   # chkconfig ovirt-engine off

   Copy to Clipboard Toggle word wrap

   Note

   Though stopping BareMetal-Manager from running is not obligatory, it is recommended as it ensures no changes will be made to the environment after the backup has been created. Additionally, it prevents BareMetal-Manager and HostedEngine-VM from simultaneously managing existing resources.

10. Updating DNS

    Update your DNS so that the FQDN of the Red Hat Enterprise Virtualization environment correlates to the IP address of HostedEngine-VM and the FQDN previously provided when configuring the hosted-engine deployment script on Host-HE1. In this procedure, FQDN was set as manager.example.com because in a migrated hosted-engine setup, the FQDN provided for the engine must be identical to that given in the engine setup of the original engine.

11. Creating a Backup of BareMetal-Manager

    Connect to BareMetal-Manager and run the engine-backup command with the --mode=backup, --file=FILE, and --log=LogFILE parameters to specify the backup mode, the name of the backup file created and used for the backup, and the name of the log file to be created to store the backup log.

    # engine-backup --mode=backup --file=FILE --log=LogFILE

    Copy to Clipboard Toggle word wrap

12. Copying the Backup File to HostedEngine-VM

    On BareMetal-Manager, secure copy the backup file to HostedEngine-VM. In the following example, manager.example.com is the FQDN for HostedEngine-VM, and /backup/ is any designated folder or path. If the designated folder or path does not exist, you must connect to HostedEngine-VM and create it before secure copying the backup from BareMetal-Manager.

    # scp -p FILE LogFILE manager.example.com:/backup/

    Copy to Clipboard Toggle word wrap

13. Restoring the Backup File on HostedEngine-VM

    Use the engine-backup tool to restore a complete backup. If you configured the BareMetal-Manager database(s) manually during engine-setup, follow the instructions at Section 7.2.3, “Restoring the Self-Hosted Engine Manager Manually” to restore the backup environment manually.
    • If you are only restoring the Manager, run:

      # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --restore-permissions

      Copy to Clipboard Toggle word wrap
    • If you are restoring the Manager, Reports, and Data Warehouse, run:

      # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --provision-dwh-db --provision-reports-db --restore-permissions

      Copy to Clipboard Toggle word wrap
    If successful, the following output displays:

    You should now run engine-setup.
    Done.

    Copy to Clipboard Toggle word wrap

14. Configuring HostedEngine-VM

    Configure the restored Manager virtual machine. This process identifies the existing configuration settings and database content. Confirm the settings. Upon completion, the setup provides an SSH fingerprint and an internal Certificate Authority hash.

    # engine-setup

    Copy to Clipboard Toggle word wrap

    [ INFO  ] Stage: Initializing
    [ INFO  ] Stage: Environment setup
    Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
    Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140304075238.log
    Version: otopi-1.1.2 (otopi-1.1.2-1.el6ev)
    [ INFO  ] Stage: Environment packages setup
    [ INFO  ] Yum Downloading: rhel-65-zstream/primary_db 2.8 M(70%)
    [ INFO  ] Stage: Programs detection
    [ INFO  ] Stage: Environment setup
    [ INFO  ] Stage: Environment customization
             
              --== PACKAGES ==--
             
    [ INFO  ] Checking for product updates...
    [ INFO  ] No product updates found
             
              --== NETWORK CONFIGURATION ==--
             
    Setup can automatically configure the firewall on this system.
    Note: automatic configuration of the firewall may overwrite current settings.
    Do you want Setup to configure the firewall? (Yes, No) [Yes]: 
    [ INFO  ] iptables will be configured as firewall manager.
             
              --== DATABASE CONFIGURATION ==--
             
             
              --== OVIRT ENGINE CONFIGURATION ==--
             
             
              --== PKI CONFIGURATION ==--
             
             
              --== APACHE CONFIGURATION ==--
             
             
              --== SYSTEM CONFIGURATION ==--
             
             
              --== END OF CONFIGURATION ==--
             
    [ INFO  ] Stage: Setup validation
    [ INFO  ] Cleaning stale zombie tasks
             
              --== CONFIGURATION PREVIEW ==--
             
              Default SAN wipe after delete           : False
              Firewall manager                        : iptables
              Update Firewall                         : True
              Host FQDN                               : manager.example.com
              Engine database secured connection      : False
              Engine database host                    : X.X.X.X
              Engine database user name               : engine
              Engine database name                    : engine
              Engine database port                    : 5432
              Engine database host name validation    : False
              Engine installation                     : True
              PKI organization                        : example.com
              NFS mount point                         : /var/lib/exports/iso
              Configure VMConsole Proxy               : True
              Engine Host FQDN                        : manager.example.com
              Configure WebSocket Proxy               : True
             
              Please confirm installation settings (OK, Cancel) [OK]:

    Copy to Clipboard Toggle word wrap

15. Synchronizing the Host and the Manager

    Return to Host-HE1 and continue the hosted-engine deployment script by selecting option 1:

    (1) Continue setup - oVirt-Engine installation is ready and ovirt-engine service is up

    Copy to Clipboard Toggle word wrap
    The script displays the internal Certificate Authority hash, and prompts you to select the cluster to which to add Host-HE1.

    [ INFO  ] Engine replied: DB Up!Welcome to Health Status!
    [ INFO  ] Acquiring internal CA cert from the engine
    [ INFO  ] The following CA certificate is going to be used, please immediately interrupt if not correct:
    [ INFO  ] Issuer: C=US, O=example.com, CN=manager.example.com.23240, Subject: C=US, O=example.com, CN=manager.example.com.23240, Fingerprint (SHA-1): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    [ INFO  ] Connecting to the Engine
              Enter the name of the cluster to which you want to add the host (DB1, DB2, Default) [Default]:
    [ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
    [ INFO  ] The VDSM Host is now operational
    [ INFO  ] Saving hosted-engine configuration on the shared storage domain
              Please shutdown the VM allowing the system to launch it as a monitored service.
              The system will wait until the VM is down.

    Copy to Clipboard Toggle word wrap

16. Shutting Down HostedEngine-VM

    Shut down HostedEngine-VM.

    # shutdown -h now

    Copy to Clipboard Toggle word wrap

17. Setup Confirmation

    Return to Host-HE1 to confirm it has detected that HostedEngine-VM is down.

    [ INFO  ] Enabling and starting HA services
    [ INFO  ] Stage: Clean up
    [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20160509162843.conf'
    [ INFO  ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
    [ INFO  ] Stage: Pre-termination
    [ INFO  ] Stage: Termination
    [ INFO  ] Hosted Engine successfully set up

    Copy to Clipboard Toggle word wrap

Procedure 6.1. Maintaining a RHEL-Based Self-Hosted Engine (Local Maintenance)

1. Place a self-hosted engine host into the local maintenance mode:
   • In the Administration Portal, place the host into maintenance, and the local maintenance mode is automatically triggered for that host.
   • You can also set the maintenance mode from the command line:

     # hosted-engine --set-maintenance --mode=local

     Copy to Clipboard Toggle word wrap
2. After you have completed any maintenance tasks, disable the maintenance mode:

   # hosted-engine --set-maintenance --mode=none

   Copy to Clipboard Toggle word wrap

Procedure 6.2. Maintaining a RHEL-Based Self-Hosted Engine (Global Maintenance)

1. Place a self-hosted engine host into the global maintenance mode:
   • In the Administration Portal, right-click the engine virtual machine, and select Enable Global HA Maintenance.
   • You can also set the maintenance mode from the command line:

     # hosted-engine --set-maintenance --mode=global

     Copy to Clipboard Toggle word wrap
2. After you have completed any maintenance tasks, disable the maintenance mode:

   # hosted-engine --set-maintenance --mode=none

   Copy to Clipboard Toggle word wrap

Procedure 6.3. Maintaining a RHEV-H-Based Self-Hosted Engine

1. In the text user interface, select the Hosted Engine screen.
2. Select < Set Hosted Engine maintenance >, and select a maintenance mode, either Local or Global.
3. After you have completed any maintenance tasks, disable the maintenance mode. Select < Set Hosted Engine maintenance >, and select None.

Procedure 6.4. Upgrading the Self-Hosted Engine Manager Virtual Machine

1. Disable the high-availability agents on all the self-hosted engine hosts. To do this run the following command on any self-hosted engine host in the cluster.

   # hosted-engine --set-maintenance --mode=global

   Copy to Clipboard Toggle word wrap
   After a few minutes, run hosted-engine --vm-status to confirm that the environment is in maintenance mode.
2. Log in to the Manager virtual machine to upgrade the Red Hat Enterprise Virtualization Manager.
   1. Enable the Red Hat Enterprise Virtualization Manager 3.6 repository:

      # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms

      Copy to Clipboard Toggle word wrap
   2. Update the rhevm setup packages:

      # yum update rhevm\*setup\*

      Copy to Clipboard Toggle word wrap
   3. Run engine-setup and follow the prompts to upgrade the Red Hat Enterprise Virtualization Manager:

      # engine-setup

      Copy to Clipboard Toggle word wrap
   4. Remove or disable the Red Hat Enterprise Virtualization Manager 3.5 repository to ensure the system does not use any Red Hat Enterprise Virtualization Manager 3.5 packages:

      # subscription-manager repos --disable=rhel-6-server-rhevm-3.5-rpms

      Copy to Clipboard Toggle word wrap
   5. Update the base operating system:

      # yum update

      Copy to Clipboard Toggle word wrap

Procedure 6.5. Updating the RHEV-H Self-Hosted Engine Host

1. Update the RHEV-H host. See Updating Red Hat Enterprise Virtualization Hypervisors in the Upgrade Guide for more information.
2. On the host, restart VDSM:

   # systemctl restart vdsmd

   Copy to Clipboard Toggle word wrap
3. Restart ovirt-ha-broker and ovirt-ha-agent:

   # systemctl restart ovirt-ha-broker

   Copy to Clipboard Toggle word wrap

   # systemctl restart ovirt-ha-agent

   Copy to Clipboard Toggle word wrap
4. Repeat step 1 to step 3 to update all self-hosted engine hosts. If you have any standard RHEV-H hosts you can update them using step 1.
5. Disable global maintenance after all self-hosted engine hosts have been updated.

   # hosted-engine --set-maintenance --mode=none

   Copy to Clipboard Toggle word wrap

Procedure 6.6. Updating the RHEL-Based Self-Hosted Engine Host

1. Access the Administration Portal. Select a self-hosted engine host and place it into maintenance mode by clicking Maintenance. If the host is hosting the Manager virtual machine, the virtual machine will be migrated to another host. Any other virtual machines will be migrated according to your virtual machine migration policy. The high-availability agents are automatically placed into local maintenance.
2. Update the self-hosted engine host:

   # yum update

   Copy to Clipboard Toggle word wrap
3. Restart VDSM:

   # systemctl restart vdsmd

   Copy to Clipboard Toggle word wrap
4. Restart ovirt-ha-broker and ovirt-ha-agent:

   # systemctl restart ovirt-ha-broker

   Copy to Clipboard Toggle word wrap

   # systemctl restart ovirt-ha-agent

   Copy to Clipboard Toggle word wrap
5. Access the Administration Portal. Select the same host and click Activate.
6. Repeat step 1 to step 5 to update all self-hosted engine hosts. If you have standard Red Hat Enterprise Linux 7 hosts in your environment, ensure the required repository is enabled on the host as in step 2, and update the host. See Updating Red Hat Enterprise Linux Virtualization Hosts in the Upgrade Guide for more information.
7. Disable global maintenance after all self-hosted engine hosts have been updated.

   # hosted-engine --set-maintenance --mode=none

   Copy to Clipboard Toggle word wrap

Procedure 6.7. Upgrading Additional Hosts

1. Access the Administration Portal. Select the host and place it into maintenance mode by clicking Maintenance. If the host is hosting the Manager virtual machine, the virtual machine will be migrated to another host. Any other virtual machines will be migrated according to your virtual machine migration policy. The high-availability agents are automatically placed into local maintenance.
2. Ensure the required repository is enabled:

   # subscription-manager repos --enable=rhel-7-server-rhev-mgmt-agent-rpms

   Copy to Clipboard Toggle word wrap
3. Update the self-hosted engine host:

   # yum update

   Copy to Clipboard Toggle word wrap
4. Restart VDSM:

   # service vdsmd restart

   Copy to Clipboard Toggle word wrap
5. Restart ovirt-ha-broker and ovirt-ha-agent:

   # service ovirt-ha-broker restart

   Copy to Clipboard Toggle word wrap

   # service ovirt-ha-agent restart

   Copy to Clipboard Toggle word wrap
6. Access the Administration Portal. Select the host and activate it by clicking Activate.
7. Repeat the steps for all self-hosted engine hosts you want to upgrade.

Procedure 6.8. Updating the Cluster Compatibility Version

1. Access the Administration Portal. Select the Default cluster and click Edit to open the Edit Cluster window.
2. Use the Compatibility Version drop-down menu to select 3.6. Click OK to save the change and close the window.

Procedure 6.9. Upgrading the Manager

1. Enable global maintenance from one of the self-hosted engine hosts:

   # hosted-engine --set-maintenance --mode=global

   Copy to Clipboard Toggle word wrap
2. On the Manager virtual machine, subscribe to the required entitlements for receiving the Manager 3.6 packages:

   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms

   Copy to Clipboard Toggle word wrap
3. Update the rhevm setup packages:

   # yum update rhevm\*setup\*

   Copy to Clipboard Toggle word wrap
4. Run the following command and follow the prompts to upgrade the Manager:

   # engine-setup --otopi-environment=OVESETUP_DB/forceUpgradeWithHeEl6Hosts=bool:True

   Copy to Clipboard Toggle word wrap
5. Remove or disable the Manager 3.5 repository to ensure the system does not use any Manager 3.5 packages:

   # subscription-manager repos --disable=rhel-6-server-rhevm-3.5-rpms

   Copy to Clipboard Toggle word wrap

Procedure 6.10. Upgrading the Self-Hosted Engine Host

1. In the Administration Portal, click the Hosts tab, select the host on which the self-hosted engine was originally deployed, click Maintenance, and click OK. The host's virtual machines, including the Manager, will migrate to other hosts.
2. Connect to the Manager virtual machine and run the host-direct-upgrade tool to import the configuration files:

   # /usr/share/ovirt-engine/bin/host-direct-upgrade.sh --import-configuration-files [-h 3.5-host-address]

   Copy to Clipboard Toggle word wrap

   Note

   If you do not specify the optional -h 3.5-host-address parameter, you will be prompted to input the 3.5 host's IP address or FQDN later.

   The host-direct-upgrade tool checks whether the self-hosted engine is configured to allow mixed RHEL versions in the same cluster. If not, the ovirt-engine service is restarted.
3. In the Administration Portal, click the Clusters tab and select the cluster.
4. Click Edit.
5. In the Scheduling Policy tab, select InClusterUpgrade from the Policy drop-down list and click OK.
6. Download Next Generation RHVH (for RHEV-M 3.6.11 Async) or RHEL 7.
7. Install the newer operating system on the host, keeping the same IP address and host name. See Installing Red Hat Virtualization Host in the Installation Guide to install Next Generation RHVH or the Red Hat Enterprise Linux Installation Guide to install RHEL 7.
8. Connect to the Manager virtual machine and run the host-direct-upgrade tool to export the configuration files:

   # /usr/share/ovirt-engine/bin/host-direct-upgrade.sh --export-and-configure [-h 3.6-host-address]

   Copy to Clipboard Toggle word wrap

   Note

   The 3.6-host-address is the IP address or FQDN of the host that you upgraded.

   This process may take 10 to 15 minutes.
9. Check the host's status:

   # hosted-engine --vm-status

   Copy to Clipboard Toggle word wrap
   The Score should be 2800:

   !! Cluster is in GLOBAL MAINTENANCE mode !!
   
   --== Host 1 status ==--
   
   conf_on_shared_storage             : False
   Status up-to-date                  : True
   Hostname                           : rhvhhe20170926h1.localdomain
   Host ID                            : 1
   Engine status                      : "reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"
   Score                              : 2800
   stopped                            : False
   Local maintenance                  : False
   crc32                              : ffe0a244
   local_conf_timestamp               : 0
   Host timestamp                     : 1375

   Copy to Clipboard Toggle word wrap
10. In the Administration Portal, click the Hosts tab and select the 3.5 host (still in maintenance mode).
11. Click Remove and OK.
12. Click New and add the upgraded host. Its status should be Up.
13. Migrate the Manager virtual machine manually to the upgraded host. See Manually Migrating Virtual Machines in the Virtual Machine Management Guide for details.

Procedure 6.11. Comparing the Manager's SPM ID to the Host IDs

1. Connect to the Manager virtual machine and run the following command to output the SPM ID:

   # sudo -u postgres psql engine -c "SELECT vds_spm_id, vds.vds_name FROM vds"

   Copy to Clipboard Toggle word wrap
2. Connect to each host and run the following command to ouput the Host ID:

   # grep "^host_id" /etc/ovirt-hosted-engine/hosted-engine.conf

   Copy to Clipboard Toggle word wrap
3. If a host's Host ID does not match the Manager's SPM ID:
   1. In the Administration Portal, click the Hosts tab, select the host with the mismatched Host ID, click Maintenance, and click OK.
   2. Connect to the host and correct the host_id value in the /etc/ovirt-hosted-engine/hosted-engine.conf file.
   3. Reboot the host.
   4. In the Administration Portal, click the Hosts tab and select the host.
   5. Click Activate and OK.

Procedure 6.12. Upgrading the Remaining Hosts

1. In the Administration Portal, click the Hosts tab, select another host, and click Maintenance.
   The host's virtual machines will migrate to other machines, preferring hosts with newer operating systems, because of the InClusterUpgrade policy. If the virtual machines do not migrate automatically, migrate them manually. See Manually Migrating Virtual Machines in the Virtual Machine Management Guide for details.
2. When the host has no virtual machines, click Remove.
3. Install Next Generation RHVH or RHEL 7 on the host, keeping its IP address and host name.
4. In the Administration Portal, click the Hosts tab and click Add to add the upgraded host.

   Note

   The upgraded host is added manually, before the hosted-engine setup, in order to preserve its Host ID.
5. Connect to the host, disable NetworkManager, and enable the network script:

   # systemctl stop NetworkManager; systemctl disable NetworkManager; systemctl start network; systemctl enable network

   Copy to Clipboard Toggle word wrap
6. Install the screen utility if necessary:

   # yum install screen

   Copy to Clipboard Toggle word wrap
7. Run the hosted-engine setup in a screen session:

   # hosted-engine --deploy
       
   [ INFO  ] Stage: Initializing
   [ INFO  ] Generating a temporary VNC password.   
   [ INFO  ] Stage: Environment setup
             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]:
             Configuration files: []
             Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup.log
             Version: otopi-1.4.2 (otopi-1.4.2-1.el7ev)
   [ INFO  ] Hardware supports virtualization
   [ INFO  ] Stage: Environment packages setup
   [ INFO  ] Stage: Programs detection
   [ INFO  ] Stage: Environment setup
   [ INFO  ] Stage: Environment customization
   
             --== STORAGE CONFIGURATION ==--
   
             During customization use CTRL-D to abort.
             Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs3, nfs4)[nfs3]: nfs4
             Please specify the full shared storage connection path to use (example: host:/path): hostname:/path
             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]:
   
             --== SYSTEM CONFIGURATION ==--
   
   [WARNING] A configuration file must be supplied to deploy Hosted Engine on an additional host.
   [ INFO  ] Answer file successfully loaded
   
             --== NETWORK CONFIGURATION ==--
   
   [ INFO  ] Bridge rhevm already created
   [ INFO  ] Additional host deployment, firewall manager is 'iptables'
             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
   
             --== HOSTED ENGINE CONFIGURATION ==--  
   
             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:
   [ INFO  ] Stage: Setup validation
             Please provide the address of this host.
             Note: The engine VM and all the other hosts should be able to correctly resolve it.
             Host address:  [rhvh.example.com]:
   	  The Host ID is already known. Is this a re-deployment on an additional host that was previously set up (Yes, No)[Yes]?
   
             --== CONFIGURATION PREVIEW ==--
   
             Engine FQDN                        : enginevm.localdomain
             Bridge name                        : rhevm
             Host address                       : rhvh.example.com
             SSH daemon port                    : 22
             Firewall manager                   : iptables
             Gateway address                    : 192.168.1.1
             Host name for web application      : hosted_engine_2
             Storage Domain type                : nfs4
             Host ID                            : 2 
             Image size GB                      : 50
             GlusterFS Share Name               : hosted_engine_glusterfs
             GlusterFS Brick Provisioning       : False
             Storage connection                 : hostname:/path
             Console type                       : vnc
             Memory size MB                     : 4096
             MAC address                        : 00:16:3e:12:96:6b
             Boot type                          : disk
             Number of CPUs                     : 1 
             CPU Type                           : model_SandyBridge
   [ INFO  ] Stage: Transaction setup
   [ INFO  ] Stage: Misc configuration
   [ INFO  ] Stage: Package installation
   [ INFO  ] Stage: Misc configuration
   [ INFO  ] Configuring libvirt
   [ INFO  ] Configuring VDSM
   [ INFO  ] Starting vdsmd
   [ INFO  ] Waiting for VDSM hardware info
   [ INFO  ] Configuring VM
   [ INFO  ] Updating hosted-engine configuration   
   [ INFO  ] Stage: Transaction commit
   [ INFO  ] Stage: Closing up
   [ INFO  ] Acquiring internal CA cert from the engine
   [ INFO  ] The following CA certificate is going to be used, please immediately interrupt if not correct:
   [ INFO  ] Issuer: C=US, O=localdomain, CN=enginevm.localdomain.34970, Subject: C=US, O=localdomain, CN=enginevm.localdomain.34970, Fingerprint (SHA-1): 46A75DA2174D03B100D1811411C0C6627CB1D821
   [ INFO  ] Connecting to the Engine
   [ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
   
   [ INFO  ] Still waiting for VDSM host to become operational...
   [ INFO  ] The VDSM Host is now operational
   [ ERROR ] Cannot automatically set CPU level of cluster Default: inclusterupgrade is not a member of SchedulingPolicyType. Possible values for SchedulingPolicyType are: evenly_distributed, power_saving, none, vm_evenly_distributed 
   [ INFO  ] Enabling and starting HA services
   [ INFO  ] Stage: Clean up
   [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20170927190113.conf'
   [ INFO  ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
   [ INFO  ] Stage: Pre-termination
   [ INFO  ] Stage: Termination
   [ INFO  ] Hosted Engine successfully set up

   Copy to Clipboard Toggle word wrap

   Note

   You can ignore the [ ERROR ] Cannot automatically set CPU level of cluster Default message.

Procedure 6.13. Post-Upgrade Tasks

1. In the Administration Portal, click the Cluster tab and select the cluster.
2. Select 3.6 from the Compatibility Version drop-down list.
3. In the Scheduling Policy tab, select None from the Policy drop-down list and click OK.
4. Reboot each virtual machine (except the Manager virtual machine), one by one.
5. Connect to the Manager virtual machine and update its configuration:

   # engine-config -s CheckMixedRhelVersions=true --cver=3.5

   Copy to Clipboard Toggle word wrap
6. In the Administration Portal, click the Events tab and confirm that the Manager virtual machine and its storage domain were imported successfully:

   Sep 27, 2017 7:15:18 PM Hosted Engine VM was imported successfully
   Sep 27, 2017 7:15:18 PM Starting to import Vm HostedEngine to Data Center Default, Cluster Default
   Sep 27, 2017 7:15:16 PM VM HostedEngine was successfully removed.
   Sep 27, 2017 7:15:00 PM Hosted Engine storage domain imported successfully
   Sep 27, 2017 7:15:00 PM Storage Domain hosted_storage was attached to Data Center Default by SYSTEM
   Sep 27, 2017 7:15:00 PM Storage Domain hosted_storage (Data Center Default) was activated by SYSTEM
   Sep 27, 2017 7:14:57 PM The Hosted Engine Storage Domain isn't Active.

   Copy to Clipboard Toggle word wrap
7. In the Virtual Machines tab, select the Manager virtual machine, and click Shutdown.
8. Connect to a self-hosted engine host and disable global maintenance mode:

   # hosted-engine --set-maintenance --mode=none

   Copy to Clipboard Toggle word wrap
   Wait for the ovirt-ha-agent service to restart the Manager virtual machine.
9. Check the status of each host:

   # hosted-engine --vm-status

   Copy to Clipboard Toggle word wrap
   Each host should have a score of 3400:

   --== Host 1 status ==--
   
   conf_on_shared_storage             : False
   Status up-to-date                  : True
   Hostname                           : rhvhhe20170926h1.localdomain
   Host ID                            : 1
   Engine status                      : "health": "good", "vm": "up", "detail": "up"
   Score                              : 3400
   stopped                            : False
   Local maintenance                  : False
   crc32                              : 6a5a17a7
   local_conf_timestamp               : 7580
   Host timestamp                     : 7579
   
   
   --== Host 2 status ==--
   
   conf_on_shared_storage             : False
   Status up-to-date                  : True
   Hostname                           : rhvhhe20170926h2.localdomain
   Host ID                            : 2
   Engine status                      : "reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"
   Score                              : 3400
   stopped                            : False
   Local maintenance                  : False
   crc32                              : 1c87c83d
   local_conf_timestamp               : 4323
   Host timestamp                     : 4323

   Copy to Clipboard Toggle word wrap

Procedure 6.14. Removing a Host from a Self-Hosted Engine Environment

1. In the Administration Portal, click the Hosts tab. Select the host and click Maintenance to set the host to the local maintenance mode. This action stops the ovirt-ha-agent and ovirt-ha-broker services.
2. Log in to the host and disable the HA services so the services are not started upon a reboot:

   # systemctl disable ovirt-ha-agent
   # systemctl disable ovirt-ha-broker

   Copy to Clipboard Toggle word wrap
3. Remove the self-hosted engine configuration file:
   • RHEL-based hypervisor:

     # rm /etc/ovirt-hosted-engine/hosted-engine.conf

     Copy to Clipboard Toggle word wrap
   • RHEV-H:

     # unpersist /etc/ovirt-hosted-engine/hosted-engine.conf
     # rm /etc/ovirt-hosted-engine/hosted-engine.conf

     Copy to Clipboard Toggle word wrap
4. In the Administration Portal, select the same host, and click Remove to open the Remove Host(s) confirmation window. Click OK.

Procedure 7.3. Backing up the Original Red Hat Enterprise Virtualization Manager

1. Preparing the Failover Host

   A failover host, one of the hosted-engine hosts in the environment, must be placed into maintenance mode so that it has no virtual load at the time of the backup. This host can then later be used to deploy the restored self-hosted engine environment. Any of the hosted-engine hosts can be used as the failover host for this backup scenario, however the restore process is more straightforward if Host 1 is used. The default name for the Host 1 host is hosted_engine_1; this was set when the hosted-engine deployment script was initially run.
   1. Log in to one of the hosted-engine hosts.
   2. Confirm that the hosted_engine_1 host is Host 1:

       # hosted-engine --vm-status

      Copy to Clipboard Toggle word wrap
   3. Log in to the Administration Portal.
   4. Click the Hosts tab.
   5. Select the hosted_engine_1 host in the results list, and click Maintenance.
   6. Click Ok.
   Depending on the virual load of the host, it may take some time for all the virtual machines to be migrated. Proceed to the next step after the host status has changed to Maintenance.

2. Creating a Backup of the Manager

   On the Manager virtual machine, back up the configuration settings and database content, replacing [EngineBackupFile] with the file name for the backup file, and [LogFILE] with the file name for the backup log.

   # engine-backup --mode=backup --file=[EngineBackupFile] --log=[LogFILE]

   Copy to Clipboard Toggle word wrap

3. Backing up the Files to an External Server

   Back up the files to an external server. In the following example, [Storage.example.com] is the fully qualified domain name of a network storage server that will store the backup until it is needed, and /backup/ is any designated folder or path. The backup files must be accessible to restore the configuration settings and database content.

   # scp -p [EngineBackupFiles] [Storage.example.com:/backup/EngineBackupFiles]

   Copy to Clipboard Toggle word wrap

4. Activating the Failover Host

   Bring the hosted_engine_1 host out of maintenance mode.
   1. Log in to the Administration Portal.
   2. Click the Hosts tab.
   3. Select hosted_engine_1 from the results list.
   4. Click Activate.