Chapter 5. Installing the Red Hat Virtualization Manager

The RHV-M Appliance is installed during the deployment process; however, if required, you can install it on the deployment host before starting the installation:

# yum install rhvm-appliance

Manually installing the Manager virtual machine is not supported.

5.1. Deploying the Self-Hosted Engine Using Cockpit

Deploy a self-hosted engine, using Cockpit to collect the details of your environment. This is the recommended method. Cockpit is enabled by default on Red Hat Virtualization Hosts, and can be installed on Red Hat Enterprise Linux hosts.

Prerequisites

  • FQDNs prepared for your Manager and the deployment host. Forward and reverse lookup records must both be set in the DNS.

Procedure

  1. Log in to Cockpit at https://HostIPorFQDN:9090 and click VirtualizationHosted Engine.
  2. Click Start under the Hosted Engine option.
  3. Enter the details for the Manager virtual machine:

    1. Enter the Engine VM FQDN. This is the FQDN for the Manager virtual machine, not the base host.
    2. Enter a MAC Address for the Manager virtual machine, or accept a randomly generated one.
    3. Choose either DHCP or Static from the Network Configuration drop-down list.

      Note

      For IPv6, Red Hat Virtualization supports only static addressing.

      • If you choose DHCP, you must have a DHCP reservation for the Manager 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 Manager virtual machine’s IP must be in the same subnet range (10.1.1.1-254/24).
        • Gateway Address
        • DNS Servers
    4. Select the Bridge Interface from the drop-down list.
    5. Enter and confirm the virtual machine’s Root Password.
    6. Specify whether to allow Root SSH Access.
    7. Enter the Number of Virtual CPUs for the virtual machine.
    8. Enter the Memory Size (MiB). The available memory is displayed next to the input field.
  4. Optionally expand the Advanced fields:

    1. Enter a Root SSH Public Key to use for root access to the Manager virtual machine.
    2. Select or clear the Edit Hosts File check box to specify whether to add entries for the Manager virtual machine and the base host to the virtual machine’s /etc/hosts file. You must ensure that the host names are resolvable.
    3. Change the management Bridge Name, or accept the default ovirtmgmt.
    4. Enter the Gateway Address for the management bridge.
    5. Enter the Host FQDN of the first host to add to the Manager. This is the FQDN of the base host you are running the deployment on.
  5. Click Next.
  6. Enter and confirm the Admin Portal Password for the admin@internal user.
  7. Configure event notifications:

    1. Enter the Server Name and Server Port Number of the SMTP server.
    2. Enter the Sender E-Mail Address.
    3. Enter the Recipient E-Mail Addresses.
  8. Click Next.
  9. Review the configuration of the Manager and its virtual machine. If the details are correct, click Prepare VM.
  10. When the virtual machine installation is complete, click Next.
  11. Select the Storage Type from the drop-down list, and enter the details for the self-hosted engine storage domain:

    • For NFS:

      1. Enter the full address and path to the storage in the Storage Connection field.
      2. If required, enter any Mount Options.
      3. Enter the Disk Size (GiB).
      4. Select the NFS Version from the drop-down list.
      5. Enter the Storage Domain Name.
    • For iSCSI:

      1. Enter the Portal IP Address, Portal Port, Portal Username, and Portal Password.
      2. Click Retrieve Target List and select a target. You can only select one iSCSI target during the deployment, but multipathing is supported to connect all portals of the same portal group.

        Note

        To specify more than one iSCSI target, you must enable multipathing before deploying the self-hosted engine. See Red Hat Enterprise Linux DM Multipath for details. There is also a Multipath Helper tool that generates a script to install and configure multipath with different options.

      3. Enter the Disk Size (GiB).
      4. Enter the Discovery Username and Discovery Password.
    • For Fibre Channel:

      1. Enter the LUN ID. The host bus adapters must be configured and connected, and the LUN must not contain any existing data. To reuse an existing LUN, see Reusing LUNs in the Administration Guide.
      2. Enter the Disk Size (GiB).
    • For Red Hat Gluster Storage:

      1. Enter the full address and path to the storage in the Storage Connection field.
      2. If required, enter any Mount Options.
      3. Enter the Disk Size (GiB).
  12. Click Next.
  13. Review the storage configuration. If the details are correct, click Finish Deployment.
  14. When the deployment is complete, click Close.

    One data center, cluster, host, storage domain, and the Manager virtual machine are already running. You can log in to the Administration Portal to add further resources.

  15. Optionally, add a directory server using the ovirt-engine-extension-aaa-ldap-setup interactive setup script so you can add additional users to the environment. For more information, see Configuring an External LDAP Provider in the Administration Guide.

The self-hosted engine’s status is displayed in Cockpit’s VirtualizationHosted Engine tab. The Manager virtual machine, the host running it, and the self-hosted engine storage domain are flagged with a gold crown in the Administration Portal.

Enabling the Red Hat Virtualization Manager repositories is not part of the automated installation. Log in to the Manager virtual machine to register it with the Content Delivery Network:

5.2. Enabling the Red Hat Virtualization Manager Repositories

Register the system with Red Hat Subscription Manager, attach the Red Hat Virtualization Manager subscription, and enable Manager repositories.

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:

    # 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.3-manager-rpms \
        --enable=rhel-7-server-rhv-4-manager-tools-rpms \
        --enable=rhel-7-server-ansible-2.9-rpms \
        --enable=jb-eap-7.2-for-rhel-7-server-rpms

Log in to the Administration Portal, where you can add hosts and storage to the environment:

5.3. Connecting to the Administration Portal

Access the Administration Portal using a web browser.

  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.

To log out of the Red Hat Virtualization Administration Portal, click your user name in the header bar and click Sign Out. You are logged out of all portals and the Manager welcome screen displays.