Developer Documentation
Much of this developer documentation provides historical context but may not reflect the current state of the project.
If you see outdated content please navigate to the page footer and click “Report an issue on GitHub”.
It is not user documentation and should not be treated as such.
User documentation is available here.
oVirt development teams
Design Documentation
Developer Process
Obsolete:
- The development process
- Release management
- Becoming a maintainer
- How to license a project
- New project acceptance criteria
Release process
Proposals
Development Help
- Building oVirt engine
- Install nightly snapshot
- Testing ovirt-engine patches with Lago
- VDSM Developers documentation
- FAQ
- HA VMs
- Migrate PKI to SHA256 signatures
- Networking
- Internal
- Infra
- Resources
- SLA
- Storage
- Permission system
- Audit Logs and Event Notifications
- Backend Bean Validation How-to
- Backend with jrebel
Containerization
Data Warehouse
Storage
VDSM Hooks
- directlun
- faqemu
- fileinject
- floppy
- isolatedprivatevlan
- network-nat
- numa
- pincpu
- promisc
- qemucmdline
- qos
- scratchpad
- smartcard
- smbios
- vhostmd
- vmdisk
- vmfex
Unit testing
- Injector Extension
- Mock Config Extension
- Mock Config Rule
- Random Utils Seeding Extension
- Random Utils Seeding Rule
- Testing Commands
- Testing Queries
Other
Obsolete:
Old releases management
- oVirt 3.0 release management
- oVirt 3.1 release management
- oVirt 3.2 release management
- oVirt 3.3 release management
- oVirt 3.4 release management
- oVirt 3.5 release management
- oVirt 3.6 release management