Creating a Database Engine

An engine definition provides detailed information about the backing database used by a cluster; only an EDB Ark administrative user can define an engine. Once defined, all of the engines that reside within a specific tenant will be made available to all users with access to that tenant. The Ark console ships with a number of default engine definitions.

You can also create custom database engines. To create a new database engine, right-click on the Database Engines node, and select Create, then Database Engine….

ARK database engine dialog general tab

Use fields on the General tab to provide information about the engine:

  • Use the Name field to provide a user-friendly name for the engine.
  • Use the Engine ID field to specify the identifier of the engine. The identifier must be unique, and cannot be modified after the engine definition is saved.
  • Use the Database Type drop-down listbox to select the database type (PostgreSQL or Advanced Server) that will be deployed on the engine. The database type cannot be modified after the engine definition is saved.
  • Use the Version drop-down listbox to select the database server version of the engine. The version cannot be modified after the engine definition is saved.
  • Use the Server type drop-down listbox to select the backing operating system that will be used by the engine.
ARK database engine dialog software packages tab

Use fields on the Software/Packages tab to provide information about the software that will be deployed on the engine:

  • Use the RHEL subscription drop-down listbox to select the RHEL subscription service that will be used when provisioning the engine. You can use the Create - RHEL Subscription dialog to propagate the RHEL subscription list.
  • Use the Yum repo URL(s) field to provide the names and credentials associated with one or more yum repositories from which software will be installed.
  • Use the Required packages field to provide a list of the software packages that are required by the specified server.
  • Use the Optional packages field to provide a list of the additional software packages that will be installed on clusters that are provisioned using the engine.

After defining the database engine click Save to add the engine to the Database Engines list in the PEM Browser tree control.

Before using the engine, the engine must be enabled. You can use options on the engine’s context menu to manage the engine.