Procedure

1. Download the Red Hat Virtualization Host ISO image from the Customer Portal:

   1. Log in to the Customer Portal at https://access.redhat.com.
   2. Click Downloads in the menu bar.
   3. Click Red Hat Virtualization. Scroll up and click Download Latest to access the product download page.
   4. Go to Hypervisor Image for RHV 4.3 and and click Download Now.
   5. Create a bootable media device. See Making Media in the Red Hat Enterprise Linux Installation Guide for more information.
2. Start the machine on which you are installing Red Hat Virtualization Host, and boot from the prepared installation media.

3. From the boot menu, select Install RHVH 4.3 and press Enter.

   Note

   You can also press the Tab key to edit the kernel parameters. Kernel parameters must be separated by a space, and you can boot the system using the specified kernel parameters by pressing the Enter key. Press the Esc key to clear any changes to the kernel parameters and return to the boot menu.

4. Select a language, and click Continue.

5. Select a time zone from the Date & Time screen and click Done.

   Important

   Red Hat recommends using Coordinated Universal Time (UTC) on all hosts. This helps ensure that data collection and connectivity are not impacted by variation in local time, such as during daylight savings time.

6. Select a keyboard layout from the Keyboard screen and click Done.

7. Specify the installation location from the Installation Destination screen.

   Important

   • Red Hat strongly recommends using the Automatically configure partitioning option.
   • All disks are selected by default, so deselect disks that you do not want to use as installation locations.
   • At-rest encryption is not supported. Do not enable encryption.

   • Red Hat recommends increasing the size of /var/log to at least 15GB to provide sufficient space for the additional logging requirements of Red Hat Gluster Storage.

     Follow the instructions in Growing a logical volume using the Web Console to increase the size of this partition after installing the operating system.

   Click Done.

8. Select the Ethernet network from the Network & Host Name screen.

   1. Click Configure…​ → General and select the Automatically connect to this network when it is available check box.
9. Optionally configure Language Support, Security Policy, and Kdump. See Installing Using Anaconda in the Red Hat Enterprise Linux 7 Installation Guide for more information on each of the sections in the Installation Summary screen.
10. Click Begin Installation.

11. Set a root password and, optionally, create an additional user while Red Hat Virtualization Host installs.

    Warning

    Red Hat strongly recommends not creating untrusted users on Red Hat Virtualization Host, as this can lead to exploitation of local security vulnerabilities.

12. Click Reboot to complete the installation.

    Note

    When Red Hat Virtualization Host restarts, nodectl check performs a health check on the host and displays the result when you log in on the command line. The message node status: OK or node status: DEGRADED indicates the health status. Run nodectl check to get more information. The service is enabled by default.

1. Log in to the Web Console.

   Use the management FQDN and port 9090, for example, https://server1.example.com:9090/.

2. Navigate to Subscriptions, click Register System, and enter your Customer Portal user name and password.

   The Red Hat Virtualization Host subscription is automatically attached to the system.

3. Click Terminal.

4. Enable the Red Hat Virtualization Host 7 repository to allow later updates to the Red Hat Virtualization Host:

   # subscription-manager repos --enable=rhel-7-server-rhvh-4-rpms

1. Log in to the first hyperconverged host as the root user.

2. Perform the following steps for each host in the cluster, including the first host.

   1. Use SSH to log in to a host as the root user.

      [root@server1]# ssh root@server1.example.com

   2. Enter yes to continue connecting.

      [root@server1]# ssh root@server2.example.com
      The authenticity of host 'server2.example.com (192.51.100.28)' can't be established.
      ECDSA key fingerprint is SHA256:Td8KqgVIPXdTIasdfa2xRwn3/asdBasdpnaGM.
      Are you sure you want to continue connecting (yes/no)?

      This automatically adds the host key of the first host to the known_hosts file on the target host.

      Are you sure you want to continue connecting (yes/no)? yes
      Warning: Permanently added '192.51.100.28' (ECDSA) to the list of known hosts.

   3. Enter the password for the root user on the target host to complete the login process.

      root@server2.example.com's password: ***************
      Last login: Mon May 27 10:04:49 2019
      [root@server2]#

   4. Log out of the host.

      [root@server2]# exit
      [root@server1]#

      Note

      When you log out of the SSH session from the first host to itself, the user and server in the command line prompt stay the same; it is only the session that changes.

      [root@server1]# exit
      [root@server1]#

Procedure

1. Log in to the first hyperconverged host as the root user.

2. Generate an SSH key that does not use a password.

   1. Start the key generation process.

      # ssh-keygen -t rsa
      Generating public/private rsa key pair.

   2. Enter a location for the key.

      The default location, shown in parentheses, is used if no other input is provided.

      Enter file in which to save the key (/home/username/.ssh/id_rsa): <location>/<keyname>

   3. Specify and confirm an empty passphrase by pressing Enter twice.

      Enter passphrase (empty for no passphrase):
      Enter same passphrase again:

      The private key is saved in <location>/<keyname>. The public key is saved in <location>/<keyname>.pub.

      Your identification has been saved in <location>/<keyname>.
      Your public key has been saved in <location>/<keyname>.pub.
      The key fingerprint is SHA256:8BhZageKrLXM99z5f/AM9aPo/KAUd8ZZFPcPFWqK6+M root@server1.example.com
      The key's randomart image is:
      +---[ECDSA 256]---+
      |      . .      +=|
      | . . . =      o.o|
      |  + . * .    o...|
      | = . . *  . + +..|
      |. + . . So o * ..|
      |   . o . .+ =  ..|
      |      o oo ..=. .|
      |        ooo...+  |
      |        .E++oo   |
      +----[SHA256]-----+

      Warning

      Your identification in this output is your private key. Never share your private key. Possession of your private key allows someone else to impersonate you on any system that has your public key.

Procedure

1. Log in to the first host as the root user.

2. Copy your public key to the host that you want to access.

   # ssh-copy-id -i <location>/<keyname>.pub <user>@<hostname>

   Enter the password for <user>@<hostname> if prompted.

   Warning

   Make sure that you use the file that ends in .pub. Never share your private key. Possession of your private key allows someone else to impersonate you on any system that has your public key.

1. Log into the Web Console

   Browse to the the Web Console management interface of the first hyperconverged host, for example, https://node1.example.com:9090/, and log in with the credentials you created in the previous section.

2. Start the deployment wizard

   1. Click Virtualization → Hosted Engine and click Start underneath Hyperconverged.

      

      The Gluster Configuration window opens.

   2. Click the Run Gluster Wizard for Single Node button.

      

      The Gluster Deployment window opens in single node mode.

3. Specify hyperconverged host

   Specify the back-end FQDN on the storage network of the hyperconverged host and click Next.

   

4. Specify volumes

   Specify the volumes to create.

   

   Name

   Specify the name of the volume to be created.

   Volume Type

   Specify a Distribute volume type. Only distributed volumes are supported for single node deployments.

   Brick Dirs

   The directory that contains this volume’s bricks.

5. Specify bricks

   Specify the bricks to create.

   

   RAID

   Specify the RAID configuration to use. This should match the RAID configuration of your host. Supported values are raid5, raid6, and jbod. Setting this option ensures that your storage is correctly tuned for your RAID configuration.

   Stripe Size

   Specify the RAID stripe size in KB. Do not enter units, only the number. This can be ignored for jbod configurations.

   Disk Count

   Specify the number of data disks in a RAID volume. This can be ignored for jbod configurations.

   LV Name

   The name of the logical volume to be created. This is pre-filled with the name that you specified on the previous page of the wizard.

   Device

   Specify the raw device you want to use. Red Hat recommends an unpartitioned device.

   1. With multipath devices

      If the environment has multipath devices for the Gluster deployment from the cockpit, use multipath WWIDs.
      For example:

      /dev/mapper/3600508b1001caab032303683327a6a2e
      instead of /dev/sdb

   2. Without the multipath devices

      If there are no multipath devices in the environment. Blacklist these devices.

      Note

      Blacklist: Listing of specific devices that will not be considered for multipath.

      There are different ways to blacklist the device. For more information, refer to RHEL 7 DM Multipath, chapter 4.2.

      • To blacklist the device /dev/sdb

        1. Create a directory: /etc/multipath/conf.d/

        2. Create a file under this directory with the following content: blacklist {
           devnodes "<device>"
           }
           For example:

           [root@ ~]# cat /etc/multipath/conf.d/99-custom-multipath.conf
           blacklist {
               devnodes "sdb"
           }

           Important

           Local disks should not have multipath names. Use lsblk command to check for multipath names.
           

           If there are multipath names on the disks, after blacklisting the disks,reboot the hosts.

   Size

   Specify the size of the logical volume to create in GB. Do not enter units, only the number. This number should be the same for all bricks in a replicated set. Arbiter bricks can be smaller than other bricks in their replication set.

   Mount Point

   The mount point for the logical volume. This is pre-filled with the brick directory that you specified on the previous page of the wizard.

   Thinp

   This option is enabled and volumes are thinly provisioned by default, except for the engine volume, which must be thickly provisioned.

   Enable Dedupe & Compression

   Specify whether to provision the volume using VDO for compression and deduplication at deployment time.

   Logical Size (GB)

   Specify the logical size of the VDO volume. This can be up to 10 times the size of the physical volume, with an absolute maximum logical size of 4 PB.

   Configure LV Cache

   Optionally, check this checkbox to configure a small, fast SSD device as a logical volume cache for a larger, slower logical volume. Add the device path to the SSD field, the size to the LV Size (GB) field, and set the Cache Mode used by the device.

   Warning

   To avoid data loss when using write-back mode, Red Hat recommends using two separate SSD/NVMe devices. Configuring the two devices in a RAID-1 configuration (via software or hardware), significantly reduces the potential of data loss from lost writes.

   For further information about lvmcache configuration, see Red Hat Enterprise Linux 7 LVM Administration.

6. Review and edit configuration

   Review the contents of the generated configuration file and click Edit to modify the file, and Save to keep your changes.

   Click Deploy when you are satisfied with the configuration file.

   

7. Wait for deployment to complete

   You can watch the deployment process in the text field.

   The window displays Successfully deployed gluster when complete.

   Click Continue to Hosted Engine Deployment and continue the deployment process with the instructions in Section 5.2, “Deploy the Hosted Engine on a single node using the Web Console”.

Procedure

1. Open the Hosted Engine Deployment wizard

   If you continued directly from the end of Configure Red Hat Gluster Storage on a single node, the wizard is already open.

   Otherwise:

   1. Click Virtualization → Hosted Engine.
   2. Click Start underneath Hyperconverged.

   3. Click Use existing configuration.

      Important

      If the previous deployment attempt failed, click Clean up instead of Use existing configuration to discard the previous attempt and start from scratch.

2. Specify virtual machine details

   

   1. Enter the following details:

      Engine VM FQDN

      The fully qualified domain name to be used for the Hosted Engine virtual machine, for example, engine.example.com.

      MAC Address

      The MAC address associated with the Engine VM FQDN.

      Important

      The pre-populated MAC address must be replaced.

      Root password

      The root password to be used for the Hosted Engine virtual machine.

   2. Click Next. Your FQDNs are validated before the next screen appears.

3. Specify virtualization management details

   1. Enter the password to be used by the admin account in the Administration Portal. You can also specify notification behaviour here.

      
   2. Click Next.

4. Review virtual machine configuration

   1. Ensure that the details listed on this tab are correct. Click Back to correct any incorrect information.

      
   2. Click Prepare VM.

   3. Wait for virtual machine preparation to complete.

      

      If preparation does not occur successfully, see Viewing Hosted Engine deployment errors.

   4. Click Next.

5. Specify storage for the Hosted Engine virtual machine

   1. Specify the back-end address and location of the engine volume.

      
   2. Click Next.

6. Finalize Hosted Engine deployment

   1. Review your deployment details and verify that they are correct.

      Note

      The responses you provided during configuration are saved to an answer file to help you reinstall the hosted engine if necessary. The answer file is created at /etc/ovirt-hosted-engine/answers.conf by default. This file should not be modified manually without assistance from Red Hat Support.

      
   2. Click Finish Deployment.

7. Wait for deployment to complete

   This takes up to 30 minutes.

   The window displays the following when complete.

   
   Important

   If deployment does not complete successfully, see Viewing Hosted Engine deployment errors.

   Click Close.

8. Verify hosted engine deployment

   Browse to the Administration Portal (for example, http://engine.example.com/ovirt-engine) and verify that you can log in using the administrative credentials you configured earlier. Click Dashboard and look for your hosts, storage domains, and virtual machines.