Installation Guide

Procedure

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

   # subscription-manager register

2. Find the Red Hat Enterprise Linux Server and Red Hat Virtualization subscription pools and record the pool IDs:

   # subscription-manager list --available

3. Use the pool IDs to attach the subscriptions to the system:

   # subscription-manager attach --pool=pool_id

   Note

   To view currently attached subscriptions:

   # subscription-manager list --consumed

   To list all enabled repositories:

   # yum repolist

4. Configure the repositories:

   # subscription-manager repos \
       --disable='*' \
       --enable=rhel-7-server-rpms \
       --enable=rhel-7-server-supplementary-rpms \
       --enable=rhel-7-server-rhv-4.2-manager-rpms \
       --enable=rhel-7-server-rhv-4-manager-tools-rpms \
       --enable=rhel-7-server-ansible-2.9-rpms \
       --enable=jb-eap-7-for-rhel-7-server-rpms

1. To ensure all packages are up to date, run the following command on the machine where you are installing the Red Hat Virtualization Manager:

   # yum update

   Note

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

2. Run the following command to install the rhvm package and dependencies.

   # yum install rhvm

Procedure

1. Run the engine-setup command to begin configuration of the Red Hat Virtualization Manager:

   # engine-setup

2. Press Enter to configure the Manager:

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

3. Optionally allow engine-setup to configure the Image I/O Proxy (ovirt-imageio-proxy) to allow the Manager to upload virtual disks into storage domains.

   Configure Image I/O Proxy on this host? (Yes, No) [Yes]:

4. Optionally 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]:

   To configure the websocket proxy on a separate machine, select No and refer to Appendix F, Installing a Websocket Proxy on a Separate Machine for configuration instructions.

   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.

5. Choose whether to configure Data Warehouse on the Manager 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]:

   To configure Data Warehouse on a separate machine, select No and see Installing and Configuring Data Warehouse on a Separate Machine in the Data Warehouse Guide for installation and configuration instructions.

6. Optionally allow access to a virtual machines’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.

7. Optionally install Open Virtual Network (OVN). Selecting Yes will install an OVN central server on the Manager machine, and add it to Red Hat Virtualization as an external network provider. The default cluster will use OVN as its default network provider, and hosts added to the default cluster will automatically be configured to communicate with OVN.

   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.

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

9. 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; iptables is deprecated.

   Setup can automatically configure the firewall on this system.
   Note: automatic configuration of the firewall may overwrite current settings.
   NOTICE: iptables is deprecated and will be removed in future releases
   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.

10. Choose to use either a local or remote PostgreSQL database as the Data Warehouse database:

    Where is the DWH 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 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, input the following values for the preconfigured remote database host:

      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.

11. Choose to use either a local or remote PostgreSQL database as the Manager database:

    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:

    • If you select Remote, input the following values for the preconfigured remote database host:

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

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

    Engine admin password:
    Confirm engine admin password:

13. Select Gluster, Virt, or Both:

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

    Both offers the greatest flexibility. In most cases, select Both. Virt application mode allows you to run virtual machines in the environment; Gluster application mode only allows you to manage GlusterFS from the Administration Portal.

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

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

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

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

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

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

    Note

    This step is skipped if you chose not to configure Data Warehouse on the Manager machine.

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

    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 (recommended when the Manager and Data Warehouse are installed on the same machine).

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

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

    When your environment has been configured, engine-setup displays details about how to access your environment. If you chose to manually configure the firewall, engine-setup provides a custom list of ports that need to be opened, based on the options selected during setup. The engine-setup command also saves your answers to a file that can be used to reconfigure the Manager using the same values, and outputs the location of the log file for the Red Hat Virtualization Manager configuration process.

21. If you intend to link your Red Hat Virtualization environment with a directory server, configure the date and time to synchronize with the system clock used by the directory server to avoid unexpected account expiry issues. See Synchronizing the System Clock with a Remote Server in the Red Hat Enterprise Linux System Administrator’s Guide for more information.
22. Install the certificate authority according to the instructions provided by your browser. You can get the certificate authority’s certificate by navigating to`http://your-manager-fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA`, replacing your-manager-fqdn with the fully qualified domain name (FQDN) that you provided during the installation.

1. In a web browser, navigate to https://your-manager-fqdn/ovirt-engine, replacing your-manager-fqdn with the fully qualified domain name 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 in conjunction with the password that you specified during installation.
4. Select the domain against which to authenticate from the Domain list. 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 will be chosen based on the locale settings of your web browser. If you would like 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.

1. Run the following command on the machine on which the Red Hat Virtualization Manager is installed:

   # engine-cleanup

2. You are prompted whether to remove all Red Hat Virtualization Manager components:

3. Type Yes and press Enter to remove all components:

   Do you want to remove all components? (Yes, No) [Yes]:

4. Type No and press Enter to select the components to remove. You can select whether to retain or remove each component individually:

   Do you want to remove Engine database content? All data will be lost (Yes, No) [No]:
   Do you want to remove PKI keys? (Yes, No) [No]:
   Do you want to remove PKI configuration? (Yes, No) [No]:
   Do you want to remove Apache SSL configuration? (Yes, No) [No]:

5. You are given another opportunity to change your mind and cancel the removal of the Red Hat Virtualization Manager. If you choose to proceed, the ovirt-engine service is stopped, and your environment’s configuration is removed in accordance with the options you selected.

   During execution engine service will be stopped (OK, Cancel) [OK]:
   ovirt-engine is about to be removed, data will be lost (OK, Cancel) [Cancel]:OK

6. Remove the Red Hat Virtualization packages:

   # yum remove rhvm* vdsm-bootstrap

Procedure

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

   # subscription-manager register

2. Find the Red Hat Enterprise Linux Server and Red Hat Virtualization subscription pools and record the pool IDs:

   # subscription-manager list --available

3. Use the pool IDs to attach the subscriptions to the system:

   # subscription-manager attach --pool=pool_id

   Note

   To view currently attached subscriptions:

   # subscription-manager list --consumed

   To list all enabled repositories:

   # yum repolist

4. Configure the repositories:

   # subscription-manager repos \
       --disable='*' \
       --enable=rhel-7-server-rpms \
       --enable=rhel-7-server-supplementary-rpms \
       --enable=rhel-7-server-rhv-4.2-manager-rpms \
       --enable=rhel-7-server-rhv-4-manager-tools-rpms \
       --enable=rhel-7-server-ansible-2.9-rpms \
       --enable=jb-eap-7-for-rhel-7-server-rpms

1. Servers that are not connected to the Internet can access software repositories on other systems using File Transfer Protocol (FTP). To create the FTP repository, install and configure vsftpd:

   1. Install the vsftpd package:

      # yum install vsftpd

   2. Start the vsftpd service, and ensure the service starts on boot:

      # systemctl start vsftpd.service
      # systemctl enable vsftpd.service

   3. Create a sub-directory inside the /var/ftp/pub/ directory. This is where the downloaded packages will be made available:

      # mkdir /var/ftp/pub/rhevrepo

2. Download packages from all configured software repositories to the rhevrepo directory. This includes repositories for all Content Delivery Network subscription pools attached to the system, and any locally configured repositories:

   # reposync -l -p /var/ftp/pub/rhevrepo

   This command downloads a large number of packages, and takes a long time to complete. The -l option enables yum plug-in support.

3. Install the createrepo package:

   # yum install createrepo

4. Create repository metadata for each of the sub-directories where packages were downloaded under /var/ftp/pub/rhevrepo:

   # for DIR in find /var/ftp/pub/rhevrepo -maxdepth 1 -mindepth 1 -type d; do createrepo $DIR; done;

5. Create a repository file, and copy it to the /etc/yum.repos.d/ directory on the offline machine on which you will install the Manager.

   The configuration file can be created manually or with a script. Run the script below on the system hosting the repository, replacing ADDRESS in the baseurl with the IP address or fully qualified domain name of the system hosting the repository:

   #!/bin/sh
   
   REPOFILE="/etc/yum.repos.d/rhev.repo"
   echo -e " " > $REPOFILE
   
   for DIR in `find /var/ftp/pub/rhevrepo -maxdepth 1 -mindepth 1 -type d`;
   do
       echo -e "[`basename $DIR`]"	>> $REPOFILE
       echo -e "name=`basename $DIR`" >> $REPOFILE
       echo -e "baseurl=ftp://_ADDRESS_/pub/rhevrepo/`basename $DIR`" >> $REPOFILE
       echo -e "enabled=1" >> $REPOFILE
       echo -e "gpgcheck=0" >> $REPOFILE
       echo -e "\n" >> $REPOFILE
   done;

6. Install the Manager packages on the offline system. See Section 2.2, “Installing the Red Hat Virtualization Manager Packages” for instructions. Packages are installed from the local repository, instead of from the Content Delivery Network.
7. Configure the Manager. See Section 2.3, “Configuring the Red Hat Virtualization Manager” for initial configuration instructions.
8. Continue with host, storage, and virtual machine configuration.

1. Download the RHVH 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, the Red Hat Virtualization page opens on the Get Started tab.
   4. Under Hypervisor Image, click Download RHVH to access the product download page.
   5. In the Version drop down list, select 4.2.
   6. Choose the latest Hypervisor Image and click Download Now.
   7. 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 RHVH, booting from the prepared installation media.

3. From the boot menu, select Install RHVH 4.2 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.
6. Select a keyboard layout from the Keyboard screen and click Done.

7. Select the device on which to install RHVH from the Installation Destination screen. Optionally, enable encryption. Click Done.

   Important

   Red Hat strongly recommends using the Automatically configure partitioning option. However, if you do select I will configure partitioning, see Section 5.2.1, “Custom Partitioning” for details.

   Note

   For information on preserving local storage domains when reinstalling RHVH, see Upgrading to RHVH While Preserving Local Storage in the Upgrade Guide for Red Hat Virtualization 4.0 for more details.

8. Select a network from the Network & Host Name screen and click Configure…​ to configure the connection details. Enter a host name in the Host name field, and click Done.
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 RHVH installs.

    Warning

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

12. Click Reboot to complete the installation.

    Note

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

13. Register the system to receive updates:

    • If you are registering RHVH with the Content Delivery Network:

      1. Log in to the Cockpit user interface at https://HostFQDNorIP: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

    • If you are registering RHVH with Red Hat Satellite 6:

      1. Log in to the Cockpit user interface at https://HostFQDNorIP:9090.
      2. Click Terminal.

      3. Register RHVH with Red Hat Satellite 6:

           # rpm -Uvh http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm
           # subscription-manager register --org="org_id"
           # subscription-manager list --available
           # subscription-manager attach --pool=pool_id
           # subscription-manager repos \
             --disable='*' \
             --enable=rhel-7-server-rhvh-4-rpms

Procedure

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

   # subscription-manager register

2. Find the Red Hat Enterprise Linux Server and Red Hat Virtualization subscription pools and record the pool IDs:

   # subscription-manager list --available

3. Use the pool IDs to attach the subscriptions to the system:

   # subscription-manager attach --pool=poolid

   Note

   To view currently attached subscriptions:

   # subscription-manager list --consumed

   To list all enabled repositories:

   # yum repolist

4. Configure the repositories:

   # subscription-manager repos \
       --disable='*' \
       --enable=rhel-7-server-rpms \
       --enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
       --enable=rhel-7-server-ansible-2.9-rpms

   For Red Hat Enterprise Linux 7 hosts, little endian, on IBM POWER8 hardware:

   # subscription-manager repos \
       --disable='*' \
       --enable=rhel-7-server-rhv-4-mgmt-agent-for-power-le-rpms \
       --enable=rhel-7-for-power-le-rpms

   For Red Hat Enterprise Linux 7 hosts, little endian, on IBM POWER9 hardware:

   # subscription-manager repos \
       --disable='*' \
       --enable=rhel-7-server-rhv-4-mgmt-agent-for-power-9-rpms \
       --enable=rhel-7-for-power-9-rpms

5. Ensure that all packages currently installed are up to date:

   # yum update

6. Reboot the machine.

1. By default, when adding a host to the Red Hat Virtualization Manager, the Manager configures the required firewall ports. See ] for details. However, if you disable Automatically configure host firewall when adding the host, manually configure the firewall according to xref:host-firewall-requirements_RHV_install[.

2. Install the dashboard packages:

   # yum install cockpit-ovirt-dashboard

3. Enable and start the cockpit.socket service:

   # systemctl enable cockpit.socket
   # systemctl start cockpit.socket

4. You can log in to the Cockpit user interface at https://HostFQDNorIP:9090.

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

4. Use the Data Center drop-down menu to select an FCP data center.

   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 menus. The storage domain types that are not compatible with the chosen data center are not available.

6. Select an active host in the Use 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 to create the storage domain and close the window.