3.5. Configuring Red Hat Enterprise Virtualization Manager

Summary
Once package installation is complete the Red Hat Enterprise Virtualization Manager must be configured. The rhevm-setup command is provided to assist with this task. The script asks you a series of questions, the answers to which form the basis for system configuration. Once all required values have been provided the updated configuration is applied and the Red Hat Enterprise Virtualization Manager services are started.

Procedure 3.4. Configuring Red Hat Enterprise Virtualization Manager

  1. Start setup script

    To begin configuring the system run rhevm-setup as the root user.
    # rhevm-setup
  2. Stop JBoss Enterprise Application Platform

    To install Red Hat Enterprise Virtualization Manager the JBoss Enterprise Application Platform needs to first be stopped. Stopping this service allows it to be configured for use with the Manager. Type yes to stop the service and proceed with Manager installation.
    In order to proceed the installer must stop the JBoss service
    Would you like to stop the JBoss service? (yes|no):
    
  3. Override Apache configuration

    Red Hat Enterprise Virtualization uses the mod_proxy module for the Apache web server (httpd) to redirect network traffic from the HTTP and HTTPS ports which you select, to the application server that the Manager runs on. If the rhevm-setup script detects an existing httpd configuration then you will need to decide whether or not to override it:
    RHEV Manager uses httpd to proxy requests to the application server.
    It looks like the httpd installed locally is being actively used.
    The installer can override current configuration .
    Alternatively you can use JBoss directly (on ports higher than 1024)
    Do you wish to override current httpd configuration and restart the service? ['yes'| 'no']  [yes] :
    • If you do not receive this message, there is no existing httpd configuration on the system and the script will move to the next step.
    • If you do receive this message, you must:
      • enter yes if you wish to configure the Manager to listen to HTTP and/or HTTPS ports lower than port 1024; or
      • enter no if you do not wish to configure the Manager to listen to HTTP and/or HTTPS ports lower than port 1024, leaving the existing httpd configuration intact.
  4. Set Port for HTTP

    The script prompts for entry of the port to use for HTTP communication. To use the default value, 80, press Enter. To use an alternative value enter it in the field, and then press Enter.
    HTTP Port  [80] :
    The port you select also appears in the URL that must be used to access the Red Hat Enterprise Virtualization Manager over HTTP.
  5. Set Port for HTTPS

    The script prompts for entry of the port to use for HTTPS communication. To use the default value, 443, press Enter. To use an alternative value enter it in the field, and then press Enter.
    HTTPS Port  [443] :
    Where a port other than 443 is selected it changes the URL that must be used to access the Red Hat Enterprise Virtualization Manager over HTTPS.
  6. Set Fully Qualified Domain Name (FQDN)

    The script prompts for entry of the system's fully qualified domain name. This name should be resolvable via both forward and reverse DNS lookup. The script attempts to determine the fully qualified domain name automatically. The value identified is listed in square brackets as the default setting for the fully qualified domain name, based on your setup.
    Host fully qualified domain name. Note: this name should be fully resolvable  [rhevm31.demo.redhat.com] :
    Where the automatically determined fully qualified domain name is correct, press Enter to use the value and continue. Where the automatically determined fully qualified domain name is not correct, enter the correct value and press Enter to use the new value and continue.
  7. Set Administrator Password

    The script creates an authentication domain internal to the Red Hat Enterprise Virtualization Manager for the default administrative account. The domain is named internal, the administrative user is called admin. External authentication domains are added as a post-installation step using the rhevm-manage-domains command.
    You must choose a password for the admin user. You will be asked to enter it a second time to confirm your selection.
    Password for Administrator (admin@internal) :
  8. Set Organization Name

    The script prompts for entry of the Organization Name. The Organization Name appears in the Subject field of the certificate used to secure communications with the Red Hat Enterprise Virtualization Manager.
    Organization Name for the Certificate [demo.redhat.com] :
  9. Configure Default Storage Type

    The script prompts for selection of the default storage type. This is the storage type that is used for the Default data center. You are able to add further data centers that use different storage types from the Administration Portal at any time.
    The default storage type you will be using  ['NFS'| 'FC'| 'ISCSI']  [NFS] :
    The default selection is Network File System (NFS). The other available values are:
    • Fibre Channel (FC), and
    • Internet Small Computer System Interface (ISCSI).
    The NFS, FC, and ISCSI options are used to connect to remote storage. Red Hat Enterprise Virtualization also supports the LOCALFS storage type which allows the use of local storage attached to the virtualization hosts. The LOCALFS storage type is not however a supported choice for use in the Default data center.
    To use the default selection, NFS, press Enter. To select FC, or ISCSI then enter the desired value.
  10. Select database location

    Red Hat Enterprise Virtualization supports the use of a local database on the management system, or a remote database provided elsewhere in your environment. The setup script prompts you to indicate whether you wish to use a local database, which is the default option, or a remote database:
    Enter DB type for installation ['remote'| 'local']  [local] :
    • Enter local to have the setup script create a local PostgreSQL database server for the Manager.
      The script prompts for entry of a password to use for the local Red Hat Enterprise Virtualization Manager database. Enter the desired password. You will be asked to enter the password again to confirm it.
      Database password (required for secure authentication with the locally created database) :
    • Enter remote to have the script use a remote database server for the Manager.
      1. You will be prompted to provide:
        • the IP address or hostname of the remote database server,
        • the port number on which the remote database server is listening,
        • the administrative user name for the remote database server, and
        • the administrative user's password.
        The database server that you specify must be configured to allow remote connections. Additionally, the database user that you select must have the permissions required to create databases on the remote database server.
        Enter DB type for installation ['remote'| 'local']  [local] : remote
        Enter the host IP or host name where DB is running: database.demo.redhat.com
        Enter DB port number  [5432] : 5432
        Enter DB admin user name  [postgres] :
        Remote database password :
        Confirm password :
        
      2. Secure connection

        You can configure Red Hat Enterprise Virtualization Manager to use a secure connection, encrypted using SSL when connecting to the remote database server. You must ensure that the remote database server is configured to support secure connections before enabling them.
        Configure secure connection? (make sure SSL is configured on remote database) ['yes'| 'no']  [no] :
        Enter yes to use secure database connections.
      The setup script will connect to the remote database server to verify the details that you provided are correct.
  11. Configure NFS ISO Domain

    The script asks whether or not an NFS share should be configured on the server and used as an ISO storage domain.
    Configure NFS share on this server to be used as an ISO Domain? ['yes'| 'no']  [yes] :
    An ISO storage domain is used to store copies of removable media for use when provisioning and using virtual machines. The Red Hat Enterprise Virtualization Manager is able to use either an ISO storage domain on the system it is installed to or one that exists on remote storage. In either case the ISO storage domain must be accessible via NFS. The ability to configure an ISO storage domain is also available from the Administration Portal after installation.
    To take the default action, which is to configure an NFS share for use as an ISO storage domain, press Enter. To skip this step type no and press Enter.
    If you chose to configure an NFS share then you will also need to provide both a path and a display name for it. The path is the location on the local file system where the NFS share must be created. The directory must not already exist.
    Local ISO domain path  [/usr/local/exports/iso] :
    The ISO domain will be created and exported as an NFS share. It will be shown as active in the Red Hat Enterprise Virtualization Manager once the first active virtualization host has been added to the Default data center.
  12. Configure Firewall

    The Red Hat Enterprise Virtualization Manager requires that network traffic on a number of ports be allowed through the system's firewall. The rhevm-setup script is able to configure this automatically, but selecting this option overrides any existing firewall configuration. Where there is an existing firewall configuration that needs to be maintained you must manually configure the firewall to include the additional rules required by the Red Hat Enterprise Virtualization Manager.
    Firewall ports need to be opened.
    The installer can configure iptables automatically overriding the current configuration. The old configuration will be backed up.
    Alternately you can configure the firewall later using an example iptables file found under /etc/ovirt-engine/iptables.example
    Configure iptables ? ['yes'| 'no']:
    
    • To proceed with automatic firewall configuration type yes and then press Enter.
    • To skip automatic firewall configuration type no and then press Enter. You will need to add rules equivalent to those found in /etc/ovirt-engine/iptables.example to your iptables configuration.
  13. Confirm Configuration

    You have now provided the script with all the information required to complete configuration of the Red Hat Enterprise Virtualization Manager. The values which you entered are displayed for confirmation.

    Example 3.2. Configuration Confirmation Screen

    RHEV Manager will be installed using the following configuration:
    =================================================================
    override-httpd-config:         yes
    http-port:                     80
    https-port:                    443
    host-fqdn:                     rhevm31.demo.redhat.com
    auth-pass:                     ********
    org-name:                      demo.redhat.com
    default-dc-type:               NFS
    db-remote-install:             local
    db-local-pass:                 ********
    nfs-mp:                        /usr/local/exports/iso
    config-nfs:                    yes
    override-iptables:             yes
    Proceed with the configuration listed above? (yes|no): yes
    

    • To permanently apply the configuration values listed type yes and then press Enter to apply the configuration.
    • If one or more of the configuration values listed is incorrect type no and then Enter to revisit the configuration.
    The configuration values are applied. A number of services need to be started and as a result this step takes some time. Do not terminate the installation once application of the configuration values has commenced.
    Once the script has completed successfully take note of the additional information it provides. In particular note down the SSH Certificate fingerprint, SSH Public key fingerprint, and Red Hat Enterprise Virtualization Manager URL for your records.

    Example 3.3. Successful Configuration

    Installing:
    Installing:
    Configuring RHEV Manager...                              [ DONE ]
    Creating CA...                                           [ DONE ]
    Editing JBoss Configuration...                           [ DONE ]
    Setting Database Configuration...                        [ DONE ]
    Setting Database Security...                             [ DONE ]
    Creating Database...                                     [ DONE ]
    Updating the Default Data Center Storage Type...         [ DONE ]
    Editing RHEV Manager Configuration...                    [ DONE ]
    Editing Postgresql Configuration...                      [ DONE ]
    Configuring the Default ISO Domain...                    [ DONE ]
    Configuring Firewall (iptables)...                       [ DONE ]
    Starting JBoss Service...                                [ DONE ]
    Configuring HTTPD...                                     [ DONE ]
    
     **** Installation completed successfully ******
         (Please allow RHEV Manager a few moments to start up.....)
    
    **** To access RHEV Manager browse to http://rhevm31.demo.redhat.com:80 ****
    
    Additional information:
     * RHEV Manager CA SSL Certificate SHA1 fingerprint: 45:BC:C2:78:D8:D5:58:C0:B9:A4:65:E1:5F:8F:5D:B4:71:5D:8E:7C
     * SSH Public key fingerprint: d3:4e:b3:3c:89:d2:dd:24:82:f5:6e:f8:4d:db:f6:d8
     * A default ISO share has been created on this host.
       If IP based access restrictions are required, please edit /usr/local/exports/iso entry in /etc/exports
     * The installation log file is available at: /var/log/ovirt-engine/engine-setup_2012_08_29_16_38_10.log
     * Please use the user "admin" and password specified in order to login into RHEV Manager
     * To configure additional users, first configure authentication domains using the 'rhevm-manage-domains' utility
    

Result
The Red Hat Enterprise Virtualization Manager has been installed and configured successfully. You are now able to connect to the Administration Portal for the first time.