Install the following system components:

• java-11-openjdk-devel

• mime-types or mailcap

• unzip

• openssl

• bind-utils

• postgresql-server >= 12.0

• postgresql >= 12.0

• postgresql-contrib >= 12.0

• python3-dateutil / dateutil

• python3-cryptography / cryptography

• python3-m2crypto / m2crypto

• python3-psycopg2 / psycopg

• python3-jinja2 / Jinja2

• python3-libxml2 / libxml2[python]

• python3-daemon

• python3-otopi >= 1.10.0

• python3-ovirt-setup-lib

• maven >= 3.5

• ansible-core >= 2.12.0

• ansible-runner >= 2.1.3

• ovirt-ansible-roles >= 1.2.0

• ovirt-imageio-daemon >= 2.0.6

• ovirt-engine-metrics (optional)

• ovirt-provider-ovn (optional)

• python3-ovirt-engine-sdk4 (optional)

• ansible-lint / python3-ansible-lint (optional)

• python3-flake8 / pyflakes (optional)

• python3-pycodestyle / pycodestyle (optional)

• python3-isort (optional)

• python3-distro

The project is built and run using java 11. 4.3 branches and earlier are excluded.

• Use alternatives command to configure java and javac to version 11:

WildFly 15 is required along with ovirt-engine-wildfly-overlay. Preferred way is to install following packages:

• ovirt-engine-wildfly

• ovirt-engine-wildfly-overlay

Both packages can be installed from oVirt COPR CentOS repositories. Repository list can be updated using the following commands:

+ $ sudo dnf copr enable -y ovirt/ovirt-master-snapshot centos-stream-8 $ sudo dnf install -y ovirt-release-master

• For more info see copr master-snapshot repositories.

OVN/OVS is an optional dependency. If you want to use it, check the requirements in the ovirt-engine.spec.in file for a list of packages. Otherwise, you should reply 'No' when asked about it by engine-setup.

Build locales requires at least 10240 file descriptors, create the following file, replace <user> with user that is used for building, and logout/login:

If soft limit was not set, before building, apply new limit using:

Development environment by default uses ports 8080 (HTTP), 8443 (HTTPS), 8787 (java debug), and 54323 (ovirt-imageio-proxy) so make sure they are accessible from the outside. For example:

If you also want to connect to the database from the outside:

Finally, apply changes using:

If compiling in a virtual machine, javac might experience difficulties on guests with dynamically growing RAM so it’s better to have VM’s starting allocation and maximum allocation set to the same value.

Initialize PostgreSQL configuration files:

Configure PostgreSQL to accept user and password:

Locate pg_hba.conf within your distribution, common locations are:

• /var/lib/pgsql/data/pg_hba.conf

• /etc/postgresql-*/pg_hba.conf

• /etc/postgresql/*/main/pg_hba.conf

Within pg_hba.conf set method to password for 127.0.0.1/32 and ::1/128 for IPv4 and IPv6 local connections correspondingly.

If you want to make postgres accessible from the outside, change 127.0.0.1/32 to 0.0.0.0/0 and ::1/128 to ::/0.

Tune PostgreSQL configuration: Locate postgresql.conf within your distribution, common locations are:

• /var/lib/pgsql/data

• /etc/postgresql*

Within postgresql.conf make sure following values are set:

If you want to connect from the outside, set also:

Enable and start (systemctl enable postgresql --now).

Create database for ovirt-engine, usually the following sequence should work to create a user named engine that owns database named engine:

Enable uuid-ossp extension for the database:

Since oVirt 4.5 the engine is integrated with ansible-core and ansible-runner, so you need to install RPM packages for both, but not additional configuration is required.

All previously used configuration for ansible-runner-service is no longer relevant and 'ansible-runner-service*' packages and configuration can be removed.

Development environment is supported only under non-root account. Do not run this sequence as root.

Each instance of application must be installed at different PREFIX and use its own database. Throughout this document application is installed using PREFIX="${PREFIX}" and engine database and user, these should be changed if a new instance is required. Do not mix different versions of product with same PREFIX/database.

From this point on, the "${PREFIX}" will be used to mark the prefix in which you selected to install the development environment.

To build and install ovirt-engine at your home folder under ovirt-engine directory execute the following command:

$ "${PREFIX}/bin/engine-setup"

$ "${PREFIX}/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py" start

ENGINE_DEBUG_ADDRESS=0.0.0.0:8787

$ "${JBOSS_HOME}/bin/jboss-cli.sh" \
  --connect \
  --timeout=30000 \
  --controller=localhost:8706 \
  --user=admin@internal \
  --commands="OPTIONAL_COMMA_SEPARATED_COMMANDS"

ENGINE_JMX_INTERFACE=public

$ PGPASSWORD=engine \
  ./packaging/dbscripts/schema.sh \
    -c apply -u engine -d engine_dao_tests

$ make maven BUILD_GWT=0 BUILD_UT=1 EXTRA_BUILD_FLAGS="-P enable-dao-tests \
  -D engine.db.username=engine \
  -D engine.db.password=engine \
  -D engine.db.url=jdbc:postgresql://localhost/engine_dao_tests"

$ sudo cp -p "${PREFIX}/share/ovirt-engine/conf/ovirt-vmconsole-proxy.conf \
/etc/ovirt-vmconsole/ovirt-vmconsole-proxy/conf.d/50-ovirt-vmconsole-proxy.conf

$ ovirt-imageio --conf-dir $PREFIX/etc/ovirt-imageio

$ mkdir $PREFIX/var/log/ovirt-imageio

$ cat $PREFIX/etc/ovirt-imageio/conf.d/99-local.conf
[handlers]
keys = logfile

[logger_root]
handlers = logfile

[handler_logfile]
args = ('/home/username/ovirt-engine/log/ovirt-imageio/daemon.log',)

$ make dist
$ rpmbuild -ts @tarball@
# yum-builddep @srpm@
# rpmbuild -tb @tarball@