このコンテンツは選択した言語では利用できません。
Chapter 1. Installing and Configuring Data Warehouse
1.1. Overview of Configuring Data Warehouse
You can install and configure Data Warehouse on the same machine as the Manager, or on a separate machine with access to the Manager:
- Install and configure Data Warehouse on the Manager machine
- This configuration requires only a single registered machine, and is the simplest to configure, but it increases the demand on the Manager machine. Users who require access to the Data Warehouse service require access to the Manager machine itself. See Configuring the Red Hat Virtualization Manager in Installing Red Hat Virtualization as a standalone Manager with local databases.
- Install and configure Data Warehouse on a separate machine
- This configuration requires two registered machines. It reduces the load on the Manager machine and avoids potential CPU and memory-sharing conflicts on that machine. Administrators can also allow user access to the Data Warehouse machine, without the need to grant access to the Manager machine. See Section 1.2, “Installing and Configuring Data Warehouse on a Separate Machine” for more information on this configuration.
It is recommended that you set the system time zone for all machines in your Data Warehouse deployment to UTC. This ensures that data collection is not interrupted by variations in your local time zone: for example, a change from summer time to winter time.
To calculate an estimate of the space and resources the ovirt_engine_history database will use, use the RHV Manager History Database Size Calculator tool. The estimate is based on the number of entities and the length of time you have chosen to retain the history records.
The following behavior is expected in engine-setup:
-
Install the Data Warehouse package, run
engine-setup, and answerNoto configuring Data Warehouse:
Configure Data Warehouse on this host (Yes, No) [Yes]: No
-
Run
engine-setupagain; setup no longer presents the option to configure Data Warehouse.
To force engine-setup to present the option again, run engine-setup --reconfigure-optional-components.
To configure only the currently installed Data Warehouse packages, and prevent setup from applying package updates found in enabled repositories, add the --offline option .
