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.
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.
Backend modules vdsbroker
Introduction: VDS (=Host) broker is a collection of commands that are host-related. Each host is instantiated a VdsManager, and every host-related command is eventually trickled to that hosts’ VdsManager. Before reading on, it is recommended to read the Backend modules bll page in order to gain an understanding of how commands work in oVirt.
Commands: Like bll commands, VDS commands have a strict naming convention that the VDS commands factory relies on to instantiate vds commands. The naming convention is *VDSCommand. VDS commands can be classified in to two main types:
- Executor commands - Run code that actually implements a command
- Pre/post commands - Run code before or after executor commands
Commands can then be further classified into two additional categories, independent from the previous classification:
- IRS (=SPM) commands - Storage related commands, or commands related to the host selected as the Service Pool Manager
- VDS commands - Non-SPM commands