Local or Remote Hosting
The following components can be hosted on either the {engine-name} or a remote machine. Keeping all components on the {engine-name} machine is easier and requires less maintenance, so is preferable when performance is not an issue. Moving components to a remote machine requires more maintenance, but can improve the performance of both the {engine-name} and Data Warehouse.
- Data Warehouse database and service
-
To host Data Warehouse on the {engine-name}, select
Yes
when prompted byengine-setup
.To host Data Warehouse on a remote machine, select
No
when prompted byengine-setup
, and see Installing and Configuring Data Warehouse on a Separate Machine in Installing {virt-product-fullname} as a standalone {engine-name} with remote databases.To migrate Data Warehouse post-installation, see Migrating Data Warehouse to a Separate Machine in the Data Warehouse Guide.
You can also host the Data Warehouse service and the Data Warehouse database separately from one another.
- {engine-name} database
-
To host the {engine-name} database on the {engine-name}, select
Local
when prompted byengine-setup
.To host the {engine-name} database on a remote machine, see Preparing a Remote PostgreSQL Database in Installing {virt-product-fullname} as a standalone {engine-name} with remote databases before running
engine-setup
on the {engine-name}. - Websocket proxy
-
To host the websocket proxy on the {engine-name}, select
Yes
when prompted byengine-setup
.
Self-hosted engine environments use an appliance to install and configure the {engine-name} virtual machine, so Data Warehouse, the {engine-name} database, and the websocket proxy can only be made external post-installation. |
Remote Hosting Only
The following components must be hosted on a remote machine:
- DNS
-
Due to the extensive use of DNS in a {virt-product-fullname} environment, running the environment’s DNS service as a virtual machine hosted in the environment is not supported.
- Storage
-
With the exception of local storage, the storage service must not be on the same machine as the {engine-name} or any host.
- Identity Management
-
IdM (
ipa-server
) is incompatible with themod_ssl
package, which is required by the {engine-name}.