Procedure

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

   Note

   If you are using an IPv6 network, use an IPv6 transition mechanism to access the Content Delivery Network and subscription manager.

2. Find the Red Hat Virtualization Manager subscription pool and record the pool ID:

   # subscription-manager list --available

3. Use the pool ID to attach the subscription to the system:

   # subscription-manager attach --pool=pool_id

   Note

   To view currently attached subscriptions:

   # subscription-manager list --consumed

   To list all enabled repositories:

   # dnf repolist

4. Configure the repositories:

   # subscription-manager repos \
       --disable='*' \
       --enable=rhel-8-for-x86_64-baseos-eus-rpms \
       --enable=rhel-8-for-x86_64-appstream-eus-rpms \
       --enable=rhv-4.4-manager-for-rhel-8-x86_64-rpms \
       --enable=fast-datapath-for-rhel-8-x86_64-rpms \
       --enable=jb-eap-7.4-for-rhel-8-x86_64-rpms \
       --enable=openstack-16.2-cinderlib-for-rhel-8-x86_64-rpms \
       --enable=rhceph-4-tools-for-rhel-8-x86_64-rpms \
       --enable=rhel-8-for-x86_64-appstream-tus-rpms \
       --enable=rhel-8-for-x86_64-baseos-tus-rpms

5. Set the RHEL version to 8.6:

   # subscription-manager release --set=8.6

6. Enable the pki-deps module.

   # dnf module -y enable pki-deps

7. Enable version 12 of the postgresql module.

   # dnf module -y enable postgresql:12

8. Enable version 14 of the nodejs module:

   # dnf module -y enable nodejs:14

9. Synchronize installed packages to update them to the latest available versions.

   # dnf distro-sync --nobest

Procedure

1. Ensure all packages are up to date:

   # dnf upgrade --nobest

   Note

   Reboot the machine if any kernel-related packages were updated.

2. Install the rhvm package and dependencies.

   # dnf install rhvm

3. Run the engine-setup command to begin configuring the Red Hat Virtualization Manager:

   # engine-setup

4. Optional: Type Yes and press Enter to set up Cinderlib integration on this machine:

   Set up Cinderlib integration
   (Currently in tech preview)
   (Yes, No) [No]:

   Important

   Cinderlib is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information on Red Hat Technology Preview features support scope, see Red Hat Technology Preview Features Support Scope.

5. Press Enter to configure the Manager on this machine:

   Configure Engine on this host (Yes, No) [Yes]:

6. Optional: Install Open Virtual Network (OVN). Selecting Yes installs an OVN server on the Manager machine and adds it to Red Hat Virtualization as an external network provider. This action also configures the Default cluster to use OVN as its default network provider.

   Important

   Also see the "Next steps" in Adding Open Virtual Network (OVN) as an External Network Provider in the Administration Guide.

   Configuring ovirt-provider-ovn also sets the Default cluster’s default network provider to ovirt-provider-ovn.
   Non-Default clusters may be configured with an OVN after installation.
   Configure ovirt-provider-ovn (Yes, No) [Yes]:

   For more information on using OVN networks in Red Hat Virtualization, see Adding Open Virtual Network (OVN) as an External Network Provider in the Administration Guide.

7. Optional: Allow engine-setup to configure a WebSocket Proxy server for allowing users to connect to virtual machines through the noVNC console:

   Configure WebSocket Proxy on this machine? (Yes, No) [Yes]:

   Important

   The WebSocket Proxy and noVNC are Technology Preview features only. Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information see Red Hat Technology Preview Features Support Scope.

8. Choose whether to configure Data Warehouse on this machine.

   Please note: Data Warehouse is required for the engine. If you choose to not configure it on this host, you have to configure it on a remote host, and then configure the engine on this host so that it can access the database of the remote Data Warehouse host.
   Configure Data Warehouse on this host (Yes, No) [Yes]:

   Important

   Red Hat only supports installing the Data Warehouse database, the Data Warehouse service, and Grafana all on the same machine as each other.

9. Press Enter to configure Grafana on the Manager:

   Configure Grafana on this host (Yes, No) [Yes]:

10. Optional: Allow access to a virtual machine’s serial console from the command line.

    Configure VM Console Proxy on this host (Yes, No) [Yes]:

    Additional configuration is required on the client machine to use this feature. See Opening a Serial Console to a Virtual Machine in the Virtual Machine Management Guide.

11. Press Enter to accept the automatically detected host name, or enter an alternative host name and press Enter. Note that the automatically detected host name may be incorrect if you are using virtual hosts.

    Host fully qualified DNS name of this server [autodetected host name]:

12. The engine-setup command checks your firewall configuration and offers to open the ports used by the Manager for external communication, such as ports 80 and 443. If you do not allow engine-setup to modify your firewall configuration, you must manually open the ports used by the Manager. firewalld is configured as the firewall manager.

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

    If you choose to automatically configure the firewall, and no firewall managers are active, you are prompted to select your chosen firewall manager from a list of supported options. Type the name of the firewall manager and press Enter. This applies even in cases where only one option is listed.

13. Specify whether to configure the Data Warehouse database on this machine, or on another machine:

    Where is the DWH database located? (Local, Remote) [Local]:

    • If you select Local, the engine-setup script can configure your database automatically (including adding a user and a database), or it can connect to a preconfigured local database:

      Setup can configure the local postgresql server automatically for the DWH to run. This may conflict with existing applications.
      Would you like Setup to automatically configure postgresql and create DWH database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:

      • If you select Automatic by pressing Enter, no further action is required here.

      • If you select Manual, input the following values for the manually configured local database:

        DWH database secured connection (Yes, No) [No]:
        DWH database name [ovirt_engine_history]:
        DWH database user [ovirt_engine_history]:
        DWH database password:

        Note

        engine-setup requests these values after the Manager database is configured in the next step.

    • If you select Remote (for example, if you are installing the Data Warehouse service on the Manager machine, but have configured a remote Data Warehouse database), input the following values for the remote database server:

      DWH database host [localhost]:
      DWH database port [5432]:
      DWH database secured connection (Yes, No) [No]:
      DWH database name [ovirt_engine_history]:
      DWH database user [ovirt_engine_history]:
      DWH database password:

      Note

      engine-setup requests these values after the Manager database is configured in the next step.

    • If you select Remote, you are prompted to enter the username and password for the Grafana database user:

      Grafana database user [ovirt_engine_history_grafana]:
      Grafana database password:

14. Specify whether to configure the Manager database on this machine, or on another machine:

    Where is the Engine database located? (Local, Remote) [Local]:

    • If you select Local, the engine-setup command can configure your database automatically (including adding a user and a database), or it can connect to a preconfigured local database:

      Setup can configure the local postgresql server automatically for the engine to run. This may conflict with existing applications.
      Would you like Setup to automatically configure postgresql and create Engine database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:

      • If you select Automatic by pressing Enter, no further action is required here.

      • If you select Manual, input the following values for the manually configured local database:

        Engine database secured connection (Yes, No) [No]:
        Engine database name [engine]:
        Engine database user [engine]:
        Engine database password:

15. Set a password for the automatically created administrative user of the Red Hat Virtualization Manager:

    Engine admin password:
    Confirm engine admin password:

16. Select Gluster, Virt, or Both:

    Application mode (Both, Virt, Gluster) [Both]:

    • Both - offers the greatest flexibility. In most cases, select Both.
    • Virt - allows you to run virtual machines in the environment.

    • Gluster - only allows you to manage GlusterFS from the Administration Portal.

      Note

      GlusterFS Storage is deprecated, and will no longer be supported in future releases.

17. If you installed the OVN provider, you can choose to use the default credentials, or specify an alternative.

    Use default credentials (admin@internal) for ovirt-provider-ovn (Yes, No) [Yes]:
    oVirt OVN provider user[admin@internal]:
    oVirt OVN provider password:

18. Set the default value for the wipe_after_delete flag, which wipes the blocks of a virtual disk when the disk is deleted.

    Default SAN wipe after delete (Yes, No) [No]:

19. The Manager uses certificates to communicate securely with its hosts. This certificate can also optionally be used to secure HTTPS communications with the Manager. Provide the organization name for the certificate:

    Organization name for certificate [autodetected domain-based name]:

20. Optionally allow engine-setup to make the landing page of the Manager the default page presented by the Apache web server:

    Setup can configure the default page of the web server to present the application home page. This may conflict with existing applications.
    Do you wish to set the application as the default web page of the server? (Yes, No) [Yes]:

21. By default, external SSL (HTTPS) communication with the Manager is secured with the self-signed certificate created earlier in the configuration to securely communicate with hosts. Alternatively, choose another certificate for external HTTPS connections; this does not affect how the Manager communicates with hosts:

    Setup can configure apache to use SSL using a certificate issued from the internal CA.
    Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:

22. You can specify a unique password for the Grafana admin user, or use same one as the Manager admin password:

    Use Engine admin password as initial Grafana admin password (Yes, No) [Yes]:

23. Choose how long Data Warehouse will retain collected data:

    Please choose Data Warehouse sampling scale:
    (1) Basic
    (2) Full
    (1, 2)[1]:

    Full uses the default values for the data storage settings listed in the Data Warehouse Guide (recommended when Data Warehouse is installed on a remote server).

    Basic reduces the values of DWH_TABLES_KEEP_HOURLY to 720 and DWH_TABLES_KEEP_DAILY to 0, easing the load on the Manager machine. Use Basic when the Manager and Data Warehouse are installed on the same machine.

24. Review the installation settings, and press Enter to accept the values and proceed with the installation:

    Please confirm installation settings (OK, Cancel) [OK]:

1. In a web browser, navigate to https://manager-fqdn/ovirt-engine, replacing manager-fqdn with the FQDN that you provided during installation.

   Note

   You can access the Administration Portal using alternate host names or IP addresses. To do so, you need to add a configuration file under /etc/ovirt-engine/engine.conf.d/. For example:

   # vi /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf
   SSO_ALTERNATE_ENGINE_FQDNS="alias1.example.com alias2.example.com"

   The list of alternate host names needs to be separated by spaces. You can also add the IP address of the Manager to the list, but using IP addresses instead of DNS-resolvable host names is not recommended.

2. Click Administration Portal. An SSO login page displays. SSO login enables you to log in to the Administration and VM Portal at the same time.
3. Enter your User Name and Password. If you are logging in for the first time, use the user name admin along with the password that you specified during installation.
4. Select the Domain to authenticate against. If you are logging in using the internal admin user name, select the internal domain.
5. Click Log In.
6. You can view the Administration Portal in multiple languages. The default selection is chosen based on the locale settings of your web browser. If you want to view the Administration Portal in a language other than the default, select your preferred language from the drop-down list on the welcome page.

Procedure

1. From the Administration Portal, click Compute → Hosts.
2. Click New.
3. Use the drop-down list to select the Data Center and Host Cluster for the new host.
4. Enter the Name and the Address of the new host. The standard SSH port, port 22, is auto-filled in the SSH Port field.

5. Select an authentication method to use for the Manager to access the host.

   • Enter the root user’s password to use password authentication.
   • Alternatively, copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication.

6. Optionally, click the Advanced Parameters button to change the following advanced host settings:

   • Disable automatic firewall configuration.
   • Add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
7. Optionally configure power management, where the host has a supported power management card. For information on power management configuration, see Host Power Management Settings Explained in the Administration Guide.
8. Click OK.

Prerequisites

1. Install the NFS utils package.

   # dnf install nfs-utils -y

2. To check the enabled versions:

   # cat /proc/fs/nfsd/versions

3. Enable the following services:

   # systemctl enable nfs-server
   # systemctl enable rpcbind

Procedure

1. Create the group kvm:

   # groupadd kvm -g 36

2. Create the user vdsm in the group kvm:

   # useradd vdsm -u 36 -g kvm

3. Create the storage directory and modify the access rights.

   # mkdir /storage
   # chmod 0755 /storage
   # chown 36:36 /storage/

4. Add the storage directory to /etc/exports with the relevant permissions.

   # vi /etc/exports
   # cat /etc/exports
    /storage *(rw)

5. Restart the following services:

   # systemctl restart rpcbind
   # systemctl restart nfs-server

6. To see which export are available for a specific IP address:

   # exportfs
    /nfs_server/srv
                  10.46.11.3/24
    /nfs_server       <world>

Procedure for Red Hat Enterprise Linux hosts

1. On the host, create the directory to be used for the local storage:

   # mkdir -p /data/images

2. Ensure that the directory has permissions allowing read/write access to the vdsm user (UID 36) and kvm group (GID 36):

   # chown 36:36 /data /data/images
   # chmod 0755 /data /data/images

1. Create a local storage directory:

   # mkdir /data
   # lvcreate -L $SIZE rhvh -n data
   # mkfs.ext4 /dev/mapper/rhvh-data
   # echo "/dev/mapper/rhvh-data /data ext4 defaults,discard 1 2" >> /etc/fstab
   # mount /data

2. Mount the new local storage:

   # mount -a

3. Ensure that the directory has permissions allowing read/write access to the vdsm user (UID 36) and kvm group (GID 36):

   # chown 36:36 /data /rhvh-data
   # chmod 0755 /data /rhvh-data

Procedure

1. Create a new configuration file in the /etc/multipath/conf.d directory.
2. Copy the individual setting you want to override from /etc/multipath.conf to the new configuration file in /etc/multipath/conf.d/<my_device>.conf. Remove any comment marks, edit the setting values, and save your changes.

3. Apply the new configuration settings by entering:

   # systemctl reload multipathd

   Note

   Do not restart the multipathd service. Doing so generates errors in the VDSM logs.

Verification steps

1. Test that the new configuration performs as expected on a non-production cluster in a variety of failure scenarios. For example, disable all of the storage connections.
2. Enable one connection at a time and verify that doing so makes the storage domain reachable.

Procedure

1. In the Administration Portal, click Storage → Domains.
2. Click New Domain.
3. Enter a Name for the storage domain.
4. Accept the default values for the Data Center, Domain Function, Storage Type, Format, and Host lists.
5. Enter the Export Path to be used for the storage domain. The export path should be in the format of 123.123.0.10:/data (for IPv4), [2001:0:0:0:0:0:0:5db1]:/data (for IPv6), or domain.example.com:/data.

6. Optionally, you can configure the advanced parameters:

   1. Click Advanced Parameters.
   2. Enter a percentage value into the Warning Low Space Indicator field. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged.
   3. Enter a GB value into the Critical Space Action Blocker field. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked.
   4. Select the Wipe After Delete check box to enable the wipe after delete option. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
7. Click OK.

Procedure

1. Click Storage → Domains.
2. Click New Domain.
3. Enter the Name of the new storage domain.
4. Select a Data Center from the drop-down list.
5. Select Data as the Domain Function and iSCSI as the Storage Type.

6. Select an active host as the Host.

   Important

   Communication to the storage domain is from the selected host and not directly from the Manager. Therefore, all hosts must have access to the storage device before the storage domain can be configured.

7. The Manager can map iSCSI targets to LUNs or LUNs to iSCSI targets. The New Domain window automatically displays known targets with unused LUNs when the iSCSI storage type is selected. If the target that you are using to add storage does not appear, you can use target discovery to find it; otherwise proceed to the next step.

   1. Click Discover Targets to enable target discovery options. When targets have been discovered and logged in to, the New Domain window automatically displays targets with LUNs unused by the environment.

      Note

      LUNs used externally for the environment are also displayed.

      You can use the Discover Targets options to add LUNs on many targets or multiple paths to the same LUNs.

      Important

      If you use the REST API method discoveriscsi to discover the iscsi targets, you can use an FQDN or an IP address, but you must use the iscsi details from the discovered targets results to log in using the REST API method iscsilogin. See discoveriscsi in the REST API Guide for more information.

   2. Enter the FQDN or IP address of the iSCSI host in the Address field.
   3. Enter the port with which to connect to the host when browsing for targets in the Port field. The default is 3260.

   4. If CHAP is used to secure the storage, select the User Authentication check box. Enter the CHAP user name and CHAP password.

      Note

      You can define credentials for an iSCSI target for a specific host with the REST API. See StorageServerConnectionExtensions: add in the REST API Guide for more information.

   5. Click Discover.

   6. Select one or more targets from the discovery results and click Login for one target or Login All for multiple targets.

      Important

      If more than one path access is required, you must discover and log in to the target through all the required paths. Modifying a storage domain to add additional paths is currently not supported.

      Important

      When using the REST API iscsilogin method to log in, you must use the iscsi details from the discovered targets results in the discoveriscsi method. See iscsilogin in the REST API Guide for more information.

8. Click the + button next to the desired target. This expands the entry and displays all unused LUNs attached to the target.
9. Select the check box for each LUN that you are using to create the storage domain.

10. Optionally, you can configure the advanced parameters:

    1. Click Advanced Parameters.
    2. Enter a percentage value into the Warning Low Space Indicator field. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged.
    3. Enter a GB value into the Critical Space Action Blocker field. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked.
    4. Select the Wipe After Delete check box to enable the wipe after delete option. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
    5. Select the Discard After Delete check box to enable the discard after delete option. This option can be edited after the domain is created. This option is only available to block storage domains.
11. Click OK.

Procedure

1. Click Storage → Domains.
2. Click New Domain.
3. Enter the Name of the storage domain.

4. Select an FCP Data Center from the drop-down list.

   If you do not yet have an appropriate FCP data center, select (none).

5. Select the Domain Function and the Storage Type from the drop-down lists. The storage domain types that are not compatible with the chosen data center are not available.

6. Select an active host in the Host field. If this is not the first data domain in a data center, you must select the data center’s SPM host.

   Important

   All communication to the storage domain is through the selected host and not directly from the Red Hat Virtualization Manager. At least one active host must exist in the system and be attached to the chosen data center. All hosts must have access to the storage device before the storage domain can be configured.

7. The New Domain window automatically displays known targets with unused LUNs when Fibre Channel is selected as the storage type. Select the LUN ID check box to select all of the available LUNs.

8. Optionally, you can configure the advanced parameters.

   1. Click Advanced Parameters.
   2. Enter a percentage value into the Warning Low Space Indicator field. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged.
   3. Enter a GB value into the Critical Space Action Blocker field. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked.
   4. Select the Wipe After Delete check box to enable the wipe after delete option. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
   5. Select the Discard After Delete check box to enable the discard after delete option. This option can be edited after the domain is created. This option is only available to block storage domains.
9. Click OK.

Procedure

1. Click Storage → Domains.
2. Click New Domain.
3. Enter the Name for the storage domain.
4. Select the Data Center to be associated with the storage domain. The data center selected must be of type POSIX (POSIX compliant FS). Alternatively, select (none).

5. Select Data from the Domain Function drop-down list, and POSIX compliant FS from the Storage Type drop-down list.

   If applicable, select the Format from the drop-down menu.

6. Select a host from the Host drop-down list.
7. Enter the Path to the POSIX file system, as you would normally provide it to the mount command.
8. Enter the VFS Type, as you would normally provide it to the mount command using the -t argument. See man mount for a list of valid VFS types.
9. Enter additional Mount Options, as you would normally provide them to the mount command using the -o argument. The mount options should be provided in a comma-separated list. See man mount for a list of valid mount options.

10. Optionally, you can configure the advanced parameters.

    1. Click Advanced Parameters.
    2. Enter a percentage value in the Warning Low Space Indicator field. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged.
    3. Enter a GB value in the Critical Space Action Blocker field. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked.
    4. Select the Wipe After Delete check box to enable the wipe after delete option. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist.
11. Click OK.

Procedure

1. Click Compute → Hosts and select the host.
2. Click Management → Maintenance and OK. The host’s status changes to Maintenance.
3. Click Management → Configure Local Storage.
4. Click the Edit buttons next to the Data Center, Cluster, and Storage fields to configure and name the local storage domain.
5. Set the path to your local storage in the text entry field.
6. If applicable, click the Optimization tab to configure the memory optimization policy for the new local storage cluster.
7. Click OK.

Verification

1. Click Storage → Domains.
2. Locate the local storage domain you just added.