Product SiteDocumentation Site

Chapter 4. Data Collection Setup and Reports Installation

The Red Hat Enterprise Virtualization Manager optionally includes a comprehensive management history database, which can be utilized by any application to extract a range of information at the data center, cluster, and host levels. As the database structure changes over time a number of database views are also included to provide a consistent structure to consuming applications. A view is a virtual table composed of the result set of a database query. The definition of a view is stored in the database as a SELECT statement. The result set of the SELECT statement populates the virtual table returned by the view. If the optional comprehensive management history database has been enabled, the history tables and their associated views are stored in the rhevm_history database.
In addition to the history database Red Hat Enterprise Virtualization Manager Reports functionality is also available as an optional component. Red Hat Enterprise Virtualization Manager Reports provides a customized implementation of JasperServer, and JasperReports. JasperServer is a component of JasperReports, an open source reporting tool, capable of being embedded in Java-based applications. It produces reports which can be rendered to screen, printed, or exported to a variety of formats including PDF, Excel, CSV, Word, RTF, Flash, ODT and ODS. Reports built in Red Hat Enterprise Virtualization Manager Reports are accessed via a web interface. In addition to a range of pre-configured reports and dashboards for monitoring the system, you are also able to create your own ad hoc reports.
Before proceeding with Red Hat Virtualization Manager Reports installation you must first have installed the Red Hat Enterprise Virtualization Manager, as described in Chapter 3, Manager Installation.
The Red Hat Enterprise Virtualization Manager Reports functionality depends on the presence of the history database, which is installed separately. Both the history database and the Red Hat Enterprise Virtualization Manager Reports are optional components. They are not installed by default when you install the Red Hat Enterprise Virtualization Manager.
Procedure 4.1. Install and Configure History Database
  1. Install Required Packages

    Use yum to initiate installation of the rhevm-reports-dwh package, or the rhevm-reports package if you also intend to install Red Hat Enterprise Virtualization Manager Reports. You must run this command as the root user on the system hosting the Red Hat Enterprise Virtualization Manager.
    • To install only the data warehouse package:
      # yum install rhevm-reports-dwh
    • To install both the data warehouse package and the Red Hat Enterprise Virtualization Manager Reports package:
      # yum install rhevm-reports
  2. Confirm Package Installation

    The required packages are downloaded. Once all packages have been downloaded they are listed for review. You will be prompted to confirm that you wish to continue with the installation. Once you have confirmed the operation yum installs the packages. Some further configuration is, however, required before the reports functionality can be used.
  3. Configure History Database

    You need to use the rhevm-dwh-setup command to configure the Extract, Transform, Load (ETL) process and database scripts used to create and maintain a working history database.
    1. You must run this command as the root user on the system hosting the Red Hat Enterprise Virtualization Manager.
      # rhevm-dwh-setup
    2. For the history database installation to take effect it is necessary to restart the jbossas service. The rhevm-dwh-setup command asks you:
      Would you like to stop the JBoss service? (yes|no):
      Type yes and then press Enter to proceed. The command then:
      • stops the jbossas service,
      • creates and configures the rhevm_history database, and
      • starts the jbossas service.
Result:
The rhevm_history database has been created. The Red Hat Enterprise Virtualization Manager is configured to log information to this database for reporting purposes.
Procedure 4.2. Install and Configure Red Hat Enterprise Virtualization Manager Reports
  1. Use yum to install the Red Hat Enterprise Virtualization Manager Reports package, rhevm-reports, if you did not already do this when performing the datawarehouse installation. This package must be installed on the system that the Red Hat Enterprise Virtualization Manager is installed. You must be logged in as the root user.
    # yum install rhevm-reports
  2. You must run this command as the root user on the system hosting the Red Hat Enterprise Virtualization Manager.
    # rhevm-reports-setup
  3. For the Red Hat Enterprise Virtualization Manager Reports installation to take effect it is necessary to restart the jbossas service. The rhevm-reports-setup command asks you:
    In order to proceed the installer must stop the JBoss service
    Would you like to stop the JBoss service? (yes|no):
    Type yes and then press Enter to proceed. The command then performs a number of actions before prompting you to set the password for the Red Hat Enterprise Virtualization Manager Reports administrative user (rhev-admin). Note that the reports system maintains its own set of credentials.
    Please choose a password for the admin user (rhevm-admin):
    You will be prompted to enter the password a second time to confirm it.
Result:
Red Hat Enterprise Virtualization Manager Reports have been installed successfully. Access Red Hat Enterprise Virtualization Manager Reports at http://demo.redhat.com:8080/rhevm-reports, replacing demo.redhat.com with the fully qualified domain name of the Red Hat Enterprise Virtualization Manager. If during Red Hat Enterprise Virtualization Manager installation you selected a non-default HTTP port replace 8080 with the port chosen.
Use the username rhevm-admin and the password you set during reports installation to log in for the first time. Note that the first time you log into Red Hat Enterprise Virtualization Manager Reports a number of web pages are generated, as a result your initial attempt to login may take some time to complete.