• Stars
    star
    512
  • Rank 86,323 (Top 2 %)
  • Language
    Java
  • License
    Other
  • Created about 12 years ago
  • Updated 3 months ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

The oVirt Engine virtualization manager

oVirt Engine - Open Virtualization Manager

last build

Welcome to the oVirt Engine - Open Virtualization Manager source repository.

How to contribute

Submitting patches

Patches are welcome!

Please submit patches to github.com:ovirt-engine. If you are not familiar with the review process you can read about Working with oVirt on GitHub on the oVirt website.

Found a bug or documentation issue?

To submit a bug or suggest an enhancement for oVirt Engine please use oVirt GitHub issues.

If you find a documentation issue on the oVirt website please navigate and click "Report an issue on GitHub" in the page footer.

Still need help?

If you have any other questions, please join oVirt Users forum / mailing list and ask there.

Developer mode installation

Preparations

Prerequisites

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

Note on Java versions

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

Prepare your dev environment for java 11

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

$ sudo alternatives --config java

There are 4 programs which provide 'java'.

  Selection    Command
-----------------------------------------------
   1           java-latest-openjdk.x86_64 (/usr/lib/jvm/java-12-openjdk-12.0.1.12-1.rolling.fc30.x86_64/bin/java)
   2           java (/opt/jdk-9/bin/java)
   3           java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.3.7-5.fc30.x86_64/bin/java)
*+ 4           java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.212.b04-0.fc30.x86_64/jre/bin/java)

Enter to keep the current selection[+], or type selection number: 3

$ sudo alternatives --config javac

There are 2 programs which provide 'javac'.

  Selection    Command
-----------------------------------------------
*+ 1           java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.212.b04-0.fc30.x86_64/bin/javac)
   2           java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.3.7-5.fc30.x86_64/bin/javac)

Enter to keep the current selection[+], or type selection number: 2

- export `JAVA_HOME` if `mvn` is not executing using java-11:
```console
#put this in your ~/.bashrc
$ export JAVA_HOME=/lib/jvm/java-11

$ mvn -v | grep "Java version: "
Java version: 11.0.4, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-11-openjdk-11.0.4.11-0.fc30.x86_64

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

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.

System settings

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

/etc/security/limits.d/10-nofile.conf
<user> hard nofile 10240
#<user> soft nofile 10240  # optional, to apply automatically

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

$ ulimit -n 10240

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:

firewall-cmd --add-port=8080/tcp --permanent
firewall-cmd --add-port=8443/tcp --permanent
firewall-cmd --add-port=8787/tcp --permanent
firewall-cmd --add-port=54323/tcp --permanent

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

firewall-cmd --add-port=5432/tcp --permanent

Finally, apply changes using:

firewall-cmd --reload

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.

PostgreSQL accessibility

Initialize PostgreSQL configuration files:

$ sudo postgresql-setup --initdb --unit postgresql

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:

max_connections = 150
work_mem = 8MB
autovacuum_max_workers = 6
autovacuum_vacuum_scale_factor = 0.01
autovacuum_analyze_scale_factor = 0.075
maintenance_work_mem = 64MB

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

listen_addresses = '*'

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

Database creation

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

# su - postgres -c "psql -d template1"
template1=# create user engine password 'engine';
template1=# drop database engine;
template1=# create database engine owner engine template template0
encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8';
template1=# \q

Enable uuid-ossp extension for the database:

# su - postgres -c "psql -d engine"
engine=# CREATE EXTENSION "uuid-ossp";
engine=# \q

Ansible Runner configration

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

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.

Build

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

$ make clean install-dev PREFIX="${PREFIX}"
Note
${PREFIX} should be replaced with the location in which you intend to install the environment.
Note
Add SKIP_CHECKS=1 to disable tests.
Build targets
all

Build project.

clean

Clean project.

all-dev

Build project for development.

install-dev

Install a development environment at PREFIX.

dist

Create source tarball out of git repository.

maven

Force execution of maven.

generated-files

Create file from templates (.in files).

When creating new templates, generated files will be automatically appears in .gitignore, updated .gitignore should be part of committing new templates.
Build customization

The following Makefile environment variables are available for build customization:

PREFIX

Installation root directory. Default is /usr/local.

BUILD_GWT

Build GWT. Default is 1.

BUILD_ALL_USER_AGENTS

Build GWT applications for all supported browsers. Default is 0.

BUILD_LOCALES

Build GWT applications for all supported locales. default is 0.

BUILD_DEV

Add extra development flags. Usually this should not be used directly, as the all-dev sets this. Default is 0.

BUILD_UT

Perform unit tests during build. Default is 0.

BUILD_JAVA_OPTS_MAVEN

Maven JVM options. Can be defined as environment variable. Default is empty.

BUILD_JAVA_OPTS_GWT

GWT compiler and dev mode JVM options. Can be defined as environment variable. default is empty.

Note
Note that BUILD_JAVA_OPTS_GWT overrides BUILD_JAVA_OPTS_MAVEN when building GWT applications (BUILD_JAVA_OPTS_MAVEN settings still apply, unless overridden).
DEV_BUILD_GWT_DRAFT

Build "draft" version of GWT applications without optimizations. This is useful when profiling compiled applications in web browser. Default value is 0.

Following changes are applied for draft builds: - Prevent code and CSS obfuscation. - Reduce the level of code optimizations.

+ On local development environment, using GWT Super Dev Mode (see below) is preferred, as it automatically disables all optimizations and allows you to recompile the GWT application on the fly.

DEV_BUILD_GWT_SUPER_DEV_MODE

Allows debugging GWT applications via Super Dev Mode, using web browser’s JavaScript development tooling. Default value is 1.

Do a local Engine development build as you normally would. Then, start the Super Dev Mode code server as following:

$ make gwt-debug DEV_BUILD_GWT_SUPER_DEV_MODE=1

In your browser, open http://127.0.0.1:9876/ and save the "Dev Mode On" bookmark. Next, visit the GWT application URL (as served from Engine) and click "Dev Mode On". This allows you to recompile and reload the GWT application, reflecting any changes you’ve made in the UI code.

DEV_EXTRA_BUILD_FLAGS

Any maven build flags required for building.

For example, if your machine is low on memory, limit maximum simultaneous GWT permutation worker threads:

DEV_EXTRA_BUILD_FLAGS="-Dgwt.compiler.localWorkers=1"
DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS

Any maven build flags required for building GWT applications.

By default, GWT applications are built for Firefox only. To build for additional browsers, provide comma-separated list of user agents, see frontend/webadmin/modules/pom.xml for full list.

For example, to build for Firefox and Chrome:

DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=gecko1_8,safari"

To build for all supported browsers, use BUILD_ALL_USER_AGENTS=1.

For example, to build only the English and Japanese locale:

DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.locale=en_US,ja_JP"

To build for all supported locales, use BUILD_LOCALES=1.

For example to build engine without obfuscated Javascript code:

DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.style=pretty"

To build engine without obfuscated CSS styles:

DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.cssResourceStyle=pretty"
DEV_REBUILD

Disable if only packaging components were modified. Default is 1.

PY_VERSION

Python defaults to python3 if available, use PY_VERSION=2 in order to override.
This options affects various services and several features written in python.

Note
engine-setup which runs otopi, uses different customized variable OTOPI_PYTHON
WILDFLY_OVERLAY_MODULES

Change location of WildFly overlay modules. If you want to disable WildFly overlay configuration completely, please set to empty string. Default is /usr/share/ovirt-engine-wildfly-overlay/modules.

ISORT

Set name/location of the isort utility, which is used during make validations (also called from make install-dev). Defaults to isort. If not found, that’s ok. If found, should be at least version 5.7. The version in CentOS Stream 8 is ok. The version provided by RHEL 8 (and rebuilds) is too old, 4.3. Some ways to get a newer version:

  • dnf copr enable -y sbonazzo/EL8_collection

  • Install from pypi in a python virtualenv/venv, e.g.:

sudo dnf install python3-virtualenv
mkdir -p $HOME/venv
cd $HOME/venv
virtualenv-3 python3-isort
. python3-isort/bin/activate
pip install isort

And, before running make,

export ISORT=$HOME/venv/python3-isort/bin/isort

If you do have an older version installed and want make to ignore it, you can point the variable at some non-existing name/location, e.g.:

export ISORT=nonexistent

Setup

To setup the product use the following command:

$ "${PREFIX}/bin/engine-setup"
Note
otopi, and therefore engine-setup, now defaults to python3 except el7, use:
$ OTOPI_PYTHON=/usr/bin/python2 "${PREFIX}/bin/engine-setup"
to override.

During engine setup, a certificate has to be issued and you will be asked for a hostname. If you want to upload and download images from administration portal, it has to be the name by which your machine is accessible from the outside.

JBoss

If you want to use different WildFly/EAP installation, specify it at --jboss-home= parameter of setup.

Environment

OVIRT_ENGINE_JAVA_HOME

Select a specific Java home.

OVIRT_ENGINE_JAVA_HOME_FORCE

Set to non zero to bypass Java compatibility check.

Refresh

If there are no significant changes, such as file structure or database schema, there is no need to run the setup again, make install-dev <args> will overwrite files as required, run engine-setup to refresh database schema.

Do remember to restart the engine service.

If there is a significant change, safest path is to stop service, remove ${PREFIX} directory, build and setup.

The ${PREFIX}/bin/engine-cleanup tool is also available to cleanup the environment, it is useful for application changes, less for packaging changes.

Service administration

Most utilities and services are operational, including PKI, host deploy.

To start/stop the engine service use:

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

While the service is running, this command will not exit. Press <Ctrl>-C to stop service.

Access using HTTP or HTTPS:

Remote debug

By default, debug address is 127.0.0.1:8787. If you want to make engine accessible to the remote debugger, after running engine-setup edit the following file: ${PREFIX}/etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf:

ENGINE_DEBUG_ADDRESS=0.0.0.0:8787

Running instance management (JMX)

ovirt-engine service supports jmx as management interface. Actually, this is the standard jboss jmx interface, while authentication can be done using any engine user with SuperUser role. Access is permitted only from the local host.

Access JMX shell using provide OPTIONAL_COMMAND for non interactive usage:

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

Useful commands:

Modify log level
/subsystem=logging/logger=org.ovirt.engine.core.bll:write-attribute(name=level,value=DEBUG)
Create a new log category
/subsystem=logging/logger=org.ovirt.engine:add
Get the engine data-source statistics
ls /subsystem=datasources/data-source=ENGINEDataSource/statistics=jdbc/
Get threading info
ls /core-service=platform-mbean/type=threading/

By default JMX access is available only to localhost, to open JMX to world, add ${PREFIX}/etc/ovirt-engine/engine.conf.d/20-setup-jmx-debug.conf with:

ENGINE_JMX_INTERFACE=public

DAO tests

Create empty database for DAO tests refer to Database creation.

Provided user is engine, password is engine and database is engine_dao_tests.

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

Run build as:

$ 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"

VM console

After the environment is setup and installed, some adjustments are required.

Copy vmconsole-host configuration:

$ 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

If selinux is enabled on your machine, set type on vmconsole helper using:

$ sudo chcon --type=bin_t "${PREFIX}/libexec/ovirt-vmconsole-proxy-helper/ovirt-vmconsole-list.py"

ovirt-imageio

After setup, you need to run ovirt-imageio manually if you want to upload and download images via the administration portal. To run ovirt-imageio, run the following command:

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

This assumes you have installed ovirt-imageio-daemon and you have run engine-setup.

In development mode, ovirt-imageio logs to stderr using DEBUG level. If you would like to log to a file create a log directory:

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

And install a drop-in configuration file to override engine developement setup:

$ 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',)

RPM packaging

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

The following spec file variables are available for package customization:

ovirt_build_quick

Quick build, best for syntax checks. Default is 0.

ovirt_build_minimal

Build minimal Firefox only package. Default is 0.

ovirt_build_user_agent

When using quick or minimal build, build only for this user agent. Default is gecko1_8 (Firefox). To build for Chrome use safari.

ovirt_build_gwt

Build GWT components. Default is 1.

ovirt_build_all_user_agents

Build GWT components for all supported browsers. Default is 1.

ovirt_build_locales

Build GWT components for all supported locales. Default is 1.

Examples:

Build minimal rpm package for Firefox

$ rpmbuild -D"ovirt_build_minimal 1" -tb @tarball@

Build minimal rpm package for Chrome or Safari

$ rpmbuild -D"ovirt_build_minimal 1" -D"ovirt_build_user_agent safari" -tb @tarball@

Ansible Lint

To use ansible-lint locally you need to install it from PyPI in a python virtualenv/venv, e.g.:

sudo dnf install python3-virtualenv
mkdir -p $HOME/venv
python3 -m venv $HOME/venv/ansible-lint
. $HOME/venv/ansible-lint/bin/activate
pip3 install "ansible-lint>=6.0.0,<7.0.0"

Run of the lint:

$ ansible-lint -c build/ansible-lint.conf packaging/ansible-runner-service-project/project/roles/*

Branch/release management

Git branch master should always have the latest version.

Releases should be done from stable branches. So-called "bump patches", to increase the version, should be created using the script bump_release.sh. This creates two git commits - one for doing the release, which should be tagged, and the next one for getting back to development builds, which have a timestamp+git-hash in their RPMs names.

When branching stable branches, master branch should be bumped to the next Y or Z version. There is currently no script for doing that. It can be done using something like:

find . -name pom.xml -exec sed -i "s:4.5.1.3-SNAPSHOT:4.5.2-SNAPSHOT:" {} +

Replace 4.5.1.3 with the current version, and 4.5.2 with the version you want to bump to.

More Repositories

1

vdsm

The Virtual Desktop Server Manager
Python
160
star
2

terraform-provider-ovirt

Terraform provider for oVirt 4.x
Go
137
star
3

ovirt-web-ui

Modern lightweight UI for standard (non-admin) oVirt users
JavaScript
115
star
4

ovirt-ansible

This project has been archived, development moved to https://github.com/ovirt/ovirt-ansible-collection
Shell
94
star
5

ovirt-site

oVirt website
Sass
87
star
6

ovirt-engine-sdk

oVirt Python SDK
Python
86
star
7

ovirt-ansible-collection

Ansible collection with official oVirt modules and roles
Python
71
star
8

moVirt

A mobile client for oVirt
Java
50
star
9

cockpit-ovirt

cockpit-ovirt: oVirt plugin for Cockpit Project
JavaScript
36
star
10

ovirt-container-engine

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
Shell
35
star
11

ovirt-node

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
Python
34
star
12

ovirt-ansible-vm-infra

This project has been archived, development moved to https://github.com/ovirt/ovirt-ansible-collection
Python
34
star
13

ovirt-ansible-hosted-engine-setup

Python
33
star
14

512-byte-vm

A VM image in 512 bytes. Yes, you read it right.
Assembly
33
star
15

ovirt-openshift-extensions

Implementation of flexvolume driver and provisioner for oVirt
Go
31
star
16

go-ovirt

Go SDK Source-Code for oVirt 4.x, generated by ovirt/ovirt-engine-sdk-go.
Go
29
star
17

ovirt-guest-agent

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
C
25
star
18

ovirt-ansible-infra

This project has been archived, development moved to https://github.com/ovirt/ovirt-ansible-collection
Shell
24
star
19

ovirt-ansible-image-template

This project has been archived, development moved to https://github.com/ovirt/ovirt-ansible-collection
Shell
23
star
20

ovirt-engine-sdk-java

The oVirt Java SDK
Java
23
star
21

ovirt-engine-sdk-ruby

Ruby gem that simplyfies access to the oVirt Engine API
Ruby
20
star
22

ovirt-node-ng-image

The source for oVirt Node NG installer ISO and RPM image
Shell
20
star
23

ovirt-imageio

The oVirt image transfer daemon and clients.
Python
19
star
24

ovirt-engine-api-model

oVirt Engine API Model
Java
19
star
25

ovirt-engine-sdk-go

The generator of Go SDK for oVirt v4.0+
Go
19
star
26

ovirt-provider-ovn

This is a repository for ovirt-provider-ovn.
Python
19
star
27

mom

oVirt Memory Overcommitment Manager, a tool for managing overcommitment on KVM hosts.
Python
18
star
28

ovirt-hosted-engine-setup

Hosted Engine setup tool for the oVirt project
Python
18
star
29

ovirt-appliance

Appliance for oVirt Engine: an OVA shipping CentOS Stream and oVirt Engine, wrapped in an RPM.
Python
18
star
30

csi-driver

oVirt's CSI driver for Openshift and Kubernetes
Go
17
star
31

ovirt-ansible-disaster-recovery

This project has been archived, development moved to https://github.com/ovirt/ovirt-ansible-collection
Python
17
star
32

jenkins

Python
16
star
33

ovirt-ansible-engine-setup

This project is now archived, development moved to https://github.com/ovirt/ovirt-ansible-collection
HTML
15
star
34

ovirt-node-ng

This repository contains the code of the nodectl tool used within oVirt Node NG. The repository which contains the code for building oVirt Node NG is at https://github.com/oVirt/ovirt-node-ng-image.
Python
15
star
35

python-ovirt-engine-sdk4

Python SDK for version 4 of the oVirt Engine API
Python
14
star
36

ovirt-system-tests

This repository includes automated tests executed on the whole oVirt distribution
Python
13
star
37

ovirt-engine-extension-aaa-ldap

oVirt Engine AAA LDAP Extension
Java
13
star
38

java-client-kubevirt

Kubevirt java client (java-client-kubevirt) for oVirt
Java
13
star
39

cluster-api-provider-ovirt

Machine API implementation for oVirt
Go
13
star
40

go-ovirt-client

An easy-to-use overlay for the Go SDK.
Go
12
star
41

Node

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
Python
11
star
42

ovirt-ansible-cluster-upgrade

This project has been archived, development moved to https://github.com/ovirt/ovirt-ansible-collection
Shell
11
star
43

ocp-on-ovirt

this repo contains all the tools and automations for ocp-on-rhv CI.
Go
11
star
44

ovirt-containers

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
Go
10
star
45

otopi

otopi - oVirt Task Oriented Pluggable Installer/Implementation.
Python
10
star
46

ovirt-ansible-manageiq

This project has been archived, development moved to https://github.com/ovirt/ovirt-ansible-collection
Shell
10
star
47

ovirt-ansible-repositories

This Ansible role is used to set up the repositories required for oVirt engine or host installation.
Shell
9
star
48

ovirt-ansible-dpdk-setup

This project hasn't been maintained for quite some time, so it's archived
Python
9
star
49

v2v-conversion-host

Python
9
star
50

ovirt-vdsmfake

This is a mirror for http://gerrit.ovirt.org, for issues use https://github.com/oVirt/ovirt-vdsmfake/issues
Java
9
star
51

ovirt-release

This package contains the yum configuration for oVirt repositories.
Makefile
9
star
52

imgbased

imgbased provides a specific management method to derive writeable filesystem layers from read-only base images.
Python
8
star
53

vdsm-jsonrpc-java

JSON RPC Java client for oVirt
Java
8
star
54

ovirt-engine-dashboard

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
JavaScript
8
star
55

ovirt-engine-api-metamodel

oVirt Engine API Metamodel
Java
8
star
56

ovirt-engine-metrics

Used to configure and deploy oVirt metrics, logs collection and integration with the central metrics store
Shell
8
star
57

ovirt-engine-ui-extensions

UI Plugins that provides various extensions to the oVirt Administration Portal.
JavaScript
8
star
58

ovirt-openvswitch

This is a repository for ovirt-openvswitch.
Shell
7
star
59

gerrit-admin

Python
7
star
60

ovirt-vmconsole

Enables secure access to virtual machine serial console in oVirt environment.
Python
6
star
61

ovirt-engine-keycloak

Package that provides Keycloak overlay configuration to be run on oVirt Engine's Widlfly/EAP instance
Python
6
star
62

cockpit-machines-ovirt-provider

6
star
63

ovirt-ansible-shutdown-env

ovirt-ansible-shutdown-env Ansible role
Shell
6
star
64

ovirt-engine-extension-aaa-jdbc

Java
6
star
65

releng-tools

Release management tools and configuration files for oVirt release engineering
Python
6
star
66

ovirt-live

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
Makefile
6
star
67

ovirt-dwh

oVirt Engine Data Warehouse
Java
5
star
68

engine-db-query

engine-db-query is a tool and python module to query the oVirt engine database.
Python
5
star
69

ovirt-hosted-engine-ha

Hosted engine manager for oVirt project.
Python
5
star
70

ost-images

qcow images for OST
Shell
5
star
71

ovirt-wgt

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
NSIS
5
star
72

infra-docs

Python
5
star
73

ovirt-design

Design repository for all things oVirt
CSS
5
star
74

ovirt-ui-components

Reusable components for Open Virtualization UIs
JavaScript
5
star
75

ovirt-lldp-labeler

The oVirt Link Layer Discovery Protocol labeler
Python
4
star
76

ovirt-engine-cli

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
Python
4
star
77

ovirt-engine-api-explorer

This project has been obsoleted in oVirt 4.4.3 and it's no longer used
JavaScript
4
star
78

ioprocess

IOProcess - preventing D state on I/O with Python
C
4
star
79

ovirt-container-node

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
4
star
80

ovirt-cockpit-sso

Provides SSO from oVirt's Administration portal to Cockpit running on an oVirt's host
Shell
4
star
81

ovirt-optimizer

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
Java
4
star
82

ovirt-host

This meta package pulls in all the dependencies needed for an oVirt hosts.
Makefile
4
star
83

ovirt-engine-kerbldap-migration

A package to ease migration from oVirt engine legacy LDAP provider into the new ovirt-engine-extension-aaa-ldap provider.
Python
4
star
84

ovirt-setup-lib

oVirt setup common library
Python
3
star
85

samples-uiplugins

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
JavaScript
3
star
86

ovirt-jboss-modules-maven-plugin

Maven plugin to generate JBoss Modules configuration files for dependencies
Java
3
star
87

ovirt-engine-wildfly

WildFly packaging for oVirt Engine consumption
Shell
3
star
88

ovirt-log-collector

Log Collector tool for oVirt Engine
Python
3
star
89

ovirt-iso-uploader

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
Roff
3
star
90

ocp-lab-setup

set up oVirt/RHV in a lab
Shell
3
star
91

repoman

Manage artifact repositories
Python
3
star
92

ovirt-engine-extension-aaa-misc

oVirt Engine AAA Misc Extension
Java
3
star
93

buildcontainer

Container image for building oVirt
3
star
94

ovirt-jenkins-plugin

Jenkins plugin to run agents using oVirt
3
star
95

csi-driver-operator

Operator for deploying oVirt CSI driver
Go
3
star
96

ovirt-engine-extensions-api

oVirt Engine Extensions API definition
Java
3
star
97

k8sOVirtCredentialsMonitor

Monitor k8s secrets and update the oVirt connection
Go
3
star
98

ovirt-dependencies

dependencies for the oVirt engine
Shell
3
star
99

ovirt-host-deploy

This is a mirror for http://gerrit.ovirt.org, for issues use http://bugzilla.redhat.com
Python
3
star
100

ovirt-engine-nodejs-modules

Hold the nodejs dependencies needed to build oVirt JavaScript applications with yarn offline
JavaScript
3
star