Procedure

1. Download the Red Hat Enterprise Linux 7 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. Beside Red Hat Enterprise Linux click Versions 7 and below.
   4. In the Version drop-down menu, select version 7.6.
   5. Go to Red Hat Enterprise Linux 7.6 Binary DVD and and click Download Now.
   6. Create a bootable media device. See Making Media in the Red Hat Enterprise Linux Installation Guide for more information.
2. Start the machine you are installing as a Red Hat Enterprise Linux host, and boot from the prepared installation media.

3. From the boot menu, select Install Red Hat Enterprise Linux 7.6 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 Enterprise Linux installs.

    Warning

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

12. Click Reboot to complete the installation.

1. Register your machine to Red Hat Network.

   # subscription-manager register --username=<username> --password=<password>

2. Attach the pool.

   # subscription-manager attach --pool=Pool ID number

3. Disable the repositories.

   # subscription-manager repos --disable="*"

4. Enable the additional channels required for Red Hat Enterprise Linux hosts.

   # subscription-manager repos --enable=rhel-7-server-rpms  --enable=rh-gluster-3-for-rhel-7-server-rpms  --enable=rhel-7-server-rhv-4-mgmt-agent-rpms --enable=rhel-7-server-ansible-2.9-rpms

1. Install the packages required for RHHI for Virtualization.

   # yum install glusterfs-server vdsm-gluster ovirt-hosted-engine-setup cockpit-ovirt-dashboard gluster-ansible-roles

2. Start and enable the Web Console.

   # systemctl start cockpit
   # systemctl enable cockpit

3. Configure the firewall for the Web Console traffic

   1. Open ports for the cockpit service.

      # firewall-cmd --add-service=cockpit
      # firewall-cmd --add-service=cockpit --permanent

   2. Verify that the cockpit service is allowed by the firewall.

      Ensure that cockpit appears in the output of the following command.

      # firewall-cmd --list-services | grep cockpit

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 each host that you want to access, including the host on which you execute the command, using both the front-end and the back-end FQDNs.

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

   Enter the password for <user>@<hostname> when 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.

   For example, if you are logged in as the root user on server1.example.com, you would run the following commands:

   # ssh-copy-id -i <location>/<keyname>.pub root@server1front.example.com
   # ssh-copy-id -i <location>/<keyname>.pub root@server2front.example.com
   # ssh-copy-id -i <location>/<keyname>.pub root@server3front.example.com
   # ssh-copy-id -i <location>/<keyname>.pub root@server1back.example.com
   # ssh-copy-id -i <location>/<keyname>.pub root@server2back.example.com
   # ssh-copy-id -i <location>/<keyname>.pub root@server3back.example.com

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 packages

   No additional packages are required for Red Hat Hyperconverged Infrastructure for Virtualization, but you can use this tab to install any additional packages you require on the host.

   

5. 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.

   Add Volume

   To add more volumes, click the Add Volume option and it will create a blank entry. Specify the name of the volume to be added and if arbiter volume is required, check the arbiter check box. It is recommended to use the brick path as /gluster_bricks/<volname>/<volname>.

6. 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.

   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.

   1. (Optional) If your system has multipath devices, additional configuration is required.

      1. To use multipath devices

         If you want to use multipath devices in your RHHI for Virtualization deployment, use multipath WWIDs to specify the device. For example, use /dev/mapper/3600508b1001caab032303683327a6a2e instead of /dev/sdb.

      2. To disable multipath device use

         If multipath devices exist in your environment, but you do not want to use them for your RHHI for Virtualization deployment, blacklist the devices.

         1. Create a custom multipath configuration file.

            # mkdir /etc/multipath/conf.d
            # touch /etc/multipath/conf.d/99-custom-multipath.conf

         2. Add the following content to the file, replacing <device> with the name of the device to blacklist:

            blacklist {
              devnode "<device>"
            }

            For example, to blacklist the /dev/sdb device, add the following:

            blacklist {
              devnode "sdb"
            }

         3. Restart multipathd.

            # systemctl restart multipathd

         4. Verify that your disks no longer have multipath names by using the lsblk command.

            If multipath names are still present, reboot hosts.

7. 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.

   

8. 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.

      Network Configuration

      Choose either DHCP or Static from the Network Configuration drop-down list.

      • If you choose DHCP, you must have a DHCP reservation for the Hosted Engine virtual machine so that its host name resolves to the address received from DHCP. Specify its MAC address in the MAC Address field.

      • If you choose Static, enter the following details:

        • VM IP Address - The IP address must belong to the same subnet as the host. For example, if the host is in 10.1.1.0/24, the Hosted Engine virtual machine’s IP must be in the same subnet range (10.1.1.1-254/24).
        • Gateway Address
        • DNS Servers

      Bridge Interface

      Select the Bridge Interface from the drop-down list.

      Root password

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

      Root SSH Access

      Specify whether to allow Root SSH Access.The default value of Root SSH Access is set to Yes.

      Number of Virtual CPUs

      Enter the Number of Virtual CPUs for the virtual machine.

      Memory Size (MiB)

      Enter the Memory Size (MiB). The available memory is displayed next to the input field.

      Note

      Red Hat recommends to retain the values of Root SSH Access, Number of Virtual CPUs and Memory Size to default values.

   2. Optionally expand the Advanced fields.

      

      Root SSH Public Key

      Enter a Root SSH Public Key to use for root access to the Hosted Engine virtual machine.

      Edit Hosts File

      Select or clear the Edit Hosts File check box to specify whether to add entries for the Hosted Engine virtual machine and the base host to the virtual machine’s /etc/hosts file. You must ensure that the host names are resolvable.

      Bridge Name

      Change the management Bridge Name, or accept the default ovirtmgmt.

      Gateway Address

      Enter the Gateway Address for the management bridge.

      Host FQDN

      Enter the Host FQDN of the first host to add to the Manager. This is the front-end FQDN of the base host you are running the deployment on.

      Network Test

      If you have a static network configuration or are using an isolated environment with addresses defined in /etc/hosts, set Network Test to Ping.

   3. 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 an email address for notifications, which requires further configuration after deployment; see Chapter 8, Post-deployment configuration suggestions.

      
   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 can take some time, depending on your configuration details.

   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.